Hello Bill,

You wrote:
>After a bit more investigation, the member id is simply a figure
>calculated when the member is created. So, my question is: why would the
>system care about this?

Both the file level ID and the member level ID are simply the date and
time of creation.  For example, a file or member level ID of 1000330114652
is interpreted as 2000/03/30 11:46:52

The system cares about this value because it indicates that the file or
member being restored was created at a different time from the one
currently on the system.  That may indicate that the data in the member is
sufficiently different to warrant human intervention.  It may indicate
that the only thing common to the file or member is the name -- it may
have a completely different format.

There are two approaches:

        o Specify ALWOBJDIF(*ALL) which will rename the existing object
before restoring
        o Restore into a different library, delete the existing object,
and move the restored object

The format level ID is the magic one that is calculated from field names,
field order, and field attributes, and results in the classic level-check
I/O error.

Simon Coulter.

   FlyByNight Software         AS/400 Technical Specialists

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                 ASCII Ribbon campaign against HTML E-Mail  / \

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.