About CHandberg

CHandberg · ‎05-29-2024

Does the job exit with an error or a warning? If it's an error i'll agree with the other suggestions to fix the error by its source. If it' a warning, and you want to allow your batch-flows to complete with a warning, then you can edit the sasbatch.bat file. \SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat Just remove the REM in the last four lines as stated in the comments in the file. This is on a windows platform but I assume that you can do something similar if it's another platform.

CHandberg · ‎08-04-2023

@thesasuserYes, last week we installed the hotfix mentioned below, and it seems to have solved the issue (SAS Support had told us not to hotfix anything while they were troubleshooting) https://support.sas.com/kb/69/520.html Problem Note 69520: SAS® Studio V logon (SAS® Viya® 3.5) fails and produces the error "Compute Server .... terminated unexpectedly" We also had another issue that the servername was registered in the Windows DNS with uppercase, and the linuxserver was named in lowercase... it caused a lot of trouble that disturbed the troubleshooting.

CHandberg · ‎02-10-2023

Hi @thesasuser No, the track is still in progress... I don't know if you have told your support team about I have the same issue on Linux, but you can refer to my track no SAS 7613719935 if you want to.

CHandberg · ‎01-27-2023

I have the same issue on a SAS Viya 3.5 on a Linux server and I'm gathering logs, etc to Global Support as we speak. I'll let you know if we get a break-through...

CHandberg · ‎05-01-2022

It could be because you use Integrated Windows Authenticaton in the connection profile. Uncheck IWA and type username and password. It is important that you use the domain in the username eg mydomain\myuser. The reason is that you “loose the domain” when you “jump to the next server” using UNC-path with IWA.

CHandberg · ‎03-21-2019

Hi All Can anyone tell me why and when the work-directory changes, when I use e.g. workspace-server? In my autoexec I create a dataset and place it in work. The dataset appears in "Z:\saswork\_TD<ProcessID>_Servername_\". All is good. When I try to use it in DI Studio or Enterprise Guide, it is missing because work has changed to "Z:\saswork\_TD<ProcessID>_Servername_\Prc2\". When I use the DisplayManager all is good and Prc2 doesn't appear. It is the same processID, so the path must change between the execution of the autoexec and the actual program. Can someone please enlighten me what is going on and preferably how to change it? Thanks in advance! /Christian OS:Windows SAS 9.4 M4

CHandberg · ‎10-25-2018

The solution is here: https://communities.sas.com/t5/Administration-and-Deployment/SAS-Scheduler-ID-running-X-CMD/m-p/429059#M11968 Edit: I didn't remember it was a longer thread. Sorry... The solution is to edit your "E:\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat" and remove the REM-statements in the end of the script... /Christian

CHandberg · ‎09-28-2018

I think you'll find this code useful. It was one of my first "Metadata-reports" so it probably could be made more elegant, but it'll work. I'll recommend you to use METABROWSE in the DisplayManager to go explore your Metadata OR use MetaCoda's tools. Good Luck... /C

CHandberg · ‎04-04-2018

Unfortunately SAS DI sometimes generate code that make Warnings you can't do anything about. So to make your flow complete you have to do the "workaround".

CHandberg · ‎04-04-2018

Hi @Helannivas I think you should look at the sasbatch.bat -file Eg. :"E:\SAS\Config\Lev1\SasApp\BatchServer\sasbatch.bat" As default it returns RC=1 if there is warnings in the sas-program. This will PPM interpret as an error. To make it accept warnings and return 0, you should remove the REM statements in the last 4 lines of the sasbatch.bat-file set rc=%ERRORLEVEL% if %rc%==1 goto makenormalexit exit /b %rc% :makenormalexit exit /b 0 You should consider the arguments in this discussion: SAS-Scheduler-ID-running-X-CMD

CHandberg · ‎04-04-2018

Hi Paul I'll definitely try that as a solution. Until now I've been able to just use the Datastep Metadata Functions, but it seems that I have to explore the possibilities in using Proc Metadata. Thank you for the answer!

CHandberg · ‎03-22-2018

I was affraid that this was the answer. Even the Metabrowser in DisplayManager are not able to display the value, so I think SAS has a little issue 🙂 Thanks for the fast reply and thank you for the reference to the Java Metadata Interface.

CHandberg · ‎03-22-2018

Hi All I need to read the 'DefaultValue'-attribute from the DiagramXml-property. (XML that control the formatting of the job in DI Studio) Unfortunately the content of the attribute is more than 32767 chraracters long so i'm not able to read the full content. spnrc = metadata_getattr(spuri,'DefaultValue',Jobxml); Is there a way to read more than 32767 chars into a sas variable, use char functions on it and write it back?

CHandberg · ‎02-27-2018

Hi Ravi I think it might be a security issue. I assume that you use ACTs on your sasapp2 applicationserver. Are your user member of the correct groups so he can read metadata on SASAPP2? Otherwise he can't see it if you use "Public and SASUSER Denied ACT" on the appservercontext. /Christian

CHandberg · ‎02-09-2018

Hi... Go to this file \SAS\Config\Lev1\SASMeta\MetadataServer\adminUsers.txt and insert your user. Restart the metadataserver and you will be able to log on to SMC and grant the permissions needed. Remember to remove your user from the file (and restart the metadataserver) when you're done...

Online Status	Offline
Date Last Visited	‎07-03-2024 11:41 AM

Re: SAS LSF job re-run if failed

Re: Creation of compute server session fails in SAS Viya

Re: Creation of compute server session fails in SAS Viya

Re: Creation of compute server session fails in SAS Viya

Re: ERROR: User does not have appropriate authorization level ...

SAS Work-directory changes during execution

Re: SAS 9.4 with lsf configuration

Re: List of Jobs, Flows & dependencies between

Re: Platform Process Manager issue.

Re: Platform Process Manager issue.

Juletip #21 - Proc SQL, other use than join

Re: DLR Kredit: Utilizing SAS Global Forum for company and professiona...

Re: Platform Process Manager issue.

Re: How do I read metadata attributes containing more than 32767 chars...

Re: How do I read metadata attributes containing more than 32767 chars...

Re: ERROR: User does not have appropriate authorization level ...

Cannot Execute stp via Proc stp on specific Appservercontext

Re: SAS 9.4 with lsf configuration

Re: List of Jobs, Flows & dependencies between

Re: SAS Scheduler ID running X CMD

Re: SAS LSF job re-run if failed

Re: Creation of compute server session fails in SAS Viya

Re: Creation of compute server session fails in SAS Viya

Re: Creation of compute server session fails in SAS Viya

Re: ERROR: User does not have appropriate authorization level ...

SAS Work-directory changes during execution

Re: SAS 9.4 with lsf configuration

Re: List of Jobs, Flows & dependencies between

Re: Platform Process Manager issue.

Re: Platform Process Manager issue.

Re: How do I read metadata attributes containing more than 32767 chars...

Re: How do I read metadata attributes containing more than 32767 chars...

How do I read metadata attributes containing more than 32767 chars?

Re: SAS Excel issue

Re: Management Console, No unrestricted users

SAS Community Nordic