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

old-name
specifies the name of the zone to be renamed.
Note:
  1. The specified name cannot be GLOBAL.
  2. The old zone name cannot be the same as the new zone name.
TO
specifies the new name for the zone. This operand is required.
Note:
  1. The new zone name cannot be GLOBAL.
  2. The new zone name cannot be the same as the old zone name.
NEWDATASET
indicates that the zone to be renamed and the SMPCSI containing it are not yet defined by a zone index in the global zone. (For example, there might be a zone index for the old zone name, but not for the data set specified by NEWDATASET, or there might not be any zone index at all for the old zone name.) SMP/E will rename the zone in the indicated data set, and then create a zone index for the new zone name and the SMPCSI data set containing that zone.
You must specify either NEWDATASET or SAMEDATASET.
Note:
  1. The indicated data set must be an existing SMPCSI containing the zone to be renamed. ZONERENAME does not create the SMPCSI data set for you.
  2. The data set must not be the same as the one currently defined in the zone index for the old zone name.
  3. The data set name must conform to the naming conventions for a CSI data set and therefore must have a low-level qualifier of .CSI. The data set name can contain no more than 44 characters.
  4. NEWDATASET tells SMP/E to rename only the zone in the indicated data set. It does not rename the SMPCSI data set containing that zone. You cannot use the ZONERENAME command to rename SMPCSI data sets.
OPTIONS
specifies the name of the OPTIONS entry to use for processing the renamed zone. The OPTIONS subentry in the zone definition of the RENAMED zone is set to the specified name. If OPTIONS is not specified, the OPTIONS subentry in the definition of the renamed zone is not changed.
RC
changes the maximum return codes allowed for the specified commands. These return codes determine whether SMP/E can process the ZONERENAME command.
Before SMP/E processes the ZONERENAME command, it checks whether the return codes for the specified commands are less than or equal to the values specified on the RC operand. If so, SMP/E can process the ZONERENAME command. Otherwise, the ZONERENAME command fails. For more information about the RC operand, see Processing the SMP/E RC operand.
Note:
  1. The RC operand must be the last operand specified on the command.
  2. If you do specify the RC operand, return codes for commands not specified do not affect processing for the ZONERENAME command. Therefore, if you use the RC operand, you must specify every command whose return code you want SMP/E to check.
RELATED
specifies the name of the target or distribution zone to which the renamed zone is related. The RELATED subentry in the zone definition of the renamed zone is set to the specified name. If RELATED is not specified, the RELATED subentry in the renamed zone's definition is not changed.
SAMEDATASET
indicates that the zone to be renamed is already defined by a zone index in the global zone, and is to be renamed in its current data set. The zone index is be changed to indicate the new zone name.
You must specify either SAMEDATASET or NEWDATASET.
Note: SAMEDATASET is mutually exclusive with TOTYPE(TARGET).
TOTYPE(TARGET)
indicates that the zone to be renamed is currently a distribution zone in a copy of an SMP/E CSI data set and is to be changed to a target zone. After the rename operation, the GLOBALZONE ZONEINDEX record indicates that this is now a target zone and the zone definition for the zone is updated to indicate that it is a target zone.
Note:
  1. TOTYPE is mutually exclusive with SAMEDATASET.
  2. TOTYPE is needed only if you are changing a target zone to a distribution zone. For example, suppose you did a system generation and copied the distribution zone to initialize the target zone. You could use the ZONERENAME command to rename the copied distribution zone and change the type to target.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014