We are using CA Common Services with V15 in our systems.
We are trying to apply the latest maintenance for the product through MSM portal.
We have received the latest maintenance and also have done the apply for all the PTF's after reviewing the hold actions.
We are unable to fetch the details for the effected libraries in MSM.
Can you please help us to find the effected libraries for the roll out of the maintenance.
Thank You
Release : 15.0
Component : Chorus Software Manager
To check the status of the ++HOLD/++RELEASE SUMMARY REPORT you could go to your CSM's path /mpm/scroot//DatabaseM/CA/error_hold_data/ and browse file ALL-HOLDDATA.TXT.
Search on the reason code listed in the report in ALL-HOLDDATA.TXT to get more information. For example:
1PAGE 0001 - NOW SET TO GLOBAL ZONE DATE 06/27/22 TIME 04:47:14 SMP/E 37.10 SMPHRPT OUTPUT
RECEIVE ++HOLD/++RELEASE SUMMARY REPORT
NOTE: SMD NF - SYSMOD NOT RELEASED - NOT FOUND IN THE GLOBAL ZONE
RSN NF - SYSMOD NOT RELEASED - NOT HELD FOR THIS REASONID
INT HLD - SYSMOD NOT RELEASED - CANNOT RELEASE INTERNAL SYS HOLD
SYSMOD TYPE STATUS REASON FMID ++HOLD MCS STATEMENTS
CAADE00 ERR N/A AC68557 CAADE00
CAADE00 FIXC N/A TR41001 CAADE00
CAADE00 FIXC N/A TR41344 CAADE00
CAADE00 FIXC N/A TR42501 CAADE00
CAADE00 FIXC N/A TR42675 CAADE00
CAADE00 FIXC N/A TR48812 CAADE00
CAADE00 FIXC N/A TR49924 CAADE00
++HOLD(CAADE00) ERROR FMID(CAADE00)
REASON(AC68557) DATE(14079) CLASS(HIPER)
COMMENT(
PROBLEM DD-2075: DSF RETURN CODE BDM001 AFTER APPLYING RO67544
SMRTDATA(CHGDT(140321) FIX(RO68211)
SYMP(DAL)
)).
You could the verify that RO68211 is applied. If it is not then it should be applied.
Instead reviewing SMPHRPT you could run the exception SYSMOD report in CSM or SMP/E batch.
This is the syntax for batch SMP/E:
REPORT ERRSYSMODS
ZONES(GLOBAL,targetzone)
NOPUNCH .
If you do not have CSM you can download the HOLDDATA with this FTP JCL as an example:
//ALOC EXEC PGM=IEFBR14
//DISTLOAD DD DSN=hlq.HOLDDAT6,
// DISP=(NEW,CATLG,DELETE),UNIT=(3390),
//* VOL=SER=TECH09,
// STORCLAS=IPCSDUMP,
// SPACE=(CYL,(5,5),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80000)
//ESDGET EXEC PGM=FTP,PARM='(EXIT TIMEOUT 720'
//SYSTCPD DD DSN=VTAM.TCPIP.TCPIP.DATA,DISP=SHR
//*ftp.ca.com
//FTPCMDS DD *
LOCSIte FWFriendly
//SYSPRINT DD SYSOUT=*
//INPUT DD *
ftp.broadcom.com
anonymous [email protected]
cd /pub/HoldData/
ascii
LOCSIte FWFriendly
locsite LR=80 REC=FB BLOCKSI=0
locsite PRI=20 SEC=10 CY
get ALL-HOLDDATA.TXT 'hlq.HOLDDAT6' (REPLACE
quit
/*
To find the effected libraries for the roll out of the maintenance I would refer you to the LIST ALLZONES. This is the JCL to generate this report:
//SMPGO EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=OLD,DSN=HLQ.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DUMMY
//SMPLIST DD SYSOUT=*
//*
//SMPCNTL DD *
SET BDY(GLOBAL).
LIST ALLZONES.
/*
After any products is installed you should be able to refer to the startup JCL to find the startup target loadlib that is required for a specific product. This is what I would recommend.
In the LIST ALLZONES report you could search on DDDEF's:
For example:
1PAGE 3045 - NOW SET TO TARGET ZONE CAIT18 DATE 06/28/22 TIME 12:33:11 SMP/E 37.12 SMPLIST OUTPUT
LIST SUMMARY REPORT FOR CAIT18
ENTRY-TYPE ENTRY-NAME STATUS
DATA STARTS ON PAGE 2733
DDDEF STARTS ON PAGE 1758
LMOD STARTS ON PAGE 1762
MACRO STARTS ON PAGE 2633
On PAGE 1758 - NOW SET TO TARGET ZONE CAIT18 DATE 06/28/22 TIME 12:33:11 SMP/E 37.12 SMPLIST OUTPUT you will see a list of all the target datasets:
CAIT18 DDDEF ENTRIES
NAME
AAGJCULP DATASET = HLQ.IDMS.R190.AAGJCULP
SHR
AAGJDATV DATASET = HLQ.IDMS.R190.AAGJDATV
SHR
AAGJMAC DATASET = HLQ.IDMS.R190.AAGJMAC
SHR
AAGJMOD DATASET = HLQ.IDMS.R190.AAGJMOD
SHR
AAGJMSG DATASET = HLQ.IDMS.R190.AAGJMSG
CAGJLOAD DATASET = HLQ.IDMS.R190.CAGJLOAD
SHR
To find the target LOADLIB that is used at runtime to start the product at runtime you should research this in the documentation for the product because it is not possible to depend on this SMP/E report alone. You can use this report to get the HLQ for a target LOADLIB but you should depend on the product documentation also.