Batch Link Facility › JCL Requirements

JCL Requirements

Before debugging a batch application using the batch link facility, modify the application JCL to enable the batch link environment. Do this manually as described here, or automatically using the batch link JCL conversion facility.

Change the application JCL for each step to be debugged. These changes include the following steps:

1. Modify the PGM= field on the // EXEC statement to execute CAMRBL01.
2. Insert the application executable library at the end of the STEPLIB or JOBLIB concatenation if it does not exist in LINKLIST.

   Note: It is possible to use the dynamic symbolic support feature if you:

   • Have multiple CA Endevor SCM C1DEFLTS

     and

   • Are debugging as if you have a single C1DEFLTS.

     To do so, insert a fully qualified data set name containing the C1DEFLTS with your site under the STEPLIB concatenation ID.

3. Insert additional DD statements for the application data sets used by the debugging engine, including INT1PARM, INT1PROF, INT1PNLL, and INT1MSGL.

   Note: For more information about these additional DD statements, see The Batch Link DD Statements.

4. Insert an INT1OPTS DD containing in-stream debugging options, such as the original program name from the PGM= field on the // EXEC statement.

   Note: For more information about valid options, see Batch Link Options.

Note: Different requirements apply for DB2 applications.

The following code is a sample JCL stream for batch link:

// JOB
// EXEC PGM=CAMRBL01,PARM='application parms'
//STEPLIB  DD DISP=SHR,DSN=CAI.CAILIB
//         DD DISP=SHR,DSN=USER.LOADLIB
//         DD DISP=SHR,DSN=USER.C1DEFLTS
//INT1PARM DD DISP=SHR,DSN=CAI.CAISRC
//INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB
//INT1PNLL DD DISP=SHR,DSN=CAI.CAIPNL1
//INT1MSGL DD UNIT=SYSDA,SPACE=(TRK,(1,1))
//INT1OPTS DD *
  EXEC=CAMRCOBB,PROFILE=USER01
/*