![]() |
|
#11
|
|||
|
|||
|
I seem to recall from long ago that the OS will return these generations in order of the most recently cataloged first.
Which can lead to a rather obscure bug, if your logic depends on them being in a specific order. If you have GDG Base: MDMX000.BS100.GDG Version 1: MDMX000.BS100.GDG.G0001V00 Version 2: MDMX000.BS100.GDG.G0002V00 Version 3: MDMX000.BS100.GDG.G0003V00 Version 4: MDMX000.BS100.GDG.G0004V00 Version 5: MDMX000.BS100.GDG.G0005V00 But a recent fix created & cataloged a new version of generation 3, thus now: Version 3: MDMX000.BS100.GDG.G0003V01 then the order they will be returned in is 1st: MDMX000.BS100.GDG.G0003V01 2nd: MDMX000.BS100.GDG.G0005V00 3rd: MDMX000.BS100.GDG.G0004V00 4th: MDMX000.BS100.GDG.G0002V00 5th: MDMX000.BS100.GDG.G0001V00 Can anyone confirm if this is correct, or am I remembering it wrong? (In any case, the smart way to program this is to make it independent of the order of the input, either by reading an appropriate date off a header record or a data field on each record, or by sorting the input as needed before the program, or some similar programming technique.)
__________________
Tim Bonham |
|
#12
|
||||
|
||||
|
Quote:
Code:
Code:
Now look at the output at SYSUT2 of step CONCAT2: Code:
__________________
Stefan There are 10 types of people in the world: Those who understand binary, and those who don't. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|