- ALIAS
- specifies the alias names for the data element in both the target
and distribution libraries.
You can use ALIAS when data elements
of the same type must be defined in the same zone and must have the
same name for programming access. In this case, you can specify the
common name on ALIAS and a unique name as the data element name.
- DELETE
- indicates that the element and all of its alias names are to be
removed from the target libraries, the distribution libraries, and
the SMP/E data sets.
Note: - DELETE is mutually exclusive with all other operands except DISTLIB
and VERSION.
- If the element statement is in a base function, you may want to
use the DELETE operand on the ++VER MCS to delete the previous release,
rather than on the element statement to delete a specific element.
- Specification of the DELETE operand results in all alias names
of the data element being deleted along with the data element identified.
- DISTLIB
- specifies the ddname of the distribution library for the data
element.
Note: - DISTLIB must be specified if the element has
not been previously recorded on the target zone or distribution zone.
- If a data element entry already exists in the target zone or distribution
zone and the value currently in that entry does not match that specified
in the DISTLIB operand, the SYSMOD is not applied or accepted.
- element
- specifies the type of element. Table 1 shows the MCSs used for
the various element types.
- FROMDS
- identifies the partitioned data set that contains this element.
Note: The
FROMDS operand and its DSN, NUMBER, VOL, and UNIT suboperands are
included in the MCS generated by the BUILDMCS command. IBM® does not intend the FROMDS operand to be
used in manually coded MCS.
- DSN
- specifies the dsname of the FROMDS data set. The specified data
set name must conform to standard data set naming conventions and
cannot contain parentheses. The maximum length of the entire name
is 44 characters (including the periods).
- NUMBER
- specifies a number that SMP/E is to use when assigning a name
to the SMPTLIB data set associated with this FROMDS data set. (This
is similar to the way the relative file number is used in RELFILE
processing.)
- VOL
- specifies, for an uncataloged data set, the volume serial number
of the volume containing the FROMDS data set. If specified, this volume
identifier must be from 1 to 6 alphanumeric characters.
VOL may
be omitted for a cataloged data set.
- UNIT
- specifies, for an uncataloged data set, the UNIT type containing
the FROMDS data set. If specified, the UNIT value must be from 1 to
8 characters and must conform to standard UNIT naming conventions.
SMP/E accepts any nonblank characters specified between the open and
close parentheses, up to a maximum length of 8.
UNIT may be omitted
for a cataloged data set.
Note: FROMDS is mutually exclusive with
DELETE, RELFILE, and TXLIB.
- name
- specifies the name of the element to be replaced. The name can
contain any alphanumeric characters and $, #, @, or hex C0.
- RELFILE
- specifies which relative file associated with the SYSMOD contains
this element. This operand is required if you provide the element
in RELFILE format, rather than inline or in a TXLIB data set.
Note: RELFILE
is mutually exclusive with DELETE, FROMDS, and TXLIB.
- RMID
- specifies the last PTF that replaced this data element.
This operand can be used only in a service-updated function, and the
specified PTF must be integrated into the function.
Note: RMID is
mutually exclusive with DELETE.
- SYSLIB
- specifies the ddname of the target library for the specified element.
Note: SYSLIB
is mutually exclusive with DELETE.
- TXLIB
- specifies the ddname of the partitioned data set containing the
element. This operand is required if the element is provided in a
TXLIB data set rather than inline or in RELFILE format.
Note: - SMPTLIB cannot be used as a value on the TXLIB operand.
- TXLIB is mutually exclusive with DELETE, FROMDS, and RELFILE.
- VERSION
- specifies one or more function SYSMODs that currently contain
the element. The function containing the data element statement takes
over ownership of the element from the specified functions.
When VERSION is
specified on an element statement, it overrides any VERSION operand
values specified on the ++VER MCS.