BEN0110 - PROCESS LOGIC ERROR...PLEASE CHECK CMDS
BEN0120 - LEASE HAS EXPIRED.....JOB CANCELED
BEN0130 - WARNING LEASE TERM HAS EXPIRED..........
BEN0140 - WARNING, CALLED PGM RTN CODE NOT = 00
BEN0141 - DB2 ERROR OCCURED, SEE REASON CODE
BEN0150 - WARNING, FIELD EDIT CAUSED OVER-FLOW
BEN0160 - REQUEST VALUE DISPLAYED
BEN0165 - TRACE REQUESTED, COMMAND ENTRY DISPLAYED
BEN0170 - CALL PARM EXCEEDS 100 LIMIT
BEN0171 - EXCEEDED 100 PERFORM LEVELS, STACK FULL
BEN0172 - EXCEEDED 100 RETURN POINTERS, STACK FULL
BEN0180 - NOT NUMERIC FIELD FOUND, PROCESS SKIPPED
BEN0181 - BINARY NUMBER EXCEEDS MAX, 2,147,483,647
BEN0182 - ADD OVERFLOWED FIELD SIZE, MAX 15 DIGITS
BEN0210 - FILE DEFINED AS BOTH INPUT AND OUTPUT
BEN0211 - MAX FILE NUMBER IS 99 PER JOB
BEN0221 - "INTO" FIELD MISSING
BEN0222 - "DELIMITED BY" FIELD MISSING
BEN0223 - DECIMAL SIZE GREATER THAN 15 PLACES
BEN0230 - LENGTH INVALID OR GREATER THAN 32760 LIMIT
BEN0231 - LENGTH OPERAND MAY NOT BE ZERO
BEN0240 - POSITION OPERAND GREATER THAN 32760 LIMIT
BEN0241 - POSITION OPERAND MAY NOT BE ZERO
BEN0242 - TYPE CODE NOT C, P, OR X
BEN0250 - FILE NAME GREATER THAN 8 CHARACTERS
BEN0255 - ONLY ONE FILE REQUEST ALLOWED
BEN0256 - FILE DDNAME DID NOT REQUEST A READ
BEN0257 - "WORKAREA" IS INPUT ONLY DEFINED
BEN0258 - ALL MASKS FOR A GIVEN FILE MUST BE EQUAL
BEN0260 - OPERAND KEYWORD OR PARENTHESIS MISSING
BEN0261 - PACKED NUMBER IS LIMITED TO 15 DIGITS
BEN0262 - HEX LITERAL MUST BE VALID AND FULL BYTES
BEN0263 - LABEL HAS NOT BEEN DEFINED
BEN0264 - LABEL WAS PREVIOUSLY DEFINED
BEN0265 - NO CONDITIONAL SYMBOL GIVEN
BEN0270 - NO COMMAND FILE FOUND
BEN0271 - "EOJ" IS A RESERVED TAG NAME
BEN0272 - "VAR" IS A RESERVED DATA LABEL
BEN0273 - "LOC" IS A RESERVED DATA LABEL
BEN0280 - COMMAND FILE EMPTY, PLEASE INPUT COMMAND
BEN0281 - PROCESS TAG HAS NOT BEEN DEFINED
BEN0282 - FILE NAME REQUIRED FOR EXPLICIT FORMAT
BEN0287 - DB2 SQL FORMAT ERROR, BUFFER OVERFLOWED
BEN0290 - COMMAND VERB NOT RECOGNIZED
BEN0291 - COMMAND TABLE LIMIT REACHED
BEN0292 - LITERAL POOL SIZE LIMIT REACHED
BEN0293 - "DEFINES" LABEL TABLE LIMIT REACHED
BEN0294 - ENTRY TABLE LIMIT REACHED, MAX 99
BEN0295 - NO ENTRY PARMS FOUND
BEN0296 - DLILINK AREA NAME NOT FOUND
BEN0310 - FILE DDNAME FAILED TO OPEN, CHECK JCL
BEN0320 - SYNC ERROR, FILE MUST BE IN ASCENDING ORDER
BEN0330 - FILE IS PDS ORGANIZATION, NOT ALLOWED
BEN0340 - FILE DIRECTORY IS FULL, MEMBER NOT SAVED
BEN0340 - MEMBER ON DIRECTORY BUT NOT ON FILE
BEN0360 - FILE HAS RECFM=U, NOT ALLOWED
BEN0370 - FILE IS A PDS, USE WRITEPDS VERB
BEN0380 - FILE IS NOT A PDS TYPE
BEN0390 - FILE RECORD LENGTH IS ZERO, NOT ALLOWED
BEN0410 - BENCHR01 DD IS MISSING, PLEASE USE STANDARD PROC
BEN0510 - BENCHR08 DDNAME IS MISSING, CHECK JCL
BEN0610 - BENCHR02 DDNAME IS MISSING, CHECK JCL
BEN0710 - BENCHR03 DDNAME IS MISSING, CHECK JCL
BEN0810 - BENCHR04 DDNAME IS MISSING, CHECK JCL
BEN0910 - BENCHR05 DDNAME IS MISSING, CHECK JCL
BEN1010 - BENCHR07 DDNAME IS MISSING, CHECK JCL
BEN1020 - SORT FAILED IN XREF REPORT R07
BEN1110 - USER DICTIONARY NOT REQUESTED, DD MISSING
BEN1120 - BENCHOBJ DDNAME IS MISSING, CHECK JCL
BEN1130 - WORD NOT FOUND IN DICTIONARY
BEN1140 - USER WORD HASHED DUPLICATE VALUE
BEN1210 - BENCHR06 DDNAME IS MISSING, CHECK JCL
BEN1310 - PANVALET FILE ACCESS FAILED
BEN1330 - DYNAMIC ACCESS FAILED, TASK TERMINATED
BEN1510 - LIBRARIAN FILE ACCESS FAILED
BEN1530 - MEMBER START FAILED, MEMBER SKIPPED
BEN1770 - FATAL ERROR, NOT A COMPRESSED RECORD
BEN1910 - SQL ERROR MESSAGE ACCESS FAILURE
BEN1911 - MAX OF 10 CURSORS EXCEEDED
BEN1912 - DSNTIAR MESSAGE DECODE IS INACTIVE
BEN1915 - CURSOR NAME GREATER THAN 8 CHARACTERS
BEN1920 - SQL ERROR WARNING MESSAGE
BEN1930 - SQL STATEMENT ATTEMPTING EXECUTION
BEN1940 - STMT LOAD OF VARIABLE OVERFLOWED BUFFER
BEN1950 - NOT NUMERIC FIELD FOUND, REQUEST SKIPPED
BEN1960 - CODE:XXXX IS AN UNKNOWN VARIABLE TYPE
BEN1965 - INVALID HOST VARIABLE L=XXXXX, XXXXX REQ
BEN1966 - INTERNAL SQL WORK TABLE OVERFLOWED
BEN1967 - PROCESS WIL CONTINUE WITH SQL ERROR
BEN1968 - ATTEMPTING ROLLBACK DUE TO FATAL ERRORS
BEN1970 - SQL HOST VARIABLE TABLE EXCEEDS 300 FLDS
USER ABEND CODES:
U1001 - NON-ZERO CONDITION CODES SET, CHECK R01 MESSAGES
EXPLANATION:
During the processing of this run, the next instruction to execute was at the end of the command list. Workbench expects a process loop handling normal end-of-job when all records have been processed. Use "GOTO EOJ" if you wish to stop processing at the end of the command statements.PROCESS RESULT:
All processing up to this point would have been successfully done. Return code of cc=4 will be set to warn of a possible error.PROGRAMMER ACTION:
Check your input commands for logic errors looking for a fall out at the end of the command list. To avoid the error message, at the end of your command list code a GOTO EOJ which is equivalent to a fall out condition.
BEN0120 - LEASE HAS EXPIRED.....JOB CANCELED
EXPLANATION:
The lease period has expired. Workbench will not process any requests.PROCESS RESULT:
Job will stop with a condition code cc=8.PROGRAMMER ACTION:
Check with your system representative.
BEN0130 - WARNING LEASE TERM HAS EXPIRED..........
EXPLANATION:
This a warning that Workbench will stop processing in a few days.PROCESS RESULT:
Job will process with a cond code cc=4.PROGRAMMER ACTION:
Check with your system representative.
BEN0140
- WARNING CALLED PGM RTN CODE NOT = 00EXPLANATION:
This is a warning that the user called program returned a non-zero return code.PROCESS RESULT:
Job will continue processing.PROGRAMMER ACTION:
Check user program requirements.EXPLANATION:
The call attach facility did not succeed. The return code and reason code values can be found in the IBM Advanced application guide manual. Normally the cause DB2 is down or your system id given is mistyped.PROCESS RESULT:
Job will attempt to recover and continue.PROGRAMMER ACTION:
Check DB2 system status and the stated reason code.
BEN0150 - WARNING FIELD EDIT CAUSED OVERFLOW
EXPLANATION:
This a warning that the data replacement failed. The operation required more room to expand than was available.PROCESS RESULT:
Job will continue processing, but request will be skipped.PROGRAMMER ACTION:
Report R01 will report those records skipped. A manual approach may be needed to alter those records.
BEN0160 - REQUEST VALUE DISPLAYED
EXPLANATION:
Informational message that the requested value was converted and displayed.PROCESS RESULT:
Job will continue processing.PROGRAMMER ACTION:
Report R01 will report displays.EXPLANATION:
PARM=TRACE was used on the execute statement of Workbench. The trace facility will list each command in object format as it is executed. Primary use is for telephone debugging support. See your systems representative.PROCESS RESULT:
Job will process issuing displays on R01.PROGRAMMER ACTION:
None. Use the displays to verify your process loops. Through telephone support, we can determine byte size, format type, and field location as well as special verb indicators.
BEN0170 - CALL PARM EXCEEDS 100 LIMIT
EXPLANATION:
CALL verb request attempted to pass more than 100 data fields.PROCESS RESULT:
Edits will continue but no processing will be done.PROGRAMMER ACTION:
Reduce parm list to less than 100.
BEN0171 - EXCEEDED 100 PERFORM LEVELS, STACK FULL
EXPLANATION:
CALL verb request attempted to save it's return address, but it exceeded 100 entries.PROCESS RESULT:
Processing will continue as if the operation was successful, but the command action was skipped for this request. Condition code of cc=4 is set.PROGRAMMER ACTION:
Likely you have a logic problem and are calling the performed routine without issuing a RETURN. Each time you perform the same routine, another return address is saved but never cleared with a RETURN. Having GOTO's in a routine that jump you out of the performed routine can cause this common error.
BEN0172 - EXCEEDED 100 RETURN LEVELS, STACK FULL
EXPLANATION:
Same messages as BEN0171 above.
BEN0180 - NOT NUMERIC FIELD FOUND, PROCESS SKIPPED
EXPLANATION:
An automatic numeric conversion was being done, but a non-numeric data value was found during the operation.PROCESS RESULT:
Processing will continue as if the operation was successful, but the command action was skipped for this request. Condition code of cc=4 is set.PROGRAMMER ACTION:
To avoid the error message use a numeric test (IF fld1 NOT NUMERIC) to clear out the bad data.
EXPLANATION:
During addition/subtraction, the result value was too large for a binary receiving field.PROCESS RESULT:
Processing will continue with the warning message, but the receiving field was not modified. Condition code of cc=4 is set.PROGRAMMER ACTION:
Change the receiving field to be packed or character (15 max digits) or reduce the amount being added into the field. IBM's max size for binary was reached.EXPLANATION:
During addition/subtraction, the internal work field overflowed.PROCESS RESULT:
Processing will continue with the warning message, but the receiving field was not modified. Condition code of cc=4 is set.PROGRAMMER ACTION:
Reduce or split up the add/subtract requirements. IBM's max size for packed fields was reached.EXPLANATION:
Editor compiled the command into the command table ready for processing. Edits were successfully completed.PROCESS RESULT:
Next command will be edited.PROGRAMMER ACTION:
Confirm all commands are accepted.
BEN0210 - FILE DEFINED AS BOTH INPUT AND OUTPUT
EXPLANATION:
Editor already marked the file name given as an input or output file, but the command given is in conflict with the previous setting.PROCESS RESULT:
Edits will continue but no processing will be done.PROGRAMMER ACTION:
Review the commands given for all references of the file name used in the command. Common causes are (1) using an output name on a MOVE, IF, PRINT, DUMP, DUMPH or COMPARE statement; (2) WRITE statement has file names reversed.
BEN0211 - MAX FILE NUMBER IS 99 PER JOB
EXPLANATION:
Editor found over 99 files being defined.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Reduce files to 99 or less.EXPLANATION:
Editor found non-numerics in either LENGTH or POSITION operands.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the numeric field.
BEN0221 - "INTO" FIELD MISSING
EXPLANATION:
Editor could not find the INTO keyword required in the STRING/UNSTRING verb.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the command syntax.EXPLANATION:
Editor could not find the DELIMITED BY keyword required in the STRING/UNSTRING verb.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the command syntax.EXPLANATION:
User specified the DEC=nn greater than 15 and Workbench as a 15 place limit. Decimal places should only be used on SQL update/insert fields to get proper values.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the command syntax.EXPLANATION:
Editor found LENGTH operand value greater than 32760.PROCESS RESULT:
Edits will continue but no process will be done.PROGRAMMER ACTION:
Correct the numeric field.EXPLANATION:
Editor found LENGTH operand value was zero, which is not allowed.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the numeric field.EXPLANATION:
Editor found POSITION operand greater than 32760.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the numeric field.EXPLANATION:
Editor found POSITION operand equal to zero.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Correct the numeric field.
BEN0242 - TYPE CODE NOT C, P, OR X
EXPLANATION:
Editor found TYPE operand not C, P, XPROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Define TYPE operand as Char, Packed, or Hex type. Default if not specified is Character.
BEN0250 - FILE NAME GREATER THAN 8 CHARACTERS
EXPLANATION:
Editor found a file name that was greater than 8 character limit.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Reduce the file name size. It must match the JCL ddname used which also is limited to 8 characters.EXPLANATION:
Editor found a READ verb requesting more than one file name.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Change the command statement to use only one file.EXPLANATION:
Editor found a file name used but could not find a READ, READPDS, or SYNC verb to request a record read.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Remove the possible unwanted reference or add your read request by using a READ, SYNC, READPDS, READLIB, or READPAN verb. This is a common error. Check your working storage fields for a mis-typed file name in the DEFINES. Defines fields are always input files and never output ddnames.EXPLANATION:
Editor found the special 4K WORKAREA being referenced as an output file. WORKAREA is only available as an input type ddname.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Changed the write statement so that the work area is not the output file name.EXPLANATION:
Editor found a READPDS/PAN/LIB member name mask that did not match a previous statement definition.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
All file ddname masks within the same job step must match. If you wish to use the same file with a different member name, select/read in a second ddname for the same file.EXPLANATION:
Editor could not determine the next keyword to process in the explicit syntax given.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Look for incorrect spelling or syntax in the explicit format used. Correct and reprocess.EXPLANATION:
Editor found more than the 15 digit limit in the packed field being used.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Reduce the digit count to 15 or less and reprocess. If more than 15 digits are required, use Hex format which has no limits except card size.EXPLANATION:
Editor found a Hex field being defined with a non-hex character or not defined in full bytes.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Review the hex characters and correct. See DEFINES verb in the Command Section for rules and restrictions.EXPLANATION:
Editor could not find the label referenced. Labels must be specified before their use. Syntax may be incorrect.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Check any spelling errors, define the label used, or correct the syntax. Labels must start in column 1. See DEFINES verb.EXPLANATION:
Editor found label being defined has already been accepted.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Remove duplicate "DEFINES" statements.EXPLANATION:
"IF" statement had no conditional verb or symbol.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Review syntax of the "IF" statement and correct.EXPLANATION:
BENCHCMD file failed to open. Check JCL for missing file.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Review JCL or use the standard JCL proc.EXPLANATION:
EOJ is a reserved tag name used in the GOTO verb. A EOJ routine name was found being defined by the user.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
EOJ does not need to be defined because it is an internal branch tag name. The edit is to prevent coding confusions.EXPLANATION:
VAR is a reserved field name for dynamic modification of field attributes. A VAR field name was found being defined by the user.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
VAR does not need to be defined because it is an internal field name. The edit is to prevent coding errors.
EXPLANATION:
LOC is a reserved field name for dynamic modification of field attributes. A LOC field name was found being defined by the user.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
LOC does not need to be defined because it is an internal field name. The edit is to prevent coding errors.EXPLANATION:
BENCHCMD file was empty. Process requests are required and will not default.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Input commands for processing.EXPLANATION:
A GOTO verb was used and referenced a process tag but it could not resolve the reference.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Define the label.EXPLANATION:
An SQL statement was identified by the use of "EXECSQL". The statement given did not fit in the 32760 byte dymanic buffer area as required by the dynamic SQL facility. This size also includes the total number of field bytes along with the statement command string. Normally the user has symply forgotten the "END-EXEC" to denote the end of the SQL.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Review the SQL command.EXPLANATION:
Editor could not determine process verb that was requested.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Check syntax and spelling for the indicated statement.
EXPLANATION:
Editor could not build any more commands into the command table. See system representative for limit details.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Reduce command statement size. Removing periods "." will save command entries in the table.
EXPLANATION:
Editor could not build any more literals into the literal table. See system representative for limit details.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
Reduce literals used in the command stmts.
EXPLANATION:
Editor could not build any more labels into the label table. See system representative for limit details.PROCESS RESULT:
Edits will continue but will not process. PROGRAMMER ACTION: Reduce labels used in the "DEFINES" stmts.
EXPLANATION:
The editor found more than 99 parms being requested, which overflows Workbench's storage limit.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
The maximum PCBs that can be passed to Workbench is 99. If you are calling from another supervisor program passing linkage parms, we suggest you group the elements under a common layout to avoid the 99 individual field address limit. Although it is not advertised, Workbench can be called from any User program as well as call User programs by using the ENTRY/DLILINK verbs.
EXPLANATION:
Editor found a request for linkage parms but did not find a valid ENTRY verb.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
DLILINK requires an ENTRY verb. See the command section under DLILINK.
EXPLANATION:
Editor could not match the linkage area name in the ENTRY.PROCESS RESULT:
Edits will continue but will not process.PROGRAMMER ACTION:
DLILINK requires an ENTRY verb. See the command section under DLILINK.
EXPLANATION:
The given command was determined to be an IDMS process command. However, the full IDMS syntax was not correct.PROCESS RESULT:
No processing will occur, job will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the IDMS command verb syntax.
EXPLANATION:
Input or output file failed to open.PROCESS RESULT:
No processing will occur; job will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Input files using in the SYNC process was found to be not ascending.PROCESS RESULT:
Partial processing may have occurred. Job will stop with a return code of cc=8.PROGRAMMER ACTION:
Make sure the input files are sorted ascending and rerun job.EXPLANATION:
A READ verb was requested on an entire PDS file. The READ and SYNC verb can only read QSAM or VSAM VB or FB files.PROCESS RESULT:
No processing has begun. Job will stop with a return code of cc=8.PROGRAMMER ACTION:
If library processing is needed use the READPDS verb. Otherwise check the JCL to see if the member name was specified on the file.EXPLANATION:
The PDS file directory is full.PROCESS RESULT:
Partial processing may have occurred. Job will stop with a return code of cc=8.PROGRAMMER ACTION:
Delete the old file and re-allocate the directory blocks on the file. Workbench can write up to 21 member entries per directory block.
EXPLANATION:
The PDS file directory is probably damaged.PROCESS RESULT:
Partial processing may have occurred. Job will stop with a return code of cc=8.PROGRAMMER ACTION:
A rare situation but possible should two jobs be updating the PDS at the same time.EXPLANATION:
Workbench will not permit the processing of undefined files such as load libraries.PROCESS RESULT:
No processing will begin. Task will stop with a return code of cc=8.PROGRAMMER ACTION:
Load libraries are not permitted to be accessed or modified with Workbench. See your systems software staff for special load module modifying utilities.
EXPLANATION:
A QSAM sequential output request was made on a PDS defined file.PROCESS RESULT:
No processing will begin. Task will stop with a return code of cc=8.PROGRAMMER ACTION:
Check your processing verbs. You must change either your JCL or your WRITE request.
EXPLANATION:
A READPDS was made on a sequential file. You must use a READ verb.PROCESS RESULT:
No processing will begin. Task will stop with a return code of cc=8.PROGRAMMER ACTION:
Check your processing verbs. You must change either your JCL or your READ request.EXPLANATION:
The file requested has a record length of zero. Undefined file formats are not permitted.PROCESS RESULT:
No processing will begin. Task will stop with a return code of cc=8.PROGRAMMER ACTION:
Load libraries are not permitted to be or modified with Workbench. See you systems software staff for special load module modifying utilities.EXPLANATION:
BENCHR01 output print file failed to open. Message will display on the JES log.PROCESS RESULT:
Edits will not continue. Job will stop.PROGRAMMER ACTION:
Correct the JCL by adding BENCHR01 ddname.EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.EXPLANATION:
The XREF report has an internal sort to process the data names. Check your sort messages on the JES log for more messages.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Possible sort work space problems. Contact the system representative for further information.
EXPLANATION:
Spelling facility attempted to read user dictionary words from ddname BENCHWRD.PROCESS RESULT:
Warning message only, Workbench's base dictionary will be used.PROGRAMMER ACTION:
Standard Proc specifies this ddname as DUMMY to avoid message.EXPLANATION:
Output ddname for object word dictionary is missing.PROCESS RESULT:
Job terminates.PROGRAMMER ACTION:
Restricted process.
EXPLANATION:
Word found in text could not be located in dictionary.PROCESS RESULT:
Informational message displayedPROGRAMMER ACTION:
Workbench could not find the displayed word in its dictionary. New words can be added to the dictionary process via BENCHWRD. This file requires one word per record with file attributes of RECFM=VB and LRECL=34. See SPELL verb for more information.
EXPLANATION:
User word entered via BENCHWRD ddname was hashed numerically, but was already found in the dictionary.PROCESS RESULT:
Warning message to indicate duplicate. Processing will continue. PROGRAMMER ACTION: Error indicates two situations. One, the word already exists in the dictionary, or two, the dictionary is becoming full. It is estimated Workbench's hashing algorithm can handle 150,000 words.EXPLANATION:
Spelling check totals.PROCESS RESULT:
Information message. Processing will continue.PROGRAMMER ACTION:
None.
EXPLANATION:
Output print file failed to open.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the JCL and rerun job.
EXPLANATION:
Panvalet file open or read failed.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
The most common problem is an invalid interface to the Panvalet browse modules. New releases of Panvalet, incorrect file definitions with respect to recfm=u have been found over the years. See your system representative for assistance.EXPLANATION:
Workbench attempted to recover from error BEN1310, but could not proceed.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
See problem BEN1310 for details.
EXPLANATION:
Workbench requested a work file dynamically but the operating system could not satisfy the request.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Workbench most likely requested a device such as SYSDA that is not defined for your data center. See your system representative for assistance.
EXPLANATION:
VSAM read access failed.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Verify the VSAM file is defined correctly or see your system representative for assistance.
EXPLANATION:
Librarian file open or read failed.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
The most common problem is an invalid interface to the Librarian browse modules. New releases of Librarian, incorrect file definitions with respect to recfm=u have been found over the years. See your system representative for assistance.
EXPLANATION:
Workbench attempted to recover from error BEN1510, but could not proceed.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
See problem BEN1510 for details.
EXPLANATION:
A member was found in the directory but when it started to read the entry, the member records were not found.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Verify that another user did not delete the member while your task was processing. Otherwise see your system representative.
EXPLANATION:
The file record being decompressed did not contain the special control flag bytes. Decompress is not possible.PROCESS RESULT:
Partial processing may have occurred to the request. Processing attempt to continue with a return code of cc=4.PROGRAMMER ACTION:
Verify that the command syntax is correct. Often you have the ddnames reversed. The compressed file should be on the left and the receiving file to the right.
EXPLANATION:
This is an internal programming message indicating DSNTIAR load module could not be found.PROCESS RESULT:
Processing will continue, but you should check with the systems representative for correction.PROGRAMMER ACTION:
None, this is a Workbench internal error.
EXPLANATION:
Workbench has a 10 cursor limit for DB2 user declared cursors in a single process step. This limit can extended upon request and reload of your DB2 Workbench system.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Reduce the number of unique cursors being defined. Cursors can be dynamically rebuilt by using Workbench symbolics in place of keywords and even table names. By re-executing the "DECLARE" and the open/fetch/close logic. See reference section for examples.
EXPLANATION:
Workbench uses IBM's DSNTIAR program to decode the SQLCODE into text. This program is not properly linked into the BENCH load module and cannot be called. Please refer the problem to your systems support staff. DSNTIAR must be statically linked into the BENCH load. Refer to the installation guide for DB2 link requirements.PROCESS RESULT:
Processing will continue normally.PROGRAMMER ACTION:
Please refer the problem to your systems support staff. DSNTIAR must be statically linked into the BENCH load. Refer to the installation guide for DB2 link requirements.
EXPLANATION:
The DB2 cursor name given is greater the 8 characters which is a Workbench limit.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Reduce the cursor name size to eight.
EXPLANATION:
DB2 has issued an error message. The text of the error is printed as received from the dbms.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Refer to the IBM DB2 error manual for details of the condition. The information given is similar to messages received in COBOL program erorr handling routines.EXPLANATION:
This message follows BEN1920 and prints the SQL statement that Workbench was attempting to process.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Verify the command listed is the format and variables you intended to use. Possibly the symbolic substitution you requested caused an invalid DB2 statement.
EXPLANATION:
This is an internal programming message indicating a variable being loaded into the dynamic SQL verb buffer was too large for Workbench's reserved work space.PROCESS RESULT:
Processing will stop with a cc=8. Please check with the systems representative to report the problem.PROGRAMMER ACTION:
None, this is a Workbench internal error.
EXPLANATION:
See message BEN0180
EXPLANATION:
xxxx is filled in with an error code for more information. See the DB2 manuals for value descriptions. This is an internal Workbench error message. The variable type given is not supported.PROCESS RESULT:
Processing will stop with a cc=8. Please check with the systems representative to report the problem.PROGRAMMER ACTION:
None, this is a Workbench internal error.
EXPLANATION:
The DB2 variable given is too large to fit in the receiving field.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Check the variables listed in the request SQL verb. One of your variables will exceed the receiving field. Increase the receiving field to at least the size required.
EXPLANATION:
The SQL cursor requested does not match up with the host variables given on the FETCH statement.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct the variables listed in the request SQL verb.
EXPLANATION:
This an informational message warning you that an SQL error code was issued but Workbench will ignore it and continue.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will continue.PROGRAMMER ACTION:
None, verify that you expected the condition listed.EXPLANATION:
The SQL error code listed is severe enough for workbench to automatically issue a rollback. Rollback will be up to the last valid commit point.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Correct SQL error code listed.
EXPLANATION:
Workbench and IBM have a 300 column limit for SQL statements.PROCESS RESULT:
Partial processing may have occurred prior to the request. Processing will stop with a return code of cc=8.PROGRAMMER ACTION:
Reduce the variables listed in the request SQL verb.
EXPLANATION:
Workbench was executing with PARM=ABEND which issues a user abend should edit or process errors occur in the job.PROCESS RESULT:
Partial processing may have occurred prior to the output request. Processing will stop with a return code of cc=U1001 abend.PROGRAMMER ACTION:
Check for messages on R01 edit report. ERRORS=ABEND is not required and generally only used to prevent cataloging files.