# Messages

## General

SWX0000S REXXTOOLS AUTHCODE MISSING, INVALID, OR EXPIRED

  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.

SWX0001W YOUR LICENSE TO USE A REXXTOOLS PRODUCT FEATURE WILL EXPIRE IN count DAYS

  Explanation: A temporary authorization code for one or more REXXTOOLS features is about to expire.

  Response: Contact Neon Systems, or your distributor.

## STORAGEX Function

SWX0240E STORAGEX ADDRESS IN ERROR AT xxxxxxxx

  Explanation: The address argument has an invalid component.

  Response: Correct the address argument and retry the function call.

SWX0241E STORAGE AT 'xxxxxxxx'X COULD NOT BE ACCESSED

  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.

SWX0242E STORAGE AT 'xxxxxxxx'X COULD NOT BE MODIFIED

  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.

SWX0243E STORAGE MODIFICATION IS CURRENTLY DISABLED

  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.

## REXX Module Load (SWXCRRLD)

SWX0260E MODULE module IS NOT AMODE 31

  Explanation: Modules that are to be LINKed to by REXX must run AMODE(31).

  Response: Re-linkedit the indicated module.

SWX0261E MODULE module IS NOT REENTRANT

  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.

## QSAM, BPAM, and VSAM Interfaces

SWX0300E DDNAME ddname IS ALREADY IN USE

  Explanation: This ddname has already been opened.

  Response: You must close a ddname before you can reopen it.

SWX0301E DDNAME ddname IS NOT IN USE

  Explanation: This ddname has not yet been opened.

  Response: Open the ddname before you attempt any other VSAM operation.

SWX0302E INVALID OPTION SPECIFIED

  Explanation: The MACRF option you specified was invalid.

  Response: Correct the options argument and retry the open.

SWX0303E synadmsg

  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.

SWX0304E DATASET DSORG IS INVALID FOR SELECTED ACCESS METHOD

  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.

SWX0305E DATASET RECFM IS NOT SUPPORTED

  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.

SWX0306E DATASET BLKSIZE IS INVALID

  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.

SWX0307E DATASET LRECL IS INVALID

  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.

SWX0308E GET IS INVALID IN THIS CONTEXT. CHECK OPEN OPTIONS

  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.

SWX0309E RETRIEVED RECORD'S LRECL IS INVALID

  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.

SWX0310E FINDM MUST BE PERFORMED BEFORE GET

  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.

SWX0311E RETRIEVED BLOCK'S LENGTH IS INVALID

  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.

SWX0312E CURRENT RECORD LIES OUTSIDE THE RETRIEVED BLOCK

  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.

SWX0313E PUT IS INVALID IN THIS CONTEXT. CHECK OPEN OPTIONS

  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.

SWX0314E NO RECORD TO UPDATE. A GET MUST PRECEDE A PUT FOR UPDATE

  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.

SWX0315E THIS OPERATION IS INCOMPATIBLE WITH THE CURRENT ACCESS METHOD

  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.

SWX0316E STOWM IS INVALID IN THIS CONTEXT. CHECK OPEN OPTIONS

  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.

SWX0317E FINDM IS INVALID IN THIS CONTEXT. CHECK OPEN OPTIONS

  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.

## Dynamic SQL

SWX0600I sqlcommand

  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.

SWX0601W DECLARE STATEMENT IS UNSUPPORTED

  Explanation: The DECLARE STATEMENT command is not supported.

  Response: Remove the DECLARE STATEMENT command.

SWX0602W DECLARE STATEMENT IS UNRECOGNIZED

  Explanation: The DECLARE type is not recognized.

  Response: Only DECLARE CURSOR, DECLARE VARIABLE, and DECLARE TABLE, are supported. Check for spelling or syntax errors.

SWX0603E CURSOR NAME csrname IS INVALID OR RESERVED

  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.

SWX0604E MAXIMUM NUMBER OF DECLARED CURSORS EXCEEDED

  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.

SWX0605E CUSOR NAME csrname IS ALREADY IN USE

  Explanation: You have tried to re-declare a cursor that has already been declared.

  Response: Free the cursor before trying to re-declare it.

SWX0606E DECLARE CURSOR STATEMENT IS UNUSABLE

  Explanation: The DECLARE CURSOR cannot be used.

  Response: Check for syntax errors, and rerun the program.

SWX0607E VARIABLE NAME varname IS INVALID

  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.

SWX0608E DECLARE STATEMENT SYNTAX ERROR

  Explanation: The DECLARE command cannot be used due to syntax errors.

  Response: Correct any errors and rerun the program.

SWX0609E FREE STATEMENT IS UNUSABLE

  Explanation: The FREE command is in error.

  Response: Check for syntax errors, correct these, and rerun the program.

SWX0610E FREE STATEMENT IS UNRECOGNIZED

  Explanation: The FREE type is unrecognized.

  Response: Only FREE CURSOR and FREE VARIABLE commands are supported. Check for spelling errors.

SWX0611E CURSOR NAME csrname IS OPEN

  Explanation: The operation on the cursor cannot be performed because the cursor is open.

  Response: Close the cursor before attempting the operation.

