Writing Specifications Using a Text Editor

The WinCross user interface eliminates the traditional need for a programmer to write complicated specification files, referred to as “job files” in WinCross. Using the WinCross user interface, syntax is automatically checked when you enter row, table and filter logic, or create glossary variables. If you prefer, however, you can edit or create WinCross specifications using a conventional text editor or View|Job File. (The only way to process tables is by using Run|Tables.)

 

When using a text editor to create or edit job files, always engage the Run syntax check only option in Run|Tables to check for errors prior to running your tables. Upon selecting Run with Run syntax check only, errors are reported to the report log file (*.lg). Such errors may include warnings about improper use of reserved key words (NET, SUB, etc.) or a misuse of the Scan (S) feature for variables having different lengths. The report log is automatically displayed on screen when an error or warning occurs.

 

When creating or editing a job file using a text editor, you must save it in ASCII format. If you save it using the *.job file extension, it will be displayed in the file list on the Open Job dialog box. To see what a job file looks like, you can print the EXAMPLE-VARIABLE.JOB sample file, automatically installed with WinCross. You can print a job file from WinCross using File|Print|Print Job or from text editors such as WordPad or Notepad. When printing a job file from WinCross, it automatically inserts line numbers for reference. Do not include these when creating your own job file using a text editor.

 

Some EXAMPLE-VARIABLE.JOB examples are used in the following descriptions:

 

There are six sections that must be present in any job file. Each section title must be entered in uppercase lettering, be enclosed in square brackets and appear in the following order:

 

[VERSION]

[PREFERENCES]

[GLOSSARY]

[TABLES]

[BANNERS]

[TITLE]

 

IMPORTANT: Section titles should be formatted flush left and begin in column 1, as should individual table numbers in the [TABLES] section. With a few exceptions, all other lines in each section must be indented one space.

Related topics:

View|Job File