Statements and parameters for DEVSUPxx

3

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

4

Specifies that new AL labels are written as ISO/ANSI Version 4. The Version 3 and 4 labels that are current 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.

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.

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.

{HPF_FMTWRITE|HPF_IMBEDDEDLR|HPF_TTEDCW}

Enables or disables a zHPF feature. Use the option to disable a zHPF feature only at the direction of the system programmer or IBM service support.

DISABLE(HPF_FMTWRITE)

Disable the zHPF Format Writes support.

ENABLE(HPF_FMTWRITE)

Enable the zHPF Format Writes support.

DISABLE(HPF_IMBEDDEDLR)

Disable the zHPF Imbedded Locate Record support.

ENABLE(HPF_IMBEDDEDLR)

Enable the zHPF Imbedded Locate Record support.

DISABLE(HPF_TTEDCW)

Disable the zHPF TCA Extension support.

ENABLE(HPF_TTEDCW)

Enable the zHPF TCA Extension support.

Default: ENABLE(HPF_FMTWRITE|HPF_IMBEDDEDLR|HPF_TTEDCW)

TCTCOMPRESSION

Enables or disables the transparent cloud tiering compression feature.

ENABLE(TCTCOMPRESSION)

Enables the transparent cloud tiering compression feature.

DISABLE(TCTCOMPRESSION)

Disables the transparent cloud tiering compression feature.

Default: DISABLE(TCTCOMPRESSION)

AOM496I

Enables or disables the issuing of the AOM496I status message on the console for transparent cloud tiering operations.

ENABLE(AOM496I)

When the AOM496I feature is enabled, the AOM496I status message for transparent cloud tiering operations is issued to the console.

DISABLE(AOM496I)

When the AOM496I feature is disabled, the AOM496I status message for transparent cloud tiering operation is not issued to the console.

Default: DISABLE(AOM496I)

PPRCMT

Enables or disables the Multi-Target PPRC support.

DISABLE(PPRCMT)

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

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.

Default: DISABLE(PPRCMT)

PPRCSUM

Enables or disables the PPRCSUM feature of the Device Manager.

• If the PPRCSUM feature is enabled or disabled after IPL, one device in every control unit must be varied online to activate the feature.
• Because the PPRCSUM feature gets disabled after an HCD dynamic activation, one device in every control unit must be varied online to activate the feature after an ACTIVATE IODF.

DISABLE(PPRCSUM)

When the PPRCSUM feature is disabled, PPRC suspends notification for individual devices is displayed in message IEA494I.

ENABLE(PPRCSUM)

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

If GDPS or other PPRC monitoring software is active, make sure that the appropriate version of this software is installed before you enable PPRCSUM.

Default: DISABLE(PPRCSUM)

REFUCB

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

DISABLE(REFUCB)

The system does not refresh the UCB when a DSS COPY, RESTORE, or ICKDSF FLASHCPY, INIT or REFORMAT operation has changed either the volume serial number (VOLSER) or the volume table of contents (VTOC) location.

ENABLE(REFUCB)

The system automatically updates the UCB when the device support software detects that a DSS COPY, RESTORE, or ICKDSF FLASHCPY, INIT, or REFORMAT operation has changed either the VOLSER or VTOC location. The DEVMAN REFUCB service is invoked 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 or VTOC location in the UCB.
• If the device is OFFLINE, no action is taken.

Default: ENABLE(REFUCB)

REFUCB_FAIL = {NONE|VARYOFF_RODEV}

Specifies action to be taken when a failure occurs when refreshing the UCB.

NONE

If REFUCB_FAIL=NONE is specified in the DEVSUP member, message IEA253I is displayed and no action is taken if the REFUCB failed to update the UCB. IEA253I DEVSUP REFUCB_FAIL=NONE ACTION IS SET

VARYOFF_RODEV

