The holddata for SECINT looks like below. Note the function SYSMOD, not PTF SYSMOD ID: ++ HOLD (HSMA230) FMID(HSMA230) REASON(BHxxxxx) ERROR DATE(yyddd)
COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(B5.9,T5.7) CHGDT(yyddd))) CLASS(SECINT). ++ HOLD (HSMA240) FMID(HSMA240) REASON(CHxxxxx) ERROR DATE(yyddd) COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(B5.9,T5.7) CHGDT(yyddd))) CLASS(SECINT). ++ HOLD (HSMA230) FMID(HSMA230) REASON(BHxxxxx) ERROR DATE(yyddd) COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(B7.5,T7.2) CHGDT(yyddd))) CLASS(SECINT). ++ HOLD (HSMA240) FMID(HSMA240) REASON(CHxxxxx) ERROR DATE(yyddd) COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(B7.5,T7.2) CHGDT(yyddd))) CLASS(SECINT). ++ HOLD (HSMA220) FMID(HSMA220) REASON(AHxxxxx) ERROR DATE(yyddd) COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(B7.5,T7.2) CHGDT(yyddd))) CLASS(SECINT). Etc etc This is unlike the normal full holddata, which can be the PTF SYSMOD ID's: ++HOLD(UJ09068) FMID(HBB77B0) REASON(BA64026) ERROR DATE(22314) COMMENT(SMRTDATA(CHGDT(221110))) CLASS(PE). The optional SECINT ASSIGNS file, which you don't have to download, look like this: ++ ASSIGN SOURCEID(SECINT) TO(UIxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UIxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UIxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UIxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UJxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UJxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UJxxxxx). ++ ASSIGN SOURCEID(SECINT) TO(UJxxxxx). Etc etc In the example from Dave Jousma, with the APPLY SOURCEID(SECINT), I believe this would only work if you've also obtained the ASSIGN file from Resource Link too. When you run the REPORT ERRSYSMODS report, for SECINT HOLD CLASS it will the "SYSMOD NAME" as the FMID ID, which is different to a "normal" HOLD which lists the PTF SYSMOD. Made up example:: HOLD SYSMOD APAR ---RESOLVING SYSMOD---- HOLD HOLD FMID NAME NUMBER NAME STATUS RECEIVED CLASS SYMPTOMS HMJ4102 UW31189 AN80203 UW32213 GOOD YES PE HSMA230 HSMA230 AHxxxxx UIxxxxx GOOD YES SECINT Regards Patrick -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: 19 January 2023 16:13 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to determine if Enhanced HOLDDATA received? We may be talking at cross purposes here; I'm concerned about the hold class SECINT, not the source with the same name. The SECINT hold is on the PTF with the exposure, not the PTF correcting it. LIST HOLDDATA HOLDERROR. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Dave Jousma [000001a0403c5dc1-dmarc-requ...@listserv.ua.edu] Sent: Thursday, January 19, 2023 10:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to determine if Enhanced HOLDDATA received? On Thu, 19 Jan 2023 15:30:07 +0000, Seymour J Metz <sme...@gmu.edu> wrote: >I'm concerned with the SMP side of things; as long as a PTF is correctly flagged as PE, I don't care about the APAR unless there is a reason to bypass. > > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 > I cannot say for sure if that is the case or not. When doing a maintenance cycle, I'll pull the list from RL, and run an apply check/apply specific to SECINT to satisfy audit requirements that we are applying vulnerability fixes. APPLY SOURCEID ( SECINT ) GROUPEXTEND ( NOAPARS NOUSERMODS ) BYPASS ( HOLDSYSTEM ) NOJCLINREPORT RETRY ( YES ) My last time was a week ago, and I was surprised at the number that needed to go on to my pretty current V2.5 zone. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UI83571. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09625. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09744. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UO02058. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UO02059. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UI83640. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09561. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09564. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09567. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09570. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09665. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09697. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09698. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UJ09729. GIM22701I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD UI83424. Spot checking the first one, It was not fixing a ERROR PTF. Entry Type: SYSMOD Zone Name: GLOBAL Entry Name: UI83571 Zone Type: GLOBAL Description: Type: PTF Status: FMID: Date/Time: 23.003 08:42:37 REC -------- -------- -------- -------- -------- -------- ----- SREL Z038 FMID HSMA250 PRE UI83116 SUP AH50369 DH50369 SOURCEID ORD00052 PUT2212 SECINT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
