On 2020-12-03 10:12 AM, Charles Mills wrote:
I believe you, but why then is the macro undefined? Why is the definition now
commented out?
>From <limits.h> (actually CEE.SCEEH.H(LIMITS)) on z/OS V2R4:
/*
* POSIX.1 1990 Section 2.8.5 Statement 1065 -
* these macros "shall be omitted on specific
* implementations where the corresonding value is
* >= the stated minimum, but where the value
* can vary depending on the file to which it is
* applied."
*
*
*/
/*
* #define LINK_MAX
* #define MAX_CANON
* #define MAX_INPUT
* #define NAME_MAX
* #define PATH_MAX
* #define PIPE_BUF
*/
Charles
Tried this?
"an application may use the/fpathconf/()
<https://pubs.opengroup.org/onlinepubs/009696699/functions/fpathconf.html>,/pathconf/()
<https://pubs.opengroup.org/onlinepubs/009696699/functions/pathconf.html>, and/sysconf/()
<https://pubs.opengroup.org/onlinepubs/009696699/functions/sysconf.html> functions to
determine the actual value of a limit at runtime."
(https://pubs.opengroup.org/onlinepubs/009696699/basedefs/limits.h.html)
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
