OK, I stand enlightened. A particular extent can be identified by unit address and from there back to volser. I abide by my previous post. I would rather see IBM work on more productive enhancements. Seriously, how long does it take to debug a broken APF environment? It happens rarely, and with any experience at all the cause is clear. An application can test for APF and put out a message telling the user to investigate. (Abending is shameful.) That should be good enough.
Also note that if APF is broken, the app might be hard put to issue commands or chase control blocks. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Friday, November 18, 2016 12:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Which STEPLIB concatenation is not authorized? On 11/18/2016 9:43 AM, Jesse 1 Robinson wrote: > The fundamental difficulty of displaying/presenting the concatenation > sequence goes to the heart of program fetch and DEB management in general. > The mapping for a concatenation consists of a series of track extents for > input I/O; VOLSER identity is not part of the map. Not sure I agree with this. The DEB extent entry doesn't list the volser per se as a 6-byte character field, but it does have the 4-byte UCB address which is even better because with that you can find out not only volser but every else about the unit... -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
