Hi Andreas Please could you raise a ticket with SAS Technical Support - they may be able to assist and provide some advice about whether anything specific needs to be configured to access ESRI.    Thanks Susan   ... View more

Hey,    just saw your post as searching for the deletion of repositories.  Now that is documented under SAS Model Manager 15.2.  SAS Help Center: Delete a Repository   Best regards, Andreas ... View more

Hello,   Thanks a lot for your response.   All the limits in /etc/sysctl.conf has been modified to highest number to handle the load.   net.ipv4.tcp_max_syn_backlog: 4096 net.core.somaxconn:6000 net.core.netdev_max_backlog:3000 net.ipv4.tcp_keepalive_time=300 net.ipv4.tcp_keepalive_intvl=60 net.ipv4.tcp_keepalive_probes=20 net.ipv4.tcp_fin_timeout=30 net.core.netdev_max_backlog=3000   What surprises me is that, WebServer has already send ACK to Load balancer for close request. I could see in ssl webserver logs as POST /SASLogon/ClearPass entries.   Even my TCP dump output shows the same. But still my Webserver is not able to reuse/clear the unused sockets and it seems it is still waiting for something(Unknown).   We have 300 users and 6 JVMS with 16GB heap memory. I am not sure where this bottleneck exists.   Thanks & Regards, Sandeep ... View more

Hey,   you can use command 'bacct -u <username>' to see how many exited Jobs there are.   Another way is to search at the accounting files. Under your platform directory '../lsf/work/<clusterXX>/logdir' you should normaly find some files 'lsb.acct'. Maybe they have a numeric extension. These files hold a record per Job, so you can search for the user you are interested in.   I process these files with SAS so we have a history of the Grid jobs.   Greetings Andreas   bacct - command reference https://www.ibm.com/support/knowledgecenter/en/SSETD4_9.1.3/lsf_command_ref/bacct.1.html   lsb.acct - file reference https://www.ibm.com/support/knowledgecenter/en/SSETD4_9.1.3/lsf_config_ref/lsb.acct.5.html   ... View more

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 ... View more

Two versions of LSF will result in two resource managers thinking they have complete control over the machine's resources which will not be the case. Bot could think that a machine is good to launch a job on which will cause two jobs to go to the same machine. Not good workload management.   If your concern is putting a newer version of SAS on a machine without upgrading LSF, that is not a problem. SAS 9.4Mx comes with support for older versions of LSF, albeit possibly with reduced functionality. For example, 9.4M6 will support LSF 9.1.1.1 but ships with LSF 10.1.0.6 ... View more

Hello Luke, we are running also a Grid but with different version (SAS 9.4 M3 to M5) and LSF 9.1.3. 1. How Do you set the queue definition in the grid options set? I use here queue=”<target queue>” in the Grid options field. 2. It’s a question how you run the batch jobs. We are using the SASGSUB for batch jobs with the ability to control most of the options. Which scheduler will you use, Plattform Process Manager? 3. There is an option for making SAS Applications gridCapable if they are not by default, maybe this is an option? http://support.sas.com/documentation/cdl/en/gridref/67371/HTML/default/viewer.htm#n1inymfs0b7go2n147xdknz0ygpx.htm Also you could have a look to the ‘esub’ feature of LSF. It is described in ‘Administering Platform LSF’ under the topic ‘External Job Submission and Execution Controls’. It is an external script (bash) which can change a job’s Options. In your case you can switch the queues or something else based on the user or something else. We use it for the things not are possible under the standards (e.g. Connection Services, debug feature) for direct them to the grid. It is very handy option but could be a potential performance bottleneck if the script run’s long time. Best regards, Andreas ... View more