PM61614: CM BATCH JCL PROCEDURE PARMS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CM batch JCL procedure parms
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool for      *
  *                 z/OS who use the CM Batch function.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- User defined JCL symbols on the      *
  *                      PROC statement of the CM batch JCL      *
  *                      procedure are not generated in the      *
  *                      run job created by CM Batch.            *
  *                                                              *
  *                      2- Using CM Batch to import and         *
  *                      analzye a change where the specified    *
  *                      change owner and name identify an       *
  *                      existing change, results in an analyze  *
  *                      being attempted on the existing change. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- CM BATCH JCL procedure not generated by CM BATCH.
  
  Example:
  User defined JCL symbols on the PROC statement are P1 and P2.
  //GOCCM   PROC SSID=,PLAN=,P1=,P2=
  //GOCCM    EXEC PGM=IKJEFT01,DYNAMNBR=200,
  //      PARM=('CALL *(GOCCCM) ''/SSID(&SSID)PLAN(&PLAN)'' ')
  >snip<
  //GOCCM   PEND
  
  User invokes CM batch to analyze and build run job for a
  change:
  
  //GOCCM    EXEC GOCCM,SSID=DSNA,PLAN=plan_name,
  P1=ABC,P2=XYZ
  
  Without the fix for this APAR, the run job generated by
  CM batch does not contain the P1 and P2 parameters.
  //GOCCM    EXEC GOCCM,SSID=>subsystem<,
  PLAN=plan_name
  
  2- Using CM batch to import and analzye a change where the
  specified change owner and name identify an existing change,
  results in an analyze being attempted on the existing change.
  

Problem conclusion

• 1- CM batch has been enhanced to support propagating user
  JCL symbols in the PROC statement into jobs generated by
  CM batch.
  
  Example:
  User defined JCL symbols on the PROC statement are P1 and P2,
  and the values of P1 and P2 are specified in 'PARM' as
  illustrated in the example below:
  
  //GOCCM   PROC SSID=,PLAN=,P1=,P2=
  //GOCCM    EXEC PGM=IKJEFT01,DYNAMNBR=200,
  //      PARM=('CALL *(GOCCCM) ''/SSID(&SSID) PLAN(&PLAN) ',
  //  'P1=&P1 P2=&P2',
  //  '''')
  >snip<
  //GOCCM   PEND
  
  User invokes CM batch to analyze and build run job for a change:
  //GOCCM    EXEC GOCCM,SSID=DSNA,PLAN=plan_name,
  P1=ABC,P2=XYZ
  
  With the fix for this APAR, the run job generated by
  CM batch does contain the P1 and P2 parameters:
  
  //GOCCM    EXEC GOCCM,SSID=>subsystem<,
  PLAN=plan_name,P1=ABC,P2=XYZ
  
  2- CM batch has been enhanced to support a CM batch
  cataloged JCL procedure name other than the default
  GOCCM.
  
  Example:
  The user defines the CM batch JCL procedure in member T01
  of MY.PROCLIB which stores JCL procedures.  Since the
  member name is not the default of GOCCM, the MBR value
  in 'PARM' must be set to the name of the PDS member name.
  
  Content of member T01:
  //GOCCM   PROC SSID=,PLAN=,P1=,P2=
  //GOCCM    EXEC PGM=IKJEFT01,DYNAMNBR=200,
  //      PARM=('CALL *(GOCCCM) ''/SSID(&SSID) PLAN(&PLAN) ',
  //  'MBR=T01 P1=&P1 P2=&P2',
  //  '''')
  >snip<
  //GOCCM   PEND
  
  User invokes CM batch using the T01 cataloged JCL
  procedure to analyze and build run job for a change:
  //GOCCM    EXEC T01,SSID=DSNA,PLAN=plan_name,
  P1=ABC,P2=XYZ
  
  With the fix for this APAR, the run job generated by
  CM batch will use the T01 cataloged procedure:
  
  //GOCCM    EXEC T01,SSID=>subsystem<,PLAN=plan_name,
  P1=ABC,P2=XYZ
  
  3- When attempting to import a change and the specified
  change owner and name identifies an existing change,
  CM batch will now fail with RC=16.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK78302

Modules/Macros

•    GOCCM
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• RA10 PSY UK78302

     UP12/04/28 P F204

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.