Help with TSO parsing?
I admit that I have no experience with this. I am attempting to modify a
TSO command processor that I downloaded from IBM. I am adding a new
keyword at the end. I am failing at execution time with the messages:
IKJ56293I RACSEQ2 FAILED - PARSE SERVICE ROUTINE HAD AN INVALID INPUT
PARAMETER BLOCK+
IKJ56293I RETRY, THEN IF ERROR CALL YOUR SYSTEM PROGRAMMER (REGISTER 15
= 12)
The parse code is:
KWXMLDD IKJKEYWD
IKJNAME 'XMLDDN',SUBFLD=XMLDDN,ALIAS=('DDN','DDNAME')
IKJNAME 'XMLDSN',SUBFLD=XMLDSN,ALIAS=('DSN','DSNAME')
IKJNAME 'XMLPATH',SUBFLD=XMLPATH,ALIAS=('PATH')
...
XMLDDN IKJSUBF
XMLDDIKJIDENT 'XMLDDN',UPPERCASE,MAXLNTH=8,FIRST=ALPHA,X
OTHER=ALPHANUM, X
HELP=('DD name to use for XML output')
XMLDSN IKJSUBF
XMLDSIKJPOSIT DSNAME,USID, X
HELP=('Dataset Name to be used for XML output')
XMLPATH IKJSUBF
XMLPAT IKJIDENT 'XMLPATH',ASIS,MAXLNTH=255, X
FIRST=ANY,OTHER=ANY,X
VALIDCK=VALDPATH, X
HELP=('UNIX path and file name')
If I remove the SUBFLD and ALIAS from the three IKJNAME macros, I don't
get the parse error. If I put a IKJKEYWD in front of each of the IKJNAME
macros, I don't get the parse error. What I'm trying to do is say that
the command will accept at most one of XMLDDN, XMLDSN, or XMLPATH.
Any TSO gurus left out there that want to admit it?
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
On 27/03/2008, McKown, John [EMAIL PROTECTED] wrote:
I admit that I have no experience with this. I am attempting to modify a
TSO command processor that I downloaded from IBM. I am adding a new
keyword at the end. I am failing at execution time with the messages:
IKJ56293I RACSEQ2 FAILED - PARSE SERVICE ROUTINE HAD AN INVALID INPUT
PARAMETER BLOCK+
IKJ56293I RETRY, THEN IF ERROR CALL YOUR SYSTEM PROGRAMMER (REGISTER 15
= 12)
The parse code is:
KWXMLDD IKJKEYWD
IKJNAME 'XMLDDN',SUBFLD=XMLDDN,ALIAS=('DDN','DDNAME')
IKJNAME 'XMLDSN',SUBFLD=XMLDSN,ALIAS=('DSN','DSNAME')
IKJNAME 'XMLPATH',SUBFLD=XMLPATH,ALIAS=('PATH')
...
XMLDDN IKJSUBF
XMLDDIKJIDENT 'XMLDDN',UPPERCASE,MAXLNTH=8,FIRST=ALPHA,X
OTHER=ALPHANUM, X
HELP=('DD name to use for XML output')
XMLDSN IKJSUBF
XMLDSIKJPOSIT DSNAME,USID, X
HELP=('Dataset Name to be used for XML output')
XMLPATH IKJSUBF
XMLPAT IKJIDENT 'XMLPATH',ASIS,MAXLNTH=255, X
FIRST=ANY,OTHER=ANY,X
VALIDCK=VALDPATH, X
HELP=('UNIX path and file name')
If I remove the SUBFLD and ALIAS from the three IKJNAME macros, I don't
get the parse error. If I put a IKJKEYWD in front of each of the IKJNAME
macros, I don't get the parse error. What I'm trying to do is say that
the command will accept at most one of XMLDDN, XMLDSN, or XMLPATH.
Any TSO gurus left out there that want to admit it?
Ahem, hrumph...
Your code *looks* OK at a glance. In particular, the idea of having
alternative keywords, with different subfields, is fine.
Are you sure it assembled properly, in particular that all your IKJ
macros are between the IKJPARM and the IKJENDP? IIRC, this is not
always caught by the macros at assembly time.
Tony H.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
sigh talking to myself and feeling old... I found the problem. I had a parse validation check routine which was returning an invalid return code, causing the PARSE to fail. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
On Thu, 27 Mar 2008 12:30:34 -0500, McKown, John John.Mckown wrote: sigh talking to myself and feeling old... I found the problem. I had a parse validation check routine which was returning an invalid return code, causing the PARSE to fail. Earlier the same day, he wrote: Any TSO gurus left out there that want to admit it? I'll admit to knowing TSO PARSE. What's harder to admit is that I recognize words from an old Carpenters song. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
---snip---
I admit that I have no experience with this. I am attempting to modify a
TSO command processor that I downloaded from IBM. I am adding a new
keyword at the end. I am failing at execution time with the messages:
IKJ56293I RACSEQ2 FAILED - PARSE SERVICE ROUTINE HAD AN INVALID INPUT
PARAMETER BLOCK+
IKJ56293I RETRY, THEN IF ERROR CALL YOUR SYSTEM PROGRAMMER (REGISTER 15
= 12)
The parse code is:
KWXMLDD IKJKEYWD
IKJNAME 'XMLDDN',SUBFLD=XMLDDN,ALIAS=('DDN','DDNAME')
IKJNAME 'XMLDSN',SUBFLD=XMLDSN,ALIAS=('DSN','DSNAME')
IKJNAME 'XMLPATH',SUBFLD=XMLPATH,ALIAS=('PATH')
...
XMLDDN IKJSUBF
XMLDDIKJIDENT 'XMLDDN',UPPERCASE,MAXLNTH=8,FIRST=ALPHA,X
OTHER=ALPHANUM, X
HELP=('DD name to use for XML output')
XMLDSN IKJSUBF
XMLDSIKJPOSIT DSNAME,USID, X
HELP=('Dataset Name to be used for XML output')
XMLPATH IKJSUBF
XMLPAT IKJIDENT 'XMLPATH',ASIS,MAXLNTH=255, X
FIRST=ANY,OTHER=ANY,X
VALIDCK=VALDPATH, X
HELP=('UNIX path and file name')
If I remove the SUBFLD and ALIAS from the three IKJNAME macros, I don't
get the parse error. If I put a IKJKEYWD in front of each of the IKJNAME
macros, I don't get the parse error. What I'm trying to do is say that
the command will accept at most one of XMLDDN, XMLDSN, or XMLPATH.
Any TSO gurus left out there that want to admit it?
-unsnip--
This is far back in my memory, so firgive me if I'm a bit blurry here.
I think that instead of IKJNAME, you want to use IKJKEYWD macros at the
beginning. I don't remember exactly how to check for exclusivity; I'll
take a look in my old docs. IIRC, you might also use the IKJIDENT macro
in that position, eliminating the IKJSUBF entirely.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
McKown, John wrote: sigh talking to myself and feeling old... I found the problem. I had a parse validation check routine which was returning an invalid return code, causing the PARSE to fail. You might think of removing explicit aliases DDN and DSN. IKJPARS will recognize them as unambiguous truncations of DDNAME and DSNAME keywords unless the rest of the syntax is rather strange. Bob Wright - MVS Service Aids -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with TSO parsing?
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Wright Sent: Thursday, March 27, 2008 2:17 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Help with TSO parsing? McKown, John wrote: sigh talking to myself and feeling old... I found the problem. I had a parse validation check routine which was returning an invalid return code, causing the PARSE to fail. You might think of removing explicit aliases DDN and DSN. IKJPARS will recognize them as unambiguous truncations of DDNAME and DSNAME keywords unless the rest of the syntax is rather strange. Bob Wright - MVS Service Aids I finally read that part of the book. [grin]. Well, I'm a belt and suspenders type person when I write code. And it is easier to leave them in than take them out. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
