How can we assure that CA Hyper-Buf will not process started tasks in the system?

Document ID : KB000046196
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

How can we assure that CA Hyper-Buf will not process started tasks in the system?

Resolution:

This Constraint option can be used to turn off started tasks in the CA Hyper-Buf intercept process. This is written as a documentation update so you can add this to your CA Hyper-Buf User Guide.

Default: TASKS=ALL

Restriction: This constraint is accepted at any level, but should only be specified in the system default section.  If specified at any other level, the last entry encountered will override all previous entries, which may produce unexpected results.  The TASKS keyword is used to restrict what tasks types get analyzed by BrightStor CA-Hyper-Buf. The normal setting, TASKS=ALL, allows the constraint parameters to be applied to every job and started task on the system in which BrightStor CA-Hyper-Buf is active. TASKS=ALL is the default.

Specifications:       TASKS=ALL

                              TASKS=NOSTC

3.2.??.1 TASKS=NOSTC

This specification forces BrightStor CA-Hyper-Buf to exclude all started tasks and TSO sessions, analyzing and applying constraint parameter entries only to batch jobs.

3.2.??.2 TASKS=ALL

This specification allows BrightStor CA-Hyper-Buf to run in the normal mode.

Every task type (JOB and STC) will have the constraint parameters applied to it, looking for matches or exclusions as the parameters may dictate.