Using generic and specific definitions

BMC recommends that generic job definitions (and corresponding generic CMEM rules to force these jobs definitions) be created with all the common processing logic for all jobs which must be monitored from Control-M/EM. Whenever unique definitions for specific jobs or groups of jobs which require different processing logic are needed, they should be created physically above the generic definition.

For example, suppose all production jobs (PRD*) must shout an error message to Control-M/EM alerts monitor when they end NOTOK, but different processing logic is needed for the following jobs:

• Job PRDCICS - sends a job failure e-mail message to service@bmc.com, and the shout message should be sent not only to the Control-M/EM alerts window but also to the z/OS operator console as an unrollable message.
• Job PRDBCKUP - must be automatically rerun (a maximum of 3 times) in case the job ends NOTOK.
• Job PRDDB2 - Should be considered to end OK even if any of its steps abends with user abend U0666. No shout messages are needed in case the job fails.

The following definitions are required:

• A generic CMEM rule to capture all production jobs.

  

• Table PRODJOBS, to include all jobs definitions

  

One generic job definition - PRD* to describe the default processing logic of on spool jobs, and three more job definitions for the jobs that required special processing logic.

The following are the 4 jobs definitions:

• PRD* – job scheduling definition

  

  • The generic definition contains a MEMNAME PRD*, and is placed as the last definition in the table.
  • When ended NOTOK, the shout message is routed to U-ECS, i.e., the Control-M/EM Alerts Window and the Control-M log.
  • The shout message contains the special AUTOEDIT variable %%JOBNAME, which is replaced with the full job name before the shout is executed.
• PRDCICS - job scheduling definition

  

  

  Note:

  • If any of the job steps (ANYSTEP), complete with completion code higher than 4, than the job end status is set to ENDED-NOTOK (DO NOTOK).
  • An e-mail message (DO MAIL) is sent to address SERVICE@BMC.COM in case the job ends NOTOK.
  • When ended NOTOK the shout message is routed to OPER2, meaning that the message will be routed to the Control-M/EM Alerts Window, Control-M log and to the z/OS CONSOLE as an unrollable message.
• PRDBCKUP - job scheduling definition

  

  Note:

  • If any of the job steps (ANYSTEP) complete with completion code higher than 0, than the job will be automatically scheduled for rerun (DO RERUN).
  • Maximum rerun number is set to 3 times (MAXRERUN 003).
• PRDDB2 - job scheduling definition

  

  If any of the job steps (ANYSTEP) complete with user ABEND code U0666, consider the job as ended OK (DO OK).