Logic of the SMART Table Entity Scheduling Definition

The following points about the logic of your SMART Table Entity should be noted:

• The SMART Table Entity is used to help determine and control the processing of the jobs in the table.
  • You defined the following three sets of Basic Scheduling Criteria:
  • EOW criteria result in jobs being scheduled on the last day of the of week.
  • EOM criteria result in jobs being scheduled on the last day of the month.
  • EXERCISES criteria result in jobs being scheduled every day, for purposes of the exercises in this guide.

  You will soon see how these sets of scheduling criteria apply to the job scheduling definitions in this table.

• You defined an IN condition: IDJOB1-ENDED-OK. This condition is set when job IDJOB1 in table IDGS1 ends successfully. This means that successful completion of IDJOB1 is a prerequisite to the submission of the jobs in table IDGS2 that are scheduled according to Basic scheduling criteria in the SMART Table Entity.
• You defined an OUT condition that is set only when all scheduled jobs in table IDGS2 end OK. This condition can be used as an IN condition to some other job that requires successful completion of the jobs in table IDGS2 as a prerequisite.
• You defined two sets of ON TABLE-END/DO parameters:
  • The first set applies if all the scheduled jobs in the table end OK. It shouts a message to that effect,
  • The second set applies if any of the scheduled jobs in the table ends NOTOK. It shouts a message to that effect; and it sets an appropriate condition that can, for example, be used to run an auxiliary job.

You are about to exit the SMART Table Entity and create the job scheduling definitions in table IDGS2. However, before doing so, outline the logic you would like to see in the job scheduling definitions.