Syncsort PROCSort Messages - procsort - 2.4

All messages issued by Syncsort PROCSort have the form:

 WERnnnx Message text

where nnn is the message number and x may be the letter A or I. The interpretation of the suffix letter, x, is given below.

A (action) message indicates a critical error condition: Syncsort PROCSort terminates in order to allow the user to correct the error(s) so that a successful sort may be run.

Example WER765A DYNALLOC ERROR OCCURRED: RC=n.

I (informational) messages document decisions internal to the sort as well as the Syncsort PROCSort response to error conditions that are not severe enough to warrant sort termination.

Examples WER749I NO OBSERVATIONS TO BE SORTED

 The following messages may be issued by Syncsort PROCSort:

WER700A

PROC SYNCSORT UNSUPPORTED FUNCTION. RETRY|NORETRY IN EFFECT.

EXPLANATION: The Syncsort MFX high-performance technique could not be used during this invocation by Syncsort PROCSort. This may be due to a small region size or the generation of an unsupported Syncsort MFX statement syntax. If the RETRY option of Syncsort PROCSort is in effect, Syncsort MFX will be reinvoked using a less efficient E15-E35 interface. If the RETRY option is not in effect, the Syncsort PROCSort execution will be terminated.

WER712A

NO MORE SPACE COULD BE OBTAINED ON THE OUTPUT FILE.

EXPLANATION: Additional space was required to contain the sorted output but none could be allocated in the output data set. The data set may have reached its limit of 16 extents, or there may be no more space on the DASD volume.

ACTION: Increase primary or secondary space allocation for the data set, or free up some space on the DASD volume.

WER720I

PROCESSING ERROR DETECTED. ATTEMPTING TO RECOVER.

EXPLANATION: The Syncsort PROCSort ESTAE recovery routine has been invoked as a result of an error condition either in Syncsort PROCSort or in Syncsort MFX. An attempt is being made to recover from the error and complete the sort.

ACTION: Subsequent messages will indicate the success or failure of the recovery process. The Syncsort PROCSort DEBUG facility is automatically enabled and will print relevant information about the error and subsequent processing.

WER721A

RECOVERY UNSUCCESSFUL. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: The Syncsort PROCSort attempt to recover from an error condition has failed. The sort will be terminated.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER722I

RECOVERY SUCCESSFUL. PROCESSING CONTINUES.

EXPLANATION: The Syncsort PROCSort attempt to recover from an error condition was successful. The sort continues processing.

ACTION: The recovery was successful. However, the initial problem needs to be detected and corrected. Contact Precisely Support or call your Syncsort support representative.

WER723A

PROCESSING ERROR DETECTED. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: The Syncsort PROCSort ESTAE recovery routine has been invoked as a result of an error condition either in Syncsort PROCSort or in Syncsort MFX. Adverse conditions prohibit a recovery attempt. The sort has terminated. The Syncsort PROCSort DEBUG facility has been automatically enabled and will print relevant information about the error.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER724A

INSUFFICIENT STORAGE FOR INITIALIZATION. CALL YOUR SYNC­SORT REPRESENTATIVE.

EXPLANATION: Syncsort PROCSort could not obtain sufficient main storage above the 16M line for data areas necessary for its initialization.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER725A

INSUFFICIENT STORAGE TO BUILD SORT CONTROL STATEMENTS. RAISE REGION.

EXPLANATION: Syncsort PROCSort could not obtain sufficient virtual storage to build the SORT control statements.

ACTION: Increase the region size.

WER727A

SORT CONTROL STATEMENTS GENERATION ERROR: RC=n. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: An error occurred while generating MFX control statements.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER728A

KEY STATEMENT CANNOT BE USED PRIOR TO SAS 9.2.

EXPLANATION: The KEY statement was introduced in SAS Version 9.2 and is not supported prior to that.

ACTION: Use the BY statement instead.

WER729A

A KEY STATEMENT MAY NOT BE SPECIFIED WITH A BY STATE­MENT.

EXPLANATION: The KEY statement and the BY statement cannot be used together.

ACTION: Specify either the BY statement or the KEY statement.

WER729I

DEGRADED PROC SORT PERFORMANCE; THE PROC MFX PRODUCT HAS BEEN INSTALLED TO USE SAS 9.3, BUT AN EARLIER VER­SION OF SAS IS IN USE.

