FDRERASE control statements

The control statements consist of a main statement (ERASE, SECUREERASE, SIMERASE, EMPTYVTOC, VERIFY, or PRINT) and one or more MOUNT statements specifying the DASD devices to be processed.

PRINT and VERIFY Statement Syntax

EMPTYVTOC Statement

EMPTYVTOC does not erase any data. It quickly writes the VTOC as empty (no data sets). EMPTYVTOC is a quick way to delete all data sets from a volume, or to initialize a volume. Many DASD can be initialized with simple control statements; up to 10 DASD volumes are processed in parallel. The VTOC size and location can be specified on the following MOUNT statements or it defaults to the existing VTOC size and location if it exists. The VTOCIX (indexed VTOC) is also created for a new VTOC or if the VTOCIX previously existed.

By default, EMPTYVTOC operates on offline volumes only. If you add the ONLINE=VARYOFF operand, the volume is varied offline (if it is not in use) and emptied. If you add the operand VARYON=AFTER, the volume is varied online after it is emptied.

EMPTYVTOC does not erase any data, nor does it uncatalog data sets that were in the VTOC.

ERASE Statement

By default, ERASE overwrites every track on the selected DASD devices with a single track-length record consisting of binary zeros, obliterating all data records that previously existed on the track. You can optionally request that every track be overwritten multiple times (ERASEPASS=n) and you can optionally specify the value to be used in each byte of the overwriting record (ERASEPATTERN=), varying it from pass to pass. Special pattern values are used to request a random pattern, or a “quick-erase” pass (erasing the tracks instead of overwriting). If multiple passes are requested, it processes every track on the volume in each pass from the “top” of the volume to the beginning.

When the overwriting record is all binary zeros, the ERASE function is quite fast since very little data must be sent down the channel for each track, allowing many DASD to be erased in parallel. Other values may require more time since the entire record must be transmitted for each track. It waits at the end of each pass to be sure that the data is hardened (written) to the DASD before continuing; this may take some seconds.

ERASE is often adequate for erasing DASD that are sold, scrapped, or returned to the manufacturer, since it makes it difficult to recover the original data even if the hard drives are removed, more so if multiple passes and patterns are used.

PRINT Statement

The PRINT statement prints information about the contents of selected tracks from an offline or online DASD. This can be used to verify that a DASD volume was actually erased. You can also use it to print the contents of a DASD volume before the erase.

By default, PRINT prints the first track from each of the first 100 cylinders on each selected DASD device, but you can specify operands to control the tracks printed. The operands for PRINT are listed at the end of the operand list that follows.

The print function prints one FDR175 message for each record on the selected tracks, including record 0 (R0) that is present on every track. However, if ERASEDATA=NONE is specified, only R0 is printed plus a count of the additional records. DASD erased with ERASE or SECUREERASE contain one track-length data record with the same value in every byte (unless ERASEPATTERN=FE was used); the value is the pattern used in the last erase pass on the track. See the description of message FDR175 for details of the print format.

SECUREERASE Statement

SECUREERASE is essentially an ERASE operation, except that minimum of ERASEPASS=3 is forced and special patterns are used. The first pattern is a random value (generated values “00”, “01”, “FE”, and “FF” are changed to “AA”), the second pass uses the complement of the first pattern, and the third pattern is a new random value (different from the first two). Up to 32 passes can be requested. The fourth pattern is a complement of the third. If more than four passes are requested, passes five through 32 use patterns of random values; instead of using the same value in every byte, each byte in each record in a cylinder is randomly generated; this is the processing described below for ERASEPATTERN=FE. The “odd” pass pattern is randomly generated, and the “even” pass pattern is the complement of the previous pass.

SECUREERASE can be used on your most sensitive data to make it very unlikely that the data could be recovered if the hard drives were removed. This may be necessary to meet legal requirements, such as for the protection of financial data, social security numbers, and other personal data.

SIMERASE Statement

SIMERASE does not erase any DASD, but it can be used to validate your FDRERASE control statements, and to verify which DASD devices are erased once SIMERASE is changed to one of the other options. SIMERASE lists all DASD devices that meet the selection criteria. If you specified CHECKTARGET=YES (or let it default), SIMERASE verifies that the selected volumes are either empty or have no valid volume label. If you specified ONLINE=VARYOFF, it identifies the volume that will be varied offline (although it cannot guarantee that the VARY OFFLINE will work).

