Before moving an IMOD into production, you should test it to verify that the IMOD is working properly.
You test a loaded IMOD from the EXECUTE panel of the IMOD editor. From this panel, you can specify argument strings and the initial stack contents. After the execution is complete, you can retrieve the return string and any resulting stack contents.
To test a loaded IMOD
The EXECUTE panel appears.
Note: For information about the IMOD editor EXECUTE panel, see the online help.
Work STACK Number
Redirect SAY Output to STACK
Redirect TRACE Output to STACK
The EDIT --- ARGUMENTS ISPF editor panel appears.
The length and content of the individual arguments are governed by the ISPF editor. The aggregate length of all argument strings must be less than 4094, calculated as follows:
number_arg_characters + number_arg_lines x 2
The arguments are retained for the entire IMOD editor session and are passed to any executed IMOD whenever the ARG field is blank.
The EDIT --- INITIAL STACK ISPF editor panel appears.
The stack that is passed to the IMOD can contain any records you want. The length and content of the individual stack records are governed by the ISPF editor. The aggregate length of all stack records, calculated as follows, must be less than 32766: number_stack_characters + number_stack_records x 2
The stack records are retained for your entire IMOD editor session and are passed to any executed IMOD.
Your request is passed to the specified address space. After an IMOD is executed, the result (as specified by the terminating RETURN or EXIT instruction) and the final stack contents are available for your inspection in the displayed EDIT --- REST RESULTS panel. If an error occurs, an ISPF error indication appears at the upper right of the panel.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |