The following fields are common to many or all of the AOF test panels:
If you have already extracted data from OPSLOG Browse to use for your rule test and you enter a Y in this field, the AOF displays the AOF Test Data Selection panel, where you can view the extracted data. For more information about this panel, see Step 6: View and Verify Extracted Data in this chapter.
If you have not extracted data and you enter a Y, the AOF displays the OPSLOG Browse Test Data panel so that you can extract data. For more information about this panel, see Step 4: Access OPSLOG Browse in this chapter.
The name of the simulated console being used to enter the command or send the message.
The simulated exit type associated with the current command. Types are IMS, JES3, z/OS, and OMG.
The four-character ID of the IMS system being simulated.
For a message rule test, the simulated job name (TSO user ID or task name) associated with the current message.
For a command rule test or a request rule test, the simulated job name (TSO user ID or task name) associated with the current command.
For an end-of-memory rule test, the name of the test. The name of the test can be any valid job name or the wildcard character.
A value indicating how the AOF should treat host commands during the rule test. If the value is YES, commands are issued on your system. If the value is NO, commands are not issued, but they are simulated for test purposes.
For events originating in the generic data set interface or the OMEGAMON interface, this value indicates the report ID associated with the event.
A value indicating if and how the AOF should trace a command that REXX executes. Common values are:
The AOF traces only those host commands that fail.
The AOF traces all clauses before execution, along with the final results. This is useful for general debugging.
Similar to R, but the AOF also traces all REXX clauses and intermediate results.
For details about tracing possibilities, see The REXX Language: A Practical Approach to Programming by M. F. Cowlishaw. You can order a copy of this book from Prentice-Hall.
The identification string for the system.
Specifies eight bytes of data you want to pass between rules that execute for the same event. Depending on what type of rule you are testing, the event can be a command, message, global variable event, OMEGAMON event message, request event, end-of-memory event, or delete-operator-message event.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |