Operands

ALLZONES

indicates that SMP/E should list information from the global zone and all the target and distribution zones defined by ZONEINDEX subentries.

Note:

ALLZONES is mutually exclusive with HOLDDATA, HOLDERROR, HOLDFIXCAT, HOLDSYSTEM, HOLDUSER, MCS, NOACCEPT and NOAPPLY.
You can limit the information to be listed by specifying only the entries or entry types that you need. For example:
```
SET     BDY(GLOBAL)    /* set to global zone      */.
LIST    SYSMOD(UZ12345)/* list this SYSMOD entry  */
        ALLZONES       /* from wherever it is     */.
```
lists SYSMOD entry UZ12345 in each zone to which it has been applied or accepted.
ALLZONES is allowed when the SET command specifies the global zone, a target zone, or a distribution zone.
The entries listed are the same, regardless of the type of zone you specify, because the output is determined by the additional operands on the LIST command and by the entry types valid within each zone to be listed. For example, the following lists module X in all target and distribution zones:
```
LIST ALLZONES MOD(X).
```
The global zone is skipped, because there are no modules in the global zone.

APARS

indicates that SMP/E should list APAR SYSMODs.

Note:

APARS can also be specified as APAR.
When APARS is used with FUNCTIONS, PTFS, or USERMODS, SMP/E lists any SYSMOD whose type matches any one of those specified.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.

ASSEM

indicates that SMP/E should list all ASSEM entries or the specified ASSEM entries.

Note: ASSEM is allowed when the SET command specifies a target zone or distribution zone.

BACKUP

indicates that SMP/E should list all BACKUP entries or the specified BACKUP entries.

Note:

BACKUP is mutually exclusive with all other LIST operands.
BACKUP is allowed when the SET command specifies a target zone.

BYPASS

indicates that SMP/E should list entries for SYSMODs installed using the BYPASS operand.

Note:

Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.

DDDEF

indicates that SMP/E should list all DDDEF entries or the specified DDDEF entries.

DELETE

indicates that SMP/E should list entries for function SYSMODs that have been explicitly deleted from the target zone or distribution zone by other function SYSMODs.

Note:

DELETE is allowed when the SET command specifies a target zone or distribution zone.
DELETE can also be specified as DEL.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.

DLIB

indicates that SMP/E should list all DLIB entries or the specified DLIB entries.

Note: DLIB is allowed when the SET command specifies a target zone or distribution zone.

DLIBZONE

indicates that SMP/E should list the DLIBZONE entry.

Note:

DLIBZONE is allowed when the SET command specifies a distribution zone.
DLIBZONE can also be specified as DZONE.

element

is used to list a particular type of data element entry. element indicates that SMP/E should list all data element entries of that type or the specified data element entries.

Note:

element is allowed when the SET command specifies a target zone or distribution zone.
"Data Element MCS" in 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.
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 a 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 list SYSMOD entries in which the ERROR indicator is set.

Note:

ERROR is allowed when the SET command specifies a target zone or distribution zone.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.
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 listed.

Note:

Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.
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
```
A given source ID can be explicitly specified only once on the EXSRCID operand.
The same source ID cannot be explicitly specified on both the EXSRCID and SOURCEID operands.
If a source ID is specified, implicitly or explicitly, on the EXSRCID operand and on the SOURCEID operand, all SYSMODs with that source ID are excluded from processing.
If a given SYSMOD has multiple source IDs and at least one of those source IDs is specified implicitly or explicitly on the source ID operand, the SYSMOD is excluded from processing if another one of its source IDs is specified implicitly or explicitly on the EXSRCID operand.
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.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
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.

FEATURE

indicates SMP/E should list all FEATURE entries or the specified FEATURE entries.

Note:

FEATURE is allowed when ALLZONES is specified or the SET command specifies the global zone.
FEATURE with the FORFMID operand lists only FEATUREs with the specified FMIDs.

FMIDSET

indicates that SMP/E should list all FMIDSET entries or the specified FMIDSET entries.

Note:

FMIDSET is allowed when the SET command specifies the global zone.
FMIDSET can also be specified as FMSET.
To list element and SYSMOD entries owned by an FMID defined in a particular FMIDSET entry, use the FORFMID operand, not FMIDSET. The FMIDSET operand provides a listing only of the specified FMIDSET entries, not a listing of the entries owned by FMIDs defined in the specified FMIDSET entries.

FORFMID

indicates that SMP/E should list only entries currently owned by one of the specified FMIDs or by an FMID defined in one of the specified FMIDSET entries.

Note:

You can specify FMIDs, FMIDSET entries, or both.
Only element and SYSMOD entries are listed by the FORFMID operand.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not, unless an element type operand was also specified. In that case, FORFMID limits the element entries that are listed.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
FORFMID with the HOLDDATA operand lists only SYSMODs with the specified FMID that have been received.

FUNCTIONS

indicates that SMP/E should list function SYSMODs.

Note:

FUNCTIONS can also be specified as FUNCTION.
When FUNCTIONS is used with APARS, PTFS, or USERMODS, SMP/E lists any SYSMOD whose type matches any one of those specified.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.

GLOBALZONE

indicates that SMP/E should list the GLOBALZONE entry.

Note:

GLOBALZONE is allowed when the SET command specifies the global zone.
GLOBALZONE can also be specified as GZONE.

hfs_element

is used to list a particular type of hierarchical file system element entry. hfs_element indicates that SMP/E should list all hierarchical file system element entries of that type or the specified hierarchical file system element entries.

Note:

hfs_element is allowed when the SET command specifies a target zone or distribution zone.
"Hierarchical File System Element MCS" in 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.
To list UNIX shell scripts for the zone, enter the LIST command for the hfs_element type of SHELLSCR. To list all shell scripts for the zone, specify SHELLSCR by itself. To list only specific shell scripts, include the names of the shell script files with the SHELLSCR operand. An example is shown in Example 5: List entries for specific UNIX shell scripts.
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.

HOLDDATA

indicates that SMP/E should list HOLDDATA. How the HOLDDATA is listed depends on whether you specify the SYSMOD operand with the HOLDDATA operand.

When specified with the SYSMOD operand, HOLDDATA indicates that SMP/E should list only SYSMODs that are held, and should include the ++HOLD message control statements (HOLDDATA) associated with the SYSMOD entries that are listed. No separate HOLDDATA entries are listed.
When specified without the SYSMOD operand, HOLDDATA indicates that SMP/E should list all HOLDDATA entries. No SYSMOD entries are listed.
You can limit which HOLDDATA entries are listed by coding one or more of the following operands:
- HOLDERROR
- HOLDFIXCAT
- HOLDSYSTEM
- HOLDUSER
If you specify more than one type of hold, SMP/E lists only entries containing holds for all the specified types. For example, the following commands list all HOLDDATA entries with both HOLDERROR and HOLDSYSTEM reason IDs:
```
SET      BDY(GLOBAL)    /* set to global zone       */.
LIST     HOLDDATA       /* list only the HOLDDATA   */
         HOLDERROR      /* entries that contain     */
         HOLDSYSTEM     /* both error and system    */
                        /* holds                    */.
