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


Operands

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

APARS
indicates that SMP/E should unload APAR SYSMODs.
Note:
  1. APARS can also be specified as APAR.
  2. When APARS is used with FUNCTIONS, PTFS, or USERMODS, SMP/E unloads any SYSMOD whose type matches any one of those specified.
  3. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
ASSEM
indicates that SMP/E should unload all ASSEM entries or the specified ASSEM entries.
DDDEF
indicates that SMP/E should unload all DDDEF entries or the specified DDDEF entries.
DELETE
indicates that SMP/E should unload entries for function SYSMODs that have been explicitly deleted from the target zone or distribution zone by other function SYSMODs.
Note:
  1. DELETE can also be specified as DEL.
  2. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD was also specified, even if it was not.
DLIB
indicates that SMP/E should unload all DLIB entries or the specified DLIB entries.
element
is used to unload a particular type of data element entry. It indicates that SMP/E should unload all data element entries of that type or the specified data element entries.
Note:
  1. Data element entries exist only in the target and distribution zones.
  2. The "SMP/E Modification Control Statements" topic in SMP/E for z/OS Reference shows the types of data elements that can be specified for the element operand.
  3. Some types of elements, such as panels, messages, or text, may have been translated into several languages. In these cases, the element operand contains xxx, which represents the language used for the element. (If an element was not translated, the element operand does not contain any xxx value.) The "SMP/E Modification Control Statements" topic in SMP/E for z/OS Reference contains a table that shows the xxx values and the languages they represent.
ERROR
indicates that SMP/E should unload SYSMOD entries in which the ERROR indicator is set.
Note:
  1. ERROR can also be specified as ERR.
  2. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD was also specified, even if it was not.
  3. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
EXSRCID
indicates that SYSMODs associated with the specified source IDs should not be unloaded.
Note:
  1. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  2. There are two ways to specify source IDs:
    • Explicitly, by fully specifying a particular source ID (for example, RSU0711). In this case, all SYSMODs that contain the identified source ID are excluded.
    • Implicitly, by partially specifying a source ID value using asterisks (*) as global characters and percent signs (%) as placeholders.
      • A single asterisk indicates that zero or more characters can occupy that position. Here are some examples:
        • For RSU*, all SYSMODs that contain a source ID that begins with the character string RSU* are excluded.
        • For *0711, all SYSMODs that contain a source ID that ends with the character string 0711 are excluded.
        • For RSU*1, all SYSMODs that contain a source ID that begins with the character string RSU and ends with the character string 1 are excluded.
      • A single percent sign indicates that any one single character can occupy that position. For RSU0%11, for example, SYSMODs that contain any of these source IDs are excluded: RSU0711, RSU0211, and RSU0311. SYSMODs that contain source ID RSU00711 are not excluded.

    Any number of asterisks and percent signs can be used within a single partially specified source ID.

    The following examples are valid source ID specifications:
    RSU0709
    RSU*
    IBM.Device.20%4
    IBM.Device.*.zAAP
  3. A given source ID may be explicitly specified only once on the EXSRCID operand.
  4. The same source ID may not be explicitly specified on both the EXSRCID and SOURCEID operands.
  5. If a source ID is specified implicitly on the EXSRCID operand and also, either implicitly or explicitly, on the SOURCEID operand, all SYSMODs with that source ID are excluded from processing.
  6. If a given SYSMOD has multiple source IDs, if at least one of those source IDs is specified either implicitly or explicitly on the SOURCEID operand, and if another one of its source IDs is specified either implicitly or explicitly on the EXSRCID operand, the SYSMOD is excluded from processing.

    For example, assume PTF UZ12345 has been assigned source IDs SMCREC and PUT0703. If you specify SOURCEID(SMC*) and EXSRCID(PUT0703), the SYSMOD is excluded from processing.

  7. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
  8. A source ID value might contain mixed case alphabetic characters. However, SMP/E ignores the case when identifying matches for a specified source ID value. For example, a specified source ID value of ABCDEF matches a value of abcdef.
FORFMID
indicates that SMP/E should unload only entries currently owned by one of the specified FMIDs or by an FMID defined in one of the specified FMIDSET entries.
Note:
  1. You can specify FMIDs, FMIDSET entries, or both.
  2. Only element and SYSMOD entries are unloaded by the FORFMID operand.
  3. Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD had also been specified, even if it has not, unless an element type operand was also specified. In that case, FORFMID limits the element entries that are unloaded.
  4. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