If REFUCB_FAIL=VARYOFF_RODEV is specified, message IEA253I message is displayed and the device is varied offline by REFUCB issuing the VARY OFFLINE command to the device. If the device cannot be varied offline, it will be changed to a read-only volume.

REFVTOC

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

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.

ENABLE(REFVTOC)

When the REFVTOC feature is enabled and the system detects a volume expansion, the system issues message IEA019I. If the volume is online, 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.

Default: ENABLE(REFVTOC)

SSR

Enables or disables the secondary space reduction support of the Device Manager.

DISABLE(SSR)

Disables the secondary space reduction support.

ENABLE(SSR)

Enables the secondary space reduction support.

Default: ENABLE(SSR)

SUPPR_SMF19_DUMPCOND=

Enables or disables the secondary space reduction support of the Device Manager.

YES

Suppresses the generation of SMF type 19 records for the LSPACE command on dump conditioned volumes.

NO

Allows the generation of SMF type 19 records for the LSPACE command on dump conditioned volumes.

If SUPPR_SMF19_DUMPCOND=YES is specified, the following message is logged:

IEA253I SMF SUBTYPE 19 RECORDS ARE SUPPRESSED FOR LSPACE ON DUMP CONDITIONED VOLUMES

If SUPPR_SMF19_DUMPCOND=NO is specified, the following message is logged:

IEA253I SMF SUBTYPE 19 RECORDS ARE GENERATED FOR LSPACE ON DUMP CONDITIONED VOLUMES

If the keyword is not specified, no message is logged.

Default: NO

TCTCOMPRESSION

Enables or disables the transparent cloud tiering compression feature.

ENABLE(TCTCOMPRESSION)

Enables the transparent cloud tiering compression feature.

DISABLE(TCTCOMPRESSION)

Disables the transparent cloud tiering compression feature.

Default: DISABLE(TCTCOMPRESSION)

ZERO_DIR_PDS

Enables or fails the allocation of a PDS with zero directory block that is defined in the JCL. If the ZERO_DIR_PDS keyword is not specified, no message is logged during IPL.

ENABLE(ZERO_DIR_PDS)

Allow the allocation of PDS with zero directory block that is specified in the JCL explicitly or implicitly.

DISABLE(ZERO_DIR_PDS)

Fail the allocation of PDS with zero directory block that is specified in the JCL explicitly or implicitly.

Default: ENABLE(ZERO_DIR_PDS)

VTOC_USE_ZHPF

Specifies that you want the system to read or write VTOC DSCB records, using zHPF when it is available. You must have already specified ZHPF=YES on the ZHPF statement in the IECIOSxx parmlib member.

ENABLE(VTOC_USE_ZHPF)

Specifies that you want the system to read or write VTOC DSCB records, using zHPF when it is available and enabled. If you specify ENABLE(VTOC_USE_ZHPF) in either DEVSUPxx or by using the MODIFY DEVMAN command, the DFAVTOCHPF bit in the DFA control block is set on.

DISABLE(VTOC_USE_ZHPF)

Specifies that the system should not use zHPF to access the VTOC. If you specify or default to DISABLE(VTOC_USE_ZHPF) in either DEVSUPxx or by using the MODIFY DEVMAN command, the DFAVTOCHPF bit in the DFA control block is set off. CVAF will not use zHPF to access the VTOC.

ALLMEDIATY

Enforces data class media policies for all stand-alone, non-specific mounts.

MEDIA5PLUS

Enforces data class media policies for all stand-alone, non-specific mounts for any of the 3592 tape cartridge media types.

NO

For a device in PPRC relationship, Erase-On-Scratch issued a one-channel program to erase one track at a time until all tracks are erased.

YES

Erase-On-Scratch can erase up to 255 tracks in a single channel program, if the PPRC primary and secondary devices are maintained on the same level of microcode fix as shown in the following table.

Machine type	Microcode level
DS8100/DS8300	64.36.89.0
DS8700	76.31.70.0
DS8800	86.31.86.0

NO

