JCLCheck PTF SO11500 has Hold data but the hold reasons are not found in the SMP/E APPLY job output
Article ID: 192597
Updated On:
Products
JCLCheck Workload Automation
Issue/Introduction
SMP/E APPLY CHECK of PTF SO11500 gets the following error messages:
GIM54502E ** ALLOCATION FAILED FOR CAZ2DATV BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN TARGET
ZONE CAIT.
GIM28307E ** ALLOCATION FAILED FOR CAZ2DATV, WHICH IS REQUIRED IN ORDER TO PROCESS ELEMENT AJ6ZRYML IN SYSMOD SO11500.
GIM22601I APPLY PROCESSING FAILED FOR SYSMOD SO11500.
The APPLY job output does not show any Hold data for this PTF. What actions are needed to apply this PTF successfully?
Environment
Release : 12.0
Component : JCLCheck workload Automation
Cause
PTF SO11500 has two HOLD Reason IDs: ACTION and DDDEF.
The HOLD data is displayed in the following places:
1. SMP/E RECEIVE output report.
2. SMP/E APPLY output report. In this case, the APPLY command is coded as follows:
APPLY PTFS APARS
GROUP
BYPASS(HOLDSYS ID) CHECK .
When BYPASS(HOLDSYS) is used, all system reason IDs are bypassed, and the Hold data will not be displayed.
Resolution
1. Execute the SMP/E job using the following APPLY command:
APPLY S(SO11500) CHECK.
2. Review the SMP/E APPLY job output, and look for section "UNRESOLVED HOLD REASON REPORT FOR APPLY CHECK PROCESSING". The HOLD DATA for PTF SO11500 is displayed as follows:
++HOLD (SO11500) SYSTEM FMID(CAZ1C00)
REASON (ACTION ) DATE (20112)
COMMENT (
+----------------------------------------------------------------------+
| CA JCLCheck Release 12.0 |
+----------+-----------------------------------------------------------+
|SEQUENCE | After Apply |
+----------+-----------------------------------------------------------+
|PURPOSE | Notice that additional steps are required to implement |
| | the REST API for JCLCHeck |
+----------+-----------------------------------------------------------+
|USERS | System programmers responsible for installation. |
|AFFECTED | |
+----------+-----------------------------------------------------------+
|KNOWLEDGE | USS file systems and security. |
|REQUIRED | |
+----------+-----------------------------------------------------------+
|ACCESS | USS access requirements are described in the |
|REQUIRED | product documentation |
+----------+-----------------------------------------------------------+
**************************
* STEPS TO PERFORM *
**************************
This change adds a new REST api to JCLCheck to allow JCL to be
validated from non-z/OS platforms. Once the PTF is applied,
additional steps are required to impliment the new api. This
involves copying elements to USS librairies to make them
available for excution and customizing required options.
Implimentation is only required if you are planning to use this
feature.
For more information on JCLCheck, visit
https://techdocs.broadcom.com/ and search for CA JCLCheck Workload
Automation.
In the JCLCheck documentation, search for
'Install, Configure, and Deploy the JCLCheck REST API' for
implementation and usage details.
).
++HOLD (SO11500) SYSTEM FMID(CAZ1C00)
REASON (DDDEF ) DATE (20112)
COMMENT (
+----------------------------------------------------------------------+
| CA JCLCheck Release 12.0 |
+----------+-----------------------------------------------------------+
|SEQUENCE | Before Apply |
+----------+-----------------------------------------------------------+
|PURPOSE | Add new target and dlib libraies to JCLCheck to |
| | support the new JCLCheck REST API. |
+----------+-----------------------------------------------------------+
|USERS | Sysprog responsible for JCLCheck maintenance |
|AFFECTED | |
+----------+-----------------------------------------------------------+
|KNOWLEDGE | SMPE |
|REQUIRED | |
+----------+-----------------------------------------------------------+
|ACCESS | Access to create JCLCheck SMPE target and DLIBs. |
|REQUIRED | |
+----------+-----------------------------------------------------------+
**************************
* STEPS TO PERFORM *
**************************
New components for JCLCheck require allocating new Target and DLIB
libraries and modifying the SMPE CSI to make the new libraries
available. Below are the steps needed.
1. Allocate the new libraries using the following JCL. Specify dataset
prefixes and other values needed in your environment.
//jobname JOB ...
//ALLOC EXEC PGM=IEFBR14
//CAZ2DATV DD DSN=smpe.library.prefix.CAZ2DATV,
// DISP=(NEW,CATLG,DELETE),
// DCB=(LRECL=6140,BLKSIZE=32760,RECFM=VB),
//* VOL=SER=XXXXXX,UNIT=YYYY,
// STORCLAS=sclass,
// SPACE=(CYL,(250,50,10))
//*
//AAZ2DATV DD DSN=smpe.library.prefix.AAZ2DATV,
// DISP=(NEW,CATLG,DELETE),
// DCB=(LRECL=6140,BLKSIZE=32760,RECFM=VB),
//* VOL=SER=XXXXXX,UNIT=YYYY,
// STORCLAS=sclass,
// SPACE=(CYL,(250,50,10))
2. Update SMPE CSI to the new library information
//jobname JOB ...
//SMP EXEC PGM=GIMSMP,REGION=0M
//SMPCSI DD DISP=SHR,DSN=APCDAL.MSPS.JCK120.DEV.CSI
//SMPLOG DD SYSOUT=*
//SMPLOGA DD SYSOUT=*
//SMPRPT DD SYSOUT=*
//SMPOUT DD SYSOUT=*
//SMPLIST DD SYSOUT=*
//SMPCNTL DD *
SET BOUNDARY(CAIT0) .
UCLIN .
ADD DDDEF(CAZ2DATV)
SHR DA(smpe.library.prefix.CAZ2DATV) .
ADD DDDEF(AAZ2DATV)
SHR DA(smpe.library.prefix.AAZ2DATV) .
ENDUCL .
SET BOUNDARY(CAID0) .
UCLIN .
ADD DDDEF(AAZ2DATV)
SHR DA(smpe.library.prefix.AAZ2DATV) .
ENDUCL .
/*
).
Feedback
Yes
No
Powered by