FUNCTIONS
indicates that SMP/E should unload function SYSMODs.
Note:
  1. FUNCTIONS can also be specified as FUNCTION.
  2. When FUNCTIONS is used with APARS, PTFS, or USERMODS, SMP/E unloads any SYSMOD whose type matches any one of those specified.
  3. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
hfs_element
is used to unload a particular type of hierarchical file system element entry. It indicates that SMP/E should unload all hierarchical file system element entries of that type or the specified hierarchical file system element entries.
Note:
  1. Hierarchical file system element entries exist only in the target and distribution zones.
  2. The "SMP/E Modification Control Statements" topic in SMP/E for z/OS Reference shows the types of hierarchical file system elements that can be specified for the hfs_element operand.
  3. Some types of hierarchical file system elements, such as panels, messages, or text, may have been translated into several languages. In these cases, the hfs_element operand contains xxx, which represents the language used for the element. (If an element was not translated, the hfs_element operand does not contain any xxx value.) The "SMP/E Modification Control Statements" topic in SMP/E for z/OS Reference contains a table that shows the xxx values and the languages they represent.
JAR
indicates that SMP/E should unload all JAR entries or the specified JAR entries.
LMOD
indicates that SMP/E should unload all LMOD entries or the specified LMOD entries.
MAC
indicates that SMP/E should unload all MAC entries or the specified MAC entries.
MOD
indicates that SMP/E should unload all MOD entries or the specified MOD entries.
NOACCEPT
indicates that SMP/E should unload SYSMOD entries from the current zone that are not accepted into the specified distribution zone.
Note:
  1. NOACCEPT can also be specified as NOACC.
  2. If a target zone is specified on the SET command and no distribution zone is specified on NOACCEPT, SMP/E uses the distribution zone from the RELATED subentry in the TARGETZONE entry.
  3. If a distribution zone is specified on the SET command and no distribution zone is specified on NOACCEPT, SMP/E issues an error message.
  4. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  5. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
NOAPPLY
indicates that SMP/E should unload SYSMOD entries from the current zone that are not applied to the specified target zone.
Note:
  1. NOAPPLY can also be specified as NOAPP.
  2. If a distribution zone is specified on the SET command and no target zone is specified on NOAPPLY, SMP/E uses the target zone from the RELATED subentry in the DLIBZONE entry.
  3. If a target zone is specified on the SET command and no target zone is specified on NOAPPLY, SMP/E issues an error message.
  4. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  5. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
NOSUP
indicates that SMP/E should unload entries for SYSMODs that have not been superseded.
Note:
  1. NOSUP is mutually exclusive with SUP.
  2. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  3. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
PROGRAM
indicates that SMP/E should unload all program element entries or the specified program element entries.
PTFS
indicates that SMP/E should unload PTF SYSMODs.
Note:
  1. PTFS can also be specified as PTF.
  2. When PTFS is used with APARS, FUNCTIONS, or USERMODS, SMP/E unloads any SYSMOD whose type matches any one of those specified.
  3. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
RESTORE
indicates that SMP/E should unload SYSMOD entries in which the RESTORE indicator is set. These SYSMODs have been incompletely restored and are “in error.”
Note:
  1. RESTORE is allowed when the SET command specifies a target zone.
  2. RESTORE can also be specified as RES.
  3. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  4. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
