> 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-cics-en/statistics-and-monitoring/monitoring-of-local-communication-lines.md).
# Monitoring of local communication lines
This functionality is yet another one that makes up the statistics and alarms module.
On some occasions, a line or resource in the entity may go down, which may mean that transmissions do not arrive or cannot leave normally. That situation is difficult to detect, because sometimes those outages leave no trace or alarm. When the entity detects the situation, quite a lot of time has usually passed, and it is as a consequence of remote systems that do not connect indicating the abnormality or because local operators detect that the sending or receiving of files is not completed. This situation usually becomes more complicated and its solution is delayed, in the sense that action is not taken directly on the problem; that is, the outage or inoperability of the line is usually the last point to analyze. In addition, the product is usually "unattended" with schedulers and others, which means that many more exceptions are triggered than usual.
Monitoring local lines solves the previous situation. Not because it fixes those outages, but because it notifies them by alarm (email, SMS, etc.) as soon as it detects them, so that operators can investigate and act immediately in the right direction.
This functionality allows monitoring all local lines (to choose which ones) of the entity, indicating how often we want to monitor them. There are several types of local lines: Proxy and IP.
## Definitions
To use it, the following steps must be followed:
1. Presentation and transmission session. Define an "atypical" or "known" session for local monitoring, for example, local-999999999-MONLIN. It does not matter at all how it is defined; what matters is that it serves to notify operators and contains the JCL cards with which the procedures will be launched (see [Administration and Operation](/documentacion-editran/ibm-editran-v5.3-cics-en/operacion.md)).
2. editran local environment (see [Administration and Operation - Local Environment](/documentacion-editran/ibm-editran-v5.3-cics-en/operacion/onesait-editran-administrator/local-environment.md)). It must define
* The monitoring transaction (ZTBC)
* The fields related to local line monitoring, specifically:
* Timeout in minutes. How often we want to "test" the local lines. It is not allowed to indicate a time shorter than 4 minutes. Continuous testing does not seem appropriate, since the functionality consumes resources and, for verification, makes network calls, so it "momentarily consumes cvcs or sockets"; a test, for example every hour, or every 6 hours or every 12, seems more logical.
* Monitoring procedure (ZTBGP9C), is the procedure that is started when a line outage is detected (or when it was down and becomes operational again).
* Lines to monitor. Selection of the local lines to monitor (IP and proxys).
* If you mark S in field 1-IP, you are indicating that you want to monitor ALL listeners that handle editran transactions and arrive via IP (SECEXIT editran).
* If you mark S in field 3-PX, you are indicating that you want to monitor the lines associated with the local proxys, as well as the gateway itself. You must specify in option 1.3.3 which ones you want. In addition, you are indicating that you will also monitor the listeners that handle connections from the PX gateway (SECEXIT EDITR-PR)
* The editran notification session for the previously defined monitoring (local-999999999-MONLIN),
3. Local lines to monitor (see [Administration and operation](/documentacion-editran/ibm-editran-v5.3-cics-en/operacion/onesait-editran-administrator/local-and-remote-communication-lines.md)). You must select in the local Proxys those you want to monitor (you must also have the appropriate field for the line type to be monitored in the local environment). To select it, indicate S in the MONITOR PX field.
4. Alarms. (see [Administration and Operation](/documentacion-editran/ibm-editran-v5.3-cics-en/operacion/alarm-control-and-management-editran-ea-optional-module.md)) If you want to send an alarm (email, SMS, etc.) when the line goes down (or comes up), you must create an appropriate mask for the notification session (or the same local-999999999-MONIT session)
## Description of the processes
Every so often (timeout indicated in the environment), a process is launched that does the following:
1. If I mark MONITOR IP LINES = S in the local environment, it is verified that the listeners (editran transid that handle native IP calls through a port, editran SECEXIT) are active (if they are not, an attempt is made to activate them). In addition, an outgoing call is made to the loopback IP 127.0.0.1, so that it becomes an incoming call to the different listeners. If they answer, it seems clear that they are operational and in session to handle calls that arrive from remote endpoints. In addition, outgoing calls (client processes) are also being tested.
2. If I mark MONITOR PX LINES = S in the local environment:
* The local listeners with SECEXIT = EDITR-PR are checked in the same way as 1 (marking MONITOR IP LINES = 'S' with the local listeners with SECEXIT = editran)
* The PX gateways that have the parameter MONITOR = 'S' are checked, making an outgoing call destined for a remote system whose IP is the Proxy's loopback. This one makes the call and at that moment it reaches it, so it thinks it is a remote call, and passes it to the ZOS listener SECEXIT = EDITR-PR. In this way the entire circuit is tested: ZOS client, Proxy listener, Proxy client and ZOS listener. If an acceptance is received, the entire circuit has been tested. Otherwise, it is determined at which point in the entire circuit the problem is.
The procedure specified in the local environment (ZTBGP9C) is started with the JCL cards of the monitoring session specified in the local environment, in the case of:
* Detecting an incident on a line (provided it was not marked as already having an incident in progress). In that case, the procedure is started with function 98, cause indicating the problem and network diagnostic cause. Note: If a line has an incident, it is marked as such and in the next test performed on it, no incident is sent if it remains in that state.
* Detecting a line in operational or active state, provided the line was marked as being in incident in the previous test. In that case, the procedure is started with function 97.
* If the previous procedure is started:
* A message is written in the alarm log. (option 5.1 of the main menu)
* If there is an appropriate mask (option 5.3), with the monitoring session defined in the local environment, an alarm (external, email or SMS) is sent with the alarm log message (whether activation or outage)
## Errors
The following returns may occur:
```
* 00: INITIALIZED - CORRECT *
* 01: LISTENER NOT ACTIVE *
* 02: LISTENER DOES NOT ANSWER *
* 03: ERROR STARTING LISTENER *
* 21: GATEWAY NOT ACTIVE *
* 22: GATEWAY DOES NOT ANSWER *
* 23: ERROR RETURNED BY GATEWAY *
* 41: FICTIONAL LU NOT ACTIVE *
* 42: X25 LINE DOES NOT ANSWER *
* 43: ISARD X25 REJECTION (X0C REJECTED) *
* 44: X25 LINE OUT OF SERVICE-LOCAL PROC ERROR *
```
For each return, the diagnostic cause or more complete reason for the error is shown; for example, with a 21 return, a message similar to the following would be shown:
```
ZTP9999-LIN PX 006(172.144.026.188/07779) DOWN.GATEWAY INACTIVE FF-01
```
Indicating an error (ZTP999), on PROXY line 006 because the gateway is down. The IP of that gateway is 172.144.026.188 and it should listen on port 7779. The cause of the error and the diagnosis can be checked in 2.3.4.6 of the graphical interface.
Example:
Defined the transmission and presentation session 000099940-333333333-333333
In the local environment:
```
-------------------------------------------------------------------------------
| 18/06/2025 EDITRAN ADMINISTRATOR EDITRAN 5.3 |
| 13:57:04 GENERAL LOCAL ENVIRONMENT |
|-----------------------------------------------------------------------------|
| USER:CICSSITD F-H:20250207-13061 |
| EDITRAN LOCAL CODE : 0 0009994 0 ALIAS..................: L00 |
| LOCAL INSTALLATION NAME.: INDRA CIC DEV. |
| OPERATING SYSTEM.....: XDIP OPERATING SYSTEM VERSION.: MULT |
| CICS JOB NAME.......: CICSSITD CICS APPLICATION NAME.: CICSSITD |
| CPU NAME............: EXECUTION ENV. (E/D/H)..: E |
| MAX. NUMBER OF CONNECTIONS: 999 JCLS NOTIFICATION (M/E): E |
| NAMES OF THE EDITRAN PROCEDURES |
| BEFORE TRANSMISSION......: ZTBGP1CD BEFORE RECEIPT..... ZTBGP2CD |
| AFTER TRANSMISSION...: ZTBGP3CD AFTER RECEIPT..: ZTBGP4CD |
| STATE MODIFICATION... ZTBGP6CD |
| EDITRAN TRANSACTIONS: |
| CORE....: ZTB0 INTERFACE.: ZTBI MESSAGES..: ZTB8 |
| T/O.......: ZTBT MENU......: ZTBM OPERATOR..: ZTBO FILES..: ZTBF |
| ADMIN..: ZTBD LINE MONIT.: ZTBC INCIDENT: ZTB9 STATISTICS Q.: ZTBE |
| STATISTICS G.: ZTB3 EXCI(CICS): ZTBG TCP API...: ZTBB |
| TCP PLTINI: ZTBZ KEY MGMT: ZTB2 |
| |
| EXIT, FORWARD |
-------------------------------------------------------------------------------
```
```
-------------------------------------------------------------------------------
| 18/06/2025 EDITRAN ADMINISTRATOR EDITRAN 5.3 |
| 13:57:34 GENERAL LOCAL ENVIRONMENT |
|-----------------------------------------------------------------------------|
| EDITRAN LOCAL CODE: 0 0009994 0 SIMULT. LISTENER CONNECTIONS...: 100 |
| TCP/IP FIELDS: TCPNAME...: TCPIPB SENDS TIMEOUT (001-999).: 020 |
| MAX USER DATA TIME-OUT(MSS)..: 020 TCP-PX SEND BUFFER (LISTENER).: 262144 |
| USE DNS SERVER IN INCOMING CALLS..: N TCP-PX RECEIVE BUFFER (LISTENER).: 262144 |
| SERVER CONNECTION TIME (SS).: 030 |
| FILE QUEUE FIELDS...........: FILE PENDING TIME-OUT MINUTES..: 010 |
| LOCAL LINE MONITORING......: TIMEOUT MINUTES (>10) LINE CTRL: 010 |
| SEL (S/N) 1-IP,2-PX S S MONITOR PROCEDURE....: ZTBGP9CD |
| SES.EDI/P IMAGE. REMOTE: 3 3333333 3 APP.: 333333 (session must exist) |
| CICSPLEX-SYSPLEX FIELDS............: CICSPLEX SM RELEASE(VERSION): |
| CICSPLEX NAME (CONTEXT).: SCOPE NAME........: |
| |
| FILE INSTALLATION PREFIX........: KI.EIDC |
| WORK UNIT NAME (SYSDA,VIO,..).....: SYSDA |
| WRITE IN SYSTEM LOG (S/N)........: S |
| WORK VOLUME OR POOL (V/P)........: V VOLUME NAME: DES801 |
| ADJUST FILE CREATION SPACE (S/N): N |
| |
| EXIT, BACK |
-------------------------------------------------------------------------------
```
Defined in the PROXY lines (number 1)
```
-------------------------------------------------------------------------------
| 18/06/2025 EDITRAN ADMINISTRATOR EDITRAN 5.3 |
| 13:58:26 COMMUNICATION LINES |
|-----------------------------------------------------------------------------|
| SELECTION CRITERIA: |
| OWNER: L LINE TYPE.: P CODE.....: 0 0000000 0 |
| S OWNER TYPE NUM LINE CHARACTERISTICS |
| - --------- --- --- ------------------------------------------------------- |
| LOCAL PX 001 010.055.000.017 -07775 |
| LOCAL PX 002 010.055.000.017 -07779 |
| LOCAL PX 003 010.055.000.017 -09999 |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| EXIT, SELECT |
-------------------------------------------------------------------------------
```
The content of PX-001 is displayed (monitor field)
```
-------------------------------------------------------------------------------
| 18/06/2025 COMMUNICATION LINES EDITRAN 5.3 |
| 13:59:11 PROXY OR TCP TYPE LINE |
|-----------------------------------------------------------------------------|
| USER:CICSSITD F-H:20240701-131257 |
| OWNER: L LINE TYPE.: P CODE.....: 0 0000000 0 REFERENCE NO.: 001 |
| |
| |
| PROXY LINE: IP ADDRESS OF THE PROXY + PROXY PORT |
| |
| |
| IP ADDRESS (DNS/IP ADDR) PORT |
| ---------------------------------------------------------------- ------ |
| 010.055.000.017 07775 |
| |
| |
| MONITOR PX (S/N).....: S DIALOG PORT (LOG) PX....: 07770 |
| |
| |
| |
| |
| |
| EXIT, MODIFY |
-------------------------------------------------------------------------------
```
If, for example, an error is detected on that line and later resolved, the following messages would appear in the alarm log (option 5.1).
```
18/06/2025 ALARM FILE QUERY EDITRAN 5.3
14:00:02
SESSION: DATE: TIME:
<----- RESULTS ----->
EXT. <-- E-MAIL --> SMS
SESSION DATE TIME R-01 R-02 R-03 R-04 R-05
======================== ========== ======== ==== ==== ==== ==== ====
000099940000000010000001 21/06/2024 12:55:57
ZTG0108-NOTIFICATION OF INTERRUPTION, CODE : R140
000099940000000010000001 21/06/2024 12:56:02
ZTG0108-NOTIFICATION OF INTERRUPTION, CODE : R140
000099940000000010000001 21/06/2024 12:56:05
ZTG0108-NOTIFICATION OF INTERRUPTION, CODE : R140
000099940000000010000001 21/06/2024 12:56:11
ZTG0108-NOTIFICATION OF INTERRUPTION, CODE : R140
000099940000000010000001 21/06/2024 12:56:12
ZTG0108-NOTIFICATION OF INTERRUPTION, CODE : R140
000099940333333333333333 01/07/2024 13:09:59
ZTP9999-LIN PX 003(010.055.000.017/09999) DOWN.GATEWAY INACTIVE FF-01
000099940333333333333333 24/09/2024 15:03:06
ZTP9999-LIN PX 003(010.055.000.017/09999) DOWN.GATEWAY INACTIVE FF-01
```
If, in addition, it were defined in option 5.3, the corresponding email or SMS or external notification would have been sent. (see R-02 on the previous screen, indicating that an SMTP SMS was sent)
---
# 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-cics-en/statistics-and-monitoring/monitoring-of-local-communication-lines.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.