Thanks for all replies.
Problem was solved. Few code changes. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of peter.w...@ttc.ca Sent: ג 11 ינואר 2011 22:09 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Rexec within Rexec question I see three possible reasons why this may not work: 1) The second REXEC command you meant to send did not get constructed properly, 2) You are executing the second REXEC command interactively, which violates the restriction on interactive commands, 3) VM TCP/IP can have restrictions on using multiple services at the same time, since they may use the same paths to talk to the TCP/IP server. For instance, if both the existing path from the TCP/IP service machine to the userid processing the REXEC request and the new path from the userid to TCP/IP both use VMCF, I think you have a problem. This may be something similar. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Gonen Shoham Sent: January 11, 2011 06:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Rexec within Rexec question Hello, I am running a REXX on cms machine using REXEC. The REXEC is starting OK, but when its gets to point where it needs to run another REXEC - it ends up with RC=36. Any idea how to perform REXEC within REXEC ? Thanks !!! DISCLAIMER: This e-mail and any attachments may be confidential or legally privileged, and is only transmitted for the intended recipient. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing, retransmitting, converting to hard copy, reproducing, or using in any other way any information contained herein. Please inform us at Sapiens of the erroneous delivery by return e-mail and delete the material from any computer, disk drive, diskette, or other storage device or media. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner. DISCLAIMER: This e-mail and any attachments may be confidential or legally privileged, and is only transmitted for the intended recipient. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing, retransmitting, converting to hard copy, reproducing, or using in any other way any information contained herein. Please inform us at Sapiens of the erroneous delivery by return e-mail and delete the material from any computer, disk drive, diskette, or other storage device or media.
