About doug_sas

doug_sas · ‎11-14-2019

The host status 'closed_busy' usually indicates that one of the host's load indices has exceeded the amount specified in the lsf.cluster.<cluster_name> file in the LSF configuration directory. An example would be Begin Host HOSTNAME model type server r1m mem swp RESOURCES #Keywords apple Sparc5S SUNSOL 1 3.5 1 2 (sparc bsd) #Example In this example, if the 'r1m' load index exceeded 3.5 or the available physical memory used went below 1MB the host 'apple' would show as closed_busy. Load index definitions can be found in the LSF Administration Reference (such as https://www.ibm.com/support/knowledgecenter/en/SSWRJV_10.1.0/lsf_admin/load_indices.html)

doug_sas · ‎08-13-2019

libccme_* files should have 555 since they are read-only shared libraries. Logs can have 770.

doug_sas · ‎08-13-2019

The libccme_* libraries can have all write bits turned off. Install logs generally only need the write bit set for the user (i.e., the SAS install user or in this case the LSF/PM installer). The LSF/PM operational logs need to have the user write bit set for the user running the daemon. Sometimes that is root and other times it is the primary grid administrator.

doug_sas · ‎07-25-2019

You still need the Viya root certificate for the SSL handshake to work properly. You will get farther, but SAS will complain that the certificate is not valid.

doug_sas · ‎07-25-2019

By default, the CONNECT spawner in Viya has SSL/TLS enabled. You need to Enable the SAS/CONNECT client in 9.4 to use TLS encryption Get the Viya root certificate added to the client's certificate store. You may want to look in the Encryption in SAS Viya 3.4 (here) or refer to this other post (here) to see what you need to do.

doug_sas · ‎07-19-2019

Lots of things could cause this problem. DNS changes such that the dpds1335a cannot resolve dpds1336a Firewall changes on dpds1335a that prevents dpds1336a from connecting Network equipment breakdown. LIM is hung on dpds1335a License has expired. So you can do the following: Make sure LIM is running and responding on dpds1335a. Run 'lsid' on dpds1335a Make sure you can ping dpds1335a from dpds1336a. You could also try to telnet from dpds1336a to dpds1335a on the LIM port.

doug_sas · ‎07-08-2019

You can buy SAS Job Flow Scheduler as a single machine scheduler.

doug_sas · ‎06-18-2019

The detailed message 'The machine name cannot be resolved to an IP address" means it cannot resolve the metadata server host name to an address. This may be because you are using short host name and the domain suffix list your machine has does not include the domain for where the metadata server is located. Try connecting using the full host name including domain.

doug_sas · ‎06-03-2019

What SAS Grid Manager product are you using and what version? If your grid is using SAS Workload Orchestrator, there is the SAS Workload Orchestrator Administration Utility or the SAS Workload Orchestrator GUI that may be able to provide that information. If your grid is using Platform Suite for SAS, there are command line utilities (like BJOBS) and GUIs (like SAS Grid Manager Module for SAS Environment Manager or RTM) that may be able to help.

doug_sas · ‎05-06-2019

There are a couple ways of doing this in SAS Workload Orchestrator both using time-based configuration. You can change the queue configuration based on time to change the list of hosts that can be used for a certain period of time. You can change the host type configuration based on time to set the maximum number of jobs on a host type to 0 during a certain period of time. Create one host type for hosts you want to keep open and one host type for hosts that you want to close. SAS Workload Orchestrator has no facility to kill jobs that are still running outside of a time window. If you are using LSF, you could change the queue configuration to eliminate hosts for the period of time you want. LSF also has DISPATCH_WINDOWs and RUN_WINDOWs on queues and DISPATCH_WINDOWs on hosts that regulate when jobs can be scheduled (DISPATCH_WINDOW) or run (RUN_WINDOW).

doug_sas · ‎05-06-2019

In addition to what @JuanS_OCS said, LSF has in it 'resource connectors' that allow LSF to start up instances on various providers. SAS currently supports AWS instances, but the latest LSF has support for others. You also need a data storage strategy. For example, will it be SAS datasets? RDBMS? Hadoop? S3-like containers? Each has good & bad attributes (cost, speed, access). Also, if all instances went away, where would the data be stored for when the instances come back up? Just some things to think about.

doug_sas · ‎05-02-2019

What issues are you seeing? There was a fix for a memory leak but I have not heard of any other Windows specific problems. The latest hotfix deals with changes required to support constrained delegation on Windows. There will be other hotfixes to other components for constrained delegation coming in the future.

doug_sas · ‎03-22-2019

You are running into 2 problems: The usage of bsub is "bsub <command_to_run>". When you run "bsub test.sas", you are trying to execute the command "test.sas" which is not a command. You would need something like "bsub <path>/<to>/<SASHOME>/sas test.sas". The grid does not know where test.sas is located. You need to place the SAS program somewhere that every grid node can access and then use the full path. The command then becomes "bsub <path>/<to>/<sas>/sas <path>/<to>/<shared_directory>/test.sas" Or you can just use SASGSUB which knows how to run SAS programs on the grid and will transport the SAS program to and from the grid. You would run "sasgsub -gridsubmitpgm test.sas" If SASGSUB is installed, it is located in <config>/<LevX>/Applications/SASGridManagerClientUtility/9.4/sasgsub

doug_sas · ‎03-21-2019

My response is the same. 1) For 'sas test.sas' you have to provide a new 'sas' command that processes the job on the grid using sasgsub. 2) For 'bsub test.sas' nothing will work. The format of the bsub command is 'bsub <cmd>'. Since 'test.sas' is not a command, nothing will be done. Also, using Platform Suite for SAS, bsub jobs only run for 30 seconds.

doug_sas · ‎03-21-2019

Other users have created a script named 'sas' that calls the SAS Grid Manager Command Line Utility (sasgsub) under the covers to submit the job to the grid and wait for it to process the file. The user types 'sas test.sas' and a grid job is created, the program is run in batch in the grid, and the results returned. This works good unless they know how to get to the real SAS. Once they figure that out they will use it. 'bsub test.sas' will submit a job to run the program 'test.sas'. Not sure what will happen there - probably fail since 'test.sas' is not an executable program.

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: SAS and LSF memory optimization

Re: Rapid 7 Vulnerability for world writable files

Re: Rapid 7 Vulnerability for world writable files

Re: SAS connect fails to connect to SAS Viya

Re: SAS connect fails to connect to SAS Viya

Re: sas LSF LIM ERROR

Re: SAS Grid Manager in SAS 9.4M6

Re: sas Applications connection issue

Re: Finding process id for each Grid nodes

Re: SAS Grid on Cloud

Re: SAS Grid on Cloud

Re: Has anyone implemented SAS Workload Orchestrator in a Windows envi...

Re: Grid job distribution

Re: Grid job distribution

Re: Grid job distribution