Mandatory parameter settings

To implement a transformation, you must export a Processing Context-In   to Rule Engine and set the relevant parameter settings in the implementation script file.

These settings relate to:

  • Definitions of environment variables
  • General options in script.ges
  • The physical characteristics in script.ges

Environment variables

These variables are used by the procedures at run-time.

You must define them to allow the procedures to reference valid values (refer to the appropriate Installation Manual).

Variable Use


Reference directory (or library) containing all the reference objects
(For example, error files and executables)


Run-time environment containing the objects to be processed
(For example options, objects to read and to produce)


Reference language (French or English)
If this variable is not set, English is used by default


MQSeries or JMS queue prefix (Rule Engine MQSeries or JMS)
This mandatory variable is automatically referenced by the installation kit

General Options in script.ges

Keyword Description/Values

>Script< Section

“<THIS FILE>”,”Script.File”

Insert the name of the script section to be activated, the script being script.fic for a file, script.mqs for MQSeries, script.jms for JMS.

Use this main section to define the physical characteristics of the script, notably the names of the Rule Engine inputs and outputs for the relevant operating mode (File, MQSeries or JMS)

>Configuration< Section


define DAT

Specify the DAT directory (or library) in which the parameter files are located


Specify the name of the active transformation session


Specify this date in the format dd/mm/yyyy
If it is not defined, the system date is used


Specify the name of the technical context for the transformation


Specify the name of the transformation environment activated by the session

UNIX only

The codification parameter enables you to configure the sign for numerical signed and packed data (data types S and P).

Previously, the sign was always set in the COBOL kernel level NTR590 in EBCDIC format. However, now you can choose between an ASCII and EBCDIC format.
You set the codification parameter in the section >ScriptConfiguration< section of the sys.dat file using the following values:

  • Codification = ASCII
  • Codification = EBCDIC (default value if this parameter is not present in the sys.dat file)

Physical characteristics in script.ges

Defining the processing Context-In 

Keyword Description/Values

>Script.Ges< Section


Input_Event (Name_Sender)

The name of the exchange zone containing the Input-Events to be processed and the Processing Context-In identifier

IEvent _I (Name_Sender) 

Processing Context-In identifier preceded by the name of either the:

Output file in Step E

Input file in the next step TS 

Mandatory for a session without Step TS (Configured as E)

IEvent _Redirected (I)

Name of the Processing-Context-Out (E) for the Input-Event, providing the Redirecting Input-Event option is activated

Defining the exchange zones associated with the processing-Context-Outs in script.ges

Keyword Description/Values

Script.Ges< Section



The name of the exchange zone associated with the Processing-Context-Out that is specified in brackets

Output-Events Business Monitoring
Processing-Context-Outs dedicated to Sentinel must include the following parameter: BusinessMonitoring=yes


The name of the default exchange zone, used to receive the Output-Events for which no exchange zone has been defined

OSegt _P
(required in a session with no step S: that is, configured as ET)

Name of the output file from a T step or the input file to a subsequent S step

Rules for defining exchange zones:
  • Associate each Processing-Context-Out for Output-Events processed in a session with an exchange zone
  • You may associate more than one Processing-Context-Out with the same exchange zone
  • If an exchange zone is missing, when the Output-Events are written out as follows:
    • The Output-Events concerned are written to the OSegt exchange zone, if one is defined
    • If no OSegt exchange zone is defined, the Input-Event from which the Output-Event was generated is placed in anomaly or rejected

Defining exchange zones associated with the transformation products

Keyword Type of Data


Input-Events placed in anomaly during transformation


Input-Events rejected during transformation


Contents of Input-Events modified during transformation

Trace_ IEvent

Contents of traces generated by the Input-Events during the session

Trace_ OSegt

Contents of traces generated by the Output-Events during the session


Information required for report on transformation details


Information required for report on transformation counters


Information required for the transformation summary report


Information required for report on Input-Event redirection


Information for report on transformation anomalies and rejections


Information required for report on Input-Event aggregation counters

Detail_ Aggregation_IEvent

Information required for report on Input-Event aggregation details

Counter_ Aggregation_OSegt

Information required for report on Output-Event aggregation counters


Information required for report on Output-Event aggregation details


Information required for the accounting journal report


Information required for the compensation journal report

Refer to Set parameters for MQSeries and JMS implementations for details of the reports generated.

Related Links