Disables the Easy-Tier Copy Temperature function for software-defined storage. This option disables Query/Set Temperature functions that are 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 option enables Query/Set Temperature functions that are 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.

ALWAYS

Normal expiration date processing occurs when opening a non-VSAM data set on DASD. ALWAYS allows OPEN to process expiration date processing as it normally does. That is, OPEN issues 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.

Note: This keyword does not affect data sets on magnetic tape even if you specify NEVER.

NEVER

Disables expiration date processing when a non-VSAM data set on DASD is opened. 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.

NO

Disables support for Remote Pair FlashCopy for XRC environments.

YES

Enables support for Remote Pair FlashCopy for XRC environments.

At IPL, or when the SET DEVSUP=xx command is issued with FLASHCOPYTOXRC=YES in DEVSUPxx, this message is displayed:

IEA253I DEVSUP ALLOW REMOTE PAIR FLASHCOPY TO XRC

If FLASHCOPYTOXRC is not specified at all in DEVSUPxx, no messages are issued.

NO

Specifies that in a system-managed tape environment, SMS on a scratch allocation request will retain its current tape subsystem (device pool) limit of 253.

YES

Specifies that in a system-managed tape environment, SMS on a scratch allocation request can return more than 253 tape subsystems (device pools) to MVS™ Allocation. Before enabling this support, ensure that all systems in the sysplex can support the increased limit (z/OS® V2R2 or later or z/OS V1R13 and V2R1 with SMS APAR OA44354), otherwise jobs could incur abends.

For more information about tape subsystem limitations, see Tape subsystem limitation in z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.

NO

Disables the ICKDSF NODSEXIST parameter as the default for the ICKDSF INIT command. If the NODSEXIST parameter is disabled and the device contains data sets, the ICKDSF INIT command is not terminated because data sets exist.

If ICKDSF NODSEXIST=NO is specified, an IEA253I message is logged at IPL or after a SET DEVSUP=xx command is issued.

YES

Enables the ICKDSF NODSEXIST parameter to be the default for the ICKDSF INIT command. If the NODSEXIST parameter is the default and the device contains data sets other than the VTOC index data set or VVDS, the command terminates and message ICK32179I is in the job output. See Device Support Facilities (ICKDSF) User's Guide and Reference for more details.

If ICKDSF_NODSEXIST=YES is specified, an IEA253I message is logged at IPL or after a SET DEVSUP=xx command is issued.

Note: If an online INIT is attempted on a volume that has been initialized as an SMS-managed volume and data sets other than the VTOC index data set or VVDS exist, the command terminates and message ICK32177I is in the job output. See Device Support Facilities (ICKDSF) User's Guide and Reference for more details.

NO

Disables the ICKDSF VERIFYOFFLINE parameter as default. If you want to make sure that the device is offline to all host systems, you must specify the VERIFYOFFLINE parameter.

YES

Enables the ICKDSF VERIFYOFFLINE parameter to be defaulted if all the following are true:

1. UNIT parameter is specified.
2. Storage control microcode support exists.
3. z/OS software support exists.
4. Device is not a minidisk.

If ICKDSF_VERIFYOFFLINE=YES is specified, an IEAV253I DEVSUP ENABLED ICKDSF VERIFYOFFLINE PARAMETER DEFAULT message is also logged. If the keyword is not specified, no message is logged.

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).

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 setup 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 might incur abends.

xNN

A number from x01 - x030 equivalent to decimal 1 - 48 that indicates how many Logical Record Erase channel command words (CCWs) can be chained per channel program for the Erase-On-Scratch function. Each Logical Record Erase CCW can erase up to 255 tracks.

The LRECCW_PER_EOSCP option is provided in V2R1 for toleration purposes only. It does not change the number of Erase commands. For V2R2 and later releases, it can be used to specify the number of Erase Commands that can be chained per channel program for the Erase-On-Scratch function.

NO

