Something is up with our SAS Grid (9.4M3).  It is a new installation and even a simple "bsub sleep 20" request remains in PEND status.   bjobs -l 768   PENDING REASONS: New job is waiting for scheduling;   SCHEDULING PARAMETERS: r15s r1m r15m ut pg io ls it tmp swp mem loadSched - - - - - - - - - - - loadStop - - - - - - - - - - - RESOURCE REQUIREMENT DETAILS: Combined: - Effective: -   Is there an LSF command line command that will give detailed information on why the job is not being dispatche, like the criteria LSF is using to keep the job in the pending status? ... View more

In PC SAS you can run the DM command to open a Document viewer that shows up as an additional tab along with the Results and Explorer.  My question:  is there a way to get a hierarchical view of an ODS Document in SAS Studio? ... View more

I have a couple of questions regarding SAS Studio timing out.   What is the default inactivity time-out value for Enterprise SAS Studio?   I know the following is not the best use case of SAS Studio, but it is all I have for now.    If I submit a long running SAS program (5+ hours) from SAS Studio, will SAS Studio time-out on me?  If it does time-out then will the SAS session running my long running program be killed or will it continue to run until it completes? ... View more

In PC SAS I used %window & %display to display prompts and messages.  Is there a way to do the same from programs running in SAS Studio? ... View more

We have a full LSF license and SAS grid manager licensed but we are having an issue after the install & config with validating the SAS Grid Server.   Questions: I've heard, but want to confirm that SAS grid manager can work correctly with a Full LSF License (license for LSF from IBM for a large cluster).  Can someone confirm this? We installed SAS grid manager and the grid control server is on a host (Linux Server) that has LSF installed as an LSF Client.  When we try to validate the grid server from SAS management console it fails. The log contains these lines (cleaned up):          %put rc=%sysfunc(grdsvc_enable(_all_,server="SASApp"));signon t1; rsubmit;proc options;run;endrsubmit;signoff _all_;          rc=0          NOTE: Remote session ID T1 will use the grid service _ALL_.          NOTE: Remote signon to T1 commencing (SAS Release 9.04.01M3P062415).          ERROR: PROVIDER(Platform): LIM is down; try later          ERROR: Cannot initialize the grid provider module.          ERROR: A communication subsystem partner link setup request failure has occurred.          ERROR: Cannot initialize the grid provider module.          ERROR: Remote signon to T1 canceled.          ERROR: Invalid or unspecified remote session ID. Set OPTIONS REMOTE=session_id.          ...     I know LIM is up on the servers.    I will try running a bsub sleep from that host later today, but meanwhile does anyone have any suggestions?   Thanks,   Bryan ... View more