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