EXPLANATION: Syncsort PROCSort encountered a SAS library at a level below 9.3. The SORT high performance path cannot be used in this SAS environment.

ACTION: Follow the instructions in the Syncsort PROCSort Installation and Use Guide to make your Syncsort PROCSort library accessible to SAS 9.3.

WER739A

NO statement name FIELDS SPECIFIED.

EXPLANATION: No variable names were listed on the indicated statement.

ACTION: Specify at least one variable name on the statement.

WER740A

OPTIONS option name 1 AND option name 2 CONFLICT.

EXPLANATION: The options specified are mutually exclusive.

ACTION: Review the options and respecify appropriately.

WER744A

CONFLICT BETWEEN SYNCSORT AND PROC SYNCSORT MAINTENANCE LEVELS, VERIFY LIBRARIES.

EXPLANATION: Maintenance has been applied to either Syncsort PROCSort or Syncsort MFX, but not to both when maintenance to both is required.

ACTION: Check the libraries containing Syncsort PROCSort and Syncsort MFX, and apply the required level of maintenance to each.

WER746I

PROC SYNCSORT sort-technique-name SORT SELECTED.

EXPLANATION: Informational message. Syncsort PROCSort selected the indicated sort technique for performing the sort.

WER747A

UNSUCCESSFUL SORT - reason.

EXPLANATION: Syncsort MFX has terminated unsuccessfully. This may be due to insufficient SORTWK space, insufficient main memory, or other causes.

ACTION: Inspect the sort messages generated by Syncsort MFX to the SYSOUT data set and take appropriate corrective action.

WER747I

UNSUCCESSFUL SORT - ATTEMPTING TO PERFORM SORT AGAIN.

EXPLANATION: The Syncsort MFX high-performance technique could not be used. The sort request will be “retried” using a less efficient technique.

ACTION: Raising the amount of storage available for Syncsort MFX to use will normally allow the MFX high-performance technique to execute.

WER748A

ERROR DURING PARSING OF PROC SYNCSORT STATEMENT. CHECK SYNTAX.

EXPLANATION: The Syncsort PROCSort statement contains one or more errors as indicated.

ACTION: Correct error(s) and rerun job.

WER749I

NO OBSERVATIONS TO BE SORTED.

EXPLANATION: Either the DATA file contained no observations or the setting of the SAS OBS and FIRSTOBS options dictated that no observations be sorted.

ACTION: Look for and correct any errors in your SAS program prior to Syncsort PROCSort that may have caused SAS to set OBS=0.

WER750I

END PROC SYNCSORT. (RETRY SUCCESSFUL.) Rr.r m BATCH nnnn.

EXPLANATION: Informational message. Syncsort PROCSort has successfully com­pleted. If the completion was the result of a retry, this will be indicated. The current release (r.r) and maintenance level (m) of Syncsort PROCSort are also indicated. The batch number of the Syncsort PROCSort maintenance tape most recently applied is also displayed.

ACTION: If the completion was the result of a retry, raising the amount of storage available for Syncsort MFX may cause the MFX high-performance technique to execute.

WER755A

SAS routine name ERROR ENCOUNTERED. FUNCTION CODE=n,RC=m (HEX).

EXPLANATION: The SAS-provided routine indicated in the message did not complete successfully when called to perform the desired function.

ACTION: Check the corresponding message which appears on the SAS LOG data set to determine the cause of the error.

WER756A

I/O ERROR SYNADAF error message.

EXPLANATION: An I/O error occurred while processing the Syncsort PROCSort parameter data set specified by the $$PSPARM DD statement. The SYNADAF message text specifies the nature of the error.

ACTION: In most cases the text will be self-explanatory. Correct the error on this basis and resubmit the job. If the problem persists, call your Syncsort support representative.

WER757A

PROC SYNCSORT MODULE: module-name NOT FOUND IN ANY ACCESSED LIBRARY.

EXPLANATION: The indicated Syncsort PROCSort module could not be located in any of the accessed libraries.

ACTION: Check the Syncsort PROCSort library to see if it contains the specified module. If not, install the module again. Contact Precisely Support or call your Syncsort support representative.

WER758A

OPEN FAILED FOR LIBRARY: library-name. CHECK LIBRARY ACCESS.

EXPLANATION: The indicated library could not be opened by Syncsort PROCSort.

ACTION: Make sure that the library can be opened. For example, try using a file editor to browse the library.

