EXEC Thresholds panel fields

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:

• the AAOEXPxx member that was used during the most recent BBI-SS PAS initialization
• the most recently applied AAOEXPxx member

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:

EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed:

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:

EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed:

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:

EXEC scheduling resumes when the queue size drops below the maximum. An informational message is issued to inform you that scheduling has resumed:

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:

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:

In addition, a second message is issued that identifies the first EXEC that was not scheduled because of this queuing condition:

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.