> 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/installation/sysplex-cicsplex-environments.md).

# SYSPLEX-CICSPLEX environments

Editran has been adapted in its programming to be used in a CICSPLEX-SYSPLEX environment (affinities in this type of environment). There are certain commands that have been removed from the programming because they are incompatible (reqid, cancel, interval, TD queues, etc.). Specifically, a series of rules must be followed for its use:

1. ENQ-DEQ commands. Editran still uses this type of commands; however, they have been grouped:

* In editran, they use a single pattern (ENQMODEL=ZTB)

2. TS queues. Editran still uses this type of commands; however, they have been grouped into a single pattern (TSMODEL=ZTB)
3. INQUIRE-SET commands:

* The ZTBPO061-62-63-64 programs do an INQUIRE (term, file, task) and if the resource-remotesystem response tells us that it is on another system, we do a LINK to the same program on that other system. According to the affinity manual, the transids that do inq-set must be statically routed (at the tct level). In the definition guide manual it says that in addition to remotesystem (connection), which serves to route the request to another system, you can also specify exec link program sysid (remote system name) or through dynamic routing program. The jump rules are, in this order:
* If link with sysid is used, it executes on that specific system.&#x20;
* If link without sysid is used:
  * If DYNAMIC=YES (ppt) has been coded or PPT does not exist, the DRP (dynamic routing program) is called; in short, it executes on any system.
  * If DYNAMIC=NO has been coded, it executes locally.

To apply this option, program ZTBPO061 must be defined in all CICS except in the tor with remotesystem (stor), ZTBPO062 must be defined in all CICS except in the for with remotesystem (sfor), ZTBPO064, if you want to have the connection in a single CICS, must be defined in all CICS except in the system we want with remotesystem (sconection). ZTBPO063 is not mentioned because that is the 3270 termid on which work is done.

⚠️ Important: For the correct operation of the startup PLT of the listeners in a CICSPLEX system, it is not only necessary for the Editran CICS to be defined in CPSM, but also for them to connect to it (parameter CPSMCON=LMAS in the SIT). This is necessary so that the list of Editran CICS can be retrieved. It is also necessary for the system to determine that it is a CICSPLEX that the following fields of the local environment are filled in:

```
CICSPLEX-SYSPLEX FIELDS............:   CICSPLEX SM RELEASE(VERSION):     
 CICSPLEX NAME (CONTEXT).:          SCOPE NAME........:         
```

&#x20;


---

# 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/installation/sysplex-cicsplex-environments.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.
