> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims-en/instalacion/definicion-de-transacciones.md).

# Transaction definition

## Onesait Editran Transactions <a href="#toc9000593" id="toc9000593"></a>

The following transactions will be generated.

* ZTBO associated with PSB ZTBPOOPE. Operator transaction, Information Manager, Query Manager, and Trace and Log recording.
* ZTBT associated with PSB ZTBPOTIM. Time-out process transaction.
* ZTB1 associated with PSB ZTBPOSS1. Editran core. Performs data sending and receiving. It will have access to a single sending database and a single receiving database.
* ZTB2 associated with PSB ZTBPOSS2. NON-MANDATORY TRANSACTION. If you want several Cores or other sending/receiving databases, other transactions, ZTB2, ZTB3, etc., equivalent to ZTB1, can be generated. See the Editran SIZING section.

Transaction names may be changed during installation. The ZTBO transaction must keep this name unless a modification is made to the sources of the supplied MFS.

The transaction definitions are as follows:

```
***                                ***                                 
   APPLCTN  PSB=ZTBPOSS1                                               
     TRANSACT  CODE=(ZTB1),SERIAL=YES,                                 *
               PRTY=(7,10,3),                                          *
               MSGTYPE=(SNGLSEG,NONRESPONSE,21),                       *
               MODE=SNGL                                               
***                                ***                                 
   APPLCTN  PSB=ZTBPOSS2                                               
     TRANSACT  CODE=(ZTB2),SERIAL=YES,                                 *
               PRTY=(7,10,3),                                          *
               MSGTYPE=(SNGLSEG,NONRESPONSE,21),                       *
               MODE=SNGL                                               
***                                ***                                 
   APPLCTN  PSB=ZTBPOOPE                                               
     TRANSACT  CODE=(ZTBO),,EDIT=(ULC),SERIAL=YES,                     *
               PRTY=(7,10,3),                                          *
               MSGTYPE=(SNGLSEG,RESPONSE,20),                          *
               MODE=SNGL                                               
***                                ***                                 
   APPLCTN  PSB=ZTBPOTIM                                               
     TRANSACT  CODE=(ZTBT),SERIAL=YES,                                 *
               PRTY=(14,14,65535),                                     *
               MSGTYPE=(SNGLSEG,NONRESPONSE,15),                       *
               MODE=SNGL                                               
***                                ***                                 
   APPLCTN  PSB=ZTBGEIGA,PGMTYPE=(BATCH)                               
     TRANSACT  CODE=(ZTBI),                                            *
               MSGTYPE=(SNGLSEG,NONRESPONSE)                      
```

Time-out management may be performed internally or externally. If time-out management is to be performed internally, the time-out transaction name (ZTBT) must appear in the local Editran environment profile. This will mean that said transaction must run in a dedicated region and may not have a process time limit or a maximum number of processed messages; in this case, the application itself will schedule that transaction. If the time-out is run externally, the name of that transaction must not appear in the Editran local environment profile; in this case, the entity must implement a mechanism to periodically wake up transaction ZTBT. The transaction would be activated every 30 to 60 seconds by sending it a message with its transaction code; when scheduled, it will query the product databases for pending time-out queues and process them.

The ZTY and ZTB1 transactions will be authorized to issue the DISPLAY, START, STOP, OPNDST and CLSDST commands necessary for batch process and terminal activation.

## Onesait Editran /G Transactions <a href="#toc9000594" id="toc9000594"></a>

The following transactions will be generated.

* ZTBJ associated with PSB ZTBGOADM. Profile Administrator transaction, whose definition is:

```
  APPLCTN  PSB=ZTBGOADM                                               
     TRANSACT  CODE=(ZTBJ),EDIT=(ULC),                                 *
               PRTY=(7,10,3),                                          *
               MSGTYPE=(SNGLSEG,RESPONSE,20),                          *
               MODE=SNGL,SPA=(6000)  
```

* ZTBI associated with ZTBGEIGA, is necessary for the operation of Editran automations before and after file sending and receiving; the definition of this transaction is as follows:

```
   APPLCTN  PSB=ZTBGEIGA,PGMTYPE=(BATCH)
    TRANSACT   CODE=(ZTBI),
               MSGTYPE=(SNGLSEG,NONRESPONSE)
```

* ZTBQ associated with ZTBGOPQF, is necessary for the operation of the file queue loading mode; the definition of this transaction is as follows:

```
   APPLCTN  PSB=ZTBGOPQF                                               
     TRANSACT  CODE=(ZTBQ),                                            *
               PRTY=(14,14,65535),                                     *
               MSGTYPE=(SNGLSEG,NONRESPONSE,15),                       *
               MODE=SNGL                                               
```

This transaction will be authorized to issue the IMS /START REGION command. A mechanism must be implemented to periodically wake up this transaction every 5 or 10 minutes.

## Onesait Editran /TCP Transactions

The following transactions will be generated.

* ZTCP associated with ZTBPETCP is the transaction that receives messages sent to the client/server. If we want to have several Clients-Servers, we can associate this PSB with several transactions (ZTC1, ZTC2 for example), in which case BMP execution in parallel must be allowed. The definition of this transaction is as follows:

```
 APPLCTN  PSB=ZTBPETCP,PGMTYPE=(BATCH),SCHDTYP=PARALLEL              
     TRANSACT  CODE=(ZTCP,ZTC1),                                            *
               MSGTYPE=(MULTSEG,NONRESPONSE)
```

## Onesait Editran Sizing

The number of Editran cores and sending and receiving databases can be increased taking into account the following rules:

The new sending and receiving databases will have the same internal structure as the current ZTBPDEMD/I ZTBPDRED/I, with identical record and key names, differing only in the names of the database and the clusters. See ZTBPDE2D/I ZTBPDR2D/I.

To create a new database, it will be necessary to generate a new Core that transmits it. This Core will consist of a transaction, a copy of ZTB1, and an associated PSB, analogous to ZTBPOSS1, containing the new database. The associated Cobol program will be a renamed copy of ZTBPOSS1. See ZTB2 and ZTBPOSS2.

Each Core will have a different PSB and will access a single sending and receiving database. However, several cores may access the same database.

The new Cores can share classes and regions. The routing of transmissions to a given Core will be performed by Editran Profiles, and can be parameterized by Session. It should be taken into account that assignment to a Core will involve loading and unloading the data onto the database assigned to it in its PSB. Batch processes will be adapted to this fact.

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims-en/instalacion/definicion-de-transacciones.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
