> 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/operacion/alarm-control-and-management-editran-ea-optional-module.md). # Alarm control and management (Editran/EA) (Optional module) To see the editran/EA functions, consult the [Statistics and Monitoring](/documentacion-editran/ibm-editran-v5.3-cics-en/statistics-and-monitoring.md). By selecting option 5 from the General Menu or =5 from any submenu. ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM CONTROL AND MANAGEMENT EDITRAN 5.3 | | 18:46:57 | ----------------------------------------------------------------------------- | | | | | | | 1 ---> ALARM LOG QUERY | | | | 2 ---> ALARM MANAGER (ENVIRONMENT) | | | | 3 ---> ALARM MANAGER (SESSION) | | | | 4 ---> ENABLE ALARM MANAGEMENT | | | | 5 ---> DISABLE ALARM MANAGEMENT | | | | | | | | OPTION : | | | | | | | ----------------------------------------------------------------------------- ``` * Option: Only the values specified on the screen will be allowed. ## Alarm log query This option displays the following menu: ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM CONTROL AND MANAGEMENT EDITRAN 5.3 | | 18:47:19 ALARM LOG QUERY | ----------------------------------------------------------------------------- | | | | | | | | | | | | | PRESENTATION SESSION: | | | | DATE (DDMMYYYY)...: | | | | TIME (HHMMSS)....: | | | | | | | | ('*' in generic request) | | | | | | | | | ----------------------------------------------------------------------------- ``` The presentation session (consisting of origin code (9), remote code (9), and application (6)) has been combined into a single string so that selection can be made with asterisks (a specific string). The query is identical to that of the editran/P log. Once selected, the following menu appears: ``` 24/06/2026 ALARM FILE QUERY EDITRAN 5.3 18:47:27 SESSION: DATE: TIME: <----- RESULTS -----> EXT. <-- E-MAIL --> SMS SESSION DATE TIME R-01 R-02 R-03 R-04 R-05 ======================== ========== ======== ==== ==== ==== ==== ==== 000099940000099980000096 22/06/2026 15:21:02 ZTG0034-INCOMPATIBLE PRESENTATION STATUS WITH THE REQUEST 000099940000099980000097 22/06/2026 15:21:03 ZTG0034-INCOMPATIBLE PRESENTATION STATUS WITH THE REQUEST 000099940000099980000098 22/06/2026 15:21:04 ZTG0034-INCOMPATIBLE PRESENTATION STATUS WITH THE REQUEST 000099940000099980000099 22/06/2026 15:21:06 ZTG0034-INCOMPATIBLE PRESENTATION STATUS WITH THE REQUEST 000099940000099990PACOF1 22/06/2026 17:40:25 ZTG0187-UNENCRYPTED PRESENTATION RECEIVED 000099940000099990PACOF1 22/06/2026 17:42:55 ZTG0187-UNENCRYPTED PRESENTATION RECEIVED A00099940V00099910MINA14 24/06/2026 18:14:23 ZTG0108-INTERRUPTION NOTIFICATION, CODE: E140 ``` For a description of the results, see the error messages chapter. The following appear in the alarm log: * Error messages, whenever a mask matches (regardless of whether alarms must be notified). * Correct subsequent messages, whenever a mask matches and if alarms must be notified (to check whether the notification is performed correctly). ## Alarm manager (local environment) A local environment record appears in which general data are stored. The following menu is displayed: ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM MANAGER EDITRAN 5.3 | | 18:47:43 LOCAL ENVIRONMENT | ----------------------------------------------------------------------------- WARNING. THIS MAP HANDLES UPPERCASE AND LOWERCASE LETTERS. FILL IT IN APPROPRIATELY. GENERAL DATA FOR CONNECTION TO EXTERNAL MANAGERS: PROGRAM CALLED VIA CALL: ZTBEBA10 PROGRAM DATA PASSED: DAT:000000000-000000000-000000 GENERAL DATA FOR E-MAIL CONNECTION: email TO: geulogio@indra.es GENERAL DATA FOR SMS CONNECTION: PHONE NUMBER (SMS): 000000630938679 SPECIFIC DATA FOR E-MAIL CONNECTION VIA SMTP: email FROM: editran@madzoscicssitd.indra.es SMTP DOMAIN: NODOMVSB SMTP PROC. NAME.: SMTP SMTP PROC. CLASS..: B SPECIFIC DATA FOR E-MAIL CONNECTION VIA UNIX: email FROM: editran@madzoscicssitd.indra.es ALARM PROC. NAME...: ZTBGPEEA GENERAL DATA FOR CONNECTION TO EXTERNAL SERVERS (E-MAIL AND SMS) REMOTE TCP/IP LINE (DNS/IP-ADDRESS + REMOTE PORT): asanjose.indra.es 08102 SERVER CONNECTION TIME..: 010 TCPNAME..............: TCPIPB2 ``` It is important to type uppercase and lowercase correctly, since the map handles both types of characters. * **PROGRAM CALLED VIA CALL**: User program name, which is called from the editran procedure and to which a series of data are passed (see the call specifications for that program in “external manager notification data”). * **PROGRAM DATA PASSED:** User data to pass to the user program, which is called from the editran procedure and to which a series of data are passed (communication area covered in “external manager notification data”). * **Email To:** Email address of the user to be notified of the incident, if any alarm type e-mail = S, as defined in the session records. The value of this field is used to create sessions, although its value may vary within them. * **Phone number**: Phone number to be notified in case the SMS alarm is activated. The value of this field is used to create sessions, although its value may vary within them. * **Email FROM (SMTP)**: Email address of the user who reports the incident. It must be recognized by the SMTP machine. * **SMTP machine domain name**: Domain name of the SMTP machine. Used to perform the HELO. * **SMTP proc. name and class**: Name of the procedure with which the SMTP server was started (normally called SMTP) and class. Normally, B can be used (class B is 80 octets (punch) and class A is 132 octets). Both data are necessary to build the JCL, specifically the card: //SYSUT2 DD SYSOUT= (B, SMTP) * **Email FROM (UNIX)**: Email address of the user who reports the incident. It must be recognized by the UNIX partition machine. * **UNIX email procedure name:** Procedure name to start in case the email is sent from the HOST UNIX partition. Verify that the sendmail program is active. * **Remote tcp lines and port (e-mail and sms)** : Address - DNS IP and port where the editran server is located, which will resolve the email and SMS, if external alarm type e-mail = S or external alarm type SMS = S. * **Server connection time**: Maximum connection time in seconds to the editran server for external e-mail and for SMS. Recommended between 10 and 20 seconds. Supports up to 300 seconds. * **TCPNAME**: Name of the TCP/IP address space whose stack is attached to CICS (data required for external e-mail and SMS). ## Alarm manager (session) For user protection options for transactions, consult the [Installation Manual v5.3](/documentacion-editran/ibm-editran-v5.3-cics-en/installation.md), editran security chapter. The following menu appears, whose operation is identical to that of the editran/P presentation session operator: ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM MANAGER EDITRAN 5.3 | | 18:47:59 PRESENTATION SESSION | ----------------------------------------------------------------------------- | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | R ---> ADD WITH COPY | | | | OPTION............: | | PRESENTATION SES.. | | LOCAL CODE..: | | REMOTE CODE.: | | APPLICATION....: | | | | (If you do not fill in the field or it has a zero value, generic request is assumed) | | | | | ----------------------------------------------------------------------------- ``` When creating a session, it can be done with 2 criteria: * Select local code and/or remote code and/or application as zeros. This indicates that that profile will be notified to all presentation sessions that match it; that is, if we code local code 000099940, remote code 000000000 and application TELECA, all presentation sessions with the specified local code and application will be notified. * Select those codes with values different from zero, in which case it will only apply to that specific transmission session. In any case, if a presentation session meets 2 criteria, for example, if we have defined the presentation session itself and a record all zeros, all the specified actors will be notified. With the add-with-copy option, it checks that the selected session exists and the following menu will appear. Here, you can fill in the image session or press ENTER and select it later. ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM MANAGER EDITRAN 5.3 | | 18:48:45 PRESENTATION SESSION | ----------------------------------------------------------------------------- | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | R ---> ADD WITH COPY | | | | OPTION............: R | | PRESENTATION SES.. OF THE SESSION: | | LOCAL CODE..: 000099940 | | REMOTE CODE.: 000099980 | | APPLICATION....: COSITA | | | | (If you do not fill in the field or it has a zero value, generic request is assumed) | | | | | ----------------------------------------------------------------------------- ``` In generic selections or those with generic criteria, except in the Add option, the following menu will appear, and the session can be selected with an s to the left of the session. ``` 24/06/2026 ALARM MANAGER EDITRAN 5.3 18:49:00 PRESENTATION SESSION S LOCAL CD REMOTE CD APPLICATION - --------- ---------- ---------- 000000000 000000000 000000 000000000 000099940 000000 000000000 200099940 DAMI01 000099940 000099980 PRUEBA 000099940 000099980 PRUEB1 000099940 000099980 000100 000099940 000099990 PRUEBA 000099940 333333333 333333 END OF FILE ``` Finally, the selected session: ``` ----------------------------------------------------------------------------- | 24/06/2026 ALARM MANAGER EDITRAN 5.3 | | 18:49:14 PRESENTATION SESSION | ----------------------------------------------------------------------------- WARNING. THIS MAP HANDLES UPPERCASE AND LOWERCASE LETTERS. FILL IT IN APPROPRIATELY. PRESENTATION SESSION (LOCAL-REMOTE-APPLICATION)..: 000000000 000000000 000000 EXTERNAL MANAGER ALARM TYPE (Y/N): N NAME OF PROGRAM CALLED VIA CALL.: ZTBEBA10 EXTERNAL MANAGER NOTIFICATION DATA......: DAT:000000000-000000000-000000 MVS SMTP E-MAIL ALARM TYPE (Y/N): N UNIX USS E-MAIL ALARM TYPE (Y/N): N EXTERNAL E-MAIL ALARM TYPE (Y/N): N email TO: dmenendez@indra.es email TO: email TO: SMS ALARM TYPE (Y/N)...........: N SMS NOTIFICATION DATA (PHONE NUMBER).: 000000630938679 ALARM LEVEL (0:ERRORS, 1:POST-EMI-REC OK, 2:BOTH): 0 ``` Attention, since this is a map where it is possible to enter uppercase and lowercase characters, there may be fields where incorrect values are entered by mistake. * **PRESENTATION SESSION**: Protected field whose content is the selected record. * **ALARM TYPE XXXXX (Y/N)**: Indicates whether you want to use an alarm of that type (external manager, e-mail, SMS) or not. It is possible to use several at the same time. In the case of email, up to 3 different startup methods can be specified. If it is detected that an incident must be notified: * All managers marked with ALARM TYPE = S will be notified * All sessions defined in editran/E that meet the presentation session criteria will be notified. If we have defined two sessions in editran/E, one of them with external e-mail - SMS alarm type active and local = zeros, remote = 000099990 and application = zeros, and another all-zero session with all alarms active, if an incident occurs in presentation session 000099980 – 000099990 – PRUEBA, it will be notified: > 1. To the external manager indicated in the session local = 000000000, remote = 000000000, application = 000000 > 2. To e-mail(s) via smtp indicated in the session local = 000000000, remote = 000000000, application = 000000. > 3. To e-mail(s) via UNIX of zOS indicated in the session local = 000000000, remote = 000000000, application = 000000. The email address to notify the error is the same as in the previous case. > 4. To e-mail(s) via external server indicated in the session local = 000000000, remote = 000000000, application = 000000. The email address to notify the error is the same as in the previous case. > 5. To e-mail(s) via external server indicated in the session local = 000000000, remote = 000099990, application = 000000. This external server may be different from the one in the previous case. The email address to notify the error may not be the same as in the previous cases. > 6. To SMS indicated in the session local = 000000000, remote = 000000000, application = 000000 > 7. To SMS indicated in the session local = 000000000, remote = 000099990, application = 000000 (the SMS may be the same as or different from the previous case). * **External manager notification data**: Data to route to that manager, if manager alarm type = S. If this alarm is active, from the editran procedure, a CALL is made to the user program defined here, passing it the following communication area:
LevelNameLengthFmt.Description
1Proc function2NumProcedure function
1Presentation session24Alfn.

