JobSuite: Software for automated monitoring stations.

The JobSuite folder on the installation CD contains four programs:

- JobCopy
- JobFile
- JobRedo
- JobWrite
These programs collectively form JobSuite. Before using JobSuite, install SSMT2000 in the
default folders and be sure it is working properly.

JobFile.exe
Once the Auto File Transfer program completes the automated download of hourly files (Step 1
of automated processing), JobFile.exe moves the files into directories that have the date encoded
in their names. The encoding is in the format YYYY-MDD, where YYYY is the four digit year,
M is a hexadecimal value for the month (A=10/October, B=11/November, C=12/December), and
DD is a zero-padded two-digit day of month.

The program syntax is:

JobFile [FROMDIR=<source path>[,TODIR=<destination path>[,DELAY=<delay in hours>]]]

This completes Step 2 in the automation of the processing.

JobCopy.exe
At the same time that the main processing sequence is running, a script within the Kermit™ 95
program operates to transfer the databases to a secondary office. There, the JobCopy program
updates the appropriate folders so that operators can use a second instance of the DISPMT
program to monitor the system remotely.
JobCopy checks to see if the last Kermit log file shows a successful transfer. If so, JobCopy
copies the data to its correct directories.

The program syntax is:

JobCopy [FROMDIR=<source path>[,TODIR=<destination path>[,KERMITLOGDIR=<path to kermit logs>]]]

JobWrite.exe: (a) JobWriter

This program must be installed in the folder to which the Auto File Transfer program transfers
MTU data files. Currently this folder is "C:\Net-Tser". JobWrite will not work if SSMT2000 is
not installed in the "C:\Program Files\SSMT2000" folder.

The purpose of the JobWriter program is to automatically create the .JOB and .PRM files
necessary for processing.

JobWriter requires:
- SSMT2000 installed in C:\Program Files\SSMT2000
- A JobWrite.PRM file in the same directory as JobWrite.EXE
- A suitable PFT file (see the next section)
- A JobWrite.DAT file in the same directory as JobWrite.EXE (see the next section)
JobWrite.exe: (b) The JobWrite.DAT file
The JobWrite.DAT file contains information in the following format:
<serial number 1>=<4 character site name 1>
…
<serial number N>=<4 character site name N>
PFTFILE=<name of PFTFILE>

The PFT filename can be determined by manually running SSMT2000 and clicking the ‘Make
PFT' button, after at least one hour of data has been acquired:
- Use Auto File Transfer to transfer the files.
- Run the File-MTU program to move the file into the processing folder.
- Launch SSMT2000.
- Set the Site Parameters (TBL) folder to the processing folder (eg. "C:\Net-Tser\2002-B01").
- Check the TBL file contents using the multi-table editor.
- Click 'Make PFT'.
- Select the appropriate options. NOTE: the output data format must be '2 Frequencies Per
Octave' and you must select ‘Hourly files’.
- Click 'Save'.
- Note the 'File name:' at the bottom of the dialog box, and use that name in the JobWrite.DAT
file as shown above.
- Click 'Close'.

JobWriter reads the JobWrite.DAT file. It then breaks the serial numbers and site names into an
array. The PFT file is stored in a variable. The .JOB file is then created. It writes the TBLDIR,
TBLEDITDIR, CLBDIR, CLCDIR, PFTDIR, and then begins to use the array created from the
JobWrite.DAT file. For each serial number, JobWriter finds the first hourly file (checking A
through Z) and creates a TBL and TBLVAR entry in the JOB file. This selects the TBL file and
loads it into memory, and the TBLVAR then modifies the site name to use the 4 character site
name substitution instead of the serial number. Next, the PFTFILE line is written to the JOB file.
The last step is the creation of the required PRM file(s). A PRM entry is created in the JOB file
for every serial number in the JobWrite.DAT file. This completes the JOB file creation.

The JobWrite.DAT file can contain comments. Comment lines begin with a semi-colon. Because
semi-colons and colons are difficult to distinguish, JobWriter checks for the error of a line
beginning with a colon. JobWrite will end silently without causing the data to be processed and a
log file entry will show the problem line.
JobWrite.exe: (c) The JobWrite.PRM file
This file looks exactly like a normal PRM file, except for these four lines, which serve as a
template for JobSuite:
Table File for Series # 1 : /C:\NET-Tser\YYYY-mDD\SSSSmDDV.TBL
Table File for Series # 2 : /C:\NET-Tser\YYYY-mDD\
Table File for Series # 3 : /C:\NET-Tser\YYYY-mDD\
Table File for Series # 4 : /C:\NET-Tser\YYYY-mDD\
During automatic processing, these template lines are replaced with the appropriate date (year,
month [0-C Hex], and day), serial number, month (0-C Hex), day, and a letter indicative of the
hour (A-X).

