A fix is available
APAR status
Closed as new function.
Error description
New Function
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: This APAR is part of the full function * * support for Release 4.0 of the TS7700 * * Virtualization Engine D/T3957. * **************************************************************** * PROBLEM DESCRIPTION: New Function Support for Release 4.0 * * of the TS7700 Virtualization Engine. * **************************************************************** * RECOMMENDATION: For full support, install APAR OA49373 * * (z/OS V2R1 and V2R2). OA49373 brings in * * the necessary support from all other * * components (OA49374 and OA49375). * **************************************************************** TS7700 Release 4.0 Information: ------------------------------- This APAR was developed as part of the full function support for Release 4.0 of the TS7700 Virtualization Engine D/T3957. For a full discussion of the TS7700 Release 4.0 enhancements refer to the TS7700 Knowledge Center: http://www.ibm.com/support/knowledgecenter/STFS69/welcome APAR OA49375 provides enhancements to the IEF_ALLC_OFFLN (Allocated/Offline Device) Installation exit. The exit is now passed device prioritization information in a system-managed tape library environment. This additional information can be used by the exit when choosing a device to be brought online.
Problem conclusion
Temporary fix
Comments
This APAR is part of the full function support for Release 4.0 of the TS7700 Virtualization Engine D/T3957. This APAR specifically provides new function for the IEF_ALLC_OFFLN Installation exit to supply device prioritization information in a system-managed tape library environment. See the documentation included with this APAR for additional details. DOCUMENTATION HOLD FOR APAR OA49375 o Book Title- z/OS V2R2 MVS Data Areas Volume 4 o ORDER NO- GA32-0938 o Book Title- z/OS V2R1 MVS Data Areas Volume 6 o ORDER NO- GA32-0940 +--- LOCATION IN PUBLICATION ---------------------------+ | | | UXPARMD Information | | UXPARMD mapping | | | +-------------------------------------------------------+ This section is updated with the following information. Changes are indicated with revision bars: Structure UXPARMD Offset Dec Hex Type Len Name (Dim) Description ========================================================= ... 110 (6E) BITSTRING 1 REQTYINF REQuest TYpe INFo 1... .... UXDYNAMC X'80'" This is a Dynamic Allocation Request. | .1.. .... UXPRVALD "X'40'" OFFLINE | device table contains | valid priority | information ... Structure UXOFLTBL Offset Dec Hex Type Len Name (Dim) Description ========================================================= ... | 9 (9) BITSTRING 1 UXDEVPRI Device priority | value ... Cross Reference for UXPARMD Name Offset Hex Tag ========================================================= ... | UXDEVPRI 9 ... | UXPRVALD 6E 40 ... o Book Title- z/OS MVS Installation Exits o ORDER NO- SA23-1381 +--- LOCATION IN PUBLICATION ---------------------------+ | | | The Exits | | IEF_ALLC_OFFLN - Allocated or Offline Device | | Installation Exit | | Selecting an Eligible System-Managed Tape Library | | Device | | Selecting an eligible tape library device based on | | device priority | +-------------------------------------------------------+ This new section is being added with the following information: Selecting an eligible tape library device based on device priority The device priority value (UXDEVPRI) is added with OA49375 (z/OS V2R1 and above) and is used in a system-managed tape environment to reflect device preference information: - The priority value is a number from 0-255, where 255 is the "best" or "preferred" value, and 0 is the "worst" value. - The priority value isn't unique (so multiple devices may have the same value). - All of the priority values may not be used. So for a given request, the best device the exit sees may have a priority value of 250 instead of 255, or the best device might be 255 and the next best device might be 245, for example. - Some allocation requests may not be prioritized, so for those requests the priority value would be 0. Bit flag UXPRVALD indicates whether the devices in the offline device list have been assigned priority values. The devices in the list are presented in the same order that they were prior to OA49375. Priority values are expected to be returned in the following cases: - The Device Allocation Assist (DAA) function is being used in the TS7700 Virtualization Engine to prioritize which clusters (or distributed libraries) should be preferenced on a specific mount request. - When multiple libraries are eligible for a scratch request, some libraries may be above scratch threshold, and others may be below scratch threshold. Devices in libraries that are above scratch threshold will see a priority value of 255 and devices that are in libraries that are below scratch threshold will receive a priority value of 254. +--- LOCATION IN PUBLICATION ---------------------------+ | | | The Exits | | IEF_ALLC_OFFLN - Allocated or Offline Device | | Installation Exit | | The Offline Device Table | +-------------------------------------------------------+ This section is updated with the following information. Changes are indicated with revision bars: ... Bytes Contents 1-4 contain the device number (in EBCDIC). 5 the UXSTATUS field contains information about the offline status of the device. | 6 priority value 7-12 contain the VOLSER of the pending offline permanently resident DASD or reserved device is a volume is mounted. The format of the offline device table follows: --------------------- |Number of Entries | |(4 bytes) | |-------------------------------------------------------- | | Device Number | Status | Priority | Pending-offline | | | (4 bytes) | (1 byte) | (1 byte) | Volser (6 bytes)| |-------------------------------------------------------| |-------------------------------------------------------| | | Device Number | Status | Priority | Pending-offline | | | (4 bytes) | (1 byte) | (1 byte) | Volser (6 bytes)| --------------------------------------------------------- . . --------------------------------------------------------- | | Device Number | Status | Priority | Pending-offline | | | (4 bytes) | (1 byte) | (1 byte) | Volser (6 bytes)| ---------------------------------------------------------
APAR Information
APAR number
OA49375
Reported component name
ALLOCATION
Reported component ID
5752SC1B4
Reported release
790
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2015-11-12
Closed date
2016-05-12
Last modified date
2016-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA81666 UA81667
Modules/Macros
IEFAB48A IEFZB481
| GA320938XX | GA320940XX | SA231381XX |
Fix information
Fixed component name
ALLOCATION
Fixed component ID
5752SC1B4
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":"790","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":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 June 2016