My job runs fine with DFSORT's ICETOOL, but the SYT messages indicate you're using Syncsort's SYNCTOOL, not DFSORT's ICETOOL. I'm a DFSORT developer. DFSORT and Syncsort are competitive products. I'm happy to answer questions on DFSORT and DFSORT's ICETOOL, but I don't answer questions on Syncsort.
Joined: 18 Jul 2007 Posts: 2150 Location: At my coffee table
balakrishna reddy wrote:
Can you give me the solution using syncsort because we don't have dfsort in our shop.
Since Frank's solution did not raise any Syncsort errors (is this true?), you might have to talk with Syncsort as to why you got the 0C7 error.....
Try SyncSort Mainframe Product Services
Removing the OPTION COPY statement in this ICETOOL application should resolve the Abend0C7 in SyncSort and provide the desired output. Please let me know if you continue to encounter a problem and I would be happy to assist you further.
what's more...I made a point becouse the title was about Syncsort and 'someone who belongs to the DFSORT team' was answering.
The Subject did NOT originally mention Syncsort. If it had, I wouldn't have posted a DFSORT solution. The Subject was changed to mention Syncsort AFTER I posted my solution.
To whoever is deleting posts from this topic - please stop it!
I've posted twice here about why I used the OPTION COPY statement that works fine with DFSORT's ICETOOL (copy is more efficient than sort) and my post has been deleted both times. I thought this information was relevant given that my DFSORT/ICETOOL job is shown here with OPTION COPY, but you don't seem to agree. I don't like the implication that my job as posted doesn't work - it does work with DFSORT and I think I have the right to point that out. If you insist on removing my posts about my DFSORT job, then you should just remove my DFSORT job. This is really starting to get annoying.