Accessing the EXEC testing facility
The following figure shows an example.
BMC Software ------------------ EXEC Management ----------------- BMC AMI OpsA
COMMAND ===> TGT ===> SYSC
INTERVAL ==> 1 DATE --- 01/01/29
STATUS --- INPUT Scroll right/left TIME --- 07:29:58
Primary command: Sort
EXECs defined 159 Scheduled 2 Enabled 159
High Priority running 0 Queued 0 1
Norm Priority running 0 Queued 0 7
PRESS EXPAND TO VIEW EXEC ACTIVITY
(B)ROWSE, (E)NABLE, (D)ISABLE, (S)ELECT EXEC, (T)EST EXEC
LC NAME STATUS GROUP FUNCTION CODE AUTHOR DESCRIPTION
________ _ ________ ________ __ ________ _________________________
_ PAEXP01 ENABLED CIM4
_ PAEXP02 ENABLED CIM4
_ PAGPNL ENABLED CIM4
_ PALIST ENABLED CIM4X
T PARSE ENABLED SYSTEMS UTIL ERNST ENQ CHECKER FOR MULTISYST
_ PATTERN ENABLED RAE2
_ POST ENABLED RAE1
_ PRGAAO ENABLED RAE1
_ PROV1 ENABLED RAE1
COMMAND ===> TGT ===> SYSC
INTERVAL ==> 1 DATE --- 01/01/29
STATUS --- INPUT Scroll right/left TIME --- 07:29:58
Primary command: Sort
EXECs defined 159 Scheduled 2 Enabled 159
High Priority running 0 Queued 0 1
Norm Priority running 0 Queued 0 7
PRESS EXPAND TO VIEW EXEC ACTIVITY
(B)ROWSE, (E)NABLE, (D)ISABLE, (S)ELECT EXEC, (T)EST EXEC
LC NAME STATUS GROUP FUNCTION CODE AUTHOR DESCRIPTION
________ _ ________ ________ __ ________ _________________________
_ PAEXP01 ENABLED CIM4
_ PAEXP02 ENABLED CIM4
_ PAGPNL ENABLED CIM4
_ PALIST ENABLED CIM4X
T PARSE ENABLED SYSTEMS UTIL ERNST ENQ CHECKER FOR MULTISYST
_ PATTERN ENABLED RAE2
_ POST ENABLED RAE1
_ PRGAAO ENABLED RAE1
_ PROV1 ENABLED RAE1
After the EXEC Management panel is displayed, test an EXEC by following these steps:
To test an EXEC
- Locate the EXEC name in the member list.
- In the LC column, place a T (for Test EXEC).
In the figure EXEC Management application panel, an EXEC named PARSE is selected to be tested. - Press the Enter key.
The EXEC is loaded and the EXEC Test panel is displayed automatically. - BMC Software --------------------- EXEC Test ---------------------------------
COMMAND ===>
EXEC === QAOBCMD2 ID === 3 DATE --- 25/08/26
Options: B - Browse EXEC output V - Variable access TIME --- 14:12:03
C - Conditional Breakpoints O - OSPI session display
Primary Commands:
STEP - Single step execution CONTinue - Execute, stop at breakpoints
RUN - Execute without stopping CANcel - Terminate execution
L - Locate by line number Find - Find string
OFF - Remove all breakpoints CMDSHOW ON/OFF -Show/remove this display
SKIP - Skip current statement FORCE - Force terminate EXEC
VARON/VAROFF | EXPAND - Variable substitution on current line
Line Commands --- Break (A)fter, Break (B)efore, (O)ff
***************************************************************
B->/* REXX QAOBCMD2 */ 00001
/* DOC GROUP(AO) FUNC(SAMPLE) AUTHOR(BMC) 00002
/* DOC DESC(Sample EXEC to return command response to a batch 00003
00004
/*------------------------------------------------------------ 00005
* Sample EXEC which can be used to send command responses to a 00006
* batch job. 00007
* 00008
* No modifications to this EXEC are required. Copy execs QAOBC 00009
* and QAOBCMD3 to the UBBPROC dataset. 00010
* 00011
* This EXEC is submitted by batch job QAOBCMD1. QAOBCMD1 uses 00012
* TSO to submit QAOBCMD2. Since QAOBCMD2 runs under TSO, it 00013
* contains no IMFEXEC statements. 00014
* 00015
* QAOBCMD2 is passed 2 parameters from the batch job: 00016
* 00017
* 1. SS1 The SSID of the BBI/SS PAS where 00018
* the command should run. 00019
* 00020
* 00021
* 2. COMMAND1 This is the fully qualified 00022
* IMFEXEC CMD statement containing the 00023
* command to be issued by AO. 00024
* 00025
* QAOBCMD2 uses AO Anywhere to invoke EXEC QAOBCMD3 on the 00026
* desired system. The SHARE parameter on the AOEXEC SELECT 00027
* EXEC statement allows the command to be passed to QAOBCMD3 00028
* 00029BMC Software --------------------- EXEC Test ---------------------------------
COMMAND ===>
EXEC === QAOBCMD2 ID === 3 DATE --- 25/08/26
Options: B - Browse EXEC output V - Variable access TIME --- 14:12:03
C - Conditional Breakpoints O - OSPI session display
Primary Commands:
STEP - Single step execution CONTinue - Execute, stop at breakpoints
RUN - Execute without stopping CANcel - Terminate execution
L - Locate by line number Find - Find string
OFF - Remove all breakpoints CMDSHOW ON/OFF -Show/remove this display
SKIP - Skip current statement FORCE - Force terminate EXEC
VARON/VAROFF | EXPAND - Variable substitution on current line
Line Commands --- Break (A)fter, Break (B)efore, (O)ff
***************************************************************
B->/* REXX QAOBCMD2 */ 00001
/* DOC GROUP(AO) FUNC(SAMPLE) AUTHOR(BMC) 00002
/* DOC DESC(Sample EXEC to return command response to a batch 00003
00004
/*------------------------------------------------------------ 00005
* Sample EXEC which can be used to send command responses to a 00006
* batch job. 00007
* 00008
* No modifications to this EXEC are required. Copy execs QAOBC 00009
* and QAOBCMD3 to the UBBPROC dataset. 00010
* 00011
* This EXEC is submitted by batch job QAOBCMD1. QAOBCMD1 uses 00012
* TSO to submit QAOBCMD2. Since QAOBCMD2 runs under TSO, it 00013
* contains no IMFEXEC statements. 00014
* 00015
* QAOBCMD2 is passed 2 parameters from the batch job: 00016
* 00017
* 1. SS1 The SSID of the BBI/SS PAS where 00018
* the command should run. 00019
* 00020
* 00021
* 2. COMMAND1 This is the fully qualified 00022
* IMFEXEC CMD statement containing the 00023
* command to be issued by AO. 00024
* 00025
* QAOBCMD2 uses AO Anywhere to invoke EXEC QAOBCMD3 on the 00026
* desired system. The SHARE parameter on the AOEXEC SELECT 00027
* EXEC statement allows the command to be passed to QAOBCMD3 00028
* 00029The EXEC Test Control panel shows a scrollable listing of the EXEC at the bottom of the panel. The upper portion of the panel contains information about the available commands. Whenever an EXEC is tested, the debugger suspends execution before the first statement.
The current position of the EXEC during testing is indicated by three factors:
- The line is highlighted.
- An arrow to the left of it points at it.
- The character B (for before) or A (for after) prefixes it.
The field near the top of the panel, labeled EXEC, contains the name of the currently tested member. When working with nested EXECs (EXECs that call other EXECs as subroutines by using the IMFEXEC SELECT WAIT(YES) command), the debugger always reflects the name of the EXEC currently executing. Therefore, the value of the EXEC field can change during the debugging session and may be used to establish a point of reference for the level of processing.
If you are debugging an EXEC (EXECA) that calls another EXEC (EXECB) with IMFEXEC SELECT WAIT(NO), EXECB will execute and the debugging application has no control over EXECB and EXECB cannot be debugged.
The ID field shows the identification assigned to the current thread, so it remains constant throughout the debugging session. This field also reflects the number of EXECs executed since the last SS restart (this number does not include nested EXECs).
Because a large portion of the panel is taken up by command information that is not required by the more advanced user, the bottom portion of the panel can be expanded to cover the upper portion of the panel.
To expand the view, issue the CMDSHOW OFF primary command.
The panel will look like the following figure:BMC Software --------------------- EXEC Test ---------------------------------
COMMAND ===>
EXEC === QAOBCMD2 ID === 3 DATE --- 25/08/26
Options: B - Browse EXEC output V - Variable access TIME --- 14:12:03
C - Conditional Breakpoints O - OSPI session display
Primary Commands:
STEP - Single step execution CONTinue - Execute, stop at breakpoints
RUN - Execute without stopping CANcel - Terminate execution
L - Locate by line number Find - Find string
OFF - Remove all breakpoints CMDSHOW ON/OFF -Show/remove this display
SKIP - Skip current statement FORCE - Force terminate EXEC
VARON/VAROFF | EXPAND - Variable substitution on current line
Line Commands --- Break (A)fter, Break (B)efore, (O)ff
***************************************************************
B->/* REXX QAOBCMD2 */ 00001
/* DOC GROUP(AO) FUNC(SAMPLE) AUTHOR(BMC) 00002
/* DOC DESC(Sample EXEC to return command response to a batch 00003
00004
/*------------------------------------------------------------ 00005
* Sample EXEC which can be used to send command responses to a 00006
* batch job. 00007
* 00008
* No modifications to this EXEC are required. Copy execs QAOBC 00009
* and QAOBCMD3 to the UBBPROC dataset. 00010
* 00011
* This EXEC is submitted by batch job QAOBCMD1. QAOBCMD1 uses 00012
* TSO to submit QAOBCMD2. Since QAOBCMD2 runs under TSO, it 00013
* contains no IMFEXEC statements. 00014
* 00015
* QAOBCMD2 is passed 2 parameters from the batch job: 00016
* 00017
* 1. SS1 The SSID of the BBI/SS PAS where 00018
* the command should run. 00019
* 00020
* 00021
* 2. COMMAND1 This is the fully qualified 00022
* IMFEXEC CMD statement containing the 00023
* command to be issued by AO. 00024
* 00025
* QAOBCMD2 uses AO Anywhere to invoke EXEC QAOBCMD3 on the 00026
* desired system. The SHARE parameter on the AOEXEC SELECT 00027
* EXEC statement allows the command to be passed to QAOBCMD3 00028
* 00029This section contains the following topics:
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*