I just submitted this RFE this morning that will address this issue (if/when):

https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=134932

Note that there is another RFE for a LISTDSI enhancement for which the 
developers asked for more input so that implies they may be open to updating 
LISTDSI and if the code is open why not do multiple RFE's 😊


Lionel B. Dyck <sdg><
Website: http://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what you 
are, reputation merely what others think you are." - John Wooden

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Seymour J Metz
Sent: Friday, July 26, 2019 12:17 PM
To: [email protected]
Subject: Re: TSO REXX -- find absolute generation # from relative?

I know that you don't like CSI, but IMHO that's the best way to go. 
Postprocessing the LISTC output is easy, but will break if IBM changes the 
format.

In the long run, have you considered asking IBM for a CI enhancement to allow 
both generation and member in DSN, or to allow relative generations in LISTDSI?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
John McKown <[email protected]>
Sent: Thursday, July 25, 2019 3:47 PM
To: [email protected]
Subject: TSO REXX -- find absolute generation # from relative?

I just don't see any _simple_ way to do this. I need to convert the
gdgbase(0) into gdgbase.GnnnnVnn absolute. Believe it or not, I have a product 
which creates a number of PDS libraries (not PDSE) which are GDG. I want to 
generate some JCL which is the equivalent of:

//SYSUT1 DD DISP=SHR,DSN=GDGBASE(0)(MEMBER)

Which is a JCL error.

--
A sine curve goes off to infinity, or at least the end of the blackboard.
-- Prof. Steiner

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to