Disables the Multiple Incremental FlashCopy or the Change Recording Version 2 function.

YES

Enables the Multiple Incremental FlashCopy or the Change Recording Version 2 function.

If Multiple Incremental FlashCopy is enabled by installing the enablement OA45412 PTF followed by an IPL of the system, the MULTIPLE INCREMENTAL FLASHCOPY: CHANGE RECORDING V2 status will be seen in the output of the F DEVMAN,REPORT console command. Refer to z/OS MVS System Commands for information about the F DEVMAN,REPORT console command.

If Multiple Incremental FlashCopy is disabled by issuing SET DEVSUP=XX with MULTINCRFLC=NO in the DEVSUPxx parmlib member, the MULTIPLE INCREMENTAL FLASHCOPY: CHANGE RECORDING V2 status is not in the output of the F DEVMAN,REPORT command.

NO

Disables support for XTIOT, uncaptured UCB, and DSAB control blocks that reside above the 16-megabyte 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-megabyte line for data sets that use BSAM, QSAM, or BPAM.

This keyword is checked for syntax but otherwise it is obsolete and has no effect. Its original purpose was to specify whether most error messages in the OPEN/CLOSE/EOV component would have additional information to explain the error.

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, you might have to look up the codes.

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 that are returned in the messages.

NO

Specifies that the PPRC/Metro Mirror HyperSwap configuration is not symmetrical. This indicates that the same volume address is the not used to identify primary and secondary volumes in a pair relationship.

YES

Specifies that the PPRC/Metro Mirror HyperSwap configuration is symmetrical. This indicates the same volume address is used to identify both primary and secondary volumes in a pair relationship.

A symmetrical logical configuration is a duplicate configuration where the Metro Mirror primary and secondary disk subsystems are configured with the same Logical Subsystem number (LSS) and Channel Connection Address (CCA) pairs. That is the PPRC primary and secondary devices have the same LSS and CCA in the local and remote storage controllers. These configurations are believed to be common as most clients configure Metro Mirror primary and secondary disk subsystems identically. An asymmetrical configuration has logical LSS and CCA numbers different between the local and remote sites.

YES

If CVAF returns a STAT011 error to its caller, the VTOC index is not disabled.

If STAT011_PRESERVE_INDEX=YES and RETRY(STAT011) are both specified in the DEVSUPxx member, DADSM allocation performs the following actions without disabling the VTOC index:

1. Detect the failure that is associated with IEC608I message and performs an SVC dump of DADSM with of the following diagnostic codes:
   • 0820040B
   • 0853040B
   • 0854040B
   • 0855040B
   Those codes occur when the common VTOC access facility (CVAF) sets the status x0B(STAT011) while using an orphan Format-3 DSCB as a free Format-0 DSCB. If this situation is detected, the dump is not issued until later during VTOC validation process.
2. Use the VTOC validation function to determine the status of the orphan Format-3 DSCBs and other VTOC conditions. Examples of VTOC conditions are VTOC NOT CONVERTED, INCORRECT EXTENTS, or DUPLICATE F1 WITH SAME F3. The following message indicates that validation is entered. The validation does not reclaim any orphan Format-3 DSCBs.

   IEC604I VTOC VALIDATE ENTERED ON DEVICE xxxx,volser ,----,DEVMAN 

If there are DSCB-related errors, DSCBs, message IEC618_ is displayed. If there are other VTOC errors, an IEC602I message may be issued. For example:

IEC618I ORPHAN FMT-3 DSCB,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx, DSCB=cccchhhrr)

IEC618E INCORRECT EXTENTS IN DSCB=cccchhhrr), DSN=Up to 44-byte datasetname 

IEC618E SAME F3 WITH DUPLICATE F1=cccchhhrr), DSN=Up to 44-byte datasetname

IEC618E INCORRECT F3s COUNT IN F9=cccchhhrr), DSN=Up to 44-byte datasetname