```

Note:

HOLDDATA is allowed when the SET command specifies the global zone.
HOLDDATA with the FORFMID operand lists only SYSMODs with the specified FMID that have been received.

Table 1 summarizes the LIST results for various combinations of the HOLDDATA operand with other related operands.

Table 1. Information listed for HOLDDATA combined with other operands
HOLD-related operands	Information listed when the SYSMOD operand is specified	Information listed when the SYSMOD operand is not specified
HOLDDATA (without HOLDERROR, HOLDFIXCAT, HOLDSYSTEM, or HOLDUSER)	SYSMOD entries plus all associated ++HOLD statements.	All ++HOLD statements of all types.
HOLDDATA (with HOLDERROR, HOLDFIXCAT, HOLDSYSTEM, or HOLDUSER)	SYSMOD entries for SYSMODs that have the specified HOLDDATA types, plus all associated ++HOLD statements for those SYSMODs.	All ++HOLD statements of the specified types.
HOLDERROR, HOLDFIXCAT, HOLDSYSTEM, or HOLDUSER (without HOLDDATA)	SYSMOD entries for SYSMODs that have the specified HOLDDATA types. No ++HOLD statements included with the SYSMOD entries.	SYSMOD entries for SYSMODs that have the specified HOLDDATA types. No ++HOLD statements are included with the SYSMOD entries.

HOLDERROR

When specified without the HOLDDATA operand (and either with or without the SYSMOD operand), HOLDERROR indicates that SMP/E should list only SYSMODs associated with error hold reason IDs. The associated ++HOLD message control statements are not listed.

Note: If the reason IDs are bypassed or resolved, these SYSMODs might not actually be held during APPLY or ACCEPT processing.

When specified with the HOLDDATA operand but without the SYSMOD operand, HOLDERROR indicates that HOLDDATA entries for error hold reason IDs should be listed. No SYSMOD entries are listed.

Note:

HOLDERROR is allowed when the SET command specifies the global zone.
HOLDERROR can also be specified as HOLDERR.

HOLDFIXCAT

When specified without the HOLDDATA operand (and either with or without the SYSMOD operand), HOLDFIXCAT indicates that SMP/E should list only SYSMODs associated with the fix category hold reason IDs. The associated ++HOLD message control statements are not listed.

When specified with the HOLDDATA operand but without the SYSMOD operand, HOLDFIXCAT indicates that HOLDDATA entries for fix category hold reason IDs should be listed. No SYSMOD entries are listed.

When specified with the HOLDDATA and the SYSMOD operands, HOLDFIXCAT indicates that HOLDDATA entries for fix category hold reason IDs should be listed, and the SYSMOD entries for those held SYSMODs should be listed.

Note:

HOLDFIXCAT is allowed only when the SET command specifies the global zone.
HOLDFIXCAT and ALLZONES are mutually exclusive.

HOLDSYSTEM

When specified without the HOLDDATA operand (and either with or without the SYSMOD operand), HOLDSYSTEM indicates that SMP/E should list only SYSMODs associated with system hold reason IDs. The associated ++HOLD message control statements are not listed.

Note: If the reason IDs are bypassed or resolved, these SYSMODs might not actually be held during APPLY or ACCEPT processing.

When specified with the HOLDDATA operand but without the SYSMOD operand, HOLDSYSTEM indicates that SMP/E should list HOLDDATA entries for system hold reason IDs. No SYSMOD entries are listed.

Note:

HOLDSYSTEM is allowed when the SET command specifies the global zone.
HOLDSYSTEM can also be specified as HOLDSYS.

HOLDUSER

When specified without the HOLDDATA operand (and either with or without the SYSMOD operand), HOLDUSER indicates that SMP/E should list only SYSMODs associated with user hold reason IDs. The associated ++HOLD message control statements are not listed.

Note: If the reason IDs are bypassed or resolved, these SYSMODs might not actually be held during APPLY or ACCEPT processing.

When specified with the HOLDDATA operand but without the SYSMOD operand, HOLDUSER indicates that HOLDDATA entries for user hold reason IDs should be listed. No SYSMOD entries are listed.

Note: HOLDUSER is allowed when the SET command specifies the global zone.

JAR

indicates that SMP/E should list all Java™ Archive (JAR) file entries or the specified JAR entries.

LMOD

indicates that SMP/E should list all LMOD entries or the specified LMOD entries.

Note: LMOD is allowed when the SET command specifies a target zone or distribution zone.

LOG

indicates that SMP/E should list either the total contents of the LOG or the contents within a selected date range.

(mm dd yy, mm dd yy) specifies a range of dates within the data set to be listed. If no date range is specified, the contents of the entire LOG data set are listed.

The dates are specified as mm dd yy, where mm is the month (01 to 12), dd is the day (01 to 31), and yy is the year (00 to 99). Blanks separate the month, day, and year.

The following commands list the data in the LOG for June 8 through June 11, 2008:

SET      BDY(TGT1)      /* set to target zone       */.
LIST     LOG(06 08 07   /* list log within this     */
             06 11 07)  /* date range               */.

These commands list the data in the LOG for one day, June 9, 2008:

SET      BDY(TGT1)      /* set to target zone       */.
LIST     LOG(06 09 07   /* list log for this one    */
             06 09 07)  /* day                      */.

Note:

LOG is mutually exclusive with all other LIST operands.
To determine which LOG data set to list, SMP/E checks the SMPLOG DDDEF entry in the zone specified on the SET command.
SMP/E views its LOG data set as one "logical" data set, even though there might actually be two separate physical data sets: SMPLOG and SMPLOGA. So, if an SMPLOGA DDDEF is defined in the zone and data has spilled over from the SMPLOG data set into the SMPLOGA data set, LIST LOG also lists the contents of the SMPLOGA data set. You can also specify a date range that spans the SMPLOG and SMPLOGA data sets, or a date range that is only in the SMPLOGA data set, because SMP/E views the two data sets as a single "logical" data set.

MAC

indicates that SMP/E should list all MAC entries or the specified MAC entries.

MCS

specifies that SMP/E should list all or the specified . LIST MCS can be used to print PTF cover letters.

If no SYSMOD IDs are specified, SMP/E lists the message control statements associated with all the SYSMOD entries in the current zone.

If SYSMOD IDs are specified, SMP/E lists only the message control statements for the specified SYSMOD entries. For example, the following commands list only the message control statements for AZ12345:

SET      BDY(TGT1)      /* set to target zone       */.
LIST     APAR           /* list all APAR type       */
         SYSMOD         /* SYSMODs plus             */
         MCS(AZ12345)   /* this one MCS entry       */.

MOD

indicates that SMP/E should list all MOD entries or the specified MOD entries.

NOACCEPT

indicates that SMP/E should list SYSMOD entries from the current zone that are not accepted into a particular distribution zone. You can use NOACCEPT to:

See which SYSMODs have been received but have not yet been accepted into the specified distribution zone.
To do this, specify the global zone on the SET command and the distribution zone you want to check on the NOACCEPT operand.
See which SYSMODs have been applied in a particular target zone but have not yet been accepted into one of these zones:
- Its related distribution zone
- The distribution zone specified on NOACCEPT
To do this, specify the desired target zone on the SET command and take one of these actions:
- To check for SYSMODs that have not been accepted into the related distribution zone, specify NOACCEPT without a zone name.
- To check for SYSMODs that have not been accepted into a particular distribution zone, specify NOACCEPT with the appropriate distribution zone name.
Compare which SYSMODs are accepted in two distribution zones.
To do this, specify one distribution zone on the SET command and the other on the NOACCEPT operand. SMP/E lists the SYSMODs that have been accepted into the set-to zone, but not into the NOACCEPT zone.

For examples, see Examples.

Note:

NOACCEPT can also be specified as NOACC.
If you specify either the global zone or a distribution zone on the SET command, you must specify a distribution zone on NOACCEPT.
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.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
You can also use the REPORT SYSMODS command to compare zones and to generate the commands needed to install SYSMODs in the zone where they are not installed. See The REPORT SYSMODS command for more information.

NOAPPLY

indicates that SMP/E should list SYSMOD entries from the current zone that are not applied to a particular target zone. You can use NOAPPLY to:

See which SYSMODs have been received but have not yet been applied to the specified target zone.
To do this, specify the global zone on the SET command and the target zone you want to check on the NOAPPLY operand.
See which SYSMODs have been accepted into a particular distribution zone but have not yet been applied to one of these zones:
- Its related target zone
- The target zone specified on NOAPPLY
To do this, specify the desired distribution zone on the SET command and take one of these actions:
- To check for SYSMODs that have not been applied to the related target zone, specify NOAPPLY without a zone name.
- To check for SYSMODs that have not been applied to a particular target zone, specify NOAPPLY with the appropriate target zone name.
Compare which SYSMODs are applied to two target zones.
To do this, specify one target zone on the SET command and the other on the NOAPPLY operand. SMP/E lists the SYSMODs that have been applied to the set-to zone but not to the NOAPPLY zone.

For more information, see Examples.

Note:

NOAPPLY can also be specified as NOAPP.
If you specify either the global zone or a target zone on the SET command, you must specify a target zone on NOAPPLY.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
You can also use the REPORT SYSMODS command to compare zones and to generate the commands needed to install SYSMODs in the zone where they are not installed. See The REPORT SYSMODS command for more information.

NOSUP

indicates that SMP/E should list entries for SYSMODs that have not been superseded.

Note:

NOSUP is mutually exclusive with SUP.
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.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.

OPTIONS

indicates that SMP/E should list all OPTIONS entries or the specified OPTIONS entries.

Note: OPTIONS is allowed when the SET command specifies the global zone.

ORDER

indicates that SMP/E should list all ORDER entries in the global zone or the specified ORDER entries.

Note: ORDER is allowed when ALLZONES is specified or the SET command specifies the global zone.

PRODUCT

indicates SMP/E should list all PRODUCT entries or the specified PRODUCT entries.

Note: PRODUCT is allowed when ALLZONES is specified or the SET command specifies the global zone.

PROGRAM

indicates that SMP/E should list all program element entries or the specified program element entries.

PTFS

indicates that SMP/E should list PTF SYSMODs.

Note:

PTFS can also be specified as PTF.
When PTFS is used with APARS, FUNCTIONS, or USERMODS, SMP/E lists any SYSMOD whose type matches any one of those specified.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD has also been specified, even if it has not.

RESTORE

indicates that SMP/E should list SYSMOD entries in which the RESTORE indicator is set. These SYSMODs have been incompletely restored and are in error.

Note:

RESTORE is allowed when the SET command specifies a target zone.
RESTORE can also be specified as RES.
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.
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 list only SYSMOD entries associated with one of the specified SOURCEID values.

Note:

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.
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 example, 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
```
A given source ID can be explicitly specified only once on the source ID operand.
The same source ID cannot be explicitly specified on both the EXSRCID and SOURCEID operands.
If a source ID is specified, implicitly or explicitly, on the SOURCEID operand and also on the EXSRCID operand, all SYSMODs with that source ID are excluded from processing.
If a given SYSMOD has multiple source IDs of which at least one is specified either implicitly or explicitly on the SOURCEID operand and another 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.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
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 list all SRC entries or the specified SRC entries.

