A fix is available
APAR status
Closed as new function.
Error description
New Function APAR
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users at HBB7760 and HBB7770 * **************************************************************** * PROBLEM DESCRIPTION: New function to support IPL of z/OS * * and SADMP from DASD in an alternate * * subchannel set. (D/T2817 D/T2818) * **************************************************************** * RECOMMENDATION: * **************************************************************** Because z/OS and SADMP can only be IPLed from devices in subchannel set zero, users must define the PPRC secondary devices for the IPL volume, IODF volume and SADMP volume in subchannel set zero. This is burdensome for users whose environment is device number constrained.
Problem conclusion
Temporary fix
Comments
This support allows z/OS and SADMP to be IPLed from devices in an alternate subchannel set. Users may define the PPRC secondary devices for the IPL, IODF, and SADMP volumes in a subchannel set other than zero. Then SADMP and z/OS can be IPLed from the currently active subchannel set after a Hyperswap has occurred. Note: This support is intended for HyperSwap environments in which an alternate subchannel set is used where the device numbers for the IPL volume, the IODF volume, and the SADMP volumes are identical between the primary and alternate subchannel set. This support is not intended for HyperSwap environments in which a HyperSwap will swap between different device numbers within subchannel set zero. For IPL'ing z/OS: A H/W enhancement, which is required for this support, allows a 5-digit device number to be specified for th z/OS IPL device. The first digit indicates the subchannel set. LOADxx IODF statement: ---------------------- Column 36 of the IODF statement in LOADxx is the subchannel set indicator. This field indicates which subchannel set should be used as the primary volume during IPL. An asterisk "*" may now be specified for this value. Specification of an "*" for this field indicates that the subchannel set of the IPL volume should be used as the subchannel set for the primary volumes. DIAGxx AUTOIPL statement: ------------------------- The device number specification on the SADMP and MVS operands of the AUTOIPL DIAGxx statement is updated to accept an "*" before the 4-digit device number. The "*" denotes that the device from the active subchannel set should be used. If no "*" appears before the 4-digit device number, AUTOIPL processing will use the device in subchannel set 0. For example: AUTOIPL SADMP(*0180,SP03E0 ) MVS(*0181,0181MG ) Note: With This support, the use of "*" is only intended for HyperSwap environments where the HyperSwap will occur between identical device numbers in alternate subchannel sets. DISPLAY IPLINFO: ---------------- Message IEE254I is issued for the DISPLAY IPLINFO command. 5-digit device numbers are shown in message IEE254I for IPL, IODF, and LOADxx devices as in the following example: SY1 IEE254I 12.33.20 IPLINFO DISPLAY 045 SYSTEM IPLED AT 12.26.41 ON 08/01/2011 RELEASE z/OS 01.rr.mm LICENSE = z/OS USED LOADMG IN SYS0.IPLPARM ON 00343 ARCHLVL = 2 MTLSHARE = N IEASYM LIST = (CB,L) IEASYS LIST = (MD) (OP) IODF DEVICE: ORIGINAL(00343) CURRENT(00343) IPL DEVICE: ORIGINAL(00980) CURRENT(00980) VOLUME(ZRP21 ) DISPLAY DIAG: ------------- The display of the AUTOIPL options is updated as follows: 1. If an "*" is prefixed to the SADMP device or MVS device in the DIAGxx member, it is shown on the AUTOIPL line of IGV007I, for example: AUTOIPL SADMP(*0180,SP03E0 ) MVS(*0181,0181MG ) 2. If MVS(LAST) was specified in DIAGxx, DISPLAY DIAG will show the device number of the currently active SYSRES, prefixed by an "*" to denote the currently active subchannel set. For example: AUTOIPL SADMP(NONE) MVS(*0980,0181MG ) Note: The "*" indication is only meaningful in a HyperSwap environment in which alternate subchannel sets are used. If this is not a HyperSwap environment or, if a HyperSwap environmentin which alternate subchannel sets are not used then the "*" indicates subchannel set zero. Further, MVS with the "LAST" option may not achieve the desired results in a HyperSwap environment where alternate subchannel sets are not used, if a HyperSwap has occurred and there has been no intervening IPL since the Hyperswap. Stand-Alone Dump (SADMP): ----------------------- There are two processes involving SADMP, the SADMP IPL program generation and the SADMP program initialization. The SADMP IPL program generation process is performed using information specified on the invocation of AMDSADMP macro. The information includes device numbers for the SADMP IPL and output volumes. This process is not updated to allow specification of 5-digit output devices. Instead, it is assumed that the SADMP IPL program is initially generated on a device in the primary subchannel set and then mirrored to an alternate subchannel set device. After a HyperSwap, SADMP can be IPLed from the mirrored copy. It is also assumed that the dump output devices specified at generation time are also mirrored to devices in the same alternate subchannel set as the IPL device so that they will be available when SADMP is IPL'ed from the alternate subchannel set. A H/W enhancement, which is required for this support, allows a 5-digit device number to be specified for the SADMP IPL device. The first digit indicates the subchannel set ID of the device. Message AMD083I is updated to show the subchannel set of the IPL device. If dump output devices were specified at SADMP generation, the device numbers without the subchannel set id are specified. If dump output devices were not specified at SADMP generation time, the operator is prompted through message AMD001A to specify the output device. The device number without the subchannel set is expected in response to this WTOR. SADMP will first look in the subchannel set of the SADMP IPL volume for the specified output device. If the device is not found in that subchannel and that subchannel is not zero, processing will continue by looking for the device in subchannel set 0. =============================================================== = Additional Information = =============================================================== Additional Keywords: MSGAMD083I MSGIEE254I MSGIGV007I WAIT0B1 Supporting APARs: OA35135 - IOS (5752SC1C3) OA35136 - SADMP (5752SC115) OA35137 - IPL (5752SC1C9) OA35139 - CONSOLES (5752SC1B8) OA35140 - VSM (5752SC1CH) Supporting H/W Required (at or above the following level): Driver: 93 EC Stream: N48168 MCL: 085 Note: This support was shipped in the base of HBB7780 for all supporting components. =============================================================== = Documentation Updates = =============================================================== MVS System Commands (SA22-7627), Chapter 1, section on "Loading the System Software", as follows: ... Once the system hardware is ready, you can use the system console to load the system software... ... 2. A=INITIALIZE SYSTEM CONTROL PROGRAM, A1: Specifies the device number that contains the system residence volume (IPL volume). | Note: Depending on your hardware level, the device | number you enter for the IPL volume may be prefixed by | the subchannel set id for the device. The default is | subchannel set 0. ... =============================================================== MVS System Commands (SA22-7627), Chapter 1, section on "Explanation of the A=INITIALIZE SYSTEM CONTROL PROGRAM, A2 Field", as follows: ... The LOAD parameter is eight characters long and contains the following information: 1. The first four characters (characters 1 through 4 of the LOAD parameter) specify the hexadecimal device number for for the device that contains the I/O definition file VSAM data set. This is also the device on which the search for the LOADxx member of SYSn.IPLPARM or SYS1.PARMLIB begins. The device number can be in the range X'0000' to X'FFFF'. If the number is less than 4 digits, specify | leading zeros before the device number. This device must | be in the same subchannel set as the IPL device. If you do not specify the device number, the system uses the device number of the system residence (SYSRES) volume. ... =============================================================== MVS Initialization and Tuning Reference (GA22-7592), Chapter on LOADxx, section on "Placement of LOADxx", as follows: ... Consider placing LOADxx in the SYSn.IPLPARM data set. During IPL, the system looks for LOADxx in the following order: 1. SYS0.IPLPARM through SYS9.IPLPARM on the IODF volume. 2. SYS1.PARMLIB on the IODF volume. 3. SYS1.PARMLIB on the sysres volume. | Note: The IODF volume must be in the same subchannel set | as the IPL device. ... =============================================================== MVS Initialization and Tuning Reference (GA22-7592), Chapter on LOADxx, section "Statements/parameters for LOADxx", as follows: ... IODF The IODF statement identifies... Col Contents ... | 36 Subchannel set indicator. Indicates the subchannel set | IOS uses for normal base devices that have a special | secondary device with the same address. The following | values can be specified: | | 0 Indicates the normal base devices in subchannel | set 0 are used for the IPL. | | n Indicates the special secondary devices in | this subchannel set are used for the IPL. | | * Indicates the subchannel set of the IPL device is | used for the IPL. | | On systems where special secondary devices are | connected, if this value is not specified or is not | valid (for example, not a 0, 1, 2, or *), the system | will prompt the operator with message IEA111D to | determine what subchannel set should be used. Default: None ... =============================================================== MVS System Codes (SA22-7626), Chapter on wait state codes, section on 0B1, as follows: ... System Programmer Response: ... Code Action 01 Verify that the correct device number was specified on the LOAD parameter. Verify that the same volume as | SYSn.IPLPARM or SYS1.PARMLIB and is in the same | subchannel set as the IPL device. Enter the correct IODF data set name in the LOADxx parmlib member. ... 03 Load device does not have the proper subchannel identifier. Verify that the device on which the IODF resides is defined. Verify that the correct device number was specified on the LOAD parameter. Verify that the hardware configuration matches the definitions in | the IODF. Verify that the device on which the IODF | resides is in the same subchannel set as the IPL device. =============================================================== HCD Planning (GA22-7525), chapter on "Planning your I/O configuration definition", section on "Defining a special secondary device (3390D)", as follows: Delete the bullet that reads "IPL and IODF devices cannot have secondaries in subchannel set 1." =============================================================== HCD Planning (GA22-7525), chapter on "Specifying an I/O configuration at IPL", section on "IODF Processing at IPL", as follows: ... To identify the IODF selected at IPL, do the following: 1. Identify the IODF volume...See the processor documentation | for more information. The IODF volume must be in the same | subchannel set as the IPL device. ... =============================================================== HCD Planning (GA22-7525), chapter on "Specifying an I/O configuration at IPL", section on "Using your initial I/O configuration with special secondary (3390D) devices for reIPL", as follows: | If special secondary (3390D) devices are used in an | alternate subchannel set, the operating system must...as primaries and secondaries. In the LOADxx parmlib member, the SCHSET parameter allows | you to specify which subchannel set should be used as the | primary devices for the IPL. You may specify the subchannel | set number to be used for the primary devices or you may | specify an "*". The "*" denotes that the devices in the | same subchannel set as the IPL volume should be brought | online as the PPRC primary devices. ... =============================================================== MVS Data Areas Volume 3 (IEFCITUX-IRDDCE), Section on IOSDIODI map, as follows: Offsets ------- Dec Hex Type/Value Len Name (Dim) Description --- ---- ---------- --- ---------- --------------------- ... | 64 (40) BITSTRING 1 IODI_IODFOSS Original IODF device | subchannel set id | 65 (41) CHARACTER 63 Available ...
APAR Information
APAR number
OA35135
Reported component name
IOS
Reported component ID
5752SC1C3
Reported release
760
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function
Submitted date
2010-12-08
Closed date
2011-08-18
Last modified date
2014-01-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BLWMIPIB BLWRSTOP BLWSWTCH IEAIPL03 IEAVNP02 IOSDCDA IOSDCSC IOSDIODI IOSIOFR IOSVUSER
| SA22762700 | SA22759200 | SA22762600 | GA22752500 |
Fix information
Fixed component name
IOS
Fixed component ID
5752SC1C3
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
15 January 2014