Extract Data as Tab-Separated file from Broadcast Job

JOBXDATA jobfile|jobid

This program extracts statistical and accounting data for an individual job into a tab-separated-field file. The output file name is the same as the given input job instance file but with extension .TAB.  Note that this format is also now available as an output from JOBXLDATA.

If the parameter is given as a job ID number (and if Job ID is specified as being unique within the system) then the program searches for the Job ID. In this case the output file is placed in the EXTDATA directory under the defined USERJOBS directory for the system.

The fields available for extraction are controlled by the file JXFIELDS.LST in the defined USERJOBS directory for your system. Full documentation for the field content and selection appear in the original supplied file. If you define custom variables for your broadcast, you can also add them to the extracted data.  JXFIELDS.DFT-LST shows the full list of available fields, with a brief description of each, but the following features of the field list should be specially noted:

The fields CALLTIME and CONNECT are unlikely to be meaningful when a single job item is attempted both as a fax and as an e-mail transmission.

You can count separately the call and connect times in each of a set of priorities.  For example specifying CALL_6789 as a field name counts the call time for the item when transmitted with priorities six through nine.  This may be helpful when calls are charged differently for different priorities.

Proof and Report FS files are excluded unless the job option keyword ExtractProofRep keyword is given.

Failed transmissions are excluded from the CALLTIME and CONNECT unless job option keyword ExtractFailTimes is given.

If you change or add to the selected fields in JXFIELDS.LST, bear in mind that you will not be able to consolidate files from before and after the change.

You can override the JXFIELDS.LST filename using the UJP command $extract_fields.  This is not recommended because it is usually important to maintain a standard set of fields for all jobs, and these can be placed in the default file.

The jobfile parameter may have a '+' prefix to indicate that the filename is a list of job instance files to be processed.

This program is normally invoked automatically by JOBCONS, but can also be run as an end-job-task or independently from a console session.  It returns a positive errorlevel on failure.

Example:

JOBXDATA @FFJOBS\Steve\NO_JTYPE\JOB00123.UJP

IF ERRORLEVEL 1 ...