SUP

indicates that SMP/E should list entries for SYSMODs that have been superseded.

Note:

SUP is mutually exclusive with NOSUP.
Because this operand describes the type of SYSMOD to be listed, SMP/E processes it as though SYSMOD was also specified, even if it was not.
If no SYSMOD types are specified, all eligible SYSMODs are included. To process specific types of SYSMODs, you must specify the desired SYSMOD types.
To list "dummy" entries for superseded SYSMODs (entries for SYSMODs that were superseded but not installed), do not specify a SYSMOD type operand. No SYSMOD type is associated with such entries.

SYSMODS

indicates that SMP/E should list all SYSMOD entries or the specified SYSMOD entries.

You can limit which SYSMOD entries are listed by coding one or more of the following SYSMOD qualifier operands:

APARS, FUNCTIONS, PTFS, or USERMODS
BYPASS
DELETE
ERROR
EXSRCID
FORFMID
HOLDERROR, HOLDFIXCAT, HOLDSYSTEM, or HOLDUSER
NOACCEPT
NOAPPLY
NOSUP or SUP
RESTORE
SOURCEID

For the operands shown on separate lines, SMP/E lists only SYSMOD entries that meet all the specified criteria. For the operands shown on the same line, SMP/E lists SYSMOD entries that meet any one of the specified criteria. For example, the following commands list all APAR SYSMODs that were previously installed and subsequently have been superseded:

