About doug_sas

doug_sas · ‎04-07-2025

sas-folders and sas-types are now merged into the sas-file-store service/pod.

doug_sas · ‎03-28-2025

Look in the sas-batch-<hash> pod logs to see if there is a more detailed error.

doug_sas · ‎02-25-2025

So '-gridwork' should point to the grid shared directory and be the same from the client machine as it is from the grid machine. For example, SASGSUB has '-GRIDWORK /grid/shared/dir' means that SASGSUB will create a user directory & job directory at '/grid/shared/dir/<user>/<job>'. In the grid, the GridServer directory should have a grid.cfg that has SASGRIDSHARDIR also set to `/grid/shared/dir``. Is that correct? Have you logged onto a grid machine as the user and tried to run the command that LSF ran?

doug_sas · ‎02-25-2025

OK, I do not have enough information. What is the client platform? What is the server platform? Are you using a shared directory?

doug_sas · ‎02-25-2025

Does /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml exist? (I am assuming it does since it works for you) Is /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml a valid Log configuration file? (I am assuming it does since it works for you) Do users have access to the output log location (the grid shared directory)?

doug_sas · ‎02-07-2025

In the grid server metadata under the Options tab would be a field named 'Required Resources'. If that field has a value in it (like 'SASApp'), then one of the hosts in the LSF cluster has to have that resource name associated with it as a boolean resource in the lsf.cluster.<cluster-name> file.

doug_sas · ‎01-28-2025

The default ciphersuites in 9.4M8 prefer TLS 1.3 and its ciphersuites, but may fall back to TLS 1.2 with some very strong ciphersuites. It may be the ciphersuites, but it also may be a server certificate that is created with a unsupported hash since most ciphersuites offered require SHA256 or higher.

doug_sas · ‎12-16-2024

I use kc [-n <namespace>] delete jobs --field-selector='status.successful=1'

doug_sas · ‎03-12-2024

You could always play around in SAS OnDemand for Academics for free...

doug_sas · ‎03-11-2024

@woo wrote: Thank you. We are running with LSF and gsub. We don't have grid orchestrator. Any commands we can use? ps -ef cmd doesn't shows any process with connect spawner. We have multiple sasapp and for same app servers, we have obj. spawner definition defined. A spawner is not needed in a grid. LSF replaces the spawner as the daemon that starts CONNECT servers. Run the following code: %put rc=%sysfunc(grdsvc_enable(_ALL_,server=SASApp)); SIGNON T1; (this assumes you have a SAS Application Server context 'SASApp' that has a logical grid server defined) Once this runs, there should be a SAS process running on the grid in CONNECT server mode. Use the LSF 'bjobs' command from a terminal to see the job information. To make the server go away, run the following code: SIGNOFF T1; If you had a CONNECT spawner, the process name would be 'cntspawn' in 9.4

doug_sas · ‎03-11-2024

It is more accurate to say 'if SAS/CONNECT is configured' instead of installed. SAS/CONNECT can be installed, but if you did not have any SAS/CONNECT Server Configurations (or SAS/CONNECT configurations) defined in your plan file, a SAS/CONNECT spawner would not have been configured and Logical CONNECT servers may not have been configured either.

doug_sas · ‎03-11-2024

You track things started on the grid through the Grid provider's UI. SAS Workload Orchestrator serves up its own UI (no mid-tier needed) SAS has the SAS Grid Manager Module for SAS Environment Manager to serve up one for LSF (mid-tier required). Hadoop YARN has the UI for the YARN Resource Manager

doug_sas · ‎03-11-2024

SAS/CONNECT is a pre-requisite for any grid product so you should have it licensed, but unless your plan file specified CONNECT spawners to be running, they will not automatically be set configured by SDW. SAS Grid can start CONNECT servers by adding the grdsvc_enable statement before the SIGNON statement so a spawner is not needed. CONNECT servers started this way are often called 'grid servers', but are just CONNECT servers started by the grid provider (SWO, LSF, YARN).

doug_sas · ‎01-10-2024

Since your RSUBMITs are followed immediately by SIGNOFFs, the CONNECT servers may be torn down before your code completes. You need to add WAITFOR statements to cause the SIGNOFFs to wait until the RSUBMIT code blocks complete. I will agree with Patrick that having Tivoli just schedule all three jobs at the proper time seems like a easier approach.

doug_sas · ‎10-26-2023

If SEGVs occur on one specific machine, my guess would be that something is out of sync due to a incomplete or failed hotfix installation. Assuming all your machines are at the same version/maintenance level with the same hotfixes installed, compare the files in the <SASROOT>/SASFoundation/9.4 directory on a working machine to the ones on the failing machine to see if there are differences, specifically in shared library files *.so (UNIX/Linux) or *.dll (Windows). Also, the SEGVs may occur in multiple SAS programs, but only when executing something similar (a specific PROC or data step function). If you can find out what it was executing when SEGV occurred, maybe that would help narrow it down.

Online Status	Offline
Date Last Visited	‎11-18-2025 09:37 AM

Re: Help running sas-viya batch job submissions

Re: Help running sas-viya batch job submissions

Re: SASGSUB LOGCONFIGLOC Error

Re: SASGSUB LOGCONFIGLOC Error

Re: SASGSUB LOGCONFIGLOC Error

Re: Sas grid resource issue -validation issue

Re: howto detect which cipher ciphersuites workspace server uses on wi...

Re: Deleting completed kubernettes jobs in SAS Viya4 on AWS

Re: Licence SAS

Re: SAS/CONNECT and Grid

Restricting access to SAS Enterprise Manager to Authorized Users (Viya...

Re: Help running sas-viya batch job submissions

Re: Deleting completed kubernettes jobs in SAS Viya4 on AWS

Re: SAS/CONNECT and Grid

Re: SAS/CONNECT and Grid

Re: SAS/CONNECT and Grid

SAS® Viya® Workload Management: The Next Generation of Elasticity

Re: Help running sas-viya batch job submissions

Re: Help running sas-viya batch job submissions

Re: SASGSUB LOGCONFIGLOC Error

Re: SASGSUB LOGCONFIGLOC Error

Re: SASGSUB LOGCONFIGLOC Error

Re: Sas grid resource issue -validation issue

Re: howto detect which cipher ciphersuites workspace server uses on wi...

Re: Deleting completed kubernettes jobs in SAS Viya4 on AWS

Re: Licence SAS

Re: SAS/CONNECT and Grid

Re: SAS/CONNECT and Grid

Re: SAS/CONNECT and Grid

Re: SAS/CONNECT and Grid

Re: while sas code running in batch/Scheduler can we submit same sas c...

Re: Recursive Segmentation Violations - system exiting error while ex...