> 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/download-cics-version/operations-to-perform-upon-receiving-the-product/software-download.md).

# Software download

Once the software has been received, it will be downloaded into the libraries described (standard-type reception), which will be created in the IEBCOPY JCL;

JCL libraries with the following characteristics: 

```cobol
//JCLS   DD     DSN=Puntero.JCLLIB,DISP=(NEW,CATLG),                         X
//              DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=6160),               X
//              SPACE=(CYL,(1,1,15)),UNIT=Unidad,VOL=SER=Volumen
```

EXECUTABLES library with the following characteristics: 

```cobol
//LOAD   DD     DSN=Puntero.LOADLIB,DISP=(NEW,CATLG),                        X
//              DCB=(DSORG=PO,RECFM=U,LRECL=0,BLKSIZE=19069),                X
//              SPACE=(CYL,(25,0,100)),UNIT=Unidad,VOL=SER=Volumen
```

ℹ️ As many libraries as desired can be downloaded, that is, it may be that for some client it is of interest to create several executable libraries. In that case, all of them must be included in the editran procedures and in the CICS startup. In this manual, it will be treated as though all the executables are in the same library.

If a license file is received, we will leave it without doing IEBCOPY, pending license update.

👉 It is recommended that in this library creation step, the following be identified with the created pointer:

* Editran.
* Version received. For example, V5R2. In the case of buffer files, when they are received, it is recommended not to enter a version. The reason is that in Editran the dsname of the buffers is stored in the profiles file, so that, if a version is updated, the same buffer should still be valid. If this is not done, when the version is updated, the FCT should be refreshed with the new name and all the Editran profiles. Another possibility is that the buffers do not change their name, but have a pointer to an old version, but this seems rather unclean.

ℹ️ It is important that the names of libraries and pointers do not vary. The reasons are:

* The names we give to the libraries, or to the pointers, will be updated in all the JCLs and procedures.
* The executable library name will be in the CICS startup.


---

# 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/download-cics-version/operations-to-perform-upon-receiving-the-product/software-download.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.