Usage Note 54987: Running a SAS® grid session in display mode from the SASGSUB command generates the error " Invalid ARM Agent name"
In SAS®, when you use the -GRIDRUNSASDMS option in the SASGSUB command to start an interactive SAS grid session in display mode, the session might fail. When this failure occurs, the following error message is generated in the log:
ERROR: Invalid ARM Agent name.
This problem happens when you have an APM_ARMSETUP macro in your appserver_autoexec_usermods.sas file that resides in the SAS-configuration-directoryn\SASApp directory. It is fine to have the macro in the SASApp directory when you run SAS or SAS grid sessions in batch. However, there are no ARM or APM measurements appropriately logged in interactive SAS. As a result, the SAS session fails when you start an interactive SAS grid session in display mode.
To avoid this problem, use the -NOAUTOEXEC option for the SASGSUB command's DMS run mode. To set this up automatically so that it only affects the DMS run mode of SASGSUB, you can add this option to your grid_usermods.cfg file.
For example, in UNIX operating environments, add or edit the following line in the grid_usermods.cfg file (in the SAS-configuration-directory/Levn/SASApp/GridServer directory) so that it includes the -NOAUTOEXEC option:
sasdmopts="-noautoexec"
In Windows operating environments, add or edit the following line in the grid_usermods.cfg file (in the SAS-configuration-directory\Levn\SASApp\GridServer folder) so that it includes the -NOAUTOEXEC option:
set SASDMSOPTS=-noautoexec
This addition or modification will be added only to the DMS run-mode code in the sasgrid script.
Operating System and Release Information
| SAS System | SAS Grid ManagerClient | Microsoft® Windows® for x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8 Pro x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Pro | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Pro 32-bit | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2008 R2 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2008 for x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 Datacenter | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 R2 Std | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 Std | 9.4 | | 9.4 TS1M0 | |
| Windows 7 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Windows 7 Professional x64 | 9.4 | | 9.4 TS1M0 | |
| 64-bit Enabled AIX | 9.4 | | 9.4 TS1M0 | |
| 64-bit Enabled Solaris | 9.4 | | 9.4 TS1M0 | |
| HP-UX IPF | 9.4 | | 9.4 TS1M0 | |
| Linux for x64 | 9.4 | | 9.4 TS1M0 | |
| Solaris for x64 | 9.4 | | 9.4 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2015-07-17 09:41:34 |
| Date Created: | 2015-01-13 09:24:43 |