IEC602I VTOC NOT CONVERTED ON uuuu,volser, 0,(EXTENT=CCHHCCHH,DSCB=CCCCHHHHRR-CCCCHHHHRR)

Take a DEVMAN SVC dump of the current indexed VTOC. The dump will be presented as follows:

DUMP TITLE=VTOC VALIDATTION,VOLSER=volser, REASON=IEC6xxx,ERROR= errormessage-text. The REASON=IEC6xxx will be REASON=IEC618I, REASON= IEC618E, or REASON= IEC602I.

errormessage-text will include one of the following reasons:

• ORPHAN FMT3 CHAIN
• ORPHAN FMT-3 DSCB
• INCORRECT EXTENTS IN DSCB
• ORPHAN F3 W/ INVALID DSCB
• SAME F3 WITH DUPLICATE F1
• INCORRECT F3s COUNT IN F9
• OTHER VTOC ERRORS

If orphan Format-3 DSCB is the only type of error that is indicated by orphan Format-3 DSCB in message IEC618I, and if RETRY(STAT011) is activated in the system, the system will retry the allocation to use up one or two orphan Format-3 DSCB. The VTOC index is not disabled because STAT011_PRESERVE_INDEX=YES was specified. If RETRY(STAT011) is not activated, the system will not retry to use up ORPHAN FMT-3 DSCB. However, the failure will still not disable the VTOC index.

If another VTOC error (as shown in IEC618_ and IEC602I with a different reason text such as ORPHAN FMT3 CHAIN or INCORRECT EXTENTS IN DSCB), is detected, the VTOC index is not disabled. The failure is issued with CVAF status code STAT011 regardless of whether RETRY(STAT011) is activated.

If the retry does not succeed, the following message is issued to confirm the error:

IEC603I VTOC ERRORS MAY EXIST ON uuuu,volser, 8 

NO

If CVAF returns a STAT011 error to its caller, the VTOC index may be disabled.

If STAT011_PRESERVE_INDEX=NO is activated, DADSM allocation performs the following actions in addition to disabling the VTOC index or converting it to OSVTOC:

• Internally detects the failure associated with IEC608I message followed by an SVC dump of DADSM with diagnostic codes: DIAG=0820040B, 0853040B, 0854040B, or 0855040B. Those codes are occur when CVAF sets status x0B(STAT011) when it uses an orphan Format-3 DSCB as a free Format-0 DSCB. The dump is not being issued until validation processing begins.
• A VTOC validation function determines the status of the orphan Format-3 DSCBs and other VTOC conditions. The following message is displayed to indicate that validation is entered.

  IEC604I VTOC VALIDATE ENTERED ON DEVICE xxxx,volser,----,DEVMAN 

• Message IEC618_ is displayed for any errors about the DSCBs. If there are other VTOC errors, an IEC602I message may be issued. For example:

  IEC618I ORPHAN FMT-3 DSCB,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx, DSCB=cccchhhrr) 

  IEC618E ORPHAN FMT3 CHAIN,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx, DSCB=cccchhhrr) 

  IEC618E INCORRECT EXTENTS IN DSCB=cccchhhhrr, DSN=Up to 44-byte datasetname

  IEC618E SAME F3 WITH DUPLICATE F1=cccchhhhrr, DSN=Up to 44-byte datasetname

  IEC618E INCORRECT F3s COUNT IN F9=cccchhhhrr, DSN=Up to 44-byte datasetname 

  IEC602I VTOC NOT CONVERTED ON uuuu,volser, 0, (EXTENT=CCHHCCHH,DSCB=CCCCHHHHRR-CCCCHHHHRR) 

Take a DEVMAN SVC dump of the current indexed VTOC. For example:

DUMP TITLE=VTOC VALIDATION,VOLSER=volser, REASON=IEC6xxx,ERROR= errormessage-text

REASON=IEC6xxx will be REASON=IEC618I, REASON= IEC618E, or REASON= IEC602I.

