> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John
> Sent: Wednesday, June 28, 2006 11:28 AM
> To: [email protected]
> Subject: Allocation Error
>
>
> Hi, All,
>
> Anybody have an idea what this means:
>
> "Individual General Device Element (IGDE) not found."
>
> This is all the explanation there is for abend S05C, reason 0229. The
> job log does not identify which dataset(s) caused the problem. It's a
> DFSORT step that uses tape for both SORTIN and SORTOUT, DASD
> work packs
> for SORTWKnn and JES SYSOUT for the logs, etc.
>
> TIA,
How about this one, from IBMLink:
<quote>
When an esoteric contains both DASD and Tape, there is the possibility
of encountering an abend05c rc229. In the reported problem, the
esoteric SYSDA was changed to contain both DASD and tape. It is
documented in the HCD Planning Manual, section 'Specifying an Esoteric
Device Group for Allocation' that the group named SYSDA must include
only direct access devices.
</quote>
Item 0A16668
==
Also there are a lot of things about tape I/O errors causing a SWAP, but
before replying "GO" to the swap, the operator varies the tape drive
offline. This causes DDR to "mess up" the UCB.
example: APAR 0A13707
<quote>
ABEND05C RC229 SEEN WHEN A Z/OS VARY ONLINE IS DONE TO A "MANAGED"
DEVICE AFTER THE DEVICE WENT OFFLINE
An ABEND05C rc229 may be seen when a z/OS vary online is done
to a tape device which is managed by JES3 or OEM. When managed
by JES3 or certain OEMs, tape devices are assigned by multiple
system at the same time. A VARY ONLINE,SHR also causes this
assignment which is denoted in the UCB by the UCBMASGN bit.
When these tape devices are varied offline, they are
unassigned and the UCBMASGN bit should be cleared. If the
unassign fails, the UCBMASGN bit may be left on. When these
devices are varied back online using the z/OS vary online
command as opposed to a JES3 or OEM vary online, allocation sees
that the UCBMASGN bit is on and bypasses building an IGDE for
the tape devices since it appears to already be assigned. This
results in an ABEND05C rc229 whenever a job considers this
device for allocation.
In the reporting case, the unassigns failed due to a no paths
condition to the device when it was varied offline:
IOS002A xxxx,NO PATHS AVAILABLE
Note: This is similar to OA04106/OA06708.
</quote>
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
