Re: Specifhing the ENVBLOCK (was: Just PDSE)

7:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Specifhing the ENVBLOCK (was: Just PDSE) Separate chains per TCB, so linear chain within TCB but no correlation between TCBs. Programs that use conflicting or incompatible environments across multiple TCBs are on their own :) On Mon, Apr 10, 2023

Re: Specifhing the ENVBLOCK (was: Just PDSE)

M > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Specifhing the ENVBLOCK (was: Just PDSE) > > On Sun, 9 Apr 2023 20:41:33 +, Seymour J Metz wrote: > > >Curse you, OCO! > > > >I suspect that validating a potential ENVB address requires running a > tree

Re: Specifhing the ENVBLOCK (was: Just PDSE)

nday, April 9, 2023 5:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Specifhing the ENVBLOCK (was: Just PDSE) On Sun, 9 Apr 2023 20:41:33 +, Seymour J Metz wrote: >Curse you, OCO! > >I suspect that validating a potential ENVB address requires running a tree >rather than just a lis

Re: Just PDSE

On 8/04/2023 2:23 pm, Brian Westerman wrote: Just so you know, it's not SYSPLEX that you need, it's GRS and you have have that with just a couple FICON ports. Are you sure about that? Regular PDS needs GRS to safely share between multiple systems, if that was all that was required no-one woul

Re: Specifhing the ENVBLOCK (was: Just PDSE)

On Sun, 9 Apr 2023 20:41:33 +, Seymour J Metz wrote: >Curse you, OCO! > >I suspect that validating a potential ENVB address requires running a tree >rather than just a list. > shows only linear chains. So there

Re: Specifhing the ENVBLOCK (was: Just PDSE)

Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu] Sent: Sunday, April 9, 2023 3:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Specifhing the ENVBLOCK (was: Just PDSE) (Subject: changed: this has drifted far from"PDSE") On Sun, 9 Apr 2023 09:50:44 +, Seymour J Metz wrote: &

Specifhing the ENVBLOCK (was: Just PDSE)

(Subject: changed: this has drifted far from"PDSE") On Sun, 9 Apr 2023 09:50:44 +, Seymour J Metz wrote: >Chapter 12. TSO/E REXX programming services > Thanks. Eek! TMI. Where I see: Entry specifications For the IRXEXCOM routine, the contents of the registers on entry are:

Re: Just PDSE

Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu] Sent: Saturday, April 8, 2023 9:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Just PDSE On Sun, 9 Apr 2023 00:14:46 +, Seymour J Metz wrote: >Presumably R0 should be zero if not pointing to an ENVB. > Cite the source,

Re: Just PDSE

On Sun, 9 Apr 2023 00:14:46 +, Seymour J Metz wrote: >Presumably R0 should be zero if not pointing to an ENVB. > Cite the source, please. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email

Re: Just PDSE

ct: Re: Just PDSE On Fri, 7 Apr 2023 21:47:54 -0400, Tony Harminc wrote: > >While looking at the help for CALL, I see - shades of another recent >discussion - that there is now a NOENVB | PASSENVB option: > >NOENVB The NOENVB operand indicates that the REXX environment > blo

Re: Just PDSE

On Fri, 7 Apr 2023 21:47:54 -0400, Tony Harminc wrote: > >While looking at the help for CALL, I see - shades of another recent >discussion - that there is now a NOENVB | PASSENVB option: > >NOENVB The NOENVB operand indicates that the REXX environment > block (ENVBLOCK) address is not to

Re: Just PDSE

Just so you know, it's not SYSPLEX that you need, it's GRS and you have have that with just a couple FICON ports. I have been doing it at several sites now that really don't need CF's (and some who can't afford them) and it works very well, no problems at all. Brian ---

Re: Just PDSE

On Fri, 7 Apr 2023 at 20:44, Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: [...] > Heck, you can't even: > //RUN EXEC PGM='MYNAME.LINKLIB(MYFILE)',PARM='Wonbat' > > Even though TSO lets you: > CALL 'MYNAME.LINKLIB(MYFILE)' 'Wonbat' > > And why does TSO force the p

Re: Just PDSE

On Fri, 7 Apr 2023 22:10:15 +, Frank Swarbrick wrote: >z/OS for UNIX files holds program objects, just like PDSE as far as I know. >Now all we need is >//RUN EXEC PGM='/u/myname/myexefile' > Heck, you can't even: //RUN EXEC PGM='MYNAME.LINKLIB(MYFILE)',PARM='Wonbat' Even though TSO lets

Re: Just PDSE

Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Friday, April 7, 2023 10:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Just PDSE On Fri, 7 Apr 2023 16:17:04 +, Gibney, Dave wrote: >The issue with this has always been and still is the fact that you cannot >safely shar

Re: Just PDSE

On Fri, 7 Apr 2023 17:18:52 +, Gibney, Dave wrote: > >> -Original Message- >> From: Paul Gilmartin >> > >> Do program objects in a z/FS directory satisfy (some) requirements for PDSE? > >Maybe, but you still cant share without SYSPLEX > In the old, old days, before *HFS* sharing existe

Re: Just PDSE

> -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Paul Gilmartin > Sent: Friday, April 7, 2023 9:47 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Just PDSE > > On Fri, 7 Apr 2023 16:17:04 +, Gibney, Dave wrote: > > >Th

Re: Just PDSE

On Fri, 7 Apr 2023 16:17:04 +, Gibney, Dave wrote: >The issue with this has always been and still is the fact that you cannot >safely share PDES without SYSPLEX (perhaps not full SYSPLEX) ... > Do program objects in a z/FS directory satisfy (some) requirements for PDSE? -- gil

Just PDSE

The issue with this has always been and still is the fact that you cannot safely share PDES without SYSPLEX (perhaps not full SYSPLEX) but still more than our small couple LPAR shop needed, And since our development to production path was from Development LPAR to Production LPAR via libraries on