The error-message-text will be one of the following reasons:

• ORPHAN FMT3 CHAIN
• ORPHAN FMT-3 DSCB
• INCORRECT EXTENTS IN DSCB
• ORPHAN F3 W/ INVALID DSCB
• SAME F3 WITH DUPLICATE F1
• INCORRECT F3s COUNT IN F9
• OTHER VTOC ERRORS

If orphan Format-3 DSCB is the only type of errors indicated by ORPHAN FMT-3 DSCB in IEC618I, and if RETRY(STAT011) is activated in the system, the system will retry the allocation to use up one or at most two orphan Format-3 DSCB. It will not disable the index if the allocation is successful. If RETRY(STAT011) is not activated, the system will not retry to use up the orphan Format-3 DSCB. However, any VTOC failure will disable the VTOC index because STAT011_PRESERVE_INDEX=NO is used.

In addition to detecting the orphan Format-3 DSCBs (only 'ORPHAN FMT3 CHAIN' in IEC618I message) condition, if another VTOC error is detected as shown in IEC618E or IEC602I with a different reason text, the VTOC index will be disabled, and the system will call the CONVERT routine to convert to non-indexed VTOC(aka.OSVTOC).

An IEC608I message with reason code 24 is issued.

EC608I DADSM FUNCTION DISABLED THE VTOC devn,volser, 24, CCHHR

Issue an IEC604I message before converting the disabled-index VTOC to non-indexed VTOC(OSVTOC) device.

IEC604I VTOC CONVERT ROUTINE ENTERED ON devn,volser, DI-O,DEVMAN 

The CONVERT(IGG0425P) routine will attempt to reclaim the orphan DSCBs, and fix any space errors if possible.

The system will restart the allocation one more time on the non-indexed VTOC device.

Tip: After the disabled indexed VTOC is converted to OSVTOC, performance might be affected by a large VTOC or the increasing number data sets over time. If that is the case, use the ICKDSF program to convert the VTOC back to an indexed VTOC with the ICKDSF BUILDIX command. For example:

BUILDIX DDNAME(DDVOL) IX

If the keyword is not specified, no message is logged.

Default: NO

RETRY(STAT011)

If the keyword is activated, DADSM allocation will perform the following actions:

1. Detect the failure with the IEC608I message followed by an SVC DADSM dump with diagnostic codes 0820040B, 0853040B, 0854040B, or 0855040B. They are the result of CVF setting status x0B(STAT011).
2. Take a DEVMAN SVC dump of the disabled-index VTOC and issue the IEC608I message with reason code 24.

   IEC608I DADSM FUNCTION DISABLED THE VTOC devn,volser, 24,CCHHR

3. Issue the IEC604I message before converting the disabled-index VTOC to non-indexed VTOC(OSVTOC) device. For example:

   IEC604I VTOC CONVERT ROUTINE ENTERED ON devn,volser, DI-O,DEVMAN

4. Restart the allocation one more time on the non-indexed VTOC device. Notice that the disabled indexed VTOC has been converted to OSVTOC. The performance may affect slightly if the number data sets is increased significantly over time. If that is the case, use ICKDSF program to convert the VTOC back to an indexed VTOC with the ICKDSF BUILDIX command:

   BUILDIX DDNAME(DDVOL) IX

   Refer to the STAT011_PRESERVE_INDEX keyword to see how the system behaves when the RETRY(STAT011) keyword is used with STAT011_PRESERVE_INDEX keyword.

The following two tables provide a summary of how these two keywords are combined together in the system.

Table 1. Without the RETRY(STAT011) DEVSUP keyword

STAT011_PRESERVE_INDEX=NO

STAT011_PRESERVE_INDEX=YES

