Re: :Re: Message IRX0006I running an edit macro CLIST

2017-09-01 Thread Jesse 1 Robinson
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dan D Sent: Friday, September 01, 2017 12:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: :Re: Message IRX0006I running an edit macro CLIST Hi Skip, Have you checked the ISPF command table for your command? =3.9 then change the table

Re: :Re: Message IRX0006I running an edit macro CLIST

2017-09-01 Thread Dan D
Hi Skip, Have you checked the ISPF command table for your command? =3.9 then change the table to ISP. We have quite a few CLISTs there ... WHOAMI3 SELECT CMD(%WHOAMI) Then a WHOAMI CLIST that checks for ISPF and pops up a window with user info. If it's not within ISPF it just WRITES

Re: Message IRX0006I running an edit macro CLIST

2017-08-29 Thread CM Poncelet
gt; From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of CM Poncelet > Sent: Monday, August 28, 2017 6:04 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: :Re: Message IRX0006I running an edit macro CLIST > > FWIW > > The oddity is that

Re: Message IRX0006I running an edit macro CLIST

2017-08-29 Thread Jesse 1 Robinson
@LISTSERV.UA.EDU] On Behalf Of CM Poncelet Sent: Monday, August 28, 2017 6:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: :Re: Message IRX0006I running an edit macro CLIST FWIW The oddity is that there are *no* edit macro statements after "ISREDIT MACRO (PARMSTR)". So why is an

Re: :Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread Paul Gilmartin
On Tue, 29 Aug 2017 04:37:19 +0100, CM Poncelet wrote: > >... made the "ISREDIT MACRO (PARMSTR)" statement wholly irrelevant >(because no actual *edit* commands then followed it). All the commands >that *did* follow it could be issued in native Clist or REXX, without a >preceding "ISREDIT MACRO"

Re: :Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread CM Poncelet
*Any* commands that can be issued in a Clist or REXX proc (e.g. "ISPEXEC SELECT PGM(J00YCKAL) PARM(JLRCL)" etc.)can also be issued in an edit macro. But *only edit* statements (e.g. "EXCLUDE ALL P'¬'" then "CHANGE ALL P'.' ' ' NX" etc.) can be issued in edit macros. The point I was making was that

Re: :Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread Paul Gilmartin
On Tue, 29 Aug 2017 02:04:25 +0100, CM Poncelet wrote: >FWIW > >The oddity is that there are *no* edit macro statements after "ISREDIT >MACRO (PARMSTR)". So why is an edit macro declared in the Clist? >  >E.g. "ISPEXEC SELECT PGM(J00YCKAL) PARM(JLRCL)" etc.can be issued >directly from the Clist

Re: :Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread CM Poncelet
n List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Sunday, August 27, 2017 8:31 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Message IRX0006I running an edit macro CLIST > > Typically the user is EDITing a PDS Member with JCL and enters

:Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread Jesse 1 Robinson
, 2017 8:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Message IRX0006I running an edit macro CLIST Typically the user is EDITing a PDS Member with JCL and enters JEM on the command line Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IB

Re: Message IRX0006I running an edit macro CLIST

2017-08-28 Thread Paul Gilmartin
On Mon, 28 Aug 2017 02:59:02 +0100, CM Poncelet wrote: >  >As for the 'mysteries', I would guess that IBM published a PTF to >*enforce* the rule that edit macros should always begin with 'ISREDIT >MACRO' - and had previously been ignored. ... >  For Rexx, at least, I've always experienced an

Re: Message IRX0006I running an edit macro CLIST

2017-08-27 Thread Lizette Koehler
LISTSERV.UA.EDU > Subject: Re: Message IRX0006I running an edit macro CLIST > > There are two parms for this Clist: DSJNAME and PARMSTR. How is JEM invoked? > (E.g. it could be invoked as "TSO JEM HLQ.DSJN1.THEREST MACPARM2".) > > On 27/08/2017 18:25, Feller, Paul wr

Re: Message IRX0006I running an edit macro CLIST

2017-08-27 Thread CM Poncelet
* > > Thanks.. > > Paul Feller > AGT Mainframe Technical Support > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: Sunday, August 27, 2017 12:11 > To: IBM-MAIN@

Re: Message IRX0006I running an edit macro CLIST

2017-08-27 Thread CM Poncelet
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of CM Poncelet > Sent: Saturday, August 26, 2017 2:36 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Message IRX0006I running an edit macro CLIST > > FWIW > (a) The "ISREDIT

Re: Message IRX0006I running an edit macro CLIST

2017-08-27 Thread Feller, Paul
August 26, 2017 2:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Message IRX0006I running an edit macro CLIST FWIW (a) The "ISREDIT MACRO" should be the *1st* executable statement; there should be no "PROC 0 " in edit macros - unless the edit macro is actually em

Re: Message IRX0006I running an edit macro CLIST

2017-08-27 Thread Jesse 1 Robinson
@LISTSERV.UA.EDU Subject: (External):Re: Message IRX0006I running an edit macro CLIST FWIW (a) The "ISREDIT MACRO" should be the *1st* executable statement; there should be no "PROC 0 " in edit macros - unless the edit macro is actually embedded in the Clist (a bit unusual). (b) Anyquote

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread Paul Gilmartin
On Sat, 26 Aug 2017 12:48:56 -0700, Lizette Koehler wrote: >Did you use ISRDDN and search for JEM? Just to verify what you see. > >Only time I see this is when a CLIST is on SYSEXEC > ISRDDN is badly broken. I've reported this and received WAD. If a DDNAME is a mixed cocatenation of UNIX

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread CM Poncelet
FWIW (a) The "ISREDIT MACRO" should be the *1st* executable statement; there should be no "PROC 0 " in edit macros - unless the edit macro is actually embedded in the Clist (a bit unusual). (b) Anyquotes should be enclosed in both '/*' and '*/' open/closing chars, even in Clist.   The usual way to

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread Walt Farrell
On Sat, 26 Aug 2017 15:27:21 +, Jesse 1 Robinson wrote: >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: >...snipped... > >What might cause a CLIST to be

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread Lizette Koehler
Did you use ISRDDN and search for JEM? Just to verify what you see. Only time I see this is when a CLIST is on SYSEXEC Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: Saturday, August 26,

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread Paul Gilmartin
On 2017-08-26, at 10:21, Jesse 1 Robinson wrote: > 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

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread Jesse 1 Robinson
, August 26, 2017 9:03 AM To: IBM-MAIN@LISTSERV.UA.EDU 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

Re: Message IRX0006I running an edit macro CLIST

2017-08-26 Thread retired mainframer
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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson >