DFSMSdss: Build the IPLable stand-alone DFSMSdss image
Description
Starting with z/OS® V1R12, DFSMSdss uses BSAM instead of EXCP to read from and write to DFSMSdss dump data sets during DUMP, COPYDUMP, and RESTORE operations. As a result, if you plan to use DFSMSdss Stand-Alone Services, you must rebuild the IPL-capable core image for the Stand-Alone Services program.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | DFSMSdss. |
|---|---|
| When change was introduced: | General migration action not tied to a specific release. |
| Applies to migration from: | z/OS V2R1 and z/OS V1R13. |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if you want to use DFSMSdss Stand-Alone Services. |
| Target system hardware requirements: | Stand-Alone Services supports the IBM® 3494 TotalStorage Enterprise Automated Tape Library, the IBM 3495 TotalStorage Enterprise Automated Tape Library, and the IBM 3590 TotalStorage Enterprise Tape Subsystem. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | Stand-Alone Services does not support the creation of the core image on an SMS-managed volume. |
| System impacts: | If this migration action is not performed, users
of DFSMSdss standalone restore cannot restore to tape any backups
that were created with greater than 65520-byte blocks. The operation
fails with the message ADRY3530I SEQUENCE ERROR ON RESTORE
TAPE. Backups created with 65520 byte blocks can be restored as before. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take
Follow these steps:
- Use the DFSMSdss command BUILDSA to create a Stand-Alone
Services IP-capable core image. On the command, you can specify:
- Device from which Stand-Alone Services are to be IPLed (such as a card reader, tape drive, or DASD volume)
- Operator console to be used for Stand-Alone Services
The BUILDSA command builds the IPLable core image on the current operating system and determines a record size, based on whether the IPL is performed from a card, tape, or DASD.
- Use your security management product, such as RACF®, to protect the SYS1.ADR.SAIPLD.Vvolser data set and the Stand-Alone Services modules.
- If you have not already done so, create a backup copy of your system that can be restored by this function. For information about backing up volumes, see z/OS DFSMSdfp Storage Administration.
Notes:
- To ensure that Stand-Alone Services is available when you run from DASD, do not delete the SYS1.ADR.SAIPLD.Vvolser data set or move it to another volume.
- If you IPL from DASD and later change the volume serial number, you must rerun the BUILDSA function to create a new core image data set with the new volume serial number in the name.
- If you attempt to use the DFSMSdss stand-alone restore program from z/OS V1R11 to restore a backup that was created with a block size greater than 65520 bytes, the operation fails with the message ADRY3530I SEQUENCE ERROR ON RESTORE TAPE.
Reference information
For more information, see z/OS DFSMSdfp Storage Administration.