On Thu, 13 Mar 2025 09:45:02 -0500, Linda Chui <[email protected]> wrote:



>Assuming your -mzos-sys-include comes from 
>https://www.ibm.com/docs/en/open-xl-c-cpp-zos/2.1?topic=compiler-jcl-example, 
>you can see the preamble states it is for C (non-XPLINK). 
>
>There is a USS (or shell) example given in the same document at 
>https://www.ibm.com/docs/en/open-xl-c-cpp-zos/2.1?topic=applications-compiling 
>which includes both C and C++ compilation parts. 
>
>Please do ensure your z/OS service level is up to date as well as there may 
>have been changes to the system, compiler, header files, etc.
>In general, you should NOT need to specify -mzos-sys-include explicitly since 
>the install configuration should have set all the defaults for you.

Thank you. Between your help and the ztech help I have one clean C++ compile.

I have *a lot* of questions that do not seem to be answered by the compiler 
documentation:

- The CLANG manual seems to be pretty necessary. Is it anywhere in the IBM 
documentation tree?
- In 
https://www.ibm.com/docs/en/open-xl-c-cpp-zos/2.1?topic=options-supported-clang 
what is the significance of some options being listed in *not bold* type?
- The reason I missed the JCL PROC examples is that the (only) manual has 
compiler invocation instructions in two disparate places: "Invoking the 
Compiler" and "Compiling." That is confusing.
- The error message that I cited in my previous post is wrong -- otherwise I 
might have figured things out for myself. It says the compiler requires z/OS 
2.1 or above (which is confusing because I am running on 3.1) when the real 
error is "C header used in a C++ compile" or something like that.
- How do I specify the target ARCH level (like I can with the legacy compiler)?
- How do I specify the OPT level (like I can with the legacy compiler)?

Thank you,
Charles

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to