Wrong JCL generated during PTT Post Install Customization

Article Id: 110886
Status: Published
Updated On: 17-08-2018 14:45
Products:
CA RC/Migrator , CA Endevor SCM Interface , DB2 Administration , CA RC Compare for DB2 for z/OS , CA RC Extract for DB2 for z/OS , CA RC/Query , CA RC Secure for DB2 for z/OS , CA RC Update for DB2 for z/OS , CA Database Analyzer for DB2 for z/OS , CA Fast Unload for DB2 for z/OS , CA Fast Check for DB2 for z/OS , CA Fast Index for DB2 for z/OS , CA Fast Load for DB2 for z/OS , CA Rapid Reorg for DB2 for z/OS
Issue/Introduction:

Doing an Upgrade to R19. The PXMPARM Customization to build and initialize the Thread Terminator PXMPARM generated the wrong JCL.

 

Environment:

Release:
Component: PTT

Resolution:

The PTT control file Dataset Name and the Xmanager PXMPARM Dataset in Thread Terminator Create Control File Display are two different and separate datasets. Problem was caused by confusing these two. Distinguishing the two resolve the problem.