I agree with Itschak. The ISREDIT EDIT ... command does a "recursive" edit of another member/data set, when you are already in ISPF EDIT on something else. If your CLIST wants to edit a member/data set and run a REXX edit macro, then remove the ISREDIT EDIT line and have the CLIST invoke the ISPF editor as Itschak showed, using the IMACRO to invoke the REXX edit macro.
On Tue, Apr 9, 2013 at 1:51 PM, [email protected] <[email protected]> wrote: > 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) +++ > 9 *-* "ISREDIT MACRO" > >>> "ISREDIT MACRO" > +++ RC(20) +++ > 10 *-* "ISREDIT FIND HBRIDG" > >>> "ISREDIT FIND HBRIDG" > +++ RC(20) +++ > 11 *-* "ISREDIT CHANGE V606 V652" > >>> "ISREDIT CHANGE V606 V652" > +++ RC(20) +++ > 12 *-* "ISREDIT SAVE" > >>> "ISREDIT SAVE" > +++ RC(20) +++ > 13 *-* "ISREDIT END" > >>> "ISREDIT END" > +++ RC(20) +++ > FREE FILE(SYSEXEC) > *** > > > My undersatanding of the RC(20) means that I dont have a proper > environment. > > Can Some One explain to me how to properly Invoke a Rexx Exec from a CLIST > I need very specific details.. > > Thank You In Advance > Paul > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
