publish-06: extracting changed data ; tab_publish_timestamp

• Article Type: General
• Product: Aleph
• Product Version: 20
• Relevant for Installation Type: Dedicated-Direct; Direct; Local;

After performing a full export of the PRIMO-FULL data (p_publish_04) on 20090112, quite a few changes were made to the XXX01 data. z07p records are being created/processed; z00p records are being created.

But when publish-06 is run on the PRIMO-FULL publishing set with the "Create tar file for" parameter of "From last handled date" no export file is created.

Resolution:
The p_publish_06 Help has the following for "Update Date Flag":

There is a variable which holds the last date this service run. This flag determines whether to update the date stored in this variable. This variable facilitates the 'Create Tar file for: From last handled date' option. The variable resides in ./aleph/tab/tab_publish_timestamp.

The entries in this table are structured like this:
02 TAB-LINE OCCURS 100.
03 TAB-SET PICTURE X(20).
03 FILLER PICTURE X(1).
03 TAB-TIMESTAMP PICTURE X(15).

If you run p_publish_06 with 'Create Tar file for: Range of documents' and there is no line in tab_publish_timestamp for the Set name you specify and you specify "Update Date Flag Yes", it will create one.

But if you run p_publish_06 with 'Create Tar file for: From last handled date' and there is no line in tab_publish_timestamp for the Set name you specify and you specify "Update Date Flag Yes", the job will do nothing.

If you create an $aleph_root/tab/tab_publish_timestamp file with this line in it:
PRIMO-FULL yyyymmdd0000001 <where "yyyymmdd " is the date you want to use as the last date>

then the p_publish_06 LAST-DATE run will work.

Note 1: you also want to set the "Update Date Flag" to "Yes" so that future runs with LAST-DATE will get the correct records.

Note 2: though the tab_publish_timestamp is in the a-tree, Development says that they will *not* be sending a new version of this file in any Service Pack, so its presence there is not a problem.

See also KB 16384-48177 (-- link below).