In JCL, you can refer multiple times to the same temporary DSN; allowing &tempname in PARSE, DAIR and DYNALLOC would allow doing the same thing dynamically. As it stands, you have to extract the DSN and volume from the first allocation and use them in the remaining allocations.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Monday, January 17, 2022 8:44 PM To: [email protected] Subject: Re: TSO RECEIVE prompt for output temporary dataset On Mon, 17 Jan 2022 19:41:34 -0500, Tony Harminc wrote: >On Mon, 17 Jan 2022 at 11:08, Seymour J Metz wrote: >> >> The ampersand for temporary dataset names is a JCL convention, not a TSO >> convention. > >Back in the late 1970s or maybe early 1980s there was a short-lived >APAR "fix" that added support for using the ampersand to specify >temporary datasets in IKJPARS. > There's no need for that. One can create a temp data set simply by omitting specification of DSNAME. > ... It was quickly withdrawn - I speculate >because someone with the necessary design sense could see that there >would be a near endless series of followon fixes to make everything >work. > The challenge lies in creating dynamically the control blocks that the converter would have creating statically; PASS; referback; ENQ; ... What were they thinking?! Maybe in JES 5. But I want a way to rename/alias a DDNAME, scope within a step. >Maybe one of our IBMers here could dig up that APAR or even comment on >what happened. -- gil ---------------------------------------------------------------------- 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