SOURCEID
indicates that SMP/E should unload only those SYSMOD entries associated with one of the specified SOURCEID values.
Note:
  1. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  2. There are two ways to specify source IDs:
    • Explicitly, by fully specifying a particular source ID (for example, RSU0711). In this case, all SYSMODs that contain the identified source ID are selected.
    • Implicitly, by partially specifying a source ID value using asterisks (*) as global characters and percent signs (%) as placeholders.
      • A single asterisk indicates that zero or more characters can occupy that position. Here are some examples:
        • For RSU*, all SYSMODs that contain a source ID that begins with the character string RSU are selected.
        • For *0711, all SYSMODs that contain a source ID that ends with the character string 0711 are selected.
        • For RSU*1, all SYSMODs that contain a source ID that begins with the character string RSU and ends with the character string 1 are selected.
      • A single percent sign indicates that any one single character can occupy that position. For RSU0%11, for instance, SYSMODs that contain any of these source IDs are selected: RSU0711, RSU0211, and RSU0311. SYSMODs that contain source ID RSU00711 are not selected.

    Any number of asterisks and percent signs can be used within a single partially specified source ID.

    The following examples are valid source IDs:
    RSU0709
    RSU*
    IBM.Device.20%4
    IBM.Device.*.zAAP
  3. A given source ID may be explicitly specified only once on the SOURCEID operand.
  4. The same source ID may not be explicitly specified on both the EXSRCID and SOURCEID operands.
  5. If a source ID is specified implicitly on the SOURCEID operand and also, either implicitly or explicitly, on the EXSRCID operand, all SYSMODs with that source ID are excluded from processing.
  6. If a given SYSMOD has multiple source IDs, if at least one of those source IDs is specified either implicitly or explicitly on the SOURCEID operand, and if another one of its source IDs is specified either implicitly or explicitly on the EXSRCID operand, the SYSMOD is excluded from processing.

    For example, suppose PTF UZ12345 has been assigned source IDs SMCREC and PUT0703. If you specify SOURCEID(SMC*) and EXSRCID(PUT0703), the SYSMOD is excluded from processing.

  7. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
  8. A source ID value might contain mixed case alphabetic characters. However, SMP/E ignores the case when identifying matches for a specified source ID value. For example, a specified source ID value of ABCDEF matches a value of abcdef.
SRC
indicates that SMP/E should unload all SRC entries or the specified SRC entries.
SUP
indicates that SMP/E should unload entries for SYSMODs that have been superseded.
Note:
  1. SUP is mutually exclusive with NOSUP.
  2. Because this operand describes the type of SYSMOD to be unloaded, SMP/E processes it as though SYSMOD had also been specified, even if it has not.
  3. If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
SYSMODS
indicates that SMP/E should unload all SYSMOD entries or the specified SYSMOD entries.
You can limit which SYSMOD entries are unloaded by coding one or more of the following SYSMOD qualifier operands:
  • APARS, FUNCTIONS, PTFS, or USERMODS
  • DELETE
  • ERROR
  • EXSRCID
  • FORFMID
  • NOACCEPT
  • NOAPPLY
  • NOSUP or SUP
  • RESTORE
  • SOURCEID
Note:
  1. SYSMODS can also be specified as SYSMOD.
  2. If you specify any of the SYSMOD qualifier operands, SMP/E assumes that you want the SYSMOD entries unloaded and thus processes as if you had also entered SYSMOD.
USERMODS
indicates that SMP/E should unload USERMODs.
Note:
  1. USERMODS can also be specified as USERMOD.
  2. When USERMODS is used with APARS, FUNCTIONS, or PTFS, SMP/E unloads any SYSMOD whose type matches any one of those specified.
XZLMODP
indicates that SMP/E should unload MOD entries for all modules that have been linked into load modules controlled by a different target zone. (The MOD entries for these modules contain XZLMODP subentries.)
Note:
  1. XZLMODP is allowed only when the SET command specifies a target zone.
  2. The appropriate MOD entries are unloaded, regardless of whether the MOD operand was specified on the UNLOAD command.
  3. If both MOD and XZLMODP are specified, only MODs with cross-zone subentries are unloaded. If a list of MODs and XZLMODP are specified, all the specified MODs, as well as all the MODs with cross-zone subentries, are unloaded.
XZMODP
indicates that SMP/E should unload LMOD entries for all load modules containing modules from a different target zone. (The LMOD entries for these load modules contain XZMODP subentries.)
Note:
  1. XZMODP is allowed only when the SET command specifies a target zone.
  2. The appropriate LMOD entries are unloaded, regardless of whether the LMOD operand was specified on the UNLOAD command.
  3. If you specify both LMOD and XZMODP, only LMODs with cross-zone subentries are unloaded. If you specify a list of LMODs and XZMODP, all the specified LMODs, as well as all the LMODs with cross-zone subentries, are unloaded.

For examples of unloading each specific entry type, see the topic for that entry in the "SMP/E Data Set Entries" topic in SMP/E for z/OS Reference.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014