SWX0612E CURSOR NAME csrname NOT FOUND

  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.

SWX0613E VARIABLE NAME varname NOT FOUND

  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.

SWX0614E NO VARIABLES FOR PROGRAM progname

  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.

SWX0615I db2message

  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.

SWX0616E SQL STATEMENT STRING IS EMPTY

  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.

SWX0617E token IS NOT A RECOGNIZED SQL VERB

  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.

SWX0618E token IS NOT A RECOGNIZED OPTION

  Explanation: The token in the OPTIONS command is not a valid option.

  Response: Check for spelling errors.

SWX0619E NO OPTIONS SPECIFIED

  Explanation: No options followed the OPTIONS verb.

  Response: You must code at least one option.

SWX0620E OPTIONS STATEMENT SYNTAX ERROR

  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.

SWX0621E DB2 DID NOT COMPLETE SQLCA

  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.

SWX0622E NO. OF INTO VARS DOES NOT MATCH NO. OF SELECTED COLS

  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.

SWX0623E CONNECT STATEMENT SYNTAX ERROR

  Explanation: The CONNECT statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0624E SET STATEMENT SYNTAX ERROR

  Explanation: The SET statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0625E DESCRIBE STATEMENT SYNTAX ERROR

  Explanation: The DESCRIBE statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0626E TABLE/VIEW NAME IS TOO LONG

  Explanation: The table or view name is longer than 254 bytes.

  Response: Correct the problem and retry the request.

SWX0627E VARIABLE NAME varname IS INVALID OR TOO LONG

  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.

SWX0628E CLOSE STATEMENT SYNTAX ERROR

  Explanation: The CLOSE statement is not usable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0629E CURSOR NAME csrname HAS BEEN USED BEFORE IT HAS BEEN DECLARED

  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.

SWX0630E OPEN STATEMENT SYNTAX ERROR

  Explanation: The OPEN statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0631E FETCH STATEMENT SYNTAX ERROR

  Explanation: The FETCH statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0632E BEGIN/END DECLARE SECTION SYNTAX ERROR

  Explanation: The BEGIN or END DECLARE SECTION statement is not useable due to syntax errors.

  Response: Correct the problem and retry the request.

SWX0633E STATEMENT CONTAINED AN INVALID OUTPUT VARIABLE

  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.

SWX0634E STATEMENT CONTAINS A QUESTION MARK. QUESTION MARKS ARE NOT PERMITTED.

  Explanation: A question mark was found in the host command expression.

  Response: Question marks are not permitted and must be removed.

SWX0635E END OF STATEMENT FOUND BEFORE END OF LITERAL

  Explanation: The parser ran out of tokens before a closing quote mark was found.

  Response: Correct the problem and retry the request.

SWX0636E STATEMENT CONTAINS A TOKEN LARGER THAN 250 BYTES

  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.

SWX0637E 'EXEC SQL' OR TERMINATING SEMICOLON SYNTAX ERROR

  Explanation: The EXEC SQL or terminating semicolon were mis-coded.

  Response: Check for spelling and punctuation errors. Correct the problem and retry the request.

SWX0638E INTO CLAUSE SYNTAX ERROR

  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.

SWX0639E varname IS AN INVALID DATA VARIABLE NAME

  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.

SWX0640E varname IS AN INVALID INDICATOR VARIABLE NAME

  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.

SWX0641E INPUT INDICATOR VARIABLE varname CONTAINS A VALUE THAT CANNOT BE CONVERTED TO A SMALLINT NUMBER

  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.

SWX0642E IRXEXCOM DETECTED INVALID VARIABLE NAME

  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.

SWX0643E A COLON WAS NOT IMMEDIATELY FOLLOWED BY A VARIABLE NAME

  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.

SWX0644E VARIABLE varname CONTAINS A VALUE THAT IS MORE THAN 32767 BYTES LONG

  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.

SWX0645E VARIABLE varname COULD NOT BE CONVERTED TO TYPE db2type

  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.

SWX0646E RELEASE STATEMENT SYNTAX ERROR

  Explanation: The RELEASE statement could not be used due to syntax errors.

  Response: Correct the problem and retry the request.

## Dynamic Allocation

SWX0800E token IS NOT A RECOGNIZED ALLOCATE KEYWORD

  Explanation: The token listed is not a valid ALLOCATE or FREE keyword.

  Response: Check for spelling errors, errors in abbreviation, and punctuation errors.

SWX0801E A STATUS OF 'NEW' IS INCOMPATIBLE WITH A DATA SET CONCATENATION REQUEST

  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.

SWX0800E keyword KEYWORD SYNTAX ERROR

  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.

## Internal

SWX0900S REXXTOOLS STACK OVERFLOW

  Explanation: The product's storage stack pointer has exceeded one of its bounds.

  Response: Contact Neon Systems.

SWX0901S REXXTOOLS STACK UNDERFLOW

  Explanation: The product's storage stack pointer has exceeded one of its bounds.

  Response: Contact Neon Systems.

SWX9002S INVALID ANCHOR BLOCK

  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.

© Copyright 1998 by Open Software Technologies, Inc.