Explanation: Either you have mis-entered the authorization code, or your license to use the product (or feature) has expired.
Response: Verify that you have entered the authorization code correctly. If the code is correct, contact Neon Systems.
Explanation: A temporary authorization code for one or more REXXTOOLS features is about to expire.
Response: Contact Neon Systems, or your distributor.
Explanation: The address argument has an invalid component.
Response: Correct the address argument and retry the function call.
Explanation: Either the storage at the indicated location has not been allocated or is fetch protected.
Response: Correct the problem and retry the function call.
Explanation: The storage at the indicated location is protected, and cannot be modified by a problem state program in user key.
Response: Correct the problem and retry the function call.
Explanation: The STORFL of the current environment block indicates that use of the STORAGE function is invalid. STORAGEX interprets this bit setting as disallowing storage modification only.
Response: Use another REXX environment or do not attempt to modify storage.
Explanation: Modules that are to be LINKed to by REXX must run AMODE(31).
Response: Re-linkedit the indicated module.
Explanation: Modules that are to be LINKed to by REXX must be reentrant in order to not be reloaded with each LINK.
Response: Re-link-edit the indicated module.
Explanation: This ddname has already been opened.
Response: You must close a ddname before you can reopen it.
Explanation: This ddname has not yet been opened.
Response: Open the ddname before you attempt any other VSAM operation.
Explanation: The MACRF option you specified was invalid.
Response: Correct the options argument and retry the open.
Explanation: The SYNAD exit was invoked for an I/O operation. The text of the message describes the operation attempted.
Response: This message is caused by various problems. If reading a sequential file, verify that the file is not empty. If you have specified DCB parameters for an existing file, verify that these are consistent with the information in the VTOC. Use the TSO LISTD command to obtain data set DCB characteristics.
Explanation: You have tried to open a file using the wrong access method.
Response: Verify the access method argument of the OPEN function. QSAM and BPAM can be used with sequential files and PDSs. VSAM can be used with VSAM files only.
Explanation: The BPAM and QSAM interfaces support only those RECFMs listed in their respective chapters. Specifically, spanned records are not supported.
Response: Do not open the failing data set.
Explanation: BLKSIZE cannot exceed 32760. For variable length records the block size must be at least 8, and must always be at least 4 bytes longer than the LRECL.
Response: Correct the block size and retry the operation.
Explanation: LRECL must be greater than zero and less than or equal to the block size. If RECFM=F is used, LRECL must be identical to BLKSIZE. If RECFM=FB is used, BLKSIZE must be an even multiple of LRECL. If variable length records are used, the LRECL must be at least 4.
Response: Correct the LRECL or BLKSIZE (whichever is appropriate) and retry the operation.
Explanation: The GET function has been used with incompatible open options.
Response: Verify that the file is open for input or update. GET cannot be used with a file that is open for output.
Explanation: The detected logical record length is either zero, longer than the indicated LRECL parameter, or longer than the block size.
Response: This could happen if you read an empty sequential data set, or if you specify DCB characteristics that are incompatible with the characteristics defined in the VTOC. Correct the problem and re-run the job.
Explanation: A FINDM function call did not precede the failing GET.
Response: When using BPAM, you must establish position using the FINDM function prior to reading a member. Correct the problem and re-run the job.
Explanation: The indicated length of the retrieved block was either zero, or longer than the value given by BLKSIZE parameter.
Response: This could happen if you read an empty sequential data set, or if you specify DCB characteristics that are incompatible with the characteristics defined in the VTOC. Correct the problem and re-run the job.
Explanation: The retrieved record is not entirely contained within the current block.
Response: This could be caused by an invalid record descriptor word (RDW). Dump the file to determine the cause of the problem. If no problem is found, call OST technical support.
Explanation: A PUT was issued for a file that was opened with incompatible options.
Response: PUT may be used only with files that are open for output or update. It may not be used with a file that is open for input. Correct the open options and re- run the job.
Explanation: A PUT for update was executed without a preceding GET for update.
Response: A record must be read with GET prior to PUTting it back. You must do this even if you plan to ignore the read record. Correct the problem and re-run the job.
Explanation: A function has been used that is not proper for the access method in use.
Response: This problem has several forms. You may not, for example, use the FINDM function with a file that was opened using QSAM. If you intended to use another access method, correct the access method argument of the OPEN function, and retry the operation.
Explanation: STOWM was used with a file that was opened with incompatible options.
Response: STOWM may be used only with files that are open for output or update.
Explanation: FINDM was used with a file that was opened with incompatible options.
Response: FINDM may be used only with files that are open for input or update.
Explanation: This is an informational message that shows the current SQL command. Usually the sqlcommand displayed is the "processed string", not the input command string. However, in some cases the unprocessed command string is displayed.
Response: If this message is accompanied by error messages, correct the problem and rerun the exec.
Explanation: The DECLARE STATEMENT command is not supported.
Response: Remove the DECLARE STATEMENT command.
Explanation: The DECLARE type is not recognized.
Response: Only DECLARE CURSOR, DECLARE VARIABLE, and DECLARE TABLE, are supported. Check for spelling or syntax errors.
Explanation: The cursor name cannot be used.
Response: Cursor names must be valid REXX variable symbols 1 to 8 bytes long. $SWXCSR$ is a reserved name.
Explanation: More cursors were declared than are available in the pool of static cursors.
Response: You must free a cursor in order to declare another one.
Explanation: You have tried to re-declare a cursor that has already been declared.
Response: Free the cursor before trying to re-declare it.
Explanation: The DECLARE CURSOR cannot be used.
Response: Check for syntax errors, and rerun the program.
Explanation: The host variable name not a valid REXX variable name.
Response: Check for coding errors. Refer to the REXX Reference for information regarding valid REXX variable names. Note though, that the "?" cannot be used, even though it is permitted in REXX symbols.
Explanation: The DECLARE command cannot be used due to syntax errors.
Response: Correct any errors and rerun the program.
Explanation: The FREE command is in error.
Response: Check for syntax errors, correct these, and rerun the program.
Explanation: The FREE type is unrecognized.
Response: Only FREE CURSOR and FREE VARIABLE commands are supported. Check for spelling errors.
Explanation: The operation on the cursor cannot be performed because the cursor is open.
Response: Close the cursor before attempting the operation.
Explanation: You have attempted to use a cursor before you have declared it.
Response: Use the DECLARE CURSOR command to declare the cursor before using its name. If you thought you did, check for logic or spelling errors.
Explanation: You have attempted an operation on a variable that is not declared.
Response: You either did not declare the variable, or you have already freed it.
Explanation: You have attempted to free variables for the program, but no variables were found.
Response: Check to make sure that you have not already freed the variables.
Explanation: A non-zero SQLCODE has been returned by DB2. The message explains the problem.
Response: Refer to DB2 Messages and Codes, SC26-4379 for problem resolution.
Explanation: The host command was zero-length or all blanks.
Response: You must pass a non-blank host command expression. Use the TRACE C REXX instruction to trace host command execution.
Explanation: The SQL command could not be executed because the first word was not a recognized SQL command.
Response: Check for spelling errors in your host command.
Explanation: The token in the OPTIONS command is not a valid option.
Response: Check for spelling errors.
Explanation: No options followed the OPTIONS verb.
Response: You must code at least one option.
Explanation: The OPTIONS command could not be executed due to syntax errors.
Response: Check for spelling errors. Also note that options must be separated by one or more blanks.
Explanation: A DB2 request did not result in the SQLCA being filled in.
Response: Verify that you connected to a DB2 subsystem prior to executing the command.
Explanation: The INTO clause of a SELECT or FETCH statement does not have the same number of variables as there are columns to be retrieved.
Response: Correct the problem and retry the request.
Explanation: The CONNECT statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The SET statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The DESCRIBE statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The table or view name is longer than 254 bytes.
Response: Correct the problem and retry the request.
Explanation: The variable name is not a valid REXX variable name.
Response: Correct the problem and retry the request. Refer to REXX Reference for the definition of valid variable names.
Explanation: The CLOSE statement is not usable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The cursor that has been OPENed, FETCHed, or CLOSEd, or used in a WHERE CURRENT OF clause has not been declared.
Response: Execute a DECLARE CURSOR statement prior to using the csrname in any other statement.
Explanation: The OPEN statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The FETCH statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The BEGIN or END DECLARE SECTION statement is not useable due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: One of the output variables in the statement was not a valid REXX variable name.
Response: Correct the problem and retry the request. Refer to REXX Reference for the definition of valid variable names.
Explanation: A question mark was found in the host command expression.
Response: Question marks are not permitted and must be removed.
Explanation: The parser ran out of tokens before a closing quote mark was found.
Response: Correct the problem and retry the request.
Explanation: The parser encountered a token larger than the maximum.
Response: Neither DB2 nor REXX require tokens larger than 250 bytes. Correct the problem and retry the request. Check for missing blank delimiters.
Explanation: The EXEC SQL or terminating semicolon were mis-coded.
Response: Check for spelling and punctuation errors. Correct the problem and retry the request.
Explanation: The INTO clause could not be processed.
Response: Verify that your host variables are all prefixed with colons, and that host variable expression are separated by commas.
Explanation: The variable named in this message is not a valid REXX variable name.
Response: Correct the problem and retry the request. Refer to REXX Reference for the definition of valid variable names.
Explanation: The variable named in this message is not a valid REXX variable name.
Response: Correct the problem and retry the request. Refer to REXX Reference for the definition of valid variable names.
Explanation: The indicator variable contains a non- numeric value.
Response: Use TRACE I to find the problem. Indicator variables must contain numeric values between -32768 and +32767.
Explanation: The REXX variable access routine indicated that a variable name in the request is invalid.
Response: Correct the problem and retry the request. Refer to REXX Reference for the definition of valid variable names.
Explanation: A colon that was not immediately followed by another token was found.
Response: You may have coded a blank between the colon and the variable name. Correct the problem and retry the request.
Explanation: A value larger than the maximum accepted by DB2 was found.
Response: DB2 will not accept a value larger than this. Correct the problem and retry the request.
Explanation: The variable listed could not be converted from the REXX printable data type to the target DB2 data type.
Response: Usually this happens when a variable declaration is missing. Check for spelling errors.
Explanation: The RELEASE statement could not be used due to syntax errors.
Response: Correct the problem and retry the request.
Explanation: The token listed is not a valid ALLOCATE or FREE keyword.
Response: Check for spelling errors, errors in abbreviation, and punctuation errors.
Explanation: The request tried to allocate more than one data set with a status of NEW.
Response: You can only allocate NEW data sets one at a time.
Explanation: The keyword listed was not followed by a correct value expression.
Response: Keyword values must be enclosed in parentheses. In addition, each keyword has specific value coding requirements.
Explanation: The product's storage stack pointer has exceeded one of its bounds.
Response: Contact Neon Systems.
Explanation: The product's storage stack pointer has exceeded one of its bounds.
Response: Contact Neon Systems.
Explanation: The SWXANCHR module has been corrupted.
Response: Try logging off and logging back on. If that does not correct the problem, obtain a dump of the SWXANCHR module, and contact Neon Systems.