Presentation session code

Origin (9) – Destination (9) – Application (9)

1Error date-time14Alfn.Error date-time in ssaammddhhmmss format
1Message68Alfn.

Error notification data generated by editran.

(it may be a notification with normal termination)

ZT+xxxx-TEXT (xxxx=0000 Normal operation).

1Jobname8Alfn.Name of the job with the problem (or normal operation)
1Jobnumber8Alfn.Job number with the problem (or normal operation)
1External manager notification data30Alfn.User data for the notification to EXTERNAL MANAGER that the user included in the editran profiles.
* **Email To:** User email address (up to 3) to be notified of the incident, if any alarm type e-mail = S. This data is taken from the environment (if it has any), when creating the session. Its value does not have to be the same as the environment value. * **Phone number:** Phone number to be notified in case the SMS alarm is activated. This data is taken from the environment (if it has any), when creating the session. Its value does not have to be the same as the environment value. * **Alarm level:** Indicates which level we want to report for the alarm: * ‘0’: Report the active ALARM TYPES (S), if any, in the event of errors in procedures (1,2,3,4) or in the event of exceptions (procedure 5), or in the event of an abend in any of the above. * ‘1’: Report the active ALARM TYPES (S), if any, in the event that the post-emission and post-reception processes finish correctly. * ‘2’: Both cases. ## Enable alarm management For user protection options for transactions, consult the [Installation Manual v5.3](/documentacion-editran/ibm-editran-v5.3-cics-en/installation.md), editran security chapter. In this option no screen is displayed; instead, the operator activates the entire system at will (if it was already activated, the appropriate message is displayed). ## Disable alarm management For user protection options for transactions, consult the [Installation Manual v5.3](/documentacion-editran/ibm-editran-v5.3-cics-en/installation.md), editran security chapter. In this option no screen is displayed; instead, the operator deactivates the entire system at will (if it was already deactivated, the appropriate message is displayed). --- # 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/operacion/alarm-control-and-management-editran-ea-optional-module.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.