Cool, thanks. I wonder if a STEPLIB will Just Work for assembler, then? We have a tiny bit of CICS stuff and have been compiling it on the MVS side because we didn't know how to make it work on the USS side.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Mario Bezzi Sent: Thursday, March 5, 2026 12:32 PM To: [email protected] Subject: Re: Compiling C under USS Phil, looking at my JCL compile procedure I see that the SDFHLOAD library is part of the STEPLIB concatenation, meaning that the XL C compiler uses regular MVS program load services to invoke the CICS provided interpreter. That's why I thought that using the STEPLIB environment variable described by the USS User's Guide here: https://www.ibm.com/docs/en/zos/3.2.0?topic=cts-building-steplib-environment-steplib-environment-variable may solve the problem, but it didn't. My current understanding, basing on Linda's recommendation, is that the xlc command overrides the same environmental variable with the value provided in the xlc.cfg file. BTW - Compiling with the verbose option > xlc -v -qcics -c main.c provides some visibility into what the xlc driver does. I hope this helps, mario ---------------------------------------------------------------------- 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
