One further note for the archives: The IBM example COBOL program for the system JSON facilities (HWTJXCB1) is coded to use deliberately STATIC calls to all of the JSON subroutines, when in fact they are quite happy to be called DYNAMICALLY, so all of the steps I used to link in the JSON "stub" module statically were unnecessary. Putting SYS1.CSSLIB into the STEPLIB for a modified copy of the example program that uses dynamic calls to the JSON subroutines produced identical results to the statically bound program.
Performance in a high-volume JSON-using application may be helped by using a static binding, but somehow I don’t think by very much. Thanks IBM . . . . Peter From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Farley, Peter Sent: Sunday, April 27, 2025 1:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Is library SYS1.CSSLIB mirrored anywhere in the Unix file system? For the archives: Using an external link to a SYS1.CSSLIB member in my private Unix file space did NOT work to refer directly to the member using the binder syntax “INCLUDE /u/tsouser/external-link-to-LIBRARY(MEMNAME)”. I unfortunately did not save the error messages generated by that test, but they may have been due to what I discovered using the next option. This command: OCOPY SYS1.CSSLIB(MEMNAME) /u/tsouser/MEMNAME BINARY In a TSO session or in a batch TSO job step does work to copy a binary executable to the Unix file system BUT the source library MUST be a PDSE (SYS1.CSSLIB is an ordinary PDS) because OCOPY will only copy “program objects” to the Unix file system. Copying a member from SYS1.CSSLIB (or any other ordinary PDS containing executable programs) is then a two-step process: 1. Copy SYS1.CSSLIB(member) to a PDSE 2. OCOPY PDSE member to Unix file system Once that is done, using the binder control card “INCLUDE /u/tsouser/MEMNAME” resolved the necessary bind-time entry points. I did not yet try setting up an external link in my private Unix space to a PDSE executable member to see if that would work as input to the binder. Peter From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Farley, Peter Sent: Wednesday, April 23, 2025 8:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Is library SYS1.CSSLIB mirrored anywhere in the Unix file system? Thanks for the links. I agree the second seems less relevant. Peter From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Paul Gilmartin Sent: Wednesday, April 23, 2025 5:16 PM To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: Is library SYS1.CSSLIB mirrored anywhere in the Unix file system? On Wed, 23 Apr 2025 20:48:53 +0000, Farley, Peter wrote: >Possibly, if the binder will resolve those properly AND if I knew how to set >them up. Do you have a recipe or a doc pointer for creating external links? >https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/3.1.0?topic=links-creating-external-link__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NN92Lx13TXg4MEj00IVF71Y7ZRWKIUpjcs9ONczq8lbdnijwzQavrp7RVPthux8Bwrv8YgbMti4rUdQ1PNA6ltXB7n1fJS6iTBoa024X$<https://urldefense.com/v3/__https:/www.ibm.com/docs/en/zos/3.1.0?topic=links-creating-external-link__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NN92Lx13TXg4MEj00IVF71Y7ZRWKIUpjcs9ONczq8lbdnijwzQavrp7RVPthux8Bwrv8YgbMti4rUdQ1PNA6ltXB7n1fJS6iTBoa024X$>Seems > less relevant: >https://urldefense.com/v3/__https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors/9.7.2?topic=information-creating-external-links__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NN92Lx13TXg4MEj00IVF71Y7ZRWKIUpjcs9ONczq8lbdnijwzQavrp7RVPthux8Bwrv8YgbMti4rUdQ1PNA6ltXB7n1fJS6iTJHBcDZT$<https://urldefense.com/v3/__https:/www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors/9.7.2?topic=information-creating-external-links__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NN92Lx13TXg4MEj00IVF71Y7ZRWKIUpjcs9ONczq8lbdnijwzQavrp7RVPthux8Bwrv8YgbMti4rUdQ1PNA6ltXB7n1fJS6iTJHBcDZT$> -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
