On Fri, 29 Jul 2016 12:21:26 -0500, Tom Marchant <[email protected]>
wrote:
>>>
>>Is this true even if RRRRRRR is an APAR ID rather than a SYSMOD ID? (I
>>understand
>>that's IBM's practice though not ours -- I recurrently need to submit RCFs.)
>
>What do you mean? An APAR is a SYSMOD. Do you mean, "What if an APAR fix
>(++APAR) was created with a SYSMOD ID of RRRRRRR?"
>
No. My understanding is that IBM's practice is (was?) that the reason ID
is the ID of an APAR which may be resolved by one or more PTFs which
SUPersede the reason ID which is not itself a delivered SYSMOD. This
is hinted at by:
z/OS
z/OS 2.1.0
SMP/E Version 3
SMP/E for z/OS Commands
The ACCEPT command
Processing
SYSMOD selection
Applicability checking
Exception SYSMODs (HOLD)
Exception data is considered resolved when one or more of the following are
true:
HOLDERROR and HOLDFIXCAT exception data is considered resolved if any of
the following conditions apply:
o The SYSMOD named as the reason ID for the exception is already
applied or
is superseded by a SYSMOD that is already applied.
o The SYSMOD named as the reason ID for the exception is being applied
concurrently or
is being superseded by a SYSMOD being applied concurrently.
o The applicable BYPASS operand is specified.
Yes, this suggests that the reason ID is always a SYSMOD ID, but I believe
that isn't (or recently wasn't) the case. Note the two mentions of
"superseded".
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
