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.
Re: Rexec within Rexec question
What's REXEC? Rexx is built-in to CMS. Nothing special is needed except that the first line be a Rexx comment so that CMS can tell the difference between EXEC, EXEC2 and Rexx. Generally speaking, if Rexx can't find a called exec (or function), you haven't ACCESSed the necessary disk. Les Gonen Shoham wrote: 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.
Re: Rexec within Rexec question
Remote EXEC: rexec executes the specified command on a remote host. On 11 Jan 2011 at 12:45, Les Koehler wrote: What's REXEC? Rexx is built-in to CMS. Nothing special is needed except that the first line be a Rexx comment so that CMS can tell the difference between EXEC, EXEC2 and Rexx. Generally speaking, if Rexx can't find a called exec (or function), you haven't ACCESSed the necessary disk. Les Gonen Shoham wrote: 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.
(Fwd) Re: Rexec within Rexec question
I Should also have mentioned: The remote host must be running a rexecd service (or daemon) for rexec to connect to. Billy --- Forwarded message follows --- Remote EXEC: rexec executes the specified command on a remote host. On 11 Jan 2011 at 12:45, Les Koehler wrote: What's REXEC? Rexx is built-in to CMS. Nothing special is needed except that the first line be a Rexx comment so that CMS can tell the difference between EXEC, EXEC2 and Rexx. Generally speaking, if Rexx can't find a called exec (or function), you haven't ACCESSed the necessary disk. Les Gonen Shoham wrote: 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. --- End of forwarded message ---
Re: Rexec within Rexec question
Now I understand. Doesn't change my advice. If exec1 executes exec2 then exec2 must be on an accessed disk, NUCXLOADed or in a shared segment (or whatever they call it these days). Essentially, no different than your local environment. Les Billy Bingham wrote: Remote EXEC: rexec executes the specified command on a remote host. On 11 Jan 2011 at 12:45, Les Koehler wrote: What's REXEC? Rexx is built-in to CMS. Nothing special is needed except that the first line be a Rexx comment so that CMS can tell the difference between EXEC, EXEC2 and Rexx. Generally speaking, if Rexx can't find a called exec (or function), you haven't ACCESSed the necessary disk. Les Gonen Shoham wrote: 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.
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.
Re: Rexec within Rexec question
On Tuesday, 01/11/2011 at 06:47 EST, Gonen Shoham gone...@sapiens.com wrote: 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 ? If you log onto the 2nd user directly, can it successfully REXEC to the 3rd user? If so, talk to the Support Center. There is nothing in the REXEC documentation about not being able to cascade REXECs. I really wouldn't expect any interference since there is no direct TCP/UDP connection between REXECD and the 2nd user. RC=36 is the initial return code set by REXEC internally before it starts running and (in theory) means that the remote side (where 3rd user is located) did a TCP RESET. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: Rexec within Rexec question
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.
Re: REXEC question
On Thursday, 07/17/2008 at 07:50 EDT, Fox Blue [EMAIL PROTECTED] wrote: I set up the REXEC daemon on z/VM 5.3 and wanted to do a logon of a userid RVMCP with my own credentials. For this the RVMCP directory entry has a LOGONBY option that names my own userid. When I do a LOGON RVMCP BY myuser then it works well. However when I do this via rexec such as rexec -l rvmcp.by.myuser remote.host q names this gives me a return code of 1 saying that myuser may not login as RVMCP. I didn't find any additional information for eventual additional configuration of REXECD on this in the documentation, so maybe somebody has experienced a similar problem and could give me a hint. I have RSU 0801 applied on the system. Do you have an ESM (RACF, VM:Secure, etc.)? Alan Altmark z/VM Development IBM Endicott
Re: REXEC question
On Thu, 17 Jul 2008 08:47:19 -0400, Alan Altmark [EMAIL PROTECTED] wrote: On Thursday, 07/17/2008 at 07:50 EDT, Fox Blue [EMAIL PROTECTED] wrote: I set up the REXEC daemon on z/VM 5.3 and wanted to do a logon of a userid RVMCP with my own credentials. For this the RVMCP directory entry has a LOGONBY option that names my own userid. When I do a LOGON RVMCP BY myuser then it works well. However when I d o this via rexec such as rexec -l rvmcp.by.myuser remote.host q names th is gives me a return code of 1 saying that myuser may not login as RVMCP. I didn't find any additional information for eventual additional configuration of REXECD on this in the documentation, so maybe somebod y has experienced a similar problem and could give me a hint. I have RSU 0801 applied on the system. Do you have an ESM (RACF, VM:Secure, etc.)? Alan Altmark z/VM Development IBM Endicott No, there is no ESM only basic z/VM authorisation. Meanwhile we opened a PMR and got already a fix. The reason was that the userid field was not padded with blanks to lenght of 8. The fix is working well and we are waiting for the APAR/PTF. Best regards, Florian
REXEC question
Dear all, I set up the REXEC daemon on z/VM 5.3 and wanted to do a logon of a useri d RVMCP with my own credentials. For this the RVMCP directory entry has a LOGONBY option that names my own userid. When I do a LOGON RVMCP BY myuser then it works well. However when I do t his via rexec such as rexec -l rvmcp.by.myuser remote.host q names this gives me a return code of 1 saying that myuser may not login as RVMCP. I didn't find any additional information for eventual additional configuration of REXECD on this in the documentation, so maybe somebody h as experienced a similar problem and could give me a hint. I have RSU 0801 applied on the system. Thanks in advance. Best regards, Fox
