What is the correct process when a SYSMOD is discovered post-release
to have a corequisite in a FMID other than its own? Is the developer's
only recourse to create a dummy PTF to bear the ++IF ... REQ for the
SYSMOD in the other function and let that resolve a ++HOLD ERROR?
I read:
# 2.8 "SMP/E V3R4.0 Reference"
FMID
specifies the FMID to which the held SYSMOD is applicable.
It appears to me that for ++HOLD ERROR the FMID operand would be
more useful if it specified, instead, the FMID to which the
corrective SYSMOD must be applied, and the HOLD were enforced
only in zones containing that specified FMID.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