This is existing behavior without this fix. It is also the default behavior similar to prior releases. Will not detect orphan DSCBs and will not validate VTOC during the time of the failure. Takes an SVC dump of the VTOC with the IEC608I message. This is a SVC dump, not a DEVMAN dump like specified in the other quadrants. The SVC dump is accompanied with DIAG=0820040B, 0853040B, 0854040B, or 0855040B. It is the result of CVAF setting status x0B(STAT011) when it uses an orphan Format-3 DSCB as a free Format-0 DSCB. The VTOC index is disabled and the job fails. The next access or allocation to the VTOC will cause VTOC convert routine to be entered and reclaimed the orphan DSCBs. An ICKDSF job must be executed by a system administrator with the option to convert back to indexed VTOC.

Detects orphan DSCBs and validates VTOC. This message is issued: IEC604I VTOC VALIDATE ENTERED ON DEVICE xxxx,volser,----,DEVMAN Message IEC618_ is displayed for any errors about the DSCBs. If there are other VTOC errors, the IEC602I message may be issued. IEC618I ORPHAN FMT-3 DSCB,DEV=uuuu,volser,yy (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E ORPHAN FMT3 CHAIN,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E INCORRECT EXTENTS IN DSCB=cccchhhhrr,DSN=Up to 44-byte datasetname IEC618E SAME F3 WITH DUPLICATE F1=cccchhhhrr,DSN=Up to 44-byte datasetname IEC618E INCORRECT F3s COUNT IN F9=cccchhhhrr,DSN=Up to 44-byte datasetname IEC602I VTOC NOT CONVERTED ON uuuu,volser,0,(EXTENT=CCHHCCHH,DSCB=CCCCHHHHRR-CCCCHHHHRR) Take DEVMAN DUMP:DUMP TITLE=VTOC VALIDATION,VOLSER=volser,REASON=IEC6xxx,ERROR= error-message-text. The IEC6xxI reason will be IEC618I, IEC618E, or IEC602I. The error-message-text will be one of the following reasons: ORPHAN FMT3 CHAIN ORPHAN FMT-3 DSCB INCORRECT EXTENTS IN DSCB ORPHAN F3 W/ INVALID DSCB SAME F3 WITH DUPLICATE F1 INCORRECT F3s COUNT IN F9 OTHER VTOC ERRORS Will fail because it's not attempting to retry on orphan DSCBs because the keyword RETRY(STAT011) is not used. Since the VTOC index is to be preserved, the VTOC convert routine will not be entered to clean up orphan DSCBs. An ICKDSF job needs to be executed by a system administrator with REFVTOC option to clean the orphan DSCBs.

Table 2. With the RETRY(STAT011) DEVSUP keyword

STAT011_PRESERVE_INDEX=NO

STAT011_PRESERVE_INDEX=YES

Detect orphan DSCBs and validate VTOC. Issue these messages: IEC604I VTOC VALIDATE ENTERED ON DEVICE xxxx,volser,----,DEVMAN Message IEC618_ is displayed for any errors about the DSCBs. If there are other VTOC errors, the IEC602I message may be issued. IEC618I ORPHAN FMT-3 DSCB,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E ORPHAN FMT3 CHAIN,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E INCORRECT EXTENTS IN DSCB=cccchhhhrr,DSN=Up to 44-byte datasetname IEC618E SAME F3 WITH DUPLICATE F1=cccchhhhrr,DSN=Up to 44-byte datasetname IEC618E INCORRECT F3s COUNT IN F9=cccchhhhrr,DSN=Up to 44-byte datasetname IEC602I VTOC NOT CONVERTED ON uuuu,volser,0,(EXTENT=CCHHCCHH,DSCB=CCCCHHHHRR-CCCCHHHHRR) Take DEVMAN DUMP: DUMP TITLE=VTOC. VALIDATION,VOLSER=volser,REASON=IEC6xxx,ERROR=error-message-text The IEC6xxI reason will be IEC618I, IEC618E, or IEC602I. The error-message-text will be one of the following reasons: ORPHAN FMT3 CHAIN ORPHAN FMT-3 DSCB INCORRECT EXTENTS IN DSCB ORPHAN F3 W/ INVALID DSCB SAME F3 WITH DUPLICATE F1 INCORRECT F3s COUNT IN F9 OTHER VTOC ERRORS Will retry on the orphan DSCB because the keyword RETRY(STAT011) is used. If orphan Format-3 DSCB is the only type of error indicated by ORPHAN FMT-3 DSCB in IEC618I, the system will retry the allocation to use up one or at most two orphan format-3 DSCBs, and will disable the VTOC index because STAT011_PRESERVE_INDEX=NO. If the retry fails, it will disable index and convert to OSVTOC to retry allocation once more. It will reclaim the orphan DSCBs.

Detect orphan DSCBs and validate VTOC. This message is issued: IEC604I VTOC VALIDATE ENTERED ON DEVICE xxxx,volser,----,DEVMAN Message IEC618_ is displayed for any errors about the DSCBs. If there are other VTOC errors, the IEC602I message may be issued. IEC618I ORPHAN FMT-3 DSCB,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E ORPHAN FMT3 CHAIN,DEV=uuuu,volser,yy, (DSCBNO=xxxxxxxxx,DSCB=cccchhhrr) IEC618E INCORRECT EXTENTS IN DSCB=cccchhhrr,DSN=Up to 44-byte datasetname IEC618E SAME F3 WITH DUPLICATE F1=cccchhhrr,DSN=Up to 44-byte datasetname IEC618E INCORRECT F3s COUNT IN F9=cccchhhrr,DSN=Up to 44-byte datasetname IEC602I VTOC NOT CONVERTED ON uuuu,volser,0,(EXTENT=CCHHCCHH,DSCB=CCCCHHHHRR-CCCCHHHHRR) Take DEVMAN DUMP: DUMP TITLE=VTOC VALIDATION,VOLSER=volser,REASON=IEC6xxx,ERROR=error-message-text The error-message-text will be one of the following reasons: ORPHAN FMT3 CHAIN ORPHAN FMT-3 DSCB INCORRECT EXTENTS IN DSCB ORPHAN F3 W/ INVALID DSCB SAME F3 WITH DUPLICATE F1 INCORRECT F3s COUNT IN F9 OTHER VTOC ERRORS Will retry on the orphan DSCB because the keyword RETRY(STAT011) is used. If orphan Format-3 DSCB is the only type of error indicated by ORPHAN FMT-3 DSCB in IEC618I, and since RETRY(STAT011) is used, the system will retry the allocation to use up one or at most two orphan format-3 DSCB, and will not disable the VTOC index because STAT011_PRESERVE_INDEX=YES. If the retry fails, it will not disable index and will not convert to OSVTOC to retry to reclaim the orphans. An ICKDSF job needs to be executed by a system administrator with REFVTOC option to clean the orphan DSCBs.

NO

Indicates that OPEN processing to issue RACROUTEs based on the options set in RACF® such as SETROPTS TAPEDSN and SETROPTS CLASSACT(TAPEVOL).

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 that is 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 that is 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

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.

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 that is 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.

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 that are generated by the tape system are RACF-protected.

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.

FAIL

Denies accessing of data sets that typically cannot be accessed.

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.

• 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.

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, 32 K when specified in kilobytes, 1 M when specified in megabytes, and 1G when specified in gigabytes. The maximum values are 2147483648, 2097152 K, 2048 M, and 2 G. These maximum block size values are much larger than the system supports for BLKSIZE. However, coding a large value 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 that is 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.

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.

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 relabeled. Attempts to relabel 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.

YES

Specifies that tape cartridges written at track capacities that the drive is not capable of reading. For example,. it specifies that a 36-track cartridge on a D/T3480 or a 256-track cartridge on a D/T3590 Model B1x is to be relabeled at the device-capable track capacity by the OPEN or EOV label editor routines. This relabel 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 that is written on the cartridge by the device and placed in the sense data.