Thanks for this Paul and yes it both clarifies and confirms my suspicions. Steve
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: 16 October 2014 14:13 To: [email protected] Subject: Re: REXX syscall spawnp and IPCS 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 yet another address. > Does this clarify?: The TSO command environment z/OS Using REXX and z/OS UNIX System Services SA23-2283-00 http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.bpxb60 0/tsoenv.htm The TSO command environment (ADDRESS TSO) can be used from a z/OS UNIX REXX environment, and is initialized with: address tso [command] where command can be any TSO/E command, CLIST, or REXX exec that can run in a batch TSO TMP. Commands addressed to TSO are run in a TSO TMP that is running in a separate address space and process from your REXX program. This provides you with the capability to run TSO commands. It does not provide you with the capability to use TSO commands to affect your REXX environment, or to have REXX statements or other host command environments affect your TSO process. ... Specifying environment variable BPXWRFD in a REXX program before the TSO process is started causes the TSO process to inherit open file descriptors 10 thru 99. Perhaps you could use those descriptors. dup2() as needed. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail message has been scanned and cleared by Postini / Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
