Group management

Section + Keyword Keyword Value Section + Keyword to Input Properties of the Keyword to Input

>Choice<

Group

Yes

 

 

>Ident_Type<

Code_Group

Segment

 

 

 

Context

>Fixed<

Position_Code_Group

Length_Code_Group

Type_Code_Group

>Value<

Code_Group

 

 

Maximum length = 34

Data type = A or N

Aggregate Input-Events

Section + Keyword Keyword Value

>Choice<

Aggregation

Yes

Aggregate Output-Events

Section + Keyword Keyword Value

> Enrich_Exit <

OSegt

Yes, if the P_Exit_Aggregation_OSegt_Group keyword in script.ges is set to Yes

>Choice<

Aggregation

Yes

>Ident_Type<

 

Rule_Aggregation

OSegt. The name of the rule is included in the structure of the Output-Event

Output.  The name of the rule is associated with the output.

Balancing check

Section + Keyword Keyword Value Section + Keyword to Input Properties of the Keyword to Input

>Choice<

Balancing_Check

Yes

 

 

>Ident_Type<

 

 

 

Code_Balance_Check
(field associated with the Input-Event type)

Segment

 

 

Context

>Fixed<

Position_Code_

Balance_Check,

>Value<

Code_Balance_Check

 

 

Length = 1

 

The balancing check is only enabled by the value 1

Rule_Balancing
(identifies the balancing rule associated with the Output-Events)

OSegt

 

 

Output

 

The name of the rule is included in the structure of the Output-Event

 

The name of the rule is associated with the output

Rule_Balancin_Compens
(identifies the balancing compensation rule associated with the Output-Events)

OSegt

 

 

Output

 

The name of the rule is included in the structure of the Output-Event

 

The name of the rule is associated with the output

Accounting checks and reversals

Accounting checks

Section + Keyword Keyword Value

>Choice<

Accounting_Processing

Yes

Reversals

Section + Keyword Keyword Value Section + Keyword to Input Properties of the Keyword to Input

>Choice<

     

Accounting_Processing

Yes

 

 

>Ident_Type<

 

 

 

Code_Reversal
(field associated with the Input-Event type)

Segment

 

 

Context

>Fixed<

Position_Code_Reversal

>Value<

Code_Reversal

 

 

 

Parameter settings for system tuning

This section explains the keywords used during system tuning. These keywords are to be found in sys.dat.

Checking numeric values in mapped fields

Section + Keyword Value Meaning

>Check<

Numeric

Yes

 


No

Mapped fields that are defined as numeric are checked for numeric content in Output-Events or modified segments
The Input-Event is placed in anomaly if the check fails

The above check is not made
If a field that is defined as numeric does not contain a numeric value, the transformation may be terminated with a system error

Checking for the existence of table keys

Section + Keyword Value Meaning

>Check<

 

 

Existence_Table

Yes

 


No

For a table to which access is controlled by the session, the Input-Event being processed is placed in anomaly if a table key cannot be found.

The processing is deemed to be correct, whatever the type of access control.

For details of this function, refer to the section on tables in the Axway Composer Reference Guide.

Check for the existence of rules

Section + Keyword Value Meaning

>Check<

 

 

Existence_Rule

Yes

 

 

 



No

Rule Engine checks at the beginning of the session that the configuration contains the rules that are specified for processing, for pre-processing of Input-Events, and for the processing associated with outputs

These include aggregation, transformation, modification, audit and balancing rules. If the check fails on any rule, the session is not started

If a rule that is required for processing is missing from the configuration, the Input-Event in question is rejected (placed in anomaly) when it is processed

This option allows you to ensure that you have all the required parameters before you start the processing.
It helps to avoid anomalies in the processing caused by the absence of a rule that may be required for processing a large number of Input-Events.

Caution   This check is applied for all Input-Event types with parameters on-line, even if these parameters are not required for the session. To enable this option, you require a full set of parameters.

Optimizing the writing of Output-Events

Section + Keyword Value Meaning

>Optimization<

 

 

Length_OSegt

Yes


No

When it is written out, the length of the Output-Event matches that of its structure

The Output-Event is padded with blanks to a fixed length of 4000 characters

>Optimization<

 

 

RTrim_OSegt

Yes


No

When it is written out, the Output-Event is truncated if the rightmost characters in the structure are blanks

When it is written out, the length of the Output-Event matches that of its structure

Audit

Section + Keyword Keyword Value Section + Keyword to be Input Properties of the Keyword to Input

>Choice<

 

 

 

Auditing

Yes

>Auditing<

 

>Auditing<

 

 

 

Position_Identifier_Stamping

NNNN (<=4000)

 

The start position for the stamping identifier in the Input-Event segment

Length_Identifier_Stamping

NN (maximum 25 characters)

 

Length of the stamping identifier
(see below)

Type_Counter_Stamping

Numeric

Packed

 

Data type of the stamping counter
(see below)

Stamping_Identifier_Completed

Yes

 

No

 

Any value in the field that contains the stamping identifier is replaced by the recalculated value

The existing value is retained

Type_Stamping

Stamping

Series

 

See below

See below

>Ident_Type<

 

 

 

Rule_Audit

Output

 

 

OSegt

 

Structure

 

Name of the audit rule associated with the output

 

Name of the audit rule contained in the Output-Event

 

Name of the audit rule = name of the Output-Event structure

>Multi sessions audit<

 

 

 

Position_Identifier_Stamping_Origin

