Validation of JES2 track group map
On an all-member warm start, you can use the SPOOL=VALIDATE start
option to request that JES2 validate the track group map. This is
typically not needed unless you receive indications from JES2 such
as the following:
- Persistent JES2 disastrous errors ($HASP095, error code $DIS)
- LOGREC symptoms records (SYMRECs) that point to track group allocation
or purge problems.
Not all SYMRECs warrant your use of SPOOL=VALIDATE. Some of the symptom records are considered informational only. See z/OS JES2 Diagnosis for a list of the SYMRECs and an indication of their severity.
Immediate spool validation can then be useful as an immediate validation of the track group map in place of the ongoing track group validation cycle wherein all track groups are validated once every 7 days.
If JES2 rebuilds the job queues, JES2 forces track group validation on the next all-member warm start. If that rebuild occurs during an all-member warm start, the track group validation occurs during that warm start; it does not wait until the next all-member warm start.