-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: 15 October 2014 14:55
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX syscall spawnp and IPCS
On Wed, 15 Oct 2014 02:04:59 -0500, Elardus Engelbrecht wrote:
parm.1=/userhome/sa/myrexx.rx
parm.1
On 2014-10-16, at 06:00, Steve Austin wrote:
Thanks for all your responses. The fact that the SYSTSIN I've built in the
spawned address space appears not to be read by IPCS, has led me to suspect
the address TSO in the in the spawned address space is itself causing TSO
commands to run in
Thanks for this Paul and yes it both clarifies and confirms my
suspicions.
Steve
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Paul Gilmartin
Sent: 16 October 2014 14:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX syscall spawnp
Shmuel Metz (Seymour J.) wrote:
parm.1=/userhome/sa/myrexx.rx
parm.1=myrexx.rx
What are you trying to do?
Good question.
Hmm, I looked again at that posted code and found many such double assignments.
In fact, the first parm.1 could be deleted or commented out. But the second one
is not
On Wed, 15 Oct 2014 02:04:59 -0500, Elardus Engelbrecht wrote:
parm.1=/userhome/sa/myrexx.rx
parm.1=myrexx.rx
Hmm, I looked again at that posted code and found many such double assignments.
I frequently do similarly for testing:
/* Second assignment prevails. (Comments are good!) */
Paul Gilmartin wrote:
I frequently do similarly for testing:
/* Second assignment prevails. (Comments are good!) */
parm.1 = parm for testing
parm.1 = parm for production
... and simply swap the two lines to switch to testing mode. No need to
comment.
Your choice. I also find it
In
d3571c7d425590479eb3adb197bfc47b03616...@m4ukex02.intranet.macro4.com,
on 10/13/2014
at 08:06 AM, Steve Austin steve.aus...@macro4.com said:
The REXX child environment clearly knows to map STDIN to SYSTSPRT,
What are you trying to say? The REXX interface knows how to do what
you told it to
On Mon, 13 Oct 2014 20:13:59 -0500, Shmuel Metz (Seymour J.) wrote:
at 08:06 AM, Steve Austin said:
The REXX child environment clearly knows to map STDIN to SYSTSPRT,
What are you trying to say? The REXX interface knows how to do what
you told it to do; there's nothing special about the name
Sent: 10 October 2014 18:55
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX syscall spawnp and IPCS
Steve:
Hard to help unless we see your Rexx code ?
Regards,
Scott
From: Steve Austin
Sent: Friday, October 10, 2014 10:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Hello
Hello,
I've run out of hammers trying to use REXX syscall spawnp to run a REXX
that drives IPCS in a child address space. IPCS is starting OK, but it
does not appear to be accepting the SYSTSIN cards I'm piping to it. My
latest attempt retrieves the input from the piped STDIN and queues it to
Steve:
Hard to help unless we see your Rexx code ?
Regards,
Scott
From: Steve Austin
Sent: Friday, October 10, 2014 10:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Hello,
I've run out of hammers trying to use REXX syscall spawnp to run a REXX
that drives IPCS in a child
11 matches
Mail list logo