XCOM Messages changed eg XCOMM0793I & XCOMM0805I
search cancel

XCOM Messages changed eg XCOMM0793I & XCOMM0805I

book

Article ID: 202099

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM Data Transport - Linux PC XCOM Data Transport - z/OS XCOM - SUPPORT

Issue/Introduction

Since putting maintenance on to xcom i have noticed that the xcomm0793i message has changed. 

XCOMM0793I TCP/IP REMOTE CONNECTION ESTABLISHED FROM

and now since the maintenance it looks like this

nnn.n.nnn.nn    #                   XCOMM0793I TCP/IP REMOTE CONNECTION ESTABLISHED FROM IP=nnn.n.nnn.nn

it has a "#" but no transfer number or TID.

 

the XCOMM0805I has also changed from before the maintenance

XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=nn.nnn.nn.n 

to after the maintenance

nnn.n.nnn.nn    #343464             XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=nnn.n.nnn.nn

at least it has a TID number in it.

 

 

 

 

 

 

 

 

 

Environment

Release : 12.0

Component : CA XCOM Data Transport for z/OS

Resolution

Some of these messages were changed to provide a means of identifying the type of incoming requesting the IDENT field of the message prefix header, if it’s available. Subsequently, the “#” has been removed if the request number is not available. This # removal is part of the AT-TLS enhancement test fix (APAR #: ST15002).

In this case, the request # is not available yet because the message gets logged before the request details have been received. This change will not be changing back.