lgtst: Check Active Instances & existing Logon Groups via OS Level

Test program lgtst is used to check the active instances of your SAP System and check existing logon groups directly at operating system level. In SAP Systems you can do this using transactions SM51 (Overview of SAP Application Servers), SMMS (Message Server Monitor) or SMLG.

The prerequisite is a unique message server address consisting of the message server host name and the message server port. With the message server port you have to be particularly careful that the port number (e.g. 3600/tcp, see e.g. /etc/services) assigned to the port name (sapms, SID=SAP-System-ID) has exactly the same value on all participating hosts. For this reason these details should be defined in the global profile DEFAULT.PFL:

• rdisp/mshost = HOSTNAME of Message Server
• rdisp/msserv = sapmsSID

When you call program lgtst without any parameters, you get a list of call parameters (mandatory and optional):

> lgtst

Test Program for LG-Layer (SAP Login Info), Version 5, Dec 21 2009

required options
  pf=name           : profile name or
  name=SID          : system sid or
  -H mshost         : hostname of message server and
  -S msserv         : service-name / number of message server

additional options
  -T tracefile      : name of trace file     (default dev_lg)
  -W waittime       : for net-calls          (default 10000 millisecs)
  -D [1|2|3]        : display server and/or logon groups
  -N [1|2|3]        : display sncnames for server and/or logon groups
          1         : display both
          2         : display only server
          3         : display only logon groups
   ( default is -D 1 )
  -E [0|1]          : with SAP J2EE Info
  -G group          : group logon data
  -X group          : group logon detail data
   [-L 1]             group logon data with sncname
  -A name           : sncname of application server via name
  -P ip,port        : sncname of application server via ipadr/port

  -C n              : do it n times
  -Y n              : delay n millisecs for each loop

To test the message server connection you should set the SAP profile parameters specified in the prerequisites. If you then enter:

lgtst -H HOSTNAME-Message-Server -S sapmsSID

you get a list divided into two parts:

• List of active SAP server instances (with services)
• List of available logon groups (with default instances)

 lgtst -S sapmsPRD -H ci12
using trcfile: dev_lg

list of reachable application servers
-------------------------------------
[app_PRD_10] [app10] [192.168.10.10] [sapdp10] [3210] [DIA UPD BTC SPO ICM ]
[app_PRD_11] [app11] [192.168.10.11] [sapdp11] [3211] [DIA UPD BTC SPO ICM ]
[ci_PRD_12] [ci12] [192.168.10.12] [sapdp12] [3212] [DIA UPD ENQ BTC SPO UP2 ICM ]

list of selectable logpn groups with favorites
------------------------------------------------
[CUSTOMER] [192.168.10.11] [3211] [620]
[SPACE] [192.168.10.10] [3210] [620]
[WEB] [192.168.10.10] [3210] [620]