Sample JCL to start IMS Connect

You can use this sample JCL to start IMS Connect as a z/OS® procedure or job.

You invoke IMS Connect by using either a z/OS procedure or a z/OS job. If you start multiple instances of IMS Connect with the same configuration, a connection outage can occur.

To avoid starting the same IMS Connect address space more than once, start IMS Connect by running a z/OS job with a unique z/OS initiator class assigned to it, rather than starting the connection as a procedure. The following sample starts IMS Connect as a z/OS job:

//HWS01    JOB   MSGLEVEL=1,TIME=1440,CLASS=Y,USERID=&USERID
//*********************************************************************
//*  BRING UP IMS CONNECT USING A JOB                                 *
//*********************************************************************
//HWS01    EXEC HWS,SOUT=A

Two examples of starting IMS Connect as a z/OS procedure are shown below. In the first example, the JCL statements illustrate that both IMS Connect and BPE have configuration members (HWSCFG00 and BPECFGHT). In addition, PGM=HWSHWS00 is required to run IMS Connect in authorized supervisor state and key 7.

//HWS       PROC  RGN=0M,SOUT=A, 
//             BPECFG=BPECFGHT,
//             HWSCFG=HWSCFG00
//*
//*********************************************************************
//*  BRING UP AN IMS CONNECT USING HWSHWS00                           *
//*********************************************************************
//STEP1    EXEC PGM=HWSHWS00,REGION=&RGN,TIME=1440,
//             PARM='BPECFG=&BPECFG,HWSCFG=&HWSCFG'
//STEPLIB  DD   DSN=SDFSRESL,DISP=SHR
//         DD   DSN=CEE.SCEERUN,UNIT=SYSDA,DISP=SHR
//         DD   DSN=SYS1.CSSLIB,UNIT=SYSDA,DISP=SHR
//         DD   DSN=GSK.SGSKLOAD,UNIT=SYSDA,DISP=SHR
//PROCLIB  DD   DSN=USER.PROCLIB,DISP=SHR
//SYSPRINT DD   SYSOUT=&SOUT
//SYSUDUMP DD   SYSOUT=&SOUT
//HWSRCORD DD   DSN=HWSRCDR,DISP=SHR

In the second example, the BPE program properties table entry, BPEINI00 is used instead of HWSHWS00. When you use BPEINI00, the address space runs in authorized supervisor state and key 7. IMS Connect uses BPEINI00 unless you explicitly identify PGM=HWSHWS00, as in the example above. If you use BPEINI00, you must also add the BPEINIT=HWSINI00 parameter, which identifies the HWS BPE initialization parameters module. A sample startup procedure using BPEINI00 is shown below.

//HWS       PROC  RGN=0M,SOUT=A,
//            BPECFG=BPECFGHT,
//            HWSCFG=HWSCFG00
// *
// *************************************************************
// *  BRING UP AN IMS CONNECT USING BPEINI00
// *************************************************************
//STEP1    EXEC PGM=BPEINI00,REGION=0M,TIME=1440,
//             PARM='BPECFG=&BPECFG,BPEINIT=HWSINI00,
//             HWSCFG=&HWSCFG'
//STEPLIB  DD   DSN=SDFSRESL,DISP=SHR
//         DD   DSN=CEE.SCEERUN,UNIT=SYSDA,DISP=SHR
//         DD   DSN=SYS1.CSSLIB,UNIT=SYSDA,DISP=SHR
//         DD   DSN=GSK.SGSKLOAD,UNIT=SYSDA,DISP=SHR
//PROCLIB  DD   DSN=USER.PROCLIB,DISP=SHR
//SYSPRINT DD   SYSOUT=&SOUT
//SYSUDUMP DD   SYSOUT=&SOUT
//HWSRCORD DD   DSN=HWSRCDR,DISP=SHR

Note: The IMS.SDFSRESL library is required in the STEPLIB, because all IMS Connect modules reside in the IMS.SDFSRESL library. IMS Connect requires the CEE.SCEERUN, SYS1.CSSLIB, and GSK.SGSKLOAD libraries (which are the C execution and z/OS system SSL libraries) only when SSL support is used.

IMS Connect requires a minimum region specification of 250M. To ensure that IMS Connect can acquire adequate space above the line, specify REGION=0M.