home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
o22516d1.zip
/
DSDEMO.@IP
/
DSCCIECI.BAK
< prev
next >
Wrap
Text File
|
1992-07-29
|
5KB
|
120 lines
This application demonstates the usage of CICS/OS2's ECI facility along
with Micro Focus CCI software.
Files: DSCCIECI.DOC - This file
INSTALL.CMD - Install command file - probably needs modification
DSFRONT.CBL - DS/2 program
DSCLIENT.CBL - CCI Client program
COMMAREA.CBL - CopyBook used by programs
DSSERVER.CBL - CCI Server-ECI program
CLOSESRV.CBL - CCI Close Server-ECI program
CUSTIO.CCP - CICS OS/2 ECI-I/O program used by DSSERVER
and BMSFRONT
BMSFRONT.CCP - CICS OS/2 Cobol program
CUST.BMS - CICS OS/2 BMS map for BMSFRONT program
DSCCIECI.GS - DS/2 Screenset
DSCCIECI.CPB - DSCCIECI.GS Data Block
DS-CNTRL.MF - DS/2 Control Block
CCISIGNA.CPY - CCI Signature copybook
CCITABLE.CPY - CCI Procedure Pointer copybook
FAAECIW.CBL - ECI Control copybook
ANIMCUST.CMD - CMD file to animate the application
CUSSERVE.CMD - CMD executed from ANIMCUST.CMD to start DSSERVER
CUSTFILE.BTR - Indexed file used in the demo
This application is the regular CUSTOMER demo of the Dialog System.
The screenset has been modified with the addition of two fields to the
data block to be used in the call to the CCI programs. Additional
windows have also been added to give the user more information on the
success/failure of the transaction.
DSFRONT calls a CCI Client(DSCLIENT) which communicates to a CCI
Server(DSSERVER) which connects to a CICS OS/2 program(CUSTIO) via ECI.
BMSFRONT Links to the same I-O program(CUSTIO).
Named pipes were used for this example.
CICS OS/2 must be running and the server program(DSSERVER) must be
running in a session on the machine where CICS OS/2 is located.
To be able to Animate CUSTIO, change your SIT table to allow just 1
free task, and then change your MCO2.CFG file from D-V124 to D-@03@.
This will make sure the Animator will always be in control of the free
task.
The following CICS OS/2 defintions are required.
PCT CUST BMSFRONT
SNT SYSAD With a signon password of SYSAD.
FCT CUSTFILE KSDS file with dthe following settings;
Keylength=5, start pos=0, rec=284/284.
You can move CUSTFILE.BTR to the directory specified in the FCT or you can
create it by using the CECI command SET FILE(CUSTFILE) OPEN RESET
The CUSTFILE.BTR has 1 record with a key of 11111 in it.
The following CICS OS/2 defintion is optional.
SIT Change the number of free tasks to 1 so that
you are guaranteed that the CUSTIO will Animate
when called thru ECI in task @03@.
PPT CUSTIO Mark as Resident for better performance.
Remember that you have to bring down CICS OS/2 for these table entries
to be active.
It is assumed that you have all the appropriate COBDIR etc... set in your
CONFIG.SYS. If not, you will have to execute those SET statements prior to
bringing up the regular WB or execute ANIMCUST.CMD.
* Check DSFRONT, DSCLIENT, DSSERVER, and CLOSESRV from the regular WB menu.
* BMS translate CUST.BMS from the CICS OS/2 WB menu.
* CICS+Check BMSFRONT and CUSTIO from the CICS OS/2 WB menu.
!!Make sure you use the COBOL2 directive on the Command Line!!
* Bring up CICS OS/2
* Run the CUST transaction.
* In another session execute ANIMCUST.CMD.
This will bring up CCI server program DSSERVE.
If you have brought up CICS OS/2 to Animate the free task, you will have
to switch to that session when doing the ECI call and Animate the
CUSTIO program.
You can Step thru it until you get to the RECEIVEALL statement.
At this point the server is looking for requests from the client
* Another session Animating DSFRONT will be present, you can step thru this
and see how it sets itself up as a client.
You will see after executing a LOAD off the DS/2 screen with the key of
11111 that the client program DSCLIENT will do a send and then hang on the
RECEIVE statement. At that time you can go back to the server session
and see that you have fallen off the RECEIVEALL statement.
* To shut down the Server (DSSERVER) program, run CLOSESRV in another
OS/2 session.
*************************************************************************
Possible uses of this type of setup could be where you have any type of
program that would like to use facilities of CICS OS/2. It gives you
the ability to communicate to/thru one CICS OS/2 on a Lan to
another CICS (MVS etc..). The workstations could be running OS/2, DOS or
Windows.
The CUSTFILE could be located on another CICS(MVS etc..) and
be marked as a remote file in the CICS OS/2 FCT table. CICS OS/2 would
then FUNCTION SHIP to the remote CICS
OR
program CUSTIO could also be marked as a remote program in the
CICS OS/2 PPT table and actually be located along with the CUSTFILE
on the remote CICS. This would be a DISTRIBUTED PROGRAM LINK.