16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

c89, cc, and c++<br />

RECFM<br />

Incorrect values are ignored.<br />

LRECL<br />

None<br />

BLKSIZE<br />

None<br />

DSORG<br />

Incorrect values are treated as if no value had been specified.<br />

22. The following environment variables are parsed as blank-delimited words, and<br />

therefore no embedded blanks or other white-space is allowed in the value<br />

specified. The maximum length of each word is 1024 characters:<br />

prefix_INCDIRS<br />

prefix_INCLIBS<br />

prefix_LIBDIRS<br />

prefix_OPTIONS<br />

prefix_OPERANDS<br />

23. An S-name is a short external symbol name, such as produced by the z/<strong>OS</strong><br />

XL C/C++ compiler when compiling z/<strong>OS</strong> XL C programs with the<br />

NOLONGNAME option. An L-name is a long external symbol name, such as<br />

produced by the z/<strong>OS</strong> XL C/C++ compiler when compiling z/<strong>OS</strong> C programs<br />

with the LONGNAME option.<br />

24. The z/<strong>OS</strong> XL C/C++ run-time library supports a file naming convention of //<br />

(the filename can begin with exactly two slashes). c89/cc/c++ indicate that the<br />

file naming convention of // can be used.<br />

However, the Shell and Utilities feature does not support this convention. Do<br />

not use this convention (//) unless it is specifically indicated (as here in<br />

c89/cc/c++). The z/<strong>OS</strong> Shell and Utilities feature does support the P<strong>OS</strong>IX file<br />

naming convention where the filename can be selected from the set of<br />

character values excluding the slash and the null character.<br />

25. When coding in C and C++, c89, cc, and c++, by default, produce reentrant<br />

executables. For more information on reentrancy, see z/<strong>OS</strong> XL C/C++<br />

Programming Guide. When coding in assembler language, the code must not<br />

violate reentrancy. If it does, the resulting executable may not be reentrant.<br />

26. The prefix_CVERSION, prefix_PVERSION and prefix_CLASSVERSION<br />

environment variables are set to a hex string in the format 0xPVVRRMMM<br />

where P is product, VV is version, RR is release and MMM is modification<br />

level. For example, the prefix_CVERSION and prefix_CLASSVERSION for the<br />

z/<strong>OS</strong> V1R2 compiler is 0x41020000.<br />

27. c89 passes some options to the compiler to ensure that expected behavior is<br />

achieved; for example, P<strong>OS</strong>IX behavior. These options are passed onto the<br />

compiler as defaults that the user can overwrite. When default options passed<br />

by c89 are in conflict with options and/or pragmas that the user specified, the<br />

compiler issues warning and/or severe error messages. Since the user did not<br />

specify options that c89 passed as defaults, these messages may confuse the<br />

user. Prior to the z/<strong>OS</strong> V1R5 release, the compiler was unable to differentiate<br />

between the options that c89 passed as defaults and the user-specified<br />

options so it was unable to correctly resolve conflicting pragma/option<br />

combinations. In some cases, the compiler would overwrite pragmas with the<br />

options that c89 passed as defaults thus limiting a user’s ability to use<br />

pragmas. As of z/<strong>OS</strong> V1R5, the compiler is now able to recognize c89 defaults<br />

and avoid confusion from messages for options, which were not explicitly<br />

specified by the user, and overriding pragmas, when the user did not explicitly<br />

request it. It is believed that most users will benefit from this feature so it is the<br />

default behavior. To enable the old behavior, environment variable<br />

Chapter 2. Shell command descriptions 103

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!