Rules Structure

The following tables describe the structures of the Test Job Failures–Option 1 solution rules:

Table 107 Test Job Abended—Option 1 Rule Structure

Item	Description
Title	Test Job Abended – Option 1
Name	IEF450I
Table	TESTJOB1
Message	IEF450I jjj {ppp} sss - ABEND {Scde \| Ucde} REASON=xxxxxxxx TIME=hh.mm.ss
Message Description	Job jjj terminated abnormally.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	If a test job abends, this rule notifies the job owner immediately. The rule is triggered if the job that issued the message is named according to certain test job naming conventions. The rule assumes that the TSO user ID of job owner is the prefix of the job name. (For more details concerning rule assumptions, see Customization in this table.)
Rule Actions	Sets variable %%UNAME to the prefix of the job name. Sends a message notifying TSO user %%UNAME of the abend.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 3—the rule is provided as an example. Some customization is needed if the rule is to be implemented.
Customization	The rule makes several assumptions regarding test job naming conventions. These assumptions must be adapted to site conventions: Test jobs are assumed to be prefixed T. Adapt the JNAME field in the rule’s ON statement to site conventions. The rule is triggered only for jobs matching the JNAME field specification. The TSO user ID of the job owner is assumed to be the first four characters of the job name. Adapt the rule actions (setting variable %%UNAME) to site conventions. Table 108 Test Job Not Run—JCL Error—Option 1 Rule Structure*
Item	Description
Title	Test Job Abended—Option 1
Name	IEF4521
Table	TESTJOB1
Message	Either of the following messages: IEF452I jjj JOB NOT RUN - JCL ERROR IEF453I jjj JOB NOT RUN - JCL ERROR
Message Description	Job jjj failed due to a JCL error.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	If a test job fails as a result of a JCL syntax error, this rule notifies the job owner immediately. The rule is triggered if the job that issued the message is named according to certain test job naming conventions. The rule assumes that the TSO user ID of job owner is the prefix of the job name. (For more details concerning rule assumptions, see Customization in this table.)
Rule Actions	Sets variable %%UNAME to the prefix of the job name. Sends a message notifying TSO user %%UNAME of the JCL error.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 3—the rule is provided as an example. Some customization is needed if the rule is to be implemented.
Customization	The rule makes several assumptions regarding test job naming conventions. These assumptions must be adapted to site conventions: Test jobs are assumed to be prefixed T*. Adapt the JNAME field in the rule’s ON statements to site conventions. The rule is triggered only for jobs matching the JNAME field specifications. The TSO user ID of the job owner is assumed to be the first four characters of the job name. Adapt the rule actions (setting variable %%UNAME) to site conventions.

Parent Topic

Test Job Failures–Option 1