> 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-1.md).
# Installation
The elements that require generation in the IMS of the Editran/E Alarm Management 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
| | | | |
|---|
| ZTBEDPED | ZTBEDPEI | ZTBEDALD | ZTBEDALI | |
### Clusters
| | | | |
|---|
| ZTBEFPED | ZTBEFPEI | ZTBEFALD | ZTBEFALI | |
### PSBs
#### **PSBs for initial load**
#### **Batch PSBs**
#### **Program PSBs**
#### **Local line monitoring**
#### **Procedures**
#### **BMP execution parameter file (DFSRRC00).**
## Steps to follow in the installation
### Obtaining the libraries
Normally, IEBCOPY format files will be obtained, which the application 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. Using the result of the generation of databases, the source files for the CLUSTERs will be prepared for the next step.
**IMS Definitions**
**Database**
* Alarm Profiles Database ZTBEDPED (HIDAM)
```
DATABASE DBD=ZTBEDPED
DATABASE DBD=ZTBEDPEI
```
* Alarm log database ZTBEDALD (HIDAM)
```
DATABASE DBD=ZTBEDALD
DATABASE DBD=ZTBEDALI
```
**Transactions and programs**
* ZTBL. Alarm Management transaction.
```
APPLCTN PSB=ZTBEOA00
TRANSACT CODE=(ZTBL), *
PRTY=(7,10,3), *
MSGTYPE=(SNGLSEG,RESPONSE,20), *
MODE=SNGL
```
* Alarm Control BMP.
```
APPLCTN PSB=ZTBEEA00,PGMTYPE=(BATCH)
```
* ZTBM. Monitoring transaction.
```
APPLCTN PSB=ZTBEEMCO,PGMTYPE=(BATCH)
TRANSACT CODE=(ZTBM), *
MSGTYPE=(SNGLSEG,NONRESPONSE)
```
* The transaction must be authorized to issue the IMS /START REGION command.
* BMP for local communication line monitoring.
```
APPLCTN PSB=ZTBEEMCO,PGMTYPE=(BATCH)
```
#### Initialization of Databases and Files
The databases listed below will be initialized with the corresponding JCL, duly adapted to the installation.
| | |
|---|
| ZTBEDPED | | ZTBEJCPE |
| ZTBEDALD | | ZTBEJCAL |
#### Modification of Onesait Editran Profiles and Procedures
From the Profile Administrator menu, the Local Environment, option 1.1, will be modified to register the Alarm Management transaction. This will propagate the modification to all sessions. On the second screen, transaction ZTBL will be registered in the ALARM ADM field, transaction ZTBM in the NETWORK MONITORING transaction field, and procedure JCL ZTBEJMCO in the procedure field.
#### Modification of Onesait Editran /G Procedures
Since the alarm activation occurs within the processes before and after sending and receiving, as well as in the process triggered by transmission interruption, it is necessary to modify the Editran procedures 1 to 5.
The "SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATB2),DISP=SHR" card will be added in steps A1P, A2P, A3P, A4P and A7I of each procedure, in the event that external "server" notification types (e-mail and SMS) are used and DNS must be resolved.
The ZTBGP2 procedure is shown below as an example
```cobol
// SOURCE PROC=,FUNCTION=,L0=,
// L1=,L2=,R1=,R2=,AP=
//*********************************************************************
//* INDRA *
//*********************************************************************
//* PRE-RECEPTION PROCEDURE EDITRAN/G *
//*********************************************************************
//* DATA: *
//* ORIGIN (O=OPERATOR,E=EDITRAN,A=APPLICATION JCL) ----> 1 BYTE *
//* *
//* FUNCTION (06=RECEPTION INITIALIZATION, *
//* 08=RECEPTION REQUEST FOR PRESENTATION )---> 2 BYTE *
//* *
//* PRESENTATION SESSION : *
//* LOCAL CODE L1 --------------------------------> 6 BYTES *
//* L2 --------------------------------> 3 BYTES *
//* REMOTE R1 --------------------------------> 6 BYTES *
//* R2 --------------------------------> 3 BYTES *
//* APPLICATION AP --------------------------------> 6 BYTES *
//* *
//* LOCAL ENVIRONMENT ALIAS (FOR PARTICULAR USES) *
//* L0 --------------------------------> 3 BYTES *
//* PRESENTATION APPLICATION (FOR SPECIAL USES) *
//* PR --------------------------------> 6 BYTES
//*********************************************************************
//A2P EXEC PGM=ZTBGB120,REGION=8M,
// PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP'
//STEPLIB DD DSN=IMS510P.RESLIB,DISP=SHR
// DD DSN=KI.EGDI.LOAD,DISP=SHR
//*ZTBGFEST DD DSN=KI.EGDI.ZTBG.ESTADOS,DISP=SHR
//ZTBGFPER DD DSN=KI.EGDI.ZTBG.PERFILES,DISP=SHR
//ZTBGFLOG DD DSN=KI.EGDI.ZTBG.LOG,DISP=SHR
//ZTBGF032 DD DSN=KI.EGDI.ZTBG.ZTBGF032,DISP=SHR
//ZTBGFESD DD DSN=KI.EGDI.ZTBGFESD,DISP=SHR
//ZTBGFESI DD DSN=KI.EGDI.ZTBGFESI,DISP=SHR
//ZTBGFLIS DD SYSOUT=*
//ZTBGFMSJ DD SYSOUT=*
//ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105)
//ZTBGFINT DD SYSOUT=(H,INTRDR),DCB=(BLKSIZE=80)
//CEEDUMP DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATB2),DISP=SHR
// SET LOCAL0=&L0
// SET PRESEN=&PR
```
---
# 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-1.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.