User Guide

______________________________________________________

GSSEVENT – SCRIPT

The GSSEvent program uses files located within the \GSS\GSSEvent\ECRData These files

must only be edited with a full comprehensive of the actions they involve as errors

within this file will result in the loss of data.

[Collect Sales Data]

Action01=GSSPOSNET_CREATE

Action02=GSSPOSNET_ATTACH

Action03=GSSPOSNET_GETFILELIST *.BKP

Action04=GSSPOSNET_RECEIVE_LATEST_FILE {LOCATIONNO}\

Action05=GSSPOSNET_VERIFY_BKP_FILES {LOCATIONNO}\

Action06=GSSPOSNET_DELETE_ALL_FILES

Action07=GSSPOSNET_GETFILELIST *.TXT

Action08=GSSPOSNET_DELETE_ALL_FILES

Action09=GSSPOSNET_GETFILELIST *.JNL

Action10=GSSPOSNET_DELETE_ALL_FILES

Action11=GSSPOSNET_DETACH

Action12=GSSPOSNET_FREE

Action13=PROCESS_BKP_FILES {LOCATIONNO}\

Action14=LOAD_JOURNAL JNL{LOCATIONNO}.CSV

Action15=FILE_SALES_DATA

Action16=UPDATE_USAGE

Action17=UPDATE_TOTALS

Shown above is the Z Collect Data event from the FS-3600 Event Library. Preceding the

action list is a section that tells GSSEvent how to deal with failures within the

subsequent action list.

The first line ‘OnFailure=Z Collect Data’ is the default event that GSSEvent should insert

into the event timetable if there is any kind of failure within the script that is not

explicitly dealt with by a subsequent OnFailure line.

GSSEvent will insert a new event into the timetable a number of minutes after the failed

event, up to a maximum number of times. These retry events are controlled by two

lines in the GSSEvent.INI file, in the [GSSEventOptions] section.

‘MaxRetries’ controls how many attempts GSSEvent will try the event and

‘TimeBeforeRetry’ gives the time in minutes that the retry event should be inserted into

the timetable after the failure.

The log of failed events will only show the last failed event after all OnFailure events and

maximum retries has been exhausted.