> 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/onesait-editran-administrator/local-environment.md). # Local environment The screen that allows you to manage the General Local Environment and subenvironments is displayed. ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 15:32:13 LOCAL ENVIRONMENT | ----------------------------------------------------------------------------- | | | | | | | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | | | OPTION : C | | LOCAL CODE : | | | | ('*' generic subenvironment selection) | | | | | ----------------------------------------------------------------------------- ``` In this version of the product, the Multi-environment functionality exists. That is, we can present ourselves to other customers as one or several centers. The first, and it may be the only one, is called the General Local Environment and the next and subsequent ones will be called Subenvironments. In both cases the local code consists of 9 characters with the following format xnnnnnnnx. The Local Code and the desired option (Add, delete, query, or modify) must be specified. In the query and modify option, if the code is not typed, the General Environment screen will be displayed. ℹ️ With a \* in the first position, all Subenvironments appear. ℹ️ The first time the add is performed, it will refer to the General Local Environment. The first screen of the general environment is as follows: ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | 15:32:31 GENERAL LOCAL ENVIRONMENT ----------------------------------------------------------------------------- | USER:CICSSITD F-H:20260619-10151 | EDITRAN LOCAL CODE : 0 0009994 0 ALIAS..................: L00 | LOCAL INSTALLATION NAME.: INDRA CIC DESA | OPERATING SYSTEM.....: XDIP OPERATING SYS. 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): M | NAMES OF THE EDITRAN PROCEDURES | BEFORE SEND........: ZTBGP1CD BEFORE RECEIVE..... ZTBGP2CD | AFTER SEND.........: ZTBGP3CD AFTER RECEIVE......: ZTBGP4CD | STATUS MODIFICATION... ZTBGP6CD | EDITRAN TRANSACTIONS: | CORE....: ZTB0 INTERFACE.: ZTBI MESSAGES..: ZTB8 | T/O.......: ZTBT MENU......: ZTBM OPERATOR..: ZTBO FILES..: ZTBF | ADMIN....: ZTBD LINE MONITOR.: ZTBC INCIDENT: ZTB9 STAT. MGT: ZTBE | STAT. MGT: ZTB3 EXCI(CICS): ZTBG TCP API...: ZTBB | PLTINI TCP: ZTBZ KEY MGMT: ZTB2 | | EXIT, ADVANCE ----------------------------------------------------------------------------- ``` The second screen of the local environment: ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 15:32:48 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..: 002 | | LOCAL LINE MONITORING......: TIMEOUT MINUTES (>10) LINE CTRL: 010 | | IP(Y/N): S PROXY(Y/N): S MONITORING PROC.........: 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 | ------------------------------------------------------------------------------- ``` At the top, the user and date/time of the last record modification appear. The general environment fields are transferred to each of the presentation session records (in short, it is a template record), regardless of whether that presentation session contains a local code different from the general environment, thereby making it possible for their content to vary between one presentation and another. ℹ️ The content of the fields has the following meaning: ## Screen 1 * **USER:** Contains the last user who modified the record. It is common to all profile records. * **F-H**: Date and time of the last modification. * **EDITRAN LOCAL CODE**: Identification number of the editran User Entity. With this code it will be recognized by all Entities interconnected with compatible editran. * **ALIAS**: Data included as a parameter in the before/after send/receive procedures launched from editran/P for eventual use by the Interface being used. Specifically, the editran/G procedures do not use it, although they receive the parameter, so it can be included by the user in the processes that can be added in the standard procedures. * **LOCAL INSTALLATION NAME**: literal referring to the Name of the editran User Entity. It is an informational field. * **OPERATING SYSTEM**: Name of the OS required for the appropriate automation processes to run. For DOS/VSE operating environments you must type DOS or VSE; any other value typed (MVS, XA, SP, etc.) will trigger the batch processes of those environments, which are of a different nature. It is an informational field. * **OPERATING SYS. VERSION**: Operating System version. It is an informational field. * **CICS JOB NAME**: You must specify the name of the CICS where the editran platform runs. Identification needed so batch processes can communicate the requested process to that CICS. * **CICS APPLICATION NAME:** You must specify the name of the CICS application where the editran platform runs (it may be the same name as the job). Identification needed for EXCI and TCP/IP processes. * **CPU NAME**: This is the name of the CPU where the CICS with editran/P installed is located. It is used for environments with several machines and for the user interfaces to communicate to editran/P the action to perform. * **EXECUTION ENV.**: Specifies the Execution Environment used by the product. Values are: E (Production environment), D (Development or testing), or H (Homologation, valid only for Indra). Recommendation: E * **MAX NUMBER OF CONNECTIONS**: Maximum number of transmission sessions that editran can manage simultaneously. It must be consistent with the number of possible cvcs to connect. When editran generates a call, it checks the number of sessions pending connection or connected. If this number is greater than the maximum cvc, it does not manage the request. In incoming calls, it accepts the call as valid, since the network has clearly provided a cvc and this was available. If an outgoing call reaches the maximum cvc limit, it generates a connection time-out until retries are exhausted. * **JCLS NOTIFICATION (M/E)**: The possibility has been implemented to start the messages that EDITRAN/G communicates to CICS through EXCI (this had been done via a MODIFY). In the local environment operator, a new parameter appears to choose such functionality (MODIFY or EXCI). If the last option is chosen, it will be sent through the generic connection (see exci buffer definition). The advantage of this option is that editran/G will know with complete certainty whether it has been able to notify the message to CICS and no library authorization is required. ⚠️Recommendation: E. {% hint style="info" %} ℹ️ This parameter also controls that access to editran files from batch processes is done via EXCI (definitions the same as for EXCI-type buffers, [Definition and Management of Buffer Files](/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files.md)). {% endhint %} * **NAMES OF THE PROCEDURES** editran: They will be those provided in the installation, ZTBGP1, ZTBGP2, ZTBGP3, ZTBGP4 and ZTBGP6, or the name they have been given in the local entity.
EDITRAN TRANSACTIONS: * **CORE**: EDITRAN core (default ZTB0). * **INTERFACE**: Communication interface with batch processes (ZTBI). * **MESSAGES**: Display of informational messages to the EDITRAN operator (ZTB8). * **T/O:** Time-Out or Timer process (ZTBT). * **MENU**: Main editran menu with its Interactive facilities (ZTBM). * **OPERATOR**: Operation request menu (ZTBO). * **FILES**: File Query menu (ZTBF). * **ADMINISTRATOR**. Administrator menu (ZTBD). * **LOCAL LINE MONITORING**. Transaction to monitor the different local lines (ZTBC). For more information, consult the user\_manual-editran-CICS\_StatisticsAndMonitoring. * **INCIDENTS**. Incident management and "ABEND" of the other transactions (ZTB9). * **STAT. MGT**. Transaction for Statistics Query (ZTBE). * **STAT. MGT**. Transaction for Statistics Management (ZTB3). * **EXCI (CICS).** Transaction for managing EXCI matrix buffer files (see the user\_manual-editran-CICS\_bufferFileManager) (ZTBG). * **TCP API.** Child client-server transaction for TCP/IP (ZTBB). * **TCP PLTINIT.** Startup transaction for the TCP/IP listeners (ZTBZ). If you decide not to call it that, consult the user\_manual-editranTCP-CICS\_technicalDocumentation, startup PLT specifications. * **EXCHANGE KEY MANAGEMENT**. Transaction for it (ZTB2). For more information, consult the user\_manual-editran-CICS\_bufferFileManager. ℹ️ To learn about the programs associated with the above transactions, consult the user\_manual-Installation\_and\_User-editran-CICS\_v5.3.
## Screen 2 * **SIMULTANEOUS LISTENER CONNECTIONS**: It is the maximum number of active connections as a result of incoming calls to a listener. When a call arrives, the listener, if that event is not satisfied, passes the socket to the server child (which, when the transmission ends, informs the listener again that a socket is available again). In this way, multiple undesired transactions from being activated in CICS are avoided, and even bombing can be detected. If the listener detects that the number of active server children is equal to the number of simultaneous connections, it will not accept new incoming calls. In addition, in this situation, it will send a message to the core indicating this reason (this message will only be sent if no other similar event occurred in the last 2 seconds, preventing the core itself from suffering bombing by message reports that have had this event). When defining the listener to TCP, there is a BACKLOG parameter, which means that if, for example, 40 calls are received at the same time and its value is 20, it automatically rejects 20. > ⚠️Recommendation: The value of this field must be less than BACKLOG and only affects incoming connections through a specific port. * **TCPNAME:** Name of the TCP/IP address space whose stack is attached to CICS. * **SEND TIME-OUT IN MILLISECONDS. (001-999)**.: When data is sent to the network, if the buffer fills up, a process is performed to see if there is data on the network to read. Up to now, this process was carried out with a delay of 1 second (to millisecond = 999). This process slows down transmissions in large systems, especially when there are few sessions simultaneously. In entities with a low amount of MIPS, many concurrent sessions, etc., values below 999 may cause slowdown in CICS. > ⚠️Recommendation: If you have few concurrent sessions, you have MIPS available, and you want to increase transmission speed, set this value to 100 (100 milliseconds). In other cases increase the value to 999 (which indicates 1 second). If you have concurrent sessions, few MIPS, or the transmission speed is sufficient, set 999. * **USER DATA TIME-OUT MAX(MSS)**: It is (only for editran/TCP and editran/TX-PR), the maximum waiting time from when a connection request leaves or a connection indication arrives until the user data is responded to. In the case of an incoming call, the listener passes that time to the child server, which during that time must receive user data, pass it to the core, receive a response to it from the core, and resend it to the network. In the case of an outgoing call, the core sends that time and the connection data to the client process, which during that time must send user data, receive a response to it from the network, and return it to the core. > Also, it is used so that when the client-server process is in data traffic and tries to write into a buffer to send it to the remote side, tcp can respond that it has the buffer full. At that moment, this timer is activated and is only canceled if some byte is successfully sent to the network. If the described timer expires without the previous processes having completed, the established socket is released. > > Also, it is used so that when the client-server process receives a SAB message from the remote side and is started on the core, that timer is triggered, so that if the core does not release it within the described time, the socket is closed. > > With reference to the above, the listener has another 2 timers, taken from the EZACONFG file, so that all IP timers are parameterized: > > ACCTIME parameter. It is used to stay in wait, waiting for network events. During that time, the listener remains suspended waiting for what the network tells it without listening to other types of events (operator, termination plt, etc.). > > GIVTIME parameter. It is used so that when a call is accepted and the child server is started (givesocket), the listener remains in wait during that time or until it receives a response from the child server (takesocket). > > ⚠️Recommendation: this time should be relatively short, between 10 and 20 seconds. * **TCP-PX SEND BUFFER (LISTENER)**: Only applies to incoming TCP or Proxy connections. In reality, it only comes into operation when the connection is incoming and the remote side requests a RECEIVE. In that case, data must be sent. The listener process starts a server child process that imposes the buffer we indicate (if it is different from zero). Keep in mind that, if outgoing connections occur, the tcp-px send buffer does not take its value from here; it takes its value from the equivalent parameter at the transmission session level. The reason for applying this local environment buffer instead of the session buffer is that the session for which it will operate is not yet known, and it is necessary to point the server-child process buffer at that moment. In current zos versions the maximum value is 262144. Larger values are allowed in case future zos versions allow it. If zeros are specified, no send buffer is imposed on TCP-PX connections, and the value assumed is that of the IP stack. > ⚠️Recommendation. If you have few simultaneous connections, set the maximum value. If you have incoming connections and outgoing transmissions, set the maximum value. Otherwise, set zeros. Keep in mind that if, for example, you connect and send bursts of 50 messages of 4050 to a remote side, you will be placing 200,000 bytes in the buffer**.** * **TCP-PX RECEIVE BUFFER (LISTENER)**: Only applies to incoming TCP and Proxy connections. In reality, it only comes into operation when the connection is incoming and the remote side requests a SEND. In that case, data must be received. The listener process starts a server child process that imposes the buffer we indicate (if it is different from zero). Keep in mind that, if incoming connections occur, the TCP-PX receive buffer does not take its value from here; it takes its value from the equivalent parameter at the transmission session level. The reason for applying this local environment buffer instead of the session buffer is that the session for which it will operate is not yet known, and it is necessary to point the server-child process buffer at that moment. In current zos versions the maximum value is 262144. Larger values are allowed in case future zos versions allow it. If zeros are specified, no receive buffer is imposed on TCP-PX connections, and the value assumed is that of the IP stack. > ⚠️Recommendation. Try to check whether you can set maximum values. Keep in mind that if, for example, you connect and receive bursts of 50 messages of 4050 from a remote side, you will be placing 200,000 bytes in the buffer. * **FILE QUEUE FIELDS**. They are fields for monitoring pending file queue sends. * **PENDING FILES TIME-OUT MINUTES**: Time out in minutes after which a process is desired to control the files pending to be sent. Recommendation (for example, every 10 minutes) It does not seem logical to be monitoring permanently for consumption reasons. * **LOCAL LINE MONITORING FIELDS**: The statistics and alarms module is required. (see [Statistics and Monitoring](/documentacion-editran/ibm-editran-v5.3-cics-en/statistics-and-monitoring.md)) You must specify the ZTBC monitoring transid. These are fields for monitoring the different local lines. * **TO MINUTES**: Time out in minutes after which a process is desired to control the different local lines to monitor. Recommendation (for example, every 6 hours). It does not seem logical to be monitoring permanently for consumption reasons. * **MONITORING PROC.:** Procedure (ZTBGP9C) to be started when a down line is detected (or when it was down and becomes operational again). * **LINES TO MONITOR**. Selection of the local lines to monitor (ip, proxys). In turn, within Proxies, each line must be specified in option 1.9. The IP lines are those of the EZACONFG configuration file. * **SES.EDI/P REMOTE IMAGE**: Session with which the procedure will be notified and from which its JCL cards are taken (it must be defined). Note. If you include that session in the alarms mask, option 5.3, it can send an alarm (email, etc.), when events occur (positive or negative) on the line. If you do not define 5.3, everything that happens goes to the alarms log (option 5.1). * **CISPLEX-SYSPLEX FIELDS:** Fields to identify calls to the SYSPLEX-CICSPLEX APIs. You must have a license for this. * **CICSPLEX SM RELEASE(VERSION)**: Version of the CICSPlex SM (System Manager) software. * **NAME OF THE CICSPLEX (CONTEXT):** It is the logical name of the CICSPlex, which is a set of CICS regions under common administration. CONTEXT refers to the point of view from which you are operating (for example, a specific region or the entire plex). * **NAME OF THE SCOPE:** Indicates the scope of administration or operation, that is, which subset of resources is being worked on. * **FILE INSTALLATION PREFIX**: Maximum 11 bytes. Used for defining intermediate files and optionally application receive files. It must comply with MVS rules regarding the length of segments separated by periods. * **WORK UNIT NAME**: Generic storage unit for defining intermediate and work files. The space used by editran/G for these files is comparable to that of send or receive, being released after the presentation send or receive loads. * **SAVE TO SYSTEM LOG**: If S, the messages generated by editran/G are sent to the system log. If N, they are written to ZTBGFPRI whose DD is found in the editran/G procedures. * **VOLUME OR WORK POOL**: Specify the (V)olume or (P)ool of the intermediate files and buffers so that they are taken by default when the presentation session is created. * **WORK VOLUME**: Specify the name of the volume or pool of the intermediate files and buffers so that they are taken by default when the presentation session is created. * **ADJUST FILE CREATION SPACE (Y/N)**. If S is coded, it means that application files will be read to obtain their size and thus calculate the space that must be applied to the sender buffer, csbnedi, to each of the compressed send files and to each ZTBGF54 send file. If N is coded, it means that the old system will continue to be used, that is, the ESP.PRIM. (REGS) field of the presentation session profile will be used. * **USE DNS SERVER IN INCOMING CALL (Y/N)**: Indicates whether in incoming calls we are going to resolve the numeric IP by its symbolic name (reverse lookup). It is useful for all IP connection types. In the case of I (TCP) connection, the editran core can validate the remote IP. In the case of proxy connection, the core can validate the remote and local IP (Proxy machine). > ⚠️ Recommendation: If you do not have DNS in the sessions, indicate N. If you have DNS in the sessions and want to validate the remote IP (or local in the case of proxy), indicate S. Press ENTER to add. Press PF3 to cancel. ℹ️ The values of the local environment data are transferred to the corresponding presentation session values when these are added, as default values. ℹ️ Modifying the local environment is done exactly like adding it, but in this case the corresponding profile must have been previously created. When these data are modified, the coincident ones in the presentation sessions are also modified. ℹ️ Query is also the same, but the fields appear protected. It is accessed with option “C” without filling in the environment code. From the same screen from which the Local Environment is accessed, a Secondary Local Environment or Local Subenvironment is added (optional and as many as desired): A Subenvironment query is performed with option “C” and filling in the code to be queried. The generic query option is obtained by typing an asterisk in the first field of the subenvironment code, which will display this screen: ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 15:33:32 LOCAL SUBENVIRONMENTS N032 | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | LOCAL CODE..: * ******* * | | S SUBENVIRONMENT DESCRIPTION ALIAS | | - ------------- -------------------- --------- | | A 0009994 A ENVIRONMENT A0009994A AL9 | | A 0009994 0 DES A9994 SUBENVIRONMENT L0A | | A 0009998 0 IMS IMS | | Z 0009994 Z EXPIRED PRODUCTS Z0Z | | Z 0009994 0 EXPIRED ENVIRONMENT Z00 | | 0 0000003 0 THREE TRE | | 0 0000075 0 FFF P00 | | 0 0002103 0 ADF UNI | | 0 0006008 0 LIFETIME L08 | | 0 0006033 0 GENERALLI SEGUROS L63 | | 0 0008500 0 ADF CTI | | 0 0008910 0 TEST L33 | | 0 0009000 0 AA BES | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` The subenvironment screen is as follows: ``` ----------------------------------------------------------------------------- | 22/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 15:33:43 LOCAL SUBENVIRONMENT | ----------------------------------------------------------------------------- | USER:MIGRA-50 F-H:20071220-093904 | | | | | | | | LOCAL SUBENVIRONMENT CODE........: A 0009994 A | | | | | | SUBENVIRONMENT ALIAS.............: AL9 | | | | | | SUBENVIRONMENT DESCRIPTION...........: ENVIRONMENT A0009994A | | | | | | | | | | | | | | | | EXIT | ----------------------------------------------------------------------------- ``` The contents of the fields have the following meaning: * **SUBENVIRONMENT LOCAL CODE** The same as the associated profile. It refers to the Secondary Local Environment. * **SUBENVIRONMENT ALIAS**: Alias of the subenvironment. * **SUBENVIRONMENT DESCRIPTION**: Description of the Secondary Local Environment. It is an informational parameter. --- # 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/onesait-editran-administrator/local-environment.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.