When you try to score a model using the RUNMODEL statement with the SCOREACCEL procedure, errors similar to the following might appear in the CAS log:

ERROR: General error in UDF/XSP/UDM SAS_SYSFNLIB.SAS_SCORE_EP: SQLSTATE U0031: SASTblOp failed: CLI Error Code 7504: in UDF/XSP/UDM
       SAS_SYSFNLIB.SASTBLOP_CONTRACT: SQLSTATE U1010: DS2 program failed to be prepared. TKTSPrepare returned 0x80fff8
ERROR: The SQL command to run the SAS Embedded Process failed.
ERROR: Execution of model 'model01' failed (rc=0x90ffd815).
ERROR: The action stopped due to errors.
ERROR: The SQL command to run the SAS Embedded Process failed. [ABORT]

The journal table, created with the 'OPTIONS=EPTRACE=YES;EPDEBUG=4;JOURNALTABLE=xxx; option, might contain errors similar to the following:

ERROR: Base table or view not found MS_1E108A5679E44BDD81E3A1AE2AFFCDF6
ERROR: Table "SASEP.MS_1E108A5679E44BDD81E3A1AE2AFFCDF6" does not exist or cannot be accessed.
ERROR: Status code 0x80fff802 returned.
ERROR: DS2 internal error code 0x5BFD7A112192434F. Refer to DS2 documentation for resolving errors.
ERROR: Status code 0x80fff802 returned.
ERROR: DS2 internal error code 0xC5493DBF975A41D3. Refer to DS2 documentation for resolving errors.
ERROR: Unable to create stored program for sasep.ms_1e108a5679e44bdd81e3a1ae2affcdf6_12jul2021123032537.
ERROR: [HY000]Compilation error. (0x817ff229).

The issue occurs when the following is true:

• The model was published using PROC SCOREACCEL PUBLISHMODEL.
• The model was published to Teradata.
• The MODELTYPE=DS2 option was used with the publishing.
• The DS2 file referenced with the PROGRAMFILE= option creates a package rather than a data set.

The issue is caused because the wrong file was used in the original publishing of the model. When you publish to Teradata, use a DS2 data program file.