> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/administracion-y-operacion/navigation-between-screens/main-menu/administrator/presentation-session.md). # Presentation session To specify the parameters that describe a Session profile, it is essential to have previously created the Local Environment record.
Enter the desired option and the local entity codes (if blank, the general local environment is used), the remote entity codes and the presentation application code, whose profiles must have been previously created. A series of screens are displayed with most of the fields filled in with the default values taken from the profiles of the local entity, the remote entity, and the presentation application. The Session identification parameters for ediItran must be specified (Local Code, Remote Code, and Application), along with the desired option (Add, Query, Delete, or Modify). The meaning of the fields is as follows: * LOCAL CODE: Identification number of the ediItran user entity (NIF). With this code, it will be recognized by all entities interconnected with ediItran. (If blank, the general local environment is used) * REMOTE CODE: Identification of the remote ediItran installation (for example, the entity's NIF number). * APPLICATION: ediItran application code for the Session. * If OPTION = R, the Sessions menu appears again.
The meaning of the fields is as follows: * LOCAL CODE: Identification number of the ediItran user entity (NIF). With this code, it will be recognized by all entities interconnected with ediItran. (If blank, the general local environment is used) * OF REMOTE CODE: Identification of the remote ediItran installation (for example, the entity's NIF number) that we want to copy. * APPLICATION: ediItran application code for the Session we want to copy. Once the above fields have been entered correctly, consecutive screens will appear with the parameters that define the Session. By pressing \ and \, you can move from one screen to another. The screens and the meaning of their fields are as follows:
* REMOTE NAME: Name of the Remote Installation. * REMOTE VER.: specifies the value of the editran version of the Remote Installation. * APP NAME: Name of the editran Application. * VALIDATE INCOMING ADDRESS (Y/N): Validate local-remote NRIs or the incoming call packet IP address. Allowed values: (L)ocal, (R)emote, both (X), or none (N). If PAD, only local values can be validated. If IP, only remote values can be validated. Recommendation: In situations where you want to homologate the remote end through NRI or want calls to arrive through a specific path, you can indicate it this way. In other situations, enter N. * ACCESS IDENTIFIER: Allows sessions to be established with remotes that support multiple local environments. * CONNECTION TYPE: Type of line used to connect to the Remote Installation. * (CONNECTION TYPE 1,2 indicates the order of connection preference.) * ‘I’: TCP/IP * ‘Y’: PROXY If the option you enter is 1
* SESSION ENABLED. (Y/N): can have 2 values. 'Y': can be called. 'N': cannot be called. * TRACE (Y/N): whether ediItran should record all messages exchanged in this Session. 'Y': all messages are recorded. 'N': this feature is not used for the Session. * CALLING END (L/R/X): can have three values. 'L': only the Local end can call. 'R': only the Remote end is allowed to call. 'X': either end may call. * VALIDATE INCOMING ADDRESS (Y/N): can have 2 values. 'Y' or 'N'. * ROTATE ADDRESS: can have two values. 'R': if more than one address has been entered, the last one used to establish the connection remains the stable address. 'N': addresses are rotated, but their order is not altered for the next connection. * TRAFFIC DIRECTION (S/R/X): can have 3 values. 'S': data can only be sent in this session. 'R': data can only be received in this session. 'X': data can be sent and received in this session. * AUTOMATIC CONNECTION (Y/N): can have 2 values. 'Y': the switched virtual circuit is established automatically when the start of transmission or reception is requested. 'N': a manual connection must be requested before transmission or reception is requested. * AUTOMATIC DISCONNECTION (Y/N): can have 2 values. 'Y': the switched virtual circuit is automatically cleared when the end of a transmission or reception is requested. 'N': a release request must be made to end the connection when a transmission or reception finishes, if the Remote side does not release it. * TIME-OUT (MSS): three digits in minutes and seconds indicating the maximum time to wait for a response from the Remote end (only for control or connection messages). If no response is received after this time, the request to the Remote end is repeated. It also applies to connection requests (although in this case, if the value is less than 100 -1 minute-, this is taken as the minimum value). * TIME-OUT-NSM (MSS): Three digits in minutes and seconds indicating the maximum time to wait for a response from the Remote end when sending a block of data messages. If no response to the data is received after this time, the request to the remote end is repeated until the number of retries is reached. Warning: the program that handles burst time-outs will impose a minimum time of 1 minute, so if a timer below this value is coded in this field, its value will be ignored during transmission. * MAX. NUMBER OF RETRIES: number of times the Time Out process is repeated, after which the operation (transmission, reception, connection) is abandoned. * START TIME and END TIME: time window for establishing a connection or starting a transmission or reception (from the Local or Remote side). When both fields are 0, it indicates that there is no time window, and the above operations can be performed whenever desired. * REC. LEN (2=4050): specifies the record length of the 4050 Send and Receive Buffer file. It must match the record length specified by the Remote end for this Session. It is mandatory if any Buffer file is used. * This length will be only 2=4050 for remote version = 5.2, 5.21 or 5.3 * CRYPTOGRAPHY (Y/N): can have 2 values. 'Y' when cryptography is used, 'N' when cryptography services are not used. Below, all the parameters involved in the cryptographic system are listed and described. Appendix C includes a table with the parameters, key types, or encryption errors. * CRYPTOGRAPHIC VERSION: can have the following values: * 300 When key exchange is performed outside editran. * 400 When key exchange is performed outside editran. New encryption. * EDITRAN-GC (Y/N): For automatic key exchange. * If CRYPTOGRAPHY = 'Y'
* DATA ENCRYPTION ALGORITHM: indicates whether data should be encrypted during transmission. It can have the following values: * 'Spaces': when data is not to be encrypted during upload/download. * 'TD3C': if you want to encrypt data with the Triple DES triple-key algorithm (192 bits) (for TD3C we need cryptographic version '300') * AES1 if you want to encrypt data during upload/download (Simple AES). Only allowed with remote editran/g version > 5.2. * AES2 if you want to encrypt data during upload/download (Double AES). Only allowed with remote editran/g version > 5.2. * AES3 if you want to encrypt data during upload/download (Triple AES). Only allowed with remote editran/g version > 5.2. * AUTHENTICATION ALGORITHM: indicates the algorithm used to encrypt the session key and the data exchanged to authenticate the ends. It can have the following values: * 'Spaces': when you do not want to authenticate the ends (option not valid if you want to encrypt data during transmission). * 'DES': when you want to authenticate the ends with the DES algorithm. * 'RSA': when you want to authenticate the ends with the algorithm (valid only for Cryptography version 3.00). * 'RSA2': if you want to authenticate the ends with the RSA algorithm * 'RSA4': when you want to authenticate the ends with the RSA algorithm (both options valid only for Cryptography version 400 and local and remote editran 5.2). * LOCAL KEY: only valid when CRYPTOGRAPHY VERSION IS '300'. The Label or tag of an auxiliary key must be specified. If the AUTHENTICATION ALGORITHM is 'DES', the Label of the 'EXPORTER' auxiliary key must be specified, and if the AUTHENTICATION ALGORITHM is 'RSA', the Label or tag of the local private key must be specified. * REMOTE KEY: only valid when CRYPTOGRAPHY VERSION IS '300'. The Label or tag of an auxiliary key must be specified. If the AUTHENTICATION ALGORITHM is 'DES', the Label of the 'IMPORTER' auxiliary key must be specified, and if the AUTHENTICATION ALGORITHM is 'RSA', the Label or tag of the remote public key must be specified. Local subsystem. Local active key exchanged with the remote entity Remote subsystem. Remote active key exchanged (received from the remote entity). **Note: Exchanges with key management of interchan**ge. An application has been created that allows automating the exchange of exchange or transport keys, whether DES or RSA (requires DES and RSA cryptography on both ends). With this system, key exchanges are secure (no one sees keys in clear text), reliable, and automated. In addition, it allows key changes without needing to change the editran profiles. For more information, see the manual **editran Key Manager User Manual.**
* editran/FF Verification is the way to "verify" that it is possible to proceed with loading into editran/FF. Its possible values are: * 'N' - Indicates that it operates without editran/FF * 'S' - Indicates that it operates with editran/FF and that, in order to load, the editran/FF Windows server must indicate whether or not the session is enabled; the requirements for having the necessary signatures for loading are met. * 'X' - Indicates that it operates with editran/XADES. File signing for the General Treasury of Social Security (TGSS) (see EDIFFuser manual) * **DELETE IF THEY EXIST (Y/N)**: with Y, existing application files whose name matches those that will be downloaded in a subsequent reception process will be deleted. If N is specified and such files exist, the process stops * **Physical name of the reception application file.** If entered, it must meet the following rules: * Library: 10 bytes * File: The possibility has been implemented, at the operator's discretion, for editran to generate reception files with names different from those it creates by default. Fields with % indicated in the study for the name of the reception file will be accepted:
Thus, if reception files are specified without %, a single file is generated with the same format as before. If a reception file is specified with the % variable, a file name is generated by resolving the % variable. * For example, FICH%P, in which case if the application is PRUEBA, a file called FICHPRUEBA would be generated. The download of **binary files** is carried out in the **IFS file system**, for this reason directory names must be preceded by the / symbol, indicating that this is a directory and not a library. If, in the same reception, files with different formats (fixed/binary) are received, it is mandatory for there to be the library where the fixed files will be downloaded and a directory with the same name as the library for the binary files. * **TRANSMISSION SESSIONS**: Up to 20 transmission applications may be defined. The operation is as follows: **An add** NUMBER: indicates the number of transmission applications to be added (01-20) APPLICATION: · If there is only one transmission application, by default it will match the presentation session application. This name can be changed to another 6-character alphanumeric name. If there is more than one application, we will use a 5-character alphanumeric template. For example TRANSMISSION SESSIONS - NUMBER: 05 APPLICATION TEMPLATE: PRUEB PRUEBA PRUEBB PRUEBC PRUEBD PRUEBE **A modification** NUMBER: indicates the number of transmission applications to be added (01-20) APPLICATION: · If there is only one transmission application, we can enter any name we want. · If there is more than one application, we can use the template as in the add case or not use it. If no template is used, we will leave the TEMPLATE field blank and fill in APPLICATION. The field must match the first field in the table For example TRANSMISSION SESSIONS - NUMBER: 02 TEMPLATE; APPLICATION: PRUEBA PRUEBA NOMINA Once the data on this screen has been validated, if Enter is pressed, the following screen will be displayed:
Name of the Buffer files. Send and Receive are each 4050 bytes long, respectively. And they are the ones to be used by the session.
* **Description**: Name of the presentation application. * **Load Type**: Offers the possibility of dynamic loading. * A: Cumulative loading of application files into the "buffers" carried out in successive load requests. * N: Only one load is allowed until the file is sent or initialized. * **Division criterion**: Only in native mode 5.3.1 and in compatible 5.0, 5.1, 5.2, 5.2.1, 5.3, and if several transmission sessions are to be used for the presentation session. The following values can be specified: * V: The application send 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 in it might not be used in the presentation. * S: Distribution by file or by batch marked by synchronization points, depending on the converter. Successive complete files or batches would be assigned to each send buffer. * N: No division is performed. * **Send conversion table**: Name of a table resident in the FGIGATCO file, which converts the characters to be sent from the application file into the characters indicated in that table (it does not change the data language, but adapts it to another table of the same language). If the application file language is EBCDIC, there will be a table in the FGIGATCO file called Send-conversion-table + E. If it is ASCII, it will be called Send-conversion-table + A. If two files are to be sent in different languages, both tables will be applied. * **Translate on reception (A/E/N**): Indicates whether we want to translate on reception and into which language. Translates to A (ASCII) or E (EBCDIC), as long as the language of the file data is compatible for translation, that is, the two possible combinations are: RECEIVED FILE DATA LANGUAGE 'A' and TRANSLATE ON RECEPTION 'E', RECEIVED FILE DATA LANGUAGE 'E' and TRANSLATE ON RECEPTION 'A'. Two files in reception with different languages cannot be translated. * **Reception conversion table:** Name of a table resident in the FGIGATCO file, which converts the characters received in the reception file into the characters indicated in that table (it does not change the data language, but adapts it to another table of the same language). If the language of the received application file is EBCDIC, there will be a table in the FGIGATCO file called Reception-conversion-table + E. If it is ASCII, it will be called Reception-conversion-table + A. If two files are received with different languages, both tables will be applied. * **Delete buffer file**: deleting a buffer should be understood as CLRPFM of a file. * **After transmission**: If Y, the send buffer(s) are deleted when the send presentation ends. * **After reception**: If Y, the receive buffer(s) are deleted when the reception presentation ends. * **Request download acknowledgment (Y/N**). This is to confirm whether a remote download is correct, so that the sender will not load if it does not know this data or if the timeout period has not elapsed. It is not possible to operate with sessions using specific buffers. Check them. Values * 'Y' - The end that indicates this value, in its transmissions, expects the remote side to confirm the remote download. * 'N'. Do not confirm downloads. * **Wait time (minutes)**.: 00-99 - Time the sender waits without being able to perform a new load if the remote side does not send the correct download result * **User programs**: Called by editran at the end of the pre/post send/receive and exception processes. * These programs will be provided by the user and will be called at the end of the presentation processes. * The communications area passed to them contains all the information used by IGA (IGA and editran profiles). * If you want to use a file, it must be included in the corresponding procedure. With Enter, the add will be performed. With PF3, you leave. The data values of a presentation application are passed to the presentation sessions of that entity, when they are created, as default values. Modifying the profile of a presentation application is done in the same way as adding it, but the profile must already exist. The modified values are transferred to the matching fields in the presentation sessions of the same entity. Query is the same as the previous functions. When deleting an application profile, a screen identical to the one described appears. With Enter, the deletion is confirmed and with PF3 it is cancelled. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/administracion-y-operacion/navigation-between-screens/main-menu/administrator/presentation-session.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.