Changing parameters at dynamic unallocation
With your dynamic unallocation request, you can include text units to change a data set's or z/OS® UNIX file's parameters as it is being deallocated. If your request is in the form of verb code 02, key 8, the changes are honored when the data set or z/OS UNIX file is actually released, unless they have been overridden in the meantime. If your dynamic unallocation request is in the form of verb code 02, key 7, the changes take effect immediately.
The parameters that can be changed at deallocation are:
- Output class — see Overriding SYSOUT class specification - Key = '0018'
- HOLD/NOHOLD parameters — see Overriding SYSOUT nohold specification - Key = '000A' and Overriding SYSOUT hold queue specification - Key = '0059'
- Remote work station destination — see Overriding SYSOUT remote workstation specification - Key = '0058':
- For a JES2 environment SYSOUT data can be routed to:
- Remote workstation
- Node
- Special local
- Userid
- For a JES3 environment SYSOUT data can be routed to:
- ANYLOCAL
- JES3-defined device name
- Device number
- JES3-defined symbolic group name
- NJE node
- For a JES2 environment SYSOUT data can be routed to:
- Userid — see Overriding SYSOUT user ID specification - Key = '0063'Note: For a JES2 environment only.
- Data set or z/OS UNIX file disposition — see z/OS UNIX overriding file disposition specification - Key = '801A'
- When the SYSOUT output is to be printed (JCL DD statement SPIN parameter) — see z/OS UNIX file path specification - Key = '8017'.
Allocation disposition cannot be overridden for the following (see Overriding disposition specification - Key = '0005'):
- Passed data sets
- VSAM data sets, when SMS is not active
- System-named data sets, except for subsystem data sets.
You cannot delete members of partitioned data sets with a disposition of DELETE; the system deletes the entire data set. An overriding disposition of DELETE for data sets allocated as shared is not valid; the system fails the overriding disposition request.