The steps described in the following pages of this document will result in the installation of the OD/390 Internet Access feature. After the feature is installed, further customizing may be required to meet your installation's specific OD/390 requirements. OD/390 customizing is addressed in the next section of this document.
Most of the automated jobs needed to accomplish the installation are provided by IBM. Examples are provided for those installation steps that do not have distributed jobs.
The OD/390 Internet Access feature installation process involves: preliminary preparation, receiving the IBM distributed materials, modifying/executing IBM supplied jobs and installation verification. The installation jobs execute IBM programs and utilities that are provided in the OD/390 prerequisite products.
During the installation process you may wish to consult other IBM manuals
for additional information.
Appendix A, Additional Reference Material contains a list of
manuals that you may find useful during the installation
process.
STEP AA -- Install OD/390 Internet Access Feature Prerequisite Software
Description: The preliminary step to the OD/390 Internet Access feature installation process is to ensure that all prerequisite software is installed and operational. In addition, the OD/390 base system and the CICS Web Interface must be installed and operational.
The planning and installation steps required to install the OD/390 Internet Access feature prerequisite software can be found in the documentation distributed with the Program Directory for IBM EDMSuite OnDemand for OS/390 V2R1, OnDemand for OS/390 V2R1 Installation and Customization Guide and OnDemand for OS/390 V2R1 Program Description and Operations Manual. A complete list of OD/390 Internet Access feature prerequisite software can be found in the Installation Overview section of this document. All products listed must be installed and operational prior to beginning the OD/390 Internet Access feature specific installation steps.
Process: None.
Completion: This step will be complete when all prerequisite
software is installed, operational and the necessary subsystems
can support the OD/390 Internet Access feature.
STEP 01 -- Load OD/390 Internet Access Feature Datasets
Description: The first step of the installation process is to load the OD/390 Internet Access feature installation datasets from the distribution tape to disk. The datasets being allocated will contain the JCL, load modules, HTML source, samples, and precompiler Database Resource Management System (DBRMS) libraries distributed by IBM.
Process: This step uses an IBM supplied load job, provided on the distribution tape, to load the OnDemand files to disk. The job is the first file on the distribution tape and can be copied to disk using the following IEBGENER job step:
//LOAD0 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=IOD.V2R1ME.IODLOADW.UNLD,DISP=(OLD),UNIT=3490,
// VOL=(,RETAIN,SER=ODW21E),LABEL=(1,SL)
//SYSUT2 DD DSN=IOD.V2R1ME.IODLOADW,DISP=OLD
//SYSIN DD DUMMY
/*
The sample IOD.V2R1ME.IODLOADW file is listed in Appendix B, Sample JCL for OD/390 Internet Access Feature Load. The supplied job has three steps. The first step deletes any previously allocated OD/390 Internet Access feature V2R1 distribution files. The second step allocates new distribution files on disk. The third step loads the installation files on the distribution tape to the files allocated in the second step.
Modify the file as appropriate to your installation and execute the job.
Completion: This step will be complete when the distribution
files have been loaded to disk.
STEP 02 -- Define DB2 Presentation Control Table
Description: This step creates the DB2 Presentation Control Table required for the OD/390 Internet Access feature.
The OD/390 Internet Access feature PCT table space, table and index are created. A DB2 COMMIT occurs after all objects of a particular object type are created. The COMMIT will ensure that successfully created objects do not have to be recreated if later object types fail.
The DB2 DDL and other DB2 control information is contained in the OD/390 library WEBDB2. You will need to modify the IODCPCT member in the library to select your database name and DB2 STOGROUP name. A PDS editor may be useful in performing this step.
Process: The STEP 02 JCL invokes the DB2 DSNTIAD program to create the DB2 objects.
Make the following modifications to IODCRPCT, as appropriate:
Completion: This step will be complete when the DB2 object
has been successfully created.
STEP 03 -- Link Modules
Description: This step will link the OD/390 Internet Access feature modules with your installation's pre-requisite software products. Prior to re-linking, the LE/370 run-time options must be reviewed to assure compatibility with OD/390.
Process: Member IODUCWI contains the LE/370 run-time options required by the OD/390 Internet Access Feature. Please review these options and compare them with your CICS LE/370 run-time options. If your current CICS LE/370 configuration is not compatible with OD/390, you must merge your CICS LE/370 options into member IODUCWI and re-assmble the module. You can re-assemble IODUCWI using member IODAUOPT in the Internet Access Feature JCL library.
Due to CICS pre-requisite software considerations, object modules are distributed with the V2R1ME Internet Access Feature. Four OD/390 Internet Access Feature modules require special consideration under CICS/TS V1R3. These modules are: IODWWBCV, IODWWBSC, IODWWBSN and IODWWB00. Separate CICS/TS V1R3 object and load libraries are distributed with V2R1ME for these four modules. A separate link job is also required.
The re-link JCL can be found in members IODLINK4 and IODLKTS4 of the OD/390 Internet Access Feature JCL library. The IODLINK4 job refers to the IOD.V2R1ME.WEBOBJ and IOD.V2R1ME.WEBLOD libraries. The IODLKTS4 job referes to the IOD.V2R1ME.WEBOBJ.CICSTS13 and IOD.V2R1ME.WEBLOD.CICSTS13 libraries. Please review the members, making the necessary changes to the dataset names and execution parameters, as described in the job prologues. It is only necessary to run job IODLKTS4 if you plan to execute the OD/390 Internet Access Feature in a CICS/TS V1R3 environment. As distributed, the link jobs will include the IODUCWI object module in each program load module.
After linking the modules, please be sure to place the IOD.V2R1ME.WEBLOD.CICSTS13 library ahead of the IOD.V2R1ME.WEBLOD library in the CICS RPL concatenation.
Completion: This step will be complete when the modules are linked
successfully.
STEP 04 -- Bind DB2 Packages and Plans
Description: The DBRMLIB members shipped with the OD/390 Internet Access feature must now be converted to application packages and plans. These members must be bound by DB2 with other DBRMLIB members that were placed in the DBRM library during OD/390 base system customizing.
Process: The STEP 04 JCL invokes a DB2 DSNTIAD program to process the SQL bind statements. OD/390 Internet Access feature JCL library members IODBPKG4, IODBPLN4 and IODGRNT4 are used in this step. Refer to Appendix D, OD/390 Internet Access Feature Quick Reference for a list of the JCL library bind member names.
Modify IODBPKG4 as follows:
Modify IODBPLN4 as follows:
Modify IODGRNT4 as follows:
Execute the jobs in the order listed above.
Completion: This step will be complete when all
of the DB2 plans and packages have successfully completed the bind
process and the grants have been done.
STEP 05 -- Define DB2 Resources to CICS
Description: STEP 05 adds the Resource Control Table (RCT) entries for the OD/390 Internet Access feature to an existing RCT in a CICS V4R1 or CICS/TS V1R1 environment. This step can be skipped if you are installing the OD/390 Internet Access Feature in a CICS/TS V1R2 or CICS/TS V1R3 environment.
A reassembly and relink of your existing RCT is required in order to include the OD/390 transaction identifiers and their associated DB2 plan names.
Process: The STEP 05 process includes executing existing JCL that assembles and link edits your RCT.
Review the OD/390 Internet Access feature RCT entries that can be found in member IODRCT4 of your OD/390 Internet Access feature Sample library. OD/390 Internet Access Feature DB2 Resources - CICS/ESA V4R1 and CICS/TS V1R1 contains a listing of this member. Changes to the plan names will affect the bind process as described in Step 04 -- Bind DB2 Packages and Plans. The transaction names cannot be modified.
Modify your location's CICS JCL to include the OD/390 Internet Access feature RCT entries.
Completion: This step will be complete when the
RCT has been successfully updated.
STEP 06 -- Define CICS Resources
Description: STEP 06 defines the CICS resources required by the OD/390 Internet Access feature. This step defines the table entries for the OD/390 Internet Access Feature programs and transactions for all supported CICS environments. In addition, RDO is supplied to define the RCT entries for CICS/TS V1R2 and CICS/TS V1R3 environments as well as the RDO required to define the CICS Web Interface in a CICS/TS V1R3 environment.
Process: Review the CICS resource entries in members IODRDO4, IODWRCT4 and IODWTCP4 in your OD/390 Internet Access feature Sample library.
Member IODRDO4 contains the CICS program and transaction defintions. Section OD/390 Internet Access Feature CICS Program and Transaction Definitions contains a listing of this member. Review the comments at the top of the member and modify the RDO, as required. If you do not have the OD/390 Server Feature installed, it will be necessary to uncomment the following PPT entries before the CICS resource are updated:
*DEFINE PROGRAM(IODXFLDQ) GROUP(IODWEB) * DESCRIPTION(OD/390 WEB SERVER FOLDER QUERY) * LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) * USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) * EXECKEY(USER) EXECUTIONSET(FULLAPI) **TS13 DYNAMIC(NO) CONCURRENCY(QUASIRENT) JVM(NO) *DEFINE PROGRAM(IODXDOCG) GROUP(IODWEB) * DESCRIPTION(OD/390 WEB SERVER GET DOCUMENT) * LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) * USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) * EXECKEY(USER) EXECUTIONSET(FULLAPI) **TS13 DYNAMIC(NO) CONCURRENCY(QUASIRENT) JVM(NO)
Note that it will be necessary to modify the program definition for IODXDOCG to specify EXECKEY(CICS) if your OnDemand installation uses MVS Compression Services.
Member IODWRCT4 contains the CICS RCT defintions for the OD/390 Internet Access Feature in either a CICS/TS V1R2 or CICS/TS V1R3 environment. Section OD/390 Internet Access Feature CICS DB2 Resource Definitions - CICS/TS V1R2 and CICS/TS V1R3 contains a listing of this member. Modify the plan names, as required. Changes to the plan names will affect the bind process as described in Step 04 -- Bind DB2 Packages and Plans. The supplied transaction names cannot be modified. Review the comments at the top of the member and modify the RDO, as required.
Member IODWTCPT4 contains a sample CICS TCPIPSERVICE defintion that must be defined in a CICS/TS V1R3 environment in order to initialize the CICS Web Interface. Section OD/390 Internet Access Feature CICS Web Interface Definition contains a listing of this member. Review the comments at the top of the member. Modify the port number value, as required.
It is necessary to add the following DD statement to the CICS startup job in order to enable the use of the OD/390 HTML panels within your CICS environment:
//DFHHTML DD DISP=SHR,DSN=IOD.V2R1ME.WEBHTML,FREE=CLOSEPlease see OD/390 Internet Access Feature Customization Tasks for details on customizing the OD/390 HTML panels.
Completion: This step will be complete when the OD/390 CICS
resources have been defined to CICS.
STEP 07-- Load Presentation Control Table
Description: STEP 07 loads the OD/390 Internet Access feature Presentation Control Table used by the Online programs.
Process: STEP 07 invokes a job to load the Presentation Control Table.
Modify member IODIPCT of library WEBJCL:
Execute the job after the changes are complete.
Completion: This step will be complete when the
Presentation Control Table has been successfully loaded.
STEP 08 -- Load System Default Table
Description: STEP 08 loads the system defaults used by the OD/390 Internet Access feature.
Process: STEP 08 invokes a job to load the System Default Table.
Modify member IODISDT of library WEBJCL:
Execute the job after the changes are complete.
Completion: This step will be complete when the
System Defaults have been successfully loaded.
STEP 09** -- Change the CWI Analyzer Program name
Description: STEP 09 changes the CWI analyzer name used by the OD/390 Internet Access Feature in the CICS/ESA V4R1, CICS/TS V1R1 and CICS/TS V1R2 environments. This step does not apply to the CICS/TS V1R3 environment.
Process: STEP 09 invokes a CWI transaction to change the analyzer.
Modify the analyzer name:
Completion: This step will be complete when the
CICS Web Interface has been successfully restarted.
STEP 10** -- Perform OD/390 Internet Access Feature Functional Test
Description: This step will verify the operability of the OD/390 Internet Access feature. Note that this is an optional step. You may choose to skip this step at your location.
Process: Perform all steps outlined in Appendix E, OD/390 Internet Access Feature Functional Test Plan.
Completion: This step will be complete when all Functional
Test Plan steps as
outlined in
Appendix E, OD/390 Internet Access Feature Functional Test Plan
have completed successfully.
STEP 11** -- Automate Internet Access Feature Startup
Description: STEP 11 automates the startup of the Internet Access Feature in the CICS/ESA V4R1, CICS/TS V1R1 and CICS/TS V1R2 environments. This step does not apply to the CICS/TS V1R3 environment.
Automating this process is optional. This step includes the reassembly and relinking of your existing CICS PLT table entries.
Process: Review the sample PLT entries provided in OD/390 Internet Access Feature CICS PLT Entries. The PLT entries can also be found in member IODPLT in the Internet Access Feature Sample library, WEBSAMP. Make the necessary changes to your PLT startup member for OD/390. Reassemble and relink the PLT table to include the OD/390 entries.
Member IODICWBC of WEBSAMP contains a listing of the COBOL program which is used to start the CICS WEB Interface (CWBC) transaction. Please review this sample and make any changes necessary to run the program in your environment. Member IODCSMP of WEBJCL can be used to compile and link the module.
Completion: This step will be complete when the Internet Access Feature startup is automated.