Yup, this did exactly what I needed.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Richard Way
Sent: Friday, April 30, 2021 9:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to specify logical SYSLIB when linking with xclang
,-L/usr/lpp/cbclib/lib
34 libraries = -libmcmp
35 steplib = cbc.sclccmp
**
Bottom of Data
On 29/04/2021 3:23 am, Richard
IST=ALL,XREF -obin/zprotect obj/zprotect/zprotect.cpp.o
lib/libsapi.a lib/libvtk-core.a /usr/lib/GSKCMS64.x /usr/lib/GSKSSL64.x
Rich Way
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Richard Way
Sent: Wednesday, April 28, 2021 11:51 AM
To:
I am having a problem using xlclang++ to link my program on uss. I have
unresolved references, but I actually know where the modules that are needed
are located - I am just unable to express that information to the binder.
As an example, CSNERNG is located in "CSF.SCSFMOD0", but isn't found becau
I currently work for Micro Focus, and we have the "Fortify" product line. I am
NOT in that group, however, and I really don't know if it does what you are
looking for or not - although I know it does have support for scanning
mainframe COBOL for vulnerabilities. I don't know about HLASM.
Someth
