What are you talking about? Function code 2 for ceebenv is defined as follows:
2 Perform setenv(). Adds, changes, or deletes an environment variable in the environment list. OK, it says “set” env not “put” env. Semantics appear the same. That environment variable _EDC_PUTENV_COPY seems intended to permit an obsolete storage location (pre-z/OS V1R2 it says) for environment variables. Why would you want that? Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Tuesday, October 3, 2023 2:15 PM To: [email protected] Subject: Re: Assembler access to USS functions On Tue, 3 Oct 2023 16:35:25 +0000, Farley, Peter wrote: >I found something one can use from assembler to access environment variables >in the LE Vendor Interfaces manual: > >https://www.ibm.com/docs/en/zos/3.1.0?topic=clearenv-ceebenv > >Seems right on target with Dave’s original request. > Interestingly: o There's no function_code corresponding to putenv() o Thus no mention of sensitivity to _EDC_PUTENV_COPY <https://www.ibm.com/docs/en/zos/3.1.0?topic=functions-putenv-change-add-environment-variable> -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
