Problem is, as soon as I apply additional IFTHEN in the OUTREC the result is different on what INREC has provided. To test, just move the END before OUTREC to see what's meant. Any advise on where to look for the bug is appreciated. Btw, the competitor does the same attempt without issues.
1. The single IFTHEN=(WHEN=INIT...) doesn't make a real sense. It works in the same manner as unconditional OUTREC OVERLAY=...
2. It would be nice to have samples: what output is expected vs. what is produced with/without this "extra IFTHEN"? The readers have no obligation to run such test for you.
3. For clarity, and for better understanding of the process it would be a good idea to place the control statements in the order they are really applied at run time:
Code:
INCLUDE ...
INREC ...
SORT ...
OUTREC ...
OUTFIL ...
END
I would expect the first output as this is where I want to apply additional IFTHEN clauses for the final job. Just don't see my mistake here.
IFTHEN INIT should apply in any case, doesn't it?
Joined: 17 Oct 2006 Posts: 2481 Location: @my desk
Joerg.Findeisen wrote:
Btw, the competitor does the same attempt without issues.
Were you suggesting that, with some other sort product, it gives a different result? I am trying to figure out what exactly is your problem.
Can you post the control statements that you used for each run that produced the different results above?
To me it should provide exactly the same result as when using:
Code:
OUTREC OVERLAY=(121:+0,TO=ZD,LENGTH=4)
To summarize this, DFSORT provides same result for both variants in the OUTREC statement while SYNCSORT fails using IFTHEN OVERLAY in my OUTREC.
@sergeyken: Hope I could make the issue more clear now. Sorry for the confusion if any.
Initial question of mine was if I am doing something wrong for SYNCSORT or if it is a bug in the Software. Presently I am guessing my coding is correct.
produces the same output in both products. As stated, there are a few more IFTHEN in my OUTREC (which I haven't posted yet) to be applied so I wish to see the same result with IFTHEN at first. Sometimes SYNCSORT is more strict with Syntax and it puzzles me why I see different results.
Joined: 15 Aug 2015 Posts: 1255 Location: Bamberg, Germany
The code shall be used to find expired DFDSS backups which by identifier can be either Daily, Weekly or Monthly and have a creation date that exceeds a certain value (hence the IDCAMS input).
If all GDS have been expired also the associated empty GDG base with no active GDS has to be deleted.
With the supplied code, SYNCSORT would provide me with DELETE statements for the latest active GDS which is not correct.
Most of my installations do have in fact DFSORT which never lets me down, but out of curiosity I'd like to see it working also with SYNCSORT.