Navigation:  Using CGX - Step-By-Step >

CommandLine Operation

 Previous pageReturn to chapter overviewNext page

CommandLine Operation

CGX can be run in command line mode enabling it to be scheduled to run automatically via any task scheduler including the Window's task manager.

 

Any saved template can and should be checked first before scheduling it in a production environment. The Test Command Line Parameters invokes the identical processes that are invoked when the program is launched with command line parameters.  Note that only one copy of CGX can be running at any point in time there you will not be able to test the command line from the command prompt or via a batch file while the program is open.

 

The first step is to select the template you want to check:

 

CmdLine1

 

 

Once the template has been selected, summary information is displayed showing the major various options such as the primary contact folder, message class, output file and export processing mode. The construction of what the command line should be is shown at the bottom of the screen. The command line structure that is displayed conforms to that used by the Windows Task Manager.

 

 

CmdLine2

 

Processing of the template in command line mode can be fully tested by clicking on the "Test Command Line" button.

 

If <Run Quiet> is checked, the template will processed in "silent mode" with no messages being displayed, exactly as it would operate when run in a production setting.

 

If <Simulate> is checked, no actual changes will be applied to an Output dataset if the processing mode for the template is set to <Update>.

 

If the template is processed  successfully, the following message is also displayed.

 

CmdLine3

 

 

RUN-TIME FAILURES:

 

All messages that would typically be displayed while running CGX in online mode are recorded a PgrmMsg log file in addition to any operational and data errors.

 

In addition, CGX also provides 2 other indicators of the success or failure of a runtime failure:

 

1.the Dos ErrorLevel can be checked to see if it contains a value other then zero (= success) which can be checked within a batch file
2.a one line log file is created in the directory where CGX is installed called "clfailed.log" which will contain a one line entry containing the numeric failure code and failure description.