Physical organization

This section summarizes briefly the physical organization of the product. For more information on this topic related specifically to the machine on which you are running Rule Engine, refer to the appropriate Installation Manual.

This illustration is specific to MVS:

Physical organization

The various elements are grouped by category:

Input data

Directory Contents

System files
(SYS for MVS)

System files:

The system context, including all the Rule Engine options supplied

Error messages: contains descriptions of all errors generated during processing

Executable files (EXE for MVS)

Executables for all required transformations

Report templates
(FMT for MVS)

Templates for all reports:

Results of redirection

Details of transformation anomalies

Input-Event aggregation counters

Details of Input-Event aggregation

Aggregation counters for accounting Output-Event

Details of Output-Event aggregation

Transformation counters

Transformation counters summary

Details of modified Input and Output-Events generated in a session

Account log

Configuration files
(REF et DAT for MVS)

Configuration files:

Some of these are updated by automatic procedures (for example, descriptors, functional context, rules and compiled tables)

Others must be updated manually via the implementation script script.ges, where the value of ges is the implementations file, mqs for MQSeries, jms for JMS

The data to be processed by the procedures. You can configure the names.


Continuous use

The JCLLIB or SCRIPT directory (or library) contains the run-time procedures:

Procedure Purpose

For continuous use


Procedure for transforming Input-Events into Output-Events

Syntax : rdjexp [txt/pdf/html] [session] [audit] [business] [ews]

txt : file *.edi report format (by default)


Procedure for creating a file of Input-Events in anomaly, to be passed to InterPlay


Procedure for gathering tracking information to be sent to Sentinel

For use during tuning


Procedure for automatic compilation of the Rule Engine environment parameter settings, to be run after export from AI Enabler


Procedure for merging the default functional context parameter files (sys.dat and usr.dat) in the Rule Engine environment during partial exchanges  from AI Enabler (securing exchanges) which requires merging exchange files with those already present


Procedure for extracting the configuration settings in the form of an input file


Procedure for printing the contents of the compiled parameter files


Procedure for extracting the configuration settings in the form of an RGTR file


Procedure for updating the compilation of the configuration file

For use during installation


Procedure for reinitializing the environment, used to create an empty site: Under DAT, only the supplied files are re-initialized


Procedure for running and managing the SIC (Information and verification system) installation process

Output data

Directory Contents
MVS Windows/UNIX  
EDI edi Reports containing the results of the execution of the various procedures



Temporary work files used by the procedures


envref/dat and dat

Parameter files updated by rdjmaj and rdjrch after export from AI Enabler:

  • The descriptors (sys.dat)
  • The compiled rules and tables



The products generated by rdjexp:

  • The Output-Events
  • Modified Events
  • Redirected Events
  • Input-Events in anomaly during transformation
  • Rejected Events
  • Input-Event traces
  • Output-Event traces

Related Links