On Sun, Oct 23, 2016 at 3:21 PM, Walt Farrell <[email protected]> wrote:
> On Sun, 23 Oct 2016 15:15:27 -0500, Paul Gilmartin <[email protected]> > wrote: > > >On Sun, 23 Oct 2016 11:08:38 -0500, Steve Horein wrote: > >> > >>Not being very fluent in 'nix, shouldn't there be a way to set/export > >>variables in memory, avoiding the I/O with reading to/from a file? > >>I could see the desire to flush the variables to disk for preservation, > but > >>repeated look-ups would probably be more efficient. > >> > >Name-Token services? > > > >It's the curse of Conway's law. z/OS provides too many dissimilar ways > >of performing similar functions. Name--token, system symbols, > >jcl symbols, ISPF variables, ISPF Edit variables, Rexx variables, ... > >All have different syntax to set and access them. > > The situation is perhaps further complicated by multi-address-space > considerations, especially when invoking UNIX commands. > This is a theoretical concern in my case - the sharing of "named data" amongst multiple System REXX programs and multiple invocations of said programs being possible under some conditions. But, in my particular case (MPF message processing) this is unlikely due to the relatively low activity of processing on my dying system. And many of the variable names have the jobname as part of the name. Which makes them unique because we run with the JES2 DUPL_JOB=DELAY as is "traditional" for JES2. These variables are being used to pass data from one message, issued by a given job, to later System REXX programs invoked by a subsequent message for that job. There are very few which are "job independent" or "global to all". > > -- > Walt > > -- Heisenberg may have been here. Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