VERIFY Statement

The VERIFY statement can be used to verify that a DASD volume has actually been erased. It reads the specified tracks on the selected volumes, and analyzes their contents to see it appears that they were erased with FDRERASE. To pass the verification, a track must contain a single full-track record containing the same character in every byte or containing the random pattern generated by ERASEPATTERN=FE.

If every verified track appears to be erased, the VERIFY reports that the volume is erased. Tracks that do not verify are printed in the format used by the PRINT statement (message FDR175) so that you can see what they contain. If more than ERASENUMB= tracks fail verification, VERIFY stops processing the volume.

By default, VERIFY verifies the last track from every cylinder on each selected DASD device, but you can specify operands to control the tracks verified. However, the elapsed time of the VERIFY is proportional to the number of tracks verified. The operands for VERIFY are listed at the end of the operand list that follows.

If all tracks pass verification, message FDR177 is printed to indicate this and to show what erase pattern was found (ERASE if the tracks contain no records, “xx” if all bytes contain X'xx' and “FE (Random)” if the FE pattern was detected.

Note that if you used operands to rebuild the VTOC after the volume was erased, the VTOC and VTOCIX tracks do not pass verification. You can successfully verify such volumes only if you use VERIFY operands such as ERASESTARTCYL= to start the verification after the VTOC and VTOCIX. If you plan to verify erased volumes, we suggest that you use the EMPTYVTOC function to rebuild the VTOC after running VERIFY.

EMPTYVTOC, ERASE, SECUREERASE, SIMERASE PRINT & VERIFY Statement Operands

TYPE=FULL

Must be specified on this statement.

ACTIVETARGET=

BYPASS

DASD that have active PPRC or EMC SRDF mirrors are not erased; you must terminate the PPRC/SRDF session before erasing the DASD. In addition, DASD in EMC subsystems that appear to be online to other systems are not erased.

PROCESS

DASD that have active PPRC or EMC SRDF mirrors are erased. This may slow down the erase since all the erased tracks must be mirrored to the remote DASD. In addition, DASD in EMC subsystems that appear to be online to other systems are erased.

Default: BYPASS.

When ACTIVETARGET=PROCESS is specified and a PPRC or SRDF session is active, FDRERASE performance may be degraded.

ALREADYERASED=

BYPASS

DASD that have been previously erased by FDRERASE are bypassed with an explanatory message. This is useful if you need to restart an FDRERASE job so that volumes previously completed are not erased again. However, if it was previously erased with the CPYVOLID=YES operand in effect, which leaves the volume in a usable state, FDRERASE erases it again.

PROCESS

DASD that have been previously erased by FDRERASE are erased again.

Default: BYPASS.

CHECKTARGET=

NO

The contents of the offline DASD is not checked. Any offline volume can be erased. CHECKTARGET=NO is required if you wish to erase DASD other than empty volumes and those created by FDRPAS. There may be additional security requirements for this operand. (See Securing FDRERASE.) If there are data sets on the volume, FDRERASE does not uncatalog them. You can make CHECKTARGET=NO invalid by setting option CHKTARGNO to “NO” in the FDR Global Options Table in the FDRERASE load library (see CHKTARGNO).

YES

FDRERASE checks the DASD device before beginning an erase operation to ensure that the DASD is empty or does not have a valid volume label “VOL1”. If the volume label contains “VOL1”, it checks to be sure that the volume contains only a VTOC, VTOCIX, VVDS, and/or ABR Model DSCB. DASD with no valid volume label include FDRPAS SWAP source DASD and SWAPDUMP target DASD (these have “FDR3” instead of “VOL1”), as well as FDRINSTANT target DASD (these have “FDR1” instead of “VOL1”.) Using CHECKTARGET=YES accepts all DASD whose label is invalid for any reason plus those with no volume label at all. If it fails these tests, the volume is bypassed with an explanatory message.

Default: YES.

FDRERASE cannot ensure that the selected devices are offline to all other sharing systems. You must take great care not to select DASD that contain data that is currently in use or that is needed later as it is possible to erase a DASD volume that is in use on another system when especially when specifying the CHECKTARGET=NO operand.

CONFERASE=

NO

Suppresses the messages and begins the erase immediately.

YES

Before beginning the erase, FDRPAS requests confirmation via console WTOR message FDRW01 that must be replied before the erase can start. All devices selected by each MOUNT statement are listed (note that some of them may be later bypassed because they are not eligible for erase). The FDRW01 message is preceded by FDR235 WTO messages defining the DASD volumes to be erased. Only one reply is required per FDRERASE step.

Default: NO.

CPYVOLID=

NO

After completing the erase, there is no VTOC on the volume. All tracks are erased; the label track (cylinder 0 track 0) is rewritten with a volume label with an ID of “FDR5” so that the volume cannot be varied online; the volume serial is the original volume serial of the volume. If you wish to use the volume, you need to initialize it with EMPTYVTOC or ICKDSF.

YES

If the volume has a valid volume label and VTOC before the erase, then FDRERASE invokes ICKDSF to rebuild an empty VTOC (and possibly a VTOCIX) after the volume is erased. If the volume was SMS-managed, the SMS flag is still on in the VTOC. The volume label has an ID of VOL1 so that the volume can be varied online.

By default, the volume has its original volume serial number, and the VTOC (and VTOCIX, if present) has its original location and size. You can specify options on the MOUNT statement to change the volume serial number, and to change the size and/or location of the VTOC.

Default: NO. CPYVOLID=YES is assumed if you specify VARYON=AFTER, EMPTYVTOC, or CHANGEVOL=.

If you are erasing a large number of volumes, it is faster to use CPYVOLID=NO and run EMPTYVTOC in a separate job to re-initialize all of the volumes after all the ERASEs are complete.

ERASEPASS=

ERSP=

nn

Specifies the number of times that FDRERASE overwrites each track. Note that FDRERASE starts at the top (highest cylinder) of each volume and continues through cylinder 0, then repeats for the next pass. At the end of each pass, FDRERASE ensures that the data has been written from cache to the back-end DASD. The overwriting data is a single full-track record; it is all binary zeros unless ERASEPATTERN= or SECUREERASE is specified.

If the function is ERASE, only values from 1 to 8 are accepted.

If the function is SECUREERASE, only values from 3 to 32 are accepted.

Default: 1 for ERASE and 3 for SECUREERASE.

ERASEPATTERN=

EPAT=

hh…

Specifies the byte to be used for each erasing record used by the ERASE function (it is ignored for SECUREERASE). It consists of a series of bytes (up to eight bytes, two hex digits per byte). The first byte is used to fill the record for the first pass, the second for the second pass, and so on. If you specify fewer bytes than the value of ERASEPASS=n, binary zeros are used for the extra passes.

There are some pattern bytes with special meanings:

01

Indicates that this pass is to erase the track instead of writing a pattern; 01 could be used as the last pattern to cause the track to be erased, leaving no records on the track.

FE

Indicates that random values are to be used. Unlike other patterns, the bytes throughout the record on each track varies, and a different pattern is used for each track within a cylinder. If “FE” appears twice in a row in ERASEPATTERN, the first pattern is randomly generated, but the pattern for the next pass is the complement of the preceding pass. If “FE” appears three times in a row, the third pattern is randomly generated, while a fourth occurrence of “FE” in a row is the complement of the third pattern, and so on. If any other pattern character appears between occurrences of “FE”, the next “FE” generates a new random pattern.

For SECUREERASE, the patterns are random, as described earlier. You cannot override the patterns for SECUREERASE, although you can override the number of passes (ERASEPASS=).

Default: 00 for ERASE, random from SECUREERASE.

HARDENTIMEOUT=

HTO=

nnnn

Specifies the number of seconds (0-255) that FDRERASE waits for data to be hardened (written from cache to DASD) at the end of each pass of ERASE and SECUREERASE. A value of 0 disables the hardening commands; 0 is valid only for ERASE, not SECUREERASE. On EMC subsystems, a value other than the default of 120 causes FDRERASE to wait for the entire time out value even if the count of unhardened tracks stalls (stops decreasing). On other than EMC subsystems, the control unit continues to harden data even if FDRERASE has stopped waiting for it.

Default: 120 (2 minutes).

LOGMESS=

LM=

NO

No SYSLOG/console messages are written.

YES

Messages are written to SYSLOG (and usually to an operator console) documenting that the erase of each volume has completed (the “successful” message and all error messages).

Default: YES.

MAXEU=

nn

Specifies the maximum number of volumes (1-64) that can be erased concurrently if they reside in the same underlying FBA physical DASD or RAID group in the DASD subsystem, if it can be determined. This avoids performance degradation that can occur if many logical volumes that reside on the same underlying DASD are erased concurrently, because of contention for the disk heads and data paths to the DASD.

If a MOUNT statement in this FDRERASE step specifies DASD devices that reside on various underlying DASD or even in different DASD subsystems, then the MAXEU= and MAXTASKS= operands interact to control the active erase tasks. FDRERASE attempts to start up to MAXTASKS= erase tasks, as long as no more than MAXEU active tasks are directed to the same underlying DASD or RAID group.

FDRERASE uses queries that vary by DASD manufacturer to identify the underlying physical DASD or RAID group for each DASD volume, but it cannot determine the underlying DASD volumes in all DASD subsystems. If it cannot make this determination for some or all DASD specified, it does not limit the number of erase tasks affecting those DASD volumes.

You may be able to increase the value of MAXEU if the DASD are in a high-performance subsystem, but you may need to experiment to find an appropriate value.

MAXEU= is ignored if VOLSORT=NO is specified.

Default: 8

MAXTASKS=

nn

Specifies the maximum number of volumes that can be erased concurrently, from 1 to 64. If one of the following MOUNT statements selects a number of offline DASD volumes that exceeds MAXTASKS=nn, FDRERASE starts the indicated number of internal erase tasks; as each one finishes another one is started, until all selected DASD have been erased. The number of tasks can also be modified dynamically while FDRERASE is running. (See Console Commands for FDRERASE.)

MAXTASKS=64 (the default) requires a below-the-line private area of up to 8.5MB. If the available below-the-line private area on the system where FDRERASE is run is smaller, MAXTASKS= is automatically reduced, to avoid storage shortage errors, unless you have specified the MAXTASKS= operand.

MAXTASKS= applies to each MOUNT statement separately. The DASD volumes specified on each MOUNT statement are completely processed (up to MAXTASKS= concurrently) until they are all complete. Then the next MOUNT statement is processed.

If VOLSORT=YES is specified or defaulted, then the maximum concurrent erase tasks may be less than 64 because of the processing described above under MAXEU=, where FDRERASE attempts to limit the number of concurrent erases that affect the same underlying physical DASD or RAID groups. If the underlying physical DASD cannot be determined, but the total number of DASD to be erased exceeds MAXTASKS=, then FDRERASE spreads the active tasks by z/OS device address, to attempt to achieve the same result.

For EMPTYVTOC, the maximum value for MAXTASKS= is 10.

Default: 64 except EMPTYVTOC defaults to 10.

ONLINE=

BYPASS

DASD devices that are online are bypassed with an explanatory message. If the bypassed DASD was selected by a full 4-digit device address (not a prefix), the message causes the step to end with return code to call attention to the bypassed device.

VARYOFF

DASD devices specified on each MOUNT statement that are online to this system are varied offline and erased if they are not currently allocated to any task on this system. To ensure that you are varying the proper devices offline, WTOR message FDRW01 is issued to the operator's console to confirm each device.

Default: BYPASS.

It is your responsibility to ensure that the online volumes that you have specified are not online or in use on any other system. If you erase a volume in use on another system, the results are unpredictable, and data is lost. ONLINE=VARYOFF is primarily intended for use when erasing DASD as you are leaving a disaster/recovery site since it relieves you of the need to manually vary all the volumes offline.

If you specify ONLINE=VARYOFF and the volumes to be varied offline contain data sets, you must also specify CHECKTARGET=NO in order to erase those volumes. If the volumes are empty, then CHECKTARGET=NO is not required.

PRTDEFAULTS

If specified, it lists the defaults for various operands that affect FDRERASE operation. If overriding operands are present before the PRTDEFAULTS operand, it displays those overrides. Overriding operands that follow the PRTDEFAULTS operand are not displayed.

SELTERR=

Specifies what happens at step termination if FDRERASE finds that one or more selected offline devices was not erased because it did not meet all the criteria, such as it was already erased (unless ALREADYERASED=PROCESS was specified) or not created by FDRPAS or empty (unless CHECKTARGET=NO was specified).

NO

A condition code or ABEND is not to be issued at step termination. You might use SELTERR=NO when you expect some devices in your ERASEUNIT= list may not be eligible.

YES

A condition code or ABEND is issued at step termination to call attention to the volumes that were bypassed.

Default: YES, unless overridden in the FDR Global Options Table (see SELTERR).

VARYON=

AFTER

After erasing the DASD, the volume is varied online and remounted. CPYVOLID=YES is forced. The volume serial of the DASD must not match the serial of any other online volume (such as the FDRPAS target device if you are erasing an FDRPAS source DASD); if it does match you can use the CHANGEVOL= operand of the MOUNT statement to relabel the volume. The VARY ONLINE is done after the erase is complete and the FDR241 ERASE COMPLETE message is printed.

NOAFTER

The DASD volume is left offline after the erase.

Default: NOAFTER.

VOLSORT=

NO

The underlying DASD volumes are not used to sort or limit the DASD volumes erased concurrently. DASD are selected in the order that their UCBs are found in the operating system and up to MAXTASKS= DASD volumes are erased concurrently.

YES

FDRERASE uses hardware queries (that vary by DASD manufacturer) to identify the underlying physical FBA DASD or RAID group for each logical DASD selected for erase and the DASD volumes are sorted by that DASD ID. See MAXEU= to understand how this ID affects FDRERASE operation.

Default: YES.

Additional PRINT and VERIFY Statement Operands

The following operands can be specified ONLY on a VERIFY or PRINT statement. If all of them are omitted, VERIFY defaults to verifying the last track of every cylinder, and PRINT defaults to printing track 0 from each of the first 100 cylinders on each selected DASD volume:

ERASEDATA=

NONE

(PRINT only) Specifies that only Record 0 (R0) is printed from each selected track, including a count of the additional data records on the track. This greatly reduces the size of the printout when printing from a volume before it has been erased.

Default: One line is printed for each record on each selected track.

ERASENUMB=

nnnnn

(VERIFY and PRINT only) For VERIFY, specifies the number of tracks (1-65535) that must fail erase verification on a DASD volume before the VERIFY function stops processing the volume. For PRINT, specifies the number of tracks (1-65535) whose contents are printed from each DASD volume. The tracks that are verified or printed are controlled by the operands ERASESTARTCYL=, ERASESTARTTRK=, and ERASESKIP=, described below. See FDR175 for details of the print format.

Default: 100.

ERASESKIP=

nnnnn

(VERIFY and PRINT only) ERASESKIP=, in conjunction with ERASESTARTCYL= and ERASESTARTTRK=, described below, specify the tracks to be verified or printed. The first track is specified by ERASESTARTCYL= and ERASESTARTTRK=, and subsequent tracks are selected by adding the ERASESKIP= value (1-32767) to the relative track number of the last track printed. If you want to print contiguous tracks, specify ERASESKIP=1.

Default: 15 (verify or print one track from contiguous cylinders).

ERASESTARTCYL=

ERASESTARTTRK=

(VERIFY and PRINT only) ERASESTARTCYL= specifies the cylinder number (0-65535) of the first track to verify or print, and ERASESTARTTRK= specifies the track number (0-14) of the first track to verify or print. Both values are in decimal.

Default: VERIFY defaults to ERASESTARTCYL=0 and ERASESTARTTRK=14 which is the last track of the first cylinder. If ERASESKIP= is set to or defaults to 15, then the last track of every cylinder is verified.

Default: PRINT defaults to 0 for both operands. If both are omitted, the print starts with the label track (cylinder 0 track 0).

To VERIFY the entire DASD volume, specify operands ERASESTARTCYL=0, ERASESTARTTRK=0, and ERASESKIP=1.

ONLINE=

BYPASS

Verify or print only offline DASD

VERIFY

(VERIFY only) Verify ONLINE DASD as well as OFFLINE DASD. Note that ONLINE DASD may fail verification if tracks in the VTOC, VTOCIX, or VVDS are verified. You can use the ERASESTARTCYL= and/or ERASESTARTTRK= operands to start the verification after the VTOC/VTOCIX/VVDS.

Default: For VERIFY, only OFFLINE DASD are verified. Any ONLINE DASD selected by the MOUNT statement are bypassed with a diagnostic message.

Default: For the PRINT command, ONLINE and OFFLINE volumes are printed.

MOUNT Statement Syntax

One or more MOUNT ERASEUNIT= statements follow the main statement and each specifies a DASD device or set of devices to be erased, verified, or printed. Only DASD devices that are offline on the system where FDRERASE is executing are selected unless ONLINE=VARYOFF is specified on the main statement. However, if the main statement is a PRINT statement, then ERASEUNIT= can specify any offline or online DASD device.

The DASD selected by each MOUNT statement are completely processed before the next MOUNT statement is examined. MAXTASKS= (on the main statement) applies only to the DASD selected on a single MOUNT statement, so if the MOUNT specifies only one or a few DASD, only those DASD are erased concurrently. The ability to enter multiple MOUNT statements is provided primarily to allow varying values for the new VTOC and volume serial on the erased DASD. It is suggested that unless you need to vary the VTOC location and size or volume serial, you provide a single MOUNT statement and identify all of the DASD to be erased on that statement.

MOUNT Statement Operands

ERASEUNIT=

EU=

uuuu

Specifies the z/OS device addresses of the DASD devices to be erased, verified, or printed. The address can be specified as a 4-digit (hex) z/OS device address, or it can be specified as 1, 2, or 3 digits with a trailing asterisk (*); in this case all eligible offline z/OS DASD addresses starting with the prefix specified are erased. To erase multiple devices or ranges of devices (by prefix), specify them in parentheses, separated by commas, but you cannot specify more than 255 subparameters (device addresses or address prefix ranges) within the parentheses. If you use address prefixes, the total number of devices to erase can be up to 8190.

Only devices that are offline are erased (but online or offline DASD can be printed). However, if you specify ONLINE=VARYOFF, online devices that can be placed offline on this system are also erased (this is intended mainly for use at disaster/recovery sites). If a device is manually placed offline after the erase step starts, it is not selected. For a VERIFY function, only offline DASD are verified; you can specify ONLINE=VERIFY if you want to verify online DASD as well as offline DASD.

If the range to be erased includes devices that are in your I/O configuration but which do not really exist (are not in the hardware configuration of the DASD subsystem), you may receive this console message “IOS002A dev, NO PATHS AVAILABLE” for each such device if it is the first time that the device has been accessed since the last IPL. The messages can be ignored. They may occur only under certain releases of OS/390.

For example,

MOUNT ERASEUNIT=17C0 erases one DASD 17C0MOUNT ERASEUNIT=17C* erases DASD in the range 17C0-17CFMOUNT ERASEUNIT=17* erases DASD in the range 1700-17FFMOUNT ERASEUNIT=(17*,18*,19A*) erases DASD in the ranges 1700-17FF, 1800-18FF,
and 19A0-19AF.

CHANGEVOL=

CV=

Allows you to change the volume serial of the erased volume, after the erase is complete. CPYVOLID=YES is assumed on the main statement. The value must be six characters with these values:

*

The equivalent character is copied from the original volume serial on the DASD.

/

Insert a sequence number into the new serial. You can put 1 to 6 slashes in the name. See CHANGEVOLNUM=.

&uuu

This string is replaced with the DASD device address.

Any other character

That character is inserted in that position in the new volume serial.

For example,

CHANGEVOL=ABC***

changes the volser to ABC plus the original last 3 characters

CHANGEVOL=**XY**

puts XY in the 3rd and 4th positions, copying the original characters in the other positions

CHANGEVOL=XX&UUU

changes the volser to XX plus the device address (for example, XX17CA)

CHANGEVOL=ABCXYZ

changes the volser to ABCXYZ

CHANGEVOL=AB///Z

changes the volser to ABnnnZ. “nnn” is incremented for each new volume.

CHANGEVOLNUM=

nnnnn

Specifies the starting sequence number to be used when the CHANGEVOL= value contains one or more / (slashes). The value can be from 0 to 65535.

The maximum sequence number generated is 65535.

Default: 0.

CHECKTARGETVOL=

CHKTVOL=

If specified, the volume serial of the volume to be erased is compared to the value specified. The value can be a complete volume serial (up to six characters) or it may be a volume serial prefix followed by an asterisk (*). For example, CHECKTARGETVOL=PAY001 or CHECKTARGETVOL=PAY*. If the volume has a proper volume label but the volume serial does not match, it is not erased. If it has no volume label or if it was previous erased by FDRERASE or was an FDRPAS source volume, the comparison is not done and the volume is erased. The operand can be abbreviated CHKTVOL=.

CHECKTARGETVOL=vol (a complete volume serial) is usually appropriate only when ERASEUNIT=uuuu specifies only a single device. However, if there are multiple MOUNT statements in an FDRERASE job, FDRERASE processes them one at a time, so only one volume is erased at a time.

STORAGEGROUP

SG

The erased VTOC has the “SMS-managed” flag turned on. This is honored only if the VTOC is being rebuilt (CPYVOLID=YES or EMPTYVTOC on the main statement). You must add the volume serial of the erased DASD to your SMS configuration before it can be used as an SMS-managed volume.

Default: If the DASD had a valid volume label and VTOC, and the SMS flag was on in the original VTOC, it remains on in the erased VTOC. Otherwise, it is off.

VTOCCYL=

VTOCTRK=

VTOCLOC=

Specifies the new starting location of the VTOC, if CPYVOLID=YES or EMPTYVTOC is specified on the main statement. You can specify the starting cylinder number (VTOCCYL=cccc) and starting track (VTOCTRK=tt). If VTOCCYL= is specified but not VTOCTRK=, the starting track defaults to 0. VTOCTRK= cannot be specified without VTOCCYL=.

Alternately, you can specify the starting track of the VTOC, relative to track 0 on the volume (VTOCLOC=nnnnn).

If you specify one of these operands to specify the start of the new VTOC, you must also specify the size of the VTOC (VTOCSIZE=).

Because of IBM requirements, the last track of the VTOC can be no higher than relative track 65535 (cylinder 4368), so the starting track of the new VTOC plus the new VTOC size cannot exceed 65535.

Default: The VTOC (and VTOCIX if present) is written in its original location with its original size.

VTOCSIZE=

VS=

nnnn

Specifies the new size of the VTOC, in tracks (1-9999). VTOCSIZE= must be specified in conjunction with parameters specifying the starting track of the new VTOC (see above).

VTOC Notes

If the main statement specified the EMPTYVTOC operation or the CPYVOLID=YES operand, then ICKDSF is invoked at the end of the operation to build a VTOC (and possibly a VTOCIX).

The operands above (VTOCxxxx=) can be used to specify the location and size of the empty VTOC. If they are not specified and if the volume already has a VTOC, the empty VTOC has the same location and size. If there was an indexed VTOC (VTOCIX) on the volume, even if it was not active, it is rebuilt and activated with the same location and size.

For an EMPTYVTOC operation, if the volume did not previously have a valid volume label and VTOC, then the VTOC size and location must be specified or the EMPTYVTOC fails. A new VTOCIX is created, 1/16th the size of the VTOC (rounded up, with a minimum of three tracks) and is placed immediately after the new VTOC. This provides a very quick and easy way to initialize a set of volumes with a VTOC and VTOCIX.

If you specify the new VTOC size and location, and the volume originally contained a VTOCIX or did not contain a VTOC, a new VTOCIX is created, 1/16th the size of the VTOC (rounded up, with a minimum of three tracks) and is placed immediately after the new VTOC.

EXCLUDE Statement Syntax

An EXCLUDE statement identifies a volume or a group of volumes that are not to be processed. One or more EXCLUDE statements may be present and must follow the main statement and precede the MOUNT statement(s).

The control statements are always scanned in the order that they were input; therefore, EXCLUDE statements must precede MOUNT statements.

Example 1. Select all units starting with “07C” except unit address “07C0”.

EXCLUDE ERASEUNIT=07C0
MOUNT ERASEUNIT=07C*

Example 2. Select all units starting with “07” except the units starting with “07C” and “07D” as well as unit “07E0”.

EXCLUDE ERASEUNIT=07C*
EXCLUDE ERASEUNIT=07D*
EXCLUDE ERASEUNIT=07E0
MOUNT ERASEUNIT=07*