Seeing as there are so many, and it has been so long, and the World
changes so much, would a resonable security step be to make a plan to
acquire all new valid & approved signatures, and on target-day delete
all of the o;d sements and replace them with new segments? Yes, a big
deal, but golly, these are signatures, which reflects a higher level of
On 1/23/2014 11:01 AM, Stone, Joel wrote:
I am trying to clean house a bit. There are two hopefully identical *PAGSEG objects. They are signatures.
PAG123 is in OLDLIB, and also in NEWLIB.
How can I validate that they are the same signature?
The create date and other dates are of no use as they have been moved around over the years and dates were altered during the moves.
The sizes are all the same so that doesn't help.
The concern is that Sally Jones got married and changed her name to Sally Smith.
Her signature PAG123 may be in OLDLIB as "Jones", but in NEWLIB as "Smith".
The best way I can think of is to print the old and new next to each other and visually check.
There are about 500 signatures.
In RPG, I want to print the old on the left, the new on the right. So I need to CHGCURLIB OLDLIB, load the pagseg into the print buffer, and then CHGCURLIB NEWLIB and load it again.
But I am afraid that the *PAGSEG objects don't get resolved until print time, so that wont work.
How can I print the OLDLIB and NEWLIB next to each other in RPG or COBOL? Or is it not possible since they are not married up until the output writer starts?
Thanks in advance!
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com