On Thu, 23 Nov 2023 18:13:27 +0000, Farley, Peter wrote: >Probably preserved for IBM (pick your language) PROC compatibility. The only >place I have ever seen temporary link libraries used is in IBM-supplied >compile-link-go PROC’s, where the link step SYSLMOD DD uses >DSN=&&GOSET(&MEM) and the GO step uses “PGM=*.linkstepname.SYSLMOD”. I’ve >never seen that JCL paradigm used in a production job anywhere. > I fear I rook my inspiration from those PROCLIB members. And I ignored the maxim, "Don't take IBM's defaults as IBM's recommendations."
And I was astonished at the generated DDNAMEs I saw in allocation messages. >If performance needs to be improved, there is always the option to copy the >program objects needed from the resident PDSE to a Unix directory in the PATH. > "cp" cam move program objects. Can I then invoke them with LINKMVS and/or pass the classic R1 PLIST for compatibility with batch JCL? (I wish I could //SrEPLIB DD PATH=... to avoid synching copies.) On Thu, 23 Nov 2023 12:53:32 -0600, Jon Perryman wrote: > ... >Temporary datasets never use VOL=SER=. They are accessed through a DD that >optionally exists for the life of the job (DDNAME= or DSN=&&XXX). >Technically they are uncatalogued but the word uncatalogued implies use of >VOL=SER=, > But they can use VOL=REF, which is sometimes needed. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
