Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| SAS Companion for the OpenVMS Operating Environment |
ERROR: Bad
parameter value
ERROR: Insufficient
space in file xxx.xxxxx.DATASAS data sets are limited in size to 4,194,304 blocks. When this value is exceeded, you receive these errors.
ERROR: Broadcast
trapping disabled due to internal errorsThis message indicates that a non-fatal error occurred while the SAS System was trying to establish broadcast message trapping. Although your SAS session will initialize, broadcast messages will not be trapped properly if you are running the SAS System in the windowing environment.
ERROR: Cannot
create mailbox for subprocess. Check quotas and privilegesThe SAS System encountered an error while trying to create the mailbox used by the X 'DCL-command' form of the X statement or command. This message may 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 privilegesThe SAS System encountered an error while trying to spawn a subprocess from the X command or statement. This message may be preceded by an OpenVMS message indicating the exact nature of the problem. Check your process quotas and privileges.
ERROR: Data
overrun. Tape device mounted with blocksize smaller than used to write dataThe block size specified in the DCL MOUNT command is smaller than the actual block size of the tape. Remount the tape with the correct block size.
ERROR: Error
attempting terminal input with /SPAWN=NOWAIT in
effectYou cannot invoke the SAS System interactively in a SPAWN/NOWAIT subprocess. For additional details, see Running SAS in a SPAWN/NOWAIT Subprocess.
ERROR: Error
while loading image image-nameThe SAS System 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-specificationAn error occurred when the SAS System 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-specificationAn error occurred when the SAS System 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 supportedThis 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 the procedure VAXTOAXP.
ERROR: Insufficient
memory to initialize the SAS SystemThere is not enough memory for the SAS System to initialize.
ERROR: Interactive
SAS invocation unsupported with /SPAWN=NOWAIT in
effectYou cannot invoke the SAS System 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-nameInsufficient memory was obtained to load the image.
ERROR: Invalid
conversion of KEYVALUE to data type of specified key on indexed fileA 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 FIXEDIf you are writing records to a file that uses fixed-length records, you must use the LRECL= external I/O statement option to specify the record length.
ERROR: LRECL
must be specified with RECFM=DA record format of D (DATA step unlabeled tape) was specified but the LRECL= option was not specified. Correct your program and resubmit it.
ERROR: Maximum
of 8 parameters exceeded for PARAMETERS= optionDue to DCL restrictions, a maximum of eight parameters can be specified for a job that was submitted to a printer queue. Correct your program and resubmit it.
ERROR: Module module-name signalled fatal error conditionThe SAS System encountered a fatal internal error. Report this error to your SAS Support Consultant.
ERROR: Output
open of a text library requires exclusive access. File is already openThe OpenVMS system allows 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 optionThe 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 optionThe SAS System does not support the following key data types: unsigned 8-byte binary, signed 8-byte integer, collating key, and packed decimal string.
ERROR: Subordinate
image image-name not foundThe SAS System could not find the named subordinate image while trying to load a higher-level image. This message is preceded by a message that indicates which high-level image was being loaded. Report this error to your SAS Installation Representative.
ERROR: This
option can be used on command line onlyA host system option that can be used only in the SAS command or configuration file was specified in the OPTIONS statement.
ERROR: Trying
to write block shorter than 14 bytes. File will not be completeWhile writing to tape, the SAS System attempted to write a block that is less than 14 bytes long. This error typically indicates that the entire file is less than 14 bytes. Use the LRECL= option to extend the length of each record.
ERROR: Unable
to print fatal conditionThe SAS System encountered a fatal internal error. Report this error to your SAS Support Consultant.
ERROR: Update
access to indexed files is not supportedYou 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 supportedYou 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 outputWhile wildcards and concatenated file specifications are allowed for input, they are not allowed for output. Correct your program and resubmit it.
Full screen
SAS could not obtain a channel to the terminalWithout a channel to the terminal, the windowing method of running the SAS System cannot run. Your process may have reached the SYSGEN CHANNELCNT limit.
Illegal
use of dms-command. Key processing terminated
prematurely.
Illegal
use of dms-command in a DM statement or from
a command lineCertain 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: BUFSIZE
value too large. Maximum size of 65535 used.The largest I/O transfer size allowed under OpenVMS is 65,535 bytes. The SAS System uses this value for the BUFSIZE= value.
NOTE: CC=CR
and OVERPRINT may yield unexpected results. Use options NOOVP with CC=CRWith 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 usedCC=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: Could
not load image SASMSGThe SASMSG image, which contains the text of all host messages, could not be loaded. Although the SAS System is able to run without this image, report this error to your SAS Installation Representative.
NOTE: LRECL
option ignored for PRINT files when RECFM equals VARIABLEThe LRECL= external I/O statement option specifies record lengths when RECFM=FIXED; it is not valid when RECFM=VARIABLE. Modify your SAS job accordingly.
NOTE: OVERPRINT
ignored when specified with option CC=CROverprinting is not allowed when you write to files with carriage-return carriage control.
NOTE: Previous
value of logical-name has been supersededThe OpenVMS logical name has been superseded by a new value.
NOTE: Some
records have been truncated to existing length of variable length recordDuring 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 optionThis message is printed if you are writing records that are larger than those specified by the LRECL= external I/O statement option. You may want to modify the LRECL= value accordingly.
NOTE: Text
library members cannot be spooled. Device type of PRINTER or PLOTTER ignoredYou 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-nameWhile loading the named image, the SAS System 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 foundThe SAS System 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 conditionThe SAS System was unable to print the fatal condition that it encountered. Report this error to your SAS Support Consultant.
%SAS-E-NOPGMCON,
no program constants found for image image-nameThe named image contains invalid internal data. Report this error to your SAS Installation Representative.
%SAS-E-UNLOADERR,
error while unloading image image-nameThe SAS System was unable to unload the named image while it was cleaning up resources. 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-ASNERR,
error assigning files during CLI processingIf the SAS System encounters an error while assigning a logical name when parsing options, this message is printed, along with the name of the file that the SAS System was trying to assign. Correct the problem and perform the operation again.
%SAS-F-ASNTERM,
error assigning filename to terminalThe SAS System 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 handlerThe SAS System 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 foundThe SAS System 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 initializeThe SAS System 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-nameAn error occurred when the SAS System 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-BRGLOOP,
transfer vector stub-name/image-name not fixedAn internal error occurred in the SAS System. Report this error to your SAS Support Consultant.
%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-specificationAn error occurred when the SAS System was closing the configuration file file-specification. Report this error to your SAS Support Consultant.
%SAS-F-CONFIGOPEN,
error opening file-level filenameThe SAS System encountered an error while trying to open a configuration file. File-level indicates whether the configuration file was at the process, group, or system 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-CORRUPT,
image image-name is corruptThe SAS System detected an error in the named image while trying to load it. Report this error to your SAS Installation Representative.
%SAS-F-DELETE,
error deleting file file-specificationAn error occurred when the SAS System was deleting a file in the WORK subdirectory. For more information, see The CLEANUP Tool.
%SAS-F-ERRCREWRK,
error creating work library subdirectory directory-nameAn error occurred when the SAS System 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 occurredThis 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 SAS Support Consultant.
%SAS-F-INVOPTVALUE,
value for host-option host option is invalidYou specified an invalid value for the host-option option. For the valid values for the option, see System Options. Specify a valid value and perform the operation again.
%SAS-F-INVWRKLIB,
work library specified contains invalid directory pathThe 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-nameThe SAS System 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 memoryMemory 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-NOMEM,
SAS memory manager ran out of memory for internal useMemory 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 queueAn 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-nameThe SAS System 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-nameThe SAS System 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-nameThe SAS System 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 inputAn error occurred when the SAS System 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 deviceThe SAS System 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-specificationAn error occurred when the SAS System 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-optionThe option that was specified was converted to its new name under the current release of the SAS System.
%SAS-I-DEAPNOTFOUND,
SASDEAP1.EXE cannot be foundTo fully unload an image once it has been loaded, the SASDEAP1.EXE image must be loaded. This image performs privileged unloading; if the SAS System cannot find this image, privileged unloading is not active.
%SAS-I-NODECW,
The DECwindows device driver was not foundThe DECwindows device driver image was not found. Ask your SAS Installation Representative to check the installation of the product at your site.
%SAS-I-NOMSG,
unable to retrieve resource thief messagesThe SAS System encountered an error while trying to read a message file. This error does not keep the SAS System from running, but if you encounter resource-critical situations (such as out-of-disk conditions), title messages will not appear. Report this error to your SAS Support Consultant.
%SAS-I-OBSOPT,
ignoring obsolete option option-nameThe option that was specified was a valid option in an earlier version of the SAS System, but it is no longer valid and is ignored.
%SAS-W-ALTNOTPRNTQ,
value for option-name specifies a queue that
is not an output queueYou specified an invalid queue name for the given option. Correct your program and resubmit it.
%SAS-W-INVNOLOG,
interactive mode prohibits use of /NOLOG, qualifier ignoredIf you are entering the SAS System 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 matchYou attempted to use an X command to deassign a logical name that does not exist.
%SAS-W-NOLOGTAB,
no logical name table matchYou 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 operationYou 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 ignoredYou 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 commandThe X command status could not be retrieved from the subprocess.
The GOLD
key is not supported in numeric modeIn the SAS windowing environment, you cannot use the Gold key while in numeric mode. Turn numeric mode off with the APPLICATION command before you press the Gold key.
Type LOGOFF
to return to SASYou entered one of the following forms of the X statement and spawned a subprocess:
X '';
X;
Warning:
CC option may be specified for print files only. Option ignoredYou specified the CC= option for a nonprint file. This option is valid only for print files. Modify your SAS job accordingly.
WARNING:
low stack encountered for task task-nameThe task named has a stack size that is too small for the attempted job. You can use the STACK system option to modify the amount of stack space allocated for the job. Report this message to your SAS Support Consultant.
X command
submode not supported in batchYou used one of the following forms of the X statement in a SAS job that is running in batch mode:
X '';
X;
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.