UNIX Scripts
UNIX scripts have the additional execution option being the menu option Execute/ Execute and retain. This option will create a Telnet window to the UNIX host, execute the script, display the results and leave the Telnet window up. Additional commands or a review of what occurred can then be undertaken directly in the Telnet window. When completed the Telnet window should be closed to return to the script editor.
Note: A connection must be correctly set-up to support UNIX script testing. See the installation manual and the section on UNIX connections.
Script Syntax
There are a number of conventions that must be followed if a host script is to be used by the QAD scheduler. These conventions are:
1 The first line of data in 'standard out' must contain the resultant status of the script. Valid values are '1' to indicate success, '-1' to indicate a warning condition occurred but the result is considered a success, '-2' to indicate a handled error occurred and subsequent dependent tasks should be held, -3 to indicate an unhandled Failure and that subsequent dependent tasks should be held.
2 The second line of data in 'standard out' must contain a resultant message of no more than 256 characters.
3 Any subsequent lines in 'standard out' are considered informational and are recorded in the audit trail. The normal practice is to place a minimum of information in the audit trail. All bulk information should be output to 'standard error'.
4 Any data output to 'standard error' will be written to the error/detail log. Both the audit log and detail log can be viewed from the QAD Data Warehouse Designer tool under the scheduler window.