Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2

Control cards can take advantage of the use of wild cards in the definition of the jobname and /or 
jobstepname. Wildcards are defined with the use of an asterisk as part of the jobname or jobstepname 
and work with all logical operations as shown in the following examples:

Whenever a control card is added, deleted or changed, you must stop and then restart the agent before 
the changes take effect.

The following table provides examples of control cards using procstepnames when evaluating condition 
codes. Wild cards can also be used with procstepnames.

SETCC2.STEP1<>8

Any return code less than 8 or greater than 8 from job SETCC2, job step 
STEP1 is ignored (considered normal). Only condition code 8 would be 
considered abnormal.

SETCC4.STEP2<=12

Any return code less than or equal to 12 from job SETCC4, job step STEP2 
is ignored (considered normal). Any condition code above 12 would be 
abnormal.

SETCC4.STEP3>=16

Any return code greater than or equal to 16 from job SETCC4, job step 
STEP3 is ignored (considered normal). Any condition code lower than 16 
would be abnormal.

SETCC4.STEP4<20

Any return code less than 20 from job SETCC4, job step STEP4 is ignored 
(considered normal). Any condition code 20 or above would be abnormal.

SETCC4.STEP5>24

Any return code greater than 24 from job SETCC4, job step STEP5 is 
ignored (considered normal). Any condition code less than 24 would be 
abnormal.

SET*.STEP1=4

Any return code equal to 4 from a job whose jobname begins with “SET” and 
contains the job step of “STEP1” is ignored (considered normal).

SETCC6.ST*<=12

Any return code less than or equal to 12 from job SETCC6 with a job step that 
begins with “ST” is ignored (considered normal) Any condition code above 12 
would be invalid.

SETCC*.ST*>4

Any return greater than 4 from a job whose jobname begins with “SETCC” with 
a job step that begins with “ST” is ignored (considered normal).