The job that requests the DD that has the faulty volser has nothing to do with the console, it's just doing its thing. It's just that while it has the IEF238D outstanding, you cannot vary consoles.
Neither device; the non-existent volser, (which obviously does not have a unit), nor the console, is allocated to any address space on any LPAR while this behavior is in effect. If I cancel the job (IEFBR14 with fault DD to test this) that specifies the non-existent volume, the outstanding IEF238D would drop its ENQ, and I can vary consoles all day long. When I do they get allocated to the CONSOLE address space like they should. Retry on the vary <dev>,console while IEF238D was pending would just reissue the same IEE799D message. _Jan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: dinsdag 25 augustus 2015 11:21 To: [email protected] Subject: Re: vary <dev>,console with an IEF238D outstanding. Cannaerts, Jan wrote: >Does anyone have an insight on the technical limitations that cause the >following behavior? >While there is an IEF238D outstanding, in our case because some DD specified a >nonexistent volser, "vary <dev>,console" gives us IEE799D. What type of console is it? What is the DD doing with a volser AND console? Can you issue a D U to see by what A/S in what LPAR is that device allocated? What do you see with D GRS,C? What do you see if you try out this: REPLY ??,RETRY Also check what Barbara Nitz asked. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