WER759A

BLDL FAILED FOR LIBRARY: library-name. RAISE REGION OR CHECK LIBRARY ACCESS.

EXPLANATION: Syncsort PROCSort encountered a BLDL failure for the indicated library. When attempting to perform a BLDL for the library identified, an error occurred.

ACTION: The cause of the error is either insufficient virtual storage or a perma­nent I/O error on the library.

WER760A

ATTEMPT TO LOAD PROC SYNCSORT MODULE: module-name FROM LIBRARY: library-name FAILED.

EXPLANATION: The indicated Syncsort PROCSort module could not be loaded from the specified library.

ACTION: Check that the Syncsort PROCSort module attributes are set so that the module can be loaded. If not, install the module again. Contact Precisely Support or call your Syncsort support representative.

WER761A

SYNCSORT LOAD MODULE NOT FOUND. VERIFY ACCESS TO SYNC­SORT LIBRARY.

EXPLANATION: Syncsort PROCSort was unable to locate the SYNCSORT load module.

ACTION: Make sure you are accessing the library in which Syncsort MFX resides.

WER762A

INCOMPATIBLE MAINTENANCE LEVELS: SYNCSORT Rr.r TPFn PROC SYNCSORT Rr.r.

EXPLANATION: The Syncsort MFX product is not at the correct release or main­tenance level required to execute the indicated Syncsort PROCSort release.

ACTION: Make sure that you are accessing the specified release of Syncsort MFX. If necessary, install the specified release.

WER763A

INDEXED DATA SET CANNOT BE SORTED IN PLACE UNLESS THE FORCE OPTION IS USED.

EXPLANATION: The input data set has one or more indexes defined on it, and no target data set was specified for the sorted output.

ACTION: Specify the FORCE option to replace the input data set, and delete all indexes which exist for it.

WER764A

OPTIONS PROCESSING ERROR: RC=n. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: Syncsort PROCSort encountered an internal error while processing HOST SORT options.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER765A

DYNALLOC ERROR OCCURRED: RC=n.

EXPLANATION: An error occurred while attempting to dynamically allocate the data set specified for writing SORT messages.

ACTION: See either IBM publication z/OS MVS Programming: Authorized Assembler Services Guide SA22-7608 or OS/390 V2R10.0 MVS Authorized Assem­bler Service Guide GC28-1763.

WER766A

INPUT DATA SET SUBSET SPECIFIED BY USING THE FIRSTOBS OPTION, OBS OPTION, OR WHERE CLAUSE CANNOT REPLACE INPUT DATA SET UNLESS THE FORCE OPTION IS USED.

EXPLANATION: Only a subset of the input data set has been selected for sorting and no target data set was specified for the sorted output.

ACTION: If you do not want to replace the input data set with a subset, then specify an output data set. If you want to replace the input data set with a subset, you must use the FORCE option.

WER767I

INITIALIZATION PROCESSING ERROR: RC=n. ATTEMPTING RECOVERY.

EXPLANATION: Informational message. Syncsort PROCSort encountered an internal error during its initialization process and is attempting to recover from it.

WER768A

RECOVERY UNSUCCESSFUL. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: The attempt to recover from the internal error encountered during the initialization process failed.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER769I

RECOVERY SUCCESSFUL. PROCESSING CONTINUES.

EXPLANATION: Informational message. The attempt to recover from the internal error encountered during the initialization process was successful.

WER770A

INITIALIZATION PROCESSING ERROR: RC=n. CALL YOUR SYNC­SORT REPRESENTATIVE.

EXPLANATION: Syncsort PROCSort encountered an internal error during its initialization process. No attempt is made to recover from it since the DEBUG option was specified. A reason code of 802 indicates that the Syncsort PROCSort library has 8.2 support applied, but the SAS application is using a version of SAS prior to 8.2.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER771I

INPUT FILE IS ALREADY SORTED. NO SORTING DONE.

EXPLANATION: Informational message. Syncsort PROCSort has determined that the sort information stored in the input data set indicates that it is already sorted in the desired way. Since no target data set was specified for the sorted output, no sorting was performed.

WER772I

INPUT FILE IS ALREADY SORTED. IT HAS BEEN COPIED TO THE OUTPUT FILE.

EXPLANATION: Informational message. Syncsort PROCSort has determined that the sort information stored in the input data set indicates that it is already sorted in the desired way. Since a new output data set was specified, the input data set is copied to the output data set without sorting.

