SMP/E for z/OS Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Candidate selection

SMP/E for z/OS Commands
SA23-2275-01

The SYSMOD selection operands of the ACCEPT command can be specified separately or in combination in order to control the SYSMODs that SMP/E is to process. When specified separately, SMP/E selects only those SYSMODs that meet the one selection criterion specified. When you specify them in combination, SMP/E does the following checking to build the complete candidate list:

  1. SMP/E assumes that normal SYSMOD processing is:
    1. RECEIVE
    2. APPLY
    3. ACCEPT
    Therefore, before SMP/E accepts a SYSMOD, it checks to make sure you have applied it. SMP/E does this checking by looking at the applicable target zone to see if the SYSMOD has been installed there (not by looking at any information in the global zone SYSMOD entry). A SYSMOD is considered installed in the target zone if the entry indicates the SYSMOD is applied or superseded. The applicable target zone is determined from the RELATED subentry in the distribution zone DZONE entry.
    In some circumstances, you may want to accept a SYSMOD before it is applied—for example, when preparing the distribution libraries before doing a full system generation. In this case, you must specify the BYPASS(APPLYCHECK) operand, telling SMP/E not to check the target zone to make sure the SYSMOD has been applied.
    Note: The BYPASS(APPLYCHECK) function was previously provided by the NOAPPLY operand, which is no longer supported.
  2. SMP/E checks the global zone and the specified distribution zone to determine which SYSMODs in the global zone and SMPPTS have not already been accepted into the distribution zone.

    SMP/E checks each such SYSMOD to see if it meets the criteria of any additional selection operands.

    1. If you specify the EXCLUDE operand, SMP/E makes sure the SYSMOD was not specified in the exclude list.
    2. If you specify one or more of the SYSMOD-type operands (that is, FUNCTIONS, PTFS, APARS, or USERMODS), SMP/E checks to make sure the SYSMOD type was one of those specified.

      If you do not specify a SYSMOD-type operand, the default is for SMP/E to process only PTF SYSMODs.

    3. If you specify the FORFMID operand, SMP/E makes sure that either the FMID value on one of the ++VER statements within the SYSMOD or the SYSMOD ID itself matches either an FMID specified in FORFMID or one of the FMID values contained in a specified FMIDSET.
    4. If you specify the SOURCEID operand, SMP/E makes sure one of the SOURCEIDs of the SYSMOD matches a source ID that you have specified, either explicitly or implicitly, on the SOURCEID operand.
    5. If you specify the EXSRCID operand, SMP/E makes sure none of the SOURCEIDs of the SYSMOD matches a source ID you have specified, either explicitly or implicitly, on the EXSRCID operand.
      Note: If a given SYSMOD has multiple source IDs and you specify at least one of them implicitly or explicitly on the SOURCEID operand, and another one explicitly or implicitly on the EXSRCID operand, that SYSMOD is excluded from processing.

      Similarly, if you specify a given source ID implicitly or explicitly on the EXSRCID operand and also implicitly or explicitly on the SOURCEID operand, all SYSMODs with that source ID are excluded from processing.

    Each SYSMOD that satisfies all of these conditions is considered a candidate for the ACCEPT process. In other words, by specifying the SYSMOD type operands, the FORFMID operand, or the SOURCEID operand in combination, you cause SMP/E to select only SYSMODs that meet all the specified conditions.

  3. If you specify the SELECT operand, each SYSMOD specified in the select list is considered a candidate, regardless of its SYSMOD type, FMID value, or SOURCEID value. That is, SELECT has an additive effect on the SYSMOD selection. This is called select-mode processing. If you do not specify SELECT, this is called mass-mode processing.
    Note: If SELECT is the only operand you specify, only SYSMODs in the select list are processed.
  4. If you specify the XZREQ operand, unsatisfied cross-zone requisites that are needed in the set-to zone become candidates for installation. These SYSMODs are in addition to other SYSMODs that are chosen due to other operands, such as FORFMID and SOURCEID. If FORFMID is specified, only cross-zone requisites for the FMIDs specified on the FORFMID operand become candidates for installation. Other operands on the command, such as EXSRCID, have no effect on which cross-zone requisites become candidates for installation.
  5. If you specify the GROUP or GROUPEXTEND operand, SMP/E checks each of the candidate SYSMODs to determine whether they have any requisites that must also be accepted. SMP/E automatically includes the following SYSMODs, as long as they are not specified on the EXCLUDE operand or excluded by the EXSRCID operand:
    • Any SYSMOD not already accepted and specified as a prerequisite (that is, specified in the ++VER statement PRE operand) of one of the candidate SYSMODs
    • Any SYSMOD not already accepted and specified as a corequisite (that is, specified in the ++VER statement REQ operand) of one of the candidate SYSMODs
    • Any SYSMOD not already accepted and specified as a conditional requisite (that is, specified in the ++IF statement REQ operand) of one of the candidate SYSMODs
    • Any SYSMOD not already accepted and specified as a conditional requisite (CIFREQ subentry) in the distribution zone SYSMOD entry for one of the candidate SYSMODs
    If one of these requisites is held or not available and you specified GROUPEXTEND, SMP/E checks the global zone for any SYSMODs that have been received and that either supersede the requisite, or that match or supersede its HOLDERROR reason ID. The lowest-level SYSMOD found is then used to satisfy the requisite.
    • If you specified NOAPARS with GROUPEXTEND, SMP/E does not include APARs that resolve error reason IDs for the held requisites.
    • If you specified NOUSERMODS with GROUPEXTEND, SMP/E does not include USERMODs that resolve error reason IDs for the held requisites.
    Once a SYSMOD is added to the candidate list, it is eligible to be checked for additional requisites. The FORFMID, SOURCEID, and SYSMOD type operands have no effect on SYSMODs brought in because of the GROUP or GROUPEXTEND operand. The following example accepts all those SYSMODs with a source ID of PUT0701 that are applicable to EBB1102, plus any additional SYSMODs that are required, even though their source ID is not PUT0701 or their FMID is not EBB1102:
    SET      BDY(DLIB1)         /* Set to DLIB1 zone.       */.
    ACCEPT   SOURCEID(PUT0701)  /*                          */
             FORFMID(EBB1102)   /*                          */
             GROUP              /*                          */.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014