I did RSVP -Yes , but it doesn't seem to be coming through to the 'Going' above ... View more

@huntdoug has given the correct answer. You can either install / configure the auditing and logging / EM service architecture - which records much more detailed information, or you can look at the metadata server log for basic connection info.   I had to do this for someone just a few days ago and they didn't have the the full auditing and logging installed, so I analysed the metadata server log. using this simple program - it may not be perfect, so check your results:   *reads in metadata server log and attempts to determine who connected.; filename mdlog "/Path to the metadata server log/sasmeta......log" ; data connections; length userid $32; format time time. date date.; infile mdlog ; input @1 date yymmdd10. @12 time time8.; userid=scan(_infile_,4,':'); userid=strip(scan(userid,1,'-')); /* Sample data 2021-03-29T23:43:35,642 INFO [133178522] :sastrust@saspw - Request made to cluster SASMeta - Logical Metadata Server (A5L3816M.AX000001). 2021-03-29T23:43:35,642 INFO [133178522] :sastrust@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A5L3816M.AX000001) to server SASMeta - Metadata Server (A5L3816M.AZ000001) at sasmeta.xyz.co.nz:8561. 2021-03-29T23:43:35,652 INFO [133178526] :sasevs@saspw - New client connection (6181722) accepted from server port 8561 for SAS token user sasevs@saspw. Encryption level is Everything using encryption algorithm AES. Peer IP address and port are [10.123.456.789]:56444 for APPNAME=/SASAuthorizationServices - Web Infra Platform Identity Services 9.4. */ if userid not in('svc_sas_prod','sasevs@saspw','sasadm@saspw','sastrust@saspw','svc_lasradm_prod'); run; *unique users; proc sort data=connections out=uniqueusers nodupkey; by userid; run;   And I only had to report on connections for one week, so I just ran this 7 times to analyse the 7 daily metadata log files, so clearly this could be enhanced to automate processing of a range of logs. Unfortunately, it only reports who connected to the SAS System, not what they did.   To implement more comprehensive auditing and logging can be a reasonable amount of work to set up. If you set up workspace server logging (for example, every EG session has the log saved to disk), this can consume lots of disk space, so you need to consider retention periods, automated archiving etc. Typically a dedicated log disk volume is set up of maybe 100 or 200GB in size just to store logs. Auditing and logging seems to be a requirement more and more these days. I've had to set this up for a number of government sites to comply with increased security requirements.             ... View more

Hi, I think rajdeep has pointed you in the direction of the information you are after.   I'll just add a general comment to your question which I interpret as asking is there a way of getting schedule etc information from Metadata?   I haven't attempted to get Job/Deployed Job/Flow etc related metadata, but I have read and written other metadata objects: Yes, you can read and write metadata programmatically.  I wouldn't say it's easy and it takes a bit to get your head around the metadata model. If you are wanting to access metadata objects, take a look at these documents: Metadata Model Reference: https://support.sas.com/documentation/cdl/en/omamodref/67417/HTML/default/viewer.htm#titlepage.htm   SAS Language interfaces to metadata https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lrmeta/titlepage.htm   Mark ... View more

So I interpret the question as: You've got some data in a CAS lib that you can see in SAS Viya. You now want to use SAS Studio ("Develop SAS Code") to access the data in that CAS Library.   That's quite easy: You need to use a libname statement using the CAS engine like this:   * here, abc is the libref, cas is the CAS engine and you specify the library name (exactly as defined in CAS) in caslib=; Libname abc cas caslib='XYZ';   *the following will list the tables that are in the CAS library proc datasets lib=abc; quit; *assuming you have a table called sales in the caslib, then you can use it in code like this: data MaySales;  set abc.sales;  where Month='May'; run;   I've made some assumptions with the above code, particularly the libname statement. I assume that you are using SAS StudioV that is in the same environment as SAS Viya. That way you don't have to specify CAS connection information. If you are using SASStudio or other SAS Coding tools like Enterprise Guide that are separate from the SAS Viya environment then you will have to specify the cashost, port and maybe authentication.   HTH   Mark       ... View more

Hi, This is a common issue when using data that was created on one server on a different server. Often experienced when migrating from an older SAS environment to a new one, or a Windows server to a Unix server   Have a read of the documentation here: https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/movefile/n06qan4j3ffr6fn11bs4q11r8r56.htm There's a section that discusses your error along with solutions.   You mention that you need to convert multiple datasets. I can't offer you code solutions, but I can reflect on how I went about a similar issue at a site where I carried out a migration: They had I think about 100,000 or so datasets that needed converting. The datasets were strewn through out many directories, I think about 30,000 directories if I remember corrrectly. The approach I took was that I wrote a SAS program that 'spidered' a data volume, that is, it examined each directory, starting at the highest level  and then each subdirectory recursively. It examined every SAS dataset as well as other SAS artifacts such as catalogs to see if they needed to be converted to UTF-8. It also checked for things like password protection, corrupt datasets etc. Anyway, out of this, it produced a big 'shopping list' of SAS datasets that needed conversion, along with the path name   Part two of the process was a SAS program that used the 'shopping list' to assign libnames and execute code to read the dataset and convert it to UTF8. It did this using methods discussed in the documentation link above.   I hope that's helpful information. ... View more

