The Shadow OS/390 Web Server
Setting up the sample Web Server Programs
All of the source code to the Sample programs can be found in the
SWS.SV040501.SAMP dataset. This dataset should have been copied
off of the tape during the install.
In order to run the sample DB2 program, the following steps need to
be performed ahead of time:
- Ensure that you have a Q.staff table, This table is provided
by QMF.
- Pre-Compile (using the DB2 pre-compiler), compile and link the
SWCODBP2 program in the SAMP dataset. Sample JCL to do this is
provided in the SWS.SV020100.CNTL dataset, member COB2DB2.
- Grant execute on the plan created to public.
The sample IMS DBCTL program has the following requirements:
- The IMS PARTs database, DI21PART, needs to be available to IMS.
This database is part of the IMS IVP installation.
- The DFSSAM02 PSB, also part of the IVP install, needs to be gen'd
and available.
The source code for this sample can be found in
member SWCOIM in the SWS.SV020100.SAMP dataset.
This sample uses the Transaction Server for IMS feature and has the
following requirements:
- The Transaction Server for IMS Installation steps need to have
been completed. These steps are described in the Shadow Web Server
Installation Manual.
- The IMS PARTs database, DI21PART, needs to be available.
- The PART transaction needs to be available.
- The following change(s) needs to be made to the SWCOIMAP source
code:
- Change the PARTNER_LU_NAME parameter to your systems
NETWORKNAME.IMSBASELUNAME in the following statement in the
Procedure Division of the program:
MOVE 'P390.IMSLU62' TO PARTNER-LU-NAME.
- Optionally change the following to specify a different part no:
MOVE '3007228' TO SEND-BUFFER-CONTENTS.
- Compile and link the program into the SWSRPCLB dataset.
This sample requires that both the IMS DBCTL Sample
and the Transaction Server for IMS requirements to be met, but instead of
making modifications to the SWCOIMAP program, the IMS Transaction
server program used in this case is SWCIMAP2.
This sample uses the Transaction Server for CICS feature and has the
following requirements:
- The Transaction Server for CICS installation steps need to have
been completed. These steps are described in the Shadow Web Server
Installation Manual.
- The sample vsam file that is supplied by IBM for CICS, FILEA,
needs to be available to CICS.
- The DFH$FILA and DFH$EXCI groups need to be installed in CICS.