Or you can use the SDSF ISFSLASH command to do a D GRS,RES=(*,dsn) Ant.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Thursday, 14 March 2013 8:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: jj$lwa - list of allocated userids The CBTTAPE website has several incarnations of WHOHAS, some actually called WHOHAS (file 139, 167, 300, 716, 732), one called SYSDSN (file 160), another called QCB (file 300), and probably a few more I didn't find in a quick scan. Possibly one of those could work for you. If you can find one that just displays the data by writing to SYSPRINT/SYSOUT/etc., you might be able to capture the data with OUTTRAP and get it to the Rexx code that way. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roy Reynolds Sent: Wednesday, March 13, 2013 2:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: jj$lwa - list of allocated userids I have a batch REXX process that attempts to allocate a dataset exclusive. Before attempting this I'd like to invoke a program that creates a list of userids allocated to the dataset and VPUTs the list to an ISPF shared variable pool. Then the calling REXX exec can VGET the list and parse it to write the User list in an email, explaining why the exclusive allocation will fail. In interactive ISPF I use JJ$LWA ( I don't have RACF operator auth) but I need a variation of it to put the list in an ISPF variable to be used as I've noted above. Does anyone have something like this I can use? I'm not a good assembler programmer or I'd do it myself. TIA, Roy -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
