All,
Sorry about that. Thought I had the answer. After trying this again myself,
several times, with several changes to the REXX code and more diagnostics, I
finally hit the books.
What your doing looks fine except for one thing listed in the book:
Interactive System Productivity Facility (ISPF) Services Guide z/OS Version 1
Release 2.0
Document Number SC34-4819-01
2.28.3 Parameters
list-id
The LMDFREE service removes this dslist ID from the list of dslist IDs.
The LMDLIST and LMDFREE service cannot use the dslist ID for the
remainder of the TSO session.
It says there that even if you free a dslist ID, you can't use it again for the
remainder of that TSO session. Which I don't really understand either, because
a re-exec of the REXX gives the same results again, rather than empty lists.
Furthermore, changing the second dslist ID to something different yields the
same results - just the vtocix is listed - for either the same volume or any
other volume I cared to plug in (even when the second volume listed didn't
match the first!).
This may be a "broke" rather than a WAD, or we just don't have the right code
to flush the LMDLIST internal list within the same REXX.
Still looking.
Gary
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of TISLER Zaromil
Sent: Friday, November 11, 2005 8:11 AM
To: [email protected]
Subject: Re: LMDLIST, strange behaviour or WAD?
Sorry.
<snip>
- second part: only the dataset name
<snip>
should be:
- second part: only the last dataset name
^^^^
Zaromil
----------------------------------------------------------------------
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
