Introduction:

Reads the job card in an Adobe Central Field Nominated File and creates an output XML file that can then set JetTrac JobController variables for any part of the job card that needs to be used within that job, like what printer or filename to send to/create, what printer driver to use, etc.

Technical Support:

If you need assistance in installing and configuring JetTrac JobCardProcessor™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac JobCardProcessor™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.

How to run JTJobCardProcessor:
To run JTJobCardProcessor you will need these files in the same folder:

JTJobCardProcessor.exe

ExitHandler.dll
Executable files and dll files should not be edited for any reason.

Default Functionality:

When JTJobCardProcessor is run as a step in a JetTrac job it will open up the input file (which needs to be a Field Nominated File with a ^job on line 1) and read the content of the ^job line and compare it to the config file entry then sets variables in JobController from the instructions in the config file.
When setting up a job step using JTJobCardProcessor in JobConfig the only lines of the config you need to worry about are the first line (for the config file), the Input DAT and the Output XML. If left as an asterisk * the Input DAT will be whatever file is in the data folder that triggered the job running. This works well if it’s the first step but if the input is also the output of a previous job step you would need to specify the fully qualified path of the input DAT to be read in.

In JobConfig, file paths entered should not be in quotes.
As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.
For more specifics go to the JetTrac Field ServiceJobConfig page.

JTJobCardProcessor Command Line:

“C:\JetTrac\Programs\JTJobCardProcessor\JTJobCardProcessor.exe” input.dat output.xml JTJobCardProcessor.ini JobController.log
The command line begins with the file path to the module’s executable file followed by the path to the input DAT file, the desired path and name for the output XML file, along with the file paths to the config and log files. Each part of the command line is the fully qualified path to the file, in quotes, separated by a space (it doesn’t matter how many)

Job Step Configuration Window in JobConfig for JetTrac JobCardProcessor:

Sample Config File:

Variables=afp:AFP,abmk:ABMK,z:Printer,asp:PrinterDriver

Additional Notes:

The INI file is key-value format and has one required key.

The key is Variables and the value is a comma separated list of Job Card commands and the associated JobController Variable Name that should be set. Within one variable you need to specify the command, e.g. z or asp (with the normal – in front) then a colon then the JobController variable name you want to set.
For example, if the job card was this:
^Job PurchaseOrder -AFXON =APFON -RTRUNC -z\\Server\ShareName -aspHPLJ4
The there would be two JobController variables set:

Printer with a value of \\Server\ShareName

PrinterDrive with a value of JPLJ4
The output XML would contain this:
<?xml version=”1.0″?>

<variables>

<AFP/>

<ABMK/>

<Printer>\\Server\ShareName</Printer>

<PrinterDriver>HPLJ4</PrinterDriver>

<UnusedOptions>^JOB PurchaseOrder -AFXON -APFON -RTRUNC</UnusedOptions>

</variables>
You could then run SetVariables to set any variables that you want to use in subsuquent job steps.