Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
Are you sure you have input records satifying the criteria? As this has something to do with the options to handle short records in your VB file.
You've two steps coded, so, without looking at SYSOUT we can not tell which step has thrown the error, please post the SYSOUT.
Off hand, you may try this
Code:
EXEC PGM=SORT,PARM='VLTESTI=2'
When VLTESTI=2 is specified, SyncSort will treat comparisons to fields not completely contained within the record as false and decide a record’s status for inclusion or omission from fields that are available.
Joined: 17 Oct 2006 Posts: 2481 Location: @my desk
This has nothing to do with the error message, but why dont you use JOINKEYS as you have Syncsort JOIN readily available.
Do you really need a SYNCTOOL SPLICE here?
Also you have padded a VB record at the end which SHOULD NOT be done. If you want to add indicators to a VB record, it should be done at the beginning and not at the end.
Of course, I have used JOIN and got the result. The design document needs to show at least two possibilities to be chosen by customer. Otherwise it will be rejected outright. They demanded a Ezytrieve (which I don't know) or COBOL solution (which takes lot of lines). They believe that SORT is a third party utility and may be removed anytime in future !!!
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
Quote:
They believe that SORT is a third party utility and may be removed anytime in future !!!
Yes, your/their sort product might be replaced one day - it will not be removed outright.
Why would replacing the sort product be an issue?
Quote:
COBOL solution (which takes lot of lines.
It doesn't have to. . . In fact, this type of requirement is so common that many places have a "shell" module that can be easily cloned for new requirements. There is a "sticky" near the top of the COBOL part of the forum that will match/merge 2 files. It works as is and would only need to be changed to accomodate your specifics. Maybe this can help you.
I dont think there is really a need to provide some approach which involves multiple passes of data just to make somebody happy.
And here since your output file is VB, you DONT need to specify the length as you never know where the data ends. You can simply omit the length field.
I have tried it the way you suggested. The job has completed successfully but I have not got the expected results. I think there is something wrong the way I used the values with SPLICE parameter.
Joined: 17 Oct 2006 Posts: 2481 Location: @my desk
ramsri wrote:
I have tried it the way you suggested. The job has completed successfully but I have not got the expected results. I think there is something wrong the way I used the values with SPLICE parameter.
ramsri,
Your initial post shows two input files. And your recent post shows only one!. I can only guess what your actual requirement is.
The first input file was actually derived from the sole input file I have given in the 2nd post as per the INCLUDE condtions given in the first step of my SORT jcl.
Joined: 17 Oct 2006 Posts: 2481 Location: @my desk
ramsri wrote:
Hi,
The first input file was actually derived from the sole input file I have given in the 2nd post as per the INCLUDE condtions given in the first step of my SORT jcl.
Huh...There cant be a much simpler explanation of a requirement.
Anyways since already you have a working solution using JOINKEYS which is more efficient than the "non-working" one which you're trying upon, I dont see any point in debating further. Good luck.
