668 IBM Tivoli Workload Scheduler for z/OS Best Practices
Tivoli Workload Scheduler for z/OS V8.2 PTFs
Tivoli Workload Scheduler V8.2 has had multiple fixes over the past year. The list
of the problems and the resolutions, along with the PTF numbers, includes:
In a end-to-end environment, a job is defined with a scriptlib member
containing errors, the daily planning batch job sets the status of that job in fail
status in the Symphony file. Messages explaining the error can be found in
the Daily Planning log. Also in the current plan, if a job is dynamically added
and the associated script member contains errors, the job is not added.
Messages explaining the problem can then be found in the log of the
Controller. This causes problems in creating or executing the daily plan and
can cause business problems.
– PQ99317 resolves this problem by first having a Trial plan created before
running the current plan, so that it reveals errors in the SCRPTLIB
members. Error messages are issued in the EQQDTTOP mlog, in order to
take the correct actions to avoid problems when the daily plan is created.
– The EQQSLCHK sample JCL provides a syntactic check of all script
library members. This sample will run stand-alone, without the need to
interact with the CP database. It can also be run against all script
members in the SCRPTLIB or can be used to perform a check against
only a subset of these script members.
Currently, when a server started task abends in the C/C++ code, a CEEDUMP
(Language Environment® Dump) of the original abend and a SYSMDUMP
with completion code U4039 are taken. The CEEDUMP contains partial data
related to the address space and is not enough for a complete error analysis.
The SYSMDUMP sometimes is not related to the original abend. So there
must be a dump of the original abend as a SYSMDUMP.
– In PTF PK01415 the SYSMDUMP of the original abend is now collected
containing also the LEDATA and CEEDUMP information.
Lack of problem determination information and messages during the daily
– In PTF PK01415 the new trace and log messages have been added to
analyze errors occurred during the daily planning phase.
Lack of problem determination information when a file corruption occurs.
– In PTF PK01415 to intercept errors corrupting or locking the event files, we
have traced open and write calls on them. In this way it will be easier to
understand the origin of the corruption. This trace will write the messages
in memory in order to avoid filling log files and possible performance
reductions. If an error occurs while accessing an event file a dump is taken
for problem determination purposes; the memory traceinfo will be available
in the dump.