AA0009I
EXEC execname NOT SCHEDULED. QUEUES ARE FULL
Explanation: Informational message written to the BBI journal when an EXEC is scheduled but the appropriate EXEC queue is full. The depth of EXEC thread queues are defined in AAOEXPxx as values MAXNORMQ, MAXHIGHQ, and MAXHOTQ. When the EXEC thread is full any EXEC scheduled for that priority is discarded and not processed.
User response: If you feel this is in error, determine which EXECs are currently processing and what automation has scheduled the EXECs. The BBI Control Command of .D E ALL will display all executing and queued EXECs. If you suspect that EXECs are hung or looping use of the .D E CMD and .D E CMD,LONG commands may assist in this determination. These commands show you the last command that BMC AMI Ops Automation has seen. This is not necessarily the current command processing as there may be REXX or CLIST commands processing at the time. If the last command processing was using a TARGET, determine if there is a problem on that target. If gathering documentation for BMC Support, gather doc for both the local and target PASes. If assistance from BMC Support is required, take a console dump of the AO PAS while the EXECs are hung. If the HIGH priority thread is available, the QAODUMP EXEC can be used to obtain that console dump. If all threads are full, use the following DUMP command and response:
DUMP COMM=(provide a title)
R xx,JOBNAME=jobname_of_pas,SDATA=(CSA,RGN,TRT,GRSQ),END
Note:
BMC AMI Ops Automation was previously known as MainView AutoOPERATOR
