Axway Gateway: Messages and codes

Messages and codes

Gateway generates log messages that provide information about the processes and events that occur on the Gateway.

Structure of log messages

Each message is made up of three parts, each part displayed in a separate column:

Column

Contents

1

Time stamp (when the message was printed)

2

Message identification

3

Message text

The message identification items are displayed in two formats, depending on the user interface used. However, the message text does not change.

Message identification (column 2)

Messages are identified in a character string that comprises the following elements:

Element

Contents

Message number

Expressed using three bytes

Gateway module (or process)

The name of the Gateway module or process at the source of this message. This name is abbreviated to one of:

  • FPSIT (PeSIT protocol)
  • FTP (FTP protocol)
  • HTTP (HTTP protocol)
  • SMTP (SMTP protocol)
  • POP3 (POP3 protocol)
  • SFTP (SFTP protocol)
  • ODT (OFTP protocol)
  • PEL (PEL protocol)
  • JCT (Job Control Table)
  • NET (Network module)
  • SNAC (SNA LU 6.2 module)
  • SUP (Supervisor module)
  • PCNX (Protocol connection - customization through the cgate_log_level configuration variable)
  • TSD (TCP Server Daemon)
  • VFD (Virtual file and directory access)
  • SECS (Security errors)
  • EXT (Exit)
  • USR (User)
  • CHK (Monitor checking)
  • NOT (Notif)
  • SR (Statistics and script resolution modules)
  • INT (Payload or Data integrity)

Message Severity

  • S = Success
  • I = Information
  • W = Warning
  • E = Error

Event Name

A character string that abbreviates the name of the associated event. There is a one-to-one correspondence between message names and code numbers.

In the GUI, the Gateway module name, the code number and the type of message are concatenated. The message name is not displayed.

Example:

Depending on the interface, PEL information message number 131, named CONN_REQ, is displayed in one of the following formats:

  • <time stamp> 131 PEL I CONN_REQ <text>
  • <time stamp> PEL131I <text>

Message text (column 3)

The text of the message comprises a generic component. In turn, this component contains a (variable) number of context-dependent parameters.

Examples of message text

Code

Module

Type

Message name

Message text

048

SUP

I

KEY

key=%1, site=%2

101

NET

I

CONN_REQ

(%1) outgoing connection request [dest_address="%2"]

045

PEL

E

ABORT_IND

%1(%2) [%3] transfer aborted. reason=%4

Each instance of a message replaces the context-dependent variables by their values before writing the message in the log file. In the example messages shown in the table above, variables are designated by the percentage symbol (%), followed by a digit that represents the rank of the parameter in the message.

Related topics

Log files

Access Management (AM)

EDI Errors

Exits (EXT)

File Transfer Protocol (FTP)

FTP Reply Codes

Hypertext Transfer Protocol (HTTP)

JMS

Job Control Table (JCT)

LU 6.2 SNA Network (SNAC)

Axway Messaging connector routing (XMSC)

MGET and MPUT messages (MXF)

Monitor Checking (CHK)

Network Module (NET and NDSP)

OFTP (Odette) protocol (ODT)

PEL protocol (PEL)

PeSIT HS protocol (FPSIT)

POP3

Process Monitoring (GC)

Protocol Connection (PCNX)

Reason Codes and Messages

Routing (NOTIF)

Routing Axway Messaging (RXMS)

Rule table evaluation

SECS messages

Simple Mail Transfer Protocol (SMTP)

SSH File Transfer Protocol (SFTP)

Statistics and Script Resolution Modules (SR STATS)

Supervisor Module (SUP)

SWIFTNet (SNET)

TCP Server Daemon (TSD)

Time Driver (TDRV)

Trade messages (TRADE)

Trading Partner Management (TPM)

User Request (USR)

VFD Errors

X.400 (X420)

 

Links to documentation set for Axway Gateway 6.17.3:

Related Links