552 Getting Started with IBM Tivoli Workload Scheduler V8.3
Notifications from the TWSMD_JNS2 schedule; see “TWSMD_JNS2
schedule” on page 573.
Notifications from the TWSMD_JNS3-01 schedule; see
“TWSMD_JNS3-01 schedule” on page 575
10.Request the Tivoli Workload Scheduler infrastructure team to verify that the
expected regression test notifications are generated when the FINAL job
stream runs the next morning.
11.Request the Tivoli Workload Scheduler infrastructure team to remove the
TWSM1_111D job from the TWSMD_JNS2 job stream after Tivoli Workload
Scheduler production control verifies that they have received a notification for
the job ending in an internal status of FAIL. If this is not done, then the Tivoli
Workload Scheduler production control team will receive this notification each
morning after the FINAL job stream runs.
Deploying directory structure
This section describes the directory structure used by the Tivoli Workload
Scheduler Notification Solution (the <TWShome> directory is included here
because it is the staging area for the solution deployment tar file). With the
exception of the <TWShome> directory, the permissions of each of the
directories described in the following sections must be
750 so that scripts in the
directories can be run by user IDs other than <TWSuser>.
<TWShome>/tws_jns.tar
This is the tar file used to deploy the solution. Each time a script, schedule,
default solution file (such as the default comma-separated value (CSV) for each
Tivoli Workload Scheduler master domain manager or backup master domain
manager) is updated, you have to rebuild and stage this file here. To rebuild this
tar file:
1. Log on to the master domain manager or backup master domain manager
that contains your new
golden copy of the solution scripts and files using the
<TWSuser> user ID.
2. Run the following command:
tar -cvf tws_jns.tar JNS/csv JNS/scripts JNS/tws_defs
<TWShome>/JNS/csv
This directory contains the default configuration CSV file.
Note: The logs and monitors directories are not included in the tws_jns.tar
file because they have only runtime content.
Appendix A. Tivoli Workload Scheduler Job Notification Solution 553
<TWShome>/JNS/scripts
This directory contains the scripts that IBM supports, uses, or supports and uses,
for notification, and so on. The official contents of this directory when the solution
was delivered are discussed in the following sections.
chk4_tws_event_mon_csv.ksh
This script is used by the TWSM1_CHK4_CSV job to call the
JNS/scripts/notify_tws_production_control.ksh script if a
JNS/csv/tws_event_mon.csv file is not present.
sigterm.ksh
This script is used by the TWSM1_JRL_SIGTERM job to send a SIGTERM to
the JNS/scripts/tws_jrl_mon.pl script instance that is running using the
TWSM1_JRL_MON job. This happens a minute before the FINAL job stream is
started and results in the TWSM1_JRL_MON job successfully completing before
FINAL starts.
test_notification.ksh
This script is used to send out notifications for Regression Testing, as described
in “Solution regression testing” on page 572.
job_cancels_self.ksh
This script is used by the jobs TWSM1_107 and TWSM1_JRLC to cancel
themselves so that CANCEL (107) events are generated for regression testing
purposes. This script must be run by the <TWSuser> user ID because it runs a
conman cj command.
notify_by_app.pl
This notification script parses the three-character application ID from the job
name in the event message passed into the script. If the script is able to parse an
application ID, it attempts to run a script called
JNS/scripts/notify_<application_id>.ksh, passing the event message (and other
text passed into notify_by_app.pl).
notify_by_jobname.ksh
This example script shows one way to generate notifications based on job names
in event messages.
notify_tws_infrastructure.ksh
This script must be updated to page, e-mail, or page and e-mail the Tivoli
Workload Scheduler infrastructure team and pass the script arguments as text to
the notification method.
554 Getting Started with IBM Tivoli Workload Scheduler V8.3
notify_tws_production_control.ksh
This script generates notifications to the Tivoli Workload Scheduler production
control team, sending the parameters passed into the script as the notification text.
<TWShome>/JNS/tws_defs
This directory is used as a convenient storage place for the Tivoli Workload
Scheduler schedule and job definitions for the Tivoli Workload Scheduler
Notification Solution.
<TWShome>/JNS/logs
This directory contains the log files generated by the tws_event_mon.pl and
tws_jrl_mon.pl scripts each time they are started.
<TWShome>/JNS/monitors
This directory is the place that JRL files are created. These files have the format
listed in Table A-2.
JRL=200605300712-M83#TWSMD_JNS2.0AAAAAAAAAAAAAY4.TWSM1_JRL-37302
Table A-2 Format of the JRL files
Note: Scripts clean up their own logs each time they are started.
JRL= # File prefix
200605300712 # Date and time that the job is
running long
- # Separator
M83#TWSMD_JNS2.
0AAAAAAAAAAAAAY4.TWSM1_JRL
# Fully qualified job name
- # Separator
37302 # Jobman process ID, also known as
Job
Number in the Job Scheduling Console
(JSC)
# The file contains the command to be run when the job is running long

Get Getting Started with IBM Tivoli Workload Scheduler V8.3 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.