The following essential rule has been changed in all Procars event creation.
The following programs are affected.
Affected Programs
Program |
Version |
Release |
|---|---|---|
aexpgm3 |
5.00 |
Rel I+J |
trkins |
4.22 |
Rel I+J |
trkpar3 |
1.91 |
Rel I+J |
trkins3 |
4.15 |
Rel I only |
trkins3s |
3.77 |
Rel I only |
Automatic Manifest Event Generation
Automatic Manifest Event Generation has been changed from hardcoded generation of IMAN/TMAN event to a configurable generation via TRKPAR3 (use TRKPAR3 settings for new group Air Export / MAWB Print - Events for HAWBs).
Configure a automated event for manifest event generation in TRKPAR3 in order to conserve the previous behaviour.
Event Insertion Rule Amendment
The behaviour for automatic insertion/update of tracking events has been changed substantially:
Former versions of TRKINS prevented the insertion/update of any tracking event if it already existed but only differed in the date/time, for all tracking events and independently TRKPAR3 settings.
This general rule has been removed. Event will always be inserted or updated, depending upon single/multipe settings from TPTMNT. Special rules only apply when TRKINS is invoked with special commandline option "-NOUPDT".
Note: The change makes correct "Update/Write-Only" settings in TRKPAR3 even more important. If one wishes to conserve the "old" behaviour, one should ensure that the "W" (=Update/Write-Only) column in TRKPAR3 contains a '*' character. If the '*' character is configured, the commandline option "-NOUPDT" is used which prevents updates. The following examples only apply for TRKPAR3 setting allowing upate ("W" column contains a space):
Example 1
AWB FRA 01.08.2009 15:29 AWB PRINTED
exists and the event
AWB FRA 02.08.2009 09:29 AWB PRINTED
should be generated (triggered e.g. by TRKPAR3 settings, automated on AWB printing).
Former implementation prevented the event to be inserted and kept the event dated 01.08.2009 15:29.
The new implementation will overwrite the event if "AWB" is configured to be Single or Single-per-Location in TPTMNT (so the date of the first AWB print will be lost) or will insert the new event additionally to the existing one (in case of multiple configuration from TPTMNT).
Example 2
AWB FRA 01.08.2009 15:29 AWB PRINTED 01.08. 15:29
exists and the event
AWB FRA 02.08.2009 09:29 AWB PRINTED 02.08. 09:29
should be generated (triggered e.g. by TRKPAR3 settings, automated on AWB printing).
Behaviour did not changed since the events differ in the remarks. The event is inserted/updated applying TPTMNT3 single/multiple configuration.