Configuration and Security › Configuration › JCL Procedure

JCL Procedure

Use the following sample JCL procedure to execute CA GTS.

We recommend running CA GTS as a started task (STC).

CA GTS uses cross-memory services. The address space will become unavailable upon shutdown unless XMEM(NO) is specified in the GSINIT00 initialization parameter. You should consult your GTS client, product documentation for the proper setting. If a client product requires GTS cross-memory services and XMEM(NO) is specified, the client will report that a GTS connection cannot be made.

A sample procedure for CA GTS can be found in your GTS SMP/E target library CD51PROC; the member name is CAGTS. 

The following is a description of the sample procedure:

//******************************************************************************
//***  Sample General Transaction Server (GTS) procedure             
//***                                                                
//***  Change the following parameters                               
//***                                                                
//***   ID=                GTS ID (optional)                         
//***   GTSLOAD= GTS Load library                                    
//***   GTSSUFF= GTS Suffix dataset                                  
//***   GTSOPTN= GTS Options library                                 
//***   TCPDATA= TCPIP Data library                                  
//***                                                                
//*** See the CA General Transaction Server User Guide for more info.
//******************************************************************************
//CAGTS PROC ID=,                                                    
//                 GTSLOAD=CAI.CAGTS.CD51LOAD,     GTS LOAD LIBRARY
//                 GTSSUFF=CAI.CAGTS.SUFFIX.DSN,   GTS SUFFIX DSN
//                 GTSOPTN=CAI.CAGTS.CD51OPTN,     GTS OPTION LIBRARY
//                 TCPDATA=TCPIP.TCPIP.DATA        TCPIP DATA LIBRARY
//STEP1 EXEC PGM=CAGSMNLD,PARM='ID(&ID)' 
//STEPLIB DD DISP=SHR,DSN=&GTSLOAD 
//CASUFFIX DD DISP=SHR,DSN=&GTSSUFF 
//CAGSPARM DD DISP=SHR,DSN=&GTSOPTN 
//SYSTCPD DD DISP=SHR,DSN=&TCPDATA 
//GTSSNAP DD SYSOUT=*,DCB=(RECFM=F,LRECL=180) 
//GTSPRINT DD SYSOUT=*,DCB=(RECFM=F,LRECL=180) 
//GTSDEBUG DD SYSOUT=*,DCB=(RECFM=F,LRECL=180) 

This procedure requires the identifier of the CA GTS to be supplied on the z/OS START command, for example:

START CAGTS,ID=SYS1

The STEPLIB DD statement points to an APF-authorized library containing the CA GTS code. This DD statement may be omitted if the code is located in an authorized LINKLIST data set.

CASUFFIX points to a data set containing the overridden member names for CAGSPARM. All CAGSPARM member names not explicitly overridden are presumed to have a suffix of '00'. For more information, see the CASUFFIX DD Statement.

The CAGSPARM DD statement points to a partitioned data set that contains the member names controlling operation of the CA GTS system. For more information, see the CAGSPARM DD Statement.

The SYSTCPD DD statement points to the data set containing system-wide TCP/IP definitions. This DD statement may be omitted from the JCL Procedure if there is only one TCP/IP system executing in the environment. If there are multiple TCP/IP environments, then code the SYSTCPD DD statement pointing to the definition library for the TCP/IP under which CA GTS should execute.

The GTSSNAP DD statement is only necessary when requesting a SNAP debugging session for one of the GTS clients. This should only be performed at the request of CA Support.

GTSPRINT and GTSDEBUG should point to standard SYSOUT. They hold informational and debug messages.