Structure of the messages generated

The message context generated for a given product is formed as follows:

  • MsgId is a unique value assigned by Rule Engine MQSeries or JMS
  • CodeCharSetId is set to 0 (zero)
    The format is obtained from MQSTR
  • CorrelId is set to spaces, except when the Group Management option is enabled
    For more information, refer to Manage groups with MQSeries or JMS
  • The other elements in the context are identical to the context associated with the Input-Event being processed

The following table shows the format of the data element of the message:

Data Element Number of Characters Meaning

Filler

13 characters

 

Product number

2 characters

The code number that identifies the type of product carried by the message

Processing-Context-Out name

25 characters

Name of the Processing-Context-Out for the product, if one exists.
This field is filled for Output-Events and redirected Input-Events

Filler

24 characters

 

Number of elements

7 characters

Number (N) of elements of the product contained in the message

Length of element 1

4 characters

 

Element 1

1 to 4000 characters
(as defined in the previous field)

 

...

 

 

Length of element N

4 characters

 

Element N

1 to 4000 characters
(as defined in the previous field)

 

A number that is assigned by Rule Engine identifies each product generated.
You can transfer the data stored in a queue to a file, using the administration tools supplied.

The following table shows the product numbers assigned to each type of product.

Note   You can store no more than 2 compatible products in the same queue.
For details of compatibility, see the following table.
Product Number Description of Product Keyword in script.mqs or script.jms Compatible Product Number

01

The Input-Event to be transformed

IEvent (Sender)

 

02

Output-Events broken down by Processing-Context-Out

OSegt(Name_Output)

02
(different Processing-Context-Out)

03

Redirected Input-Events broken down by Processing-Context-Out

IEvent_Redirected (Name_Output)

03
(different Processing-Context-Out)

04

Input-Events placed in anomaly during transformation

IEvent_Anomaly

05

05

Input-Events rejected during transformation

IEvent_Rejected

04

06

Modified Input-Events

IEvent_Modified

 

07

Audit traces extracted from the processed Input-Events

Trace_IEvent

16

08

Data for report on transformation anomaly details

Detail_Anomaly_Rejection_IEvent

 

09

Data for report on redirection details

Detail_Redirection_IEvent

 

10

Data for report on transformation details

Detail_Transformation

 

11

Data for report on transformation counters

Counter_Transformation

 

12

Data for report on operation counters

Rule_Counter

 

13

Data for customized reports

Detail_Print_Customized

 

15

Data for the account log report

Log_Account

 

16

Audit traces extracted from the Output-Events generated

Trace_OSegt

07

Related Links