> Once the APAR was validated in the field and ready for PTF creation, 
> a ++RELEASE(fmid) ERROR FMID(fmid) REASON(aparnum)
> statement was added to the HOLDDATA.

Please tell me you're joking!


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of Ed 
Jaffe [[email protected]]
Sent: Thursday, January 26, 2023 1:04 AM
To: [email protected]
Subject: HOLDDATA Not Working as Expected

Actual Sysprogs,

Recently I was surprised by an unexpected REPORT ERRSYSMODS behavior. I
think I've had a misconception about this for a long time...

Like many vendors, we maintain HOLDDATA with FIXCAT information as well
as ERROR HOLD and RELEASE statements.

One of our products had a bug in the base that was fixed by an APAR for
which we added a ++HOLD(fmid) ERROR FMID(fmid) REASON(aparnum) statement
to our HOLDDATA. Once the APAR was validated in the field and ready for
PTF creation, a ++RELEASE(fmid) ERROR FMID(fmid) REASON(aparnum)
statement was added to the HOLDDATA.

After receiving the latest HOLDDATA but *not* the fixing APAR or PTF
into the GLOBAL zone, I issued a REPORT ERRSYSMODS command and was
dismayed to see the PTF in error (PE) no longer appears on the EXCEPTION
SYSMOD REPORT.

Unless I did something wrong in my testing, this behavior means that
REPORT ERRSYSMODS stops helping our customers identify PEs on their
systems the moment our HOLDDATA indicates a fix for the PE is now
available -- even if the customer has not yet received or applied the
needed fix!

Is there an another way to tell if you have PEs applied that have not
yet been corrected through service?

Thanks,

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.phoenixsoftware.com%2F&data=05%7C01%7Csmetz3%40gmu.edu%7C64f664477c574c3516e908daff634676%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C638103099107254863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=R8OOYt1ZtVFmBIBr1C3YQmkOOoHbdI1S0va%2BIAud7g8%3D&reserved=0


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to