SET      BDY(TGT1)      /* set to target zone       */.
LIST     SYSMOD         /* list SYSMODs             */
         APAR           /* that are APARs           */
         SUP            /* and are superseded       */.

On the other hand, these commands list APAR or function SYSMODs that were previously installed and subsequently have been superseded:

SET      BDY(TGT1)      /* set to target zone       */.
LIST     SYSMOD         /* list SYSMODs             */
         APAR           /* that are APARs           */
         FUNCTION       /*      or functions        */
         SUP            /* and are superseded       */.

You can expand the information listed for SYSMOD entries by coding one or more of the following operands:

HOLDDATA
MCS

Note:

SYSMODS can also be specified as SYSMOD.
If any of the SYSMOD qualifier operands (other than HOLDDATA or MCS) are specified without the SYSMOD operand, SMP/E assumes that you want the SYSMOD entries listed and, therefore, processes as if SYSMOD was also specified.
When either MCS or HOLDDATA is specified without a name list on the same LIST command as the SYSMOD operand, SMP/E assumes you want the or HOLDDATA only for those SYSMOD entries that are listed, not all the MCS and HOLDDATA entries. If you want to list all the MCS or HOLDDATA entries, use the LIST command with the MCS or HOLDDATA operand, but without the SYSMOD operand and without any of the previously identified SYSMOD qualifier operands.