NNNN (<=4000)

 

The start position for the stamping identifier in the Input-Event segment

Length_Identifier_Stamping_Origin

NN (maximum 25 characters)

 

Length of the stamping identifier
(see below)

Type_Counter_Stamping_Origin

Numeric

Packed

 

Data type of the stamping counter
(see below)

Type_Stamping_Origin

Stamping

Series

 

See below

See below

Rules to follow:

# Meaning

1

The start position and length of the field containing the stamping identifier, when added together must not exceed 4001 characters

2

Length_Identifier_Stamping:

If TimeStamp is set as the stamping type, the stamping identifier must be alphanumeric, with a length of 25 characters. The identifier must have the following format:

  • The operation date is in the form YYYYMMDD
  • The stamping time is in the form HHMMSS

In this case, when the stamping counter reaches its upper limit, the stamping time in the identifier is updated to the current time and the counter is reset to 00001

If Series is set as the stamping type, the identifier is made up of a character, which shows the type of segment being stamped, and a stamping counter. The maximum length of the identifier is 19 characters (1 alphabetic for the segment type identifier + 18 for the numeric counter)

In this case, the system stops the session if the stamping counter reaches its upper limit. A return code of 10 is set

3

Type_Counter_Stamping: Specify the data type of the numeric counter that is to form the stamping identifier

4

Stamping_Identifier_Completed: If the Input-Event comes out of a session in which the Audit option is enabled, the segments are already stamped
This option allows you to do one of the following:

Retain the existing value of the stamping identifier (value No)o

Recalculate the stamping value for the current session and overwrite the existing stamp

Phase-specific recycling of Output-Events in anomaly

Section + Keyword Keyword Value Section + Keyword to be Input Properties of the Keyword to Input

>Choice<

 

 

 

Recycling_Phase

Yes

>Ident_Type< Code_Phase_Anomaly

 

>Ident_Type<

 

 

 

Code_Phase_Anomaly

Segment

 

 

 

 

 

Context

 

 

>Fixed<

Position_Code_Phase_Anomaly,

Length_Code_Phase_Anomaly

 

>Value<

Code_Phase_Anomaly

Start position and length of the area from which the name of the phase is read and to which the name of the phase in anomaly is written for recycling

 




Name of the phase executed for all Input-Events processed

Rules to follow:

Rule Meaning

1

The sum of Position + Length must not exceed 4001

2

Maximum length of the phase name is 25 alphanumeric characters

Exits

Checking and enriching Input-Events before the transformation phases

This exit checks, enriches or modifies the data in the Input-Event segments before they are processed in the transformation phases.

Keyword Description/Values Compatible with Step ...

Section >Exit_Enrich<

 

 

Segment

Yes_C or Yes_Cobol or Yes_rdj53 or No

Yes_rdj53: Compatible with ITR506.2

P

Checking and enriching the Input-Event segments for a specific transformation Rule

This exit modifies, enriches or checks the data in the Input-Event segments before each application of a change or transformation rule.

Keyword Description/Values Compatible with Step ...

Section >Exit_Enrich<

 

 

Rule

Yes_C or Yes_Cobol or Yes_rdj53 or No.

Yes_rdj53: Compatible with ITR506.2.

T

Identifying and checking Output-Events

This exit enriches or checks the Output-Events, or identifies the output, before the Output-Events are processed.

Keyword Description/Values Compatible with Step ...

Section >Exit_Enrich<

 

 

OSegt

Yes_C or Yes_Cobol or Yes_rdj53 or No.

Yes_rdj53: Compatible with ITR506.3.

T

Anomalies and rejections from transformation

Checking for production of Output-Events

Section + Keyword Value Meaning

>Authorization<

 

 

Rule_No_Output

Yes


No

It is acceptable for a transformation rule to produce no Output-Events

If a transformation rule runs without producing Output-Events, the Input-Event is placed in anomaly

>Limit<

 

 

Stop_Phase_First_Anomaly

Yes


No

As soon as an anomaly is detected in a phase, the subsequent rules in the phase are not applied

The subsequent rules are applied to detect any further anomalies
This option is useful during testing to optimize the correction of errors

Rejected events

Section + Keyword Value Meaning

>Authorization<

 

 

IEvent_No_Output

Yes


No

It is acceptable for an Input-Event to be transformed without producing any Output-Events

If an Input-Event is transformed without producing Output-Events, the Input-Event is rejected

Rejecting a group of Input-Events

Section + Keyword Value Meaning

>Limit<

 

 

IEvent_Group_Rejected

n


0 (zero)

Processing of the group is stopped if n Input-Events are rejected

All Input-Events in the group are processed, regardless of how many Input-Events are rejected
This allows the maximum number of anomalies to be detected

Stopping the session

Section + Keyword Value Meaning

>Limit<

 

 

IEvent_Rejected

n


0 (zero)

The system stops the session if the threshold of n rejected Input-Events is reached

The transformation continues to the end however many Input-Events are rejected

Group_Rejected

n


0 (zero)

The system stops the session if the threshold of n rejected Input-Event groups is reached

The transformation continues to the end however many Input-Event groups are rejected

Percentage_IEvent_Rejected

P%

 

0 (zero)

The session is declared invalid, and a return code of 10 is set, if the final percentage of Input-Events rejected is equal to or greater than P%. P may be any value from 0 through 100

The session is deemed to be valid whatever percentage of the Input-Events are rejected

Related Links