Transfer and Error Logs

Gateway will create two logs at midnight in the C:\Gateway\Logs directory containing all of the previous day’s transactions.

The GW@M@D@Y.TXT file is a listing of all the work completed by Gateway. This file is the same as the FlushRpt.txt file from the Reporter screen. Information about the Gateway Transfer Log can be found below

Gateway also creates the SC@M@D@Y.err file. This is a listing of all work threads and status during the transfer process. This file contains the same information as the Reporter’s View Error Log file. Information about the Gateway Scanner Log can be found below

Note: Since these logs are created at midnight, the Time / Date stamp will be for the ‘present’ day even though they contain information about the previous day.

The Reporter screen saves information related to the transfer of files via the Flush To button. The Flush To field contains the name of the text file that contains the complete report of actions that have taken place (unless one exits Gateway and chooses to not add to the file when prompted). This file is located in the Gateway folder.

This file is updated:

To rename the file, change the name of the file in the Flush To field. 

 

Information about the Gateway Transfer log: 

Examples of FlushRpt and GW@M@D@Y:

Date

Scan time

Trans.start

Trans.end

Source file

Destination file

Dest.

Operation

Status

Size

Reason

01/10/08

22:48:53

22:48:53

22:48:53

F:\DAD\FILES\dad.cfi

C:\DAD\FILES\dad.cfi

Local data

COPY

Completed

(9,168)

$100

01/10/08

14:42:18

14:42:18

14:42:18

00002

 

Local data

RC

Completed

(37)

$576

 

Operation codes:

COPY = File Copy
RA = Record & Audio
A = Audio
R = Record
P = Playlist
C = Command

Reason Values

$0        NONE
$1        CUT_RECORDS_DIFFER
$2        AUDIO_FILES_DIFFER_HOST_SIZE
$4        AUDIO_FILES_DIFFER_HOST_LAST_MOD
$8        AUDIO_FILES_DIFFER_REC_DATE
$16     AUDIO_FILES_DIFFER_REMOTE_SIZE
$32     AUDIO_FILES_DIFFER_REMOTE_LAST_MOD
$64     CUTAUX_NOT_FOUND
$128   REMOTE_CUT_RECORD_NOT_FOUND
$256   REMOTE_AUDIO_FILE_NOT_FOUND
$512   FORCE_TRANSFER
$1024 FILES_DIFFER

These values are combined.  For example $3 is $1 & $2

For example:

01/10/08 16:29:44  Scan Rule: error=Can't open host file.

01/10/08 16:29:44  Scan Misc Files *.*: error=Can't exclusively open remote file.

01/10/08 17:44:19  Transport Cut 00020: file=R:\CUTS\00020.WAV->C:\CUTS\00020.WAV error=File copy incomplete.

01/10/08 19:07:11 19:11:06 19:11:08 025PRODB LOCAL DATA P Completed (2,381) $0
01/10/08 19:15:53 --:--:-- --:--:-- 80453 LOCAL DATA RA Deleted (0) $64

There can be many reasons because a file can not be transferred. Inconsistent network connections, files that are presently in use and files that are missing are all examples of such reasons.

 

Information about the Scanner log:

The Scanner.err file lists errors and reasons a file was not transferred. This information can also be found in the Error.txt file. 

The following is an example of a work thread for an audio cut. Here one can see Gateway transfer the file, update the remote Library database along with the Search database, then update it's own database (cutsaux) with details about the completed transfer. 

[01/10/08 18:45:16] WorkThread2: begun for 00006
[01/10/08 18:45:16] WorkThread2: Cut rule 00006
[01/10/08 18:45:16] WorkThread2: transporting file
[01/10/08 18:45:20] WorkThread2: transport complete
[01/10/08 18:45:20] WorkThread2: Updating Cuts record 00006
[01/10/08 18:45:20] WorkThread2: opened C:\DAD\FILES\CUTS.dbf
[01/10/08 18:45:20] WorkThread2: opened C:\DAD\FILES\CUTS.cdx
[01/10/08 18:45:20] WorkThread2: updating fields
[01/10/08 18:45:20] WorkThread2: updating fields completed
[01/10/08 18:45:20] WorkThread2: wrote record
[01/10/08 18:45:20] WorkThread2: quicksearch update complete
[01/10/08 18:45:20] WorkThread2: remote data closed
[01/10/08 18:45:20] WorkThread2: updating cutsaux
[01/10/08 18:45:20] WorkThread2: update cutsaux complete
[01/10/08 18:45:20] WorkThread2: cleaning things up
[01/10/08 18:45:20] WorkThread2: exiting thread: e=0

The following is an example of a work thread for a playlist. Gateway first checks the playlist to see if there are any audio files that need to be transferred. It then queues the list and completes the transfer. 

[01/10/08 19:12:28] WorkThread21: begun for 0703212M (2)
[01/10/08 19:12:28] WorkThread21: Cut rule 0703212M (2)
[01/10/08 19:12:31] Queueing Playlist complete
[01/10/08 19:12:31] Queueing Playlist(d)
[01/10/08 19:12:31] WorkThread21: cleaning things up
[01/10/08 19:12:31] WorkThread21: exiting thread: e=0
[01/10/08 19:12:31] WorkThread22: begun for 0703212M
[01/10/08 19:12:31] WorkThread22: Cut rule 0703212M
[01/10/08 19:12:32] WorkThread22: cleaning things up
[01/10/08 19:12:32] WorkThread22: exiting thread: e=0