Using LOCATE/CAMLST seems better than using SVC99/BPXWDYN to resolve
relative->absolute since it doesn't require allocation of the data set,
which might fail.
One question that I have is (I assume) that LOCATE/CAMLST will always use
the latest generations ("GDGNT"), so that if what you want is a stable
"current" generation then it won't do the job. With SVC99/BPXWDYN, you
can set or not set the "GDGNT" flag.
Does anyone know how to resolve relative->absolute without allocation
without "GDGNT" ?
On Sun, Jul 28, 2019 at 4:01 PM Dan D <[email protected]> wrote:
> Sam just updated my CBT file today (File 452 in the Updates).
>
> I had a tool called RXLOCATE that simply does a CAMLST LOCATE for a dsname
> in LOCDSN variable.
>
> /*rexx*/
> LOCDSN = 'userid.GDG(-1)' */
> address LINK "RXLOCATE"
> say LOCDSN 'RC=' rc
> Exit
>
> After the LINK to RXLOCATE the LOCDSN variable will have the absolute name
> or true name.
>
> Dan
>
> ----------------------------------------------------------------------
> 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