WER775A

SAS I/O ERROR OCCURRED. CHECK SAS MESSAGE LOG DATASET.

EXPLANATION: An I/O error occurred when a SAS routine attempted to access or update a SAS data set. A message indicating the actual nature of the problem should appear on the SAS message LOG data set.

WER776A

BLDL FAILURE FOR DDNAME SASLIB. RAISE REGION OR CHECK SASLIB ACCESS.

EXPLANATION: When attempting to perform a BLDL for the library identified by the SASLIB DD statement, an error occurred. The error is due either to insuffi­cient virtual storage or a permanent I/O error on the library.

WER777A

ERROR LOADING PROC SYNCSORT MODULE. CHECK PROC SYNCSORT INSTALL.

EXPLANATION: The Syncsort PROCSort module (SYNCRI03) could not be found in any of the libraries on the normal search chain or an error occurred while loading the module.

WER778A

UNEQUAL MAINTENANCE APPLIED TO PROC SYNCSORT AND SYNCSORT LIBRARIES. DATA=xxxxxxxxxxxx,xxxxxxxxxxxx.

EXPLANATION: The maintenance of the Syncsort PROCSort product is in conflict with the maintenance level of the Syncsort MFX product due to the incomplete application of one or more maintenance fixes. The hexadecimal data, if printed, indicates which maintenance fixes were incompletely applied.

WER780A

RESOLUTION PROCESSING ERROR: RC=n. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: There was an internal error during resolution processing.

ACTION: Contact Precisely Support or call your Syncsort support representative.

WER783A

ONLY ONE ALTERNATE SEQUENCE OPTION MAY BE SPECIFIED.

EXPLANATION: Multiple alternate collating sequences cannot be specified in a single execution of Syncsort PROCSort.

ACTION: Change the job so that no more than one alternate collating sequence is specified.

WER784A

INVALID SORTSEQ OPTION VALUE: value SPECIFIED.

EXPLANATION: The alternate collating sequence specified with the SORTSEQ= option is invalid.

ACTION: Replace with a valid sequence specification, or remove the option specification.

WER785A

ALTERNATE SEQUENCE sequence name IS NOT SUPPORTED IN THIS RELEASE OF PROC SYNCSORT.

EXPLANATION: The installed version of Syncsort PROCSort does not support the alternate collating sequence indicated.

ACTION: If PROC SORT supports this option and you get this message, call your Syncsort support representative. If the option indicated is not supported, specify a supported collating sequence.

WER786I

OPTION option name IS IGNORED BY SORT.

EXPLANATION: Informational message. The indicated option is accepted but ignored by Syncsort MFX.

WER788A

UNIQUEOUT OPTION CAN BE USED ONLY WITH NOUNIQUEKEY OR NOUNIQUEREC OPTIONS; THE DUPOUT OPTION CAN BE USED ONLY WITH NODUPKEY OR NODUPREC OPTIONS. UNIQUEOUT AND DUPOUT CANNOT BE USED AT THE SAME TIME.

EXPLANATION: The options specified are mutually exclusive.

ACTION: Correct the option specifications and rerun the job.

WER794I

OBSERVATIONS DELETED BY THE NONUNIQUE CATEGORY OF OPTIONS PROCESSING.

EXPLANATION: The number of observations deleted because of the NON­UNIQUEREC or NONUNIQUEKEY option is indicated.

WER795I

OBSERVATIONS WITH DUPLICATE KEY VALUES WERE DELETED.

EXPLANATION: The number of observations deleted because of the NODUP­KEY option is indicated.

WER796A

RECORD COUNT MISMATCH: EXPECTED=k, IN=n, OUT=m. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: Either of the following occurred:

1. The number of observations read from the input data set did not  equal the number expected to be read.
2. The number of observations written to the output data set did not  equal the number read from the input data set and no record  deletion options were specified.

WER798I

DUPLICATE OBSERVATIONS DELETED.

EXPLANATION: The number of observations deleted because of the NODUPREC option is indicated.

WER799A

UNDEFINED ERROR CODE: n. CALL YOUR SYNCSORT REPRESENTATIVE.

EXPLANATION: Syncsort PROCSort encountered an invalid error code (n) when processing messages to be written to the SAS LOG data set.

ACTION: Contact Precisely Support or call your Syncsort support representative.