I’m not sure exactly what you're doing, but maybe this will help. I create my
own ++HOLD records occasionally to prevent a PTF from installing before a
corresponding 'conditioning PTF' is running on all sharing systems. Haven't
seen one for a while, but these have typically been for a sysplex XCF change
that is accomplished in two stages. An IBM ++HOLD instructs me to hold off
applying the final PTF until all systems are ready for it. My ++HOLD keeps it
from going on too soon, since only I know the downstream runtime environment.
The user reason documents the PTF relationship. Once I'm ready for the final
PTF, I release my ++HOLD as shown below. Note that this is a standalone SMPE
job not embedded in any sysmod.
//SMPHOLD DD *
++RELEASE(UA70373) FMID(HDZ1D10) USER REASON(UA70229) DATE(14010) .
//*
//SYSIN DD *
SET BOUNDARY(GLOBAL) .
RECEIVE
HOLDDATA LIST .
.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Bruce Hewson
Sent: Friday, September 11, 2015 10:02 PM
To: [email protected]
Subject: SMPE -removal of USERMOD ++HOLD created instream
Hi all,
I have been changing ++HOLD REASON codes for some USERMODs.
But I found that the previous ++HOLD does not disappear nicely.
I tried using ++RELEASE but that fails. Something about the ++HOLD being
encoded inside the ++USERMOD.
Does anyone have a way to remove these ++HOLDs nicely?
Thanks
Bruce
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
