REXX CALLING ANOTHER REXX MANUAL
REXX CALLING ANOTHER REXX CODE

REXX CALLING ANOTHER REXX CODE

The simplest way is to run an IEBGENER to copy your REXX code to a PDS Individual REXX statements (which is why your /* REXX */ was ignored). The JCL you are using is suitable only for executing commands, not > REXX is: /* rexx */ say 'Job1 started' say 'Job1 ended' exit > DSN=VENDOR.SYSEXEC,DISP=SHR //SYSTSPRT DD SYSOUT=* //SYSTSIN DD > //STEPNAME EXEC PGM=IKJEFT01 //SYSEXEC DD > CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1) //JOBLIB DD > JCL I sub is: //ATEST JOB (CONRAD-B),'IBMUSE2', // > supposed to run a REXX pgm but it won't. > Hello, Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. Send email to with the message: INFO IBM-MAIN

REXX CALLING ANOTHER REXX MANUAL

Looking at the output 'it' certainly found the REXX - that's a start - success ended there! Also IKJ56500 isn't in the manual and googling didn't help.ДЇor IBM-MAIN subscribe / signoff / archive access instructions, SYSTSIN DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR Have a JCL stream, first step is supposed to run a REXX pgm but it won't. Not everyone has their own test LPARs or test IMS systems.Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. It is bad enough to have something 'critical' be down, but to be hampered because some long-gone coder got 'too cute' is exasperating.ДЄnother reason to have like named parts is to test something before going into production.

Unless/Until you are required to fix something that you did not create in the middle of the night or some other 'period of intensity', you will probably not understand this. When things like this are done in 'production', it creates a maintenance nightmare (as Enrico mentioned) for those who inherit the code. I frequently override system panels / execs with my own customized versions. Or perhaps he wants to have an ALTLIB that specifies PDS2 then PDS1, but only for the life of E2. I think Kalyan wants to have PDS2 be first in the standard search order. If they have the same name, they should perform similar actions, but they do not have to be exactly the same. > the general assumption is that if two objects have the same name, they should perform the same actions It would be better to review the requirements/standards The general assumption is that if two objects have the same name, they should perform the same actions It will only confuse people who will have to mantain Your work after You change job Why use for different things the same name ? I would like to know is there any way to specify the order in which it searches for E2 instead of standard order. Hence its starting search from the PDS in which E1 is present.ДЄs it finds E2 is the same PDS its executing from PDS1 only.

In this case we are not referring any location to pick E2 for execution. My code is using CALL statement as CALL E2. In this case there is no scope of executing E2 from any other location apart from PDS2. If you have coded like above then i am sure the code will not take the E2 from PDS1. How can I restrict E1 to execute E2 from PDS2 and not E2 from PDS1 even if PDS1 have a member with name E2. If I change the name of E2 in PDS1 then E1 is again executing E2 from PDS2. If I create an exec in PDS1 with the same name E2 as the one present in PDS2 then E1 is executing E2 in PDS1 but not the one in PDS2. I've a Rexx exec E1 in a PDS say PDS1 which executes another exec E2 in PDS2.

Calling another REXX exec from one REXX exec -IBM MainframesД¬alling another REXX exec from one REXX exec

Rexx calling another rexx