Hi @SarathP,
it brings my attention the fact that METAUSER variable is empty (and I guess password would be empty too).
Filename=/sso/biconfig/940/Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/Monitoring/PIDs/autoload_VisualAn
alyticsLASR.pid,
Owner Name=lasradm,Group Name=kmsuser,
Access Permission=-rw-rw-rw-,
Last Modified=06Jun2018:15:00:03
I see you are running the job with the OS user lasradm (and it is part of a certain group).
I suppose lasradm is part of several groups (1 primary and several secondary groups) and kmuser is the primary group... but the "sas" group should be its primary OS group. Can you ensure this?
Also, I expect lasradm should be a SAS (metadata) user, or an account for a SAS (metadata) group. If not, please do so.
And a couple of counsiderations:
- If lasradm is a SAS user, then it should be able to run.
- If lasradm is an account in a SAS group (and you need the password written in this account), then, you would need to schedule the autoload not with lasradm, but with a SAS (metadata & OS) user that is part of this group. The reason is that group accounts in metadata are not allowed to log in to the SAS metadata, because of good reasons: which user would it be? Accounts in groups are more commonly named outbound connections.
As last tip: while not a best practice and not supported by SAS Technical Support (bear this in mind), you can always overrule the default connection to metadata in the Autoload script (SAS Code), by providing yours
options metapass="sasuser1"
metaport=8561
metarepository="Foundation"
metaserver="a123.us.company.com"
metauser="myuserid";
http://documentation.sas.com/?docsetId=lrmeta&docsetTarget=n03ph3v01d4e7en1n0v7wm8o3yiu.htm&docsetVe...
Then, you can control the OS user that runs towards the filesystem, and the SAS user that connects to the metadata folders, and control the permissions on the folders on each system (Linux and SAS)
Hope it helps.
