On Mon, 2 Oct 2023 14:56:56 -0500, Kirk Wolf wrote: > >I don't think that "environmental attributes" referred to by bpx4env are the >same thing as environment variables. > I may have to stand corrected.
>I could be wrong, but I don't think that environment variables exist except >for in Language Environment (or the C library of a given non-LE C-compiler). > For example, if you look at the z/OS Unix Assembler Services guide, you will >see that the kernel services that *use* environment vars (e.g. STEPLIB) have >arguments where you give it a pointer to your envar table. > I have come to suspect that environ is hardly different from an additional argp[] accessed as if it were by keyword rather than positional. in: <https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08>, The value of an environment variable is a string of characters. For a C-language program, an array of strings called the environment shall be made available when a process begins. The array is pointed to by the external variable environ, which is defined as: extern char **environ; Does "extern" imply that it's accessible via an ESD entry? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
