Diagnostic help

Screen management

the following information needs to be provided to use this screen:
- either the value of HISPTR (pointer identifying a data) directly
- or the recording key of a table of the historization code

The processing generates a log mentioning the links between the entered key and the other Warehousing data. The lines in green indicate those data that can be archived. The lines in red indicate the data that cannot be archived and the reason for not archiving them:

• "LNK xxx => PTR yyy": specifies to which PTR pointer group this HISPTR belongs, in other words the PTR that corresponds to a HISLIK record for the archiving code, such as TYP='G' & LNK=HISPTR
• "LNK xxx <= LNK yyy": specifies that the PTR pointer group cannot be archived because the yyy pointer belonging to the same group cannot.
• "LNK xxx <= TBL CLE(1..n)": specifies that the PTR pointer itself cannot be archived because of the CLE(1..n) record in the TBL table.
• "Links between LNK xxx & LNK yyy" : specifies the link between the PTR and yyy pointers.
• "LNK xxx CLE(1..n)": specifies that the pointer itself can be archived (but is not archived because it belongs to the PTR pointer group that cannot be archived because of the yyy pointer)

First example:
Let us consider the expected input no. 276 (site/depositor = 01/ALPHA) that cannot be archived. The INPUT archiving code, the EINPUTH table and the key (01, ALPHA, 276) that identifies the EI are entered..

The log obtained is as follows:
LNK 463891 => PTR 463891
17:34:01 LNK 463891 (EINPUTH 01 ALPHA 0000276) <= LNK 464656
Link between LNK 463891 & LNK 464656 (RECEIPTL 01 0000319 0000276 1 3)
17:34:01 LNK 464656 (RECEIPTL 01 0000319 0000276 1 3) <= INPUTH 01 ALPHA 0000528
17:34:01 LNK 463891 (EINPUTH 01 ALPHA 0000276) <= LNK 464656

• Line 1: pointer 463891 (identifying the EI no. 276) belong to the pointer group 463891
• Line 2: pointer 463891 (EI no. 276) cannot be archived because pointer 464656 cannot be.
• Line 3: pointer 463891 (EI no. 276) is linked to pointer 464656 (Receipt 319, EI no. 276, line EI 1)
• Line 4: pointer 464656 cannot be archived because of the direct input no. 528
• Line 5: pointer 463891 (EI no. 276) cannot be archived because pointer 464656 cannot be.

In a nutshell: the DI 276 cannot be archived because the receipt 319 cannot be. This receipt cannot be archived because of the DI 528 still unfinished in Warehousing.

Second example:
Let us consider the receipt line (Receipt no. 2, EI no. 3, EI line no. 1) that cannot be archived.
The log yields the following result:
LNK 442492 => PTR 441972
11:33:20 LNK 441972 (EINPUTH 01 ALPHA 0000003) <= LNK 443460
Link between LNK 441972 & LNK 442492 (RECEIPTL 01 0000002 0000003 1 1)
Link between LNK 442492 & LNK 443460 (INPUTH 01 ALPHA 0000033)
11:33:21 LNK 443460 (INPUTH 01 ALPHA 0000033) <= STORINGLST 01 ALPHA 0000038
11:33:21 LNK 442492 (RECEIPTL 01 0000002 0000003 1 1)
Link between LNK 441972 & LNK 442492 (RECEIPTL 01 0000002 0000003 1 1)

• Line 1: pointer 442492 (identifying the receipt line ) belong to the pointer group 441972
• Line 2: pointer 441972 (EI no. 3) cannot be archived because pointer 443460 cannot be.
• Line 3: pointer 441972 (EI no. 3) is linked to the pointer 442492 (the receipt line)
• Line 4: pointer 442492 (the receipt line) is linked to the pointer 443460 (DI no. 33)
• Line 5: pointer 443460 (DI no. 33) cannot be archived because of the receipt line no. 38
• Line 6: pointer 442492 (the receipt line) can itself be archived.
• Line 7: pointer 441972 (EI no. 3) is linked to the pointer 442492 (the receipt line)

In a nutshell: the receipt line cannot be archived because it is attached to the EI no. 3 that cannot be archived because of the receipt line no. 38 to which it is attached via the DI no. 33.

In the event of the data being already archived, the tool specifies in the log:
- the date on which the data has been moved from the live folder to the archive folder.
- the list of the other data making this archive group.

Log example:
LNK 15417 => Archive date = 27/05/2008
Table DLVORDERH: Delivery orders
CM DEPOT 0000123
Table PICKORDER: Preparation orders
CM DEPOT 0000431
CM DEPOT 0000432
CM DEPOT 0000433
CM DEPOT 0000434
VACATION table: Waves
CM DEPOT 0000442
CM DEPOT 0000441
OUTPUTM table: Output movements
CM DEPOT 0000002761
CM DEPOT 0000002753
CM DEPOT 0000002754
CM DEPOT 0000002762
CM DEPOT 0000002755
CM DEPOT 0000002756
CM DEPOT 0000002760
DLVORDERL table: DO lines
CM DEPOT 0000123 1
SUBVAC table: Under wave number
CM DEPOT 0000441 1
CM DEPOT 0000442 1

Archiving/purge in Warehousing

In the Archiving/purge Supervisor function (GESAHI function), a "Functions" menu has been added, with the "Initialize the links" and "Diagnostic help" options.

Diagnostic help

The diagnostic support for the non-archiving generates a log based on the HISLIK records of the archiving code of type 'L' or 'G' as well as the HISPTR of the associated data, without any data being impacted.

Initialize the links

The initialization of links deletes the HISLIK records of the archiving code of type L' or 'G' and resets to zero the HISPTR of the associated data.
As a consequence, for an archiving code, the diagnostic support can only yield results if the links have not been reinitialized since the last archiving (in simulation mode or not). It is therefore important not to start the initialization of links without any real reason. This is why it is no longer started each time the "Save" button is clicked. It is only the user's request that can trigger the initialization, either from here or y starting the archiving/purge function (GESAHI function).
The initialization of links must only be requested if something has been modified in the setup of an archiving code or in its standard or specific processings. it can for instance be something that may impact the composition of the data groups or of the links between these groups.

Using the Archiving/purge function (GESAHI function)

Starting this function without initializing the links can save valuable time since the groups and links created on last starting the archiving/purge are kept.

The simulation inhibits the creation of data in the archived folder as well as the deletion of data. On the other hand, it updates the HISPTR fields of the various tables and the HISLIK table (except for records of type 'E'). This means that after performing an archiving in simulation mode, a non-archiving diagnostic can be launched.

Except in some specific cases, it is recommended to start this function without requesting details either on the historized/purged records or on the links between records, The purpose is to avoid obtaining an overly bulky and confusing log.

Entry screen

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Application error: HISPTR=0

The data entered does not exist in the HISLIK table. In other words, it is still under process in Warehousing (not having a final status).

Tables used

Refer to documentation Implementation