IKJ56500I COMMAND M NOT FOUND ***



IBM's Command List programming language & Restructured Extended Executor

IKJ56500I COMMAND M NOT FOUND ***

Postby abyvarghes » Sun Dec 15, 2013 6:15 pm

Hi All,

I am getting error like , IKJ56500I COMMAND M NOT FOUND *** , when I run below code,
DATA_SET = 'SYSD.DAILY.SYSLOG.D141213'                     
Address Tso "Alloc Fi(INPF) DA('"DATA_SET"'), Shr"         
/*Address Tso "Alloc Fi(INPF) DA('ISOPS.SDSF.OUT'), Shr" */
Address Tso "Alloc Fi(OUTF) DA('ISOPS.IPL.HISTORY'), Mod"   


And here I am trying to read the daily syslog and process it filter some values and write into another data set. I have not included all the code here. But when I run with data set SYSD.DAILY.SYSLOG.D141213 only I am getting error . But when I run with Dataset ISOPS.SDSF.OUT , which is commented here ,I am not getting this error.

But I don't use any command "M" any where in my REXX code.

Thanks,
Aby Varghese
abyvarghes
 
Posts: 13
Joined: Wed Apr 01, 2009 11:52 am
Has thanked: 0 time
Been thanked: 0 time

Re: IKJ56500I COMMAND M NOT FOUND ***

 

Re: IKJ56500I COMMAND M NOT FOUND ***

Postby Akatsukami » Sun Dec 15, 2013 8:23 pm

Do not put commas after the data set parameter.
"You have sat too long for any good you have been doing lately ... Depart, I say; and let us have done with you. In the name of God, go!" -- what I say to a junior programmer at least once a day
User avatar
Akatsukami
Global moderator
 
Posts: 1058
Joined: Sat Oct 16, 2010 2:31 am
Location: Bloomington, IL
Has thanked: 6 times
Been thanked: 51 times

Re: IKJ56500I COMMAND M NOT FOUND ***

Postby abyvarghes » Sun Dec 15, 2013 10:13 pm

Hi All,

This problem has been fixed. It was just a logic error in my REXX code.

Thanks Akatsukami for your response also.
Thanks,
abyvarghes
 
Posts: 13
Joined: Wed Apr 01, 2009 11:52 am
Has thanked: 0 time
Been thanked: 0 time

Re: IKJ56500I COMMAND M NOT FOUND ***

Postby steve-myers » Mon Dec 16, 2013 2:30 am

Thanks for letting us know.

Akatsukami: for the most part a , is considered as white space by the TSO command scanner. I couldn't find a direct reference to this in TSO/E Command Reference, but see the Delimiters topic in How to read the TSO/E command syntax section.
steve-myers
Global moderator
 
Posts: 1967
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 214 times


Return to CLIST & REXX

 


  • Related topics
    Replies
    Views
    Last post