A need to customize additional information within the JobController log file with specific pieces of data and in an organized manner.
If you need assistance in installing and configuring JetTrac JBCLog™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at firstname.lastname@example.org. Please note that the JetTrac JBCLog™ 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.
JetTrac JBCLog can only be run within JobController by adding it to a job.
Writes additional custom information to the JetTrac JobController log file.
When setting up a job step using JTJBCLog in JobConfig the only line of the config you need to worry about is the first, in this line you fill whatever fixed strings or variables you want to be written to the JobController.log file at this step.
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 BYODJobConfig page.
Within JobController job:
!x JBCLog * JBC.LOG “””@MDFName.””” “Writes a line to JobController.log File with whatever fixed strings and variable names that are desired”
This command line is a bit different, it has a special command to write whatever the variable @MDFName holds to the JobController log file.