How to make sure that events are not lost
About this task
Use one of these methods to ensure that events are not missed between
the time IBM® Z Workload Scheduler is
taken down and JES (JES2 commands are given in the
example) is taken down:
- Method 1
-
- Remove the system being stopped from the JES2 MAS by
placing it into independent mode (issue
$T MEMB(n),IND=Y, wherenis the member number of the LPAR obtained from the$DMEMBERcommand output). - Allow the jobs currently running on this system to complete.
- Stop
the tracker (
P OPCx). - Stop JES.
- Re-IPL.
- Restart JES.
- Restart the tracker.
- Resume
normal work by issuing
$T MEMB(n),IND=N, wherenis the member number of the LPAR obtained from the$DMEMBERcommand output.
- Remove the system being stopped from the JES2 MAS by
placing it into independent mode (issue
- Method 2
-
- Abend JES2 (
$PJES2,ABEND). - Stop the
tracker (
P OPCx). - Re-IPL.
- Restart JES. This will be a hot start.
- Restart the tracker.
- Abend JES2 (
- Method 3
-
- Take the tracker down (
P OPCx). - Bring
it up again under the master scheduler (
S OPCx,SUB=MSTR). Remember that a tracker cannot use JES services (SYSOUT data sets, JCC) if it runs under the master scheduler. - Bring down JES.
- Take the tracker down (
P OPCx).
- Take the tracker down (