This is a thread that won't die.
In z/OS, environment variables are in Language Environment, in the CEEEDB
("Enclave Data Block"). If your assembler code is running in LE, you can
access/set them. An empty table is created when the enclave is initialized,
which can be BEFORE dubbing which happens at the first kernel call. Look in
the LE books if you don't believe me.
Kirk Wolf
Dovetailed Technologies
http:// <http://dovetail.com>coztoolkit.com
On Thu, Oct 5, 2023, at 8:15 PM, Seymour J Metz wrote:
> The issue isn't what has access to environmental variables, but rather what
> creates them.
>
> Further, they are useful in other contexts. An otherwise legacy program that
> uses a Unix command may need to pass the odd environment variable to control
> options for which there are no switches.
>
> ________________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf of
> Jon Perryman <[email protected]>
> Sent: Thursday, October 5, 2023 9:06 PM
> To: [email protected]
> Subject: Re: Assembler access to USS functions
>
> On Thu, 5 Oct 2023 20:54:56 +0000, Seymour J Metz <[email protected]> wrote:
>
> >Even if you have an OMVS segment, you don't get dubbed ntil you use a Unix
> >service.
>
> Environment variables are not unique to UNIX and do not require dubbing. It
> is a feature of the C/C++ language that is in the STDLIB (standard library)
> and can be used in any environment.
>
> Environment variables are only useful in languages that do not support global
> variables or inter-language global variables is not supported. I suspect that
> C and Cobol global variables are shared because of LE. Languages like shells,
> Python, Java and others which are runtime languages don't have access to C
> and Cobol global variables which makes environment variables a simple
> inter-language-communications feature.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN