> 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/tcp/autom.-sockets-for-cics-tcp-ip-start-stop-through-plt.md).

# AUTOM. SOCKETS FOR CICS TCP/IP start-stop (THROUGH PLT)

1. AUTOMATIC startup (PLTPI) To start automatically, make the following entry in the PLTPI after DFHDELIM:

```
DFHPLT TYPE=ENTRY,PROGRAM=EZACIC20
DFHPLT TYPE=ENTRY,PROGRAM=ZTBPOTCI
```

2. AUTOMATIC shutdown (PLTSD) Make the following entry before DFHDELIM:

```
DFHPLT TYPE=ENTRY,PROGRAM=ZTBPOTCF
DFHPLT TYPE=ENTRY,PROGRAM=EZACIC20
```

In the startup PLT, the CICS sockets will be started and, once this is done, program ZTBPOTCI will be called, which will start a transid (ZTBZ). This transid, based on EZACONFG, will start all LISTENERs that exist (all those associated with the teleprocessing monitor where ZTBZ is run) and that contain the parameter SECEXIT = editran, so no manual action is required to activate them. It is mandatory to call ZTBZ by that name, and it has not been included in editran profiles, since if file accesses are made in the startup plt (to retrieve the name of the transid to be started), it is very likely that file access and read errors will occur (probably because CICS does not yet have them).

If you want the transid ZTBZ to have another name in your entity, run the JCL ZTBPJTCP against program ZTBPOTCI, indicating the new name of that transid (it must be previously defined in CICS). Next, define that transid in the profiles (local environment) (PLTINI TCP:). In the JCL to be run, the ZTBZ offset is specified (if the JCL fails, consult INDRA about it), the source transid (ZTBZ), and the target transid (in the following example NXZR):

```cobol
//* FIRST SEE  (CHECK THAT IT MATCHES)                               
//* SECOND REP  (CHANGE)                                               
//*                                                                     
//*        ZTBZ  -> "E9E3C2E9" OFFSET 01EA-TRANSID ZTBZ         
//*        NXZR  -> "D5E7E9D9"                                          
//*                                                                     
//**********************************************************************
//*   CHANGE OF EDITRAN TRANSACTION NAMES                      *
//**********************************************************************
//P1   EXEC  PGM=AMASPZAP                                               
//SYSLIB  DD  DSN=PUNTERO.INDRA.LOAD,DISP=SHR                           
//SYSPRINT DD  SYSOUT=*                                                 
//SYSIN  DD  *                                                          
  NAME ZTBPOTCI ZTBPOTCI                                                
  VER  01EA E9E3C2E9                                                    
  REP  01EA D5E7E9D9                                                    
/*                                                           

```


---

# 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/tcp/autom.-sockets-for-cics-tcp-ip-start-stop-through-plt.md?ask=<question>&goal=<endgoal>
```

`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.