Examples for SHOUT

SHOUT Example 1

If the job finishes executing OK, write a message to the IOA Log file under the specified user ID:

MEMNAME  GPLSP0007

DAYS     01,15

SHOUT WHEN OK TO U-SHIFTMNGR URGN  R

  MS      I HAVE FINISHED FOR TONIGHT

The message is written to the log under Control-M userid-SHIFTMNGR.

SHOUT Example 2

When IMS is not active, send a message to all operators.

Figure 310 SHOUT Parameter Example 2

JOB: IMSPROD  LIB CTM.PROD.SCHEDULE                          TABLE: IMSPROD

COMMAND ===>                                                SCROLL===> CRSR

+-------------------------------------------------------------------------+

  =========================================================================

  OUT                                                                      

  AUTO-ARCHIVE Y          SYSDB    Y      MAXDAYS      MAXRUNS             

  RETENTION:  # OF DAYS TO KEEP 030  # OF GENERATIONS TO KEEP              

  SYSOUT OP   (C,D,F,N,R)                                             FROM

  MAXRERUN     RERUNMEM                             INTERVAL       FROM    

  STEP RANGE         FR (PGM.PROC)          .          TO         .        

  ON PGMST          PROCST          CODES                              A/O

    DO                                                                     

  SHOUT WHEN OK        TIME       +     DAYS     TO OPER2          URGN R  

    MS *******  IMS IS NOT ACTIVE  *******                        

  SHOUT WHEN NOTOK     TIME       +     DAYS     TO OPER2          URGN R  

    MS *******  IMS IS NOT ACTIVE - ENDED ABNORMALLY  *******      

  SHOUT WHEN           TIME       +     DAYS     TO                 URGN   

    MS                                                                     

====== >>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<< =====

COMMANDS: EDIT, DOC, PLAN, JOBSTAT                                11.17.00

If IMS finishes executing, an unrollable message is sent to the operator. A different message is sent if IMS terminates abnormally.

SHOUT Example 3

If the job is not run because of a JCL error, notify the user who sent the job.

Figure 311 SHOUT and DO SHOUT Example

JOB: SACALC01 LIB CTM.PROD.SCHEDULE                           TABLE: SALARY

COMMAND ===>                                                SCROLL===> CRSR

+-------------------------------------------------------------------------+

  =========================================================================

  OUT                                                                      

  AUTO-ARCHIVE Y          SYSDB    Y      MAXDAYS      MAXRUNS             

  RETENTION:  # OF DAYS TO KEEP 030  # OF GENERATIONS TO KEEP              

  SYSOUT OP   (C,D,F,N,R)                                             FROM

  MAXRERUN     RERUNMEM                              INTERVAL      FROM    

  STEP RANGE         FR (PGM.PROC)          .          TO         .        

  ON PGMST ANYSTEP  PROCST          CODES JNRUN                        A/O

   DO SHOUT     TO  TSO-U0014          URGENCY U                  

     = *** JCL ERROR IN SALARY JOB ***                            

    DO                                                                     

  ON PGMST          PROCST          CODES                              A/O

    DO                                                                     

  SHOUT WHEN           TIME       +     DAYS     TO                 URGN   

    MS                                                                     

====== >>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<< ======

COMMANDS: EDIT, DOC, PLAN, JOBSTAT                                11.17.00

An urgent message is sent to the user ID that requested the job.

SHOUT Example 4

Perform a LATE shout after the New Day time has passed and a new working day has begun.

Assume the following:

• New Day time at the site is 0600.
• A job, LONGWAIT, is ordered at 1400.
• The job LONGWAIT must shout if it has not finished executing by 0700 on the following day.

However, the New Day process automatically cancels any shout requirements of jobs ordered on any previous day.

There are two ways to achieve the required LATE shout:

Method 1

1. Create a DUMMY job scheduling definition named TRIGGER, containing the following elements:
   • The TIME FROM parameter is set to 1400.
   • The OUT parameter is set to TRIGGER-SHOUT.
2. Create a DUMMY job scheduling definition named SHOUT. This job must be ordered at the New Day time, and must contain the following elements:
   • The TIME FROM parameter is set to 0700.
   • The TIME UNTIL parameter is set to 1300.
   • The MAXWAIT parameter is set to 02.
   • The IN parameter is set to TRIGGER-SHOUT.
   • The SHOUT parameter is set to WHEN LATESUB 0700.
3. Add to the LONGWAIT JOB an OUT condition, TRIGGER-SHOUT, that deletes the TRIGGER-SHOUT condition when it ends.

   This procedure works as follows:

   • The IN condition in the SHOUT job prevents it from executing between 0600 and 1359.
   • At 1400 the TRIGGER job adds the IN condition.
   • The TIME FROM and UNTIL parameter values prevent the SHOUT job from running until after the next New Day procedure, but the MAXWAIT parameter value ensures that the job remains on the Active Jobs file for the following day.
   • At 0700 on the following day
     • if the LONGWAIT job has ended, it has removed the IN condition required before the SHOUT job can run, so that there is no false shout at 0700
     • if the LONGWAIT job has not ended, the SHOUT job runs, and the shout is produced as required

Method 2

Use IOA Exit 34, and set values for the SET VAR parameter in the job scheduling definition.

For more information, see the IOAX034H sample exit in the IOA SAMPEXIT library.