Statements/Parameters for DEVSUPxx

3

Specifies that new AL labels are written as ISO/ANSI/FIPS Version 3. The current version 3 and 4 labels are preserved.

4

Specifies that new AL labels are written as ISO/ANSI Version 4. The current version 3 and 4 labels are preserved.

FORCE3

Specifies that all AL labels are forced as ISO/ANSI/FIPS Version 3, including any current version 3 and 4 labels.

FORCE4

Specifies that all AL labels are forced as ISO/ANSI Version 4, including any current version 3 and 4 labels.

YES

Specifies that data is to be stored in a compacted format on each 3480, 3490, or 359x tape subsystem, unless overridden by the user.

NO

Specifies that data is not to be stored in a compacted format on each 3480, 3490 or 359x tape subsystem, unless overridden by the user. If no installation default is provided through the DEVSUPxx member, and storing data in a compacted format is not explicitly requested on a DD statement, dynamic allocation request, the MOD=parameter on the JES3 *CALL, DJ command, or DCB macro, then the system uses the compaction default for the device. For example, the compaction default for a 3480 is NOCOMP. To determine the compaction default for a particular device, see the planning or migration documentation that accompanies the device.

YES

Specifies that data is to be stored in a compacted format on each 3480, 3490, or 359x tape subsystem, unless overridden by the user.

NO

Specifies that data is not to be stored in a compacted format on each 3480, 3490 or 359x tape subsystem, unless overridden by the user. If no installation default is provided through the DEVSUPxx member, and storing data in a compacted format is not explicitly requested on a DD statement, dynamic allocation request, the MOD=parameter on the JES3 *CALL, DJ command, or DCB macro, then the system uses the compaction default for the device. For example, the compaction default for a 3480 is NOCOMP. To determine the compaction default for a particular device, see the planning or migration documentation that accompanies the device.

The meanings for the keyword values are described in z/OS DFSMSdfp Utilities. The default is no code in the DFA, which means that IEBGENER assumes SDB=INPUT.

NON_VSAM_XTIOT=

NO

Disables support for XTIOT, uncaptured UCB, and DSAB control blocks that reside above the 16-MB line for data sets that use BSAM, QSAM, or BPAM. The default value for NON_VSAM_XTIOT is NO.

YES

Enables support for XTIOT, uncaptured UCB, and DSAB control blocks that reside above the 16-MB line for data sets that use BSAM, QSAM, or BPAM.

This controls whether the access method OPEN macro supports these three options of the data set dynamic allocation function. Set NO if you are concerned that some programs, including installed products, might not correctly handle these options. You can set YES if all programs that might process data sets that were dynamically allocated by other programs can handle these options. Setting YES but not using these options has no effect on virtual storage or performance.

PPRCSUM

Enables or disables the PPRCSUM feature of the Device Manager. Note that if the PPRCSUM feature is enabled or disabled after IPL, one device in every control unit must be varied online to activate the feature.

DISABLE(PPRCSUM)

When PPRCSUM feature is disabled, PPRC suspend notification for individual devices is displayed in message IEA494I. The default value for PPRCSUM is DISABLE(PPRCSUM).

ENABLE(PPRCSUM)

Enables the PPRCSUM feature of the Device Manager, which means using message IEA075I instead of IEA494I to report devices that transition to PPRC suspended state. The PPRCSUM feature significantly reduces the volume of messages which are written to the console when devices in a PPRC relationship are suspended. If you enable PPRCSUM, the system will issue an IEA075I message every 5 seconds or when the last device in the control unit has suspended to summarize the PPRC state for all devices in the control unit. This continues until all PPRC state transitions have completed.

Warning: If GDPS® or other PPRC monitoring software is active, make sure the appropriate version of this software is installed before enabling PPRCSUM.

OCE_ABEND_DESCRIP=

Note: As of z/OS® V1R13 with the installation of APAR OA37957, the enablement of this function is now provided through the MPFLSTxx parmlib member. For details, refer to Controlling verbose message production.

NO

Specifies that OPEN, EOV and CLOSE abend messages will not include a descriptive text for the associated numeric abend and numeric return code. To diagnose and respond to the messages, it may be necessary to look up the codes using the z/OS MVS™ System Messages books or the LookAt tool. The default value for OCE_ABEND_DESCRIP is NO.

YES

