p_file_99: last-loader-log-no incorrect?

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
I've been having problems with not being able to load MARCIVE records in Production. I had not problems in Test. So, I rechecked all of the tables in the "How to ... " document for loading MARCIVE records and saw they are the same as in Test.

I see in Test the "last-loader-log-no" is set to 632 in UTIL G/2. However, in Production it is still set to 0.

How do you calculate what that number should be? I see the record count for z73 in Test is 2955 and in Production is 29703. The 2955 doesn't coincide with the 632, so I can't make a correlation with the 29703 in production.

In Z52, I see the value for "last-loader-log-no" in Test is 632. In Production it is 7911. Should this be the number in UTIL G/2 "last-loader-log-no"?

Resolution:
The last-loader-log-no does not correlate with the number of z73 records. It corresponds to the Z73-LOG-NUMBER which is the first 9 bytes of the z73_rec_key.

The following sql will show you what the last-loader-log-no should be set to:

SQL-xxx01> select max (substr (z73_rec_key,1,9) ) from z73;

Note: If the util g/2 has "Y" in the Suppress column for "last-loader-log-no" --as is usually the case--, then the leading zeroes may be omitted.