PROC CARIMA stops processing and issues errors if the following conditions are met:

• A CASLIB= option in a LIBNAME statement specifies a predefined caslib that is not the active caslib in the SAS^® Cloud Analytic Services (CAS) session.
• The OUTEST= option in the PROC CARIMA statement specifies a data set in the library that is named in the LIBNAME statement.
• No prior PROC CARIMA step is executed in the same CAS session with an OUTEST= option specifying a data set in a library mapped to either a personal caslib or an active predefined caslib.

The following error messages appear in the log:

ERROR: A table could not be loaded.
ERROR: The action stopped due to errors.
ERROR: uniTimeSeries.arima request failed to complete normally.

If you run another PROC CARIMA step after these errors appear, the following error messages are issued in the log, and the procedure stops processing without producing output:

ERROR: I/O errors prohibit completion of CAS action.
ERROR: The action stopped due to errors.
ERROR: uniTimeSeries.arima request failed to complete normally.

To avoid the problem, start a new CAS session, and specify your personal caslib or an active predefined caslib in the CASLIB= option in the LIBNAME statement. Note that if you omit the CASLIB= option in the LIBNAME statement, the active caslib is used by default. Alternatively, you can use the following statement to change the nonactive caslib to be the new active caslib before running the PROC CARIMA step:

cas casauto cassessopts=(caslib=yourcaslib);

Then specify the new active caslib in the LIBNAME statement.

The following is an example. Suppose your CAS session has your personal caslib CASUSER as the active caslib, and PUBLIC is a nonactive caslib. The following code generates the errors:

cas session1;
libname D1 cas caslib=PUBLIC;
data D1.AIR;
   set SASHELP.AIR;
run;
proc carima data=D1.AIR outest=D1.est;
   id date interval=month;
   identify air;
   estimate q=(1)(12);
run;

To avoid the error, start a new CAS session, and specify the active caslib in your session. In this case, it is your personal caslib CASUSER in the CASLIB= option in the LIBNAME statement. Alternatively, simply omit the CASLIB= option in the LIBNAME statement as in this example:

cas session2;
libname D2 cas caslib=CASUSER;
data D2.AIR;
   set SASHELP.AIR;
run;
proc carima data=D2.AIR outest=D2.est ;
   id date interval=month;
   identify air;
   estimate q=(1)(12);
run;

Alternatively, you can use the following line of code to change the PUBLIC caslib to be the new active caslib in the session:

cas casauto cassessopts=(caslib=public);

Then specify CASLIB=PUBLIC in the LIBNAME statement before the PROC CARIMA step:

cas session3;
cas casauto cassessopts=(caslib=public);
libname d cas caslib=public;
data d.air;
   set sashelp.air;
run;
proc carima data=D.AIR outest=D.cariest;
   id date interval=month;
   identify air;
   estimate q=(1)(12);
run;