> 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/estadisticas-monitorizacion-y-alarmas/instalacion.md).
# Installation
The elements that require generation in IMS for the Editran/E Monitoring and Statistics System version 5.3, and the steps to follow for their installation, are listed in these specifications. The names of the elements are standardized and all begin with ZTBE.
## DL/I Definitions
Contains the definitions of the PSBs, DBDs, and CLUSTERs.
These members are:
### DBDs
| | | | |
|---|
| ZTBEDHID | ZTBEDHII | ZTBEDPRD | ZTBEDPRI | ZTBEDTRD |
| ZTBEDTRI | | | | |
### Clusters
| | | | |
|---|
| ZTBEFHID | ZTBEFHII | ZTBEFPRD | ZTBEFPRI | ZTBEFTRD |
| ZTBEFTRI | | | | |
### PSBs
#### **PSBs for initial load**
#### **Batch PSBs**
#### **Program PSBs**
## BMP execution parameter file (DFSRRC00)
## Steps to follow in the installation
### Obtaining the libraries
Normally, IEBCOPY-format files will be obtained, which the application itself will unload into the corresponding libraries.
### Compilation of MFSs
The formats will be assembled, adapting them to the installation's devices (DEV).
### Generation of IMS and DL/I
In IMS, the transactions, programs, and databases will be generated as indicated below. The PSBs, DBDs, and ACBs will be built, as well as the dynamic allocation of the databases. From the result of the database generation, the source files for the CLUSTERs will be prepared for the next step.
#### **IMS Definitions**
**Database**
* Historical Database ZTBEDHID (HIDAM)
> DATABASE DBD=ZTBEDHID
>
> DATABASE DBD=ZTBEDHII
* Presentation Sessions Database ZTBEDPRD (HIDAM)
> DATABASE DBD=ZTBEDPRD
>
> DATABASE DBD=ZTBEDPRI
* Transmission Sessions Database ZTBEDTRD (HIDAM)
> DATABASE DBD=ZTBEDTRD
>
> DATABASE DBD=ZTBEDTRI
**Transactions and programs**
* ZTBC. Monitoring Queries Transaction.
```
APPLCTN PSB=ZTBEO000
TRANSACT CODE=(ZTBC), *
PRTY=(7,10,3), *
MSGTYPE=(SNGLSEG,RESPONSE,20), *
MODE=SNGL,SPA=(2000)
```
* ZTBE. Monitoring Core Transaction.
```
APPLCTN RESIDENT, *
PSB=ZTBEO100, *
PGMTYPE=(TP), *
FPATH=NO, *
SCHDTYP=SERIAL
TRANSACT CODE=(ZTBE),SERIAL=YES, *
PRTY=(9,,), *
MSGTYPE=(SNGLSEG,NONRESPONSE,21), *
FPATH=NO, *
MODE=SNGL, *
EDIT=(ULC)
```
* BMP for historical summary listing.
```
APPLCTN PSB=ZTBEE002,PGMTYPE=(BATCH)
```
* BMP for recording statistics in pre/post procedures.
```
APPLCTN PSB=ZTBEE100,PGMTYPE=(BATCH),SCHDTYP=PARALLEL
```
### Initialization of Databases and Files
The following databases will be initialized with the corresponding JCL, properly adapted to the installation.
| | |
|---|
| ZTBEDHID | | ZTBEJCHI |
| ZTBEDPRD | | ZTBEJCPR |
| ZTBEDTRD | | ZTBEJCTR |
### Modification of Onesait Editran Profiles
From the Profile Administrator menu, the Local Environment, option 1.1, will be modified to register the Monitoring transactions. This will propagate the modification to all sessions. In the second screen, the transactions will be registered
* G. EDITRAN/E (Monitoring Manager or core) as ZTBE
* C. EDITRAN/E (Statistics Query) as ZTBC.
---
# 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/estadisticas-monitorizacion-y-alarmas/instalacion.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.