Specifies that abend messages for selected OPEN, EOV and CLOSE determinant errors include descriptive text for the associated numeric abend code and numeric return code. This option can eliminate the need to look up the meanings of the abend and reason codes returned in the messages in the z/OS MVS System Messages books or the LookAt tool.

REFVTOC

Enables or disables the automatic REFVTOC function of the Device Manager:

ENABLE(REFVTOC)

When the REFVTOC feature is enabled and the system detects a volume expansion, the Device Manager causes the volume VTOC to be rebuilt. This allows the newly added space on the volume to be used by the system.

DISABLE(REFVTOC)

When the REFVTOC feature is disabled and the system detects a volume expansion, the system issues message IEA019I, but the VTOC is not rebuilt. An ICKDSF Batch job must be submitted to rebuild the VTOC before the newly added space on the volume can be used. The default value for REFVTOC is DISABLE(REFVTOC).

NO

Disables the Easy-Tier Copy Temperature function for software-defined storage. This disables Query/Set Temperature functions that is used to direct data placement in the Disk Controller. NO is the default.

YES

Enables the Easy-Tier Copy Temperature function for software-defined storage. This enables Query/Set Temperature functions that is used to direct data placement in the Disk Controller.

IEA253I DEVSUP EASY-TIER FOR SOFTWARE DEFINED STORAGE

If EASYTIERHINTS=NO is specified followed by issuing the SET DEVSUP=xx command to refresh the PARMLIB member, the IEA253I message is not logged.

If the Easy-Tier Copy Temperature function for software-defined storage is enabled by setting EASYTIERHINTS=YES in the DEVSUPxx member of the PARMLIB followed by an IPL of the system, the EASY-TIER FOR SOFTWARE DEFINED STORAGE status will be seen in the output of the F DEVMAN,REPORT console command. Refer to z/OS MVS System Commands for usage of the F DEVMAN,REPORT console command.

If the Easy-Tier Copy Temperature function for software-defined storage is disabled by issuing SET DEVSUP=XX with EASYTIERHINTS=NO in the PARMLIB member, the EASY-TIER FOR SOFTWARE DEFINED STORAGE status will not be seen in the output of the F DEVMAN,REPORT command.

ALLMEDIATY

Specifies that dataclass media policies are enforced for all stand-alone, non-specific mounts.

MEDIA5PLUS

Specifies that dataclass media policies are enforced for all stand-alone, non-specific mounts for any of the 3592 tape cartridge media types.

NEVER

Disables expiration date processing when opening a non-VSAM data set on DASD. Set the parameter to NEVER if you want OPEN to disable expiration date processing when opening all non-VSAM data sets on DASD for output processing. Specifying NEVER eliminates the message IEC507D and the optional associated message IEC108I for all non-VSAM data sets on DASD. Therefore, any authorized user can open an expiration date protected non-VSAM DASD data set for output without requiring the operator to allow access.

ALWAYS

Normal expiration date processing will occur when opening a non-VSAM data set on DASD. Set the parameter to ALWAYS to allow OPEN to process expiration date processing as it normally does, that is, by issuing message IEC507D and the optional associated TSO/E message IEC108I when any attempt is made to open for output a data set on DASD for which the expiration date has not yet occurred. The default value for EXPIRATION_MESSAGE is ALWAYS.

Note: This keyword has no affect for data sets on magnetic tape even if you specify NEVER.

YES

