I don't have all the technical details, but there tends to be occasional DASD movement where FDRPAS is used to non-disruptively "move' the contents of a volume from one unit address to another. Where I fit in is I have written a (rexx based) automation routine that displays old/current IPL information to new/requested IPL information for operator verification, but used the STORAGE() function to collect that information. After discovering "moved" volumes don't reflect current values when using STORAGE(), I switched to parsing console command output. It's not the end of the world doing so, but I end up getting 50 words to look at when I am only interested in 1.
On Wed, Dec 16, 2020 at 10:44 PM kekronbekron < 000002dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote: > Just me being dumb.. what do you mean by 'IODF volume moved'? > > - KB > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, December 17, 2020 10:06 AM, Steve Horein < > steve.hor...@gmail.com> wrote: > > > Thanks! > > It looks like I get the same behavior with what Mark uses: > > > > IPALPDDV = Storage(D2x(ECVTIPA + 92),4) /* load parm dev number */ > > > > On a system that had the IODF volume "moved", the old address is also > > present in IPALPDDV. Bummer. > > > > On Wed, Dec 16, 2020 at 8:15 PM kekronbekron < > > 000002dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote: > > > > > Hi Steve, > > > This should be in Mark Zelden's IPLINFO source code - > > > http://www.mzelden.com/mvsfiles/iplinfo.txt > > > > > > - KB > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > On Wednesday, December 16, 2020 10:29 PM, Steve Horein < > > > steve.hor...@gmail.com> wrote: > > > > > > > Hi! > > > > I am able to determine the IODF unit address from IPAIODFU in IPA. > > > > However, > > > > this value becomes stale if the address changes when the storage > folks > > > > move > > > > disk around. I can see the MVS command DISPLAY IPLINFO accounts for > those > > > > changes in message IEE254I: > > > > IEE254I hh.mm.ss IPLINFO DISPLAY text > > > > Explanation: Where text is: > > > > SYSTEM IPLED AT hh.mm.ss ON mm/dd/yyyy > > > > RELEASE fmid LICENSE = system > > > > USED LOADxx IN loadxxdsname ON devx > > > > ARCHLVL = n MTLSHARE = Y N > > > > IEASYM LIST = s1 NONE > > > > IEASYS LIST = s2{(OP)} > > > > IODF DEVICE: ORIGINAL(iodfdev1) CURRENT(iodfdev2) > > > > IPL DEVICE: ORIGINAL(ipldev1) CURRENT(ipldev2) VOLUME(iplvol) > > > > Is there an accessible (lives in COMMON), supported data area that > also > > > > contains the "CURRENT" information that is present in the DISPLAY > > > > command? > > > > While I can parse the output of a console command, I would much > rather > > > > fetch only the desired information from storage, if possible. > > > > Thanks, > > > > Steve Horein > > > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
