> 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/operacion/primerospasos/administrador-de-onesait-editran/entorno-local.md). # Local environment ## Local environment This screen is accessed with option 1 of the administrator menu, 1.1 of the general menu, and by performing or cancelling the invoked function. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:10:15 LOCAL ENVIRONMENT 5.3 | ------------------------------------------------------------------------------ | | | | | | | A ADD | | | | B DELETE | | | | C QUERY | | | | M MODIFICATION | | | | | | | | OPTION : M | | LOCAL CODE : | | | | | | | | | ------------------------------------------------------------------------------ ``` ℹ️The General Local Environment (unique) will be created, where the following screens will appear: ### Primary local environment parameters (1) ``` 21/06/26 11:10:22 LOCAL ENVIRONMENT MODIFICATION (1) EDITRAN 5.3 ------------------------------------------------------------------------------ LOCAL CODE: 0 0009998 0 EDITRAN VERSION: 5.3 PHASE: 01 ALIAS : L00 INSTALLATION NAME : INDRA IMS ENVIRONMENT CONNECTION DATA MAX NO. OF CONNECTIONS: 999 TCP/IP REGION : CLIENT SERVER : ZTCP ZTC1 CHKP LIMIT : 0200 messages 010 minutes TCP T/O INTERVAL : 000200 msec. INCOMING CALL T/O: 30 sec. SENDING BUFFER : 262144 bytes RECEIVING BUFFER : 262144 bytes PROXY IP ADDRESS PORT 010.055.000.017 07778 editran.indra.es 07778 ``` * **LOCAL CODE**: Editran User Entity Identification Number. With this code it can be recognized by all Entities interconnected with Editran. * **EDITRAN VERSION**: Editran version (in 9.9 format): Must be 5.3. * **PHASE**: Last update of the Editran version (in 99 format). * **ALIAS**: Prefix for identifying files in the loading processes. It must comply with MVS rules for the name of a file. The processes before and after the transmission of the Editran interface use auxiliary files whose name begins with a general prefix for the entire installation, followed by this alias. The alias is associated with this local code. If other local codes are available, we can distinguish the files of each environment by assigning a different alias to each local code. * **INSTALLATION NAME**: Description of the General Local Environment. It is an informational parameter. #### Connection data. * **MAX NO. OF CONNECTIONS**: Maximum number of sockets supported by Editran/TCP. * **TCP/IP REGION**: Name of the installation's TCP/IP procedure through which the sessions will be interconnected. If no region is specified, the IP stack corresponding by default to the IMS regions will be used. * **CLIENT SERVER**: Name of the transaction or transactions that will manage the connections, both local and remote, and the data traffic, in both directions, of the sessions that connect via TCP/IP (ZTCP by default). The values entered here will be expanded to the sessions and may be customized to balance traffic. * **CHKP LIMIT (messages, minutes)**: Number of calls to DLI or elapsed time that triggers the generation of an IMS 'check-point' within the Client / Server. When the indicated number of messages is processed, or this time interval is reached with no activity, whichever occurs first, a CHKP macro is generated. * **TCP T/O INTERVAL**: Time that the client-server waits (in 'wait' mode) to check an event. * **INCOMING CALL T/O**: Waiting time for reception of connection data in an incoming TCP call. Marks the maximum interval between acceptance of the incoming call and reception of the session identification data. * **SEND/RECEIVE BUFFER**: Buffer assigned to the socket in outgoing TCP connections (Send / Receive buffer size). In incoming connections, the BUFFER parameter from the ZTBPFLIS configuration file of the 'listener' is applied. This parameter will be used as a general value for the sessions and may be customized in them. If this field is not filled in, the buffer will take the size defined by default in the TCPCONFIG macro of the PROFILE.TCPIP file (TCPSENDBfrsize and TCPRCVBufrsize). In the receive buffer, a value greater than the TCPMAXRCVBufrsize of the TCPCONFIG macro cannot be entered. * **PROXY IP ADDRESS and PORT**: Address and listening port of the Editran/PX product used to filter IP connections between Editran and the extranet (item 6). ℹ️By pressing PF8 you move to the second screen (which is mandatory in the creation process), where the transaction names corresponding to the Editran processes are specified. ### Primary local environment parameters (2) ``` 21/06/26 11:11:10 LOCAL ENVIRONMENT MODIFICATION (2) EDITRAN 5.3 ------------------------------------------------------------------------------ EDITRAN TRANSACTIONS CORE : ZTB1 GENERAL MENU: ZTBO PROFILE ADMIN.: ZTBJ EDITRAN/E MGMT: ZTBE TIME-OUT : OPERATOR : ZTBO AD.EDITRAN/GC: ZTBD C.EDITRAN/E: ZTBC LOG/TRACE : ZTBO FILES : ZTBO AD.EDITRAN/FF: ZTBK ALARM ADMIN: ZTBL NETWORK MONITORING PROCESS: ZTBEJMCO TRANSACTION: ZTBM QUERIES PORT: 77770 TIMEOUT: 20 sec ENCRYPTION FIELDS LOCAL LABEL : LEDITRAN REMOTE LABEL : REDITRAN BATCH INTERFACE PROCEDURES PROCESS : ZTBPJIG BEFORE SEND : ZTBGP1ID BEFORE RECEIPT: ZTBGP2ID TRANSACTION: ZTBI AFTER SEND: ZTBGP3ID AFTER RECEIPT.: ZTBGP4ID EXCEPTION PROC. : ZTBGP5ID STATE MODIF.: ZTBGP6ID FILE PREFIX: KI.EGDI SAVE IN SYSTEM LOG (Y/N): S WORK UNIT: SYSDA (SYSDA,VIO,..) ADJUST FILE CREATION SPACE (Y/N): S WORK VOL. OR POOL (V/P): P WORK VOLUME: DEVELOPMENT JCL CARDS,S: //KIIMSPR JOB (SNCE,KIT,,99),PRUEBA,CLASS=A,MSGLEVEL=1, // MSGCLASS=H //* //* //* ``` #### Editran transactions. * **CORE**: Editran core (default ZTB1). It is the transaction that supports data traffic. It is transferred to Sessions when they are created and can take different values per session. In environment modification, the new value will be transferred to those sessions whose core matched the environment's. * **TIME-OUT**: Time-Out process or Timer. It allows two options: * If the transaction name is specified (default ZTBT): * Editran processes will send Time-Out activation messages to this transaction. * The specified transaction will remain permanently scheduled (making 'WAIT' macros) as long as there are pending TIMEOUTs. * If left blank (recommended option): * Activation messages will not be sent * The T.O. transaction will not do Wait * The T.O. transaction must be invoked periodically by an external mechanism to Editran implemented by the installation. * **LOG/TRACE**: Presentation of informational messages to the Editran operator (default ZTBO). * **GENERAL MENU**: Editran Main Menu with its Interactive facilities. * **OPERATOR**: Operations requests menu. * **FILES**: File inquiry menu. * **PROFILE ADMIN.**: Editran profile administrator menu. * **EDITRAN/GC ADM.**: Only if the optional Editran/GC module is available, Exchange key management. * **EDITRAN/FF ADM.**: Only if the optional Editran/FF module is available, Electronic File Signature. * **G.EDITRAN/E and C.EDITRAN/E**: Only if the optional Editran/E module is available, Statistics and Monitoring. See the documentation for that module. * **ALARM ADMIN.**: Only if the optional Editran/EA module is available, Alarm Control and Management. See the documentation for that module. #### Network monitoring. In the event that gateways (Editran/PX) are available in Editran, their operation can be monitored by checking their activity automatically or through the application operator; for this, it is necessary to implement the following parameters: * **PROCESS and TRANSACTION**: Name of the procedure in which the program responsible for the automatic monitoring of local network resources is executed. The transaction is the one associated with said program (See manual [Monitoring Statistics and Alarms](/documentacion-editran/ibm-editran-v5.3-ims-en/estadisticas-monitorizacion-y-alarmas.md)) * **QUERIES PORT**: IP port of the “query server” on the gateway that has said server associated (default: 8120). For more information, consult the manual corresponding to the gateway: [Proxy](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/IBM/5.3/IMS/operacion/primerospasos/administrador-de-onesait-editran/broken-reference/README.md) * **TIMEOUT**: Allowed waiting interval for the query server to respond to a request. #### Batch Interface * **PROCESS and TRANSACTION**: Name of the previous and subsequent user procedures for the transmission. This value will be supplied by default in the Process and Transaction fields of the session screen. * **PROCEDURES**: They will be those provided in the installation, ZTBGP1, ZTBGP2, ZTBGP3, ZTBGP4, ZTBGP5 and ZTBGP6, or the name that has been given to them in the local entity. * **FILE PREFIX**: Maximum 11 bytes. Used for the definition of intermediate files and, optionally, application reception files. It must comply with MVS rules regarding the length of dot-separated segments. * **WORK UNIT**: Generic storage unit for defining intermediate and work files. The space used by Editran for these files is comparable to that of sending or receiving, and is released after the sending or receiving presentation loads. * **WORK VOLUME OR POOL (V/P)**: Specify the volume (V) or pool (P) of the intermediate files and buffers so they are taken by default when the presentation session is created. * **SAVE IN SYSTEM LOG (Y/N**): If Y, messages generated by Editran are sent to the system log. If N, they are written to ZTBGFPRI whose DD is located in the Editran procedures. * **ADJUST FILE CREATION SPACE (Y/N)**. If Y is coded, it means that application files will be read to obtain their size and thus calculate the space for the CSBNEDI file, for each compressed send file, and for each ZTBGFE54 send file. If N is coded, it means that the ESP.PRIM. (REGS) field of the presentation session profile will be used. * **WORK VOLUME**: Specify the name of the volume or pool of the intermediate files. * **JCL ENTRIES**: The necessary ones to launch the corresponding procedure. Simultaneous execution of several processes of the same presentation session is allowed, whether launched by the application or by JCL. In addition, the JOB name in those launched by the application behaves as follows: * Launching the JCLs of the procedures with different names to facilitate execution control for operations departments. Since the JOB names are different, they can be executed concurrently. Given Job-name as the JOB name assigned in the first specified JCL entry, the assignment mode is as follows: * Job-name of 8 characters. It is not modified. * Job-name of fewer than 8 characters. A suffix X is added, whose value is assigned according to the requested action using the following criterion:
FUNCTIONDESCRIPTIONSUFFIX
1Send load request1
2After sending2
3Send request3
6Receive initialization6
7Receive download7
8Receive request8
5Interrupt sending5
9Interrupt reception9
10 and 11 (send)Send status modificationA
10 and 11 (receive)Receive status modificationB
ℹ️Press ENTER to create. Press PF3 to cancel. The values of the local environment data are transferred to the corresponding ones of the presentation sessions, when these are created, as default values. In the case of the fields **SEND BUFFER, RECEIVE BUFFER and CORE TRANSACTION**, they are only transferred to the presentation sessions if these are not specified in the remote Modifying the local environment is done exactly the same way as creation, but in this case the corresponding profile must already have been created beforehand. When these data are modified, the matching ones in the presentation sessions are also modified. Inquiry is also the same, but the fields appear protected. It is accessed with option “C” without filling in the environment code. ## **LOCAL subenvironment** From the same screen from which the Local Environment is accessed, a Secondary Local Environment or Local Subenvironment is created (optional and as many as desired). To do this, type option “A” together with the desired subenvironment code (this code must be specified in the product license file). After pressing “ENTER”, the following screen appears: ``` 21/06/26 11:11:38 LOCAL SUBENVIRONMENT MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ LOCAL CODE : A 0009998 0 LOCAL SUBENVIRONMENT NAME: NAME A9998 SUBENV SUBENVIRONMENT ALIAS : LA8 CORE TRANSACTION : ZTB2 ``` * **LOCAL CODE**: Editran User Entity Identification Number. With this code it can be recognized by all Entities interconnected with Editran. * **LOCAL SUBENVIRONMENT NAME**: Description of the Secondary Local Environment. It is an informational parameter. * **SUBENVIRONMENT ALIAS**: It has already been explained in the primary local environment * **CORE TRANSACTION**: It has already been explained in the primary local environment The inquiry of a subenvironment is performed with option “C” and by filling in the code to be queried. The generic option for subenvironment handling is obtained by typing an asterisk in the first field of the subenvironment code, showing this screen: ``` 21/06/2 11:12:25 LOCAL SUBENVIRONMENT MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ SEL CODE ALIAS DESCRIPTION --- --------- --------- -------------------- A0009998S A8S CARAMBA A00099980 A80 NON-PRINCI SUBENVIRONMENT A1111111A 1 1 ERROR F00099980 F IMS J1111111J J11 HELLO HELLO T00099980 MIGRATION TESTS Z9999999Z Z9Z ZZZZZZZZZZZZZZZZZZZZ 000000003 E 000000004 C 000000005 5 000000006 S 000000007 7 000000008 O 000000009 N 000000010 D 000000011 ELEVEN 000000012 DOOOOOOO..CE ``` --- # 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/operacion/primerospasos/administrador-de-onesait-editran/entorno-local.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.