Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 2 Installation on z/OS : Installation Procedure for MVS Components

Installation Procedure for MVS Components
Perform the steps below to install the MVS components for the Plug-in. All members reside within the USERHLQ.INSTALL data set.
Edit the selected members in the steps. Substitute the variables, follow the instructions in the member, and submit the JCL for execution.
Step 1 Make CLIST temporary file
Change the #JOBNAME, #USERHLQ, #USERVOL statement variables according to your site’s requirements.
Member: SXN$1MKT
Step 2 Execute the File Tailoring CLIST for the installation JCL
If you make an error during input, press the attention key (PA1) and execute again, starting at step 1.
Member: SXN$2EX1 (EX member)
VOLSER Volume Serial
SXNPI
The first six characters are used.
Step 3 Upload the installation files to z/OS MVS
Member: For DFSMSdss sites, use SXN$3FT.
For non-DFSMSdss sites, use SXN$3FT@.
Step 4 Define and allocate the Plug-in product libraries
Perform this step during initial installation only.
Member:  SXN$4ALL
Step 5 Convert the product installation files to the appropriate data sets.
You can restart the installation multiple times at this step, if required.
Member: For DFSMSdss sites, use SXN$5RC
For non DFSMSdss sites, use SXN$5RC@
Table 5 defines the user substitution variables within the JCL and the parameter members that are required during the file-tailoring process. Ensure that you have all the necessary information before executing the next step (step 6).
Step 6 Execute the File Tailoring CLIST to update the product-supplied variables.
If you make an error during input, press the attention key (PA1) and execute the CLIST again.
Member: SXN$6EX2 (EX member)
Step 7 Populate the Plug-in data sets with all the update and downloaded members.
Member: SXN$7UPD
You have now completed the activities in the USERHLQ.INSTALL dataset. All further steps reference the data set that is specified in the step.
Step 8 Update CICS with the CICS Resource Definitions.
This member updates the CICS System Definition (CSD) file with the Resource definitions necessary for the Plug-in to operate and Resource definitions for IBM's CICS TCP/IP Socket interface.
This includes all the CSD definitions for the IBM CICS Socket Listener. Group TCPGROUP will be created and updated and added to List TIBLIST
Data Set: USERHLQ.JCL
Member: SXNCSDUP
Step 9 Assemble and Link the Plug-in CICS PLT entries (optional)
The Plug-in uses the suffixes XD and XI for its program list table (PLT) entries. If your CICS Region already uses these suffixes, change the suffixes in the DFHPLTXD and DFHPLTXI members in the USERHLQ.ASM data set before executing the assembly.
To view the current suffixes in the CICS Region, execute either of these two commands:
CEMT I PROG CLASS(XD)
CEMT I PROG CLASS(XI)
Data Set: USERHLQ.JCL
Member: SXNASMLK
Step 10 Define and populate CICS TCP/IP Socket File
This member defines and populates the Plug-in configuration VSAM file for CICS TCP Sockets support.
The default is NO security. Two optional security modes can be enabled by modifying USERHLQ.JCL(SXNEZADF).
To add simple user ID and password based security, uncomment the line:
*** SECEXIT=SXNSECUR, Security exit for Listener program and editing the previous line by adding a comma after MINMSGL=4 and a "X" in column 72
To enable run-time security using IDENTIY CICS security checking, un comment the above line and set SECEXIT=SXNSECID.
Data Set: USERHLQ.JCL
Member: SXNEZADF
Step 11 Update the CICS region startup procedure
The USERHLQ.LOAD library installed as part of the Plug-in must be concatenated in the DFHRPL DDName of your CICS startup procedure(s).
The new group list members TIBLIST and TCPLIST must be included in the GRPLIST of CICS System Initialization Parameter.
If Step 9 is chosen, then add the following Startup and Shutdown PLT parameters to the CICS SIP member:
PLTPI=XI
PLTSD=XD
Step 12 Enabling the IBM CICS TCP/IP Socket Interface (optional)
If you do not use the Auto Startup in Step 9, then you can manually start IBM CICS Sockets as follows from a blank CICS 3270 screen:
ezao,start,cics
A formatted 3270 screen displays the message:
CICS Sockets Interface Startup Complete.
Step 13 At this point the Plug-in MVS components are ready to use.
Refer also to TIBCO ActiveMatrix BusinessWorks Plug-in for CICS, User Guide for Windows, to learn how to use the whole product.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved