Re: Using environment variables in JCL and USS

ֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Thursday, June 27, 2024 8:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using environment variables in

Re: Using environment variables in JCL and USS

On Thu, 27 Jun 2024 10:49:03 +, Seymour J Metz wrote: >The submit() function is Unix System Services, not REXX. > No: Usage notes 1. The submit shell command uses the REXX submit() func

Re: Using environment variables in JCL and USS

From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, June 26, 2024 10:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using environment variables in JCL and USS On Thu, 27 Jun 2024 01:55:39 +, Sey

Re: Using environment variables in JCL and USS

On Thu, 27 Jun 2024 01:55:39 +, Seymour J Metz wrote: >> It's absurd that the various SUBMIT commands, TSO, ISPF, Rexx, >> and OMVS enforce FB,80, > >REXX? > >As for ISPF, it uses TSO SUBMIT, and that's where the fix has to go. Is

Re: Using environment variables in JCL and USS

לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, June 26, 2024 9:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using environment variables in JCL a

Re: Using environment variables in JCL and USS

On Tue, 25 Jun 2024 23:32:55 -0500, Paul Gilmartin wrote: >On Wed, 26 Jun 2024 03:15:25 +, kekronbekron wrote: > >>Are you able to share this, Paul? >> >I no longer have the code. > I'll suggest that as a PoC you try allocating your SYSIN to a data set, RECFM=VB to see whether it meets you

Re: Using environment variables in JCL and USS

On Wed, 26 Jun 2024 03:15:25 +, kekronbekron wrote: >Are you able to share this, Paul? > I no longer have the code. I used ISPF Edit facilities to get LRECL, RECFM of the Edited file. BPXWDYN or ALLOCATE SYSOUT INTRDR with similar attributes. Extracted lines and wrote one-by-one with EXECI

Re: Using environment variables in JCL and USS

Are you able to share this, Paul? -KB On Tuesday, June 25th, 2024 at 23:32, Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 25 Jun 2024 13:33:59 -0400, Phil Smith III wrote: > > > SWAG but have you tried a trailing semicolon? Or quotes around the value? I > >

Re: Using environment variables in JCL and USS

I found an example where the environment variables are specified directly in the ENVAR parm and not in a separate file; maybe this could work for your use case too ... //CEEOPTS  DD * ALL31(ON), STACK(3M,1M,ANY,KEEP), HEAP(4K,4K,ANY,KEEP), STORAGE(NONE,NONE,NONE,0), RPTSTG(ON),RPTOPTS(ON), ENVA

Re: Using environment variables in JCL and USS

On Tue, 25 Jun 2024 13:33:59 -0400, Phil Smith III wrote: >SWAG but have you tried a trailing semicolon? Or quotes around the value? I >found an example on the web for another product: >ENVAR C='X Y' >...which sorta suggests that the quotes might work. Might try both flavors of >quote, too. > O

Re: Using environment variables in JCL and USS

n List On Behalf Of Colin Paice Sent: Tuesday, June 25, 2024 1:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Using environment variables in JCL and USS I am writing a program using system SSL (GSK*). If I define the environment variables in USS everything works. If I specified the environment va

Using environment variables in JCL and USS

I am writing a program using system SSL (GSK*). If I define the environment variables in USS everything works. If I specified the environment variables in JCL //START1 EXEC PGM=GSKMAIN,REGION=0M, // PARM=('ENVAR("_CEE_ENVFILE=DD:STDENV")/4000') //STDENV DD * GSK_TRACE_FILE=/tmp/zzztrace.file GSK