Oh yea.. I guess if I paid more attention to the topic... I would have seen that.
It is funny that everyone starts to gravitate towards problems around the same time. Been working some on RDz.. BPX_SHAREAS and SPAWN_SCRIPT have recently become very interesting to me. I have to admit that the whole thing is starting to take on a slightly voodoo-istic shadings. The best is the BPX_SHAREAS=MUST which is more likely to be MOSTLY. <VBG>... some of this stuff just makes me laugh. Definitely would have failed the RFC writing rules. Rob Rob Schramm Senior Systems Consultant Imperium Group On Wed, Oct 23, 2013 at 10:47 PM, Kirk Wolf <k...@dovetail.com> wrote: > Rob, > > I think that EZACFSM1 is for MVS System symbols, where as IAZSYMBL is JES > System Symbols (introduced in V2R1). > > Kirk Wolf > Dovetailed Technologies > http://dovetail.com > > > On Wed, Oct 23, 2013 at 8:59 PM, Rob Schramm <rob.schr...@gmail.com> > wrote: > > > Kirk, > > > > Isn't there a utility (EZACFSM1) provided by Comm Serv to already do what > > you are talking about? Although.. EZACFSM1 is probably not as dynamic as > > you are looking for. > > > > TCPIP config uses it for fixing up symbol values. > > > > Rob Schramm > > > > > > > > Rob Schramm > > Senior Systems Consultant > > Imperium Group > > > > > > > > On Wed, Oct 23, 2013 at 8:23 PM, Paul Gilmartin <paulgboul...@aim.com > > >wrote: > > > > > On Wed, 23 Oct 2013 14:09:45 -0500, Kirk Wolf wrote: > > > > > > > >(*Note*: in the following examples, shell input is bold and follows "> > > ". > > > > Also: you need "set -o pipecurrent" when piping jessym output into > > > "read" > > > >or "." ) > > > > ... > > > >*> set -o pipecurrent * > > > >*> jessym A | read -r myvar* > > > >*> echo $myvar* > > > >B > > > > > > > Now, you've got me started. From: > > > > > > Title: z/OS V1R13.0 UNIX System Services Command Reference > > > Document Number: SA22-7802-14 > > > > > > SHEX Shell execution environments > > > > > > ... Each command in a pipeline (such as "command | command") runs > in > > a > > > child shell > > > environment, unless the pipecurrent shell option is in effect. If > > > pipecurrent is set on > > > (with set -o pipecurrent or set -P), then the last command of the > > > pipeline is executed > > > in the current shell environment. ... > > > > > > Doesn't this mean that the left list of a pipeline will always run in a > > > child shell > > > environment (therefore a separate address space?), regardless of > > > pipecurrent, > > > and that JES symbols of the parent shell will not be available in that > > > child shell > > > environment? > > > > > > -- gil > > > > > > ---------------------------------------------------------------------- > > > 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
