On Wed, 26 Sep 2012 08:56:21 -0500, Paul Gilmartin <paulgboul...@aim.com> wrote: >But still, if RECEIVE tolerates processing a SYSMOD prior to its PRErequisites >on the assumption that >APPLY will sort things out, I might hope for the same flexibility with respect >to FMID.
RECEIVE doesn't so much "tolerate" as it ignores PRErequisites (co-requisites, negative requisites, etc.). That really has to be left up to APPLY/ACCEPT to figure out for the zone into which the SYSMODs are to be installed. All RECEIVE validates is SREL and FMID for an incoming SYSMOD. It would not be practical to sift through all of the combinations in all of the Target and Distribution zones to validate eligibility down to *requisites. Complex enough if you have varied FUNCTIONs installed under an SREL from one D/T zone to the next, but at a small shop, many moons ago, I was weird enough to have multiple SRELs in a common Global (not in any common D/T zone, however). In a prior post, I attempted to ask about such flexibility with FUNCTION SYSMODs akin to ASSIGN processing. I'm hoping Kurt can shed some light. >Does the order in which SYSMOD names appear in a SELECT option matter, either >to RECEIVE or to APPLY? Not to RECEIVE, as far as I read from SMP/E Commands, and cetainly not to APPLY, neither from the book nor from my experience with it. If SMP/E Reference says otherwise, I have not stumbled across a passage that says so. This was another question I tried to ask (albeit not clearly), again hoping Kurt will respond. Also, I meant to ask about this statement your original post: >RECEIVE SELECT( > F1 > F2 > F3 > ) FROMNTS(SMPNTS-path) Was this a typo or intentional? The rest of what follows lists E2 and E3, which I am surprised RECEIVE would process since these are not part of the SELECT, unless F2/F3 are FMIDSETs? Regards, Art Gutowski Compuware ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