TARGETZONE

indicates that SMP/E should list the TARGETZONE entry.

Note:

TARGETZONE is allowed when the SET command specifies a target zone.
TARGETZONE can also be specified as TZONE.
The XZLINK(DEFERRED) value is displayed only when the TARGETZONE entry contains TIEDTO records.

USERMODS

indicates that SMP/E should list USERMOD SYSMODs.

Note:

USERMODS can also be specified as USERMOD.
When USERMODS is used with APARS, FUNCTIONS, or PTFS, SMP/E lists any SYSMOD whose type matches any one of those specified.
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.

UTILITY

indicates that SMP/E should list all UTILITY entries or the specified UTILITY entries.

Note: UTILITY is allowed when the SET command specifies the global zone.

XREF

generates cross-reference information appropriate to the entry type being listed. Table 2 shows the information included for each entry type:

Table 2. XREF information for each type of entry
Entry type	XREF information
ASSEM entries	A list of all macros whose MAC entry indicates that this module should be reassembled
Element entries	A history of all SYSMODs affecting this element
LMOD entries	A list of all MOD entries that are linked or copied to this load module
SYSMOD entries	A list of all SYSMODs specifying this SYSMOD on the ++VER DELETE operand A list of all SYSMODs specifying this SYSMOD on the ++VER NPRE operand A list of all SYSMODs specifying this SYSMOD on the ++VER PRE operand A list of all SYSMODs specifying this SYSMOD on the ++VER REQ operand A list of all SYSMODs specifying this SYSMOD on the ++VER SUP operand A list of all SYSMODs specifying this SYSMOD on the ++VER VERSION operand A list of all SYSMODs specifying this SYSMOD on the ++IF REQ operand

Note: SMP/E uses extra time and more storage to generate the additional data requested by the XREF operand.

XZLMODP

indicates that SMP/E should list 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:

XZLMODP is allowed only when the SET command specifies a target zone.
The appropriate MOD entries are listed, regardless of whether the MOD operand was specified on the LIST command.
If both MOD and XZLMODP are specified, only MODs with cross-zone subentries are listed. If a list of MODs and XZLMODP is specified, all the specified MODs, as well as all the MODs with cross-zone subentries, are listed.

XZMODP

indicates that SMP/E should list LMOD entries for all load modules containing modules from a different target zone. (The LMOD entries for these load modules contain XZMODP subentries.)

Note:

XZMODP is allowed only when the SET command specifies a target zone.
The appropriate LMOD entries are listed regardless of whether the LMOD operand was specified on the LIST command.
If both LMOD and XZMODP are specified, only LMODs with cross-zone subentries are listed. If a list of LMODs and XZMODP is specified, all the specified LMODs, as well as all the LMODs with cross-zone subentries, are listed.

ZONESET

indicates that SMP/E should list all ZONESET entries or the specified ZONESET entries.

Note: ZONESET is allowed when the SET command specifies the global zone.

For additional information about listing a specific entry type, see the subtopic for that entry in the "SMP/E data set entries" topic in SMP/E for z/OS Reference. The description of the data in the entry, as well as examples for using the LIST command, are contained there.