S322 Abend While Executing SARGRW Utility.

Products

• OM View

Issue/Introduction

When using Job Control Record fields in the SARGRW utility, the job consumes significantly more CPU time compared to using only Report Control Record fields. This high CPU utilization can lead to S322 abends due to exceeding the allotted CPU time.

Environment

• Product: View

• Version: 14.0

Cause

This behavior is expected when selection criteria include both:

• A Job Control Record field (for example, JOBOWNER), and

• A Report Control Record field (for example, ARCHDATE).

In this scenario, the SARGRW utility processes data as follows:

• It selects qualified Job Control Records first.

• For each selected Job Control Record, it then checks every associated DD.

• It attempts to find a matching Report Control Record for each DD.

This process results in a nested search operation, which can be extremely inefficient and CPU-intensive, especially when large volumes of data are involved. As a result, execution time increases significantly, making S322 abends more likely.

Resolution

Use only Report Control Record fields in the selection criteria whenever possible.

All information available in the Job Control Record is also stored in the Report Control Record. Therefore, selecting based solely on Report Control Record fields provides the same functional results with much better performance and lower CPU usage.

 

 

 

Additional Information

• There is almost no practical need to use Job Control Record fields in SARGRW selection criteria.

• The primary reason Job Control Record fields are supported is to provide users with an option to produce SARGRW output that resembles the online JOB mode view.

• For batch processing and performance-sensitive jobs, always prefer Report Control Record fields to avoid excessive CPU usage and potential S322 abends.