Re: USS Environment variables

2023-10-02 Thread Paul Gilmartin
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

Re: USS Environment variables

2023-10-02 Thread Kirk Wolf
Gil, I don't think that "environmental attributes" referred to by bpx4env are the same thing as environment variables. 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

Re: USS Environment variables

2023-10-02 Thread Paul Gilmartin
On Mon, 2 Oct 2023 03:25:11 -0400, David Cole wrote: >We are beginning to write support for USS. I personally don't know >much at all about USS (there are others here who do), so please help >me along if there are terms I'm not using quite correctly. > Is this useful

Re: USS Environment variables

2023-10-02 Thread Kirk Wolf
Dave, I'm not sure what context you are running in, but if you are running under Language Environment, then you might look at the "z/OS Language Environment Vendor Interfaces" book. There are 74 hits of "environment variable" in this book, including in the CEEEDB (enclave data block): CEE

Re: USS Environment variables - Google BARD 370 Assembler

2023-10-02 Thread Clem Clarke
Just for fun, I asked Google's AI (bard.google.com) the following: "What is the format of a linux environment block? How could I navigate an environment block in 370 assembler? The code it returned is half GCC assembler code, and something more like 370 ASM code. Cheers, Clem Clarke

Re: USS Environment variables

2023-10-02 Thread Clem Clarke
The Environment block has been essentially the same since MS/DOS.  In the 1980's (?) I wrote code in 8086 Assembler and Digital Research PL/I and C to access the Environment.  I even wrote code to set the environment - it wasn't pretty! Really it is pretty easy to read the environment.  C has

Re: USS Environment variables

2023-10-02 Thread John Pratt
grams by using the CEEENTRY and associated macros." John. -Original Message- From: IBM Mainframe Discussion List On Behalf Of David Cole Sent: Monday, 2 October 2023 6:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: USS Environment variables We are beginning to write support for USS. I

Re: USS Environment variables

2023-10-02 Thread Colin Paice
See getenv() . I dont know about assembler. On Mon, 2 Oct 2023 at 08:27, David Cole wrote: > We are beginning to write support for USS. I personally don't know > much at all about USS (there are others

USS Environment variables

2023-10-02 Thread David Cole
We are beginning to write support for USS. I personally don't know much at all about USS (there are others here who do), so please help me along if there are terms I'm not using quite correctly. We have a need for our code to access environment variables. I am being told that they can be acces