home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
da2dem.zip
/
READ.ME
< prev
next >
Wrap
Text File
|
1993-12-17
|
21KB
|
494 lines
INTRODUCING DISTRIBUTED APPLICATION/2 (DA/2)
- Demonstration Version -
┌──────────────────────────────────────────────────────────────────────────┐
│ *** NOTICE *** │
│ This version of DA/2 was developed especially for the IBM Developer's │
│ Connection for OS/2 CD-ROM. It has also been uploaded to CompuServe and │
│ the OS/2 BBS. │
│ │
│ You will be able to write sample programs to see the capability of │
│ DA/2. However, the only data that will flow between a client and │
│ a server are the words "Developers Connection". │
└──────────────────────────────────────────────────────────────────────────┘
Distributed Application/2 is a set of application programming interfaces
(APIs) that provide a consistent way to access interprocess and network com-
munication functions under Operating System/2(*) (OS/2*), making
client/server applications easier to create than ever. Distributed
Application/2 supplies you with a set of APIs designed to help you compete in
the growing client/server programming arena. The Distributed Application/2
APIs hide the complexity of the supported communications protocols and enable
you to select a communications protocol for your application at run time
without requiring you to change your code.
Distributed Application/2 supports the following communications protocols:
o Advanced program-to-program communication (APPC)
o NetBIOS
o OS/2 named pipes
By supporting these multiple protocols, Distributed Application/2 APIs can be
used to communicate between two threads in a process, two processes in an
application, two modules across a network, or within a program on a single
machine. You just choose the protocol you wish to use for each communication
conversation.
Specifically, Distributed Application/2 starts with a set of simple APIs that
support the transfer of data through the concepts of OPEN, WRITE, READ, and
CLOSE. These APIs also include features designed to make synchronization
between components easier, such as waiting for a specific message.
Distributed Application/2 also provides you with a set of advanced APIs
designed for the server. These, together with the OPEN, WRITE, READ, and
CLOSE APIs, provide an easy mechanism to synchronize communication between
your running server and multiple clients.
The Distributed Application/2 APIs have been enabled for C and REXX; This
allows you to write distributed applications in multiple programming lan-
guages.
You can also use Distributed Application/2 to communicate between
program using Distributed Application/2 and a partner using native APPC calls.
This includes:
- APPC calls supported by Information Management System (IMS) V4.1
on an MVS host system
- APPC calls supported by Information Management System (IMS)
using the LU 6.1-LU 6.2 adapter for applications on an MVS host system
- APPC calls supported by the DA2SERV CICS program that we provide. This
gives you access to CICS applications that are not 3270 oriented.
- Other APPC subsystems
When you purchase Distributed Application/2, you receive:
o The APIs enabled for C and REXX
o Complete online documentation for the APIs
o A user-interface facility to manage run-time information
o A utility to rename the redistributable components
o The object file of the host CICS server program for catching
requests from DA/2 programs.
SPECIFIED OPERATING ENVIRONMENT
_______________________________
MACHINE REQUIREMENTS
o A personal computer running OS/2 Version 2.0 or 2.1.
NOTE: For more information on the OS/2 Version 2.0 machine requirements,
refer to the IBM OS/2 Version 2.0 Information and Planning Guide
___________________________________________________
(G326-0160)
o 1 MB of hard disk space above that required by OS/2
o .5 MB of memory above that required by OS/2
o 2-button mouse or other pointing device
PROGRAM REQUIREMENTS
o OS/2 Version 2.0 operating system (with ServicePak XR06055)
o IBM Developers Toolkit for OS/2 Version 2.0.
o OS/2 Version 2.1 operating system
o To use Distributed Application/2 with NetBIOS, you need one of the
following:
- The LAN Requester feature of OS/2 LAN Server Version 2.0,
in which case any NetBIOS communication partners must also have
an IBM LAN requester installed.
- The LAN Requester feature of OS/2 LAN Server Version 3.0,
in which case any NetBIOS communication partners must also have
an IBM LAN requester installed.
- Novell(**) NetWare(**) Requester for OS/2 2.0 with the Novell
NetBIOS emulator, in which case any NetBIOS communication
partners must also have the Novell NetWare requester installed.
o To use Distributed Application/2 with APPC, you also need Extended Ser-
vices for OS/2 Version 2.0 or Communications Manager/2.
Note: If you are using OS/2 Version 2.0, you should have ServicePak
XR06055. However, you may find that Distributed Application/2
runs on a machine without the SevicePak.
Please note, however, that service for Distributed Application/2
is provided only for systems that meet the Program Requirements
listed above.
INSTALLING DISTRIBUTED APPLICATION/2
____________________________________
This section contains information needed to install this demonstration
version of Distributed Application/2. You will use the standard Distributed
Application/2 installation process that you would use after purchasing
the product. However, in this case, you will be using a directory on
your hard disk as the "source" of the installation, instead of a diskette
drive.
Since you are reading this READ.ME file, we assume you have
unpacked the DA2DEM.ZIP file, and its contents are all in one directory.
This will be used as the "source" directory for the installation.
For purposes of this explanation, the directory is called C:\DA2DEMO.
1. Type the following on the OS/2 command line:
C:\DA2DEMO\INSTALL
3. Press Enter.
4. Follow the on-screen prompts displayed by the installation and
maintenance utility.
You are now ready to use Distributed Application/2. You can erase all of
the files in the "source" installation directory (C:\DA2DEMO). After you are
finished using the demo, you can use the Installation Utility to delete it.
Open the DA/2 folder, and use the delete option of the utility.
UPDATING YOUR CONFIG.SYS FILE MANUALLY
The installation and maintenance utility copies all the files necessary to
run Distributed Application/2 to your computer's hard disk and automatically
updates your CONFIG.SYS file.
If you want to override the default settings and make your own changes to the
CONFIG.SYS file, select UPDATE CONFIG.SYS from the Install window and remove
the check from the checkbox.
Distributed Application/2 installs its files in subdirectories of C:\IBMDA.
However, you can override this directory setting at the time of installation
to give the C:\IBMDA directory a different name or to put it on a different
drive. The following list shows which directories need to be added to the
statements in your CONFIG.SYS file.
NOTE: If you choose a directory other than C:\IBMDA, these directories will
be different on your system.
+-------------------------------------+-------------------------------------+
| ADD THIS DIRECTORY: | TO THE: |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BIN | LIBPATH |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BIN | PATH |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BIN | INCLUDE |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BIN | LIB |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BIN | HELP |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\BOOK | BOOKSHELF |
+-------------------------------------+-------------------------------------+
| C:\IBMDA\CICS\SAMPLES | PATH |
+-------------------------------------+-------------------------------------+
Also be sure that any directory in which you intend to keep a connection
profile file (IBMDABB.CP) is added to your DPATH.
ACCESSING THE ONLINE DOCUMENTATION
When you install Distributed Application/2, the installation and maintenance
utility optionally installs the following documents:
o IBM Distributed Application/2 C Guide and Reference
___________________________________________________
o IBM Distributed Application/2 REXX Guide and Reference
______________________________________________________
To access these online documents from the OS/2 command line, do the
following:
1. Change to the directory in which you want to view the online documents.
The default directory name is C:\IBMDA.
2. Type the following on the OS/2 command line:
o "VIEW EPFDACG.INF" to access the Distributed Application/2 C Guide
_________________________________
o "VIEW EPFDARXG.INF" to access the Distributed Application/2 REXX
______________________________
Guide
_____
3. Press Enter. You will see the Contents window.
4. Double-click on the topic you want to view.
RUNNING THE DISTRIBUTED APPLICATION/2 (DA/2) SAMPLES
____________________________________________________
We assume you have installed the product (or demonstration version),
and have re-booted your PC so that the new PATH and LIBPATH statements
in your CONFIG.SYS have been activated. For this explanation, we'll
use C:\IBMDA as the name of the directory into which you have installed
DA/2. If you installed DA/2 into a different directory, you'll need to
use that name in place of C:\IBMDA in the instructions. We describe how
to run the REXX sample, and the C sample. You can run either one
(or both) by following these instructions.
Running the REXX Sample
-----------------------
1. >Make the samples directory current.< In an OS/2 window command
prompt, run these commands, pressing enter after each one:
C:
CD C:\IBMDA\SAMPLES
2. >Run the REXX sample.< From the same window command prompt, run the
client portion of the sample by running this command:
RXCLIENT
2a. >Specify the symbolic name.< The sample will prompt you for the
symbolic name of the connection. Enter this:
RXSAMPLE
Hint: You can discover which connections are defined for the samples
by starting the Connection Profile Editor from the DA/2 folder on
the desktop. Then use the File/Open... pulldown to open this file:
C:\IBMDA\SAMPLES\IBMDABB.CP
Note: +---> IBMDABB = DA/2
+---> .CP = Connection Profile
Each connection defined in the profile is displayed as an icon, with
its symbolic name below. You can double-click on any of the icons
to examine the details and parameters for that connection.
2b. >Note how the server gets started.< DA/2 can automatically start
server programs for you, if they're not already running. The REXX
sample starts the server program, RXSERVER.CMD, in an OS/2 window.
In this sample, the server terminates after the connection is
closed.
2c. >Some errors matter, and some don't.< You should see some character
strings displayed on the client window. If you see 'Invalid Response'
messages in the window, it means you're running the demonstration
version of the DA/2. That's ok. Other error messages usually mean
you have not installed DA/2 correctly.
3. >Learn more by examining the documentation and sample code.< You should
take some time to look at the source code for the samples, and the
online documentation. This will help you understand more about how
DA/2 works, and how you can use it to build your client/server
applications.
Running the C Sample
--------------------
1. >Make the samples directory current.< In an OS/2 window command
prompt, run these commands, pressing enter after each one:
C:
CD C:\IBMDA\SAMPLES
2. >Run the C sample.< The C sample requires you to specify some
parameters when you run the program. If you run CCLIENT without
any, you'll see this brief explanation:
usage: CCLIENT [/R] filename connName
where: /R is request response on every DAWrite
At a minimum, you need to specify the filename and connName parameters.
The filename is any text file containing data you'd like sent to the
server. The connection name is the symbolic name of the connection
between the client and server programs. (See the "Hint:" in step 2a,
above, for more information on the connection name.) Type this command:
CCLIENT CSAMPLES.MAK CSAMPLE
and press enter.
2b. >Note how the server gets started.< DA/2 can automatically start
server programs for you, if they're not already running. The C
sample starts the server program, CSERVER.CMD, in an OS/2 window.
In this sample, the server remains running after the connection is
closed.
2c. >Look for the results.< The server will write the contents of the
data it receives to an output file, CSERVER.00n. 'n' will be '0' the
first time the sample is run (it's a C sample, after all!), and
will be incremented by 1 each subsequent time you run the sample.
In this case, CSERVER.000 will contain the contents of CSAMPLES.MAK,
the filename you specified when running CCLIENT.
If you are using the demonstration version of DA/2, the output file
written by the server program will only contain:
"Developer's Connection"
That's the only data that gets written between client and server.
3. >Learn more by examining the documentation and sample code.< You should
take some time to look at the source code for the samples, and the
online documentation. This will help you understand more about how
DA/2 works, and how you can use it to build your client/server
applications.
ADDITIONAL INFORMATION FOR THIRD-PARTY DISTRIBUTORS
___________________________________________________
We provide the source files for the online help that you can customize
if you want.
COMPILING THE ONLINE HELP (EPFPROF.HLP)
_______________________________________
The source help file for Distributed Application/2 is EPFPROF.IPF. You can
change the text in this file. After changing the text, you must recompile
this .IPF file to obtain the .HLP file. The compiler, IPFC.EXE, is part of
the IBM Developers Toolkit for OS/2 2.0.
NOTE: DO NOT change the resource ids (res=nnnn) that identify the help
panels. The resource ids associate the help panels with the product's source
code. DO NOT add or delete help panels or their resource ids.
1. Run IPFC.EXE on EPFPROF.IPF.
IPFC EPFPROF.IPF >ERRORS.TXT
2. Check the compile messages and statistics in ERRORS.TXT.
3. If you have errors in the ERRORS.TXT file, make corrections to
EPFPROF.IPF and repeat steps 1 and 2.
EPFPROF.HLP is the online help that can be viewed on the workstation while
using Distributed Application/2.
CONTENTS OF PRODUCT
_______________________________________
The following is a list of the files that are copied to your workstation
when you install Distributed Application/2. Next to each is a brief
description of the file. If you chose C:\IBMDA as your install
directory, your installation should look like this:
Directory of C:\IBMDA
bin (directory) ....... Contains DA/2 product
book (directory) ...... Contains DA/2 product documentation
CONFIG.BAK .......... Backup of your CONFIG.SYS file (if updated)
EPFDACAT.ICF .......... Catalog file used for Installation
EPFDAPKG.PKG .......... Package file used for Installation
EPFDADSC.DSC .......... Description file used for Installation
READ.ME .......... DA/2 READ.ME file
samples (directory).... Contains DA/2 samples
Directory of C:\IBMDA\BIN
EPFAPPC.DLL .......... DA/2 APPC module
EPFDAREX.DLL .......... DA/2 Rexx bindings module
EPFNETB.DLL .......... DA/2 NetBIOS module
EPFNETBL.EXE .......... DA/2 NetBIOS daemon
EPFNP.DLL .......... DA/2 Named Pipes module
EPFOCRW.DEF .......... DA/2 .DEF file to create .LIB file
EPFOCRW.DLL .......... DA/2 Main module
EPFOCRW.H .......... DA/2 Header file
EPFOCRW.LIB .......... DA/2 Library file for linking
EPFPROF.DLL .......... DA/2 Connection Profile Editor resource module
EPFPROF.EXE .......... DA/2 Connection Profile Editor
EPFPROF.HLP .......... DA/2 Connection Profile Editor Help file
EPFPROF.IPF .......... DA/2 Connection Profile Editor Help file source
EPFLEVEL.CMD .......... Extracts version level from module
DAREN.CMD .......... Command file to rename re-distributable modules
EPFRCOPY.EXE .......... Executable to rename re-distributable modules
EPFIDLDS.EXE .......... Installation utility file
EPFIEXTS.DLL .......... Installation utility file
EPFIHPLB.HLP .......... Installation utility file
EPFIICIS.ICO .......... Installation utility file
EPFIICO1.ICO .......... Installation utility file
EPFIMSG.MSG .......... Installation utility file
EPFINSTS.EXE .......... Installation utility file
EPFIPII.DLL .......... Installation utility file
EPFIPRCS.EXE .......... Installation utility file
EPFIUPCK.EXE .......... Installation utility file
Directory of C:\IBMDA\BOOK
EPFDACG.INF .......... DA/2 C Guide
EPFDARXG.INF .......... DA/2 REXX Guide
Directory of C:\IBMDA\SAMPLES
CCLIENT.C .......... DA/2 C client sample source
CCLIENT.EXE .......... DA/2 C client sample executable
CSAMPLES.MAK .......... DA/2 Make file for C sample
CSERVER.C .......... DA/2 C server sample source
CSERVER.EXE .......... DA/2 C server sample executable
IBMDABB.CP .......... DA/2 C and REXX sample connection profiles
RXCLIENT.CMD .......... DA/2 REXX client sample
RXSERVER.CMD .......... DA/2 REXX server sample
Directory of C:\IBMDA\CICS
DA2SERV.OBJ .......... Host CICS object file for the DA/2 CICS Server
LINK.JCL .......... Sample Host Link Edit JCL
INSTSAMP.COB .......... Sample CICS program used by the client samples
Directory of C:\IBMDA\CICS
DA2SERV.OBJ .......... Host CICS object file for the DA/2 CICS Server
DACLNT.H .......... Include file for clients
HANDLERR.C .......... Error handling sample source
HANDLERR.H .......... Error handling sample include
HANDLERR.MAK .......... Error handling sample make file
PCCLNT.C .......... PC Sample source
PCCLNT.EXE .......... PC Sample executable
PCCLNT.MAK .......... PC Sample make file
PICLNT.C .......... PI Sample source
PICLNT.EXE .......... PI Sample executable
PICLNT.MAK .......... PI Sample make file
PMCLNT.C .......... PM Sample source
PMCLNT.EXE .......... PM Sample executable
PMCLNT.MAK .......... PM Sample make file
QDCLNT.C .......... QD Sample source
QDCLNT.EXE .......... QD Sample executable
QDCLNT.MAK .......... QD Sample make file
QKCLNT.C .......... QK Sample source
QKCLNT.EXE .......... QK Sample executable
QKCLNT.MAK .......... QK Sample make file
QRCLNT.C .......... QR Sample source
QRCLNT.EXE .......... QR Sample executable
QRCLNT.MAK .......... QR Sample make file
QWCLNT.C .......... QW Sample source
QWCLNT.EXE .......... QW Sample executable
QWCLNT.MAK .......... QW Sample make file
RXPCCLNT.CMD .......... REXX Client sample
TESTCONF.CMD .......... REXX client sample for testing CONFIRM
TESTNOCF.CMD .......... REXX Client sample for testing NO CONFIRM
(*) IBM, Operating System/2, and OS/2 are trademarks of the IBM Corporation
in the United States and other countries.
(**) Novell is a trademark of Novell, Inc.
(**) NetWare is a trademark of Novell, Inc.