Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
having nothing better to do than read these threads that go on and on,
because the TS has no idea what he is doing,
and, unfortunately, we do not ask complete, detailed questions,
(as one would of an infant):
the following is an excerpt from the above thread, that is easy to find,
when one scrolls thru the dfsort forum list looking for a similar topic:
Quote:
To determine which level of DFSORT functions you have available, look at message ICE201I in the //SYSOUT messages you receive from the DFSORT job shown below, or from any successful DFSORT job.
If you see:
ICE201I H RECORD TYPE ...
the H indicates you have the October, 2010 DFSORT functions (RESIZE, IFTRAIL, ACCEPT, ADDDAYS, DATEDIFF, TRAN=ATOE, KEYBEGIN, etc) and all of the earlier functions. This function level corresponds to z/OS DFSORT V1R10 PTF UK90025 and z/OS DFSORT V1R12 PTF UK90026. You are completely up to date on DFSORT functional PTFs.
Note: If you see WERxxxs messages, you have Syncsort, not DFSORT.
If you see:
ICE201I G RECORD TYPE ...
the G indicates you have the November, 2009 DFSORT functions (JOINKEYS, TOJUL, TOGREG, WEEKDAY, etc) and all of the earlier functions. This function level corresponds to z/OS DFSORT V1R5 PTF UK51706 and z/OS DFSORT V1R10 PTF UK51707. You are behind on DFSORT functional PTFs. Ask your System Programmer to install z/OS DFSORT V1R10 PTF UK90025 or z/OS DFSORT V1R12 PTF UK90026.
If you see:
ICE201I F RECORD TYPE ...
the F indicates you have the July, 2008 DFSORT functions (FINDREP, WHEN=GROUP, DATASORT, SUBSET, etc) and all of the earlier functions.
This function level corresponds to z/OS DFSORT V1R5 PTF UK90013 and z/OS DFSORT V1R10 PTF UK90014. You are behind on DFSORT functional PTFs. Ask your System Programmer to install z/OS DFSORT V1R10 PTF UK90025 or z/OS DFSORT V1R12 PTF UK90026.
If you see:
ICE201I E RECORD TYPE ...
the E indicates you have the April, 2006 DFSORT functions (PARSE, JFY, SQZ, SPLIT1R, etc) and all of the earlier functions. This function level corresponds to z/OS DFSORT V1R5 PTF UK90007. You are behind on DFSORT functional PTFs. Ask your System Programmer to install z/OS DFSORT V1R10 PTF UK90025 or z/OS DFSORT V1R12 PTF UK90026.
If you see:
ICE201I 0 RECORD TYPE ...
the 0 indicates you do not have the July, 2008 or April, 2006 DFSORT functions. You are way behind on DFSORT functional PTFs. Ask your System Programmer to install z/OS DFSORT V1R10 PTF UK90025 or z/OS DFSORT V1R12 PTF UK90026.
You may or may not have the Dec, 2004 DFSORT functions (IFTHEN, OVERLAY, SFF, UFF, etc), which corresponds to z/OS DFSORT V1R5 PTF UQ95214. try using one of these functions - if you get errors trying to use it, then you don't even have the Dec, 2004 PTF installed.
5 posts, and we still do not know at what level of dfsort to offer a solution.
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
well i spent 1/2 hour coming up with the SPLICE which has a logic flaw,
which occurred to me on the ride home.
now, bill has pointed me in the correct direction,
since the ts has H,
that means he is relatively up-to-date
and can use the JOINKEYS application solution.
I am home (ts is probably, also), so no more tonight
except to say,
1. KEEPNODUPS may or may not keeps non-matches from file 2
(too lazy to look-it-up in the manual.
if KEEPNODUPS keeps the non-matches from file 2, then they can be found, based on what is missing from file 1.
If KEEPNODUPS does not keep the non-matches from file 2,
then you need to do something else with SPLICE,
though the far-superior JOINKEYS has a parm which will identify (actually send them to another output file)
so that they can be reported.
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
Puru,
Good crack at it, and good idea to work it out with a simple test file first.
I think you have one too many SORT FIELDS=COPYs. Have a look at some of the other examples in the forum. The order of statements mostly doesn't matter to SORT (you can check exactly in the manual), but people tend to do them in about the same way.
You can be a bit more positive about ICETOOL. It is a powerful tool/utility/language, with many more posibilities than a plain SORT (which is very flexible anyway). If you are unfamiliar with it, like anything else new you come across, it looks complicated. Look at some examples in the documentation. Try to do some little things in it, become more familiar, and there you go.
When you get to something complicated, have a go at it, if you get stuck, you can always come back here for clarifications or assistance.
