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.

Sometimes performance must suffer a bit to allow functions to be used.  
TANSTAAFL.

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.

Peter

From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Paul Gilmartin
Sent: Thursday, November 23, 2023 2:47 AM
To: [email protected]
Subject: Re: UNIX REXX LINKMVS TASKLIB?


On Thu, 23 Nov 2023 04:18:05 +0000, Farley, Peter wrote:

>

>Performance was admirable and acceptable but this usage was obviously not a 
>high-volume commercial application, so YMMV.

>

I was just taking to heart the advice in

<https://www.ibm.com/docs/en/zos/3.1.0?topic=shell-controlling-use-steplibs>

    ... To improve performance of the z/OS® shell, avoid propagating STEPLIBs 
...



>In this day and age, why in the world would you evec contemplate using a 
>non-cataloged library?  Why even mention such a thing?  What possible business 
>case could there be?

>

In parallel with the JCL Ref. mentioning use of temporary data sets as link 
libraries:

<https://www.ibm.com/docs/en/zos/3.1.0?topic=statement-pgm-parameter<https://www.ibm.com/docs/en/zos/3.1.0?topic=statement-pgm-parameter__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!K6pg6nV91AeHVIG5ov0C6HKx5zPr51GRNQJgnvksRRoFNkcAUdNwuVWQ8ivV8inerGyiL2Lhz97RO3jMfs-2PSsEPe1mT74_5yRa3NNi$>>

    Use the PGM parameter ..., or a temporary library.



Is this obsolete, preserved for compatibility?



--

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 [email protected] with the message: INFO IBM-MAIN

Reply via email to