EXEC Thresholds panel
The following figure shows an example of the EXEC Thresholds panel:
COMMAND ===> TGT --- BBSYSA
DATE --- YY/MM/DD
TIME --- 11:41:52
Member Current
EXABCNT ===> 3 3 # of ABENDS allowed before EXEC disabled
MAXNORM ===> 5 5 Maximum concurrent Normal EXECS
MAXHIGH ===> 3 3 Maximum concurrent High Priority EXECS
MAXNORMQ ===> 5 5 Maximum Normal EXECs Queued
MAXHIGHQ ===> 3 3 Maximum High Priority EXECs Queued
MAXHOTQ ===> 10 10 Maximum Hot/First priority EXECs Queued
WARNLVL1 ===> 65 65 Initial threshold (percent)
WARNLVL2 ===> 80 80 Secondary threshold (percent)
SELLIM ===> 10 10 Maximum depth for SELECT with WAIT(YES)
MAXTPUT ===> 0 0 Maximum TPUT allowed in each EXEC
Press END to save changes, CANCEL to cancel changes
This panel provides two columns of data:
- On the left, the value of the parameters in the AAOEXPxx member for the target BBI-SS PAS
You can enter your modifications on this side of the panel. - On the right, the value of the parameters that are currently in effect for the target BBI-SS PAS; these values cannot be edited
EXEC Thresholds panel fields
The following table describes the fields on the EXEC Thresholds panel:
Field name | Description |
|---|---|
Member | Specifies the values for the new AAOEXPxx member |
Current | Specifies the values in the AAOEXPxx member that the BBI-SS PAS is currently using These values are stored in CSA. The member that the BBI-SS PAS is currently using is one of the following choices:
|
EXABCNT | Is the maximum number of abends that a single EXEC can sustain before it is disabled Valid values range from 1 to 99 and the default is 5. For example, if you specify EXABCNT=10 and an EXEC abends 10 times, the EXEC is disabled after the tenth abend. |
MAXNORM | Is the maximum number of EXECs that can execute concurrently on Normal priority threads Valid values range from 1 to 99 and the default is 1. |
MAXHIGH | Is the maximum number of EXECs that can execute concurrently on high-priority threads Valid values range from 1 to 99 and the default is 5. |
MAXNORMQ | Is the maximum number of Normal priority EXECs that may be queued for execution Valid values range from 0 to 999 and the default is 0. A value of 0 means that no checking is done. When the maximum number is reached, no more EXECs are scheduled to the Normal priority queue and a warning message is issued: EM6100W MAXNORMQ EXEC 19/ 20, OVER LAST LEVEL (95%) EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed: EM6200I MAXNORMQ EXEC 9/ 20, NO LONGER OVER THRESHOLD EXECs that you schedule with the IMFEXEC command WAIT=YES are never queued. They are executed on the thread of the EXEC that selected it. |
MAXHIGHQ | Is the maximum number of High priority EXECs that may be queued for execution Valid values range from 0 to 999 and the default is 0. A value of 0 means that no checking is done. When the maximum number is reached, no more EXECs are scheduled to the high priority queue and a warning message is issued: EM6100W MAXHIGHQ EXEC 19/ 20,OVER LAST LEVEL (95%) EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed: EM6200I MAXHIGHQ EXEC 9/ 20, NO LONGER OVER THRESHOLD EXECs that you schedule with the IMFEXEC command WAIT=YES are never queued. They are executed on the thread of the EXEC that selected it. |
MAXHOTQ | Is the maximum number of First or Hot priority EXECs that can be queued Valid values range from 0 to 999 and the default is 10. A value of 0 means that no checking is done and all Hot or First priority EXECs are queued. When the maximum is reached, no more EXECs with First or Hot priority specified are scheduled until the queue level drops below the maximum level set and a warning message is issued: EM6100W MAXHOTQ EXEC 19/ 20, OVER LAST LEVEL (95%) EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed: EM6200I MAXHOTQ EXEC 9/ 20, NO LONGER OVER THRESHOLD |
WARNLVL1 | Specifies a preliminary percentage of EXECs in a queue that, when met, generates a warning message Valid values range from 0% to 99% and the default is 60%. Use this threshold to set the first percentage that triggers a warning message to be sent. For example, if you set MAXHIGHQ=100, and WARNLVL1=60, a warning message is issued when 60 EXECs are queued to the High- priority queue. The message looks like the following example: EM6100W MAXHIGHQ EXEC 60/ 100, OVER 1ST LEVEL (60%) This threshold is applicable to the High and Normal priority queues. |
WARNLVL2 | Specifies a secondary percentage of EXECs in a queue that, when met, generates a warning message Valid values range from 0% to 99% and the default is 75%. Use this threshold to set a second percentage that triggers a warning message to be sent. For example, if you set MAXHIGHQ=100 and WARNLVL2=75, a warning message is issued when 75 EXECs are queued to the high-priority queue. The message looks like the following example: EM6100W MAXHIGHQ EXEC 75/ 100, OVER 2ND LEVEL(75%) In addition, a second message is issued that identifies the first EXEC that was not scheduled because of this queuing condition: EM6150W EXEC-COLORS NOT QUEUED,OVER LAST LEVEL THRESHOLD In this example, Colors is the name of an EXEC that was not scheduled. Additionally, no more EXECs are scheduled to the high-priority queue until the usage percentage of the queue is less than the value set for MAXHIGHQ. This threshold is applicable to the High and Normal priority queues. |
SELLIM | Is the maximum number of active EXECs on a single thread Valid values range from 0 to 99 and the default is 0. This parameter is designed to control recursive calls (where EXECA schedules EXECB, and EXECB schedules EXECC, and so on) that run out of control, and can potentially fill up the private storage in the BBI-SS PAS and cause automation to stop. An example of recursive calls is EXECA schedules EXECB with the WAIT=YES parameter and EXECB in turn, calls EXECA. |
MAXTPUT | Is the maximum number of TSO TPUTs that is allowed for each execution of an EXEC Valid values range from 0 to 999 and the default is 0. TPUTs for EXECs scheduled with the WAIT=YES parameter are counted separately from the scheduling EXEC. If the maximum is exceeded, the following message is issued and subsequent TPUTs are ignored until the EXEC terminates: EM0026W TPUT JOURNALLING SUSPENDED,BACKLOG HAS EXCEEDED MAXIMUM |
This section contains the following topic: