Previous Topic: Testing REXX Programs

Next Topic: Testing Procedure


Include a DEBUG Parameter in Your REXX Program

Before invoking REXX programs from CA Automation Point rules, be sure to test and debug them. A REXX program containing errors can go into a loop without calling or returning control to CA Automation Point.

Note: If you are not sure that a loop in a REXX program will end and you want to ensure that CA Automation Point can cancel the program if it "hangs," insert this statement into the suspect loop:

WAIT 0

If a REXX program does hang, you can always select the "Stop REXX program" option from the Cmdarea menu.

Example:

Most of the sample REXX programs in this guide contain a statement similar to the following, which starts the REXX trace facility (for REXX programs invoked from within rules, you can edit the rules file and temporarily add the DEBUG parameter):

PARSE UPPER ARG . 'DEBUG' +0 DEBUG +1
IF DEBUG \= '' THEN TRACE R

The statement allows the REXX program to execute in "debugging" mode. Invoke the DEBUG option as follows:

progname arguments DEBUG

The trace output displays in the AXCREXX window.