> 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/linux/interfaz_generica.md). # Editran/G management ## Onesait Editran/G Management When running **menug** in the Editran directory, the general menu of the Editran /G manager shown below will be activated: ![assets/image4.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-19cca8bfa388eb5b5486c831b6fbeeb4e6be92ab%2Fimage4.png?alt=media) ### Operation interface In the screens included in this document, the different types of fields are represented as follows: #### Screens On the Editran/G menu system screens, three areas can be distinguished: ![assets/image5.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-f9061d7645b5b567afbe54c7ccfd2b8a0d814be5%2Fimage5.png?alt=media) In the title area, general information about Editran /G appears: * Current date and time (at the moment the screen is activated). * Screen object: administrator, operator, etc. * Version. * **Options** In this area, the different options of a menu, the parameters the operator must enter, or the results of the requested queries may appear. * **Information** In this area, the progress information of the presentations sent by the system to the operator appears: * Presentation. * Emission and reception states. * Progress information text. #### Help It has a context-sensitive help system. In this way, when the F1 or ? keys are pressed, a window appears with the help text associated with the field or screen where the cursor is at that moment. #### Keys In Editran/G, and within the menu, the following keys can be used: | | | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | F1 ? | Context-sensitive help. | | F2 | Enters the default values of the current field, whenever possible. | | F3 | Ends data entry for the current screen, validating all fields. | | F4 | Enters the default values for the entire current screen, whenever possible. | | F6 | Performs a return to the operating system to execute other commands (shell), leaving EDITRAN/G resident. To return to EDITRAN/G, the exit command must be executed. | | Enter | Ends data entry for the current field, updating its value. If no value has been entered, it inserts the one from the last request. | | Space | Selects the field value from a list of enumerated values: | | | A (o) B ( ) C ( ) | | | or activates/deactivates the field value for a field with only two possible values | | | possible: | | | D \[X] | | Esc | Aborts data entry and returns to the previous menu. | | Delete | Deletes the character before the cursor. | | Tab | Moves to the next field without updating or modifying the value. | | Arrows | Move the cursor on the screen to the next/previous field or the next/previous value within the field. | | PgUp | Page up. | | Control-U | | | PgDn | Page down. | | Control-D | | | | | #### Selection by List In the menus of **Operator** and **Administrator** described below, the user must enter a presentation name. In these cases, if instead of a specific name a search filter with a valid mask is entered (such as \*, **?**), a screen will be displayed with the list of presentations that match the given filter. The following screen is an example in which emissions are launched from the resulting list after selecting the presentations that end in 14 (\*14). ![assets/image6.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-1ab3594a28e87cf5711881b0a8eaf5a6c2dcf4e9%2Fimage6.png?alt=media) ### Onesait Editran/G Operator To operate on exchange presentations, select option 1 from the main GESTOR DE Editran/G menu. The following options will be presented: ![assets/image7.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-8291e1ab03952634eb8342d79cb229b6b5f64a92%2Fimage7.png?alt=media) #### Load Emission Presentation * This option is only allowed when the Presentation has no activity or when it is *LOADED* and the profile is configured to allow cumulative loading. In any other case, the following message will be shown to the user *"Presentation state incompatible with the request"*. * If the request is accepted, the presentation moves to the temporary state *LOADING* in which the following steps are performed: * The pre-emission user program is executed, if it exists in the profile. * The converter program corresponding to the remote entity's version is executed. This program creates the buffer files that package the data to be transmitted. * If the loading process finishes correctly, the final state will be *LOADED*. If an error occurs, the corresponding message will be displayed and it will remain in the initial state. The image shows an example of a presentation load request for which there are no files to transmit. #### Initialize Emission Presentation Each time the transmission of a presentation ends successfully, it returns to the initial state. If for some reason an emission is interrupted and you want to cancel it to start another one 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. #### Emit Presentation This operation is accepted when the presentation emission state is: inactive (*...*), *LOADED* or *INTERRUPTED*). In general, it is the only request made to emit since, if necessary, the loading process discussed in the previous point is carried out first. Once *LOADED* as many A1R messages are sent to Editran/P as transmission sessions the presentation uses. The same is done if it were *INTERRUPTED* except that in this case, transmission will resume from the point where it stopped. The emission state changes to *TRANSMITTING* and waits to receive the notification from Editran/P of the end of the transmission(s). In the image, a typical sequence of log messages associated with an emission request for a presentation with a single transmission session. #### Interrupt Emission Presentation Option that allows the Editran operator to stop the ongoing emission (state *TRANSMITTING*). For this, each transmission session of the presentation is notified to be interrupted via the EDP message. The presentation state temporarily changes to *INTERRUPTED*, but it can be resumed by requesting the emission again. #### Initialize Reception Presentation As explained for emissions, each time the transmission of a presentation ends 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 using this option. The initialization process removes all control information from the current transmission so that the next one starts from scratch. #### Download Reception Presentation In the reception process, the download or transformation of the received buffer files is performed automatically. This means this option only has to be used exceptionally when, due to some failure, the presentation state ends up 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 try the download again. In the INTERRUPTED state this option is also allowed, but in this case there is an additional check that the total data really has 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 begin a new reception. Only when the download process finishes 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. #### Receive Presentation Each presentation in Editran can be configured to allow the remote entity to connect and send (server mode) or to allow transmission requests to be made only from the entity itself, both to emit and receive (client mode). Whenever you want to start a connection with the remote Editran to retrieve the files it has available for the presentation, this option will be chosen. Depending on the state of that presentation, the response will be different. If the presentation is inactive, that is, a new reception begins, the user program configured as previous is launched, and message A2R is sent to each transmission session. The presentation state changes to *TRANSMITTING* until receiving the notification from Editran/P of the end of the transmission(s) (A4P). In state *INTERRUPTED* the behavior is the same, except that the pre-user program is not launched since the transmission resumes from where it left off, avoiding retransmitting the already exchanged volume. In any other state, the following message will be shown to the user *"Presentation state incompatible with the request"* since a presentation can have only one transmission in progress. A special case is the state *TRANSMITTED* in which the buffers have been received, but the download process fails. In this case, it can be retried once the problem has been solved using the option *Download Reception Presentation*. In the image, a typical sequence of log messages associated with a reception request for a presentation with a single transmission session. #### Interrupt Reception Presentation The Editran operator can interrupt any reception in progress (state *TRANSMITTING*). For this, each transmission session of the presentation is notified to disconnect via the EDR message. The presentation state temporarily changes to *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 #### Presentation State Query To query a particular presentation, type the presentation and press Enter. In the screen information area (bottom) the emission and reception status information of the requested presentation will appear. ### Control File Manager ![assets/image8.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-3d6b49f61201ad34526f124d8ffc18015730eb92%2Fimage8.png?alt=media) Select the desired option and press Enter. #### Presentation State Query ![assets/image9.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-6ef6ae4644d132d109a279fc95fc022fdd20e4a4%2Fimage9.png?alt=media) Select the presentation to query and press Enter. ![assets/image10.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-cb9763c76e794b2312302dc6ba4c222435569289%2Fimage10.png?alt=media) **Presentation Status** It can 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 | 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 State Modification * **Pending Presentation** * Its value is **Yes** when a load has occurred and it has not yet been emitted. * **Presentation** * The presentation number is initialized to 1. It is incremented by one each time the presentation emission load is performed and more specifically when the state of the emission presentation changes from NOT LOADED to BUFFER LOADED, although this state automatically evolves to BUFFER LOADED and subsequently to TRANSMITTING. * **Editran sessions** * As many lines appear as transmission sessions are used in the presentation, up to a maximum of 20. Each line shows: session and description of the session state and date and time of the state change. Modifying presentation states is an extraordinary operation that should only be performed in anomalous circumstances, with the "Increase presentation number" option activated ![assets/image11.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-921a348cdb0b5f4dd6109b11598af265f9fe312e%2Fimage11.png?alt=media) The presentation session number is shown, which can be modified, and you are asked whether you want to initialize the presentation states. Enter S or N; if S, the states will change to NOT LOADED. With Enter the modification is carried out and with Esc it is canceled. ![assets/image12.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-eeb4e40294ea75421bebf7a600b277e2bdb4c459%2Fimage12.png?alt=media) #### LOG Query ![assets/image13.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-34a30eed00a918b73d316df311ed546d94584241%2Fimage13.png?alt=media) This data is used in the selection criteria for the log query. Messages generated from the entered date are displayed. * **PRESENTATION**: A specific one, a mask (for example, P\* to see all those that start with P) or zeros or blank for all. * **DATE**: Starting from a specific one or none to show the last recorded information. * **TIME**: Starting from a specific one within a date ![assets/image14.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-be032b22baa947e87147109581f170cfe02e7882%2Fimage14.png?alt=media) Once inside the log query, you navigate through it using PgUp or Ctrl-U to see the previous page and PgDn or Ctrl-D to see the next page. With Esc you will return to the query options screen. The presentation session and the date, time, and message text are shown. ### Onesait Editran/G Administrator Access the Editran/G administrator by selecting option 3 from the main menu, presenting the following screen. ![assets/image15.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-f312bc5d11decae631d075a7ebc3cb2b231a3f8d%2Fimage15.png?alt=media) #### Remote Entity Profile ![assets/image16.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-76b83d26cd9b7e37db82aea82e1984aa64a8a112%2Fimage16.png?alt=media) Enter the desired option and the code of the remote entity, which must be the same as the one used in Editran/P. ![assets/image17.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-d3864d974dcf04a9a05c0094f050ed4435fe5632%2Fimage17.png?alt=media) * **DESCRIPTION** Descriptive name of the remote entity. * **REMOTE EDITRAN/G VERSION** | | | | ------- | ---------------------------------------------------- | | **4.1** | If the remote entity is going to use Editran/G v4.1. | | **5.0** | If the remote entity is going to use Editran/G v5.0. | | **5.1** | If the remote entity is going to use Editran/G v5.1. | | **5.2** | If the remote entity is going to use Editran/G v5.2. | | | | * **ASCII/EBCDIC** * **A** ASCII * **E** EBCDIC * It is necessary to provide the character set used by the remote machine, ASCII or EBCDIC, whenever the remote version is lower than 5.0. This does not imply that data translation will be performed; that is determined in the list of files to be emitted. * **CRYPTOGRAPHY PARAMETERS** In the cryptography data section, the type of security used to protect the information exchanged by this presentation is established. The configured options here only affect the handling of the data during the creation of Editran buffers. Although it is recommended to use cryptography at this level of the protocol, it could also be selected **No** and protect only the transmission by properly configuring the Editran/P sessions. * **CRYPTOGRAPHY (Y/N)** * **Y** If you want EDITRAN/G Cryptography. * **N** If you do not want to use EDITRAN/G Cryptography If you select **Y** the rest of the settings that configure the cryptographic system are established. * **CRYPTOGRAPHY VERSION** * 2.2 > In this mode, DES encryption is performed on the buffer files. The keys used are simple and must have been previously exchanged through a connection with the remote entity configured for this purpose. * 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 allowed is RSA, extending the key length up to 4096. The hash algorithm used in the signature is sha-256. * **CONFIDENTIALITY ALGORITHM** * Algorithm to use to encrypt the data. Leave blank if you do not want data encryption. * **DES** if you want DES encryption. * **TD2** TRIPLE-DES encryption with double key. * **TD3** TRIPLE-DES encryption with 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 cryptography is enabled. * **DES** if you want to authenticate the ends (valid only for 3.0). * **RSA** if you want to authenticate the ends (valid for versions 3.0 and 4.0) * **V3.0 KEY MANAGEMENT** The keys used in public-key cryptography (RSA) are exchanged between entities with the product utility designed for this purpose: Editran/GC. If this field is set to **Y** (Yes), the active key of the configured subsystems is used. Consult the user manual of E*ditran/GC Key Management* for more information about the utility. * **LOCAL KEY** * Label of the DES auxiliary key, private RSA, mandatory when the Cryptography version is 3.0 and there is authentication. * **REMOTE KEY** * Label of the DES auxiliary key, public RSA, mandatory when the Cryptography version is 3.0 and there is authentication With Enter the record is created. With Esc you leave. The values of a remote entity's data are passed to that entity's presentations, when they are created, as default values. Modifying and querying a remote entity profile are done in the same way as creation, but the profile must already exist. The modified values are not propagated to the matching values of presentations of the same entity. In the deletion of a remote entity profile, a screen identical to the one described first appears. With Enter the deletion is confirmed and with Esc it is canceled. In all options, except creation, filters can be used to select the presentation from the list of possible ones. #### Application Profile ![assets/image18.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-6b1a47071f772198820aaf7ca70041048ab85d5a%2Fimage18.png?alt=media) ![assets/image19.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-17aa7585ee368e4f52afc0b7f5ba14de2f431534%2Fimage19.png?alt=media) * **DESCRIPTION** Name of the presentation application. * **CONVERSION TABLES** These are text files edited by the user with the correspondence table between the local character encoding scheme and the one used by EDITRAN, for both emission and reception. Each line will be of the following type, defining the characters in hexadecimal: \ \ If no local translation is needed, these fields will 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 ASCII, or 'E' if EBCDIC. For example, assuming the user creates the file mitablaA to translate ASCII characters, only mitabla would be entered in the profile. > The table files must be located in the subfolder *bin* of Editran. * **USER PROGRAMS** Called by Editran/G before and after emitting and receiving. The exception program is executed whenever an error occurs in sending. These programs will be provided by the user when they want to use this feature to integrate the product with other systems. Sample scripts are delivered with the Editran software that can be used as a template. These fields are left blank by default. The exception program **utils/U\_EXCEPTION** can be used if you want to leave a record in the log files of transmissions that are interrupted. With Enter the record is created. With Esc you leave. The values of an application presentation's data are passed to that entity's presentations, when they are created, as default values. Modifying and querying an application presentation profile are done in the same way as creation, but the profile must already exist. The modified values are not propagated to the matching values of presentations of the same entity. #### Presentation ![assets/image20.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-f0eba8fdb0e689f87b98dcd66c4f3193882d3c17%2Fimage20.png?alt=media) Enter the desired option and the codes for the remote entity and the presentation application. If those profiles already exist, the screens will use their data as a template; otherwise, the user must fill them in at this time. To navigate through them you must use the arrow keys, Esc to cancel creation, Enter to advance and to execute the creation, and F3 to finish data entry for the current screen, validating all fields. The entered data are validated in all cases except when Esc is pressed. \**\** * **Presentation Identification Data** ![assets/image21.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-4418bc8e25dfe33a6410f15471fe39807ad0d13f%2Fimage21.png?alt=media) * **Remote Data** ![assets/image22.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-639ae77bf7dd0a69c65314ed09b94932654f79a4%2Fimage22.png?alt=media) They are the ones described in the section **REMOTE ENTITY PROFILE.** * **Application Data** ![assets/image23.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-39c6079fc6826cfe3f54790f8d63f5f9597ff87d%2Fimage23.png?alt=media) In the section **APPLICATION PROFILE** general data and User programs are described. * **EDITRAN FF - CHECK SIGNATURES** > If this functionality is activated (with option Y), in the Editran/G load process an Editran/FF service is called that communicates the list of files that meet the signature workflow established in the profile of an FF Application. > > In the section [Sending operations using integrated Editran/FF](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/open/5.2.1/linux/interfaz_generica/README.md#operación-de-envíos-utilizando-editranff-integrado) this option is explained in more detail. * **Presentation Data** ![assets/image24.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-4a6313b21d8643ffca465cc3202d34510b93caef%2Fimage24.png?alt=media) * **INCREASE PRESENTATION NO. (Y/N)** > Specifies whether the presentation number and therefore the exchange session number of each of the Editran/P sessions associated with it should be incremented or not in the previous emission and reception processes. * **LOAD TYPE** > With cumulative load type, the buffer can be reloaded with new application files, as long as transmission has not started. Cumulative loading requires the use of a single transmission session. > > **N** A single load per emission. > > **A** Allows loading several times before emitting. * **REQUEST DOWNLOAD CONFIRMATION** > With remote download confirmation, the emission will not be considered complete until the result of its download is received from the remote side. When the download ends with an error, the post-reception user process will receive the value indicating it in the result parameter. In reception, the result of the last download is returned whenever the remote requests it. * **NUMBER OF TRANSMISSION SESSIONS** > Number of EDITRAN/P sessions associated with the editran/G presentation. Next, you must specify which ones they are. These sessions must have been created beforehand. All EDITRAN/P sessions will have the same local and remote codes as the editran/G presentation. * **SPLITTING CRITERION (V/S/F/N)** > Only if several transmission sessions are going to be used for the presentation. The following values can be specified: > > **V** The emission application information would be evenly distributed among the different buffers, with a minimum of 400,000 octets per buffer. This means that some of the transmission sessions defined in the presentation might not be used. > > **F** File-based distribution. Successive complete files would be assigned to each emission buffer. > > **N** No split is performed. * **Editran/P Applications** > Name of the Editran/P applications corresponding to the transmission sessions of the presentation. The table will be filled with as many elements as indicated by the number of sessions field. It is validated that the entered sessions exist. * **File Data** ![assets/image25.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-2b73b868f97e64acf5659a0a45515bb5a098b4eb%2Fimage25.png?alt=media) * **PRESENTATION EMISSION FILES** > The section consists of 7 columns: * First column: **COM** > Refers to the compression of the file or files we want to send and can have the following values: > > **F** Compression enabled. > > **N** Compression disabled. * Second column: **FMT** > Refers to the format of the files we want to send and can have the following values: > > **F** Fixed. Application files are read as fixed-length records. The length is determined by the next parameter. > > In this format there is the optional possibility of removing delimiters (line break). > > **V** Variable. Application files are read line by line, with the line delimiter being CR-LF characters on PCs and CR on UNIX machines. These delimiter characters are not sent to the remote system; in the remote conversion process the inverse operation is performed, inserting the appropriate line delimiter characters for the receiving system. This is the format that should be used to transmit text files between heterogeneous environments (UNIX PC, UNIX CICS, etc.). > > **H** Hybrid. Files are read as variable and sent to the remote system as fixed, filling each line with spaces until the record length defined in the field is completed **LONG**. > > **B** Binary. Transparent mode (no transformations). > > Only for homogeneous environments if the remote version is higher than 4.1. * Third column: **LONG** > Refers to the record length of the file or files we want to send. * Fourth column: **DEL** > Only applies to files with Fixed format. In these cases, it is indicated whether each record ends with a line break or not, and whether it is Unix format (**U**) or Windows (**D**). * Fifth column: **ALF** > Refers to the alphabet that the file or files we want to send have and can have the following values: > > **A ASCII**. The data in the file or files are in ASCII. > > **E EBCDIC**. The data in the file or files are in EBCDIC. * Sixth column: **TRA** > Refers to whether we want to translate the alphabet of the files we want to send and can have the following values: > > **Y** if you want to translate. > > **N** if you do not want to translate. > > Currently there is a wide variety of encodings that extend US-ASCII (codes 0 to 127), so it must be taken into account that for correct display of the file at both ends it is necessary for both platforms to work with compatible tables. For example, if your platform works 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 in the same way. * Seventh column: **NAME** > Refers to the path where the file or files to be sent are located. * **RECEPTION DESTINATION** > It is the path where the received files will be placed. As the file name, a mask can be specified using the wildcards mentioned below. During download, the names of the files are transformed one by one applying the given format. Characters not allowed by the operating system cannot be defined (\\, /, :, ?, \*, ", <, >, etc.). > > Wildcards can be used in reception. * **DELIMITER (D/U/N):** > **D** Downloads Fixed files with the Windows delimiter. > > **U** Downloads Fixed files with the Unix delimiter. > > **N** Downloads Fixed files without adding a delimiter. * **TRANSLATE (A/E/N):** > **A** Translated to ASCII if received in EBCDIC. > > **E** Translated to EBCDIC if received in ASCII. > > **N** Not translated. #### Generic profile query ![assets/image26.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-2fa744c7678e59faf258233c4b5800f025af2d62%2Fimage26.png?alt=media) **Remote entities** A list of remote entities is obtained with the data of the Presentations in which they are being used. If they occupy more than one screen, navigate between them with PgUp or Ctrl-U for previous page and PgDn or Ctrl-D for next page. Press ESC to return to the generic query menu. ![assets/image27.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-16106dafbdecb2e421079d0bdb5ee0a6943efaae%2Fimage27.png?alt=media) **Applications** A list of applications is obtained with the data of the presentations in which they are being used. If they occupy more than one screen, navigate through them with PgUp or Ctrl-U for previous page and PgDn or Ctrl-D for next page. Press Esc to return to the generic query menu. ![assets/image28.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-4cda7f2a7d06fe724a458fd878e9a7cea22086cd%2Fimage28.png?alt=media) **Presentations** A list of presentations is obtained with their description. If they occupy more than one screen, navigate between them with PgUp or Ctrl-U for previous page and PgDn or Ctrl-D for next page. Press Esc to return to the generic query menu. ![assets/image29.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-3557212ed101f0e58611cab25c7544a6908bf2db%2Fimage29.png?alt=media) ### Sending operations using integrated Editran/FF #### Editran/G configuration to connect to the Editran/FF server To use the functionality of sending files signed by FF, the Editran environment must be configured to communicate with the available Editran/FF server. On Unix, this configuration is located in the folders **cfg** and **bin** of the product, where the data that allow communication between Editran and the FF server are established. In **cfg** File: **distributed.cfg** ![assets/image30.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-947ec7c2cb3c30de5c10c21feb3aeb35dedb17f0%2Fimage30.png?alt=media) It must be configured with the IP address or *hostname*, plus the listening port of the machine where the Editran/FF server is installed (the default port is the **8300**). If the FF server is installed on the same machine where Editran was installed, the IP address indicated will be: 127.0.0.1:8300 In **bin** File: **EDITRAN** ![assets/image31.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-3766f33b1b47ef49760da7f2dca387c2f7c118ee%2Fimage31.png?alt=media) This variable will indicate the sending directory configured at the general level on the Editran/FF server, in which Editran will look for the signed files ready to be sent. #### Sending signed files with Editran/FF A presentation in Editran/G must be configured so that it takes as data source the Editran/FF applications that have files available for sending. To do this, a new presentation must be created in Editran/G or an existing one edited. Once in the menuG, in the application data of the presentation profile, we have the option of "**Check signatures (Y/N)**": ![assets/image32.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-cc9fe3c39c7da0fbdb8a9637a3c6e8566e061723%2Fimage32.png?alt=media) If communication with the FF server is correct, the FF Application selection screen will appear, similar to the file selection dialog for emission. If communication was not possible, an error message will appear notifying the problem. Instead of files, the Editran/FF applications that have been configured for sending with Editran will be indicated. As many applications as desired can be indicated for sending through the same Editran/G presentation: ![assets/image33.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-c10a320754e92b6f9c60b63f00dc3ea4b2ae301a%2Fimage33.png?alt=media) ## Additional functionality ### Transferred files report The generation of the daily report of transmitted files is an optional feature that the system administrator can activate at the application level. That is, if the report is activated, it will record the files transmitted by all Presentations. To configure this functionality, the script *EDITRAN* the application's runtime environment must be modified. With the service stopped, edit the script to modify the following lines: ![assets/image34.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-6ef6b3ca5356eff32e89019da2aa444c6e4067fc%2Fimage34.png?alt=media) The environment variable must be set *EDI\_REPORT\_PATH* with the path where you want the generated reports to be left. That path must be the absolute path of an existing directory. For example: ![assets/image35.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-a4a7f24ac9aff29fe2610d9ca5dc1358fee19f82%2Fimage35.png?alt=media) The name of the generated reports is *FicherosEditran.\.txt*, where yyyymmdd is the current year, month and day. These are files in csv format with columns separated by ','. Additionally, in the script *EDItran,* the level of detail of the data shown in the reports can be set using the EDI\_REPORT\_LEVEL variable: ![assets/image36.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-62a7e90ce1299415fa4e1a58b60646b4c6978ce3%2Fimage36.png?alt=media) If this variable is not provided, Editran will take 0 as the default value. To give it another value, simply edit the script as follows: ![assets/image37.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-cb3ea9376105eec7c852b9bd61166fb443a52890%2Fimage37.png?alt=media) Below are the fields shown in the daily report of transferred files: *** | **Field** | **Minimum ReportLevel value to display it** | | -------------------- | ------------------------------------------- | | Date-time | 0 | | Send/receive | 0 | | Presentation | 0 | | Local code | 0 | | Remote code | 0 | | Application | 0 | | File path | 0 | | Format | 0 | | Source alphabet | 0 | | Compressed | 0 | | Encrypted | 0 | | Size in bytes | 0 | | Delimiter | 1 | | Destination alphabet | 1 | | Signed | 1 | | Source file name | 1 | | Record length | 1 | | Number of records | 1 | | Concatenated file | 1 | ## Attachments ### Reception destination wildcards The wildcards that can be specified are: | | | | ------ | ---------------------------------------------------------- | | **+** | If the file exists, append to the previous one | | **-** | If the file exists, destroy the previous one | | **%o** | Original name of 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** the precision of the digits to define can be set by adding a number before the wildcard letter. For example, if %4c is defined, 4 digits will be written. * **Reception destination examples** In the examples, the remote entity sends us 4 files. * Case 1 > We configure the following reception destination: **../destination\_directory or ../destination\_directory/%o** *** | **Sent files** | **Downloaded files** | | -------------- | ------------------------------- | | a.txt | ../destination\_directory/a.txt | | b.txt | ../destination\_directory/b.txt | | c.txt | ../destination\_directory/c.txt | | d.txt | ../destination\_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 reception destination: **../destination\_directory/+bank\_%D-%M-%Y\_%h-%m-%s** *** | Sent files | **Downloaded files** | | ---------- | ---------------------------------------------------- | | a.txt | ../destination\_directory/bank\_17-10-2014\_14-00-01 | | b.txt | ../destination\_directory/bank\_17-10-2014\_14-00-02 | | c.txt | ../destination\_directory/bank\_17-10-2014\_14-00-03 | | d.txt | ../destination\_directory/bank\_17-10-2014\_14-00-03 | | | | > Several files are downloaded, 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 reception destination: **../destination\_directory/bank-%D-%M-%Y\_%4c** *** | **Sent files** | **Downloaded files** | | -------------- | ----------------------------------------------- | | a.txt | ../destination\_directory/bank\_17-10-2014-0000 | | b.txt | ../destination\_directory/bank\_17-10-2014-0001 | | c.txt | ../destination\_directory/bank\_17-10-2014-0002 | | d.txt | ../destination\_directory/bank\_17-10-2014-0003 | | | | > Several files are downloaded in the same session and for each one the day, month and year are defined, plus a 4-digit counter (%4c). * Case 4 > We configure the following reception destination: **../destination\_directory/bank\_%o** *** | **Sent files** | **Downloaded files** | | -------------- | ------------------------------------- | | a.txt | ../destination\_directory/bank\_a.txt | | b.txt | ../destination\_directory/bank\_b.txt | | c.txt | ../destination\_directory/bank\_c.txt | | d.txt | ../destination\_directory/bank\_d.txt | | | | > The downloaded files will have the defined name plus the original one (including the extension). * Case 5 > We configure the following reception destination: **../destination\_directory/+unique\_file** *** | **Sent files** | **Downloaded files** | | -------------- | -------------------------------------- | | a.txt | ../destination\_directory/unique\_file | | b.txt | ../destination\_directory/unique\_file | | c.txt | ../destination\_directory/unique\_file | | d.txt | ../destination\_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 reception destination: **../destination\_directory/unique\_file** *** | **Sent files** | **Downloaded files** | | -------------- | -------------------------------------- | | a.txt | ../destination\_directory/unique\_file | | b.txt | ../destination\_directory/unique\_file | | c.txt | ../destination\_directory/unique\_file | | d.txt | ../destination\_directory/unique\_file | | | | > As 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 reception destination: **../destination-directory/%o\_%D-%M-%Y** *** | Sent files | **Downloaded files** | | ---------- | ----------------------------------------- | | a.txt | ../destination\_directory/a.txt\_17-10-20 | | b.txt | ../destination\_directory/b.txt\_17-10-20 | | c.txt | ../destination\_directory/c.txt\_17-10-20 | | d.txt | ../destination\_directory/d.txt\_17-10-20 | | | | > Several files are downloaded in the same session and for each one the original name defined by the remote side (including the extension), the day, month and year are defined. ### 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 Emission/Reception**. 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 Emission/Reception**. If the user sets any program in the configuration, it will be launched when the transmission finishes successfully. Each time a presentation is emitted or received, a file is generated with the list of transmitted files. This file is the one recommended for integration with other applications. It could, for example, be used to store the paths of transmitted files in a 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. New in v5.2 Each sent/received file listing file has the following fields separated by ',': | **File field** | **Minimum EDI\_REPORT\_LEVEL value to display it** | | ----------------- | -------------------------------------------------- | | File path | 0 | | Format | 1 | | Record length | 1 | | Number of records | 1 | | Concatenated file | 1 | | | | * **Example:** script that deletes the emitted files (with EDI\_REPORT\_LEVEL=0 format) \#!/bin/sh \#Arguments: \# $1 - Presentation \# $2 - Direction \# $3 - Local code \# $4 - Remote code \# $5 - Application \# $6 - Path of the file with the list of transmitted files EXIT\_STATUS="" echo "################################################################################" echo "Emitted files are deleted by \[ $0 ]" echo "\`date\`" echo "PRESENTATION: $2-$1 ($3-$4-$5)" echo "FILES: \[$6]" while read fclave do if \[ "$fclave" != "" ]; then echo "File $fclave deleted" rm "$fclave" fi done < $6 EXIT\_STATUS="$?" echo "EXIT CODE : ${EXIT\_STATUS}" echo "##############################################################" exit ${EXIT\_STATUS} * **Example:** script that deletes the emitted files (with EDI\_REPORT\_LEVEL=1 format) \#!/bin/sh \#Arguments: \# $1 - Presentation \# $2 - Direction \# $3 - Local code \# $4 - Remote code \# $5 - Application \# $6 - Path of the file with the list of transmitted files EXIT\_STATUS="" echo "################################################################################" echo "Emitted files are deleted by \[ $0 ]" echo "\`date\`" echo "PRESENTATION: $2-$1 ($3-$4-$5)" echo "FILES: \[$6]" awk -F',' '{if ($1 != "") print $1}' $6 | while read fclave do if \[ -f "${fclave}" ]; then rm "${fclave}" echo "File $fclave deleted" fi fi done EXIT\_STATUS="$?" echo "EXIT CODE : ${EXIT\_STATUS}" echo "##############################################################" exit ${EXIT\_STATUS} * **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 **Backward compatibility** 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 by adding the following lines to the script **EDITRAN** the following lines: \################# \#EDI\_GUPGRADE: Compatibility with user programs from previous versions EDI\_GUPGRADE=1 export EDI\_GUPGRADE #### Commands **gload52** * Description Processing command for the application files to be sent. The processing consists of transforming and packaging the application files into the *buffer file.* This command is invoked by the process **editrang** when the remote version of the profile is 5.2. * Syntax gload52 \ \ \ : Submission identity. #### gload\[41|50|51] * Description Processing command for application files when the remote version of the profile is 5.1 or lower. * Syntax gload\[41|50|51] \ \ \: Submission identity. #### gunload52 * Description Processing command for the received application files. The processing consists of unpacking and transforming the received application files into the *buffer file.* This command is invoked by the process **editrang** when the remote version of the profile is 5.2. * Syntax gunload52 \ \ \: Submission identity. #### gunload\[41|50|51] * Description Processing command for received application files when the remote version of the profile is 5.1 or lower. * Syntax gunload\[41|50|51] \ \ \: Submission identity. #### traduct * **Description** This command allows translating files from **ASCII-EBCDIC** and of **EBCDIC-ASCII**. If certain characters of the standard tables need to be changed, 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, write the character to be translated and then 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, it is desired that they be 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 facilitate the update, 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 values appropriate to the new tables. * **Example:** > Suppose an entity had the following ASCII reception table ***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 output line is interpreted as follows: the ASCII character 0xA4 that resulted, according to the old translation tables, from 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 from the new local table will be removed *table5A*. * **Syntax** > traduct. ASCII-EBCDIC translation utility. > > V2.0 R0 - Apr 30 2013 > > Copyright (C) 1991-2011 INDRA > > 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 : ASCII table printout. > > -t e : EBCDIC table printout (default). > > -c : Character. > > -d : Decimal. > > -o : Octal. > > -x : Hexadecimal (default). > > -v : Verification > > -m \[e|r]: Migration of local send/receive conversion table > > 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 of the EDITRAN/G manager **menug** interactive. It allows building procedures associated with sends and/or receives, with chaining of new sends or receives. * **Syntax** igacmd. EDItran/G command-mode requester. V2.0 R0 - Apr 30 2013 Copyright (C) 1991-2011 INDRA 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 \ : Submission identifier. -v : Verbose mode. -w : Wait for the request to finish. * **Example** > It is desired that at the end of the reception of a certain submission, a send be generated to the remote editran system whose submission is PRUEBA. > > For 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 send-start operation for presentation PRUEBA. * **Return codes** In general, the command return codes are those listed in the section [editrang error codes](#códigos-de-error-editrang) and 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. | | | | -- | ------------------------------------------------------- | | 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 to receive result | | | | #### menug * **Description** This command allows direct access to the editran/G manager menu. #### estcmd * **Description** This command is used to know the status of an editran/G presentation. * **Syntax** > estcmd. EDItran/G submission status display utility. > > V5.2.1 - Feb 6 2023 > > Copyright (C) Editran INDRA > > Usage: estcmd E|R \[submission] > > \ > > E|R : Send or receive. > > \[presentacion#] : Identifier of the presentation. * **Return codes:** Numeric value from 0 to 6 corresponding to the following states > NO ACTIVITY 0 > > LOAD/DOWNLOAD 1 > > LOADED 2 > > TRANSMITTING 3 > > TRANSMITTED 4 > > INTERRUPTED 6 #### igaperfi * **Description** This command is used for managing editran/G profiles in command mode. More detailed information about this utility can be found in the document **User Manual of the Profile Manager.** #### modiperfi * **Description** The purpose of the command ***modiperfi*** is to provide the user with a non-menu-driven 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 how to use it in **User Manual of the Profile Manager.** #### igacode * **Description** This command is used to display the description of an editran/G result code. * **Syntax** > Description of the EDItranG result codes. > > V51.0 R0 - Apr 19 2013 > > Copyright (C) 1991-2011 INDRA > > Usage : igacode \ > > Where: > > \ : result code. ### Data files #### CFG subfolder * **editrang.cfg** Editran/G configuration file. It stores the profiles of the presentations. 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 version 2.2. #### BIN subfolder * **editrang.msg** File where the messages shown to the Editran/G operator are stored. * **editrang.hlp** File where the help texts for the interactive command are stored **menug**. **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\_PREVIO, U\_POSTERIOR, U\_EXCEPCION** Scripts are provided in this folder that serve as examples for the integration programs developed by users as pre- and post-processes. Functionally, they only print log messages, which will remain in *editrang.out*. > NOTE: It is recommended that new user programs be left in this subfolder or in a specific one that contains only those files. * **PSTEMIGC, PSTRECGC** Scripts that automate the exchange of RSA keys. They are the user programs after sending and receiving the presentation used by Editran/GC for the exchange of RSA keys. #### LOG subfolder * **editrang.log** File created with the **makelog**. It cyclically stores the summary of 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 using the ***printlog*** command described in the Editran/P user manual *Editran/P*. * **editrang.out** File where all outputs produced by Editran/G and the procedures and commands launched by this process are logged. It is the file where the user will find the details of the errors produced during the load and download processes. > NOTE: Files with the "out" extension are plain text and may change from one version to another. Applications should not process this file to extract information from it, as they could stop working with product updates. Below, some cases are listed as examples. Registered information from a successful send \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* CONVERSION IN SEND MODE OF PRESENTATION \[TEST] DATE-TIME: \[02/02/2023 10:27:49] VERSION: \[52] \# C F A T D L.Reg Modification date Size Sent Loaded Name \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ 1 N B N N 04020 05022019 124708 000000547005 000000547005 000000547005 /home/editran/tmp/ED41GestionClavesWindows.pdf 2 N B N N 04020 04062012 171736 000000000501 000000000501 000000000501 /home/editran/tmp/VerificaXades.log RESULT: \[0] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Output of a send that fails because there are no pending files, and configured with the exception program delivered in the installation. \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* CONVERSION IN SEND MODE OF PRESENTATION \[TEST] DATE-TIME: \[02/02/2023 10:25:40] VERSION: \[52] RESULT: CFG\_NO\_FILES \[90] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \################################################################################ EXCEPTION USER SCRIPT: ./utils/U\_EXCEPCION. Thu 2 Feb 10:25:40 CET 2023 PRESENTATION : E-TEST (000000010-000000020-PRUEBA) RESULT : \[0090] EXIT CODE : 0 \################################################################################ **Editran/G output differentiated by Presentation** There is the possibility of having the above information separated into files by Presentation. To do this, it is enough for the user to uncomment the following lines of the script *EDITRAN* to set as environment variable *EDI\_MLOG* before starting the service. ![assets/image38.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-46ec98fe1c65b2f2a2f8991e6b096f8919ac78af%2Fimage38.png?alt=media) In this case, the files are left in the subdirectory ***log*** of the installation, and are named ***\.log***. Unlike what happens with the file *editrang.out,* these files can be moved or deleted without needing to stop Editran. You only need to ensure that this Presentation has no transmissions in progress. ### 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 in the form of messages. Next, those codes and messages are detailed, with a brief explanation or recommended action, as appropriate: | MESSAGE | EXPLANATION/RECOMMENDED ACTION | | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Send load request | A load request for a sending presentation has been made | | Send request | A presentation send request has been received. | | Send end request | The interruption of the current send of the presentation has been requested. | | Send initialization request | The cancellation of the current send of the presentation has been requested | | Send canceled | The request to initialize the presentation send has been processed correctly. | | Reception installation request | A request has been made to cancel the current presentation reception. | | Reception canceled | | | Receive download request | A download request for a reception presentation has been made. | | Receive request | A presentation receive request has been received. | | Receive end request | A request has been made to interrupt the current presentation reception. | | The presentation is initialized | A request has been made to initialize a send or receive and the presentation has no pending transmission. | | The presentation is being transmitted | A request has been made to send/receive a presentation that is already being transmitted. | | Presentation state incompatible with request (\) | An incompatible request has been made with the state of the presentation. For example: request to initialize a sending 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 send to editran (A1R) *\* | Editran/P is notified to start sending a transmission session for the presentation. | | Request send end to editran (EDP) *\* | editran/P is notified to interrupt a transmission session of the presentation. | | Sending interrupted | The request to end the presentation send has been processed correctly. | | Correct and completed send conversion | The process of loading the buffers to be sent has been completed successfully. | | Correct and completed receive converter | The download process of the received buffers has been completed successfully. | | Error in the send conversion process | The buffers to be sent cannot be loaded. Consult the editrang.out file for more details about the error. | | Error in receive conversion process | The received buffers cannot be downloaded. Consult the editrang.out file for more details about the error. | | Request reception to editran (A2R) *\* | editran/P is notified to start receiving a transmission session of the presentation. | | Request reception end to editran (EDR) *\* | editran/P is notified to interrupt the reception of a transmission session of the presentation. | | Reception interrupted | A request to end reception has been processed correctly. | | editran send request (A1P) *\* | editran/P notifies that a remote request has been received for the indicated transmission session to be sent. Buffer loading is ordered if they do not exist. | | editran receive request (A2P) *\* | editran/P notifies that a remote request has been received to start receiving through the indicated transmission session. | | editran session sent (A3P) *\* | editran/P notifies that sending of the buffer file for the indicated session has ended. Sending ends when the A3P messages from all transmission sessions of the presentation are received. | | editran session received (A4P) *\* | editran/P notifies that reception of the buffer file for the indicated session has ended. When all A4P messages from the presentation's transmission sessions are received, the buffer download process is performed, which ends reception. | | editran session interrupted (A7I) *\* | editran/P notifies that the indicated transmission session has been interrupted. | | End post send editran session (A3R) | Response to editran/P for message A3P. | | Subsequent end of reception session aditran (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 correctly. | | 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 correctly. | | Error in post user process | The user process indicated in profiles has finished with an error. Consult the cause in the editrang.out file. | | Launches exception user process | The user process indicated in profiles has been launched. | | Exception user process finished | The user process indicated in profiles has finished correctly. | | Error in exception 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 download confirmation | The send is TRANSMITTED but the result of the remote download is awaited in order to consider it finished. | | Confirmation request | The remote entity is asked to confirm the status of its reception. | | Reception confirmation result: *\* | Response received from the remote entity about the status of its reception. | | Canceled wait for remote download confirmation | The user has decided to initialize a send that was pending remote download confirmation. | | Transmission completed successfully \[*\*] | Informational message when a SEND or RECEIVE finishes. | | 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 user scripts and the value returned by the Editran/G API. 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. | *CODE* | *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 the application file to be sent. | | 65 | OPEN\_OUT | Error opening the 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 with no records loaded. | | 70 | ALLOC\_ERROR | System error: memory handling. | | 71 | SAVE\_REL | Error saving the list of transmitted files. | | 73 | WRITE\_OUT | Error writing the application file to be received. | | 74 | SEQUENCE\_CSB | Erroneous CSB file: sequence error. | | 75 | TOTAL\_FILES | Erroneous CSB file: error in total number of files. | | 76 | TYPE\_FILE | Unknown file format. | | 77 | LENGTH\_CSBREC | Erroneous 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 the number actually downloaded. | | 80 | TOTAL\_CSBRECS | Erroneous CSB file: error in 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 the number actually downloaded. | | 82 | SYNCS\_CSB | Mismatch in the number of synchronizations in CSB. | | 83 | CFG\_LENGTH | Application file with a record shorter than the one specified in the profile. Check the characteristics of the files to be sent. | | 84 | STS\_RECV | Error in the download process because not all buffer files of the presentation were received. | | 85 | OPEN\_CSB | Error opening/creating CSB file\| | | 86 | NO\_PERFILG\_LOCAL | No local editran/G profile exists. | | 87 | NO\_PERFILG | No Presentation profile exists. | | 90 | CFG\_NO\_FILES | None of the files specified in the profile as emission files exist or can be found. | | 91 | USER\_SCRIPT | Error executing user script. | | 93 | PROFILES | Presentation profile incompatible with load/unload process. | | 94 | CANCELED\_REQ | Transmission canceled. | | 95 | PROC\_ERROR | Internal error: task creation in upload/download. | | 96 | RUNTIME\_EXCEPT | System error: "runtime excepction". | | 97 | NO\_LICENSE | License problem for performing one of the required functions. | | 98 | CRYPT\_ERROR | Error in the cryptographic processing of data. | | 99 | HDRFILE | Internal error: invalid control headers. | | 200 | NO\_ACK | Remote download could not be confirmed. | | 201 | NO\_STATE | Request incompatible with the state of the transmission. | | 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 record number | | 130 | EXCEPT\_P | Editran/P: Release. | | 140 | EXCEPT\_P | Editran/P: Excess retries to send. | | 160 | EXCEPT\_P | Editran/P: Total mismatch. | | 170 | EXCEPT\_P | Editran/P: Excess sync retries. | | 190 | EXCEPT\_P | Editran/P: Excess retries at end of sending. | | 240 | EXCEPT\_P | Editran/P: Profiles. | | 250 | EXCEPT\_P | Editran/P: File not prepared. | | | | | #### Exception Codes In the previous list of error codes there are some that are due to problems with transmission sessions. In these cases, the following message 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 solved 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. Launch previous. | The remote entity does not have its Buffer File available. The remote editran will automatically start the process that prepares the Buffer File and will request 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 exists | The remote entity does not have its available Buffer File. The remote editran is not configured to automatically launch the process that prepares it, so this situation will not be resolved until the remote operator acts. | | 122 | Incorrect remote buffer. Previous in possible execution | The remote entity does not have its available Buffer File 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 File 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. Total number of records | The remote Buffer is in an incorrect state. The total number of records does not match. The receiver's total records must be initialized. | | 130 | Release | Interruption due to a connection release. | | 140 | Excess retries to send | The entity requesting the send does not receive a response from the remote side. This is usually due to a temporary communications problem but should be analyzed by the operator. | | 170 | Excess synchronization retries | The sending entity does not receive the remote confirmation of having received a data burst. This may be due to slow communications and could be resolved by decreasing the parameter ***No. of records per sending block*** in the transmission session profile. | | 190 | Excess retries at end of send | The sending entity does not receive confirmation from the remote of the end of send. This situation may require both entities to end up in different states and it may be necessary to initialize at one of the ends. | | 240 | Profiles | Transmission is interrupted because one of the profile parameters of the session 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 prepared | 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.2.1-en/linux/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.