topic Re: DTSS messages in Operating System - OpenVMS

DTSS messages

David Lings — Sun, 26 Jun 2005 08:38:12 GMT

How can I disable the hundreds/thousands of DTSS error messages been sent to the OpenVMS operator's log file:

Message from user SYSTEM on PROD20
DTE Class=xot-class-0,
Reference Time=2005-06-26-12:24:24.932+01:00I0.046,
Data Octets Received=984,
Data Octets Sent=2662,
PDUs Received=20,
PDUs Sent=29,
Segments Received=30,
Segments Sent=50
eventUid 47121E18-E64F-11D9-B958-50524F443230
entityUid 63A9345F-E2F6-11D9-80B4-AA000400C928
streamUid 67FE8668-E2F6-11D9-80CF-AA000400C928

Re: DTSS messages

Veli Körkkö — Sun, 26 Jun 2005 10:12:53 GMT

There must be more. This is actually latter part of said message. I would have expected something like

%%%%%%%%%%% OPCOM 26-JUN-2005 18:07:10.32 %%%%%%%%%%%
Message from user SYSTEM on DELPRC
Event: Port Terminated from: Node LOCAL:.DELPRC X25 Access,
at: 2005-06-26-18:07:10.324+03:00I0.244
Client=Generic Client User Process "Pid=216004B6 Device=NWA7:",
Type=Switched,
State=Cleared,
Call Direction=Outgoing,
Call Association=X25 Access Template X29Login,
Target DTE Address=1,
Calling DTE Address=1024,
Protocol Identifier='01000000'H,
Channel=4095,
Outgoing Packet Size=128,
Incoming Packet Size=128,
Outgoing Window Size=2,
Incoming Window Size=2,
Reverse Charging=False,
Redirect Reason=Not Redirected,
Fast Select=Not Specified,
DTE=X25 Protocol DTE dte-0,
DTE Class=DTE-0,

%%%%%%%%%%% OPCOM 26-JUN-2005 18:07:10.33 %%%%%%%%%%%
Message from user SYSTEM on DELPRC
Reference Time=2005-06-26-18:07:02.513+03:00I0.243,
Data Octets Received=490,
Data Octets Sent=105,
PDUs Received=33,
PDUs Sent=31,
Segments Received=37,
Segments Sent=31
eventUid 1D66D3C9-E66D-11D9-8C2B-44454C505243
entityUid A0F224F6-D930-11D9-8092-AA00040016CB
streamUid A5BCC659-D930-11D9-80BC-AA00040016CB

above segment of two OPCOM messages was due to termination of single $SET HOST/X29 session and I would block the said messages using

$ mc ncl bl e d o s * g f ((node,X25 access),Port terminated)

Long version of command is

$ mcr ncl block event dispatcher outbound stream * global filter ((node,x25 access),Port terminated)

I would copy
sys$manager:net$event_local.template to sys$common:[sysmgr]net$event_local.ncl and edit essentially above command with said ncl file and execute

$ mcr ncl @sys$manager:net$event_local

This said event is by no means related to DTSS but rather to X25 component.

_veli

Re: DTSS messages

comarow — Sun, 26 Jun 2005 10:19:50 GMT

A DTSS server send out the correct time. You don't have one.

Re: DTSS messages

Veli Körkkö — Sun, 26 Jun 2005 10:41:53 GMT

well, as I said already, THIS IS NOT DTSS MESSAGE. The key thing on the OPCOM message
is

" DTE Class=xot-class-0, "

This clearly tells me that we are dealing with X25 stuff.

And since X25 events are a bit long, they tend to get split to two OPCOM messages and here we are shown the LATTER OPCOM message containing somewhat less useful information. In my earlier reply the posted messages are from an actual

$ SET HOST/X29 dte-0.1

and after subsequent logout.

_veli

_veli

Re: DTSS messages

David Lings — Mon, 27 Jun 2005 10:01:43 GMT

Thankyou,

yes you are correct :

these OPCOM messages appear in pairs.
And you correctly noted the first OPCOM message does inform that the message is to do with X.25 not DTSS.

Are these messages the equivalent of following UCX (TCPIP for OpenVMS) TELNET messages and can therefore be removed and ignored ?

%%%%%%%%%%% OPCOM 26-MAY-2005 22:55:42.54 %%%%%%%%%%% (from node PROD11 at 26-MAY-2005 22:55:42.54)
Message from user TCPIP TELNET on PROD11
TELNET Logout Request from Remote Host: 192.168.181.62 Port: 4710

********************************************
********************************************

My original complete paired X25 OPCOM messages:
-------------------------------

%%%%%%%%%%% OPCOM 27-JUN-2005 15:40:13.40 %%%%%%%%%%%
Message from user SYSTEM on PROD20
Event: Port Terminated from: Node LOCAL:.PROD20 X25 Access,
at: 2005-06-27-15:40:13.399+01:00I0.061
Client=Generic Client User Process "Pid=20801F16 Device=NWA1160:",
Type=Switched,
State=Cleared,
Call Direction=Incoming,
Call Association=X25 Access Filter OP_COM_X25_RUN,
Target DTE Address=5500090001,
Calling DTE Address=4410610001,
Protocol Identifier='00000000'H,
Channel=4032,
Outgoing Packet Size=128,
Incoming Packet Size=128,
Outgoing Window Size=2,
Incoming Window Size=2,
Reverse Charging=False,
Redirect Reason=Not Redirected,
Fast Select=Not Specified,
DTE=X25 Protocol DTE dte-4,

%%%%%%%%%%% OPCOM 27-JUN-2005 15:40:13.40 %%%%%%%%%%%
Message from user SYSTEM on PROD20
DTE Class=xot-class-0,
Reference Time=2005-06-27-15:39:01.744+01:00I0.054,
Data Octets Received=0,
Data Octets Sent=0,
PDUs Received=0,
PDUs Sent=0,
Segments Received=0,
Segments Sent=0
eventUid C0847FEA-E721-11D9-B865-50524F443230
entityUid 63A9345F-E2F6-11D9-80B4-AA000400C928
streamUid 67FE8668-E2F6-11D9-80CF-AA000400C928

Re: DTSS messages

Ian Miller. — Mon, 27 Jun 2005 10:34:10 GMT

If thats a normal end of call message for your X.25 network then you could block those messages. For examples of blocking messages sent via the DECnet/Plus event logger see SYS$MANAGER:NET$EVENT_LOCAL.TEMPLATE

Re: DTSS messages

Veli Körkkö — Mon, 27 Jun 2005 13:05:57 GMT

If you wish to get rid of those messages, the way to go is (as I said already) the "simple" ncl command:

$ mcr ncl block event dispatcher outbound stream * global filter ((node,x25 access),Port terminated)

I would copy

sys$manager:net$event_local.template

to

sys$common:[sysmgr]net$event_local.ncl

and edit essentially above command to said ncl file and execute

$ mcr ncl @sys$manager:net$event_local

and from there the change is permanent and even permanent over software upgrades since
the DECnet/Plus upgrade or reconfigure will not touch ...LOCAL.NCL files

_veli