ICE267I ZSORT ACCELERATOR PATH {SELECTED | NOT USED} RSN = nnn

Explanation

For this run, SELECTED | NOT USED indicates if the new ZSORT accelerator path is selected or not used. RSN is the reason code associated with the information.

For SELECTED and RSN=0, this indicates ZSORT accelerator path is selected.

For SELECTED and RSN not equal to 0 indicates an error was encountered.

For NOT USED and RSN=nnn, the following are reason codes that explain why the IBM Integrated Accelerator for Z Sort was not used.

193

The job is NOT running on a z15 and higher processor.

The job in question is running on a machine which does not have the IBM Integrated Accelerator for Z Sort available.

194

ZSORT path is not activated.

DFSORT exploitation of IBM Integrated Accelerator for Z Sort is shipped as disabled by default. It can be enabled with ICEPRMxx members of concatenated PARMLIB, with the ICEMAC macro, or with the OPTION control statement ZSORT option.

195

SORT FIELDS=COPY or OPTION COPY is specified.

The job is requesting a COPY operation and does not support the IBM Integrated Accelerator for Z Sort.

196

MERGE FIELDS= is specified.

The job is requesting a MERGE operation and does not support the IBM Integrated Accelerator for Z Sort.

197

INREC is specified and is not supported with the use of the IBM Integrated Accelerator for Z Sort

198

OUTREC is specified and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

199

OUTFIL is specified and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

200

DFSORT was invoked via a program and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

201

Obtaining the required amount of memory object storage failed which is required for using the IBM Integrated Accelerator for Z Sort.

Memory object size and limits can be affected by the following:

• REGION and MEMLIMIT parameters on the JOB or EXEC JCL statement:

  If REGION is set equal to a value other than 0M and MEMLIMIT is not specified, the default MEMLIMIT value defined in the SMFPRMxx member of PARMLIB is used. It is recommended jobs requesting ZSORT specify a REGION=0M.

• An IEFUSI Exit can limit the total amount of virtual storage above the bar available to any address space.
• MOSIZE run time option or DFSORT Installation options.

  MOSIZE/EXPOLD/EXPRES/EXPMAX can limit the size of the memory objects obtained by DFSORT. It is recommended to use MOSIZE=MAX for ZSORT and not further control with EXPOLD/EXPRES/EXPMAX limits.

• Physical resources: Ensure the system is configured with adequate real and auxiliary storage to back any increased virtual storage demands.

209

Minimum memory requirements are NOT met to exploit the Z Sort accelerator.

The amount of memory required to sort the input exceeded the amount of memory DFSORT was able to obtain.

210

DFSORT was unable to obtain sufficient memory object storage or MOSIZE=0 was specified.

To use the IBM Integrated Accelerator for Z Sort DFSORT must be able to obtain enough memory object storage.

211

Unsupported sort fields (UTFxx Formats, LOCALE, ALTSEQ).

IBM Integrated Accelerator for Z Sort is aimed at improving performance. Using formats that require conversion before sorting may degrade the performance.

Using such formats will disable the use of the IBM Integrated Accelerator for Z Sort.

212

SUM FIELDS is specified and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

213

JOINKEYS Maintask, Subtask1 or Subtask2 execution is specified and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

214

MODS Statement is specified (User Exits are in use) and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

215

Unknown file size or FILSZ=0 and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

If DFSORT does not have an accurate file size to be sorted, then IBM Integrated Accelerator for Z is not used.

216

When sorting variable length records (VLR), the input LRECL must be greater than 24 bytes.

217

The input/output data set is a VSAM cluster and is not supported with the use of IBM Integrated Accelerator for Z Sort.

226

DFSORT determined EXCP access method was to be used for SORTIN or SORTOUT data set which is not supported with the use of the IBM Integrated Accelerator for Z Sort.

The exploitation of IBM Integrated Accelerator for Z Sort requires the use of BSAM.

227

DFSORT was unable to obtain sufficient amount of below-the-bar storage.

Specifying SIZE/MAINSIZE=MAX may allow the job to obtain enough below-the-bar storage that will allow the use of the IBM Integrated Accelerator for Z Sort.

228

The SORT Control Field key position is beyond 4092 bytes for variable records and VLSHRT was specified.

229

The total length of the key is greater than 4080 or 4088.

DFSORT's exploitation of IBM Integrated Accelerator for Z Sort has the following limits on the total length of the control fields:

• With EQUALS in effect the total length of control fields is 4080
• With NOEQUALS in effect the total length of control fields is 4088.

Note: DFSORT no longer restricts sorting up to 4,294,967,295 records with EQUALS when using IBM Integrated Accelerator for Z Sort.

230

A condition exists in key processing that prevents DFSORT using the IBM Integrated Accelerator for Z Sort.

231

File size is approximately 32MB or smaller and is not supported with the use of the IBM Integrated Accelerator for Z Sort.

232

zHPF is either disabled on the system or the disk sortwork data sets reside on non zHPF capable DASD volumes.

Ensure zHPF is available on the system and ensure sortwork data sets are created on devices that support zHPF. The necessary amount of memory object was not available that would have allowed the sort job to be processed entirely in memory.

233

SIZE/FILSZ=Uxxxxxx was requested which prevents DFSORT from using the IBM Integrated Accelerator for Z Sort.

240

DFSORT was unable to obtain 1.5 times the input file size, or an amount that is greater than 1.5 times the input file size, as memory object storage.

Memory object size and limits can be affected by the following:

• REGION and MEMLIMIT parameters on the JOB or EXEC JCL statement:

  An IEFUSI Exit can limit the total amount of virtual storage above the bar available to any address space.

• MOSIZE runtime option or DFSORT Installation options.

  MOSIZE/EXPOLD/EXPRES/EXPMAX can limit the size of the memory objects obtained by DFSORT. It is recommended to use MOSIZE=MAX for ZSORT and not further control with EXPOLD/EXPRES/EXPMAX limits.

• Physical resources: Ensure the system is configured with adequate real and auxiliary storage to back any increased virtual storage demands.

241

DFSORT was unable to obtain enough amount of disk sort work space.

For JCL defined sortworks using SORTWKxx DD statements, the amount of space specified in the SPACE parameters was not enough. Increasing the space that amounts to the input size or using dynamically allocated sort works data sets are options to overcome this reason.