Logging remote transfers in EMS collector with CA XCOM for HP NonStop

Products

• XCOM Data Transport

Issue/Introduction

1. Remote transfers are logging messages into the $0 EMS Collector. Even if I configured into the DEFINES files the $X EMS Collector.  Any advice on this?

 $PROD VER1100 20> type defines

?tacl macro

SINK ~[#DEFINEDELETE =tcpip^host^file~]

add define =tcpip^host^file,file $system.ztcpip.hosts

SINK ~[#DEFINEDELETE =tcpip^process^name~]

add define =tcpip^process^name,file $ztc00

SINK ~[#DEFINEDELETE =tcpip^resolver^name~]

add define =tcpip^resolver^name,file $system.ztcpip.resconf

SINK ~[#DEFINEDELETE =XCOM62-PROGRAM~]

add define =XCOM62-PROGRAM, class map, file $prod.VER1100.XCOM62

SINK ~[#DEFINEDELETE =_EMS_COLLECTOR~]

add define =_EMS_COLLECTOR, class map, file $X0

SINK ~[#DEFINEDELETE =_EGEN_ADD_EVENT_TEXT~]

add define =_EGEN_ADD_EVENT_TEXT, class map, file $YES

 

2. Is there any way to see the transfer rate, for the transfers that are in execution?  XCOMQM is not showing that info:

 REQUEST   STAT   LOCAL ID           REMOTE ID       RECS      KBYTES    RETRIES     NEXT TIME

010719       A         xx.xx.xx.xx                                    0             0              0                  N/A

010806       A         xx.xx.xx.xx                                     0            0               0                 N/A

018679       A         xx.xx.xx.xx                                     0            0               0                 N/A

 

Environment

Release : 11.1

Component : CA XCOM Data Transport for HP NonStop

Resolution

Answer for both questions:

•  In order for REMOTELY initated PROTOCOL=TCPIP transfers to update a specific collector, you need to define that collector to the LISTNER when starting the process. For example:  
  
  

COMMENT *** Add defines to specify the location of the XCOM62 program
COMMENT *** the EMS collector process
COMMENT *** whether to include text in ems messages
SINK [#DEFINEDELETE =XCOM62-PROGRAM]
add define =XCOM62-PROGRAM, class map, file $dsmscm.xctndm11.xcom62
SINK [#DEFINEDELETE =_EMS_COLLECTOR]
add define =_EMS_COLLECTOR, class map, file $0
SINK [#DEFINEDELETE =_EGEN_ADD_EVENT_TEXT]
add define =_EGEN_ADD_EVENT_TEXT, class map, file $YES

== Start TCP/IP LISTNERs LSN0
DELETE DEFINE =TCPIP^PROCESS^NAME
CLEAR ALL
ADD DEFINE =TCPIP^PROCESS^NAME,CLASS MAP,FILE $ZTC0
PARAM          TCPIP^PROCESS^NAME        $ZTC0
PARAM ZTNT^TRANSPORT^PROCESS^NAME        $ZTC0

LISTNER /CPU 1,TERM $ZHOME,NAME $LSN1,PRI 150,NOWAIT,IN $ZHOME,OUT $ZHOME/0 $SYSTEM.ZTCPIP.PORTCONF

 

• The transfer rate, such as the RECS and KBYTES, will be shown if the transfer has turned on checkpoint. When you issue the XCOMQM command it will read the checkpoint file on Tandem(HP NonStop). Only if the transfer has checkpoint turned on will the command be able to gather that information that is written to the checkpoint file and display it. Any transfer without checkpoint will not be able to display the transfer rates. Now, you can get the rate information once the transfer has completed by using the SCANHIST command/utility. The SCANHIST will provide you with that information since it reads it from the XCOMHIST file.