Create the PRM file by using the 'Edit PRM' button in SSMT2000 after at least one hour of
acquisition has been obtained:
- Launch SSMT2000.
- Set the Site Parameters (TBL) folder to the processing folder (eg. "C:\Net-Tser\2002-B01").
- Click 'Edit PRM'.
- In the ‘Select Frequencies’ frame, select ‘Only One Range’ and choose ‘.MT’ (1).
- Create the first PRM file.
- Quit SSMT2000.
- Use Notepad to edit the .PRM file so that it matches EXAMPLE 2:
==============================================================
--- EXAMPLE 1 (as produced by the software) ---
Table File for Series # 1 : /C:\Net-Tser\2002-926\1334926A.TBL
Table File for Series # 2 : /C:\Net-Tser\2002-926\
Table File for Series # 3 : /C:\Net-Tser\2002-926\
Table File for Series # 4 : /C:\Net-Tser\2002-926\

--- EXAMPLE 2 (as edited by the user) ---

Table File for Series # 1 : /C:\Net-Tser\YYYY-mDD\SSSSmDDV.TBL
Table File for Series # 2 : /C:\Net-Tser\YYYY-mDD\
Table File for Series # 3 : /C:\Net-Tser\YYYY-mDD\
Table File for Series # 4 : /C:\Net-Tser\YYYY-mDD\
==============================================================
- Save this file as JobWrite.PRM, and copy it to the parent folder (eg. C:\NET-Tser).

It is best to collect one hour’s worth of data, manually create a PRM file, and then revise these
four lines in that file.
JobWrite.exe: (d) Command Line Parameters
TBLEDITDIR: specifies where TSTOFT.EXE and DFTREAD.EXE are located.
The default value is C:\EMT-SW\PROG\
(NOTE: The path MUST include the final “\”)
CLBDIR: specifies where the Box Calibration Files are located.
The default value is C:\NET-BCAL
(NOTE: The path must NOT include a final “\”)
CLCDIR: specifies where the Sensor Calibration Files are located.
The default value is C:\NET-BCAL
(NOTE: The path must NOT include a final “\”)
PFTDIR: specifies where the PFT files are located.
The default value is C:\EMT-SW\SSMT-PFT
(NOTE: The path must NOT include a final “\”)
PROCDIR: specifies which day of data to process.
This can be either a date (eg. PROCDIR=2002/11/30) or the string name of
the directory (eg. PROCDIR=2002-B30).
The default value is yesterday’s date.

You can specify multiple parameters by separating them with commas like this:
Jobwrite CLBDIR=C:\MyCals,CLCDIR=C:\MyCals,PROCDIR=C:\MyData

JobWrite.exe: (e) Scheduling JobWrite

Schedule JobWrite after having set up the scheduling for the Auto File Transfer, which moves the
files into a known directory such as C:\Net-Tser, and after having set up the scheduling for the
JobFile program. (Previously, the program FILE-MTU was used for this activity.) JobFile moves
the files into the dated subdirectories such as C:\Net-Tser\2002-B30. Once the Auto File Transfer
is set up, you will know the base directory and the calibration directories. Use a multi-parameter
form of the command line to schedule Jobwrite to be called appropriately. For example, a
command line like this:

Jobwrite CLBDIR=C:\NET-BCAL,CLCDIR=C:\NET-BCAL,PFTDIR=C:\EMT-SW\SSMT-PFT

will suffice to routinely process yesterday’s data.

JobWrite.exe: (f) JobWrite.LOG

In order to record what jobs have run and what parameters were used, JobWrite creates a log file.
If there are problems with the processing, open the log file to see if the problem lies with errors in
the directory names or paths or if there is some other error.

JobWrite is Step 3 in the automation of the processing.

JobRedo.exe
Sometimes there are data corrections that require repetition of the automated data processing.
Use JobRedo for this task. Launch JobRedo, open the folder containing the date-encoded data
folders, then select the affected date-encoded folders and click 'Process'.

If you have problems, contact Phoenix Geophysics:

mail@phoenix-geophysics.com
Tel. +1 (416) 491-7340