Macro is invoked by simply typing JEM on the command line. I have not found any user for whom it works today. (I was not the original reporter.) No ALTLIBs in effect at error time.
FYI JEM is a JCL validation product that we have run for decades in just this way. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of retired mainframer Sent: Saturday, August 26, 2017 9:03 AM To: [email protected] Subject: (External):Re: Message IRX0006I running an edit macro CLIST How is the macro invoked? On the SYSPLEX in question, do all users experience the problem? For a user who does, are any ALTLIBs in effect when the error occurs? > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jesse 1 Robinson > Sent: Saturday, August 26, 2017 8:27 AM > To: [email protected] > Subject: Message IRX0006I running an edit macro CLIST > > OK, this is a weird one. We have an old CLIST that runs as an ISPF > edit macro. On one > sysplex only, this CLIST fails with a *Rexx* error message: > > IRX0006I Error running JEM, line 2: Unmatched "/*" or quote > > The actual line being complained about is included here: > > PROC 0 DJSNAME(SPP.JOBSCAN) > /* COPYRIGHT DIVERSIFIED SOFTWARE SYSTEMS, INC., 1991,1993. > CONTROL END(ENDO) NOMSG NOFLUSH > ISREDIT MACRO (PARMSTR) > > Of course there is no closing '*/' in line 2, but it's a CLIST, not a Rexx. The CLIST was last > modified in 2007 according to ISPF stats. What appears to be exactly > the same CLIST > works fine on other sysplexes. The z/OS maintenance level (RSU1705) is > the same on > working and nonworking plexes. I have looked in SYSEXEC libraries and > in other > SYSPROC libraries for a bogus copy of this exec; nothing found. The > CLIST library is VB; > member is unnumbered, so data starts in column 9. > > What might cause a CLIST to be misinterpreted as Rexx? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
