> 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/introduction.md). # Introduction In the screen images included in this document, the different types of fields are represented as follows: * The Local and Remote Installation Codes are 9 characters long, the first and last alphanumeric. The Application Code has 6 characters (A - Z, excluding Ñ, and 0 to 9). * In all screens where it appears *“‘\*’ in generic request “*, a \* can be entered in the first or last position of the Session field and a screen with all selected sessions will appear. * In all screens where it appears *“‘\*’ in generic request “*, if nothing is entered (blanks) in the Session field, all records will be shown. It is not the same as the previous case, because if only an asterisk is selected, it will search for sessions whose key is anything that ends in blanks. To navigate between screens: * Forward between menus, submenus and functions: Enter the specified option, and you can move directly from one menu to another by typing the '=' character, followed by the desired option. * Backward between menus, submenus and functions: PF3. If you are in the main menu, editran is exited. * Navigation within a function with one or several different or repetitive screens: PF8 forward, PF7 backward, PF3 returns to the previous menu and, if it is an update, it is abandoned, ENTER performs the update and returns to the previous menu. * To enter editran, run transaction ZTBM from CICS (this name is the one specified in the Menu transaction in the general local environment), then the editran Main Menu is displayed. ✅ The Main Menu is accessed through transaction ZTBM. ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN MANAGER EDITRAN 5.3 | | 15:28:46 PHASE 01 | ----------------------------------------------------------------------------- | | | 1 ---> ADMINISTRATOR | | | | 2 ---> ACTIVITY CONTROL | | | | 3 ---> REDUCED PROFILE MANAGEMENT | | | | 4 ---> STATISTICS AND MONITORING | | | | 5 ---> ALARM CONTROL AND MANAGEMENT | | | | 6 ---> EXCHANGE KEY MANAGEMENT | | | | 7 ---> EDITRAN/FF MANAGEMENT (ELECTRONIC SIGNATURE) | | | | | | OPTION : | | | | | ----------------------------------------------------------------------------- ``` From this menu the product is managed. Once editran is installed, it is necessary to define the parameters of the Local Installation (General Local Environment and subenvironments, if necessary) and those of the SESSIONS to be used. * Option 1 invokes the Editran administrator functions. * Option 2 invokes the presentation and transmission activity control functions. * Option 3 invokes the functions of an abbreviated editran profile administrator. * Option 4 invokes the functions of the (optional) editran/E Statistics and Monitoring module. For more information and if you have this module, consult the corresponding manual. This option can be accessed without going through the main menu by entering transid ZTBE. * Option 5 invokes the functions of the (optional) editran/E Alarm Management module. For more information and if you have this module, consult the corresponding manual. * Option 6 invokes the functions of the editran/GC module (included with limitations). Its use requires at least an RSA license. For more information and if you have this module, consult the corresponding manual. This option can be accessed without going through the main menu by entering transid ZTB2. * Option 7 invokes the functions of the editran/FF module in its z/OS operating mode. Its use requires an editran CD+FF license. For more information and if you have this module, consult the corresponding manual. * The editran P and G profiles are configured as follows: * On the one hand, there is an editran/P profile file (file ZTBPFPE). The following records are stored in it: * General environment record. Corresponds to the entity's main code. It contains parameters that are common to all transmission sessions. * Subenvironment records. If the main entity also represents other entities, companies, departments, etc., it corresponds to the secondary code of each one. * Transmission session records. They contain the local code (from the general environment or subenvironment), the remote code and the transmission application. The above trio is known as an external session or transmission session and must be defined identically at both ends (the remote end will change the order of local code – remote code). * Internal session records. They are aliases of the transmission session records, which avoid having to type all the previous data (local code, remote code, transmission application) to refer to them. * Line records. These are local and remote line data records. * On the other hand, there is an editran/G profile file (file ZTBGFPE). The following records are stored in it: * General environment record. Corresponds to the entity's main code and must match the local code of the general environment record of editran/P. In reality, it is a template record, used for presentation sessions. * Subenvironment records. Corresponds to the entity's secondary codes and must match each and every one of the secondary codes of the subenvironment records in editran/P. In reality, it is a template record, used for presentation sessions. * Remote entity records. Corresponds to records that identify the remote entity (remote code). In reality, it is a template record, used for presentation sessions. * Presentation application records. Corresponds to records that identify the presentation application (data content). In reality, it is a template record, used for presentation sessions. * Presentation session records. They contain the local code (from the general environment or subenvironment), the remote code (remote record) and the presentation application (presentation application record). The above trio is known as a presentation session. Each presentation session record is associated with 1 to 20 transmission sessions (see editran/P record). --- # 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/introduction.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.