> 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.3-en/windows/interfaz_generica.md). # Editran/G Management ## Onesait Editran/G Management The installation of the product creates the editran programs folder in the Windows Start menu. Click the option "*G Menu"* which will display the editran/G manager window. ![assets/image4.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-1b4be92eff9a39f29e41e36d9370326b0cf84fa4%2Fimage4.png?alt=media) If this is the first time editran/G starts up, the first thing you must do is enter the local environment data (see chapter **3.6** Onesait Editran /G Administrator). ### Operation interface In the screens included in this document, the different types of fields are represented as follows: #### Screens Three areas can be distinguished on the editran WINDOWS screens: * **(1) Menus** In the menu area, you choose the different options for operating editran. Startup and shutdown of editran, reports, system administration. They are activated by the cursor, by underlined letters. ![assets/image5.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-6a911c7e771e0903c4cc96676f47c8867aaa52ff%2Fimage5.png?alt=media) * **(2) Toolbar** In this area, different icons appear that indicate actions equivalent to those in the menus; when you place the pointer over each icon, information associated with that icon's action appears at the bottom of the screen.\ ![assets/image6.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-9c15e6e0ce8be7619484c1c7f0a81d1e44483afe%2Fimage6.png?alt=media) * **(3) Information** In this area the information that editran sends to the operator appears: * Presentation. * Transmission and reception statuses. * Information text or messages from the remote operator. ![assets/image7.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-214dc7a022d433c1508f7577a9a4dee5905e4dae%2Fimage7.png?alt=media) * **(4) HELP** ![assets/image8.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-0d01db516964b4bb7cdf8e5941bb68765628bdc5%2Fimage8.png?alt=media) Editran/G has a help system. Thus, when the F1 key is pressed, a window with the help text appears. ### Startup and shutdown of Onesait Editran Editran startup and shutdown must be done from Windows services in this order: * Start Editran License Service. * Start Editran Base Service. ### Onesait Editran /G Operator To work with presentations, select the option in the main menu **Editran/G > Operator**. Note that if we want to act on a specific presentation, we must click the cursor on it and select it (the white background will turn blue). If none is selected, a window will appear asking you to choose the presentation to use: ![assets/image12.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-e4d2a2053dbf3d7ce75b73811cfafd50cfe16385%2Fimage12.png?alt=media) The following options will be presented: ![assets/image13.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-627ea205f0b0607fb55fa5020a3206710e10a503%2Fimage13.png?alt=media) You can also right-click to open a context menu with the same options. #### Load emission presentation. * This option is only allowed when the Presentation has no activity (state represented by ...) or when it is *LOADED* and the profile is configured to allow cumulative loading. In any other case, the user will be shown the message *"Presentation state incompatible with the request"*. * If the request is accepted, the presentation changes to the temporary state *LOADING* in which the following steps are performed: * The user program prior to transmission is executed, if it exists in the profile. * The converter program corresponding to the version of the remote entity is executed. This program creates the buffer files that package the data to be transmitted. * If the loading process completes successfully, the final state will be *LOADED*. If an error occurs, the corresponding message will be displayed and it will remain in the initial state. In the image, an example of a load request for a presentation for which there are no files to transmit. ![assets/image14.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-0bb058acc042a7a79ac885c02e0b7a83031b8c44%2Fimage14.png?alt=media) This button is equivalent to the action through menus: ![assets/image15.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-7b66e8c733458bd01310452607587bc397d92d7c%2Fimage15.png?alt=media) #### Emit presentation. This operation is accepted when the presentation transmission state is: inactive (*...*), *LOADED* or *INTERRUPTED*). In general, it is the only request made to transmit since, if necessary, the loading process mentioned in the previous point is performed first. Once *LOADED* a number of A1R messages are sent to editran/P as many as transmission sessions the presentation uses. The same is done if it were *INTERRUPTED* except that in this case, transmission will resume at the point where it stopped. The transmission state changes to *TRANSMITTING* and waits to receive the editran/P notification of the end of the transmission(s). In the image, a typical sequence of log messages associated with a transmission request for a presentation with a single transmission session. ![assets/image16.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-34034a95fc1e4a52c74ac9e45de10d3f97ef5c1e%2Fimage16.png?alt=media) Pressing this button is equivalent to the action through menus: ![assets/image17.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-2d5a6b631f28f5c068ad9b5d478a9d7b65a0fe38%2Fimage17.png?alt=media) #### Interrupt emission. Option that allows the editran operator to stop the emission in progress (state *TRANSMITTING*). To do this, each transmission session of the presentation is notified to interrupt via the EDP message. The presentation state temporarily becomes *INTERRUPTED* but it can be resumed by requesting the emission again. Pressing this button is equivalent to the action through menus: ![assets/image18.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-1b96b716b668206f695dfa3f220037ccdffab465%2Fimage18.png?alt=media) #### Initialize emission presentation Each time the transmission of a presentation finishes successfully, it returns to the initial state. If for some reason a transmission is interrupted and you want to cancel it to start another from scratch, you must select this option to initialize the presentation. The only time initialization is not allowed is when the presentation is in state *TRANSMITTING*, in that case it is necessary to interrupt it first. This button is equivalent to the action from menu: ![assets/image19.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-33bab217d4827294f58bbaf2c8c7300097a3e706%2Fimage19.png?alt=media) #### Receive presentation Each presentation in editran can be configured to allow the remote entity to connect and send (server mode), or only the entity itself to make transmission requests, both to emit and receive (client mode). Whenever you want to start a connection with the remote editran to bring the files it has available for the presentation, this option is chosen. Depending on the state of that presentation, the response will be different. If the presentation has no activity (*...*), that is, it starts a new reception, the user program configured as pre is launched, and the A2R message is sent to each transmission session. The presentation state becomes *TRANSMITTING* until the notification of the end of the transmission(s) (A4P) from editran/P is received. In state *INTERRUPTED* the behavior is the same, except that no prior user program is launched since transmission resumes at the point where it stopped, avoiding retransmitting the volume already exchanged. In any other state, the user will be shown the message *"Presentation state incompatible with the request"* since a presentation can only have one transmission in progress. A special case is the state *TRANSMITTED* in which the buffers have been received, but the download has not finished. See section [download reception](#descargar-recepción) to see how to operate in this case. This button is equivalent to the action from the menu. ![assets/image20.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-a3e910c7d1384d16f24c4c4f731c68922af5c7bd%2Fimage20.png?alt=media) #### Download reception. In the reception process, the download or transformation of the received buffer files is performed automatically. This means that this option only has to be used exceptionally when due to some failure the presentation state remains in *TRANSMITTED*. In these cases, the product log information must be analyzed to see whether it is a local error that can be corrected and the download attempted again. In INTERRUPTED state this option is also allowed, but in this case there is an additional check that the total data has actually been transmitted. The presentation state that will be seen in the user interface during the download process is *DOWNLOADING*. And when it finishes, it will be ready to start a new reception (...). Only when the download process completes successfully is the user program after reception executed. If it fails, the exception user program will be launched indicating the error code. If the user wants actions to be performed in those cases, they must be set in the presentation profile, since by default these fields are left blank in this version. Pressing this button is equivalent to the action through menus: ![assets/image21.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-d5f62227bb7119d30c388488bfb86e07a30ee291%2Fimage21.png?alt=media) #### Initialize reception presentation. As explained for transmissions, each time the transmission of a presentation finishes successfully, it returns to the initial state ready to perform the next one. Only if for some reason a reception *INTERRUPTED* or *TRANSMITTED* is to be canceled, it must be reset through this option. The initialization process removes all control information from the current transmission so that the next one starts from scratch. This option is equivalent to the menu action: ![assets/image22.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-eb7e2df7d16c990119d6be848f9df66397dd034f%2Fimage22.png?alt=media) #### Interrupt reception. The editran operator can interrupt any reception in progress (state *TRANSMITTING*). To do this, each transmission session of the presentation is notified to disconnect via the EDR message. The presentation state temporarily becomes *INTERRUPTED* but it can be resumed by requesting the reception again. If the presentation has an exception user process configured, it is executed and the error code that arrives is *110*. Pressing this button is equivalent to the action through menus: ![assets/image23.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-5755838f9fa30a339960a8a61bdb04a8cc6b26e2%2Fimage23.png?alt=media) ### Sending operation using integrated Editran/FF #### Editran/G configuration to connect to the Editran/FF server Before sending signed files, the Editran environment must be configured to communicate with the available Editran/FF server. To do this, it is necessary to have started Editran/G as administrator. The parameters related to Editran/FF can be accessed from the Help -> About Editran option or directly by clicking on the button ![assets/image24.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-fea1985e6750e316fdd367a574f6900cce44a65b%2Fimage24.png?alt=media) of the Editran/G toolbar and clicking the Editran/FF Service option. ![assets/image25.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-c508bdd1e9c46c60bb25a1ec2a671a83bf52802c%2Fimage25.png?alt=media) In the window that appears, the Editran/FF section must be configured with the IP address plus the listening port of the machine where the Editran/FF server is installed (the default port is 8300). If the FF server is installed on the same machine where Editran was installed, the IP address will be 127.0.0.1:8300 It is also necessary to indicate the sending directory configured at a general level on the Editran/FF server, in which Editran will look for the signed files ready to send. To apply the configuration, it is necessary to click the Update button and then the OK button to close the dialog. ![assets/image26.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-36ed6873b2f6929e0cbd36ee5855260bf4653b79%2Fimage26.png?alt=media) #### Sending signed files with Editran/FF An Editran/G presentation must be configured so that it uses as data source the Editran/FF applications that have files available to be sent. To do this, you have to create a new presentation in Editran/G or edit an existing one and mark the option *Send signed files in Editran/FF* of the tab *Files.* ![assets/image27.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-29534caf4baa5601673780ddb4a00288a092f6b7%2Fimage27.png?alt=media) In the dialog, the button will be enabled *New FF Application* and if communication with the FF server is correct, the ApplicationsFF selection window will appear, similar to the file selection dialog for emission. If communication has not been possible, an error message will appear notifying the problem. In the file drop-down list, you can choose between all the Editran/FF applications that have been configured for sending with Editran. ![assets/image28.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-8f297ef58035047297550b151f15302c2e1ba8f2%2Fimage28.png?alt=media) As many applications as desired can be chosen to be sent by the same Editran/G presentation. The Save button must be clicked to apply the presentation configuration before emitting the files. ![assets/image29.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-896402f837cda11ec0b06a30553e32094665172d%2Fimage29.png?alt=media) ### File inquiry ![assets/image30.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-51a37de858451c71b1593f78e8d775c8ad95c75a%2Fimage30.png?alt=media) #### Presentation Status Inquiry. To query a particular presentation, select the presentation and then choose the send type (emission or reception). In the information area of the window (bottom part), the information summarizing the status of the presentation and its transmission sessions will appear. ![assets/image31.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-4f1a790a9fcfa3829c6bb8eb847d57ae38614928%2Fimage31.png?alt=media) * **PRESENTATION STATUS** It may have the following values: | | | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **...** | The presentation is ready to start a new emission/reception. There is no transmission in progress. | | LOADED | The presentation buffer files have been generated but sending to the remote entity has not started. | | TRANSMITTING | One of the presentation's transmission sessions is connected and transmitting. | | TRANSMITTED | The transmission has finished. In emission this state indicates that the remote download confirmation is still pending. In reception it remains in this state when the download process fails. | | INTERRUPTED | One of the presentation's transmission sessions is interrupted. | *** * **PRESENTATION NO.** For presentations configured to increment the presentation number, a counter of the transmissions performed is kept and must match on both ends. This is the value shown in this field. When the presentation is not using this feature, the field appears empty as in the example. * **CHANGE DATE** UTC date and time of the last change in presentation status. * **SESSIONS** As many lines as transmission sessions are used in the presentation appear, up to a maximum of 20. Each line shows: session, date and time of creation of the buffer file, and the ratio of transmitted information with the relationship between total and confirmed records. #### Modification of presentation statuses Under normal circumstances, the way to initialize the status of a presentation, cancelling any pending transmission and leaving it ready to start a new one, is from **Editran/G > Operator > Initialize presentation**. There are some exceptional cases that may require a special modification of the presentation status. For example, when after having activated the option "*Increment presentation number*" the two ends are not synchronized and it is necessary to indicate the correct number to continue with the transmissions. ![assets/image32.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-d0dc7f70e68c0cde09ebc3b65804aeaaf2c9a75d%2Fimage32.png?alt=media) When selecting **Editran/G > File Inquiry > Modification of presentation statuses > Emission or Reception**, the confirmation screen appears warning that this operation affects both sender and receiver and that both ends must agree. When you click **OK** the state will be reset and the presentation will be in the initial state. ![assets/image33.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-066e986b90e9f0395681db96fb688544c1c54683%2Fimage33.png?alt=media) #### Log inquiry. It is accessed from the main menu by selecting the option **Editran/G > File Inquiry > Log Inquiry**. The log inquiry window consists of a search filter and the list of the results obtained. The filtering criteria are: * *Presentation*. Masks are not allowed; a specific presentation is selected or all (***\***). * *Date and time*. The messages are shown from the defined date and time up to the current date of the inquiry. Once the filter has been set, click the "OK Selection" button to apply it. ![assets/image34.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-49cf375175c31d566ffc4ef14b6ac52bf16b2712%2Fimage34.png?alt=media) ### Onesait Editran /G Administrator The Editran/G administrator is accessed by selecting the Administrator option from the main menu, presenting the following screen: ![assets/image35.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-44135755bd04748b0cb01948923aa58fc74b157d%2Fimage35.png?alt=media) #### Presentation profile. To be able to perform a transmission through editran, it is necessary to have previously defined what is called the presentation profile. It establishes all the parameters governing a type of information exchange organized by: presentation data, remote entity data, application data and file data. When choosing the Presentation profile option, a window with the tabs explained below will appear. Click the button **Save** to apply the changes made. **PRESENTATIONS TAB:** ![assets/image36.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-5a1683ffd2e879c4a81c52cc1d40078f7fd0415d%2Fimage36.png?alt=media) * **Presentation** Choose the name of the Presentation you want to create or modify. * **Local Code** Values taken from the local environment. It can only be modified if the installation has a license to work with multiple local codes. * **Presentation data** * **Number of presentation sessions** Number of transmission sessions associated with the presentation. These sessions must have been previously registered with the editran/P administrator. In the "Editran/P applications" table, you must specify which ones they are. * **Division criterion** Only applies when several transmission sessions are used for the presentation. The following values can be specified: * **None:** No splitting is performed. * **By volume:** The emission application information would be distributed equally among the different buffers, with a minimum of 400,000 bytes per buffer. This means that some of the transmission sessions defined for it might not be used in the presentation. * **By file**: File-by-file distribution. Successive complete files would be assigned to each emission buffer. * **Load type** With cumulative load type, the buffer can be reloaded with new application files, provided transmission has not started. Cumulative load requires using a single transmission session. * **Normal:** Single load per transmission. * **Accumulated:** Allows loading several times before transmitting. * **Editran/P applications** Names of the Editran/P applications corresponding to the transmission sessions of the presentation. The table enables as many elements as indicated by the number of sessions field, and in each one you can choose from the list showing those configured in editran/P for the same local and remote code. **REMOTE ENTITY TAB:** ![assets/image37.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-db9c05287951878417eab21fc4812a3d572d034b%2Fimage37.png?alt=media) * **Remote entity code:** Enter the code of the remote entity, which must be the same as the one used in Editran/P. * **Description:** Descriptive name of the remote entity. * **Remote Editran/G version:** The version of the remote Editran/G also determines the emission and reception converter to use. | **Version** | **Remote entity** | | ----------- | ---------------------------- | | **5.0** | If the remote entity is V5.0 | | **5.1** | If the remote entity is V5.1 | | **5.2** | If the remote entity is V5.2 | | **5.3** | If the remote entity is V5.3 | * **Download acknowledgment** * **Request** With remote download acknowledgment, transmission will not be considered finished until the result of the download is received from the remote side or until the timeout is exceeded. * **Timeout** Maximum waiting minutes to receive the download acknowledgment. Values between 1 and 99 are allowed (inclusive). * **Cryptography:** In the cryptography data section, the type of security used to protect the information exchanged by this presentation is established. The options configured here only affect the processing of the data during the process of creating the editran buffers. Although it is recommended to use cryptography at this level of the protocol, you can also select **No** and protect only the transmission by properly configuring the Editran/P sessions. When selecting **Yes** the rest of the settings that configure the cryptographic system are enabled. * **Cryptography version** * **3.0** In this mode, each transmitted file is encrypted with a different key when forming the buffer. The data encryption key is sent attached, protected according to the chosen authentication algorithm.\ With authentication **RSA**, the file is also signed to guarantee source authenticity and data integrity. The hash algorithm used is sha-1. * **4.0** Extends the functionality of mode 3.0 by incorporating more secure symmetric key encryption algorithms (AES).\ In this version the only authentication algorithm supported is RSA, extending the key length up to 4096. The hash algorithm used in the signature is sha-256. * **Confidentiality Algorithm** Available symmetric key encryption algorithms for cryptography version 3.0 or higher. You can select ***Do not encrypt*** if the only thing you want is to sign the files sent. * **TDES-3** (Triple DES with triple key). * **AES-128, AES-192, AES-256**. Only available for version 4.0. * **Authentication Algorithm** Algorithm used by Editran to protect the data encryption key. It also provides source authentication and integrity of the transmitted data. * **DES:** It is kept for compatibility with previous product versions. RSA use is recommended. * **RSA:** It is the mandatory algorithm when working in mode 4.0. * **Editran/GC key exchange** The keys used in public key cryptography (RSA) are exchanged between the entities using the product utility designed for this purpose: Editran/GC. If this "check" is marked, the active key of the configured subsystems is used. Consult the user manual of *Editran/GC Key Management* for more information about the utility. * **Local and Remote Key/Subsystem** Auxiliary key labels with DES authentication or Editran/GC subsystems with RSA authentication. **APPLICATION TAB** ![assets/image38.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-6ab9a6adcc32d1ad17fe4154ab79d10b60df5da5%2Fimage38.png?alt=media) * **Application** Application name. Together with the local and remote codes it forms the unique identifier of the presentation. It is not mandatory that it match the Editran/ application, although it is recommended that it does when only one session is used in the presentation. * **Description** Descriptive text of the application. * **Conversion tables** These are text files edited by the user with the correspondence table between the local character encoding scheme and Editran's own, both for emission and reception. Each line will be of the following type, defining the characters in hexadecimal: ` ` If no local translation is needed, these fields should be left blank. Otherwise, the file name should be entered, but without the last character, which is only used to identify the alphabet: **A** if it is ASCII, or **E** if it is EBCDIC. For example, assuming the user creates the file mytableA to translate ASCII characters, only mytable would be entered in the profile. The table files must be located in Editran's subfolder *bin* . * **User programs** Called by Editran/G in the processes before and after emission and reception and in exception handling, these programs will be provided by the user when they want to use this feature to integrate the product with other systems. The editran software includes some sample batch programs that can be used as a template. These fields are left blank by default. The exception program **utils\U\_EXCEPCION** can be used if you want to leave a record in the log files of the transmissions that are interrupted. **FILES TAB** ![assets/image39.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-b45bd7dea6a936d4f86dea3be62802e2aacb6663%2Fimage39.png?alt=media) * **Presentation Emission Files** Each presentation defines in advance the set of files that will be transmitted each time an emission is requested. Click the button **Add File** to configure a new emission source and its sending characteristics. * Emission source Path of the files to be emitted. Absolute paths are supported, as well as relative paths referring to the directory *bin* of editran or shared resources in UNC notation. In all cases, you can use the wildcards supported by the OS (\*, ?, etc.). * Compression (Yes/No) LZW compression of the loaded file. In reception it is decompressed according to the control fields of the received buffer. * Application File Format Format conditions are established that files must meet to ensure they are compatible with what is expected in other environments: zOS, iSeries. * **Fixed:** Application files are read in fixed-length blocks (value of the parameter **Application record length**).\ Optionally these files can have each block separated by a line break; in this case it is necessary to specify which delimiter is used (CRLF or LF).\ The delimiters do not reach the receiver; they are removed when the file is loaded. * **Variable:** Application files are read line by line. CRLF or LF is accepted as delimiter regardless of the value of the parameter **Delimiter**.\ In these cases the record length is the maximum value. As with fixed files, the delimiter is removed during the loading process. * **Hybrid:** Application files are variable, but they are sent to the remote side as fixed. Each line is padded with spaces up to the specified record length. * **Binary:** Transmission in binary mode. No processing of either format or alphabet is performed. * Application record length Together with the format of the files, it is sent to the remote installation. In zOS and iSeries environments it is necessary in order to create the received files. * Alphabet It is the original alphabet of the files to be sent. Editran only accepts the following possible alphabets **ASCII** or **EBCDIC**. The value **None** indicates that the file is treated as binary. * ASCII/EBCDIC Translation (Yes/No) When set to translate to **Yes**, when the original alphabet is ASCII it is translated to EBCDIC and if it is EBCDIC it is translated to ASCII. Currently there is a wide variety of encodings that extend US-ASCII (codes 0 to 127), so it should be noted that for correct display of the file at both ends, both platforms must work with compatible tables. For example, if on your Windows platform you work with ISO 8859-1, which includes the 'ñ' character among others, when translating it to EBCDIC it is necessary that the mainframe environment has the equivalent code page so that it is displayed the same way. * Delimiter Control code that marks the line break (record). The following are accepted **DOS** (CRLF) or **UNIX** (LF). * Send signed files in Editran/FF When this checkbox is checked or unchecked, the sending of signed files through Editran/FF applications is enabled. To learn more about the functionality of emitting signed files with Editran/FF, see the section Integrated Editran/FF using send operations * **Reception Files** * Reception destination In general, this is the directory where the received files are placed. In this case, the file name is the one indicated by the sending entity. If any character not allowed by the OS appears (:,<,>, etc.), it is replaced by '-'. If the goal is to normalize the naming of received files at the destination, it is possible to use special wildcards that are interpreted by editran. See section [Receiving destination wildcards](#comodines-destino-de-recepción) for more details. * Delimiter It only applies to files received with Fixed format. In these cases the selected delimiter is added at the end of each record. In variable files the DOS delimiter (CRLF) is always added. * Translate on reception Binary files are never translated.\ If ASCII is chosen, files received in EBCDIC will be translated and vice versa.\ If the received file already comes in the specified alphabet, no transformation is performed. #### Generic profile query The queries can be filtered by: * **Presentation** A relationship of presentations with their identifiers is obtained. ![assets/image40.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-9e3c261484678233a8b6c754362e6ee9d886b672%2Fimage40.png?alt=media) * **Remote entity** A relationship of remote entities with their description is obtained. ![assets/image41.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-e0d419b2b518c67df969d018a98ce3c7a8ee94cd%2Fimage41.png?alt=media) * **Application** A relationship of applications with their description is obtained. ![assets/image42.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-1e709259de21ca108081e4c030047b3b4b6bad08%2Fimage42.png?alt=media) ### Additional functionality #### Transmitted files report The generation of the daily transmitted-files report is an optional feature that is activated in the application configuration settings in the Windows Registry. To do this, before starting the EDITRAN service, a new value must be created in the key `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\EDITRAN.` The name of the new value is **ReportPath**, it is of type **REG\_SZ** and sets the **path** where the daily reports will be created. ![assets/image43.jpeg](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-8fc67d2e690d6e1a4f114c250db694f9d950caa5%2Fimage43.jpeg?alt=media) The name of the generated reports is *FicherosEditran.\.txt*, where yyyymmdd is the current year, month, and day. They are csv files with columns separated by ','. Additionally, the level of detail of the data shown in the reports can be set using the DWORD-type value **ReportLevel**. ![assets/image44.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-2d6baa1856edf184ffbb0cd744d3f9c40182fd72%2Fimage44.png?alt=media) Below are the fields shown in the daily transmitted files report: *** | **Field** | **Minimum ReportLevel value to display it** | | ----------------------- | ------------------------------------------- | | Date-time | 0 | | Sending/receiving | 0 | | Presentation | 0 | | Local code | 0 | | Remote code | 0 | | Application | 0 | | File path | 0 | | Format | 0 | | Alphabet at source | 0 | | Compressed | 0 | | Encrypted | 0 | | Size in bytes | 0 | | Delimiter | 1 | | Alphabet at destination | 1 | | Signed | 1 | | Source file name | 1 | | Record length | 1 | | Number of records | 1 | | Concatenated file | 1 | ## Appendices ### Receiving destination wildcards The wildcards that can be specified are: | Wildcard | Description | | -------- | -------------------------------------------------------------- | | **+** | If the file exists, append to the previous one | | **-** | If the file exists, destroy the previous one | | **%o** | Original name of the downloaded file (including the extension) | | **%D** | Day (DD) | | **%M** | Month (MM) | | **%Y** | Year (YYYY) | | **%h** | Hour (hh) | | **%m** | Minutes (mm) | | **%s** | Seconds (ss) | | **%c** | File counter (c) | In the wildcards **%Y** and **%c** you can define the precision of the digits to be written by adding a number before the wildcard letter. For example, if %4c is defined, 4 digits will be written. **Receiving destination examples** In the examples, the remote entity sends us 4 files. **Case 1**\ We configure the following receiving destination:\ `../target_directory or ../target_directory/%o` | **Sent files** | \*\*Downloaded files | | -------------- | -------------------------- | | a.txt | ../target\_directory/a.txt | | b.txt | ../target\_directory/b.txt | | c.txt | ../target\_directory/c.txt | | d.txt | ../target\_directory/d.txt | If any of the files existed before downloading, it would be destroyed by the new downloaded file. **Case 2**\ We configure the following receiving destination:\ `../target_directory/+bank_%D-%M-%Y_%h-%m-%s` | Sent files | **Downloaded files** | | ---------- | ----------------------------------------------- | | a.txt | ../target\_directory/bank\_17-10-2014\_14-00-01 | | b.txt | ../target\_directory/bank\_17-10-2014\_14-00-02 | | c.txt | ../target\_directory/bank\_17-10-2014\_14-00-03 | | d.txt | ../target\_directory/bank\_17-10-2014\_14-00-03 | Several files are downloaded, and the day, month, year, hour, minute, and second are defined for them, and in the case of files c.txt and d.txt, since both are downloaded in the same second, the content of bank\_17-10-2014\_14-00-03 would be that of those files. **Case 3**\ We configure the following receiving destination:\ `../target_directory/bank-%D-%M-%Y_%4c` | **Sent files** | **Downloaded files** | | -------------- | ------------------------------------------ | | a.txt | ../target\_directory/bank\_17-10-2014-0000 | | b.txt | ../target\_directory/bank\_17-10-2014-0001 | | c.txt | ../target\_directory/bank\_17-10-2014-0002 | | d.txt | ../target\_directory/bank\_17-10-2014-0003 | Several files are downloaded in the same session and each one is assigned the day, month, and year and a 4-digit counter (%4c). **Case 4**\ We configure the following receiving destination:\ `../target_directory/bank_%o` | **Sent files** | **Downloaded files** | | -------------- | -------------------------------- | | a.txt | ../target\_directory/bank\_a.txt | | b.txt | ../target\_directory/bank\_b.txt | | c.txt | ../target\_directory/bank\_c.txt | | d.txt | ../target\_directory/bank\_d.txt | The downloaded files will have the defined name plus the source name (including the extension). **Case 5**\ We configure the following receiving destination:\ `../target_directory/+unique_file` | **Sent files** | **Downloaded files** | | -------------- | --------------------------------- | | a.txt | ../target\_directory/unique\_file | | b.txt | ../target\_directory/unique\_file | | c.txt | ../target\_directory/unique\_file | | d.txt | ../target\_directory/unique\_file | The content of the downloaded file will be that of files a + b + c + d, due to the +. **Case 6**\ We configure the following receiving destination:\ `../target_directory/unique_file` | **Sent files** | **Downloaded files** | | -------------- | --------------------------------- | | a.txt | ../target\_directory/unique\_file | | b.txt | ../target\_directory/unique\_file | | c.txt | ../target\_directory/unique\_file | | d.txt | ../target\_directory/unique\_file | Since the files are not differentiated, they will be overwritten as they are downloaded, leaving the final content as that of file d.txt. **Case 7**\ We configure the following receiving destination:\ `../destination-directory/%o_%D-%M-%Y` | **Sent files** | **Downloaded files** | | -------------- | -------------------------------------- | | a.txt | ../target\_directory/a.txt\_17-10-2014 | | b.txt | ../target\_directory/b.txt\_17-10-2014 | | c.txt | ../target\_directory/c.txt\_17-10-2014 | | d.txt | ../target\_directory/d.txt\_17-10-2014 | Several files are downloaded in the same session and each one is assigned the original name defined by the remote side (including the extension), the day, month, and year. ### User programs These programs will be provided by the user and will be called during the presentation processes.\ Depending on when they are executed, there are three types of user programs: #### Before Sending/Receiving. If the user sets any program in the configuration, it will be the first step performed when a send begins. These programs are invoked with the following arguments: * **0** Program name. * **1** Presentation. * **2** Indicates sending (E) or receiving (R). * **3** Local Code * **4** Remote code * **5** Application #### After Sending/Receiving. If the user sets any program in the configuration, it will be launched when the transmission ends successfully.\ Each time a presentation is sent or received, a file with the list of transmitted files is generated.\ This file is the one recommended for use for integration with other applications. It could, for example, be used to store the path of the transmitted files in the database.\ These programs are invoked with the following arguments: * **0** Program name. * **1** Presentation. * **2** Indicates sending (E) or receiving (R). * **3** Local Code * **4** Remote code * **5** Application * **6** Absolute path of the file that stores the list of sent or received files. Each sent/received-file listing file has the following fields separated by ',': | **File field** | **Minimum ReportLevel value to display it** | | ----------------- | ------------------------------------------- | | File path | 0 | | Format | 1 | | Record length | 1 | | Number of records | 1 | | Concatenated file | 1 | **Example:** Post-emission script that deletes the emitted files (format ReportLevel=0) ``` @echo off REM Arguments: REM %1 - Presentation REM %2 - Direction REM %3 - Local code REM %4 - Remote code REM %5 - Application REM %6 - Path of the file with the list of transmitted files @echo off echo ############################################### echo POST-EMISSION USER SCRIPT: %0. timestamp echo PRESENTATION : %2-%1 (%3-%4-%5) echo ############################################### FOR /F %%p IN (%6) DO del /Q "%%p" > NUL 2>NUL goto:EOF ``` **Example:** Post-emission script that deletes the emitted files (format ReportLevel=1) ``` @echo off REM Arguments: REM %1 - Presentation REM %2 - Direction REM %3 - Local code REM %4 - Remote code REM %5 - Application REM %6 - Path of the file with the list of transmitted files echo ############################################### echo POST-EMISSION USER SCRIPT: %0. timestamp echo PRESENTATION : %2-%1 (%3-%4-%5) echo ############################################### FOR /F "tokens=1 delims=," %%p IN (%6) DO del /Q "%%p" > NUL 2>NUL goto:EOF ``` #### Exception. If the user sets any exception program in the configuration, it will be launched when any error occurs during sending or receiving.\ In this way, Editran could be integrated with some alert mechanism developed by the user.\ These programs are invoked with the following arguments: * **0** Program name. * **1** Presentation. * **2** Indicates sending (E) or receiving (R). * **3** Result * **4** Local Code * **5** Remote code * **6** Application **Compatibility with previous versions** The parameters that Editran passes to user programs have changed in this version.\ **It is recommended to adapt the programs developed in previous versions when upgrading the product.**\ If this is not possible, you can continue working with the old programs by configuring the installation to work in compatible mode. This mode is set when the Windows registry contains the DWORD value ***GUpgrade*** in the key *EDITRAN*. ![assets/image45.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-aad67d5d3bc9ec76a7f857cdf3abadba85d63b0d%2Fimage45.png?alt=media) ### Commands **gload53** **Description**\ Command for processing the application files to be sent. Processing consists of transforming and packaging the application files into the file *buffer.* This command is invoked by the process **editrang** when the remote version of the profile is 5.3. **Syntax** ``` gload53. EDItran/G conversion command. Usage: gload53 : Presentation identity. ``` **gload\[50|51|52]** **Description**\ Application file processing command when the remote version of the profile is lower than 5.3. **Syntax** ``` gload[50|51|52]. EDItran/G conversion command. Usage: gload[50|51|52] : Presentation identity. ``` **gunload53** **Description**\ Command for processing the received application files.\ Processing consists of unpacking and transforming the received application files into the file *buffer*.\ This command is invoked by the process **editrang** when the remote version of the profile is 5.3. **Syntax** ``` gunload53. Download command in EDITRAN/G. Usage: gunload53 : Presentation identity. ``` **gunload\[50|51|52]** **Description** Application file processing command when the remote version of the profile is lower than 5.3. **Syntax** ``` gunload[50|51|52]. Download command in EDITRAN/G. Usage: gunload[50|51|52] : Presentation identity. ``` **traduct** **Description** This command allows translating files from **ASCII-EBCDIC** and from **EBCDIC-ASCII**. If you want to change certain characters in the standard tables, the following tables must be generated: * Modifications to the table **ASCII->EBCDIC** must be written in the file **toebcdic.tbl**. * Modifications to the table **EBCDIC->ASCII** must be written in the file **toascii.tbl**. The modifiable characters are the non-alphanumeric ones (a-z, A-Z, 0-9). The characters specified in the text files must be written in hexadecimal format. Each modification must be written on one line. On each line, the character to be translated is written followed by the translated character, separated by a blank space. **Example:**\ To modify the translation of the characters Ñ ñ Ç ç (hexadecimal \[decimal] in\ ASCII: A5\[165], A4\[164], 80\[128] and 87\[135] respectively), currently translated to EBCDIC by: AC, 8F, 66 and 8E respectively, we want them translated by: 7B, 6A, 68 and 67.\ The following must be written in the file "toebcdic.tbl":\ A5 7B\ A4 6A\ 80 68\ 87 67\ In version 5.0, the standard ASCII/EBCDIC tables used by EDITRAN have been changed. To make upgrading easier, in cases where local conversion tables had to be used, the new -m option has been included.\ With this option, by specifying the name of the file that stores the current modifications, it is updated with the appropriate values for the new tables. **Example:**\ Suppose an entity had the following ASCII table in reception tableA to adapt the characters Ñ ñ to its environment:\ A4 F1\ A5 D1\ When executing the command: ``` traduct –m r tablaA tabla5A A -> E(41) -> A(50) A ========================== a4 -> 6a -> f1 = f1 a5 -> 7b -> d1 = d1 ``` Each line of the output is interpreted as follows: the ASCII character 0xA4 that, according to the old translation tables, resulted from the EBCDIC character 0x6A, in version 50 would be received as 0xF1, which is the same as the final character of the local table.\ If the new received character is the one we expect, as in this case, the line of the new local table *tabla5A*. **Syntax** ``` traduct. ASCII-EBCDIC translation utility. Usage : traduct -a|e source destination Usage : traduct -t a -t e -c -d -o -x Usage : traduct -v Usage : traduct -m [e|r] tableIn [tableOut] Where: -a : Translation to ASCII. -e : Translation to EBCDIC. source : File to translate (stdin by default) destination: Translated file (stdout by default) -t a : Print the ASCII table. -t e : Print the EBCDIC table (default). -c : Character. -d : Decimal. -o : Octal. -x : Hexadecimal (default). -v : Verification -m [e|r]: Migration of local conversion table send/receive tableIn : File with the table to migrate tableOut: File with the migrated table ``` **igacmd** **Description** This command establishes a communication mechanism between applications or user programs and editran/G, allowing operations to be invoked unattended and automatically.\ It is the equivalent command to the EDITRAN/G manager **menug** interactive.\ It allows procedures associated with sends and/or receives to be built, with chains of new sends or receives. **Syntax** ``` igacmd. EDItran/G requester in command mode. Usage : igacmd -o -p [-v] [-w] Where: -o : Operation to perform. InitE - Initialize send LoadE - Load send Send - Send EndE - Interrupt send InitR - Initialize receive UnloadR - Unload receive Recv - Receive. EndR - Interrupt receive. -p : Presentation identifier. -v : Verbose mode. -w : Wait for request completion. ``` **Example**\ It is desired that at the end of the reception of a given presentation an emission be generated to the remote editran system whose presentation is PRUEBA.\ To do this, the user file after reception will include the following call:\ `igacmd -o Send -p PRUEBA -v` When editran/G invokes the automation associated with the end of reception (previous command), igacmd will in turn send a signal to editran/G indicating that the user has requested a start-of-emission operation for presentation PRUEBA. **Return codes** In general, the return codes for the command are those listed in the section [editrang error codes](#códigos-de-error-editrang) and which correspond to the result of the operation performed by EDITRAN/G when the request is made with the -w option.\ In addition, there are other values to indicate communication problems with EDITRAN/G. | Code | Description | | ---- | -------------------------------------------------------- | | 0 | Successful result | | 60 | Incorrect syntax | | 61 | EDITRAN/G system not started | | 62 | Error communicating with EDITRAN/G when sending request | | 63 | Error communicating with EDITRAN/G when receiving result | **menug** **Description** This command allows direct access to the editran/G manager menu. **estcmd** **Description** This command is used to find out the status of an editran/G presentation. **Syntax** ``` estcmd. Utility for printing EDItran/G presentation status. Use : estcmd E|R [presentation] E|R : Emission or reception. [presentation#] : Presentation identifier. ``` **Return codes:**\ Numeric value from 0 to 6 corresponding to the following states | Code | State | | ---- | ------------ | | 0 | NO ACTIVITY | | 1 | LOAD/UNLOAD | | 2 | LOADED | | 3 | TRANSMITTING | | 4 | TRANSMITTED | | 6 | INTERRUPTED | **igaperfi** **Description** This command is used to manage editran/G profiles in command mode. You can consult detailed information about this utility in the document **Profile Manager**. **modiperfi** **Description** The purpose of the command ***modiperfi*** is to provide the user with a menu-free administration mechanism suitable for unattended administration. With this command the user can modify, simultaneously, as many parameters as desired in multiple sessions **editran/P** or in different presentations **editran/G**, as well as deregister the profiles. More information on usage mode in the document **Profile Manager**. ### Data files #### CFG subfolder * **editrang.cfg**\ Editran/G configuration file. It stores the local profile and the presentation profiles. It is not an editable file; it should only be modified from the user interface. * **ckds.des**\ File that stores the auxiliary keys for exchanging session keys in DES encryption in version 2.2. #### DOC subfolder * **editran.html**\ Editran documentation containing quick configuration and inquiry guides. #### BIN subfolder * **editrang.msg**\ File where the messages shown to the Editran/G operator are stored. **SL subfolder** * **licencia.dat**\ Editran license file. It is used to control the contracted functionality. If this file does not exist or its content is altered, the editran service cannot be started. **utils subfolder** * **U\_PREVIOUS, U\_AFTER, U\_EXCEPTION**\ In this folder, some batch programs are provided as examples for the integration programs that users develop as pre- and post-processors. Functionally, they only print log messages that will remain in *editrang.out*. > ℹ️ *Note:* It is recommended that new user programs be placed in this subfolder or that a specific one be created containing only those files. * **PSTEMIGC, PSTRECGC**\ Batch programs that automate RSA key exchange. They are the user programs after emission and reception of the presentation used by Editran/GC for key transmission. #### LOG subfolder * **editrang.log**\ File created with the command **makelog**. It cyclically stores the summary of the operations performed by Editran/G, so once the maximum number of entries is reached it overwrites the oldest one.\ It can be consulted from the Editran/G menu and through the command ***printlog*** described in the user manual of *Editran/P*. * **editrang.out**\ File where all outputs produced by Editran/G and the procedures and commands launched by this process are recorded. It is the file where the user will find the details of errors produced during the load and unload processes. Below are listed some cases as examples. > ⚠️Important: Files with the "out" extension are plain text and could change from one version to another. Applications should not process that file to extract information from it as they could stop working with product updates. Some cases are listed below as examples. Recorded information of a successful emission: ``` ********************************************************************** CONVERSION TO EMISSION OF THE PRESENTATION [W00000010-L00000010-PRUEBA] DATE-TIME: [04/12/2025 17:35:03] VERSION: [53] # C F A T D L.Reg Modification date Size Sent Loaded Name _________________________________________________________________________________________________________ 1 N B N N 04020 31032023 115853 000000000024 000000000024 000000000024 C:\Documents\Editran\Ficheros\Emitir\1234_30TDES3.txt RESULT: [0] ********************************************************************** ``` Output of an emission that fails because there are no pending files, and configured with the exception program provided in the installation. ``` ********************************************************************** CONVERSION TO EMISSION OF THE PRESENTATION [TEST] DATE-TIME: [04/02/2025 10:25:40] VERSION: [53] RESULT: CFG_NO_FILES [90] ********************************************************************** ################################################################################ EXCEPTION USER SCRIPT: ./utils/U_EXCEPTION. Tue 4 Feb 10:25:40 CET 2025 PRESENTATION : E-TEST (000000010-000000020-PRUEBA) RESULT : [0090] EXIT CODE : 0 ################################################################################ ``` **Log separated by presentation** In this version, editran can be configured so that the information in the file **editrang.out** is separated by presentation. To change it, create in the Windows registry the DWORD value ***GLogPresentacion*** in the editran key as shown in the image. The different files will also be left in the subfolder **log** of the installation and are named **\.log**. Unlike what happens with the file **editrang.out**, these can be moved or deleted without needing to stop the service. ![assets/image46.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-102dd580d67a715df6fe5b3578ab37594e8c6730%2Fimage46.png?alt=media) ### Codes and messages to the operator #### Editran/G Messages These codes are the ones reflected in the file **editrang.log** to indicate the different states a presentation goes through. On the editran/G operator screen, they appear as messages. Next, those codes and messages are detailed, giving a brief explanation or recommended action: *** | MESSAGE | EXPLANATION/RECOMMENDED ACTION | | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Emission load request | A presentation emission load request has been made. | | Emission request | An emission presentation request has been received. | | Request to end emission | An attempt has been made to interrupt the current presentation emission. | | Emission initialization request | A request has been made to cancel the current presentation emission. | | Emission canceled | The request to initialize the emission of the presentation has been processed successfully. | | Emission initialization request | A request has been made to cancel the reception in progress of the presentation. | | Reception cancelled | | | Reception unload request | A reception presentation request has been made. | | Reception request | A presentation reception request has been received. | | Reception end request | A request has been made to interrupt the reception in progress of the presentation. | | The presentation has been started | A request has been made to initialize an emission or reception and the presentation has no pending transmission. | | The presentation is being transmitted | An emission/reception request has been made for a presentation that is already being transmitted. | | Presentation state incompatible with request () | An incompatible request has been made with the status of the presentation. For example: request to initialize an emission presentation that is being transmitted. | | The presentation profile does not exist | Register the corresponding presentation profile in the editran/G administrator. | | The session profile does not exist | Register the corresponding session profile in the editran/P administrator. | | Request emission from editran (AR1) *\* | Editran/P is notified to start the emission of a transmission session of the presentation. | | Request end of emission to Editran (EDP) *\* | editran/P is notified that a transmission session of the presentation be interrupted. | | Emission interrupted | The request to end the emission of the presentation has been processed successfully. | | Correct and completed emission conversion | The buffer loading process to be emitted has been carried out successfully. | | Correct and completed reception converter | The process of downloading the received buffers was completed successfully. | | Emission conversion process error | The loading of buffers to be emitted cannot be performed. Consult the editrang.out file for more details on the error. | | Error in reception conversion process | The unloading of the received buffers cannot be performed. Consult the editrang.out file for more details on the error. | | Request reception from editran (AR2)*\* | editran/P is notified to start the reception of a transmission session of the presentation. | | Request end of reception to Editran (EDR) *\* | editran/P is notified to interrupt the reception of a transmission session of the presentation. | | Reception interrupted | The request to end reception has been processed successfully. | | Editran emission request (A1P) *\* | editran/P notifies that a remote request has been received for the indicated transmission session to be emitted. Buffer loading is ordered if none exist. | | Editran reception request (A2P) *\* | editran/P notifies that a remote request has been received to begin receiving for the indicated transmission session. | | Editran session emitted (A3P) *\* | editran/P notifies that the emission of the buffer file of the indicated session has ended. Emission ends when the A3P messages from all transmission sessions of the presentation have been received. | | Editran session received (A4P) *\* | editran/P notifies that the reception of the buffer file of the indicated session has ended. When all A4P messages from the presentation's transmission sessions have been received, the buffer unloading process is performed, which ends the reception. | | Editran session interrupted (A7I) *\* | editran/P notifies that the indicated transmission session has been interrupted. | | Post-emission end editran session (A3R) | Response to editran/P for message A3P. | | End after reception editran session (A4R) | Response to editran/P for message A4P. | | No buffer available (A1R-) *\* | Response sent to editran/P when the loading process fails upon receiving message A1P. The remote that made the request will receive an A7I message with code 121. | | Launch previous user process | The user process indicated in profiles has been launched. | | Previous user process finished | The user process indicated in profiles has finished successfully. | | Error in previous user process | The user process indicated in profiles has finished with an error. Consult the cause in the editrang.out file. | | Launch post user process | The user process indicated in profiles has been launched. | | Post user process finished | The user process indicated in profiles has finished successfully. | | Error in post user process | The user process indicated in profiles has finished with an error. Consult the cause in the editrang.out file. | | No buffer available (A2R-) *\* | Response sent to editran/P when the reception preparation process fails upon receiving message A2P. | | Waiting for remote unload acknowledgment | The emission is TRANSMITTED but the remote unload acknowledgment is still awaited in order to consider it finished. | | Unload acknowledgment received: | Unload acknowledgment reception status. | | Unload acknowledgment sent: | Unload acknowledgment sending status. | | Cancelled waiting for remote unload acknowledgment | The user has decided to initialize an emission that was pending receipt of the unload acknowledgment. | | Transmission completed successfully \[*\*] | Informational message upon completing an EMISSION or RECEPTION. | | Exception: *\* | A runtime error has occurred. | #### Editran/G error codes This table documents the different error codes that can occur during a transmission. The table shows: *COD* is the numeric value passed as a parameter to the exception user script that runs when the transmission fails. If the command ***igacmd*** as an API of editran/G is the returned value when used with the option ***--w*** (wait for transmission to finish). *ID* is the alias that identifies the error in the messages recorded in the Log file. *MESSAGE* is a brief description of the reason for the error. *** | *COD* | *ID* | *MESSAGE* | | ----- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 0 | | Successful result | | 1 | CMD\_EXEC | System error: process creation. | | 50 | APIG\_SNTX | APIG: incorrect parameters. | | 51 | APIG\_INIT | APIG: editran/G not started or not accessible. | | 52 | APIG\_GREQ | APIG: Error communicating with editran/G (request). | | 54 | APIG\_GRES | APIG: Error communicating with editran/G (response). | | 62 | NO\_TAMPON | Incorrect buffer file format. | | 64 | OPEN\_IN | Error opening application file to be emitted. | | 65 | OPEN\_OUT | Error opening application file to be received. | | 66 | READ\_CTRL | Error reading control information in TAMPON or CSB. | | 67 | WRITE\_CTRL | Error writing control information in TAMPON or CSB. | | 68 | WRITE\_DATA | Error writing data in TAMPON or CSB. | | 69 | ZERO\_REC | TAMPON file without loaded records. | | 70 | ALLOC\_ERROR | System error: memory management. | | 71 | SAVE\_REL | Error saving list of transmitted files. | | 73 | WRITE\_OUT | Error writing application file to be received. | | 74 | SEQUENCE\_CSB | Incorrect CSB file: sequence error. | | 75 | TOTAL\_FILES | Incorrect CSB file: error in the total number of files. | | 76 | TYPE\_FILE | Unknown file format. | | 77 | LENGTH\_CSBREC | Incorrect CSB file: error in file length. | | 78 | HASH\_FILE | Error calculating/verifying application file hash. | | 79 | SIZE\_FILERECS | Mismatch in the number of records in the application file. The total number of records indicated in the CSB control fields does not match those actually unloaded. | | 80 | TOTAL\_CSBRECS | Incorrect CSB file: error in the total number of records. | | 81 | SIZE\_FILEBYTES | Mismatch in the total bytes of the application file. The number of bytes indicated in the CSB control fields does not match those actually unloaded. | | 82 | SYNCS\_CSB | Mismatch in the number of synchronizations in CSB. | | 83 | CFG\_LENGTH | Application file with fewer records than specified in the profile. Check the characteristics of the files to be emitted. | | 84 | STS\_RECV | Error in the unloading process because not all buffer files of the presentation have been received. | | 85 | OPEN\_CSB | Error opening/creating CSB file. | | 86 | NO\_PERFILG\_LOCAL | No local editran/G profile exists. | | 87 | NO\_PERFILG | The Presentation profile does not exist. | | 90 | CFG\_NO\_FILES | None of the files specified in the profile as emission files exist or could be found. | | 91 | USER\_SCRIPT | Error running user script. | | 93 | PROFILES | Presentation profile incompatible with load/unload process. | | 94 | CANCELED\_REQ | Transmission cancelled. | | 95 | PROC\_ERROR | Internal error: task creation in load/unload. | | 96 | RUNTIME\_EXCEPT | System error: "runtime exception". | | 97 | NO\_LICENSE | License issue to perform any of the required functions. | | 98 | CRYPT\_ERROR | Error in cryptographic processing of the data. | | 99 | HDRFILE | Internal error: invalid control headers. | | 200 | NO\_ACK | Remote unload could not be confirmed. | | 201 | NO\_STATE | Request incompatible with transmission state. | | 104 | EXCEPT\_P | Editran/P: Abort | | 110 | EXCEPT\_P | Editran/P: Operator | | 120 | EXCEPT\_P | Editran/P: Incorrect remote buffer. Launch previous. | | 121 | EXCEPT\_P | Editran/P: Incorrect remote buffer. No previous exists. | | 122 | EXCEPT\_P | Editran/P: Incorrect remote buffer. Previous possibly running | | 123 | EXCEPT\_P | Editran/P: Incorrect remote buffer. Incorrect exchange session number | | 124 | EXCEPT\_P | Editran/P: Incorrect remote buffer. Total number of records | | 130 | EXCEPT\_P | Editran/P: Release. | | 140 | EXCEPT\_P | Editran/P: Excess retries to emit. | | 160 | EXCEPT\_P | Editran/P: Total mismatch. | | 170 | EXCEPT\_P | Editran/P: Excess synchronization retries. | | 190 | EXCEPT\_P | Editran/P: Excess retries for end of emission. | | 240 | EXCEPT\_P | Editran/P: Profiles. | | 250 | EXCEPT\_P | Editran/P: File not ready. | **A7I code table** In the previous list of error codes there are some that are due to problems with transmission sessions. In these cases the following message only appears in the editran/G log: *"Editran session interrupted (A7I) \[E|R]COD"*. For each value, the reason is explained in more detail and whether it can be resolved without operator intervention. *** | CODE. | CAUSE | EXPLANATION | | ----- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 104 | Abort | Unexpected interruption due to unknown cause. | | 110 | Operator | Interruption requested by the operator. | | 120 | Incorrect remote buffer. Previous launch. | The remote entity does not have its Buffer File. Available launch. The remote editran will automatically start the process that prepares the Buffer File and will request the transmission if the profile allows it. This code is only given when the remote entities are zOS or iSeries. | | 121 | Incorrect remote buffer. No previous buffer exists. | The remote entity does not have its Buffer File available. The remote editran is not configured to automatically start the process that prepares it, so it will not get out of this situation until the remote operator acts. | | 122 | Incorrect remote buffer. Previous may be running. | The remote entity does not have its Buffer File available because it is still in use. In many cases this may be because the remote editran is still in the download process. | | 123 | Incorrect remote buffer. Incorrect exchange session number. | The remote Buffer is in an incorrect state. The exchange number does not match. It is necessary to initialize the presentation, at least at one end. | | 124 | Incorrect remote buffer. Receiver total number of records. | The remote Buffer is in an incorrect state. The total number of records does not match. The receiver must be initialized. | | 130 | Release | Interruption due to a connection release. | | 140 | Excessive retries to transmit. | The entity requesting the transmission does not receive a response from the remote side. This is usually due to some temporary communication problem but should be analyzed by the operator. | | 170 | Excessive synchronization retries. | The sending entity does not receive the remote confirmation of having received a burst of data. It may be due to slow communications and could be solved by decreasing the parameter ***No. of records per transmission block*** in the transmission session profile. | | 190 | Excessive transmission retries. | The sending entity does not receive the remote end-of-transmission confirmation. This situation may make it necessary for both entities to remain in different states and for initialization to be required at one of the ends. | | 240 | Profiles | Transmission is interrupted because one of the session profile parameters is not compatible with the loaded buffer file. For example, if it is encrypted and the session is configured to compress during transmission. It is not recoverable without operator intervention. | | 250 | File not ready. | Transmission is interrupted because the local Buffer File is in an incorrect state. In these cases, it is advisable to initialize the Presentation. | --- # 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.3-en/windows/interfaz_generica.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.