By inline I means that it is executed in the script rather than being put on the stack.
There is a documented restriction that TSOLIB only works from the READY prompt. Due to the way that IBM implemented EXEC, a CLIST called from the READY prompt can also issue a TSOLIB. From REXX you would have to PUSH or QUEUE the command. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of David Spiegel <00000468385049d1-dmarc-requ...@listserv.ua.edu> Sent: Saturday, December 30, 2023 6:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Checking status of multiple datasets in CLIST and REXX Hi R'Shmuel AMV"SH. Gut Voch. Ich Vil Dich Freigen Ein Kasho. You said: "...TSOLIB inline. ..." What does this mean and why is it better/easier to do this in CLIST than in Rexx? Regards, David On 2023-12-29 16:13, Seymour J Metz wrote: > In my case there is a CLIST effectively called from the READY prompt, so the > TSO environment should be fully initialized. > > The reason that it's CLIST is so I can use TSOLIB inline. > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > עַם יִשְׂרָאֵל חַי > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > > ________________________________________ > From: IBM Mainframe Discussion List<IBM-MAIN@LISTSERV.UA.EDU> on behalf of > Paul Gilmartin<0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> > Sent: Friday, December 29, 2023 1:29 PM > To:IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Checking status of multiple datasets in CLIST and REXX > > On Fri, 29 Dec 2023 18:10:08 +0000, Seymour J Metz wrote: > >> I'm in an applications role and installing external software, e.g., PDS86, >> is not allowed. >> >> I just discovered that I don't even have access to SYS1.SAMPLIB. >> > !?!?!? What terrifies them? "Need to know" gone berserk? Fear of copyright > infringement? > >> I should be able to use any BPXW... service that doesn't require dubbing. >> > Long ago it was reported here that BPXWDYN failed eary in startup, before a > descriptor not necessarily needed for messages could be created. That > may have been fixed by APAR. > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email tolists...@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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
