LISTDSI alternative?
I've got a clist performing LISTDSI on a dd name to see if it is allocated. Unfortunately, this doesn't work if the file is allocated to VIO. Is there an alternative to LISTDSI that will tell whether a ddname is allocated? Thanks, Cathy -- 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
Re: LISTDSI alternative?
Not sure how I would use ISRDDN in a clist? I've considered parsing LISTALC output, but was just wondering if there was an easier way. Thanks, Cathy -- 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
Re: LISTDSI alternative?
On Thu, 19 Jun 2008 15:01:01 -0500, Cathy Taddei <[EMAIL PROTECTED]> wrote: >I've got a clist performing LISTDSI on a dd name to see if it is allocated. >Unfortunately, this doesn't work if the file is allocated to VIO. Is there an >alternative to LISTDSI that will tell whether a ddname is allocated? > What about (TSO) LISTALC STATUS? What exactly is the problem / issue? I ask, because I ran into a problem with VIO and IPLINFO using LISTDSI a while back. I changed my ISPF panel data set to a temp PDS and then used LISTDSI to find the DDNAME so I could write to it with REXX EXECIO. This failed in some environments that changed the allocation to VIO (via SMS rules). I then changed the allocation of the library to PDSE and that worked in some environments that checked for PDSE and didn't try to allocated it to VIO. But since PDSE can't be in VIO, it failed in other environments. Eventually I did it the correct way and used ISPF services (LM*) to write to the temp PDS (as opposed to EXECIO). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: LISTDSI alternative?
Cathy - try this simple exec that you can call from your exec. If you get a return code of 0 then it is allocated and if you get a 4 then it is not allocated /* rexx to test if a dd is allocated */ arg ddname call outtrap 'isa.' 'listalc sta sys' call outtrap 'off' do i = 1 to isa.0 select when word(isa.i,2) = ddname then exit 0 when word(isa.i,1) = ddname then exit 0 otherwise nop end end /* * * DD Not Found * * */ exit 4 Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We're here to make lives better." I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- 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
Re: LISTDSI alternative?
On Thu, 19 Jun 2008 15:01:01 -0500 Cathy Taddei <[EMAIL PROTECTED]> wrote: :>I've got a clist performing LISTDSI on a dd name to see if it is allocated. :>Unfortunately, this doesn't work if the file is allocated to VIO. Is there an :>alternative to LISTDSI that will tell whether a ddname is allocated? ALLOC F(ddname) DA(*) will generate RC>0 if the DDNAME is already allocated. What happens when LISTDSI is issued against VIO? RC=4 would indicate that the DDNAME is allocated. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- 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
Re: LISTDSI alternative?
Thanks, Mark. The problem is with a vendor-provided clist. They've given me a workaround that involves locally modifying a bunch of their clists, which I'll have to track and refit if they should provide PTF's (it's not SMP-maintained). I thought I'd make it easier on myself by updating the one exec that has the listdsi in it. It looks like listalc is my best bet. Although I am starting to question the value of VIO... Cathy On Thu, 19 Jun 2008 15:28:09 -0500, Mark Zelden <[EMAIL PROTECTED]> wrote: > >What about (TSO) LISTALC STATUS? > >What exactly is the problem / issue? I ask, because I ran into a problem with >VIO and IPLINFO using LISTDSI a while back. I changed my ISPF panel data set >to a temp PDS and then used LISTDSI to find the DDNAME so I could write >to it with REXX EXECIO. This failed in some environments that changed the >allocation to VIO (via SMS rules). I then changed the allocation of the >library to PDSE and that worked in some environments that checked >for PDSE and didn't try to allocated it to VIO. But since PDSE can't be >in VIO, it failed in other environments. Eventually I did it the correct >way and used ISPF services (LM*) to write to the temp PDS (as opposed to >EXECIO). > >Mark >-- >Mark Zelden >Sr. Software and Systems Architect - z/OS Team Lead >Zurich North America / Farmers Insurance Group - ZFUS G-ITO >mailto:[EMAIL PROTECTED] >z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ >Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html > -- 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
Re: LISTDSI alternative?
Thanks, Lionel. Nice and compact! Cathy On Thu, 19 Jun 2008 13:30:56 -0700, Lionel B Dyck <[EMAIL PROTECTED]> wrote: >Cathy - try this simple exec that you can call from your exec. If you get >a return code of 0 then it is allocated and if you get a 4 then it is not >allocated > >/* rexx to test if a dd is allocated */ >arg ddname >call outtrap 'isa.' >'listalc sta sys' >call outtrap 'off' >do i = 1 to isa.0 > select > when word(isa.i,2) = ddname then exit 0 > when word(isa.i,1) = ddname then exit 0 > otherwise nop > end > end >/* * > * DD Not Found * > * */ > exit 4 -- 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
Re: LISTDSI alternative?
Hi Binyamin. LISTDSI only works on DASD -- it gives RC=16 for VIO. Cathy On Thu, 19 Jun 2008 23:58:33 +0300, Binyamin Dissen <[EMAIL PROTECTED]> wrote: >ALLOC F(ddname) DA(*) will generate RC>0 if the DDNAME is already allocated. > >What happens when LISTDSI is issued against VIO? RC=4 would indicate that the >DDNAME is allocated. > >-- >Binyamin Dissen <[EMAIL PROTECTED]> >http://www.dissensoftware.com > >Director, Dissen Software, Bar & Grill - Israel -- 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
Re: LISTDSI alternative?
>Although I am starting to question the value of VIO... As well you should. As a performance/capacity analyst for over 27 years, I used to recommend VIO for small datasets (small has increased over that period), but now I don't think it's worth it, any more. DASD is so fast, cache and channels are fast and we can do in memory buffering, so VIO is (mostly) a thing of the past. Especially for overhead-fetishists, since the CPU to do VIO is higher than that to do real I/O. - Too busy driving to stop for gas! -- 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
Re: LISTDSI alternative?
Thanks for your feedback, Ted. I have passed it along to my MVS systems programmers. Cathy On Thu, 19 Jun 2008 22:00:23 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >>Although I am starting to question the value of VIO... > >As well you should. >As a performance/capacity analyst for over 27 years, I used to recommend VIO for small datasets (small has increased over that period), but now I don't think it's worth it, any more. > >DASD is so fast, cache and channels are fast and we can do in memory buffering, so VIO is (mostly) a thing of the past. >Especially for overhead-fetishists, since the CPU to do VIO is higher than that to do real I/O. > >- >Too busy driving to stop for gas! > >-- >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 -- 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
Re: LISTDSI alternative?
On Thu, 19 Jun 2008 15:28:09 -0500, Mark Zelden wrote: > >What exactly is the problem / issue? I ask, because I ran into a problem with >VIO and IPLINFO using LISTDSI a while back. I changed my ISPF panel data set >to a temp PDS and then used LISTDSI to find the DDNAME so I could write >to it with REXX EXECIO. This failed in some environments that changed the >allocation to VIO (via SMS rules). I then changed the allocation of the >library to PDSE and that worked in some environments that checked >for PDSE and didn't try to allocated it to VIO. But since PDSE can't be >in VIO, it failed in other environments. Eventually I did it the correct >way and used ISPF services (LM*) to write to the temp PDS (as opposed to >EXECIO). > How was the temp panel data set allocated? Perhaps by a profile or by JCL, or by a DYNALLOC in a Rexx exec? If the last, the RTDDN operand of BPXWDYN returns the DDNAME to you. -- gil -- 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
Re: LISTDSI alternative?
On Thu, 19 Jun 2008 20:34:08 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote: >> >How was the temp panel data set allocated? Perhaps by a profile >or by JCL, or by a DYNALLOC in a Rexx exec? If the last, the >RTDDN operand of BPXWDYN returns the DDNAME to you. > Finding the DDNAME wasn't the problem. I generate a random DDNAME [1] I use TSO ALLOCATE. The problem was I needed to know the exact data set name allocated so I could do a 2nd ALLOCATE of the temp PDS with member name included to write the panel PDS member with EXECIO. When the data set was allocated to VIO I could not find the DSN using LISTDSI in order to do the 2nd allocate. Using all the proper LM* ISPF services is a little slower, but it is the correct way to handle it and it always works. Current code: http://home.flash.net/~mzelden/mvsfiles/iplinfo.txt look for "BROWSE_ISPF:" [1] IPLINFO history: The ddname was was also part of the DSN going back to when I allocated a non-temp dsn for the panel lib and output of IPLINFO. That way there would not be a duplicate dsn if you executed IPLINFO multiple times recursively (or in other logical sessions), were blown off TSO or something failed in the exec or if you But that would leave an orphan data set under your userid HLQ - similar to what could happen with ISPF list/log dsns. Which why I wanted to change it all to temp dsns. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Reallocating temp dsn (was: LISTDSI alternative?)
On Fri, 20 Jun 2008 08:20:07 -0500, Mark Zelden wrote: > >I use TSO ALLOCATE. The problem was I needed to know the exact data >set name allocated so I could do a 2nd ALLOCATE of the temp PDS with >member name included to write the panel PDS member with EXECIO. >When the data set was allocated to VIO I could not find the DSN using >LISTDSI in order to do the 2nd allocate. Using all the proper LM* ISPF >services is a little slower, but it is the correct way to handle it and it >always works. > >Current code: > http://home.flash.net/~mzelden/mvsfiles/iplinfo.txt >look for "BROWSE_ISPF:" > Thanks. Uh, yah. Been there; couldn't do that (but I didn't try LM*). If I use BPXWDYN( 'alloc RTDDN(DD) RTVOL(V) RTDSN(DS) ...' ) to allocate it to DASD, I can process it with EXECIO using the returned DDNAME, and later reallocate it to a different DDNAME using the returned volume and dsn. But if I allocate it to VIO, the returned volume and dsn are insufficient to reallocate it. Circumventions: o I don't use VIO. o I pass the returned ddname to the utility in an alternate ddname parameter. o I allocate to the DDNAME I intend to use later. This can look bizarre: call BPXWDYN( 'alloc dd(SYSIN) unit(VIO) ...' ) 'EXECIO' stem.0 'DISKW SYSIN (stem stem.' As someone suggested earlier, who needs VIO nowadays? But the academic question remains: Is it possible to dynamically reallocate a VIO data set to a different DDNAME? Rexx? Otherwise (other than JCL referback)? How does JCL do it? -- gil -- 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
Re: Reallocating temp dsn (was: LISTDSI alternative?)
On Fri, 20 Jun 2008 09:52:09 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote: >Circumventions: > >o I don't use VIO. Can't control what other shops use or do in SMS code. > >o I pass the returned ddname to the utility in an alternate ddname parameter. > >o I allocate to the DDNAME I intend to use later. This can look bizarre: > >call BPXWDYN( 'alloc dd(SYSIN) unit(VIO) ...' ) >'EXECIO' stem.0 'DISKW SYSIN (stem stem.' Again, I needed to do the EXECIO to a PDS member. > >As someone suggested earlier, who needs VIO nowadays? Can't control what other shops use or do in SMS code. >But the academic >question remains: Is it possible to dynamically reallocate a VIO data >set to a different DDNAME? Rexx? Otherwise (other than JCL referback)? >How does JCL do it? > -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
