> 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/sesion-presentacion.md). # Presentation session ## Main screen This screen is accessed with option 4 of the administrator menu, with 1.4 of the general menu, and by carrying out or cancelling the invoked function. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:35:17 SESSION 5.3 | ------------------------------------------------------------------------------ | | | | | | | A ADD | | B DELETE | | C QUERY | | M MODIFICATION | | R ADD WITH COPY | | | | | | | | OPTION : M | | LOCAL CODE : 0 0009998 0 | | REMOTE CODE : 0 0009994 0 | | APPLICATION : TEST | | | | | | | | | ------------------------------------------------------------------------------ ``` If add with copy is selected, the following screen appears: ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:36:17 SESSION 5.3 | ------------------------------------------------------------------------------ | | | | | | | A ADD | | B DELETE | | C QUERY | | M MODIFICATION | | R ADD WITH COPY | | | | | | | | OPTION : R | | LOCAL CODE : 0 0009998 0 | | REMOTE CODE : 0 0009994 0 | | APPLICATION : TEST | | IN LOCAL CODE : 0 0009998 0 | | IN REMOTE CODE : 0 0009994 0 | | IN APPLICATION : TEST2 | | | ------------------------------------------------------------------------------ ``` Enter the desired option and the codes for the local entity, remote entity and presentation application for a specific session, and generic for all of them, and a screen like this one will appear: ``` 21/06/26 11:41:33 SESSION MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ S PRESENTATION SESSION DESCRIPTION SEE CRI SEE.CRI APP.TRANS - -------------------------- -------------------- --- --- ------- --------- 000099980 000099940 TEST 9998 9994 PAKYSV SES 5.3 S 4.0 TEST 000099980 000099940 TEST2 S0U 5.0 S 3.0 TEST2 000099980 000099940 TEST3 S0U 5.0 N TEST3 000099980 000099940 PRGIGA CICS TCP 6 GB 5.0 N PRGIGA 000099980 000099940 PRPSD2 5.2 N 3.0 PRPSD2 000099980 000099940 PRTCP0 CRYPTO 30-TD3C-RSA 5.1 S 3.0 PRTCP0 000099980 000099940 PRTCP1 WITHOUT CRYPTOGRAPHY 5.3 N PRTCP1 000099980 000099940 PRTCP2 CICS TCP 5.0 N PRTCP2 000099980 000099940 PRTCP3 CICS TCP 5.2 N PRTCP3 000099980 000099940 PRTCP4 CRYPTO 30-TD3C-DES 5.0 S 3.0 PRTCP4 000099980 000099940 PRTCP5 CRYPTO 30-TD3C-RSA 5.3 S 3.0 PRTCP5 000099980 000099940 PRTCP6 CRYPTO 30-TD3C-RSA 5.2 S 3.0 PRTCP6 000099980 000099940 PRTCP7 CICS TEST WITH ACKNOWLEDGMENT 5.3 S 3.0 PRTCP7 000099980 000099940 PRTCP8 CICS TCP 5.1 S 3.0 PRTCP8 000099980 000099940 PRTCP9 CRYPTO 40-AES2-RSA 5.2 S 4.0 PRTCP9 000099980 000099940 PRTC10 CICS TCP 3 TRANSMI 5.0 N PRTC11 000099980 000099940 PRTC14 CRYPTO 40-AES1-RSA 5.2 S 4.0 PRTC14 ``` Select the corresponding session with an ‘S’. If add with copy has been selected, the data from the selected record are taken. The presentation session is created from the source presentation session data, except the data belonging to the remote one (if it is not the same) and the application (if it is not the same). A series of screens are received with most fields filled in with the default values taken from the profiles of the local entity, the remote entity and the presentation application. The following four screens will appear: ## Screen 1 To navigate between them, the following keys will be used: PF8 to advance, PF7 to go back, PF3 to abandon the option in progress - add, delete, query or modify - and ENTER to execute it, except in query, where it has no effect. The presentation session will appear protected on each of the screens. ``` 21/06/26 11:54:29 SESSION MODIFICATION (1) EDITRAN 5.3 ------------------------------------------------------------------------------ SESSION : 0 0009998 0 - 0 0009994 0 - TEST DESCRIPTION: BUFFER RECORDS NUMBER: 00010000 RECEPTION APPLICATION FILES DELETE IF THEY EXIST (Y/N) : S CATALOGING TYPE(V/U/P): P (VOLSER, WORK UNIT OR VOL POOL) RECEPTION VOLSER : DESARROL UNIT OF VOLSER: DL.FORM.FILE (F/V/E) : V DOWN.FILE LENGTH: 01024 (MOD.F) SINGLE RECEPTION FILE (Y/N): N PHYSICAL NAME OF RECEPTION APPLICATION FILE: TRANSMISSION SESSIONS - NUMBER : 01 APPLICATION : TEST UPDATES TRANSMISSION SESSIONS ``` * **DESCRIPTION**: Presentation session name. * **BUFFER RECORDS NUMBER**: This data will be used, during loading, in the creation of the normalized CSB file, as well as for other intermediate work files, and should be calculated approximately by dividing the number of bytes of the file to be sent by the transmission length specified in the transmission session profile (252 or 4050). This parameter will not be used if SET FILE CREATION SPACE (Y/N) = ‘S’. ### Reception application file * **DELETE IF THEY EXIST (Y/N)**: With S, the existing application files whose name matches those that are going to be downloaded in a process after reception will be deleted. If N is specified **and those files exist, the process is stopped.** * **CATALOGING TYPE(V/U/P)**: If it is V, the received files are created in the "volser" specified in the next line. If it is U, they are created in the generic unit defined in the local environment. If it is P, they are created in the storageclass of the next line. * **RECEPTION VOLSER**: In the case of cataloging type ‘V’, the name of the volume where you want to create the reception application file(s) must be specified. If it is ‘P’, the name of the storageclass containing the volume pool where you want to create the reception application file(s) must be specified. If the specified cataloging type is U, it should not be entered. * **VOLSER UNIT**: If the reception "volser" has been specified, in principle it is not necessary to specify the corresponding "Unit". However, when carrying out the dynamic allocation in some installations and disk types, incompatibilities have been detected between the specified "volser" and the default "Unit". In such a case, this data must be specified. * **DL.FILE.FORMAT (F/V/E)**: If binary files are received, this field indicates how the reception application files should be created: FIXED, VARIABLE or EXPANDED VARIABLE (F-V-E). * **DOWNLOAD FILE LENGTH**: This parameter only applies to the reception of binary files. The reception application files will be created with the indicated length or with the one sent by the remote side if it does not specify it or if the length is zero. The length must meet the criteria allowed in z/OS for file allocation: fixed: max. 32756, variable: max. 32752. * **SINGLE RECEPTION FILE (Y/N)**: Indicates whether the download is desired into a single reception file or into several. If ‘N’ is specified and there is no physical name for the reception application file, and several files are received, several reception files will be generated, with the product's standard names specified in the description of the next parameter. * **PHYSICAL NAME OF RECEPTION APPLICATION FILE**: Several possibilities are allowed. 1. If it is not coded, the file name is generated automatically in one of the following formats depending on the current file number: > * If the current file number is less than 100, the format is: Prefix.lll.Rxnnnnnn.Rnnx.Aaaaaaa.Rmmmmnn > * If the current file number is equal to or greater than 100, the format is: Prefix.lll.Rxnnnnnn.Rnnx.Aaaaaaa.Snnnnnn > > where: > > > * Prefix: File Installation Prefix (Editran General Local Environment) > > * lll: Alias (Editran General or Secondary Local Environment) > > * Rxnnnnnn: An R and the first 7 characters of the remote code. > > * Rnnx: An R and the last 3 characters of the remote code. > > * Aaaaaaa: An A and the name of the presentation application > > * Rmmmmnn: An R and 4 digits of the Exchange Session number and two digits of the application file sequence number. > > * Snnnnnn: An S and 6 digits of the application file sequence number > > * If a single file is used (Single file in reception = ‘S’), all received files are downloaded into a single file with sequence number 01 (Rmmmm01), adapting its format, length and blocking to the characteristics of the received files. > > * If there is no single file (Single file in reception = ‘N’), several files are generated, differentiated by the sequence number. > > > > > For example: > > > > > > The second file received from INDRA by the TELECA application without a single file in reception could be > > > > > > Editran.L00.R000099.R990.TELECA.R000102. > > > > > > The 1024 file received from INDRA by the TELECA application without a single file in reception could be > > > > > > Editran.L00.R000099.R990.TELECA.S001024. 2. If coded, we can use > * If the files are to be received in the MVS partition > > > > * A fixed name that complies with the syntax of an MVS DSNAME. > > > > > > > - With a single file, all received files are downloaded to the specified name, adapting its format, length and blocking to the characteristics of the received files. > > > > > > > > ⚠️ If no single file is specified, and more than one file is received, a download error will occur. > > > > > * A new version of a generational file could be specified by indicating “(+n)”, where n is from 1 to 255. > > > * A name containing "variables %". The application will generate different names for each reception file according to the variables supplied. The name will be made up of fixed parts that can alternate with variables. Variables are formed with the % sign followed by a letter. > > > > > > The table on the next page shows the allowed variables and their meaning: > > > > > > ``` > > > Variable Meaning > > > %O Source DSN > > > %E Decade > > > %Y Last digit of the year > > > %A Last two digits of the year (yy) > > > %M Month in two digits (mm) > > > %X Month in one character (1,2,3,4,5,6,7,8,9,O,N,D) > > > %D Day of the month (dd) > > > %H Time (hhmmss) > > > %N Presentation session number (nnnn) > > > %C Sequence number of the received file (nn) > > > %K Sequence number of the received file (nnnnnn) > > > %R The last 7 characters of the remote end code > > > %P Application code > > > ``` > > > > > > > For example, the name editran.F%A%M%D.E%R.F%C will generate the following name for the third file received from INDRA on 1-12-00: > > > > > > > > Editran.F001201.E0099990.F03. > > > > > > * If a single file is used, only one file is generated, resolving the % variables for the first received file. Its format, length and blocking would be adapted to the characteristics of the received files. > > > * If there is no single file, as many files as have been received are generated, provided that the expansion of the variables can generate them. If two duplicate file names are generated, the download will be interrupted, unless it is a generational group. If the %H variable, hour, appears in the name, and two files are downloaded in the same second, resulting in a duplicate name, Editran will try to break the tie in the hour by waiting one second. > > > > > > The file name could refer to a generational file (+n). If more than one file is received, different generations must be indicated for each file, or different generation groups; otherwise, all files would be overwritten on the same generation, preserving only the last file. In this sense, a good strategy would be to indicate “PREFIX(+%C)”, to assign a different generation to each file (PREFIX (+1), PREFIX (+2), etc.). > > * If the files are to be received in the USS partition, then a destination path must be entered with the following possibilities: > > > - A directory name. > > > > > Generates the name of the files to be downloaded with the following format: directory/RrrrrrrrAaaaaaaNnn or directory/RrrrrrrrAaaaaaaNnnnnnn, where: > > > > > > * rrrrrrr is the numeric part of the remote code > > > * aaaaaa is the application > > > * nn or nnnnnn is the sequence number of the file to be received > > > > * If a single file is used (Single file in reception = ‘S’), all received files are downloaded into a single file with sequence number 01. > > > > * If there is no single file (Single file in reception = ‘N’), several files are generated, differentiated by the sequence number. > > > > > For example, the second file received from INDRA by the TELECA application without a single file in reception in the directory */u/received* could be /u/received/R0009999ATELECAN02. > > > > > * A fixed name that uses only characters from the POSIX portable file *name character set* > > > > > > > With a single file, all received files are downloaded to the specified name, adapting its format, length and blocking to the characteristics of the received files. > > > > > > > > ⚠️If no single file is specified, and more than one file is received, a download error will occur. > > > > > > * A name containing an editran mask will generate different names for each reception file based on the supplied variables. The name will be made up of fixed parts that can alternate with variables. Variables are formed with the % sign followed by a letter. > > > > > > > The following table shows the allowed variables and their meaning (these are the ones used by editran in open environments). > > > > > > > > ``` > > > > Variable Meaning > > > > %o Original name > > > > %D Day > > > > %M Month > > > > %Y Year > > > > %h Hour > > > > %m Minutes > > > > %s Seconds > > > > %c Counter (nnnnnn) > > > > ``` > > > > > It should be taken into account that, in order to receive different files, the mask must allow different names to be generated for each file. * **TRANSMISSION SESSIONS**: Up to 20 transmission applications may be defined. The operation is as follows: ***Creation*** > **NUMBER**: indicates the number of transmission applications to be created (01-20) > > **APPLICATION**: > > · If there is only one transmission application, by default it will match the application of the presentation session. This name can be changed to another 6-character alphanumeric name. > > · If there is more than one application, we will enter a 5-character alphanumeric template and, by pressing PF5, we will be able to view the names of the transmission applications that will be created. These names will be formed by the template and the letters A- for the first, B- for the second, C- for the third, T- for the twentieth. > > For example > > TRANSMISSION SESSIONS - NUMBER : 05 APPLICATION TEMPLATE : PRUEB > > TEST TESTB TESTC TESTD TESTE **A modification** > **NUMBER**: indicates the number of transmission applications to be created (01-20) > > **APPLICATION**: > > · If there is only one transmission application, we can enter whatever name we want, just like in creation. > > · If there is more than one application, we can use the template as in the creation case or not use it. If the template is not used, we will leave the APPLICATION TEMPLATE field blank and fill in the transmission session name however we want. > > For example > > TRANSMISSION SESSIONS - NUMBER : 02 APPLICATION TEMPLATE : > > TEST PAYROLL ℹ️With PF5 the transmission applications are updated. Once the data on this screen have been validated, if PF8 is pressed, the next screen will be displayed: ## Screen 2 ``` 21/06/26 11:33:12 SESSION MODIFICATION (2) EDITRAN 5.3 ------------------------------------------------------------------------------ SESSION: 0 0009998 0 - 0 0009994 0 - TEST SESSION ENABLED (Y/N) : S TRACE (S/C/N) : C CALLING END (L/R/X) : X VALIDATE IP ADDRESS (Y/N) : N TRAFFIC DIRECTION (L/R/X): X ROTATE ADDRESSES (L/R/X/N) : X AUTOMATIC CONNECTION (Y/N) : S AUTOMATIC DISCONNECTION (Y/N): S SYNC. REG. NO. : 025 MSG LENGTH (0252-4050) : 4050 TIME OUT (MSS) : 015 AUTOMATIC SEND (Y/N) : S DATA TIME OUT (MSS) : 030 START TIME (HHMMSS) : 000000 MAX. NUMBER OF RETRIES : 2 END TIME(HHMMSS) : 000000 --- CRYPTOGRAPHY (Y/N): S --- CRYPTOGRAPHIC VERSION (N.N): 4.0 DATA ENCRYPTION ALGORITHM : AES3 AUTHENTICATION ALGORITHM : RSA SUBSYSTEMS-LOCAL: I REMOTE : C LOCAL KEY: REM. KEY: ``` * **SESSION ENABLED (Y/N)**: It can have two values. * 'N': the session is temporarily out of service and cannot transmit or establish connections. Incoming calls will be rejected as an unknown session. * 'S' or ‘ ‘(blank): the session can operate normally. * **TRACE**: Indicates whether the messages exchanged during transmission are to be recorded in the Trace database, * 'S': all messages are recorded. * 'C': start and control messages are recorded, discarding data messages (SFP AND SBP) * 'N': none are recorded. * **CALLING END**: 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 IP ADDRESS**: Can have 3 values. * 'S': the remote addresses of incoming connection requests will be validated. * 'N': no validation will be performed. * ' ' (blank): If no value is specified, the IP address is not validated. * **TRAFFIC DIRECTION**: can have 3 values. * 'L': data can only be sent in this session. * 'R': data can only be received. * 'X': sending and receiving are allowed. * **ROTATE ADDRESSES**: Rotates the connection addresses depending on the values it takes. * ‘L’: Rotates Local addresses. When the call request establishes the socket through a proxy and/or through a client/server that is not in the first position of the profiles, the proxy address-port and/or the client/server transaction name through which the connection was established are placed in that position, and the rest are rotated, without removing any of them, so that in a later connection attempt local backups are avoided. * ‘R’: Rotates Remote addresses. When the call request establishes the socket through a remote address that is not in the first position of the profiles, the address-port through which the connection was established is placed in that position, and the remote addresses are rotated, without removing any of them, so that in a later connection attempt remote backups are avoided. * ‘X‘: Rotates both addresses, therefore avoiding all backups, local and remote. * **AUTOMATIC CONNECTION**: Can have 2 values. * 'S': the connection is established automatically when the start of sending or receiving is requested. * 'N': a manual connection must be requested before the transmission request. ℹ️Locked field with default option 'S' * **AUTOMATIC DISCONNECTION**: Can have 2 values * 'S': the connection is released automatically when transmission ends, * 'N': the connection remains established when transmission ends and must be released manually. * **SYNC RECORDS NO.**: Three-digit number that indicates the size of the synchronization burst. Editran transmission is carried out by sending consecutive blocks of records from the buffer file, after which delivery confirmation is requested from the receiver. When the receiver confirms the block, the next block is resent until all records in the file are completed. The number of synchronization records indicates the number of buffer records that make up each block. This parameter may affect transmission speed and should be chosen appropriately. It must be consistent with the time-out interval (DATA TIME-OUT). * **MESSAGE LENGTH**: Specifies the length of the emission and reception buffer records. Since each data message contains a buffer record, it also indicates the message length. It can range from 252 to 4050. It must match the length specified by the Remote. In version 5.2 and above only 4050 will be used. The OS/400 platform does not support intermediate values. * **TIME-OUT**: It is the time interval, in minutes and seconds, to wait for a response to a request. If no response is received by the end of this time, the request is resent. This interval applies to the start and end transmission requests to the remote side, to connection, association and release requests, and to any other process that requires resend mechanisms. For network connection requests, twice the interval is applied and for the activity control mechanism (STI) 5 times the interval is applied. * **AUTOMATIC SEND (Y/N)**: Allows the retry of a transmission that was requested outside the time window. If a local send or receive request is made outside the time window, marked by Start Time and End Time, this parameter allows the request to be stored and retried once the start time is reached. The retry is not carried out if any of the following circumstances occur * the Operator or the Application request the end of sending/receiving, even if transmission is not taking place, * the Session Profile is modified, * the T/O module is not active. With Automatic Send set to ‘N’, local requests that arrive outside scheduled hours are rejected. Under no circumstances are remote connection requests stored or retried. * **DATA TIME-OUT**: Similar to TIME-OUT but applied only to the data send burst. If no value is specified, the contents of the ‘Time-out’ field are applied. * **MAX. NUMBER OF RETRIES**: It is the number of times a message that requires a response from the remote side or the network (sending, receiving, synchronization, connection) is resent. When no response is received, the request is repeated the number of times indicated by this parameter and with an interval marked by ‘Time-out’. If this number of resends is reached, the request is discarded due to ‘excess retries’. The parameters ‘Number of synchronization records’, ‘Time-out’ and ‘Maximum number of retries’ must be harmonized with each other on the sending side, taking into account the speeds of the local and remote lines and the transmission length. The timeout interval must be adjusted to the time it takes for the synchronization burst (Number of synchronization records x Message Length) to reach the remote side. An inadequate interval causes unnecessary message retransmission. If the interval is too small, retries could be exhausted and the transmission aborted. * **START TIME and END TIME**: Time window for establishing a connection or starting a transmission or reception. When both fields are 0, it indicates that there is no time window, and the above operations can be performed whenever desired. This value applies to local connection, transmission or reception requests and to remote connection requests. * **CRYPTOGRAPHY**: It can have two values: ‘N’ when cryptography is not desired (default value). ‘S’ when cryptography is used. Below, all the parameters involved in the cryptographic system are listed and described. (see Annex C section) * **CRYPTOGRAPHIC VERSION (N.N)**: Can have the following values: * 3.0: External key exchange that allows data encryption with triple DES algorithm, and end authentication with DES and RSA algorithms. * 4.0: External key exchange that allows data encryption with AES and triple DES algorithm, and end authentication with RSA algorithm. * **DATA ENCRYPTION ALGORITHM**: Indicates whether data is to be encrypted during load/download time (it will never be encrypted during transmission time) and whether Triple DES or AES encryption will be used. It may have the following values: * Spaces: When you do not want to encrypt data during load/download time. * TD3C: If you want to encrypt data with the Triple DES triple-key algorithm (192 bits). * AES1: If you want to encrypt data using the AES algorithm with a 128-bit key. * AES2: If you want to encrypt data using the AES algorithm with a 192-bit key. * AES3: If you want to encrypt data using the AES algorithm with a 256-bit key. This field will appear as-is (with the indicated data) in the presentation session, while in the transmission session it will be spaces\[1] * **AUTHENTICATION ALGORITHM**: Indicates the algorithm used to encrypt the session key, and the data exchanged to authenticate the ends. It may have the following values: * DES: If you want to authenticate the ends with the DES algorithm (option not valid for Cryptography 4.0). * RSA: If you want to authenticate the ends with the RSA algorithm. The length of the RSA key in cryptography version 3.0 will be 1024, and in 4.0 it may be 1024, 2048 or 4096. * **LOCAL/REMOTE SUBSYSTEMS**: These parameters only have an effect when CRYPTOGRAPHIC VERSION is ‘3.0’ or ‘4.0’ and the authentication algorithm is RSA. The local subsystem and the remote subsystem for exchange-key management must be provided (option 6 of the main menu). These parameters can be replaced by specifying the LOC. KEY and REM. KEY parameters detailed below; when both fields are specified, LOCAL/REMOTE SUBSYSTEM will be used to obtain the keys. * **LOC. KEY**: The label of an auxiliary key will be specified. If the AUTHENTICATION ALGORITHM is ‘DES’, the label of the auxiliary ‘EXPORTER’ key will be specified, and if the AUTHENTICATION ALGORITHM is ‘RSA’, the label of the local private key will be specified. * **REM. KEY**: The label of an auxiliary key will be specified. If the AUTHENTICATION ALGORITHM is ‘DES’, the label of the auxiliary ‘IMPORTER’ key will be specified, and if the AUTHENTICATION ALGORITHM is ‘RSA’, the label of the remote public key will be specified. ``` ℹ️(1) If the remote has EDITRAN/P and EDITRAN/G separately We put: DATA ENCRYPTION ALGORITHM : TD3C AUTHENTICATION ALGORITHM : DES The remote must set: In EDITRAN/P: CONFIDENTIALITY ALGORITHM : AUTHENTICATION ALGORITHM : DES In EDITRAN/G: CONFIDENTIALITY ALGORITHM : TD3C AUTHENTICATION ALGORITHM : DES ``` Once the data on this screen have been validated, if PF8 is pressed, the next screen will be displayed: ## Screen 3 ``` 21/06/26 11:37:32 SESSION MODIFICATION (3) EDITRAN 5.3 ------------------------------------------------------------------------------ SESSION: 0 0009998 0 - 0 0009994 0 - TEST ENVIRONMENT PARAMETERS. TCP/IP CLIENT SERVER: ZTCP ZTC1 USE PROXY (Y/N): S PROXY IP ADDRESS PORT 010.055.000.017 07778 editran.indra.es 07776 PROCESS: ZTBPJIG TRANSACTION: ZTBI ALIAS: L00 BEFORE SEND : ZTBGP1ID AUTH.: S BEFORE RECEIPT. : ZTBGP2ID AUTH.: S AFTER SEND: ZTBGP3ID AUT.: S AFTER REC.: ZTBGP4ID AUT.: S EXCEPTION PROC. : ZTBGP5ID STATE MODIF.: ZTBGP6ID FILE PREFIX: KI.EGDI SAVE IN SYSTEM LOG (Y/N): S WORK UNIT: SYSDA (SYSDA,VIO,..) ADJUST FILE CREATION SPACE (Y/N): S WORK VOL. OR POOL (V/P): P WORK VOLUME: DEVELOPMENT JCL FILES,S : //KICICSP JOB (SNCE,KIT,,99),99989994P,CLASS=A,MSGLEVEL=1, // MSGCLASS=H //* //* //* ``` * **TCP/IP CLIENT SERVER**: Name of the transaction or transactions that will manage the connections, both local and remote, and the data traffic, in both directions, of the sessions that connect via TCP/IP (ZTCP by default). The values entered here will be expanded to the sessions and may be customized to balance traffic. * **USE PROXY (Y/N)**: Indicates that outgoing TCP/IP connection requests will be carried out through the Proxy defined in the Session. Incoming calls will pass through the Proxy, or arrive directly, regardless of the value of this parameter. * **PROXY IP ADDRESS and PORT**: Address and listening port of the Editran/PX product used to filter IP connections between Editran and the extranet (item 6). * **PROCESS and TRANSACTION**: Name of the User Procedures before and after transmission. * **ALIAS**: Prefix for identifying files in the loading processes. It must comply with MVS rules for the name of a file. The processes before and after the transmission of the Editran interface use auxiliary files whose name begins with a general prefix for the entire installation, followed by this alias. The alias is associated with this local code. If other local codes are available, we can distinguish the files of each environment by assigning a different alias to each local code. * **BEFORE SEND**: name of the pre-send Procedure that is executed to send or to prepare the buffer, it can also be launched if requested * **BEFORE RECEIVE**: as in the previous case, but referring to reception. * **AFTER SEND**: name of the Procedure that is executed once transmission has ended and when a transmission interruption is requested. * **AFTER RECEIVE**: as in the previous case, but referring to reception. * **EXCEPTION PROC.**.: name of the Procedure that is executed when a transmission interruption occurs * **STATE MODIF.**: name of the Procedure that is executed when a state modification is requested (2.2 from the main menu) * **AUT.**: If it is S, it indicates that from the transmission module the procedure can be executed as a consequence of a transmission event. If it is N or ‘space’, it indicates that it will only be executed when requested from the presentation module. If there is no pre/post send/receive procedure, the AUT field must be set to N * **FILE PREFIX**: This has already been explained in the environment. * **WORK UNIT**: This has already been explained in the environment. * **WORK VOLUME OR POOL (V/P)**: This has already been explained in the environment. * **LOG TO SYSTEM LOG (Y/N)**: This has already been explained in the environment. * **ADJUST FILE CREATION SPACE (Y/N)**: This has already been explained in the environment. * **WORK VOLUME**: This has already been explained in the environment. * **JCL ENTRIES**: This has already been explained in the environment. Once the data on this screen have been validated, if PF8 is pressed, the next screen will be displayed: ## Screen 4 ``` 21/06/26 11:45:55 SESSION MODIFICATION (4) EDITRAN 5.3 ------------------------------------------------------------------------------ SESSION: 0 0009998 0 - 0 0009994 0 - TEST REMOTE PARAMETERS REMOTE VERSION (N.N) : 5.3 CORE TRANSACTION : ZTB1 SEND BUFFER : 262144 RECEIVE BUFFER : 262144 REMOTE IP ADDRESS (TCP/IP) PORT 172.022.242.193 07777 editran.indra.es 07777 APPLICATION PARAMETERS LOAD TYPE (N/A/Q) : N SPLIT CRITERION (V/S/N) : V LZW ADJUSTMENT PERCENT (0-99) : 00 SEND CONVERSION TABLE : TRANSLATE ON RECEPTION (A/E/N) : E RECEIVE CONVERSION TABLE : PARAMETER: *1*6*PRUEBA*7*80* DELETE BUFFER AFTER SEND : S DELETE BUFFER AFTER RECEPTION : S REQUEST DOWNLOAD ACK (Y/N) : N WAIT TIME (MINUTES) : 00 ``` ### Remote parameters These data have already been commented on in the remote entity profile. The data from that profile appear by default and can be modified for the presentation session being created ### Application parameters These data have already been commented on in the application profile. The data from that profile appear by default and can be modified for the presentation session being created. For presentation session consultation, the same procedure is followed as for creation, although the corresponding profile must already exist and all data are protected. For modification or deletion, if the state of the presentation session is different from "not loaded" in sending and "initialized" in reception, the following confirmation screen is displayed to continue with the modification or deletion process. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:50:14 SESSION MODIFICATION 5.3 | ------------------------------------------------------------------------------ | | | **************************************************************************** | | * * | | * PRESENTATION SESSION : 0 0009998 0 - 0 0009994 0 - TEST * | | * * | | * THE STATE OF THIS PRESENTATION SESSION IS * | | * DIFFERENT FROM INITIALIZED * | | * * | | * SEND STATE RECEIVE STATE * | | * --------------------- ----------------------- * | | * 001 SENDING 104 FINISHED * | | * * | | * THE MODIFICATION MAY AFFECT THE INTEGRITY OF THE STATES * | | * * | | * CONTINUE (Y/N) : N * | | * * | | **************************************************************************** | | | | | ------------------------------------------------------------------------------ ``` If approval is given to continue, the screens that have already been seen for the other update functions are displayed and you can navigate through them using the general criterion. With ENTER, the deletion or modification will be performed and with PF3 it will be abandoned. In the case of deletion, the presentation session and all transmission sessions associated with this presentation will be deleted. If it is a modification, the field TRANSMISSION SESSIONS - NUMBER nor the field APPLICATION cannot be changed; these two fields are locked. ⚠️The REMOTE IP ADDRESS (TCP/IP) and the TCP/IP CLIENT SERVER in the transmissions will not be modified if they have not been modified on the corresponding screen. --- # 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/sesion-presentacion.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.