Specifies that the allocation assist support (available with the TS7700 Virtualization Engine) is being enabled for usage with JES3. With this support enabled, scratch allocations can be directed (through TS7700's management class policies) to specific clusters (distributed libraries) and specific allocations are directed to a preferred list of clusters (distributed libraries) returned by the library.

Before enabling this support refer to the set-up steps in the “JES3 Considerations” section in z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries. If you do not perform the setup before enabling this support, jobs may incur abends.

NO

Specifies that the allocation assistance support (available with the TS7700 Virtualization Engine) is not to be used by JES3. JES3 scratch and specific allocation requests will continue to be directed to the single library image referred to as the composite library with no knowledge of the underlying clusters (distributed libraries). NO is the default.

NO

Disables Incremental FlashCopy Version 2 function. Multiple Incremental FlashCopy targets are not allowed.

YES

Enables the Incremental FlashCopy Version 2 function. Multiple Incremental FlashCopy targets are allowed.

IEA253I DEVSUP MULTIPLE INCREMENTAL FLASHCOPY:
                 CHANGE RECORDING V2

If MULTINCRFLC=NO is specified, followed by using the SET DEVSUP command to refresh the DEVSUPxx parmlib member, the IEA253I message is not logged.

If Incremental FlashCopy Version 2 is enabled by installing the enablement PTF, the output of the F DEVMAN,REPORT console command includes MULTIPLE INCREMENTAL FLASHCOPY: CHANGE RECORDING V2. For information about the F DEVMAN,REPORT console command, refer to the topic about MODIFY DEVMAN in z/OS MVS System Commands.

ENABLE(PPRCMT)

When the PPRCMT feature is enabled, support is available to allow a device to be the primary of more than one PPRC pair.

DISABLE(PPRCMT)

When the PPRCMT feature is disabled, functionality will be in single target mode.

ENABLE(REFUCB)

When the REFUCB feature is enabled, the system automatically updates the UCB when device support software detects that a DSS COPY, RESTORE, or ICKDSF REFORMAT NEWVTOC operation has changed either the volser or the VTOC location. In the case of a volser or VTOC location change, the system invokes the DEVMAN REFUCB service on each system in the sysplex that has REFUCB enabled.

• If the device is ONLINE, REFUCB issues a VARY ONLINE, UNCONDITIONAL command, which updates both the volser and VTOC location in the UCB.
• If the device is OFFLINE, no action is taken.

DISABLE(REFUCB)

When the REFUCB feature is disabled, the system does not refresh the UCB when a DSS COPY, RESTORE or ICKDSF REFORMAT NEWVTOC operation has changed either the volser or the VTOC location. The default value for REFUCB is DISABLE(REFUCB).

YES

Enables tape authorization checks in the DATASET class but without DSTYPE=T. All tape data set names created are RACF-protected.

DSTYPE=T indicates to RACF® that the check is for data set on a tape volume and that special RACF tape data set and a tape volume processing is to be performed. Without DSTYPE=T RACF authorization checking considers only profiles in the DATASET class.

The system uses the data set name specified in the allocation or JCL to check your authorization to read or write the specified file.

In addition, the system determines the RACF erase-on-scratch setting from the RACF profile and passes it to your tape management system.

Use this option only when you have a tape management system, such as DFSMSrmm, installed and actively checking that the 44 character data set name specified by the user matches the data set name on tape. Without a tape management system, tape data set open processing can only validate the last 17 characters of the data set name against the tape volume labels.

When you request bypass label processing (BLP) and the mounted volume uses standard labels, OPEN issues the authorization check that the user is authorized to use BLP. This processing uses the existing ICHBLP resource in the RACF FACILITY class. When you specify TAPEAUTHDSN=YES only, it replaces the check that RACF makes as part of tape volume authorization checking.

NO

Indicates that OPEN processing to issue RACROUTEs based on the options set in RACF such as SETROPTS TAPEDSN and SETROPTS CLASSACT(TAPEVOL). The default value for TAPEAUTHDSN is NO.

YES

Enables additional tape authorization checks in the DATASET class for existing files on the same tape volume when any other file on the tape volume is opened. This function depends on the tape management system returning the 44 character data set name and data set sequence number to OPEN/EOV through the IFGTEP during the Volume Mount exit Volume Security function; if no data set name is returned by the tape management system, processing is as if this keyword had not been specified.

Although intended to enable an additional authorization check for the first data set when any other data set on the tape volume is opened, the implementation allows your tape management system to request one or more additional authorization checks when any data set on a tape volume is opened. Each additional data set name and data set sequence number returned results in an additional RACROUTE. Do not use this function unless you have a tape management system and it can return a data set name and data set sequence number. A data set sequence number is the label number normally specified in the JCL LABEL keyword and stored in the catalog.

When TAPEAUTHDSN=YES is in use, any additional RACROUTE matches that issued for TAPEAUTHDSN except for the data set name and data set sequence number. Otherwise TAPEAUTHF1 uses a RACROUTE that matches that used for SETROPTS TAPEDSN. When neither TAPEAUTHDSN nor SETROPTS TAPEDSN is in use, TAPEAUTHF1 support is not provided.

NO

Disables additional tape authorization checks in the DATASET class for existing files on the same tape volume when any other file on the tape volume is opened. The default value is NO.

ALLOW

Allows accessing of data sets that are not protected by a security profile. 'RC4' refers to the return code value of 4 returned from SAF as a result of the RACROUTE issued by OPEN/CLOSE/EOV. A return code of 4 in general means that the resource is not protected.

FAIL

Denies accessing of data sets that are not protected by a security profile. TAPEAUTHRC4=FAIL and TAPEAUTHDSN=YES together ensure that all tape data set names created including temporary names generated by the tape system are RACF-protected. The default value is FAIL.

Use this keyword to control PROTECTALL processing for tape data sets. This applies to the results of RACROUTE processing when both TAPEAUTHDSN=YES and when TAPEAUTHF1=YES are specified.

WARN

Allows accessing of data sets that typically cannot be accessed. RACF issues an ICH408I message to indicate why access is not allowed; however OPEN/EOV allows access.

FAIL

Denies accessing of data sets that typically cannot be accessed. The default value is FAIL.

• An application program uses the large block interface (LBI) of BSAM or QSAM to open a tape data set for output without DISP=MOD. Check the information for the program; if its maximum block size is 32760 or less, or it cannot write to tape, the program probably does not use the LBI.
• The BLKSIZE (block size) value is omitted from all sources.
• The DD statement or dynamic allocation equivalent and the data class do not specify a BLKSZLIM value.

Restriction: DFSMSdss only supports BLKSZLIM of 65,520 and higher.

An application program that uses EXCP can take this value from the DFA.

If you code K, M, or G at the end of the number, the system multiplies the number by 1024, 1,048,576 or 1,073,741,824 respectively. The minimum values are 32760 when specified in bytes, 32K when specified in kilobytes, 1M when specified in megabytes, and 1G when specified in gigabytes. The maximum values are 2147483648, 2097152K, 2048M and 2G. These maximum block size values are much larger than the system actually supports for BLKSIZE. Coding a large value, however, allows the system to choose the largest optimal block size for the device.

If the Label Anomaly exit sets return code 12, it is honored and in all cases it fails the request, overriding the DEVSUPxx setting.

ALLOW

Use this setting to allow applications to process multi-volume tape data sets even when the volume set is incomplete or in the wrong sequence.

FAIL

Use this setting to prevent applications from processing multi-volume tape data sets when the volume set is incomplete or in the wrong sequence.

When a request is failed, either by the Label Anomaly exit return code 12, or by the FAIL option, the System Completion Codes are: 413-58 (OPEN RDBK), 413-5C (OPEN FIRST), 637-B4 (EOV OUTSEQ), and 637-B8 (EOV LAST).

DFSMSrmm attempts to recover from errors that are noted in the label anomaly exit using the volume sequence information that is recorded in the DFSMSrmm control data set (CDS). Based on information returned by DFSMSrmm, OPEN and EOV processing attempts to resolve the error by updating the volume list in the job file control block (JFCB) and any JFCB extensions.

Tape users can bypass the system multivolume tape label anomaly processing by specifying OPTCD=B in the JCL. See the topic Determining Volume Switch in z/OS DFSMS Using Magnetic Tapes, z/OS MVS JCL User's Guide, and z/OS MVS JCL Reference for details of the considerations using OPTCD=B.

The tape application can optionally recover from a tape label anomaly failure by providing a DCB abend exit for the applications’ DCB. When the application DCB abend exit requests recovery, the missing or out of sequence volume condition is ignored.

YES

Specifies that tape cartridges written at track capacities that the drive is not capable of reading (for example, a 36-track cartridge on a D/T3480, or a 256-track cartridge on a D/T3590 Model B1x), be relabeled at the device-capable track capacity by the OPEN or EOV label editor routines. This re-label editor option is permitted only if the user is RACF-authorized to the volume. The volume serial number that is passed to RACF is obtained from the VOLID mark written on the cartridge by the device, and placed in the sense data.

NO

Specifies that tape cartridges written at track capacities that the drive is not capable of reading (for example, a 36-track cartridge on a D/T3480, or a 256-track cartridge on a D/T3590 Model B1x), are not allowed to be re-labeled. Attempts to re-label the cartridges are rejected when RACF protection for tape volumes is active. If no installation default for the VOLID facility VOLNSNS is provided by using the DEVSUPxx member, the system assumes VOLNSNS=NO.