At a number of sites I've loaded data into CAS using Proc CASutil from a SAS 9.4 DI server. I've found that from time to time there are errors on the CAS side. While these appear in the SAS log they don't seem to throw an error condition at the SAS 9 side of things.   To work around this, I did exactly what you suggest "I'm thinking that I may have to parse the individual log files...but how?"   How? Well that's not too hard: Build a filename with a timestamp. This will become the log filename At the start of your job, assign the filename to a fileref Next use proc printto to redirect your log to the log file Do your processing At the completion of the processing, redirect the log back i.e. proc printto log=log; Parse the log...along the lines of:   *parse temp log; data parselog; infile CASLog eof = Done; input; put 'CAS Processing Log:' _Infile_ ;     if scan(left(_Infile_),1,':')='ERROR' then do; *error processing; put "xxxxxxxxxxxxxxxxxxxxxxxx"; end; run;   You could implement something similar in Viya: 1) build and test your job code in SAS StudioV, incorporate the log processing / error processing - you might want to code in an email step to alert you if you detect an error in the log. 2) create a job to call the code 3) schedule in Environment Manager   Mark   ... View more

Interesting article. Only two weeks ago I had to come up with some solutions to batch submit jobs in Viya 3.5 from Control-M as part of the DI ETL processing and subsequent load into CAS.   I came up with two solutions. - The first being a shell script to run a SPRE session in batch as described in the article above. - The second more interesting one was to use use REST calls. I came up with a working proof of concept where by from a SAS9.4 DI Server using proc http, I made two calls:1) obtain an auth token : https://xxxx.xxxx.x.nz/SASLogon/oauth/token, then followed this with a call to the SAS Viya job execution service. I believe that Control-M can make REST calls (not tested), but otherwise Control-M could be used to call a SAS9.4 job and SAS9.4 can make the REST calls.   Part of the code for the second REST call to kick off the job: proc http      url="&viyahostname/jobExecution/jobs"         method="POST"         in=json_in         out=out;         Headers "Content-Type"= "application/vnd.sas.job.execution.job.request+json" 'Accept'='application/vnd.sas.job.execution.job+json' 'Authorization'="Bearer &access_token" ; run;   Job information and code is passed in the json_in file and included code, as well as parameters that you could pass. These parameters would appear as macro variables in the SAS session for example (json fragment):         "testparm": "test456",         "testparmB": "test789"   in the SAS Session - shows the parameters appearing as macro variables: 18  +%put _all_; GLOBAL DTSTAMP 2021_03_18T22_53_23 GLOBAL SYS_COMPUTE_DATA /opt/sas/viya/config/data/compsrv/default GLOBAL SYS_COMPUTE_JOB_ID 89EF29E8-ECCD-6C48-802D-D2146A658913 GLOBAL SYS_COMPUTE_SESSION_ID 259db425-7750-4c90-8d25-f47e5cb8fcf8-ses0000 GLOBAL SYS_COMPUTE_SESSION_OWNER mark GLOBAL SYS_JES_JOB_URI %nrstr(/jobExecution/jobs/be57e9e9-e7b1-4370-8e54-14297f3997af) GLOBAL TESTPARM test456 GLOBAL TESTPARMB test789 GLOBAL _CASPORT_ 5570 GLOBAL _CONTEXTNAME %nrstr   I kept the SAS code in the job definition simple - being a couple of statements to do a %include. The included .sas file could then contain more extensive code - in this case CAS table load, save, promote etc. code.   The job would display in the Environment Manager - Jobs screen. Like this one (from our Viya 3.4 AWS playpen):   This REST call solution meant that the batch jobs could be called from SAS9 and therefore be made into a SAS9 DI Job and be scheduled using the usual SAS9 scheduling tools. In this particular application, the existing SAS DI environment was an older - pre M5 release which meant that integration with Viya was limited. We couldn't use proc casutil or proc cas, for example to load data into CAS as part of the nightly ETL processing. Using proc http and REST calls meant that we could kick off a job on Viya that would load data into CAS after the nightly ETL batch had completed.   To develop this, I used simple CURL statements and Postman to test the REST calls   Mark ... View more

Casey -Thanks for that! I made the statement that the updates don't work with a proxy after contacting SAS tech support. They told me it was not possible. I'll try out the settings in the SASNote.   Mark ... View more