 |
|
| Error Messages |
Host Subsystem Messages under OpenVMS
-
ERROR: Bad
parameter value
ERROR: Insufficient space in file xxx.xxxxx.DATA -
SAS data sets are limited in size to 4,294,967,294 (or 4 gigabyte) blocks. When this value is exceeded, you receive these errors.
- ERROR: Cannot create mailbox for subprocess. Check quotas and privileges
-
SAS encountered an error while trying to create the mailbox used by the X 'DCL-command' form of the X statement or command. This message might be preceded by an OpenVMS message indicating the exact nature of the problem. Check your process privileges and quotas.
- ERROR: Cannot spawn subprocess. Check process limit quotas and privileges
-
SAS encountered an error while trying to spawn a subprocess from the X command or statement. This message might be preceded by an OpenVMS message indicating the exact nature of the problem. Check your process quotas and privileges.
- ERROR: Error attempting terminal input with /SPAWN=NOWAIT in effect
-
You cannot invoke SAS interactively in a SPAWN/NOWAIT subprocess. For additional details, see Running SAS in a SPAWN/NOWAIT Subprocess.
- ERROR: Error while loading image image-name
-
SAS was unable to load the named image, but processing continues if possible. Ensure that you have spelled all procedures, functions, and formats correctly. If you are unable to determine the cause of this error, contact your SAS Installation Representative.
- ERROR: Error while opening loadlist file file-specification
-
An error occurred when SAS was opening the LOADLIST file. Check the filename for valid OpenVMS filename specifications. For more information about specifying OpenVMS filenames, see OpenVMS Filenames.
- ERROR: Error while writing to loadlist file file-specification
-
An error occurred when SAS was writing to the LOADLIST file. Ensure that you have WRITE access to the LOADLIST file.
- ERROR: IEEE numbers with a length less than 3 are not supported
-
This data set contains observations with numeric variables of length 2. The data set cannot be created or translated. For information about converting 2-byte variables to 3-byte variables, see VAXTOINTEG Procedure: OpenVMS.
- ERROR: Insufficient memory to initialize the SAS System
- ERROR: Interactive SAS invocation unsupported with /SPAWN=NOWAIT in effect
-
You cannot invoke SAS interactively in a SPAWN/NOWAIT subprocess. For additional details, see Running SAS in a SPAWN/NOWAIT Subprocess.
- ERROR: Insufficient virtual memory to load image image-name
- ERROR: Invalid conversion of KEYVALUE to data type of specified key on indexed file
-
A conversion error, such as overflow, underflow, or value is not an integer, has occurred. Check the defined key data type on the indexed file and modify the KEYVALUE= value accordingly.
- ERROR: LRECL must be specified when RECFM equals FIXED
-
If you are writing records to a file that uses fixed-length records, you must use the LRECL= external I/O statement host-option or the LRECL= system option to specify the record length.
- ERROR: Module module-name signalled fatal error condition
-
SAS encountered a fatal internal error. Report this error to your on-site SAS support personnel.
- ERROR: Output open of a text library requires exclusive access. File is already open
-
The OpenVMS system enables you to write to only one member of a text library at a time. Modify your SAS job accordingly.
- ERROR: Specified key on indexed file is defined as key-data-type-1, but key-data-type-2 was used in KEYVALUE option
-
The specified KEYVALUE= value has a data type that conflicts with the defined key data type on the indexed file. Check the defined key data type on the indexed file and modify the KEYVALUE= value accordingly.
- ERROR: Specified key on indexed file is of unsupported type for KEYVALUE option
-
SAS does not support the following key data types: unsigned 8-byte binary, signed 8-byte integer, collating key, and packed decimal string.
- ERROR: This option can be used on command line only
-
A host system option that can be used only in the SAS command or configuration file was specified in the OPTIONS statement.
- ERROR: Unable to print fatal condition
-
SAS encountered a fatal internal error. Report this error to your on-site SAS support personnel.
- ERROR: Update access to indexed files is not supported
-
You have specified both a FILE and an INFILE statement that access the same indexed file. UPDATE access is currently not supported. Correct your program and resubmit it.
- ERROR: Update or random access to members of text libraries is not supported
-
You have tried to update a member of an OpenVMS text library (perhaps with a FILE statement), or used the FSLIST procedure with an OpenVMS text library. This access is currently not supported. Correct your program and resubmit it.
- ERROR: Wildcard or concatenated filespec not allowed for output
-
While wildcards and concatenated file specifications are allowed for input, they are not allowed for output. Correct your program and resubmit it.
-
Illegal
use of dms-command. Key processing terminated
prematurely.
Illegal use of dms-command in a DM statement or from a command line -
Certain SAS commands are supported only under the OpenVMS operating environment. Their use is constrained. Only one of these commands can be assigned to a single function key. The commands cannot be mixed with each other or with other windowing commands. These commands cannot be used in DM statements or typed manually on the command line. These commands are
CHINSERT DELWORD CURSORDOWN MOVEBOL CURSORLEFT MOVEEOL CURSORRIGHT NEWLINE CURSORUP NEXTFIELD DELCHAR NEXTWORD DELLINE PREVFIELD DELPCHAR PREVWORD DELTOEOL - NOTE: CC=CR and OVERPRINT may yield unexpected results. Use options NOOVP with CC=CR
-
With the CR (carriage return) file format, there is no overprint character. Therefore, set the OVP system option to NOOVP to suppress overprinting.
- NOTE: CC=PRINT and RECFM=F are conflicting attributes. CC=CR will be used
-
CC=PRINT corresponds to the variable with fixed control (VFC) file format. Therefore, a fixed record format is incompatible. CC=CR (carriage return) is compatible with a fixed record format.
- NOTE: Previous value of logical-name has been superseded
-
The OpenVMS logical name has been superseded by a new value.
- NOTE: Some records have been truncated to existing length of variable length record
-
During an update to an external file, the length of the new record exceeded the length of the existing record. The new record was truncated to the length of the existing record.
- NOTE: Some records have been truncated to length specified by LRECL option
-
This message is printed if you are writing records that are larger than those specified by the LRECL= external I/O statement option. You might want to modify the LRECL= value accordingly.
- NOTE: Text library members cannot be spooled. Device type of PRINTER or PLOTTER ignored
-
You have specified the PRINTER or PLOTTER device type keyword in a FILENAME statement with an OpenVMS text library. OpenVMS does not allow spooling of text library members.
- NOTE: Unable to queue job to printer due to the following error:
-
This message is followed by an OpenVMS message describing the error. Correct the problem and perform the operation again.
- %SAS-E-BADCHECK, bad image header for image image-name
-
While loading the named image, SAS encountered invalid data in the image and could not proceed. Ask your SAS Installation Representative to check the installation of the product. Ensure that your site is licensed for the product that you are trying to use.
- %SAS-E-NOIMAGE, image image-name not found
-
SAS was unable to load the named image because it could not find the image. Ask your SAS Installation Representative to check the installation of the product. Ensure that your site is licensed for the product that you are trying to use.
- %SAS-E-NOMSG, unable to print fatal condition
-
SAS was unable to print the fatal condition that it encountered. Report this error to your on-site SAS support personnel.
- %SAS-E-NOPGMCON, no program constants found for image image-name
-
The named image contains invalid internal data. Report this error to your SAS Installation Representative.
- %SAS-F-ASNERR, error assigning files during CLI processing
-
If SAS encounters an error while assigning a logical name when parsing options, this message is printed, along with the name of the file that SAS was trying to assign. Correct the problem and perform the operation again.
- %SAS-F-ASNTERM, error assigning filename to terminal
-
SAS encountered an error while trying to connect to the terminal. An OpenVMS message follows this message and indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-ASTERR, error establishing CTRL-C AST handler
-
SAS encountered an error while creating a handler for the CTRL-C attention sequence. The OpenVMS return code is printed along with this message. Correct the problem and perform the operation again.
- %SAS-F-AUTOEXECFNF, autoexec file file-specification not found
-
SAS could not find the autoexec file specified. Check the file specification in any AUTOEXEC= options that you have used. Also, check the file that is indicated by the SAS$INIT logical name. Make sure that you have access to the file.
- %SAS-F-BADOPTION, option syntax error in configuration file, SAS cannot initialize
-
SAS encountered a system option that was not valid in the configuration file. Check all options in the SAS command and in your configuration file for accuracy.
- %SAS-F-BADRANGE, value for option-name host option is out of range
-
A host system option with an integer value was assigned a value outside the valid range.
- %SAS-F-BADTRNLNM, Unable to translate logical name for logical-name
-
An error occurred when SAS was translating the named logical name. This message is followed by an OpenVMS return code that indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-CALLREP, please contact your SAS Site Representative and report the following error:
-
This message is printed for all fatal errors encountered during a SAS session. Check for old or duplicate versions of the named image in your default directory and in the path that is defined by SAS$LIBRARY search list logical. Report this error to your SAS Installation Representative.
- %SAS-F-CLSERR, error closing configuration file file-specification
-
An error occurred when SAS was closing the configuration file file-specification. Report this error to your on-site SAS support personnel.
- %SAS-F-CONFIGOPEN, error opening file-level filename
-
SAS encountered an error while trying to open a configuration file. File-level indicates whether the configuration file was at the process, group, system, or cluster level. file-specification is the full pathname for the file. Ensure that you spelled any configuration filenames correctly. Also, check with your system manager to ensure that you have privileges for the group- and system-level configuration files. Finally, check that the file that is pointed to by the OpenVMS logical name SAS$CONFIG exists.
- %SAS-F-DELETE, error deleting file file-specification
-
An error occurred when SAS was deleting a file in the WORK subdirectory. For more information, see The CLEANUP Tool.
- %SAS-F-ERRCREWRK, error creating work library subdirectory directory-name
-
An error occurred when SAS was creating the WORK subdirectory. An OpenVMS return code is printed to give you more information. Correct the problem and perform the operation again.
- %SAS-F-INTSASERR, A SAS error has occurred
-
This message is printed for all fatal errors that are encountered during a SAS session. Report this error and the full text of any error message that follows it to your on-site SAS support personnel.
- %SAS-F-INVOPTVALUE, value for host-option host option is invalid
-
You specified an invalid value for the host-option option. For the valid values for the option, see System Options under OpenVMS. Specify a valid value and perform the operation again.
- %SAS-F-INVWRKLIB, work library specified contains invalid directory path
-
The directory path that was specified for the data library has invalid OpenVMS directory syntax. Correct the problem and perform the operation again.
- %SAS-F-LOADERR, error while loading image image-name
-
SAS was unable to load the named image. This message is followed by an OpenVMS return code that indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-NOMEM, insufficient virtual memory
-
Memory that is needed for the internal use of the SAS memory manager could not be allocated. This message is equivalent to the message %SAS-F-CLIMEM.
- %SAS-F-NOTPRNTQ, value for option-name specifies a queue that is not an output queue
-
An invalid queue name was specified for the given option. Correct your program and resubmit it.
- %SAS-F-NOWRKFILCRE, unable to create files in the work library subdirectory directory-name
-
SAS was unable to create files in the WORK data library subdirectory. An OpenVMS message follows this message and indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-NOWRKFILDEL, unable to delete files in the work library subdirectory directory-name
-
SAS was unable to delete files in the WORK data library subdirectory. An OpenVMS message follows this message and indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-OPENERR, unable to open image image-name
-
SAS received an error while opening the named image to load it. This message is followed by an OpenVMS return code that indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-OPENIN, error opening file-specification as input
-
An error occurred when SAS was opening one of several files: the configuration file, the input SAS file, or a device. An OpenVMS return code is printed after this message that indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-OPENTERM, error opening terminal device
-
SAS encountered an error while trying to connect to the terminal. An OpenVMS message follows this message that indicates the exact nature of the problem. Correct the problem and perform the operation again.
- %SAS-F-REAERR, Error reading configuration file file-specification
-
An error occurred when SAS was reading the configuration file file-specification. Correct the problem and perform the operation again.
- %SAS-I-ALTOPT, option old-option has been converted to new-option
-
The option that was specified was converted to its new name under the current release of SAS.
- %SAS-I-OBSOPT, ignoring obsolete option option-name
-
The option that was specified was a valid option in an earlier version of SAS, but it is no longer valid and is ignored.
- %SAS-W-INVNOLOG, interactive mode prohibits use of /NOLOG, qualifier ignored
-
If you are entering SAS in interactive line mode, the NOLOG option is prohibited. This option is valid only in noninteractive and batch modes.
- %SAS-W-NOLOGNAM, no logical name match
-
You attempted to use an X command to deassign a logical name that does not exist.
- %SAS-W-NOLOGTAB, no logical name table match
-
You issued an ASSIGN or DEFINE command from the X command and specified a logical name table that does not exist.
- %SAS-W-NOPRIV, no privilege for attempted operation
-
You issued an ASSIGN or DEFINE command from the X command and attempted an operation for which your process does not have privilege.
- %SAS-W-UNSUPPORTED, the qualifier qualifier-name is unsupported and will be ignored
-
You specified a MOUNT command from the X command and specified a MOUNT qualifier that is not supported by the X command.
- %SAS-W-X_NORC, unable to retrieve status from X command
-
The X command status could not be retrieved from the subprocess.
- Type LOGOFF to return to SAS
-
You entered one of the following forms of the X statement and spawned a subprocess:
- Warning: CC option may be specified for print files only. Option ignored
-
You specified the CC= option for a nonprint file. This option is valid only for print files. Modify your SAS job accordingly.
- X command submode not supported in batch
-
You used one of the following forms of the X statement in a SAS job that is running in batch mode:
The X statement is not supported in batch mode.
|
|
Copyright © 2009 by SAS Institute Inc., Cary, NC, USA. All rights reserved.