> 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/fuentes-de-dbds-y-psbs-del-modulo-de-presentacion/psbs-asociadas-a-transacciones.md).
# PSBs associated with transactions
## PSB associated with the administrator transaction ZTBGOADM
It is the PSB of the transaction that manages option 1 of the application menu, that is, the profile administration processes of the presentation module; the other options, operator and status and log query (2.1, 2.2 and 2.3), are associated with the Editran operator transaction, so its PSB has been modified (see "PSB associated with the operator transaction ZTBPOOPE")
```
PCBALT PCB TYPE=TP, X
MODIFY=YES, X
EXPRESS=YES
PCBALT2 PCB TYPE=TP, X
MODIFY=YES
BDPERG PCB TYPE=DB, X
DBDNAME=ZTBGDPED, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGPER, X
PARENT=0
BDEST PCB TYPE=DB, X
DBDNAME=ZTBGDESD, X
PROCOPT=GON, X
KEYLEN=50
SENSEG NAME=ESTADO, X
PARENT=0
BDPERP PCB TYPE=DB, X
DBDNAME=ZTBPDPED, X
PROCOPT=GON, X
BDTERM PCB TYPE=DB, X
DBDNAME=ZTBPDTED, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGTER, X
PARENT=0
PSBGEN LANG=COBOL, X
PSBNAME=ZTBGOADM
END
```
## PSB associated with the generic interface transaction ZTBGEIGA
This PSB allows communication between the presentation module and the transmission module through the ZTBI transaction, of BMP type, to which it is associated
```
PCBALT PCB TYPE=TP, X
MODIFY=YES
BDPERP PCB TYPE=DB, X
DBDNAME=ZTBPDPED, X
PROCOPT=G, X
KEYLEN=30
SENSEG NAME=SESION, X
PARENT=0
BDPERG PCB TYPE=DB, X
DBDNAME=ZTBGDPED, X
PROCOPT=G, X
KEYLEN=50
SENSEG NAME=REGPER, X
PARENT=0
PSBGEN LANG=COBOL, X
PSBNAME=ZTBGEIGA
END
```
## PSBs associated with the pre/post issuance/receipt processes
* APPLCTN PSB=ZTBGEIG1
* APPLCTN PSB=ZTBGEIG2
* APPLCTN PSB=ZTBGEIG3
* APPLCTN PSB=ZTBGEIG4
These four PSBs, of BMP type, are identical, differing only in their name; the purpose of this is that if any of them reaches a stopped state, it does not cause the interruption of all procedures, as would happen if there were only one PSB for all of them.
If different databases are used for different transmission sessions, it will be necessary to define other PSBs, twins of the previous ones, but referencing in them the new databases on which the loading of those presentation sessions will be carried out. These new BMP PSBs must be reflected in the procedures of the PROCLIB (ZTBGP\*) of the respective presentation sessions.
* These new PSBs will also be of type BMP and we will call them:
* APPLCTN PSB=ZTBGEI21
* APPLCTN PSB=ZTBGEI22
* APPLCTN PSB=ZTBGEI23
* APPLCTN PSB=ZTBGEI24
These will reference the new sending and receiving databases created (ZTBPDE2D/ZTBPDR2D in our case). If new databases were to be implemented, the process would have to be repeated.
Their definition is detailed below (Since the only difference is the corresponding PSBNAME, only the first is shown):
```
PCBALT PCB TYPE=TP, X
MODIFY=YES, X
EXPRESS=YES
PCBALT2 PCB TYPE=TP, X
MODIFY=YES
BDEMIS PCB TYPE=DB, X
DBDNAME=ZTBPDEMD, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGEMI, X
PARENT=0
BDRECE PCB TYPE=DB, X
DBDNAME=ZTBPDRED, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGREC, X
PARENT=0
*-------------------------------------------------------------------*
* THE FOLLOWING PCB WILL ONLY APPLY WHEN AN INTERFACE IS AVAILABLE
* FOR EDITRAN KEY MANAGEMENT
*-------------------------------------------------------------------*
BDGESC PCB TYPE=DB, X
DBDNAME=ZTBPDGCD, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=REGCLA, X
PARENT=0
BDIGA PCB TYPE=DB, X
DBDNAME=ZTBGDPED, X
PROCOPT=G, X
KEYLEN=50
SENSEG NAME=REGPER, X
PARENT=0
BDEST PCB TYPE=DB, X
DBDNAME=ZTBGDESD, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=ESTADO, X
PARENT=0
BDLOG PCB TYPE=DB, X
DBDNAME=ZTBGDLOD, X
PROCOPT=A, X
KEYLEN=20
SENSEG NAME=REGLOG, X
PARENT=0
BDPRE PCB TYPE=DB, X
DBDNAME=ZTBEDPRD, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGPRE, X
PARENT=0
BDTRA PCB TYPE=DB, X
DBDNAME=ZTBEDTRD, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=REGTRA, X
PARENT=0
BDHIS PCB TYPE=DB, X
DBDNAME=ZTBEDHID, X
PROCOPT=A, X
KEYLEN=20
SENSEG NAME=REGHIS, X
PARENT=0
BDQF PCB TYPE=DB, X
DBDNAME=ZTBGDQFD, X
PROCOPT=A, X
KEYLEN=50
SENSEG NAME=REGQF, X
PARENT=0
PSBGEN LANG=COBOL, X
PSBNAME=ZTBGEIG1
END
```
## PSB associated with the file queue scheduler ZTBGOPQF
This PSB is the one for the transaction responsible for checking whether there is any file pending to be sent in the queue and launches the procedure prior to issuance for the corresponding session.
```
PCBALT PCB TYPE=TP, X
MODIFY=YES, X
EXPRESS=YES
PCBALT2 PCB TYPE=TP, X
MODIFY=YES
BDPERG PCB TYPE=DB, X
DBDNAME=ZTBGDPED, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=REGPER, X
PARENT=0
BDEST PCB TYPE=DB, X
DBDNAME=ZTBGDESD, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=ESTADO, X
PARENT=0
BDPERP PCB TYPE=DB, X
DBDNAME=ZTBPDPED, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=SESION, X
PARENT=0
BDQF PCB TYPE=DB, X
DBDNAME=ZTBGDQFD, X
PROCOPT=GOT, X
KEYLEN=50
SENSEG NAME=REGQF, X
PARENT=0
PSBGEN LANG=COBOL, X
PSBNAME=ZTBGOPQF
END
```
---
# 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/fuentes-de-dbds-y-psbs-del-modulo-de-presentacion/psbs-asociadas-a-transacciones.md?ask=&goal=
```
`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.