Aggregate Output-Events (EXAEME)

Restriction: This exit is only available in File mode and in C language.

Characteristics

Description

This exit is used to enrich and check Output-Events:

  • Before they are aggregated
  • After they are aggregated
  • When they are passed to the aggregation function, for those which are not to be aggregated

Operating principle

The exit is called for each detail or aggregated Output-Event in the session.

This exit is always called before extracting the Output-Event trace, if an audit rule is associated with the Processing-Context-Out that characterizes the Output-Event.

This exit can be called at two points in the processing phases:

  • During step T aggregation (aggregation of Output-Events by group)
  • During step S aggregation (aggregation of Output-Events, all groups together)

Specific features

When an Output-Event is checked:

  • The source Input-Event (or Input-Events) for the Output-Event may be rejected, in case of step T aggregation
  • The session may be closed, in the case of step S aggregation

Exchanged data

Five entry points are available in this exit:

  • Init: Called before reading the first Output-Event
  • Detail: Concerns an Output-Event before it is aggregated
  • Aggregated:Concerns an Output-Event resulting from an aggregation
  • Non_Aggregated:Concerns an Output-Event on which there must be no aggregation
  • Close : Called after processing the last Output-Event

Alphanumeric fields may have different descriptions depending on the programing language and the Latin or UTF-16 format used. For more information, refer to Exits and external calls.

INPUT data

Name in C Characteristics / Length Use

szSoureceCode

Alphanumeric / 25

Processing-Context-In code associated with the session (only data available on initialization)

nEntryCode

Numeric / 1

Entry point code

szRulesAppliDate

Alphanumeric / 10

Rule application date in DD/MM/YYYY format

szAggregRuleCode

Alphanumeric / 25

Name of the aggregation rule to be applied (empty for entry_code = Non_Aggregated)

IAgregStartRuleDate

Long / 10

Validity start date of the aggregation rule (DD/MM/YYYY format) to be applied (empty for entry_code = Non_Aggregated)

IAgregEndRuleDate

Long / 10

Validity end date of the aggregation rule (DD/MM/YYYY format) to be applied (empty for entry_code = Non_Aggregated)

szOsegtFormatCode

Alphanumeric / 3

Output-Event structure name

szOsegtOutputCode

Alphanumeric / 25

Processing-Context-Out name associated with the Output-Event to be processed

sOsegtContaining

Alphanumeric / 4000 max.

Content of the Output-Event to be checked or enriched

nOSegtLght

Numeric

Length of the Output-Event to be checked or enriched

OUTPUT dat

Name in C Characteristics Use

sOsegtContaining

Alphanumeric / 4000 max.

Content of the enriched and checked Output-Event

nLgMe

Numeric / 4

Length of the enriched and checked Output-Event

 

 

 

szErrorLabel

Alphanumeric / 200

Error description (if system error or Input-Event rejected)

Return value

 

  • 0: zero (EXI_nNOERREUR)
  • 1: (EXI_nREJET) Input-Event group rejection request during step T aggregation and session closure during step S aggregation
  • 9: (EXI_nERREURSYSTEME), if a system error is detected, the session is closed

Compatibility with RDJ version 1.5.3.2 (ITR615)

Five entry points are available in ITR615:

  • 1:Initialize the module and open the files
  • 2: Process an Output-Event that must not be aggregated
  • 3: Process an Output-Event before it is aggregated
  • 4: Process an Output-Event resulting from an aggregation
  • 9: Close the files

Alphanumeric fields may have different descriptions depending on the programing language and the Latin or UTF-16 format used. For more information, refer to Exits and external calls.

INPUT data

Name in COBOL Characteristics / Length Use

LLTYPTRT

9 (1)

Code indicating the type of processing performed

LLEE

Alphanumeric (4000)

Content of the Output-Event to check or enrich

LLLGEE

9 (4)

Length of the Output-Event to check or enrich

LLCDEE

Alphanumeric (3)

Structure code of the Output-Event to check or enrich

LLLIGNE

Alphanumeric (132)

