DSNU397I csect-name NUMBER OF TASKS CONSTRAINED BY resource-type TO number-of-tasks
Explanation
A utility is able to start subtasks to perform operations in parallel. However, the number of tasks that it can use has been constrained by a lack of some resource.
- csect-name
- The name of the control section that issued the message.
- resource-type
- The constraining resource. resource-type can have one of the following values:
- VIRTUAL STORAGE
- Insufficient virtual storage exists in the address space in which the utility job is running.
- VIRTUAL STORAGE BELOW
- Insufficient virtual storage exists below the line in the address space in which the utility job is running.
- DD STATEMENTS
- In the JCL DD statements, fewer sort work data set groups or sort message data sets have been specified than the maximum number of tasks than the utility could otherwise start.
KEYWORDS
- Either a keyword was missing in the utility statement or a keyword was specified that prohibits
parallel processing. For dynamic allocation of sort work data sets, SORTDEVT must be specified. For
the REORG utility unload and reload parallel processing, NOSYSREC must be specified on the unload
template, and TAPESTACK is not permitted.
- CPUS
- Starting additional tasks would overtax the available CPUs.
- SWA=BELOW
- Insufficient storage exists below the line in the address space in which the job is running.
- PARALLEL N
- The PARALLEL keyword limits the number of tasks to be started.
- ZPARM PARAMDEG_UTIL
- The setting of the PARAMDEG_UTIL subsystem parameter limits the number of tasks to be started.
- number-of-tasks
- The maximum number of tasks that can be started after applying the constraint.
This value might be different than what you specified, if the constraint is less than the minimum number of tasks that are needed for the utility to complete.
System action
Processing continues.
User response
No action is required. However, if you want to increase the number of tasks that are used by the utility to reduce the elapsed time of the utility job, consider the following possible actions based on the value of resource-type:
- VIRTUAL STORAGE
- Increase the amount of virtual storage that is available to the utility job by specifying a larger region size in the job JCL, altering the JES defaults for region size, or changing the system IEFUSI exit to allow a larger virtual region. If the utility is using BSAM data sets for which the number of buffers have been specified (BUFNO specified in the DCB field of the DD statement for the data set), consider reducing the number of buffers.
- VIRTUAL STORAGE BELOW
- If possible, increase the amount of below-the-line virtual storage that is available to the utility job by specifying a larger region size in the job JCL or reducing the number of data sets that are allocated in the job step. Relieving this constraint might not be possible.
- DD STATEMENTS
- Define additional groups of sort work data sets, or eliminate the SWnnWKmm DD statements and
specify the SORTDEVT keyword (and, optionally, the SORTNUM keyword) to allow SORT to use dynamic
allocation of its work data sets.
If the limitation is due to sort message data sets rather than sort work data sets, take one of the following actions:
- Define additional sort message DD statements
- Eliminate the UTPRINnn DD statements and allocate UTPRINT to SYSOUT so that the sort message data sets can be dynamically allocated.
- KEYWORDS
- To request dynamic allocation of sort work data sets, specify SORTDEVT in the utility statement.
To request unload and reload parallel processing if no unload template is available, specify
NOSYSREC in the utility statement. For unload and reload parallel processing, do not include
TAPESTACK in the utility unload TEMPLATE statement.
- CPUS
- Submit the job to a member that has more processors.
- SWA=BELOW
- Move the SWA above the 16 MB line for the JOBCLASS. JES command, $DJOBCLASS(n), displays whether SWA is set to BELOW for CLASS n. The $TJOBCLASS(n),SWA=ABOVE command sets SWA to ABOVE the line. The $DSTCCLASS and $TSTCCLASS commands can be used to move SWA to ABOVE for the utilities that are running in a WLM Stored Procedure Environment. Consult with the MVS™ System Programmer on these changes.
Severity
0 (informational)