APAR status
Closed as canceled.
Error description
See APAR II03288 also...... VTAMINFO TPINFO 566528901 568508501 569511701 MSGIST1386I IST1386I APAR OY57097, OY66240, OY66989 and OY67747 provide a new serviceabilty message to assist diagnosis of Dynamic Allocation problems using VTAM. All the return codes cannot be documented in a single APAR. The following MVS manuals are provided as reference and support to the VTAM Messages and Codes reference to the MVS manuals. In all manuals, refer to the Chapter on SVC99 Functions. 1) Application Development Guide: Authorized Assembler Language Programs MVS/ESA System Product: JES2 Version 4 JES3 Version 4 Document Number GC28-1645-2 Program Number 5695-047 5695-048 2) Application Development Guide: MVS/ESA System Programming Library JES2 Version 3 JES3 Version 4 Document Number GC28-1852 3) Application Development Guide: MVS/ESA System Programming Library MVS/ESA System Product: JES2 Version 5 JES3 Version 5 Document Number GC28-1467-02 Program Number 5655-068 5655-069 Figure 26-6. Class 2 Reason Codes(Unavailable System Resource) |====|===|====================================================== |Hex | | |Code|Dec|Meaning (Action has been removed - see MVS document) |====|===|====================================================== 0204 516 Meaning: Virtual storage unavailable. 020C 524 Meaning: Request for exclusive use of a shared data set cannot be honored. (dsname allocation)(1) 0210 528 Meaning: Requested data set unavailable. The data set is allocated to another job and its usage attribute conflicts with this request. (dsname allocation)(1) 0214 532 Meaning: Device(s) not available; or, if allocating an internal reader, all defined internal readers are already allocated. (dsname allocation)(1) 0218 536 Meaning: Specified volume or an acceptable volume is not mounted, and user does not have volume mounting authorization through the DYNALLOC request. (dsname allocation)(1) 021C 540 Meaning: Device name specified is undefined. (dsname allocation) VTAM Programmer Action: EXAMPLE: VTAM allocates a TPxxx DSname; where xxx=CUA, Channel Unit Address. That generic device type cannot support data set allocations. SMS may give this error if devices are in the authorized list. 0220 544 Meaning: Requested volume not available. (dsname allocation) 0224 548 Meaning: Eligible device types do not contain enough devices. (dsname allocation)(1) 0228 552 Meaning: Specified volume or device in use by system. (dsname allocation) 022C 556 Meaning: Volume mounted on ineligible permanently resident or reserved device. (dsname allocation) 0230 560 Meaning: Permanently resident or reserved volume on required device. (dsname allocation) 0234 564 Meaning: More than one device required for a request specifying a specific device. (dsname allocation) 0238 568 Meaning: Space unavailable in task input output table (TIOT). (dsname allocation, concatenation) 023C 572 Meaning: Required catalog not mounted, and user does not have volume mounting authorization. (dsname allocation) 0240 576 Meaning: Requested device is a console. (dsname allocation) 0244 580 Meaning: Telecommunication device not accessible. (dsname allocation) 024C 588 Meaning: Operating-system-managed resource was unavailable to the subsystem. (dsname allocation)(2) 0250 592 Meaning: Subsystem resource not available. (dsname allocation)(2) 0254 596 Meaning: The TIOT resource is currently unavailable and the user requested conditional ENQ on the resource. (all dynamic allocation functions) 0258 600 Meaning: There was not a sufficient number of non-restricted devices to satisfy the request, or JES3 selected a JES3-managed restricted device to satisfy the request. 025C 604 Meaning: Requested device is boxed and cannot be accessed, as a result of an I/O error condition or the operator issuing a VARY X, OFFLINE, FORCE command. (dsname allocation) 0268 616 Meaning: The tape device is not responding to request; a hardware malfunction might have occurred. (dsname allocation) 026C 620 Meaning: Request requires more SMS-managed volumes than are eligible. 0270 624 Meaning: Request requires more non-SMS-managed volumes than are eligible. 0274 628 Meaning: Telecommunication device deleted from I/O configuration. The accompanying message IEF358I contains the device name information. 0278 632 Meaning: The requested data set is migrated, but the S99NOMIG bit is on. (S99NOMIG is described in "Flags1 (S99FLAG1)" in topic 26.1.5) 0284 644 Meaning: No tape library contains enough devices to satisfy the request. The accompanying message IEF115I contains the number of devices needed. 028C 652 Meaning: Unable to allocate tape devices to the same generic device name. The accompanying message IEF112I contains the device name information. 0290 656 Meaning: The allocation failed because the system could not assign all the required tape devices within one eligible system-managed tape library. The accompanying message IEF333I contains the libraries that are eligible to this allocation request. 0294 660 Meaning: A non-tape-library request specified a tape library device. The accompanying message IEF120I contains the device name information. 0298 664 Meaning: No tape device pools available for allocation. 029C 668 Meaning: There was a library automation communication services (LACS) mount failure for a device in a IBM 3495 Tape Library Dataserver. 02A0 672 Meaning: Attempt to mount a volume on the device specified, but the mount failed. 02A4 676 Meaning: Attempt to allocate a request to a single library failed. The accompanying message IEF333I contains the device and library name information. 02A8 680 Meaning: Attempt to obtain library ID for the requested device failed. The accompanying message IEF155I contains the device name information. 02AC 684 Meaning: A volume required for a non-tape-library request was mounted on library device. The accompanying message IEF151I contains the library and volume name information. 02B0 688 Meaning: A volume required for a tape-library request was mounted on a non-library device. The accompanying message IEF152I contains the library and volume names. 02B4 692 Meaning: The volume required for a tape-library request is mounted on a device in a library that was not eligible. The accompanying message IEF153I contains the library and volume name information. 02B8 696 Meaning: Unable to obtain library status for the specified tape library. The accompanying message IEF156I contains the library name information. 02BC 700 Meaning: A non-tape-library request specified a library device. The accompanying message IEF113I contains the device name information. 02C0 704 Meaning: Unable to allocate a tape device because the device is not in the same library as the requested volume. The accompanying message IEF111I contains the device name and library name information. 02C4 708 Meaning: The allocation failed because the volume record for the specified volume could not be retrieved from the tape configuration database. The accompanying message IEF150I contains the volume serial number. 02C8 728 Meaning: Request failed for a library record from the tape configuration database. (1) The conditions that cause these return codes are detected by MVS or JES3. (2) The information reason code contains a subsystem-defined value to further describe the error. This value is documented in publications associated with the particular subsystem.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR to document Dynamic Allocation Return Codes. APAR created by VTAM to provide MVS manual numbers for the SVC99 (0A63) return codes found in IST1386I MSGIST1386I. Each release of MVS may supply a different manual name.
APAR Information
APAR number
II09616
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1996-07-26
Closed date
1996-07-26
Last modified date
2001-01-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
18 January 2001