Symbolic %*XMSG1 is not resolved when generating JCL using model MJRCMANL.
search cancel

Symbolic %*XMSG1 is not resolved when generating JCL using model MJRCMANL.

book

Article ID: 40560

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS

Issue/Introduction

Problem:

When batch JCL is generated to either run a CA RC/Migrator for DB2 for z/OS (RCM) analysis or execution, the MJRCMANL model generates the following DD statement with the data set name missing: //PTIXMSG  DD DISP=SHR,DSN=

Model member MJRCMANL in hlq.CDBAMDL has the following specified: //PTIXMSG DD DISP=SHR,DSN=%*XMSG1

How is the %*XMSG1 symbolic resolved? 

 

Cause:

Incorrect specification of hlq.CDBAXMSG within DSNAMExx member of hlq.CDBAPARM.

 

Resolution:

The DSNAMExx member in hlq.CDBAPARM data set name label specified PTIXMSG instead of XMSG for hlq.CDBAXMSG.  The following is the correct specification:

XMSG (hlq.CDBAXMSG)

Environment

Release:
Component: RCM
Powered by Wolken Software