Joined: 22 Apr 2021 Posts: 7 Location: United States
Hi Team,
I tried to generate an output file on matching records between two input files to get all matched records into an output file. For this, I have used SYNCSORT & ICETOOL using JOINKEYS but I am getting error as shown below. Please kindly advise if I am missing any thing here.
1) in ALL your posts, please, use the code tags, otherwise nobody is able to point you at any minor missing comma in your code samples
2) SYNCSORT works in coupe with SYNCTOOL. DFSORT works in coupe with ICETOOL. Please choose which one of two products you are using, or going to use? That is, ICETOOL is only an interface program to actually call DFSORT, while SYNCTOOL is similar interface program to actually call SYNCSORT.
3) Both ICETOOL, and SYNCTOOL do produce two different listings each (but different DD-names used). You MUST find, read, and present here ALL messages from BOTH of those listings either to find the answer yourself, or to ask for help from the forum.
4) ICETOOL doesn’t use neither //SYSPRINT, nor //SYSOUT
I am not really particular about using SYNCSORT or ICETOOL, but either of the case not getting the result. Both ways job is failing. I have also tried first JCL provided above with OPTION COPY instead of SORT FIELDS=COPY but still it doesn't worked out. Not sure what I am missing with 1st JCL posted above. Please advise.
I am sorry, i am unable to copy paste the job log error messages.
If so, this is a dead end.
First of all, please learn:
1) where to find error messages?
2) how to read error messages?
3) how to understand error messages?
4) how to present error messages to those you ask to help you?
ICETOOL return codes
. . . . . . . . . . . .
20
Message data set error. The TOOLMSG DD statement was not present or the TOOLMSG data set was
not opened.
. . . . . . . . . . . .
It all looks like the code sample you have presented is not related in any manner to the actual, physically running job giving this error(s), isn't it?
I'm pretty sure that you planned to run the job presented in your example, but in fact a different code has been submitted... Maybe, the difference was in one single comma only, but nevertheless, the error message doesn't match the JCL code you presented...
Joined: 22 Apr 2021 Posts: 7 Location: United States
Dear Sir's,
Thank you all for helping me on this. Actually, due to limitations I couldn't post the physical JCL here, instead i have manually typed the statements here by changing the file names. The mistake that i have done is, i used one extra line with '//' in physical JCL was causing the issue. I have deleted the line and it worked.
Thank you all for helping me on this. Actually, due to limitations I couldn't post the physical JCL here, instead i have manually typed the statements here by changing the file names. The mistake that i have done is, i used one extra line with '//' in physical JCL was causing the issue. I have deleted the line and it worked.
Thank you again for helping me on this.
Today I was so kind that have done your own job for you.
Mainly at this forum, people do not do this; the messages like yours are generally ignored, in 99% if times.
Quote:
- Dear auto-experts! My car, like this one at the attached photo, does not move. Please, help me!!!