Hi Elise,   Here are a few suggestions: Make sure that the irm_sc_init() macro is executed first before executing any other macros. For more info, refer to SAS Help Center: %irm_sc_init. For parameter substitution, refer to the SAS Help Center: Anatomy of the Task File Header documentation. If you require further assistance, please open a case with our SAS Technical Support here: “Access the SAS Customer Service Portal”.  Be sure to provide the following details in the ticket: SAS Product you are using and version a detailed description of what you are attempting to achieve what the expected result is what result you are getting the full text log with any errors Thank you! ... View more

Same library reference in libnames.txt of different federated areas or solutions may create conflict.   Example: FA1 > libnames.txt defines STAGING = %la/%bd FA2 > libnames.txt defines STAGING = %la/some_folder/%bd   Depending on which FA (and consequently libnames.txt) is being picked up by IRM, you may face error of "Data not found". So, it must be avoided.   On the other side, library references in output of different job flows can be repeated since each instance runs in its own dedicated folder. ... View more

Thank in advance for the lengthy question . ... View more

ello   Yes,    I got an azure storage blob, and had it attached as a NFS, then i created a libname towards that and used proc casutil to get the data into CAS.   On most systems I have an NFS, it was only on this PoC env. it was missing ... View more

If this is purely metadata driven code without any user written code portion then I suggest you contact SAS Tech Support. If it's user written code then just fix the code (=user written selected in the transformation).  ... View more

Posting the log would be helpull to see what kinf of error you get. If it is not the same error as mentioned by the author of this topic I would start a new topic. ... View more

Hello, Choose your incaslib= and look in the dataset work.FileInfo ! cas mySession sessopts=(caslib=casuser timeout=1800 locale="en_US"); ODS TRACE OFF; ODS OUTPUT FileInfo=work.FileInfo; proc casutil incaslib="Public"; *list tables; list files; run; QUIT; cas mySession terminate; Koen ... View more

Looks like these are the codes it's using: https://developer.sas.com/apis/rest/v3.5/Compute/#error-codes-3 ... View more

By "job log" are you referring to the log file associated with a run of a job you can get with the "download" button, or the listing in the monitoring tab? ... View more

I don't see anything documented on a built-in function to send emails for Job/Flow completion in Viya. SAS® Viya® 3.5 Administration: Jobs and Flows https://go.documentation.sas.com/doc/en/calcdc/3.5/caljobs/titlepage.htm You could build this into the flow though, i.e. a job that sends an email saying it failed if any of the flow points failed. ... View more

These variables are not present in Viya. I created a job with %put _all_ and executed it and found these variables set. I also didn't see any in the environment variables. normal: GLOBAL SYS_COMPUTE_DATA /opt/sas/viya/config/data/compsrv/default normal: GLOBAL SYS_COMPUTE_JOB_ID 64FC27DA-E57D-7E44-BAA3-187CE2220F8C normal: GLOBAL SYS_COMPUTE_SESSION_ID f027c925-2d8c-4d90-b8a0-8fd6e2769cc7-ses0000 normal: GLOBAL SYS_COMPUTE_SESSION_OWNER grwoot normal: GLOBAL SYS_JES_JOB_URI /jobExecution/jobs/5d52283b-028d-4eac-a2b7-1186d3af6b43 normal: GLOBAL _CONTEXTNAME SAS Job Execution compute context ... View more