Considerations for running HD Pointer Checker in multiple-step jobs
In TYPE=SCAN and TYPE=CHECK job steps, take note of the following considerations.
- Performance is lower and sizes of the work data sets are larger than a TYPE=ALL job.
- The JCL statements are more complex than in the TYPE=ALL job.
- When the scan steps, which are composed of multiple jobs, run in a ULU region, be careful when specifying independent—that is, with neither logical nor index relation—databases. For details, see the description of message FABP2104E in Messages and codes.
Because these restrictions or notices do not apply to the TYPE=ALL job, it is strongly recommend that you select the TYPE=ALL job. To do so, specify PROC TYPE=ALL in the PROCCTL statement.