Why doesnt the proc just require the .sas scorecode? The astore is referenced in the file, so the program could just read the string, load the astore and promote it, without all the manual overhead right? I want to set up scoring in production inside VIYA using the job scheduler. So I need to be able to retrieve all the required details to score data from the VIYA API (not to be confused with the API score code you can manually download). I only get what seems to be a epscorecode, but it does not look exactly like the score code I get from manually downloading the score code, as the manually downloaded starts with /*
* This score code file references one or more analytic stores that are located in the caslib "Models".
* This score code file references the following analytic-store tables:
* _96SJQFBWWOK4EGEAM4HYEDMKS_ast
*/
data sasep.out;
dcl package score _96SJQFBWWOK4EGEAM4HYEDMKS(); and the one from the API looks like this: package MS_09368ff81a7b41aea9fbac8bdeea6aec_15SEP2020120014413 / overwrite=yes;
dcl package score _JMW1HUQBK0CMF01WMVDI39WS(); Without the data step and starting with just package, not dcl package. Which I guess could be a bug? I suppose it should also start with dcl? So I can get what seems to be the .sas epcode from the API. Inside that file, there is a method() part. So I guess I have to parse the file, find the string to find the astore\.sashdat, load the dataset, promote it, save the file two files, then use the two in a proc astore? And correct the missing dcl in the start of the file I guess. I have to set this up to run daily scoring, so I can't rely on manually reading and loading and promoting tables. But I can't quite believe how convoluted this is compared to using the old score codes, or scoring in any other environment for that sake.
... View more
