Hello Bob (and anybody else who's watching this thread), So I've been pondering this one for a few days, trying some things on my own test system, and I am still not sure what's going on here.
The messages for the working example you showed below - the UNIT=WRK case - look like what you would expect for a successful allocation of a non-SMS managed data set on a system with SMS active (which is what you're hoping for.) The failing example - the UNIT=WORK case, where you got the IEF506I, IEF877E, IEF238D - look like what you would expect for a non-SMS managed data set, where all of the devices in the esoteric are offline. (If SMS chose a storage group, I think you would see different messages.) The behavior looks like the esoterics are valid - if the esoterics weren't defined in the IODF, and SMS didn't choose a storage group (so we actually tried to choose devices using the esoteric) you would get different messages. I did a few experiments creating esoterics in my IODF, just to compare - and the LISTEDT LUV output looks reasonable (the lookup values look reasonably well constructed, etc.) The EDT is a complicated set of structures, so it's possible there's something else wrong, but without reviewing the entire LISTEDT DETAIL output (which is usually huge) it's hard to say. Given the weird behaviors - also with the UNIT=BAT/BATCH behavior, and your concerns about the way the SMS SCDS was built - it might be worth looking at the SMS ACS routines (particularly the STORCLAS and STORGRP routines) to see what they're doing. I don't think they can modify the request in a way that would cause this behavior, although my knowledge around ACS processing is limited. -Scott Ballentine ([email protected]) IBM z/OS Allocation Development On Tue, 23 Sep 2025 09:39:45 -0500, R Dooley <[email protected]> wrote: >Hi Scott, >Thank you for the reply. > >- PLOT TWIST: Discovered yday that in addition to "UNIT=WORK" esoteric being >impacted, "UNIT=BATCH" also produces the "IEF877E Device Offline" reply >message. Albeit, "UNIT=BAT" works. > >- The SMS CDS' were copied from another system then "stripped down" versus >starting with a scratch set of CDS and building it out. This was not my >decision and it concerns me that there may be "residue" from the source LPAR. > >- In HCD these devices are not defined w/ a token. Internet search mentions >that token mismatch can cause this sort thing however, using IPCS to review >could not definitely rule this out. (see add'l info below) > >- Allocation msgs for UNIT=WRK included below. UNIT=WORK job's msg log >consists of only the IEF506I msg. > >Best regards, >Bob > > >All the messages from the UNIT=WRK job (that works): ==> >---------------------------------------------------------------------------> >//ALLOC1 DD UNIT=WRK,DISP=(NEW,CATLG), >// DSN=<mine>.WRK.T&HHMMSS., >// SPACE=(TRK,(1,1,0)), >// DCB=(LRECL=80,RECFM=FB,BLKSIZE=0) > >ICH70001I <mine> LAST ACCESS AT 16:35:43 ON MONDAY, SEPTEMBER 22, 2025 >IEFA111I <mine> IS USING THE FOLLOWING JOB RELATED SETTINGS: > SWA=ABOVE,TIOT SIZE=32K,DSENQSHR=DISALLOW,GDGBIAS=JOB >IEF236I ALLOC. FOR <mine> STEP1 >IGD100I 1182 ALLOCATED TO DDNAME ALLOC1 DATACLAS ( ) >IEF142I <mine> STEP1 - STEP WAS EXECUTED - COND CODE 0000 >IEF285I <mine>.WRK.T204358 CATALOGED >IEF285I VOL SER NOS= WRK104. > >---------------------------------------------------------------------------------------------------------------------------- > >IPCS ==> >------------- >LISTEDT LUV: (UNIT=WORK and UNIT=WRK) >Index: 000E +125BB2B4 WORK Unitname > +125BB2BC 00082000 Lookup Value For Unitname > +125BB2C0 0000000E Index of Group Mask Entry > +125BB2C4 00000000 Index of Alternate Group Mask > +125BB2C8 00000001 Number of Generic > +125BB2CC 0800FFFF Flags = Name is Esoteric > +125BB2D0 000E Index of First Generic > +125BB2D2 000F Index of Next Entry > +125BB2D4 00000001 Total Number of Groups for Unitname > +125BB2D8 00000009 Total Number of Devices for Unitname > +125BB2DC 00000000 Index of Library Section Entry > +125BB2E0 00000000 Number of Compatible Generics > +125BB2E4 00000000 Index of First Compatible Generic > >Index: 000F +125BB2E8 WRK Unitname > +125BB2F0 00092000 Lookup Value For Unitname > +125BB2F4 0000000F Index of Group Mask Entry > +125BB2F8 00000000 Index of Alternate Group Mask > +125BB2FC 00000001 Number of Generic > +125BB300 0800FFFF Flags = Name is Esoteric > +125BB304 000F Index of First Generic > +125BB306 0010 Index of Next Entry > +125BB308 00000001 Total Number of Groups for Unitname > +125BB30C 00000009 Total Number of Devices for Unitname > +125BB310 00000000 Index of Library Section Entry > +125BB314 00000000 Number of Compatible Generics > +125BB318 00000000 Index of First Compatible Generic > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
