Understanding coexistence considerations for 3592 Model E05

Coexistence support for the 3592 Model E05 is provided at z/OS V1R4 and above by installing the needed full-support PTFs without the Device Services enabling PTF. In addition to this, existing device services support (with APAR OA02207) prevents the 3592 Model E05 devices from coming online on a system that does not have all of the full-support PTFs installed. Installation of the Devices Services enabling PTF brings in all of the needed full-support PTFs. You must install the needed coexistence support on systems that will not have all of the 3592 Model E05 support installed. See Table 1 for a discussion of the coexistence PTFs that may be needed. For past discussion of the 3592 Model J1A and its coexistence considerations, refer to Understanding coexistence considerations for 3592 Model J1A.

Note: Full support for the 3592 Model E05 will first be available on z/OS V1R4 and z/OS V1R5 (refer to enabling APAR OA11388) with support for z/OS V1R6 and z/OS V1R7 available after the initial GA (refer to enabling APAR OA13110). Before using the 3592 Model E05, ensure that the appropriate full support and coexistence support is available for all of your system levels. Planned availability for z/OS V1R6 and z/OS V1R7 is year end 2005.

Review the coexistence migration tasks described in these topics:

Table 1. Coexistence migration tasks for 3592 Model E05
Environment	Coexistence considerations
Stand-Alone	As described in Introduction for 3592 Model E05, z/OS DFSMS and related licensed programs provide full support for the 3592 Model E05 and MEDIA5, MEDIA6, MEDIA7, and MEDIA8 with z/OS V1R4 and above, with support for the new media types, MEDIA9 and MEDIA10, being provided with z/OS V1R5 and above. The 3592 Model E05 support enables the tape drives to operate in the stand-alone environment in 3590 Model B1x emulation and to coexist with other 3590-1 or 3490 tape drives. However, prior to using the new 3592 Model E05 tape drives, ensure that all existing 3592 Model J1A tape drives have their microcode upgraded to recognize and enable the EFMT2 formatted cartridges to be relabelled/reused on the 3592 Model J1A. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB. Otherwise, job failures may occur with a drive with the incorrect microcode load being allocated.
IBM Tape Library	As described in Introduction for 3592 Model E05, z/OS DFSMS and related licensed programs provide full support for the 3592 Model E05 and MEDIA5, MEDIA6, MEDIA7, and MEDIA8, with z/OS V1R4 and above, with support for the new media types, MEDIA9 and MEDIA10, being provided with z/OS V1R5 and above. The system-managed tape library support allows the tape drives to operate in an ATL or MTL environment as 3590 Model B1x devices, providing device allocation and tape media management support. As appropriate for the library type and model, this support allows the 3592 Model E05 tape drives to coexist with other 3590-1 tape drives (3590 Model B, E and H and 3592 Model J) in the same tape library. However, prior to using the new 3592 Model E05 tape drives, ensure that all existing 3592 Model J1A tape drives have their microcode upgraded to recognize and enable the EFMT2 formatted cartridges to be relabelled/reused on the 3592 Model J1A. Also, ensure that VOLNSNS=YES is in the DEVSUPxx member of PARMLIB. Otherwise, job failures may occur with a drive with the incorrect microcode load being allocated.
OAMplex	For OAM's object support customers, in addition to the planning steps required for migration to the software support for the 3592 Model E05 tape drives in the stand-alone and IBM tape library environments, there are coexistence considerations your installation must take into account before you install the software in an OAMplex: For the 3592 Model E05 support, OAM object tape coexistence support is provided at z/OS V1R4 and above, through installation of the full support PTF without the device services enabling PTF. OAM coexistence support prevents lower-level systems from selecting volumes with ERDS Physical Identifier (EPI) values for object write requests that are not supported on that system and it also prevents MEDIA9 and MEDIA10 volumes from being selected on a system that is not enabled for the new media support. OAM object support has coexistence considerations when running in an OAMplex environment with at least one system with the full support installed and enabled and at least one system at a release level where the new devices are supported; however, all of the support is not installed and enabled. In this mixed environment, it is possible for a retrireve request to be received for an object, which resides on a tape cartridge volume which was written in the EFMT2 format, by a system that does not have the 3592 Model E05 support installed, or by a system that supports the 3592 Model E05, but does not support the new media types (MEDIA9 or MEDIA10), or both. Coexistence support is provided that allows OAM to attempt to locate an instance of OAM in the OAMplex where the full support is installed and enabled and also, as applicable, to locate an instance of OAM that supports MEDIA9 and MEDIA10. MEDIA9 and MEDIA10 are only supported on z/OS V1R5 and above. If an instance of OAM is found where the request can be processed, the OAM on the system where the request originated will ship the retrieve request to the target system using XCF messaging services. Once 3592 Model E05 devices are used in an OAMplex environment and objects are written to tape volumes with the new EPI value recorded, it is expected that any OAM on a system where the full support is installed and enabled is eligible for processing requests using that volume with the exception of MEDIA9 and MEDIA10 which require z/OS V1R5 or above. Therefore, the devices must be made available to all instances of OAM where the full support is installed.
OCE (Open / Close / End-of-Volume)	In support of the new media types (MEDIA9 and MEDIA10), coexistence support is provided for the new media types on z/OS V1R4 to prevent the new media types from being used on a non-supporting system. With the coexistence support installed, an abend will occur if a MEDIA9 or MEDIA10 volume is mounted on a non-supporting system.
HSMplex	For the 3592 Model E05 support, HSM coexistence support is provided at z/OS V1R4 and above, through installation of the full support HSM PTF without the device services enabling PTF. This allows the coexisting system to reject partial tapes written by the 3592 Model E05 in EFMT2. HSM coexistence support for the new media types (MEDIA9 and MEDIA10) is provided at the z/OS V1R4 level by applying both the OCE and HSM full support PTFs. This will ensure that HSM does not use MEDIA9 or MEDIA10 on a non-supporting system.