The requirement is 'onerous' if you're determined--or required--to run a Rexx in a non-TSO environment such as batch via PGM=IRXJCL. The Rexx manual documents a number of functions as 'TSO/E extensions' that are usable only if PGM=IKJEFTxx.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Friday, October 23, 2015 9:28 AM To: [email protected] Subject: (External):Re: Is there an alternative to SYSDSN(fully.qual.dataset.name) that DOES NOT Recall Migrated Datasets If the OP wanted a function that would not recall a dataset, the LISTDSI would be the solution, even if it has onerous restrictions. But could you elaborate on which restrictions are onerous? Otherwise, I would suggest going to Developerworks and input an RFE to have SYSDSN not recall the file. Another parm like NORECALL would be nice. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Paul Gilmartin > Sent: Friday, October 23, 2015 9:04 AM > To: [email protected] > Subject: Re: Is there an alternative to > SYSDSN(fully.qual.dataset.name) that DOES NOT Recall Migrated Datasets > > On Fri, 23 Oct 2015 07:49:32 -0700, Lizette Koehler wrote: > > >No SYSDSN does not as far as I know have a norecall function. > > > >However LISTDSI does. > > > LISTDSI has the sometimes onerous restriction that it must be issued > from a TSO session. > > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
