Chapter Contents
Previous
Next
SAS Companion for the OS/390 Environment

Messages from the SASCP Command Processor

To help you identify and remedy problems when running under TSO, the SAS System provides the following list of messages from the SASCP command processor. SASCP is involved in processing SAS System tasks and is invoked by the terminal monitor program as a standard TSO command processor.

SAST001I COMMAND SYSTEM ERROR +
Entering a question mark in the line following this message produces one of these additional messages:

Either the SAS command processor was unable to allocate enough memory to begin execution, or the system failed while it was parsing the command line. This message should not occur under normal conditions; inform your local SAS Support Consultant.

SAST002I DATA SET dsn NOT IN CATALOG or SAST002I DYNAMIC ALLOCATION ERROR, IKJDAIR RETURN CODE rc DARC drc CTRC crc
The SAS command processor was unable to locate a data set that was specified by the TASKLIB operand. This message usually indicates that a data set name was misspelled.

SAST003I MORE THAN 15 TASKLIB DATA SETS SPECIFIED
You have specified more than 15 task-library data sets with the TASKLIB operand. Reduce the number of task-library data sets.

SAST004I dsn IS NOT A PARTITIONED DATA SET
For the value of the TASKLIB operand, you have specified a task-library data set that is not a partitioned data set. This message usually indicates a misspelled data set name or a reference to the wrong data set.

SAST005I TASKLIB CANNOT BE OPENED
The SAS command processor was unable to open the task library. You have probably specified an invalid load library as a task-library data set in the TASKLIB operand.

SAST006I SAS ENTRY POINT NAME NOT SPECIFIED
You have not specified a member name for the SAS entry point. Use the ENTRY operand to specify an entry-point name for the SAS System.

SAST007I SAS ENTRY POINT NAME entry-name NOT FOUND
The SAS command processor was unable to locate the member name that was specified as the SAS entry point. This message usually indicates that an entry-point name was misspelled. Use the ENTRY operand to specify a valid entry-point name.

SAST007I BLDL I/O ERROR ON TASKLIB
An error occurred during BLDL processing of TASKLIB.

SAST008I OPTIONS FIELD TRUNCATED TO 256 CHARACTERS
The options parameter string that was passed to the SAS System was too long and was truncated to 256 characters. (This string consists of SAS options that you specified as the value of the OPTIONS operand plus any additional SAS options that were supplied automatically within the SAS CLIST.) This message is a warning message.

SAST009I COMMAND SYSTEM ERROR +
Entering a question mark in the line following this message produces one of these additional messages:

Either the SAS command processor was unable to allocate enough memory to invoke the SAS System, or the system was unable to create the SAS subtask. This message should not normally occur; inform your local SAS Support Consultant.

SAST010I entry-name ENDED DUE TO ERROR +
This message indicates that the SAS session has terminated abnormally (abended). Entering a question mark in the line following this message produces one of these additional messages:

A user abend code of 999 ('3E7'x) indicates an error condition. You can specify other user abend codes in the SAS ABORT statement. A system abend code should not normally occur; inform your local SAS Support Consultant.

SAST011I entry-name TERMINATED DUE TO ATTENTION
The SAS session has ended because you pressed the BREAK or ATTN key and then entered the word END in response to the message SAST013D.

SAST012I COMMAND SYSTEM ERROR +
Entering a question mark in the line following this message produces one of these additional messages:

Either the SAS command processor was unable to allocate enough memory to invoke the SAS System, or an error occurred during execution of the SASCP command. This message should not normally occur; inform your lcoal SAS Support Consultant.

SAST013D ENTER "END" TO TERMINATE SAS, OR A NULL LINE TO CONTINUE
The SAS System displays this prompt when the SAS command processor detects that the BREAK or ATTN key has been pressed. Enter the word END to leave the SAS session, or enter a null line to resume SAS processing.

SAST014I INVALID RESPONSE, MUST BE "END" OR A NULL LINE
You have entered a response other than the word END or a null line after receiving message SAST013D. Enter either the word END or a null line.

SAST015I SASCP INVOKED IN A NON-TSO ENVIRONMENT OR PASSED INVALID PARAMETERS
USE SASCP AS A TSO COMMAND TO INVOKE SAS IN THE FOREGROUND
USE PGM=SAS TO INVOKE SAS IN THE BACKGROUND
SASCP was not invoked as a TSO command, and it could not locate the appropriate TSO control blocks to reconstruct a TSO command environment, either because it was invoked as a background program or because the TSO environment is nonstandard. If you were running under TSO, contact your local SAS Support Consultant.

SAST016I PARM FIELD TRUNCATED TO 256 CHARACTERS
The PARM list operand that was passed to the CALL command is too long and was truncated. (The CALL command is used to invoke the SAS System.)

SAST017I INVALID PARAMETER LIST PASSED TO IKJDAIR
An invalid parameter list was passed to the TSO service routine IKJDAIR. This message should not normally occur; inform your local SAS Support Consultant.

SAST018I SASCP INVOKED IN A NON-TSO ENVIRONMENT USE PGM=SAS TO INVOKE SAS IN THE BACKGROUND
SASCP was not invoked under TSO.


Chapter Contents
Previous
Next
Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.