Using the standard procedure JCL

IMS HP Change Accumulation Utility sample library members (HPCSPROC and HPCSJOB) are provided as the starting point for installation of standard procedures.

These library members are documented to describe the necessary changes for use.

When the sample JCL has been modified to meet your site standards, it can be added to a system PROCLIB or IEFJOBS data set for testing and use.

Figure 1. Sample JCL procedure
Samplib(HPCSPROC)
        //HPCSPROC PROC
        //******************************************************
        //* Sample HPCA PROC. Edit to suit local JCL standards
        //* and then make available to HPCA by copying to any
        //* PROCLIB in the IEFPDSI or JES PROC00 concatenation.
        //* 
        //* This PROC is intended for use with the standard
        //* PROC invocation method of HPCA. The PARM=value
        //* and DDNAMES will be merged from the DBRC GENJCL.CA
        //* output produced by HPCA setup.
        //* ****************************************************
        //* 
        //* ****************************************************
        //* PGM=HPCADRI1 is required. PARM=  (Optional)
        //*     PARM=not-null-value overrides any PARM value
        //*                         from the DBRC skeleton JCL
        //* STEPLIB  (Optional if required modules in LINKLIB/LPALIB)
        //* All other DD's should be omitted except in the most 
        //* unusual conditions. HPCA will merge DD's from the 
        //* GENJCL.CA generated JCL into this procedure. Similar
        //* to the parameters field, if a DD is hard coded into 
        //* this procedure, it will not be overridden.
        //*******************************************************
        //HPCASTEP EXE PGM=HPCADRI1,REGION=0M
        //STEPLIB DD  DSN=&HPCSTEPL,DISP=SHR
        //*

         samplib(HPCSJOB)
         //HPCSJOB JOB,
         //    CLASS=?,MSGCLASS=?,MSGLEVEL=(1,1),
         //    REGION=0M,TIME=?
         //***********************************************************
         //* Sample HPCA JOB. Edit to suit local JCL standards
         //* and then make available to HPCA by copying to any
         //* dataset in the IEFJOBS concatenation.
         //*
         //* Customizing may be done in several ways.
         //* 1. recommended, as a complete JOB as in this sample
         //* 2. Referencing an external PROC such as HPCSPROC in the
         //*           system PROCLIBS
         //* 3. Referencing an external PROC in any available 
         //*           PROCLIB using a JCLLIB statement
         //*
         //* This JOB is intended for use with the standard
         //* PROC invocation method of HPCA. The PARM=value
         //* and DDNAMES will be merged from the DBRC GENJCL.CA
         //* output produced by HPCA Setup.
         //***********************************************************
         //*
         //***********************************************************
         //* PGM=HPCADRI1 is required. PARM=  (Optional)
         //*   PARM=not-null-value overrides any PARM value
         //*              from the DBRc skeleton JCL
         //* STEPLIB  (Optional if required modules in LINKLIB/LPALIB)
         //* All other DD's should be omitted except in the most
         //* unusual conditions. HPCA will merge DD's from the 
         //* GENJCL.CA generated JCL into this procedure. Similar
         //* to the parameters field, if a DD is hard coded into 
         //* this procedure, it will not be overridden.
         //******************************************************************
         //HPCASTEP EXEC PGM=HPCADRI1,REGION=OM
         //STEPLIB  DD   DSN=&HPCSTEPL,DISP=SHR
         //*

One or more standard procedure or job members must be placed in a PROCLIB or JOBLIB. The rules for z/OS® started tasks apply to each member.

The procedure or job has a minimum of three JCL statements (two without STEPLIB).
  1. The PROC header or JOB statement
  2. EXEC PGM=HPCADRI1 is required. The PARM= parameter is optional and generally can be omitted.
  3. STEPLIB DD to HPCA. Optional only if all required modules are located through LINKLIST/LPALIB

Optional DD statements for HPCPRINT, HPCTRACE, and HPCSYSIN must be in the standard procedure JCL to be processed. These statements are not merged from the skeletal JCL.

There are generally no other DDs in the procedure. However, because of restrictions on the processing of the skeletal JCL, it might be necessary to include additional DDs in the procedure.

The procedure might include other steps before and after the HPCADRI1 step. If these other steps are present, no information from the skeletal JCL is merged into them.

If your skeletal JCL member has one or more job steps following the CA step, include the HPCADLIM DD statement at the end of the skeleton JCL member, as shown in the following figure:
Figure 2. Skeletal JCL member with one or more job steps
/*                                                                 
//COPY3 EXEC PGM=IEBGENER,COND=(0,LT,CA%STPNO)                     
//SYSPRINT DD SYSOUT=*                                             
//*                                                                
//SYSUT1   DD DISP=OLD,DSN=&hilev.%CAGRP.GDGOUTD1
//SYSUT2   DD DSN=&hilev.%CAGRP.GDGOUTD2(+1),
//            DISP=(NEW,CATLG),           
//            UNIT=(,,DEFER),                                       
//            VOL=(,,,99),                                          
//            LABEL=EXPDT=99000,                                    
//            DCB=(&hilev.GDG.MODEL,BUFNO=16),
//            SPACE=(CYL,(40,0)),
//            STORCLAS=GSYES2   
//SYSIN    DD DUMMY   
//HPCADLIM DD DUMMY
In this example, IEBGENER is used to create a copy the CA output.
Attention: To prevent skeleton JCL parser errors, //HPCADLIM DD DUMMY cannot be followed by a slash-asterisk (/*).