RE: Restored logicals have different format level identifier to originals - what gives?

midrange-l-request@xxxxxxxxxxxx wrote:

  6. Restored logicals have different format level identifier to
     originals - what gives? (Martin Rowe)

The physicals were created by SQL (they are part of a 3rd party
application) and the logicals are ones we've created (using DDS) to
provide the access to the files from our in-house systems. To try to
narrow down the problem I created a new library and used CRTDUPOBJ to
put empty copies of a couple of the physicals into it. I then used
CRTDUPOBJ to duplicate all dependant logicals to the same library,
creating them in the same order the logicals were originally compiled
in. The logicals in the new library all had matching format level
identifiers to the live system files. So far so good. Saving &
restoring this library to another system results in the logicals
without the "Allows the null value" and the mismatched level ID. :(

Martin:

Please see PTF 5722SS1-SI23530. I ran into this same problem at V5R3 and this 
PTF fixed it for me. Might be related PTFs at other VRMs of OS/400; you'll want 
to cross-reference it.

There are apparently at least two somewhat related issues, but your mention of 
CRTDUPOBJ makes me think that SI23530 is good for you. Besides, it supersedes 
the second PTF anyway.

Hope it helps. This one can be a real surprise when it hits.

Tom Liotta