Define an exchange zone

In general, an exchange zone is defined by its type and name. The name may have properties appended to it.

Exchange_Zone = Type_EZ, "Name_EZ;properties".

Rules

Type_EZ is required and may take the following values.

Value Use

VIRTUAL

Virtual output

MQS

MQSeries-type or JMS-type exchange zones

DEFAUT

Default (file-type) exchange zone

The properties associated with an exchange zone depend on the exchange zone type. However, the total length of the name and the properties, (that is, the characters enclosed within the double quote marks), must not exceed 128 characters.

Define a virtual exchange zone in script.ges

You can use this type of exchange zone with any type of implementation of Rule Engine.

The data associated with this type of output is not physically written out. You can use this type of solution in the following situations:

  • During tuning
  • To save on writing time when some of the outputs, such as the modified Input-Events, are not used

This type of exchange zone definition must not be associated with temporary, working exchange zones or with Input-Events that are to be transformed (input exchange zone).

Definition of a virtual exchange zone on a UNIX or NT machine:

OSegt(Processing Context-Out) = VIRTUAL, "/dev/null"

Definition of a virtual exchange zone on an MVS machine:

OSegt(Processing Context-Out) = VIRTUAL, "DD DUMMY"

Define a queue-type exchange zone for MQSeries in script.mqs or for JMS in script.jms

A queue-type exchange zone is used in an MQSeries or a JMS implementation.

Queue= MQS , "Manager=Qmngr (MQSeries) or QCF (JMS);Queue=Queuename; Blocking=Yes;Buffer=nb; Reformatting=Yes"

Rules for defining a queue-type exchange zone:

  • Rule Engine: The name of the remote manager (if there is one) for the queue containing the data to be read or written:
    • Optional parameter
    • Maximum length of the manager name: 48 Characters for UNIX/WIN, 4 characters for MVS (MQSeries only)
  • Queue: Name of the queue containing the data to be read or written. It may be local or remote, if the 'Rule Engine' parameter is supplied or an alias:
    • Required parameter
    • Maximum length of the queue name: 48 characters
  • Blocking: Request to block the product by message (optional parameter):
    • Yes: Each message is filled with the maximum number of elements possible
    • No:(the default value if the Blocking keyword is not present): A single element is written in each message. This parameter is not used for queues of Input-Events, or for queues of rejected, anomalous or redirected Input-Events.
      For these, the messages must always be blocked. Rejected Input-Events are output with the same blocking used at input.
  • Buffer: Size in KB of the message input (or output) buffer for this queue (optional parameter)
    • If this parameter is missing, the buffer is set to the length of the longest message associated with the queue
    • The value nb must be in the range 1 (minimum) to 4096 (maximum)
  • Reformatting: Activates the reformatting exit (See Manage exits and external calls)

Place all properties of the queue between the double quote marks. They must be separated from each other by semi-colons (;).

Examples:

Queue of Input-Events to be transformed, for the Processing Context-In   APPLI_MQ1, on which the reformatting exit is enabled:

IEvent(APPLI_MQ1) = MQS,"Queue=CRE.ISSU.APPLI_MQ1;Reformatting=Yes"

Output-Event queue, associated with output DEST_COMPTA_GENE, with blocking and a 12KB buffer:

OSegt(DEST_ACCNT_GENE)=MQS,"Queue=OSegt.Accnt.General;Blocking=Yes;Buffer=12"

Define a file-based exchange zone in script.file

A file-based exchange zone is used in a file-based implementation or to define temporary work files in other types of implementation.

File = DEFAULT , "Name_Of_File"

Rules for defining a file-based exchange zone

Name_of_File:

  • Name of the file (path and name in UNIX or DD name in MVS) that contains the data to be read or written.
  • Required parameter.
  • Maximum length of the file name: 128 characters.

Examples:

  • File containing Input-Events to be transformed, for the Processing Context-In   SENDER_TEST, on a UNIX machine:
  • IEvent (SENDER_TEST) = DEFAULT , "/xrdj/_rdjfic/dat/file_ievent.seq"
  • File containing modified Input-Events, on an MVS machine:
  • IEvent_Modified = DEFAULT , "DD:IEVMOD"
  • File containing generated Output-Events, associated with the output ACCOUNTING, on a UNIX machine:
  • OSegt (ACCOUNTING) = DEFAULT , "/xrdj/_rdjfil/result/osegt_accnt.seq"

Related Links