Why do I need to go to the z/OS Compatibility Matrix to get a CA Dispatch PTF every time there is a new IBM z/OS release?

Products

• Dispatch Output Mgmt

Issue/Introduction

Why do I need to go to the z/OS Compatibility Matrix to get a CA Dispatch PTF every time there is a new IBM z/OS release?

Environment

Release: DISPAX00200-11.7-Dispatch
Component:

Resolution

CA Dispatch requires a z/OS JES compatibility PTF for each new IBM z/OS JES release. The compatibility PTF updates an internal CA Dispatch control block table with the correct JES field displacements for the latest JES release.  

 

JES control block field displacements usually change between z/OS JES releases. The CA Dispatch SE team must verify and update the referenced JES field displacements for all supported releases of z/OS JES. Incorrect JES field displacements can result in unpredictable processing results such as CA Dispatch task Abends and or errors in the JES address space.

 

CA Dispatch references various JES internal control blocks to obtain specific information on both input reports and output bundle SYSOUT. Examples are return codes for jobs/steps that produce SYSOUT report input to CA Dispatch and current class and or priority fields of output SYSOUT Bundles. CA Dispatch can also use this information to issue commands to JES to change the class and or priority of output SYSOUT Bundles on the JES output queue.

 

 

The CADDSPL report SYSOUT and MSGCLASS data collector task will not initialize and remain active unless you have the corresponding z/OS JES compatibility PTF applied for the z/OS JES version you are running.

Additional Information

Here is a link to the z/OS Compatibility Matrix