> 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/open-v5.2.1-en/windows/plataforma.md).
# Editran/P management
## Onesait Editran/P Manager
When selecting the option of *Editran P Menu* the Editran/P manager menu will appear.
If this is the first time Editran is started, the local environment data must be entered (see chapter **Local environment.**) and then start Editran.
### User interface description.
In the Editran WINDOWS screens, three areas can be distinguished:
* **(1) Menus.**
> In the menu area, the different options for operating Editran are selected:
>
> Starting and stopping Editran, reports, system administration...
>
> 
* **(2) Toolbar.**
> In this area, different icons appear that indicate actions equivalent to those in the menus; when hovering over each icon, information associated with that icon's action appears at the bottom of the screen.
>
> 
* **(3) Information**
> In this area appears the information that Editran sends to the operator:
>
> Session.
>
> Emission and reception states.
>
> Send and receive counters.
>
> Information text or messages from the remote operator.
**Help**
Editran WINDOWS has a help system. Thus, when the key is pressed **F1** or the button *Help topics*, a window with the help text appears.
**About**
Indicates the version of Editran and the compilation date; it also contains two informational buttons for the license and distributor.
### Starting and stopping Onesait Editran/P
To start and stop Editran, select the File option from the General Menu and then choose *Start Editran* or Stop *Editran.*
This toolbar icon is equivalent to starting and stopping Editran via menus:
Positioning the cursor and clicking on the traffic light performs the start action in Editran/P and Editran/G, leaving the traffic light green.
Positioning the cursor and clicking on the green traffic light symbol performs the stop action in Editran/P and Editran/G, leaving the traffic light red:
### Onesait Editran/P Operator
To manage exchange sessions, select the Editran/P tab in the main menu, showing the following options:
#### Connection.
To manually establish the physical connection with a remote Editran and start the transmission process, you must first select a specific session in the information screen (place the cursor over the chosen one and click with the left mouse button) and then choose the Connection menu option. The request is not allowed when the local Editran operating mode is Server.
This request is made automatically when requesting a send or receive request if the value S is specified in the parameter *AUTOMATIC CALL* in the session profile.
In the information area, indications appear about the result of the request (association established or not).
Pressing this toolbar option performs the same action as through the menu:
#### Release.
To manually release the existing connection for a given session.
Pressing this toolbar option performs the same action as through the menu:
#### Send.
To start the local sending of a file or files, select the Send option.
The request is not allowed when the local Editran operating mode is Server.
Pressing this toolbar option performs the same action as through the menu:
#### End of Sending.
To request the forced end of the local sending (sending interruption), select the option *End of Sending*
The request is not accepted when the local Editran operating mode is Server.
Pressing this toolbar option performs the same action as through the menu:
#### Receive.
To start receiving a file or files that the remote must send.
The request is not accepted when the local Editran operating mode is Server.
Pressing this toolbar option performs the same action as through the menu:
#### End of Reception.
To request the forced end of the local reception (reception interruption), select the option *End of Reception*
The request is not accepted when the local Editran operating mode is Server.
Pressing this toolbar option performs the same action as through the menu:
#### Message to the remote.
Used to send a text message to the remote. A connection with the remote Editran recipient of the operator message is required.
The following screen will appear, where the text to be sent will be entered:
Pressing this toolbar option performs the same action as through the menu:
### File inquiry.
> 
#### Local file inquiry.
To obtain information from the control record of the local send or receive buffer file, select the option **Local file inquiry**.
The following menu will appear:
You must select File type (Send or Receive) and then choose the session.
The different fields will be filled in with the data from the control record of the local send or receive file for the specified session.
For a query of the local send file (by entering Send in the File type field), the following information is obtained:
#### Remote inquiry of send files.
To query the remote send file, select the Remote file inquiry option and then choose Send. The local Editran program will send the inquiry message to the remote, leaving the local one waiting to receive the remote response. This response will be displayed on the following screen. A connection between both ends must have been previously established.
#### Remote inquiry of receive files.
To query the remote receive file, select the Remote file inquiry option and then choose Receive. The local Editran program will send the inquiry message to the remote, leaving the local one waiting to receive the remote response, which will be displayed on the following screen. A connection between both ends must have been previously established.
#### Log inquiry.
All informative messages that Editran has sent to the operator are displayed.
To consult these records, select the Log inquiry option. The following menu will appear:
Select the session, date and time and then press OK Selection
In the case of a general query, select \ in the section *Session*.
Messages are shown from the defined date to the current date of the query.
If 00:00:00 is defined in *Time* it will show all messages regardless of the time.
The file **editranp.log** is treated cyclically.
### Onesait Editran /P Administrator
To access the Editran administration menu, select the Administrator option from the Editran/P menu.
The following options will be presented:
#### Local environment.
If this option is selected, the following screen will appear:
* **Local environment code**
> Enter the identification number of the entity using Editran. With this identification number it will be recognized by all interconnected entities.
* **Name**
> Enter the description of the local environment. This field is for information only.
* **Maximum number of sessions**
> The maximum number of exchange sessions that can run concurrently at a given time can be specified.
* **TCP/IP Connection TimeOut (seconds)**
> It is the maximum waiting time from when the connection of a *socket* remote until the session data is exchanged that definitively establishes a TCP connection in editran/P. This timeout prevents other applications from connecting indefinitely to the port used by Editran. If you do not want to enable this timeout, set it to 0.
* **IP ADDRESS**
> The private IP address of the local machine in a TCP/IP network; it supports up to 3 different addresses with 3 listening ports for each address.
>
> If 0.0.0.0 is defined, Editran will listen on all IPs of the machine.
#### Session management.
To connect and perform sends and/or receives with a remote Editran, the parameters describing the session profile must be specified, and it is essential that the local environment has been previously registered (see 3.5.1 Local environment.).
As many sessions will be registered as different connections you want to establish.
Select the option **Session management** in the Administrator menu.
**General Data**
> 
The following must be specified **General Data.**
Pressing the button **Default** the fields are filled with default values.
* **Session**
> Session name identification.
* **Version**
> Version of the remote Editran system (5.2, 5.1, 5.0, or 4.1)
* **Local**
> Local environment identification code.
* **Local name**
> Name of the local environment associated with the session. This is for information only.
* **Remote**
> Remote center identification code.
* **Remote name**
> Name of the remote center associated with the session. This is for information only.
* **Application**
> Identification code of the user application of the Editran system transmission service.
* **Application name**
> Name of the user application. This is for information only.
**TCP/IP tab**
The TCP/IP tab contains the following fields:
* **Remote IP address**
> These are the IP or DNS addresses and TCP ports of the remote machine we want to connect to. Up to 6 addresses can be defined.
* **Validate Remote IP Address**
> If enabled, the IP addresses of the remote machine from which we expect to receive a connection will be validated; if the IP does not match, the incoming connection is rejected.
* **Save rotations**
> If we select this option and have more than one remote address, the order is changed by placing first the IP we managed to connect to.
* **Use Editran Proxy**
> Indicates whether the session will use **Editran/PX** to go out via TCP/IP.
* **Proxy IP Address**
> Indicates the IP address or server name **Editran/PX** to connect to.
* **Proxy Port**
> TCP listening port of **Editran/PX**.
**Options tab**
The **Options**.
Pressing the button **Default** the fields are filled with default values.
* **No. of records per sending block**
> Transmission burst length (number of records sent before receiving confirmation from the remote).
* **Buffer length**
> Length of the buffer file records. Values from 13 to 9999 bytes are allowed (with versions later than 5.2 only a value equal to or greater than 4050 is valid, and in HOST environments only 4050)
* **Calling end**
* **Local:** Only the LOCAL end can call.
* **Remote:** Only the REMOTE end can call.
* **Either:** Either end can call.
* **Traffic direction**
* **Send:** Only sending is allowed in this session.
* **Receive:** Only receiving is allowed in this session.
* **Send/Receive:** Sending and receiving can be done simultaneously.
* **Automatic call**
* **If** The session will be established automatically when the start of sending or receiving is requested.
* **No** A connection must be established before requesting send/receive.
* **CRC**
* **If** Cyclic redundancy code will be generated for each transmitted message; the CRC of each received message will be validated.
* **No** CRC is not calculated for outgoing messages nor validated for incoming messages\*\*.\*\*
* **Automatic disconnection**
* **If** The disconnection request is generated automatically when a send or receive finishes\*\*.\*\*
* **No** The disconnection is not generated automatically\*\*.\*\*
* **Operating mode**
* **Server** Neither sends nor receives can be requested (server). Only remote requests will be accepted.
* **Client** Both sends and receives can be requested (client).
* **Character set**
* **ASCII** The remote uses ASCII alphabet (UNIX and Windows environments).
* **EBCDIC** The remote uses EBCDIC alphabet (CICS, IMS, AS/400... environments).
* **Compression**
* **If** Compress the protocol data packets.
* **No** Uncompressed transmission.
* **Variable** Transmit compressed only when the size of the resulting data packet is smaller than the original.
* **LZW** LZW compression will be used in Editran/G.
* **Start time (HH:MM:SS)**
> Specifies the time of day from which transmission can start, expressed in hours (HH), minutes (MM), and seconds (SS).
* **End time (HH:MM:SS)**
> Specifies the time limit of day until which transmission can start, expressed in hours (HH), minutes (MM), and seconds (SS).
* **Time-out (Seconds)**
> It is the time interval, expressed in seconds, in which Editran waits to receive from the remote a response message to a previously sent control message.
>
> If the TIME-OUT period ends without a response being received, the same request will be sent again, starting a new waiting interval. This also applies to connection requests.
* **Synchronization Time-out (Seconds)**
> It is the time interval, expressed in seconds, in which Editran waits to receive from the remote a synchronization message for sending a block of data (burst). If no response is received by the end of this time, the message is sent again, up to the maximum number of retries.
* **Maximum number of retries**
> It is the number of times the previous TIME-OUT procedure is repeated.
**Cryptography tab**
> The following must be specified **Cryptography** of the session.
* **Cryptography**
* **Yes** If you want Editran/P cryptography.
* **No** If you do not want to use Editran/P cryptography.
* **Cryptography Version**
> This field is mandatory if Cryptography is enabled.
* **2.2** For the security subsystem of Editran/P version 2.2.
* **3.0** Cryptography compatible with CRIPTO/lib V3.0.
* **4.0** AES encryption and 2048 and 4096 RSA keys.
* **Key change V2.2**
> Selector for the cryptographic key change facility in the connection preamble.
* **Yes** Key change enabled.
* **No** Key change inhibited.
* **Key Exchange V3.0**
> When this facility is selected in cryptography version 3.0, the Editran/GC module will be responsible for providing the corresponding labels for the active keys for the subsystems indicated in the LOCAL KEY and REMOTE KEY parameters.
* **Confidentiality algorithm**
> Algorithm to use to encrypt the data.
>
> Leave blank if you do not want to encrypt the data.
* **DES** DES encryption with a single key.
* **TD2** DES encryption with a double key.
* **TD3** DES encryption with a triple key.
* **AES** AES-128 encryption.
* **AE2** AES-192 encryption.
* **AE3** AES-256 encryption.
* **Authentication algorithm**
> Algorithm to use to encrypt the keys, mandatory if a confidentiality algorithm exists.
* **DES** if you want to authenticate the ends (valid for versions 2.2 and 3.0).
* **RSA** if you want to authenticate the ends (valid for Version 3.0 and 4.0).
* **LOCAL KEY**
> Label of the DES auxiliary key or the RSA private key. Mandatory when the cryptography version is 3.0 or higher and authentication is enabled.
* **REMOTE KEY**
> Label of the DES auxiliary key or the remote RSA public key. Mandatory when the cryptography version is 3.0 or higher and authentication is enabled.
## Attachments
### Onesait Editran Components
#### Current schema
Editran is a modular product.
There are a number of components that we consider the most common (G, P, TCP/IP and Proxy), which are acquired by the vast majority of customers (although some choose not to have the Proxy), and additionally there is another series of modules that help improve the product's security, control, or functionality.
### Commands
#### EDItran
It is the program that starts and stops the Editran system.
* Syntax
The syntax of the command is:
> EDItran \[-t] \[-f] start | stop | status \[-s]
>
> -t Starts Editran with trace
>
> -f Ignores another Editran already started
>
> -s Windows only. Use this option if you do not want the window with the command result to be displayed.
>
> start Starts the Editran system
>
> stop Stops the Editran system
>
> status Gets the status of the Editran system
#### editranp
Main process of the Editran system. It is responsible for interacting with the different communication processes and with Editran/G. It is launched in the background when the Editran system starts.
#### editcp
Communication process when the protocol used for the connection is TCP/IP.
#### makelog
Creates an event file called editran.log that will contain a summary of the operations performed using Editran.
* Syntax
The syntax of the command is:
> **makelog** -n N
where **N** is the maximum number of entries (number of events) that you want to keep in the file.
* Example
You want to create an event file, editran.log, with capacity for 500 distinct entries.
The command must be executed:
**makelog** --n 500
If the system is used with a large number of simultaneous sessions, it is recommended to use 500 entries.
#### menup
Allows direct access to the Editran manager menu.
#### menucmd
Establishes a communication mechanism between applications or user programs and editran/P, allowing operations to be invoked unattended and automatically.
* Syntax
The syntax of the command is:
> **menucmd** s session x
>
> where **s** is the signal sent to request an operation from Editran, **session** is the session and **x** other options that depend on the type of operation or signal requested from Editran.
Specifically, the exact syntax of the command depending on the value of **s** is as follows:
> menucmd {E00|E11} \
>
> menucmd EOP \ \
The possible signals are:
* **E00** requests a connection request from Editran.
* **E11** requests a release request from Editran.
* **EOP** requests Editran to send a message to the remote operator.
#### copycfg
Utility to copy Editran profiles from another one used as a template.
* Syntax
The syntax of the command is:
> Usage: copycfg -s source\_session \[-d destination\_session] \[-n] \[-r remote\_code] \[-p | -a]
Where:
> -n : number of sessions to create.
>
> -s : source session.
>
> -d : destination session.
>
> -r : destination remote code.
>
> -p : copies only Editran/P sessions
>
> -a : creates Editran/G applications
This command allows registering Editran profiles starting from a session taken as a template. The source session is given in the option **--s**. By default, the Editran/P session and its corresponding Presentation in Editran/G are created, but this behavior can be changed using the option **--p** if you only want to create the session profiles.
The created profiles will depend on the chosen option:
* **Option -n**: Are created *\* sessions. These sessions are named the same as the original, adding an index. For example, if we start from PRUEBA and want to generate 5 more, they will be created from PRUEBA-1 to PRUEBA-5.
* **Option -d:** In this case the user decides the name of the created session, but this option is incompatible with the previous one.
* **Option -r:** By default, the created sessions are generated with the same local and remote code as the original. With this option the user can change the remote code of the new profile.
* Example
> To duplicate the INDRA-TEST session for a different remote, naming the new one editran-TEST, run:
>
> \>copycfg -s INDRA-TEST -d editran-TEST -r 000001230
>
> To create 10 sessions starting from PRUEBA, run:
>
> \>copycfg -s PRUEBA -n 10
#### printcfg
Editran session printing utility.
* Syntax
> Usage: printcfg \[ -lgrapsv ]
>
> Where:
>
> -l : Local Editran/G.
>
> -g : Editran/G presentations.
>
> -r : Editran/G remotes.
>
> -a : Editran/G applications.
>
> -p : Local Editran/P.
>
> -s : Editran/P sessions (Default).
>
> -v : Prints headers.
* Example
> LOCAL SESSION REMOTE APLIC LOCAL DIR REMOTE DIR
>
> \============================================
>
> INDRA-TEST W00005100 000099990 TEST TCP editran.indra.es
#### resetkey
Resets the encrypted exchange keys of a given session.
It must be used with great caution, since it leaves the keys in a state different from the original. It is essential to perform the same operation at the remote end so that synchronization in the key exchange is possible.
It should only be run if it is the first time the keys are used, or if the keys from the last exchange in the profiles file have been lost.
* Syntax
The syntax of the command is:
> **resetkey** \[session]
where session is the editran/P session. It must be written in uppercase, and if it contains any spaces, between double quotes: "
* Example
In an installation, it is desired to set the session TEST-INDRA key to an initial value.
The command must be executed:
> resetkey TEST-INDRA
#### importkey
The file *ckds.des* keeps the master key and DES auxiliary keys in the editran system. In version 5.02 the format has changed so that simple and double keys can be stored. Therefore, in some cases it may be necessary to import keys from previous versions.
For security reasons, to export the keys the user must know the value of the HMK it stores and must provide the first two hexadecimal octets as the password to access the file. It can be given as a command argument, but if it is not provided the user will be prompted.
* Syntax
The syntax of the command is:
Usage: importkey \[ -s ] \[-k\] -f\ \[--] \[labels]
> \-- : End of options. The rest of the arguments are labels
>
> -s : The source file contains simple keys
>
> -k\ : Password to access the file (HMK)
>
> -f\ : File that stores the keys to be exported
>
> labels: Labels of the keys to import
If no label is given, the command incorporates all keys in the source file whose label is not SI0000000000XX.
If the label of the key to be imported already exists in the destination file, the key will be updated with the value of the old one.
* Example
To incorporate the auxiliary key used by editran for sessions with cryptography 2.2, run the command:
> \> importkey -s -fc:\editran.520\ckds.des SI000000000016
To incorporate the user auxiliary keys by giving the access password as an argument, run:
> \> importkey -s -fckds.des.520 --kA1A3
#### printlog
Editran log printing utility.
* Syntax
> **printlog**
* Command options:
> -P Editran/P log
>
> -G Editran/G log
>
> -s session
>
> -f date DDMMYYYY
>
> -h time HHMMSS
>
> All parameters are optional
#### Onesait Editran Transmission Manager/GT
There is currently a task scheduler. To use this module, a special license including authorization is required.
For more information, consult the specific manual for *Editran/GT*.
#### NL Filter
The **nl** filter is used to convert lines from one system to another. This filter is limited to reading and writing lines. The usefulness of the filter lies in the physical difference between systems when representing text lines.
In general, a file containing lines is structured in one of two ways:
With fixed-length records (a fixed number of characters is always stored per line; for example, 100 characters for each line).
With variable-length records (line-end delimiters are used to separate the lines). These in turn have different separators on each system. The filter knows the UNIX ones.
To use the filter, simply tell it what the starting structure is (e.g. fixed records of 50 characters, or variable records with UNIX-type delimiter) and the structure we want to obtain. The filter will change the file structure to obtain the desired structure with the same content in each line.
* Syntax
> Usage: nl \[ -<#> | -v ] -i\ -o\ \[--] \[files]
>
> \-- : End of options. The rest of the arguments are files
>
> -<#>: Records of length # (fixed) without counting delimiters (Ex.: -80)
>
> -v : Variable-length records (default)
>
> -i\: Input format (Ex.: -id)
>
> -o\: Output format (Ex.: -on)
>
> \ can be: u (UNIX), d (MSDOS), n (no delimiter)
>
> files: Files to translate (stdin->stdout by default)
To indicate the type of record we are going to use (fixed or variable), we use the following options:
* **option -N** (where N is a number, e.g. 80): fixed records of N characters.
* **option -v**: variable records.
* To indicate the end-of-line delimiter used in the input file, use the **option -iX** (where X is 'n', 'u' or 'd').
* If X is n, the filter expects no end-of-line delimiter in the input file (in this case -N must have been used to indicate the record length since it must be fixed-length records).
* If X is u, the filter expects a '\n' delimiting each record. (unix type).
* If X is d, the filter expects a '\r\n' delimiting each record. (MSDOS type).
* To indicate the end-of-line delimiter to use in the output file, use the **option -oX** (where X is 'n', 'u' or 'd').
* If X is n, the filter does not write any delimiter after each line.
* If X is u, the filter writes a '\n' after each record.
* If X is d, the filter writes a '\r\n' after each record.
#### ediperfi
This is the command for administering Editran/P profiles.
You can consult the user manual *Profile Management* for more information about this utility.
### Files
#### CFG subdirectory
* **editranp.cfg**
Editran configuration file. Stores the local profile and the session profiles for remote entities. Used exclusively by Editran.
* **editranp.sdx**
Editran configuration index file.
* **ckds.des**
File where the auxiliary exchange keys of encrypted Editran sessions are located.
#### BIN subdirectory
* **editranp.msg**
File where the messages that editran presents to the editran operator are stored. Used exclusively by editran.
**SL subdirectory**
* **licencia.dat**
Editran license file. It is used to control the contracted functionality. If this file does not exist or its contents are altered, the Editran service cannot be started.
#### LOG subdirectory
* **editranp.out**
File where all outputs produced by the process are recorded **editranp** and the procedures and commands launched by this process. It is generated by redirecting the process standard output **editranp**.
* **editranp.log**
File created by the command **makelog**. It cyclically stores the summary of the operations performed by EDITRAN, so once the maximum number of entries is reached, it overwrites the oldest one.
It can be consulted from the editran menus and through the command ***printlog***.
#### DOC subdirectory
Editran documentation containing quick configuration and reference guides.
### Codes and messages to the operator
These codes are the ones reflected in the file **editranp.log** to indicate the different states through which a session passes. On the editran/P operator screen, they appear in the form of messages.
Next, the messages are listed with a brief explanation or recommended action, as appropriate:
***
| MESSAGE | EXPLANATION/RECOMMENDED ACTION |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Association established | Local association request accepted by remote end. |
| Remote association accepted | Association between applications accepted by the local end. |
| Start of transmission | Emission to the remote starts. |
| Connection made | A circuit has been established with the remote end |
| Remote connection rejected (Profiles) | Discrepancy in the remote and local profiles |
| Status query | Response to a query about the status of a session |
| Remote sender file query | The control record log of the remote emission buffer file has been requested for consultation. |
| Remote receiver file query | The control record log of the remote reception buffer file has been requested for consultation |
| Totals mismatch in sender process | In applications with totals control, the confirmed exchanged totals do not match (synchronism) |
| Totals mismatch in receiver process | In applications with totals control, the confirmed exchanged totals do not match (synchronism). |
| Emission aborted | A file emission to the remote has been aborted |
| Emission correct and finished | An emission has finished correctly |
| Local emission | Start of local file emission |
| Error opening file | An error occurred while opening a file |
| Error closing file | An error occurred while closing a file |
| Error writing file | An error occurred while writing to a file |
| Error reading file | An error occurred while reading from a file |
| Error in execution of the *SCRIPT* | An error occurred while executing a shell script. |
| Error in remote batch process | An error occurred while executing a remote shell script. |
| General interface error | An error occurred while executing a shell script. |
| Remote cryptography error (ERR##) | A cryptography error has occurred. See the Cryptography Errors section. |
| Remote error in compression/decompression | A compression/decompression error has occurred at the remote end. |
| Connection retries exhausted | The connection retries have been exhausted, according to the number of retries in the editran session profiles. |
| Synchronization retries exhausted | The synchronization retries have been exhausted, according to the number of retries in the editran session profiles. |
| Retries exhausted in sender process | The retries have been exhausted in the sender process for messages that require a response. |
| Retries exhausted in receiver process | The retries have been exhausted in the receiver process for messages that require a response. |
| Retries exhausted for emission | The emission start retries have been exhausted, according to the number of retries in the editran session profiles. |
| Retries exhausted for establishing session | The session establishment retries have been exhausted, according to the number of retries in the editran session profiles. |
| Retries exhausted for end of emission | The end-of-emission retries have been exhausted, according to the number of retries in the editran session profiles. |
| Retries exhausted for receiving | The emission start retries have been exhausted, according to the number of retries in the editran session profiles. |
| Connection exists. Batch request ignored | A connection request has been requested and it already exists. |
| Invalid calling end (profiles) | Incompatibility in the values of this field in the profile record. |
| Profiles file empty or does not exist | An error occurred while accessing the editran profiles file. |
| Reception file not ready | The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. Data exchange does not match. The exchange session number contained in the control records does not match. The emission/reception file is not loaded, or is not available for editran (the batch process specified in profiles is triggered). |
| Emission buffer file not ready | Response to remote file query. |
| Buffer files in incompatible state | The remote rejects the local request because its buffer file is not ready. It may have launched its previous automation corresponding to the request. |
| End of emission requested by operator | When the operator requests forced end of emission |
| End of emission requested by remote operator | When the remote operator requests forced end of emission. |
| End of reception requested by operator | When the operator requests forced end of reception. |
| End of reception requested by remote operator | End of transmission requested by the remote operator. |
| End of local transmission requested by the remote | When the remote requests end of reception (end of local transmission). |
| Remote emission impossible due to profiles | Check processes defined in the session profile. |
| Remote reception impossible due to profiles | Check processes defined in the session profile. |
| Start of reception | When reception of the remote file begins. |
| Remote application release | The connection has been released by the remote application. |
| Transmission release XX XX | Circuit release message. |
| Remote operator release | Occurs as a result of a release request by the remote operator. |
| Release due to crossed calls | There is a crossed call between the remote and the local and only one is accepted. |
| Release by the operator | Occurs as a result of a release request by the operator. |
| Release due to compression error | Release is requested when an error occurs in the compression/decompression of a message. |
| Release due to another established channel existing | A circuit is released because another one is already connected for a given session. |
| Release due to invalid facilities | The type of facilities used when requesting the connection will be checked. editran will only manage reverse-charge use. |
| Release due to incorrect schedule | Check the schedule given in the session profile and modify it. |
| Release due to not accepting reverse charge | Check the REVERSE CHARGE field in the session profile. |
| Release due to no free channels | Circuit limitation. The connection can be established when another established session is released. |
| Release due to network restart | A circuit release has occurred due to a network restart. |
| Release due to invalid payment type (profiles) | Check the session PAYMENT METHOD in case of conflicts. One endpoint must support billing. |
| Call rejected (invalid time) | Connection request outside of schedule. Check profiles. |
| Call rejected invalid remote address (profiles) | Check the remote NRI/IP of the session in profiles. |
| Remote call accepted | The remote connection request has been accepted. The connection is established. |
| Remote call accepted (crossing) | Both ends have requested connection establishment and the local one was handled first. |
| Remote call rejected (reverse charge) | The specification for this parameter does not match on both ends. |
| Remote call rejected (crossing) | The incoming call from the remote is rejected. |
| Remote call rejected (calling end) | The specification for this parameter does not match on both ends. |
| Remote call rejected (payment type) | The specification for this parameter does not match on both ends. |
| Local cannot emit (profiles) | Emission request rejected because the TRAFFIC DIRECTION parameter is not specified with value E or X or because the appropriate license is not available. |
| Local cannot call (profiles) | Connection request rejected because the CALLING END parameter is specified as R, so only the remote can call. |
| Local cannot receive (profiles) | Check the TRAFFIC DIRECTION parameter and license for direction. |
| Incorrect notification message | An error occurred in session establishment due to the notification message format. |
| No connection exists | A request was made that previously required connection establishment. |
| No session in profiles | Register the session in profiles. |
| No resources available | The connection can be established once another already established one has been released. This is due to the limitation of physical circuits in the local environment. |
| No network service | The local end does not have X.25 service. |
| No session | The request requires the existence of a connection between applications. |
| No post-emission batch is launched | An emission batch request has been received, which will not be processed because emission is in progress. |
| No post-reception batch is launched | A reception batch request has been received, which will not be processed because reception is in progress. |
| No pre-emission batch is launched | A reception batch request has been received, which will not be processed because reception is in progress. |
| No pre-reception batch is launched | A reception batch request has been received, which will not be processed because reception is in progress. |
| Connection pending | The request requires the existence of a connection between applications. The connection has not yet been completed. |
| Sequence lost in sender process | A jump in the message sequence number has been detected. |
| Sequence lost in receiver process | A jump in the message sequence number has been detected. |
| Incompatible profiles (compression) | The value specified at both ends for the compression parameter does not match. |
| Reception rejected by profiles (transmission direction) | The value specified at both ends for the transmission direction parameter does not match. |
| Emission download batch request | An emission download batch request has been received. |
| Emission start batch request | A batch request for the start of local transmission has been received. |
| Reception start batch request | A batch request for the start of local reception has been received. |
| Preparation and emission start batch request | A request has been received from batch to launch a job specified in profiles. |
| Preparation and reception start batch request | A request has been received from batch to launch a job specified in profiles. |
| Post-emission batch request | A request has been received from batch to launch a job specified in profiles. |
| Post-reception batch request | A request has been received from batch to launch a job that had been specified in profiles. |
| Association request | A request for connection between applications has been requested. |
| Receive request | A reception request has been requested from the local or remote operator. |
| Request not accepted. Server operating mode | A request not allowed in server operating mode has been requested. |
| Post-emission finished correctly | A response is received from the batch indicating successful completion of a process. |
| Post-reception finished correctly | A response is received from the batch indicating successful completion of a process. |
| Pre-emission finished correctly | A response is received from the batch indicating successful completion of a process. |
| Pre-reception finished correctly | A response is received from the batch indicating successful completion of a process. |
| Start of session. Local emission | The first burst of the transmission has been sent. |
| Remote operator network restart | A network restart requested by the remote operator has occurred. |
| Reception aborted | A file reception has been aborted. |
| Reception correct and finished | A file has been received successfully. |
| Received message with invalid CRC | A message has been received from the remote in a session defined in profiles with CRC validation, but its CRC is incorrect. |
| Incorrect message received from batch | Correct A5P request type. |
| Incorrect message received in sender process | Message outside protocol. |
| Incorrect message received in receiver process | Message outside protocol. |
| Remote without session / registered NRI (profiles) | The NRI of an incoming call does not match the one of the session registered in profiles. |
| SBP received in incorrect state | Message outside protocol. |
| SBR with total mismatch | Negative response to a total synchronization because the totals do not match in the receiving process. |
| SCP received in incorrect state | Message outside protocol. |
| SEP received in incorrect state | Message outside protocol. |
| Batch launched after emission | Batch process launched according to profiles. |
| Batch launched after reception | Batch process launched according to profiles |
| Batch launched before emission | Batch process launched according to profiles |
| Batch launched before reception | Batch process launched according to profiles. |
| Call made earlier | A connection request was received when a previous one to the same session was already being processed. |
| The call is made | An attempt is made to connect to the remote editran system. |
| Local key change requested | The local end has requested a key change in the application-association establishment phase. |
| Remote key change requested | The remote end has requested a key change in the application-association establishment phase. |
| Session rejected by profiles (Ascii/Ebcdic) | Correct the parameter in the session profile. |
| Session rejected by profiles (CRC calculation) | Correct the parameter in the session profile. |
| Session rejected by profiles (service quality) | Correct the parameter in the session profile. |
| Session rejected by profiles (Compression) | Correct the parameter in the session profile. |
| Session rejected by profiles (Totals control) | Correct the parameter in the session profile. |
| Session rejected by profiles (Cryptography) | Correct the parameter in the profiles profile (Cryptography) of the session. |
| Session rejected by profiles (Record length) | Correct the parameter in the session profile. |
| Session rejected by profiles (Application type) | Correct the parameter in the session profile. |
| Session rejected by profiles (Connection type) | Correct the parameter in the session profile. |
| Session rejected by profiles (Version) | Correct the parameter in the session profile. |
| Remote sending buffer inaccessible | An error occurred while accessing the remote send buffer file. |
| Remote receiving buffer inaccessible | An error occurred while accessing the remote receive buffer file. |
| Still transmitting | Request not processed because transmission is in progress. |
| Connection already exists | A connection request was made to a session that was already connected. |
| Already receiving | A duplicate request is received from the operator. |
| Already transmitting | A duplicate request is received from the operator. |
| Incorrect remote receive file (previous launched) | The remote is preparing its receive buffer. |
| Incorrect remote receive file (no previous exists) | The remote does not have its receive buffer ready because it has no previous one. |
| Incorrect remote receive file (previous possibly in execution) | The remote receive file is possibly being prepared |
| Incorrect remote receive file (session no.) | The session number of the remote receive file does not match the local one. |
| Incorrect remote receive file (total record no.) | The total number of records in the remote receive file does not match the local one. |
| Incorrect remote send file (previous launched) | The remote is preparing its send buffer. |
| Incorrect remote send file (no previous exists) | The remote does not have its send buffer ready because it has no previous one. |
| Incorrect remote send file (previous possibly in execution) | The remote send file is possibly being prepared. |
| Editran/G denies batch request locally | Editran/G does not execute the requested request. |
| Buffer file loaded | Editran/G notifies that the send buffer has been loaded. |
| Error. encrypted sending buffer and profile without Cryptography | IGA profile with cryptography and editran profile without cryptography. |
| Error. encrypted sending buffer and profile with key change | IGA encryption and key change in editran are not allowed. |
| Error. Sending buffer key and sending key differ | The key used by IGA to encrypt the buffer does not match the current editran key. |
| Error. Sending buffer length and profile differ | The length of the buffer loaded by editran/G does not match the current length of editran/P. |
| Error. compressed sending buffer and profile with compression | The data in editran/G has been compressed and compression is requested in editran/P. |
| Error. receive buffer length and profile differ | |
| Error. encrypted sending buffer and profile with compression | The data in editran/G has been encrypted and the editran/P profile uses compression. |
| RTC - Port in use by another connection | The serial port is being used by another editran connection. |
| RTC - Port out of range | The port specified in the profile does not exist. |
| Network adapter not installed or not operational | The network adapter (modem, X.25 card, etc.) is not working. |
| RTC - The modem does not respond | The modem does not respond. |
| RTC - Carrier not detected or lost | |
| Error initializing the network adapter | |
| RTC - No dial tone | |
| RTC - Remote busy | The network identifies the called DTE as busy with other communications and therefore unable to accept the incoming call. |
| RTC - No response from remote | |
| RTC - Unrecognized modem response | |
| RTC - Blank RTC number | |
| X.28 - Release by DTE(P) | The distant terminal equipment has released the communication. |
| X.28 - Local procedure error | The DCE detects a procedure error caused by the DTE. |
| X.28 - Network congestion | Condition produced within the network: due to temporary congestion. Due to temporary failure. |
| X.28 - Out of service | The dialed number is out of service. |
| X.28 - Remote procedure error | The network detects a procedure error caused by the DTE at the distant DTE/DCE end. |
| X.28 - Busy number | The network identifies the called DTE as busy with other communications and therefore unable to accept the incoming call. |
| X.28 - Invalid facility request | Invalid facility requested by the calling DTE. |
| X.28 - Access forbidden | The calling terminal equipment is not authorized to obtain communication with the called DTE. |
| X.28 - Unobtainable | The address of the called DTE is not in the numbering plan or has not been assigned to any DTE. |
| X.28 - Release by the PAD | The communication has been released by the local DCE in response to a release invitation from the distant DTE. |
| X.28 - Number without collect call | The called terminal equipment is not subscribed to accept collect calls. |
| X.28 - Incorrect IUR | The network user identifier is incorrect. |
| X.28 - No additional information | Release with diagnostic 000 from the network. |
| X.28 - Invalid command | Release with diagnostic 016 from the network. |
| X.28 - Command not allowed | Release with diagnostic 032 from the network. |
| X.28 - Timer expiration | Release with diagnostic 048 from the network. |
| X.28 - Error connecting to the PAD | |
| Session rejected by profiles (Confidentiality) | Correct the parameter in the session profile. |
| Session rejected by profiles (Authentication) | Correct the parameter in the session profile. |
| Session rejected by profiles (Automatic disconnection) | Correct the parameter in the session profile. |
| Session interrupted | Verify the interruption code |
| Remote certificate accepted | The remote certificate is accepted correctly |
| TCP - Connection reset | |
| TCP - Destination address required | The remote IP address must be specified |
| TCP - Address unavailable | The address being called is not available |
| TCP - Network unreachable | The address being called is not available |
| TCP - Connection refused | |
| TCP - Host down | Verify the status of the remote computer |
| TCP - No route to host | |
| TCP - Host not found | |
| TCP - Unrecoverable error | |
| Incorrect local receive file (total record no.) | The total number of records on the sending end does not match the expected number of records to receive. |
| Incorrect local receive file (creation date) | The date of the local receive file does not match the creation date of the remote end. |
| Version ignored due to date control | |
| Association timeout exhausted | |
| Received message with unknown header | Invalid protocol message. |
| Remote call rejected (network license) | The session is not licensed for the incoming call type. |
| SWIFT -- GetFile request made | Informational. |
| SWIFT -- GetFile request received | Informational. |
| SWIFT -- PutFile request made | Informational. |
| SWIFT -- PutFile request received | Informational. |
| SWIFT -- Request accepted | Informational. |
| SWIFT -- Request rejected | Informational. |
| SWIFT -- Incorrect state | Informational. |
| Option not available for SWIFT sessions | Informational. |
| No batch is launched after emission. Data in SWIFT | Informational in operation |
| SWIFT. Buffer in incompatible state | Informational in operation |
| SWIFT. Message with unknown identifier | Informational in operation |
| SWIFT response. | Informational. |
| Reception rejected by profiles | |
| Remote call rejected (session data) | Check that the session exists for the received ID: local-remote-application. |
| Call from PAD rejected | Check the corresponding field in the session profile's X25 parameters. |
| Release due to maximum number of sessions (profile) | Check the corresponding field in the local profile. |
| Current session released | Informational. |
| Different remote editran version (supported) | Check the session profile field. |
| Release due to inactivity timeout | |
| Remote download confirmation timeout exhausted | |
| Remote reception query | |
| Remote download in progress | |
**Notes:**
* DTE - Data terminal equipment.
* DCE - Signal conversion equipment (modem)
* I.U.R. - Network user identifier.
### Release messages in Onesait Editran
When in editran the connection cannot be established or a cut occurs during transmission, release messages are generated that identify, using two codes (cause and diagnostic), the reason that produced them.
It is difficult to document all the possible causes and diagnostics that editran/P may receive, since in many cases it depends on the network protocol used and the driver supplier, which is why in this documentation we will focus only on the releases originated by the editran protocol itself.
Connection retry conditions are also included in this chapter since action is taken depending on the releases received.
#### Onesait Editran causes and diagnostics
Below are specified the release or call rejection cause and diagnostic codes given by editran.
Cause = x'00'.
Diagnostic = x'XX'. Where "XX" is as follows:
| | |
| -- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 03 | The maximum number of sessions defined in the Local Environment (Maximum Number of Circuits) has been reached and therefore there is no channel available. |
| 04 | A collision of in-flight calls has occurred. The one with the lower Editran Installation Code is released. |
| 05 | A release has occurred because there is already an established channel for that session. |
| 08 | Editran released by the Operator. |
| 09 | A network restart has occurred by the Operator. |
| 0B | Circuit released due to Compactation-Compression error. |
| 0C | An incoming call is rejected because the entry time is incorrect according to the session specifications (START TIME and END TIME). |
| 0D | The call is rejected because the session has not been registered in Profiles. |
| 0E | The call is rejected because the Calling End defined in the session does not correspond to the one making the call. |
| 0F | Generic Editran release (files not prepared, automation startup, etc.). |
| | |
#### Connection retry conditions
The editran protocol has a recovery mechanism for temporary network failures based on retrying the connection. The only cases in which it is not retried are:
* If the CALLING END field is Remote
* If the release code is Cause = 0 and Diagnostic:
04
| | |
| -- | ---------------------------------------------------------------------------------------------------------------------------------- |
| 04 | A call collision has occurred. |
| 05 | There was already a connection for that session. |
| 08 | Release by Operator. |
| 0F | Generic Editran release. |
| 00 | No additional information. It is retried only if the connection is being established, not in drops during transmission. |
| 04 | In all cases, when retrying the connection, it will rotate to the next remote whenever several have been specified in the profile. |
### Onesait Editran Cryptography System
#### Introduction
The cryptography used by EDITRAN provides maximum security to the communications channel and meets the needs of authentication, confidentiality, and non-repudiation. The user decides the mode in which they want to transmit.
The services provided are described below.
* **Information confidentiality**
To keep the information secret during the transmission process, the information is encrypted at the sending end with an encryption key that only the final receiver can 'interpret', and with it the received information is decrypted.
To encrypt/decrypt the information, symmetric-key algorithms are used: the DES and AES symmetric key algorithm (recommended). This key is different for each transmission and is exchanged encrypted with another higher-level key.
* **Information integrity**
To ensure that what is actually received is what was sent, avoiding manipulation or alteration during transmission.
For this, an error-detection code for the information is generated at the sending end, also known as a hash, summary code, or digital fingerprint, which is verified by the final recipient end when it is received. The algorithms used are SHA1 and SHA256.
* **Authenticity of the sender / final recipient pair**
To ensure that they are truly who they claim to be and not fraudulent senders and/or recipients, it is possible to use endpoint authentication techniques using RSA algorithms. Optionally, Editran implements an authentication mechanism based on DES encryption, although this is not recommended because it is less secure.
* **Non-repudiation**
So that neither party can deny having sent or received the exchanged information.
For this, the signatures presented by both ends will be validated in the Editran authentication procedure, using RSA keys, prior to the exchange of data.
As a summary, the different possibilities for handling cryptography within Editran are described.
* **V2.2 or automatic key exchange**
This mode does not require a prior key exchange. It starts from a common one that, for greater security, is automatically changed at the discretion of the endpoints.
Both the authentication algorithm and the confidentiality algorithm are DES.
* **V3.0 or external key exchange**
In all cases the confidentiality algorithm is DES (single, double, triple).
The authentication algorithm can be DES or RSA (1024-bit keys).
The DES auxiliary keys and RSA public keys used in endpoint authentication must have been exchanged before transmission. In the case of RSA, the Editran/GC module is provided to facilitate this procedure.
* **V4.0 (recommended)**
Expands the functionality of mode 3.0 by providing more secure algorithms.
The only allowed authentication algorithm is RSA with 2048 or 4096 keys.
DES remains as the confidentiality algorithm (single, double, triple), although AES (128, 192 or 256) is recommended.
#### DES key types
* **HMK - Host Master Key**
> Its function is to encrypt the keys of the local user entity and it resides masked in the file **ckds.des**.
* **AK - Auxiliary Key**
> Its function is to encrypt the Editran master key.
>
> It is generated randomly and incorporated into the file **ckds.des** under a label.
* **TKE, TKR - Sending and Receiving Transport Keys**
> Its function is to encrypt the Editran user application data that are sent to the remote.
>
> They are stored encrypted in the profiles file.
#### Cryptography errors
Any cryptography error will generate information for the local operator and a disconnection.
The errors that can occur are:
**v2.2 cryptography errors.**
| | |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ERR1** | The end requesting a Connection Request could not re-encrypt the keys in its file. |
| **ERR2** | The end requesting to authenticate its TKE key could not encrypt the Authentication Code, although it did perform the re-encryption. |
| **ERR3** | The end requesting a Connection Request with Key Change could not generate a new TKE sending key. |
| **ERR4** | The end receiving the Remote Notification Indication had an error when re-encrypting the TKR key in its file. |
| **ERR5** | The end receiving the Notification Indication could not decrypt the Authentication Code sent by the Remote, although it did perform the Re-encryption. |
| **ERR6** | The end receiving a Notification Indication with Key Change had an error when re-encrypting the new Reception key coming from the remote (new TKR). |
| **ERR7** | The end that is going to send a user datum or Operator Message had an error in "on-line" encryption. |
| **ERR8** | The end receiving a user datum or Operator Message from the Remote had an error in "on-line" decryption. |
| **ERR9** | The end receiving a Notification from the Remote (with or without Key Change) decrypted the Authentication Code, but it is incorrect (even though it keeps the old reception key). Possibly one end deregistered and registered the editran session in Profiles. This is the most serious error. The only way out of this situation is to deregister and register the Session in Profiles at both ends. |
| | |
**v3.0 and v4.0 cryptography errors**
| | |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ERR1** | An error occurred while obtaining the local key, either because it was not provided in Profiles or because of an error in the External Key Interface. |
| **ERR2** | When trying to send an association request or a response, an error occurs when generating the uncertainty or the signature. If the algorithm used is DES, the error is in the local key. If it is RSA, the error is in the local key when generating the signature, or in the remote key when generating uncertainty. |
| **ERR3** | Error trying to generate session key. If the algorithm used is DES, the error concerns the local key. If it is RSA, the erroneous key is the remote one. |
| **ERR4** | An error occurred while obtaining the remote key, either because it was not provided in Profiles or because an error occurred in the External Key Interface. |
| **ERR5** | When processing a request or a response from the remote, an error occurs when trying to decrypt the uncertainty or the signature. If the DES algorithm is used, the erroneous key is the remote key. If RSA is used, the error is in the remote key when decrypting the signature, or in the local key when decrypting the uncertainty. |
| **ERR6** | When processing a request or a response from the remote, an error occurs when decrypting the session key. If the algorithm is DES, the error is in the remote key. If it is RSA, the key in error is the local one. |
| **ERR7** | The end that is going to send a user datum or Operator Message had an error in "on-line" encryption. |
| **ERR8** | The end receiving a user datum or Operator Message from the Remote had an error in "on-line" decryption. |
| **ERR9** | When processing a request or a response, the session key and signature are decrypted, but either the uncertainty does not match or the signature does not match (this case only in RSA). The error occurs because the exchange keys do not match at both ends. If an External Key Interface was used, the message must include the last 8 bytes of the label used. If the algorithm used is DES, the erroneous key is the local key of the end generating the message. If it is RSA, the erroneous key is the local key (if an error occurs when validating the uncertainty) or the remote key (if an error occurs when verifying the signature). |
| | |
---
# 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/open-v5.2.1-en/windows/plataforma.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.