environment is z/os 1.11. am ramping up to install 1.13.
when, in z/so 1.11, I run the smp/e report
REPORT MISSINGFIX ZONES(MVST100)
FIXCAT ( IBM.COEXISTENCE.Z/OS.V1R13 ) .
report all by itself (asking for info for ONLY ibm.coexistence.z/os.v1r13 )
the SMPPUNCH output contains
SET BDY(MVST100)
APPLY CHECK SELECT ( ……
and a long list of ptf-s appears, NONE of which is commented out.
(and the list DOES include ua59383 and ua60054 as “good to go” )
this is good.
but when I do this:
FIXCAT ( IBM.COEXISTENCE.Z/OS.V1R13
IBM.FUNCTION.HEALTHCHECKER ) .
then i get the same laundry list of ptf-s in the SMPPUNCH output … BUT NOW,
the followng two ptf-s are commented out:
ua59383, and ua60054
I have investigated those two ptf-s by reading them in the smppts dataset, as
well as by doing a ‘query’ on their respective SMPCSI info in the smp/e dialog.
I cannot find any reason why the “report mssingfix fixcat” process should give
them as “good to go” in one context, and “not good to go” in the second context.
can anyone shed any light on this in general, or in particular (as regard these
two particular ptf-s)? how does smp/e make such a varying determination?
what does it have at its disposal that I , manually, do not have ?
thank you.
/s/ tuco bonno;
Graduate, College of Conflict Management;
University of SouthEast Asia;
"I partied on the Ho Chi Minh Trail - tiến lên !! "
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
