> 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/tcp-ims-documentacion-tecnica/operaciones-de-administracion-y-configuracion.md).
# Administration and configuration operations
## Startup JCL for the processes
The BMPs that make up the Listener and the Client-Server will be run through two JCLs (ZTBPJLIS and ZTBPJTCP), which will be started manually and will remain active at all times.
The JOB name associated with the Listener (KILSZTCP) can be defined in the TCP configuration file ‘PROFILE’ assigned to the listening port for Editran.
```cobol
//KILSZTCP JOB (SNIM,KIT,,99),LISTENER,MSGCLASS=H,CLASS=A,
// MSGLEVEL=1
//TCPI EXEC IMSBATCH,MBR=ZTBPELIS,PSB=ZTBPELIS,IMSID=IMSP,
// PREFIX=IMSP,REGION=6M
//STEPLIB DD DSN=IMSP.RESLIB,DISP=SHR
// DD DSN=KI.EGDI.LOAD,DISP=SHR
//ZTBPFLIS DD DSN=KI.EGDI.ZTBP.JCLS(ZTBPFLIS),DISP=SHR
//SYSOUT DD SYSOUT=*
//
```
```cobol
//KICSZTCP JOB (SNIM,KIT,,99),CLIENT-SERVER,MSGCLASS=H,CLASS=A,
// MSGLEVEL=1
//ZTBPEBDA EXEC IMSBATCH,MBR=ZTBPEBDA,PSB=ZTBPBDDA,PREFIX=IMS510P
//STEPLIB DD DSN=IMSP.RESLIB,DISP=SHR
// DD DSN=IMSP.PGMLIB,DISP=SHR
// DD DSN=KI.EGDI.LOAD,DISP=SHR
//DFSVSAMP DD DSN=IMSP.PROCLIB(DFSVSAMP),DISP=SHR
//SYSOUT DD SYSOUT=H
//SYSPRINT DD SYSOUT=H
//PRINTDD DD SYSOUT=H
//TCPIP EXEC IMSBATCH,MBR=ZTBPETCP,PSB=ZTBPETCP,IMSID=IMSP,IN=ZTCP,
// PREFIX=IMSP,REGION=6M
//STEPLIB DD DSN=IMSP.RESLIB,DISP=SHR
// DD DSN=KI.EGDI.LOAD,DISP=SHR
//SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATB2),DISP=SHR
//SYSOUT DD SYSOUT=*,OUTLIM=999999
//
```
## Stopping the processes
The Client-Server and the Listener can be stopped using MODIFY or STOP console commands.
F nnnnnnnn,STOP or P nnnnnnn.
The Client-Server can be stopped by sending it the message
ZTCx END
Where ZTCx is the name of the transaction assigned to the client.
As BMPs, they can also be stopped with the IMS command IMS /STO REG n ABDUMP
## Environment modification
First, the Local Environment will be modified.
The transaction or transactions associated with the Client Server (ZTC\* associated with program ZTBPETCP) are set up as TCP/IP CLIENT-SERVER.
The TCP/IP REGION is the name of the TCP defined in the TCPIP.DATA file. We can leave it blank so that the default is assumed.
The CHKP LIMIT (check-point limit) regulates the execution of synchronization points in the Client-Server. The 'messages' value indicates the number of DLI calls after which a 'check-point' is generated. It should be close to the maximum number of messages per transaction allowed at the installation for other applications. The 'minutes' value indicates the maximum time between two 'check-points'. It is used to prevent the Client from going for long periods without synchronization.
The T/O INTERVAL is the maximum time in milliseconds that the application will use to complete a connection or to wait for the arrival or sending of data through a 'socket'. It will be adjusted at the installation to match the response speed of the remote installations. Long intervals slow down transmission, while short intervals can increase CPU consumption.
INCOMING CALL T/O: indicates the waiting time for receiving connection data in an incoming call. Generally, an interval of around 1 or 2 seconds is sufficient, but in the case of overloaded networks or machines, or in the case of remotes with uncorrected programming issues, it is necessary to extend this time to the order of tens of seconds.
The SEND BUFFER and RECEIVE BUFFER allow the TCP buffer assigned to each 'socket' to be modified when it is not possible to do so in the TCP definitions. They modify the values assigned by default in the TCPCONFIG macro of the PROFILE.TCPIP file (TCPSENDBfrsize and TCPRCVBufrsize parameters). The buffer value must never exceed the maximums allowed in the TCPCONFIG macro. This value will be taken as the basis for the sessions, where it can be customized.
The EDITRAN PROXY indicates the IP address where the Editran/Px product is installed. This feature allows filtering of incoming or outgoing connection requests and traffic control. It is generally run on a machine located in the DMZ to serve as a screen between the Internet, or an extranet, and our internal network. The PORT refers to the port through which Editran/Proxy listens for our connection requests. To use this feature, in outgoing calls, it must be indicated in the session (USE PROXY parameter). Incoming requests can come in, either through the Proxy or directly, transparently.
These values will be carried over to all Editran Sessions.
```
21/06/26 14:26:10 LOCAL ENVIRONMENT MODIFICATION (1) EDITRAN 5.3
------------------------------------------------------------------------------
LOCAL CODE: 0 0009998 0 EDITRAN VERSION: 5.2 PHASE: 01
ALIAS : L00 INSTALLATION NAME : INDRA IMS DEVELOPMENT
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.
SEND BUFFER : 262144 bytes RECEIVE BUFFER : 262144 bytes
PROXY IP ADDRESS PORT
010.055.000.017 07778
editran.indra.es 07778
```
## Remote modification
The CONNECTION TYPE will be set to ‘I’, it appears by default and cannot be modified. ‘USE PROXY TCP/IP= S’ so that outgoing calls are routed through the Proxy. The SEND BUFFER and RECEIVE BUFFER allow the TCP buffer assigned to each ‘socket’ to be modified when it is not possible to do so in the TCP definitions. They modify the values assigned by default in the TCPCONFIG macro of the PROFILE.TCPIP file (TCPSENDBfrsize and TCPRCVBufrsize parameters). The buffer value must never exceed the maximums allowed in the TCPCONFIG macro. This value will be taken as the basis for the sessions, where it can be customized. Remote IP addresses are recorded as REMOTE IP ADDRESS in numeric format (999.999.999.999) or as DNS names ([WWW.INDRA.ES](http://WWW.INDRA.ES)). The PORT refers to the port through which the remote Editran listens (generally 07777). If we have Editran Proxy, we can indicate
```
21/06/26 14:28:53 REMOTE ENTITY MODIFICATION EDITRAN 5.3
------------------------------------------------------------------------------
REMOTE CODE : 0 0009999 0 NAME: REMOTE TESTS PG VERSION: 5.2
CONNECTION TYPE : I (I=TCP/IP) USE PROXY TCP/IP (S/N): S
SEND BUFFER : 262144 RECEIVE BUFFER : 262144
CORE TRANSACTION: ZTB2
REMOTE IP ADDRESS (TCP/IP) PORT
172.022.242.194 07777
editran.test.indra.es 07779
```
These values will be carried over to all Editran Sessions.
## Adaptation of the Listener startup JCL
The Listener process relies on a configuration file to adapt certain values in the installation.
```cobol
//KILTZTCP JOB (SNIM,KIT,,99),LISTENER,MSGCLASS=H,CLASS=A,
// MSGLEVEL=1
//TCPI EXEC IMSBATCH,MBR=ZTBPELIS,PSB=ZTBPELIS,IMSID=IMSP,
// PREFIX=IMST,REGION=6M
//STEPLIB DD DSN=IMST.SDFSRESL,DISP=SHR
// DD DSN=KI.EGTI.LOAD,DISP=SHR
//ZTBPFLIS DD DSN=KI.EGTI.ZTB.JCLS(ZTBPFLIS),DISP=SHR
//SYSTCPD DD DSN=SW.TCPIP.SEZAPARM(TCPDATB4),DISP=SHR
//SYSOUT DD SYSOUT=*
//
TCP NAME, TCPNAME=TCPIPB
NAME OF THE CLIENT/SERVER TRANSACTION, SERVER=ZTCP
NUMBER OF CONNECTIONS THE LISTENER ACCEPTS, CON-PTE=0050
TIME-OUT INTERVAL FOR PASSING CONNECTIONS, SEC:MSG-TO=030:000
PORT ON WHICH I WILL LISTEN, PORT=7777
TIME BETWEEN 'CHECK-POINTS' (MINUTES), CHKP=060
```
As **TCPNAME** the name of the TCP region that is registered in Profiles is entered. If we leave it as spaces, the default value for that JCL (SYSTCPD card) will be used. The Listener and its Client-Server must run in the same TCP region.
THE **SERVER** corresponds to the Client-Server transaction (ZTCP).
CON-PTE indicates the number of pending connection requests that the Listener can accumulate without being processed.
**SEC:MSG-TO** indicates in seconds and milliseconds the maximum time that the Listener will wait for the Client-Server to process a connection request from the remote. These intervals will be extended if long response times occur in the Client-Server.
**PORT** points to the local port through which the application will receive the connections. Traditionally, 7777 is assigned. This is the value that can be specified in the PROFILE file as the EDITRAN port. The remote Editrans will list this port in the sessions they have defined with us. It is not necessary for one end and the other to listen on the same port number. It is enough that the local session port is correctly associated with the remote listening port and vice versa.
**CHKP** limits the maximum time interval (in minutes) to perform 'check-point'. It is analogous to the CHKP LIMIT parameter defined in the Environment for the Client Server. It ensures that the LISTENER performs synchronization from time to time.
**BUFFER** is used to modify the send and receive buffer value assigned to the 'socket', for all incoming calls. It has the same meaning as the environment SEND AND RECEIVE BUFFER 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-ims-en/tcp-ims-documentacion-tecnica/operaciones-de-administracion-y-configuracion.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.