Zone to reformat for the accounting aggregation printout, from 62 characters starting from offset 47 typtrt = 5

LLNBDECIM

Alphanumeric (1)

Number of decimals between 0 and 9 (default=0) for displaying the amounts in the accounting aggregation detail printout

LLCDMODIF

Alphanumeric (1)

Modification code

OUTPUT data

Name in COBOL Characteristics / Length Use

LLRETOUR

9 (1)

Function return codes :

  • 0 (zero): Function successful
  • 1: Session stopped

LLEE

Alphanumeric (4000)

Content of the enriched and checked Output-Event

LLLGEE

9 (4)

Length of the enriched and checked Output-Event

LLCDEE

Alphanumeric (3)

Structure code of the Output-Event to check and enrich

LLLIGNE

Alphanumeric (132)

Zone to reformat for the accounting aggregation printout, from 62 characters starting from offset 47 typtrt = 5

LLNBDECIM

Alphanumeric (1)

Number of decimals between 0 and 9 (default=0) for displaying the amounts in the accounting aggregation printout

LLCDMODIF

Alphanumeric (1)

Modification code

Note   It is recommended that you review your previous version of ITR615, before associating it with a new transformation session. Some actions associated with ITR615 in the previous version may now be replaced with intrinsic product functions or moved to other exits.

Two of the most frequent actions in version 1.5.3.2. are:

  • The carrying forward of the values of the Output-Event aggregation technical fields in the Output-Event functional zones can be cancelled
    You can now associate different aggregation rules with the Output-Events; these rules are multi-criteria and multi-number
  • Truncation of Output-Event technical headers can be moved to the Output-Event restructuring exit

Implementation

Description conventions

  Description

1.

The identifiers set in the communication area cannot be changed
If values are changed, they are ignored during session execution

2.

By default, the return code is 0 (zero)

3.

By default, the Output-Event is identical to the Input-Event

4.

If you request that the source Input-Event be rejected (return code = 1) or if there is a program error, you must set the error message field

Parameter settings

The exit can only be executed if Output-Event aggregation is enabled.

script.ges

Keyword Description / Value to be defined
>Configuration< Section

 

Edition_Agreg_Comptable

  • Yes [exit615]: Execute ITR615 exit in COBOL, for printing the detailed accounting aggregation report

sys.dat

Keyword Description / Value to be defined
>ScriptConfiguration< Section

 

P_Exit_Aggregation_OSegt_Group

(The exit is activated at stage T)

  • Yes_C: Execute EXAEME in C
  • Yes_Cobol: No COBOL program exist
  • Yes_rdj53: Execute ITR615 exit in COBOL, compatible with RDJ 1.5.3.2
  • No: Do not execute during the exit

O_Exit_Aggregation_OSegt

(The exit is activated at stage S)

  • Yes _C Execute EXAEME in C
  • Yes _Cobol: No COBOL program exist
  • Yes _rdj53: Execute ITR615 exit in COBOL, compatible with RDJ 1.5.3.2
  • No: Do not execute during the exit

Module names

Implementation

Platform Directory Name C Program COBOL Program  Compatible
with 1.5.3.2

Windows

%RDJ_EXEC%\exit

EXAEMEC.c
exidllh.h header file

ITR615.cbl

UNIX

$RDJ_EXEC/exit

EXAEMEC.c
exidllh.h header file

ITR615.cbl

MVS

&RDJEXEC..SRCLIB

EXAEMEC
exidllh.h header file.

ITR615

 

Processing Type Label Entry Point

Open

OUV-MODULE (typtrt = 1)

EXI_nINIT

Close

FERM-MODULE (typtrt = 9)

EXI_nFERM

Process an Output-Event without aggregation

TRT-ECR-SS-EDI (typtrt = 2)

EXI_nNON_AGREGE

Process an Output-Event before aggregation.

TRT-ECR-ET-EDI (typtrt = 3)

EXI_nDETAIL

Process an Output-Event resulting from aggregation.

TRT-ECR-ET-EDI-1 (typtrt = 4)

EXI_nAGREGE

Related Links