Let me try and keep this thread alive ;-)
If the environment variables are in a LE data block, then where were they kept
when omvs was first introduced? I was under the impression that omvs was
introduced by before LE, or am I wrong?
Kind regards,
Erik Janssen
On Sat, 7 Oct 2023 08:59:28 +0800, David Crayford <dcrayf...@gmail.com> wrote:
>> On 7 Oct 2023, at 6:28 am, Kirk Wolf <k...@coztoolkit.com> wrote:
>>
>> This is a thread that won't die.
>
>And there has been some absolute tosh spouted!
>
>>
>> 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.
>
>I believe you. It’s dependent on the OS. On Linux environment variables are
>stored in the proc file system, /proc/<pid>/environ. Whoever stated it’s part
>of the C runtime doesn’t know what they’re talking about.
>
>>
>> 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 <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
>>> Jon Perryman <jperr...@pacbell.net>
>>> Sent: Thursday, October 5, 2023 9:06 PM
>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>> Subject: Re: Assembler access to USS functions
>>>
>>> On Thu, 5 Oct 2023 20:54:56 +0000, Seymour J Metz <sme...@gmu.edu> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
