The immediate cause of the bad return codes is that neither EDIT nor MACRO are ISREDIT commands
As others have noted, your macro (REXX or CLIST) must be in a separate member from where you issue the EDIT command with the MACRO operand. However, allocating SYSEXEC the way you did is also a bad idea. Your TSO logon proc probably allocated SYSEXEC to give you access to various system REXXs. Your command completely replaced that allocation, leaving your user unable to access any of these. If you really need to have another library temporarily added to the standard search order, use the TSO ALTLIB command. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of [email protected] > Sent: Tuesday, April 09, 2013 11:51 AM > To: [email protected] > Subject: Invoking a Rexx Exec From a ClLIST > > Let me begin by saying I am NOT a Rex Person I know a little about > CLISTS, But I am No way a Rexx person. > > I need to call a Rexx Exec from an established CLIST. > > So before I attempted this endevor, I cobbled two small routines a > CLIST which issues EX 'TEC0P0D1.REXX(REXTEST)' and a Rexx Exec which > Edits a Dataset and Changes a Value > > The CLIST Issues: > EX 'TEC0P0D.REXX(REXTEST)' > > > > The REXXTEST Module looks like this: > /* REXX member name REXTEST */ > ISREDIT MACRO > TRACE ALL > > "ALLOC FILE(SYSEXEC) DATASET('TEC0P0D.REXX') SHR REUSE" > > ADDRESS ISPEXEC > "ISREDIT EDIT 'SYS1.PROCLIB.CICSBKUP.P(TOAQTQ2)'" > "ISREDIT MACRO" > "ISREDIT FIND HBRIDG" > "ISREDIT CHANGE V606 V652" > "ISREDIT SAVE" > "ISREDIT > > > > During invocation of the CLIST from TSO Option 6 > EX 'TEC0P0D.REXX(REXTEST)' > 5 *-* "ALLOC FILE(SYSEXEC) DATASET('TEC0P0D.REXX') SHR REUSE" > >>> "ALLOC FILE(SYSEXEC) DATASET('TEC0P0D.REXX') SHR REUSE" > 7 *-* ADDRESS ISPEXEC > 8 *-* "ISREDIT EDIT 'SYS1.PROCLIB.CICSBKUP.P(TOAQTQ2)'" > >>> "ISREDIT EDIT 'SYS1.PROCLIB.CICSBKUP.P(TOAQTQ2)'" > +++ RC(20) +++ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
