> 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-cics-en/operacion/onesait-editran-administrator/session.md). # Session To specify the parameters that describe the profile of a Session, it is essential to have previously created the General Local Environment record. When creating a record or creating it with copy, the program automatically looks up the connectivity and buffer data for a “compatible” session (with the same remote as the one you want to create). Creating local lines is not allowed (this process must be done beforehand). Creating IP lines is not allowed (only one is allowed if no other session exists with that remote). When modifying a session, creating local or remote lines is not allowed. All processes for creating local or remote lines must be completed before creating the session (opt. 1.9). Once the above fields have been entered correctly, consecutive screens will appear with the parameters that define the Session. By pressing the \ and \ keys, you can move from one screen to another. The screen that allows you to manage sessions is shown: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:12:24 SESSIONS | ----------------------------------------------------------------------------- | LOCAL CODE..: 0 0009994 0 REMOTE CODE.: * ******* * APPLICATION.: ****** | | S PRESENTATION SESSION DESCRIPTION VER CRI V.CRI APL.TRANS | | - -------------------------- -------------------- --- --- ----- --------- | | 000099940 A00099940 EDTRF2 SES:A00099940-EDTRF2 5.3 N 3.0 EDTRF2 | | 000099940 A00099940 EDTRF3 SES:A00099940-EDTRF3 5.3 N 3.0 EDTRF3 | | 000099940 A00099940 EDTRF4 SES:A00099940-EDTRF4 5.3 N 3.0 EDTRF4 | | 000099940 A00099940 EDTRF5 SES:A00099940-EDTRF5 5.3 N 3.0 EDTRF5 | | 000099940 A00099940 ESTEFF TEST ESTER IBERPAY 5.3 N 3.0 ESTEFF | | 000099940 A00099940 NORMA1 SES:A00099940-NORMA1 5.3 N 3.0 NORMA1 | | 000099940 A00099940 NORMA2 SES:A00099940-NORMA2 5.3 N 3.0 NORMA2 | | 000099940 A00099940 NORMA3 SES:A00099940-NORMA3 5.3 N 3.0 NORMA3 | | 000099940 A00099940 NORMA4 SES:A00099940-NORMA4 5.3 N 3.0 NORMA4 | | 000099940 A00099940 NORMA5 SES:A00099940-NORMA5 5.3 N 3.0 NORMA5 | | 000099940 A00099940 NORM20 ODEM-T1786 5.3 N 3.0 NORM20 | | 000099940 A00099940 NORM21 ODEM-T1787 5.3 N 3.0 NORM21 | | 000099940 A00099940 NORM22 ODEM-T1788 5.3 N 3.0 NORM22 | | | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` If the create-with-copy option is selected, a template session can be selected, either generically or specifically. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:13:01 SESSION | ----------------------------------------------------------------------------- | | | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | R ---> CREATE WITH COPY | | | | | | OPTION.......: R FROM SESSION | | LOCAL CODE..: 0 0009994 0 0 0009994 0 | | REMOTE CODE..: 0 0009998 0 0 0009998 0 | | APPLICATION..: APPLIES | | | | | ----------------------------------------------------------------------------- ``` If you want to consult, create with copy, delete, or modify without specifying a code: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:13:21 SESSIONS | ----------------------------------------------------------------------------- | LOCAL CODE..: 0 0009994 0 REMOTE CODE.: 0 0009998 0 APPLICATION.: ****** | | S PRESENTATION SESSION DESCRIPTION VER CRI V.CRI APL.TRANS | | - -------------------------- -------------------- --- --- ----- --------- | | 000099940 000099980 ABEURC SES:000099980-ABEURC 5.2 S 4.0 ABEURC | | 000099940 000099980 ABEURP S 5.3 S 4.0 ABEURP | | 000099940 000099980 ABEUR3 S 5.2 N 4.0 ABEUR3 | | 000099940 000099980 AESRSA SES:000099980-AESRSA 5.2 N 4.0 AESRSA | | 000099940 000099980 AE9994 ISSUANCE OF DEBTS 5.0 S 3.0 AE9994 | | 000099940 000099980 AE9998 RECEIPT OF DEBTS 5.2 S 4.0 AE9998 | | 000099940 000099980 AR9994 FORWARDING ISSU. DEBTS 5.0 S 3.0 AR9994 | | 000099940 000099980 AR9998 FORWARDING RECEIPT DEBTS 5.2 S 4.0 AR9998 | | 000099940 000099980 AUTOPR S 5.2 N 3.0 AUTOPR | | 000099940 000099980 A00000 KI.EGDI.Y%Y%X%D.H%H 5.0 N 2.2 A00000 | | 000099940 000099980 CE9994 ISSU. BILATERAL CHEQUES 5.0 S 3.0 CE9994 | | 000099940 000099980 CE9998 RECEIPT BILATERAL CHEQUES 5.2 S 4.0 CE9998 | | 000099940 000099980 CONFIR SES:000099980-CONFIR 5.0 N 3.0 CONFI1 | | | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` Once the presentation session is selected, it consists of 5 screens. If create with copy has been selected, the data from the selected record is used. The presentation session is created from the data in the source presentation session; the application must exist in editran. In the source presentation session, the contents of the remote center and application record may have values different from the same fields in the presentation session record, so the same thing may happen in the session to be created, even if the remote center or application record does not exist and must be created. A series of screens is 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. ## First session screen ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:13:44 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | DESCRIPTION..................: SES:000099980-ABEURC | | BUFFER RECORD NUMBER.......: 00010000 | | BUFFER FILE VOL-POOL (V/P): V ISSUE VOL.: DES805 RECEIPT VOL.: DES801 | | RECEIPT APPLICATION FILES | | DELETE IF THEY EXIST (Y/N)...: S | | CATALOGING TYPE (V/U/P)..: P (V)OLSER,(U)NIT WORK,(P)OOL | | RECEIPT VOLSER..........: DESARROL VOLSER UNIT.....: | | FILE FORMAT+LREC DOWNLOAD FILE(F/V/E): F 01024 BINARY ONLY | | SINGLE RECEIPT FILE (Y/N).: S | | PHYSICAL NAME OF RECEIPT APPLICATION FILE | | ------------------------------------------ | | | | TRANSMISSION SESSIONS - NUMBER.: 01 APPLICATION TEMPLATE: ABEURC | | | | ABEURC | | | | | | EXIT, FORWARD | ----------------------------------------------------------------------------- ``` * **DESCRIPTION**: Name of the presentation session. * **BUFFER RECORD NUMBER** for DEFINE CLUSTER of the buffer file (CICS environment only) and for the normalized CSB file. This data is important and must be calculated approximately by dividing the number of bytes in the file to be sent by the transmission length specified in the session profile (252 or 4050) * **BUFFER FILE VOL-POOL (V/P)**: Specify whether volumes or storage class (volume pool) is used in the buffer files (VOLSER-STORAGECL). This is a common parameter for both sending and receiving. * **ISSUE VOL.:** Volser or storage class for DEFINE CLUSTER of the issue buffer. When creating a session, the default is taken from the environment record. * **RECEIPT VOL.:** Volser or storage class for DEFINE CLUSTER of the receipt buffer. When creating a session, the default is taken from the environment record. **RECEIPT APPLICATION FILES:** * **DELETE IF THEY EXIST (Y/N)**. Specify whether the receipt application files should be deleted. If Y, they are deleted and created during the download. If N and they are found, the process stops. * **CATALOGING TYPE (V/U/P)**. If V, they are created in the "volser" specified on the next line. If U, they are created in the generic unit defined in the local environment. If P, they are created in the storage class on the next line. * **RECEIPT VOLSER**. If UNIT-OR-VOLSER = 'V', specify the name of the volume where you want to create the receipt application file(s). If UNIT-OR-VOLSER = 'P', specify the name of the storage class containing the volume pool where you want to create the receipt application file(s). Only necessary if 'V' or 'P' is specified in Cataloging Type. * **VOLSER UNIT**. If the receipt volser has been specified, in principle it is not necessary to specify the corresponding Unit. However, when performing dynamic allocation in some installations and disk types, incompatibilities have been detected between the specified volser and the default Unit. In that case, it must be specified. * **FILE FORMAT+LREC DOWNLOAD FILE (F/V/E)**. If x03-type files are received - MODIFIED (BINARY), this field indicates how you want the receipt application files to be created (FIXED, VARIABLE, or EXTENDED VARIABLE) (F-V-E). In addition, you can specify the length of that file (Maximum 32752 for VB and 32756 for FB). If you enter zeros, it is created with the length loaded by the remote system. * **SINGLE RECEIPT FILE (Y/N)**. Indicates whether you want the download into a single receipt file or into several. If 'N' is specified and there is no physical name of receipt application file, and several files are received, several receipt files will be generated, with the standard names as before. * **PHYSICAL NAME OF RECEIPT APPLICATION FILE**: It will show the first file that is registered in option 1.5, file administration, from which any modification on the files to be sent, as well as the sending characteristics, must be made. > Physical name of receipt application file. Several possibilities are allowed: > > 1. If it is not coded, the file name is generated automatically with the following format: > > > Prefix.lll.Rxnnnnnn.Rnnx.Aaaaaaa.Rmmmmnn > > > > where: > > > > Prefix: File installation prefix (editran/G General Local Environment) > > > > * lll: Alias (editran/P 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 order number. > > > > * If a single file is used (Single receipt file = 'S'), all received files are downloaded into a single file with order number 01 (.Rmmmm01), adapting its format, length, and blocking to the characteristics of the received files. > > > > * If there is no single file (Single receipt file = 'N'), several files differentiated by order number are generated. > > > > > For example, the second file received from INDRA by the TELECA application without a single receipt file could be editran.L00.R000099.R990.TELECA.R000102. > > 2. If the file name is coded: > > If you want to receive the files in the USS partition, you must enter a destination path with the following possibilities: > > > * A directory name. > > > > * Generates the names 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 order number of the file to be received > > > > * If a single file is used (Single receipt file = 'S'), all received files are downloaded into a single file with order number 01. > > > > * If there is no single file (Single receipt file = 'N'), several files differentiated by order number are generated. > > > > > For example, the second file received from INDRA by the TELECA application without a single receipt file in the directory */u/recibidos* could be /u/recibidos/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 under the specified name, adapting their format, length, and blocking to the characteristics of the received files. > > > > > > ⚠️If no single file is specified, and more than one file is received, an error will occur during the download. > > > > * A name containing an editran mask will generate different names for each receipt file based on the supplied variables. The name will consist of fixed parts that can be alternated 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) > > > ``` > > > > > > Keep in mind that, to receive different files, the mask must allow the generation of different names for each file. > > If you want to receive the files in the MVS partition > > > * A fixed name that complies with MVS DSNAME syntax. > > > > > - With a single file, all received files are downloaded under the specified name, adapting their format, length, and blocking to the characteristics of the received files. > > > > > > ⚠️ If no single file is specified, and more than one file is received, an error will occur during the download. > > > * We could specify a new version of a generational file by indicating "(+n)", where n is from 1 to 255. > > * A name containing "% variables". Editran will generate different names for each receipt file based on the supplied variables. The name will consist of fixed parts that can be alternated with variables. Variables are formed with the % sign followed by a letter. The allowed variables are as follows: > > > > ``` > > 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 Order number of the received file (nn) > > %K Order number of the received file (nnnnnn) > > %R The last 7 characters of the remote endpoint 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 with % 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 are generated as have been received, provided 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 resolve the conflict 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 overwrite the same generation and only the last file would be kept. 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.). * **TRANSMISSION SESSIONS**: Up to 20 transmission applications can be defined. > The operation is as follows: > > * Create > > > NUMBER: indicates the number of transmission applications to be created (01-20) > > > > APPLICATION: > > > > * If there is only one transmission application, it will by default 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 the names of the transmission applications to be created, 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 > > PRUEBA PRUEBB PRUEBC PRUEBD PRUEBE > > ``` > > * 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 when creating it. > > * If there is more than one application, we can use the template as in the create case, or we can choose not to use it. If we do not use a template, we will leave the APPLICATION TEMPLATE field blank and fill in the transmission session names however we want. For example: > > > > ``` > > TRANSMISSION SESSIONS - NUMBER: 02 APPLICATION TEMPLATE : > > PRUEBA NOMINA > > ``` ## Second session screen: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:16:04 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | LOCAL ENVIRONMENT PARAMETERS | | FILE INSTALLATION PREFIX........: KI.EIDC | | WORK UNIT NAME (SYSDA,VIO,..).....: SYSDA | | WRITE TO SYSTEM LOG (Y/N)........: N SPECIAL ADJ. CREATE FILE (Y/N): N | | VOLUME OR WORK POOL (V/P)........: V VOLUME NAME: DES805 | | | | NAMES OF THE EDITRAN PROCEDURES | | PREV.SEND P-G..: ZTBGP1CD ZTBGP1CD PREV.RECV. P-G: ZTBGP2CD ZTBGP2CD | | POST.SEND P-G..: ZTBGP3CD ZTBGP3CD POST.RECV. P-G: ZTBGP4CD ZTBGP4CD | | EXCEPT. PROC. P: ZTBGP5CD EXIT P MOD.EST.: ZTBGP6CD | | | | SHEET 01==> //KIIMSAB JOB (SNCE,KIT,,99),99949998ABEURP,CLASS=D, | | SHEET 02==> // MSGLEVEL=1,MSGCLASS=H | | SHEET 03==> //*EXPORT SYMLIST=* | | SHEET 04==> //* | | SHEET 05==> //* | | | | EXIT, BACK, FORWARD | ----------------------------------------------------------------------------- ``` **LOCAL ENVIRONMENT PARAMETERS**: * **FILE INSTALLATION PREFIX**: Maximum 11 bytes. Used for defining intermediate files and optionally application receive files. It must comply with MVS rules regarding the length of segments separated by periods. * **WORK UNIT NAME**: Generic storage unit for defining intermediate and work files. The space used by editran/G for these files is comparable to that for sending or receiving, and is released after the sending or receiving loads of the presentation. * **SAVE TO SYSTEM LOG**: If S, the messages generated by editran/G are sent to the system log. If N, they are written to ZTBGFPRI whose DD is found in the editran/G procedures. * **ADJUST FILE CREATION SPACE (Y/N)**. If S is coded, it means that application files will be read to obtain their size and thus calculate the space that must be applied to the sender buffer, csbnedi, to each of the compressed send files and to each ZTBGF54 send file. If N is coded, it means that the old system will continue to be used, that is, the ESP.PRIM. (REGS) field of the presentation session profile will be used. * **VOLUME OR WORK POOL**: Specify the (V)olume or (P)ool of the intermediate files and buffers so that they are taken by default when the presentation session is created. * **WORK VOLUME NAME**: Specify the name of the volume or pool of the intermediate files and buffers so that they are taken by default when the presentation session is created. * **NAMES OF THE EDITRAN PROCEDURES**: The fields detailed below will be filled in if User Procedures or Application Interface are used, which will be executed automatically by editran when certain events occur. > * **PREVIOUS SEND P-G**: name of the Procedure that runs before sending starts. It is essential to have specified the Issue Buffer File. Recommendation: If you want the remote system to be able to request receipt, specify a procedure in P. Otherwise, do not. > * **PREVIOUS RECEIPT P-G**: as in the previous case, but referring to the receipt process. Recommendation: If you want the remote system to be able to request sending, specify a procedure in P. Otherwise, do not. > * **POST-SEND P-G**: name of the Procedure that runs once sending has finished. It is essential to have specified the Issue Buffer File. Recommendation: Specify a procedure. > * **POST-RECEIPT P-G**: as in the previous case, but referring to the receipt process. Recommendation: Specify a procedure. In this case, it may be useful for that procedure to have a second step matching a previous receipt step so that the buffer is left ready to receive again (except when you want to control remote sends). > * **EXCEPTION PROC.** (P only): name of the Procedure that runs when a Send or Receive is interrupted. For more information about this procedure, see Appendix B. Recommendation: Specify a procedure > * **EXIT P MOD.EST**: EXIT P procedure. > * **JCL SHEETS**: for each Session, you can specify up to the first five sheets of the JCL under which the previously defined Procedures are executed. ## Third session screen: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:16:35 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | REMOTE VER.(N.N): 5.2 | | TRANSMISSION LENGTH: 4050 SESSION ENABLED: S VAL.IND-LLA(LRXN).: N | | CALL TYPE(L/R/X): X TRAFFIC(E/R/X)...: X ROUTE DIR.(L/R/X/N): X | | AUTO CALL (Y/N): S AUTO SEND (Y/N).: S OPERATOR TERMID: | | ALLOWED CONNECTION TYPE(I-IP,Y-PROXY,*-BOTH): Y | | TIME-OUT(MSS)...: 015 BURST TIME-OUT..: 030 RETRIES......: 002 | | | | ISSUE BUFFER+(E/M/P/C/D): ZTBPFEL C KI.EGDC.ZTBP.ZTBPFEL | | RECEIPT BUFFER+(E/M/C/D)..: ZTBPFRL C KI.EGDC.ZTBP.ZTBPFRL | | | | CRYPTOGRAPHY (Y/N).......: S | | CRYPTOGRAPHIC VERSION(N.N).: 4.0 | | DATA ENCRYPTION ALGORITHM.: TD3C AUTHENTICATION ALGORITHM ...: RSA | | LOCAL SUBSYSTEM...........: 4 REMOTE SUBSYSTEM..........: 4 | | LOCAL KEY: | | REMOTE KEY: | | | | EXIT, BACK, FORWARD | ----------------------------------------------------------------------------- ``` * **LOCAL CODE**: User Entity Identification Number for editran. With this number it will be recognized by the remote system connected through this session. It is your editran license code and the code by which the remote systems will see you. * **REMOTE CODE**: Identification Number of the remote Entity. It is the code provided by the remote system so that it can connect. * **APPLICATION**: Session application. * **REMOTE VERSION**: Specifies the editran version value of the Remote Installation or the version in which both editrans are used. Only values 5.0, 5.1, 5.2 and 5.3 are allowed. Recommendation: Take advantage of conversations with the representative of the remote entity to find out which editran version it has in production, so that both ends are updated to the lower of the two, which does not have to be the lowest allowed one. * **TRANSMISSION LENGTH**: Specifies the record length of the Send and Receive Buffer file; it will be 4050 (excluding the Session identification). It must match the record length specified by the remote for this Session. Recommendation: 4050. * **SESSION ENABLED (Y/N)**. In case N is indicated, the session remains disabled, so if calls are made or received, they are rejected. * **VALIDATE CALL IND. (L/R/X/N)**: Validate the IP address of the incoming call packet. Allowed values are (L)ocal, (R)emote, (X) both or (N)one. If IP, only the remotes can be validated. * **CALL ORIG. (L/R/X)**: can have three values. 'L': the only one that can call is the Local side. 'R': only the Remote side is allowed to call. 'X': either side can call. Recommendation: Set this field to X, except when you specifically want to be the only one who can call or when you want the remote side to be the only one. * **TRAFFIC (E/R/X):** can have 3 values. 'E': data can only be sent in this session. 'R': data can only be received in this session. 'X': sending and receiving data is allowed for this session. Recommendation: Set X, sessions with traffic in both directions. * **ROTATE DIR. (L/R/X/N)**: Rotate connection addresses. This is used to place first the IPs that manage to connect. It can have the following values: * L Rotate Local addresses. In the event of a call request, when the circuit is eventually established, if the local address in the profile first position does not match, the characteristics of the line that achieved session establishment are placed in that position, and the local lines are rotated, without removing any of them, so that in a later connection retry the local backups are avoided. * R Rotate Remote addresses. In the event of a call request, when the circuit is eventually established, if the remote address in the profile first position does not match, the characteristics of the line that achieved session establishment are placed in that position, rotating the remote lines, without removing any of them, so that in a later connection retry the remote backups are avoided. * X Rotate both Local and Remote addresses. In this case, if for example we connect through the third local nri with the third remote nri, both are placed first, which makes it very likely that the entire backup will be avoided in the next connection. Recommended value. * N The local and remote addresses remain unrotated. * **AUTO CALL. (Y/N):** It can only have value 'Y' (non-editable field): the switched virtual circuit is established automatically when the start of transmission or reception is requested. * **AUTO DISCONN. (Y/N):** can have the following values: * Y The session is released automatically when transmission/reception of the data ends. (recommended value). * N The session remains established after transmission/reception of the data ends. * **OPERATOR TERMID:** Name of the CICS Terminal assigned to the Session to display the informational messages corresponding to it. It is an optional field; if not specified, informational messages are not notified on screen. Recommendation: Leave this field blank. * **ALLOWED CONNECTION TYPE**: Type of line used to connect to the Remote Installation or for them to call us from it. Some sessions with one connection type and others with another can coexist, operating in parallel. A session can have several BACKUP connection types, equal or different. * 'Y': TCP/IP gateway to TCP/IP and vice versa (editran/PROXY) * 'I': TCP/IP. * **TIME-OUT (MSS)**: Three digits in minutes and seconds indicating the maximum time to wait for a response from the Remote side (only for control or connection messages). If the response is not received by the end of this time, the request is repeated to the remote. It also applies to connection requests. Recommendation: include a short time-out in this field, for example 30 seconds, since it does not represent data traffic, only control messages. * **SEND BURST TIME-OUT (MSS)**: Three digits in minutes and seconds indicating the maximum time to wait for a response from the Remote side when sending a block of data messages. If the data response is not received by the end of this time, the request is repeated to the remote until the number of retries is reached. Attention: the program that handles burst time-outs will impose a minimum time of 1 minute, so if a shorter timer is coded in this field, its value is ignored during transmission. > ⚠️ Recommendation: This time-out must be proportional to the speed of the local line, the remote line, the simultaneous local and remote connections, the transmission length and the burst itself (sync record count). For example, on a 9600 bps local line and 64 K (65536 bps) remote line (the lower of both values would be taken, 9600 bps), with 1 connection on the local side and 8 simultaneous on the remote side ((64 \* 1024) / 8 = 8192 bps) (in this case, we ignore 9600 bps and stick to the minimum, 8192 bps), with transmission length 4050 (approximately, with headers 4100 bytes \* 8 bits = 32800 bits per message), with sync record count 50, the result would be that the 50 messages would not be sent until 200 seconds ((50 \* 32800) / 8192), so in this session the send burst time-out should not be less than 330 (3 minutes, 20 seconds). * **MAX. RETRIES**: It is the number of times the Time-Out process is repeated, after which the operation is abandoned. Recommendation: Having many retries will not make sending/receiving happen. It is intended so that if the time-out or burst time-out come into play (they were not calculated well or the line is slow), the time-out message is relayed again. Ideally, the maximum number of retries should be 1 or 2. * **SENDING BUFFER FILE:** Logical name of the sending buffer file within CICS. * **SEND BUFF.+(E/M/P/C/D)**: It has five possible values related to the send buffer file ([Definition and Management of Buffer Files](/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files.md)): * 'E' specific file. Not allowed with multiple transmissions. * 'M' matrix file. * 'P' public file. * 'C' EXCI matrix file. (Recommended value for many transmissions) * 'D' unattended matrix file. * **RECEIVING BUFFER FILE:** Logical name of the receiving buffer file within CICS. * **RECV.BUFF.+(E/M/C/D)**: It has four possible values related to the receiving buffer file ([Definition and Management of Buffer Files](/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files.md)): * 'E' specific file. Not allowed with multiple transmissions. * 'M' matrix file. * 'C' EXCI matrix file. (Recommended value for many transmissions) * 'D' unattended matrix file. * **SENDING BUFFER and RECEIVING BUFFER**: output fields that indicate the Physical Name of the Buffer files * **CRYPTOGRAPHY (Y/N)**: It can have two values: 'N' when you do not want to use Cryptography (default value). 'Y' when Cryptography is used. Below, all the parameters involved in the Cryptographic system are listed and described. Review the [Annex D. Cryptography system in Onesait · Editran, Cryptography System](/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran.md) to understand first of all the possibilities of editran cryptography. Recommendation: Use cryptography, trying to encrypt data in batch and online authentication. * **CRYPTOGRAPHIC VERSION**: It can have the following values: * 3.00 When key exchange is performed outside editran. * 4.00 Cryptography is expanded with large RSA keys and AES. * **DATA ENCRYPTION ALGORITHM**: Indicates whether data are to be encrypted. It can have the following values: * 'Spaces' When data are not to be encrypted. * TD3C If data are to be encrypted (triple DES triple-key 192-bit key). * AES1 If data are to be encrypted (Simple AES with 128-bit key). * AES2 If data are to be encrypted (Double AES with 192-bit key). * AES3 If data are to be encrypted (Triple AES with 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. * **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' If you do not want to authenticate the ends. * DES If you want to authenticate the ends with the DES algorithm. * RSA If you want to authenticate the ends with the RSA algorithm (valid only for cryptographic version not lower than 3.0) * **LOCAL/REMOTE SUBSYSTEMS**: These parameters only take effect when CRYPTOGRAPHIC VERSION is '3.0' or '4.0' and the authentication algorithm is RSA. The local subsystem and the remote subsystem for managing key exchange with EDITRAN/GC (option 6 of the main menu) must be specified. These parameters can be replaced by the specification of the LOCAL KEY and REMOTE KEY parameters detailed below; when both fields are specified, LOCAL/REMOTE SUBSYSTEM will be used to obtain the keys. * **LOCAL KEY**.: The Label or tag of a secondary key will be specified. If the AUTHENTICATION ALGORITHM is 'DES', the Label of the secondary 'EXPORTER' key will be specified, and if the AUTHENTICATION ALGORITHM is 'RSA', the Label or tag of the local private key will be specified. * **REMOTE KEY**.: The Label or tag of a secondary key will be specified. If the AUTHENTICATION ALGORITHM is 'DES', the Label of the secondary 'IMPORTER' key will be specified, and if the AUTHENTICATION ALGORITHM is 'RSA', the Label or tag of the remote public key will be specified. ## Fourth session screen. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:18:40 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | LOAD TYPE..................: N ((N)ORMAL, (A)CCUMULATIVE, (Q)UEUES) | | DIVISION CRITERION(V/S/N)....: V ((V)OLUME,(S)YNC.FILE,(N)ONE) | | LZW ADJUSTMENT PERCENT (0-99).: 99 SEND CONVERSION TABLE...: | | TRANSLATE ON RECEPTION (A/E/N).: E RECEPTION CONVERSION TABLE.: | | PARAMETER.: | | DELETE BUFFER AFTER EMISSION.....: S DELETE BUFFER AFTER RECEIPT..: S | | REQUEST DOWNLOAD ACK(Y/N)....: N WAIT TIME(MINUTES).......: 00 | | | | SYNC.REC.NUM.: 025 OPERATION(S/C)..: C TRACE(S/C/N)......: S | | START TIME(HHMMSS): 060000 END TIME(HHMMSS): 235959 RETRY.W.H(X/E/R/N): X | | NETNAME EXCII...: BATCZTBG CURRENT BURST RECV: | | SEND BUFFER....: 000001 RECV BUFFER: 262144 | | USER PROGRAMS | | BEFORE EMISSION..........: BEFORE RECEIPT...........: | | AFTER EMISSION.......: AFTER RECEIPT........: | | EXCEPTION...............: RECEIPT EXIT..........: | | | | EXIT, BACK, FORWARD | ----------------------------------------------------------------------------- ``` * **LOCAL CODE**: User Entity Identification Number for editran. With this number it will be recognized by the remote system connected through this session. It is your editran license code and the code by which the remote systems will see you. * **REMOTE CODE**: Identification Number of the remote Entity. It is the code provided by the remote system so that it can connect. * **APPLICATION**: Session application. * **LOAD TYPE**: * ‘N’ normal * ‘A’ accumulative (recommended value) * 'Q' File queues. With type 'Q' editran points to the file pending transmission and loads-sends it when possible. > With cumulative load type, reloading of the buffer with new application files is allowed, provided transmission has not started. The requirements for the system to work in cumulative load mode are: > > * It is assumed that load-sensitive profiles will not be modified between processes belonging to the same presentation. > * Loading is performed according to mode 2.1 or higher. That is: the CSB' file format is maintained with the ZTBGBG10 converter. > * The emission request will behave as before in all cases. That is: load and emit in the finalised state or not loaded, and emit in the loaded or emitting state. Therefore, if a session defined with accumulative load has already been loaded and emission is requested, no new data will be loaded for it. > * The load request in the not loaded, loaded, emitting or finalised state will trigger accumulative loading of the buffer. > * Once the presentation state control has been passed, in the emitting state the buffer control record is accessed and it is checked that it is really not emitting and that loading of more files can be performed. If so, it is marked as not available for editran/P so that emission does not start during the file loading process. When loading ends, the buffer is made available again. > * It can only be performed with a transmission session. > * The CICS buffer file cannot be specific, since it must be accessible from both CICS and batch simultaneously. * **LZW ADJUSTMENT PERCENT (0-99)**. Adjustment percentage of how compression will behave, to apply it when creating intermediate files. It can take values from 00 to 99, and indicates the percentage effectiveness of compression from when the application file is taken until it is passed to the buffer; for example, in a normal situation, 80 percent compression is usually given. This parameter is used for the following: * If adjust file creation space = ‘S’ is available (local environment), the adjustment will be applied to the definition of the primary space of buffers, csbnedi and compressed files. For example, if 80 percent adjustment is set, the size of the above files will be: * For compressed files, the size of the application file divided by 5. * For buffer and csbnedi files, the sum of the sizes of the application files divided by 5. * If adjust file creation space = ‘N’ is available, it will only be applied in ZTBGF54 to "increase its size to the currently calculated one". ZTBGF54 is currently calculated based on the PHS.PRIM. (REGS) field, so that if adjustment 80 is coded, in this case ZTBGF54 will be calculated as it is now, but by five. If the 3 circumstances listed below are met, the intermediate ZTBGF54 file is created (which is not compressed). * That remote iga version > 4.0 * That there is compression and/or encryption * That one of the following 2 is met: * Application files in R format and variable. * That there is translation and/or conversion. * **EMISSION CONVERSION TABLE**: Name of a resident table in the ZTBGBTCO file, which converts the characters to be sent from the application file into the characters indicated in that table (it does not change the language of the data, but adapts it to another table of the same language). If the application file language is EBCDIC, there will be a table in the ZTBGBTCO file called Send-conversion-table + (E/F). If it is ASCII it will be called Send-conversion-table + (A/B). If two files in different languages are to be sent, both tables will be applied. * **TRANSLATE ON RECEIPT (A/E/N)**: Indicates whether we want to perform translation on receipt and to which language. It translates to A (ASCII) or to E (EBCDIC), as long as the data language of the file is compatible for translation, that is, the 2 possible combinations are: RECEIVED FILE DATA LANGUAGE ‘A’ and TRANSLATE ON RECEIPT ‘E’, RECEIVED FILE DATA LANGUAGE ‘E’ and TRANSLATE ON RECEIPT ‘A’. Two files received in different languages cannot be translated on receipt. * **RECEIPT CONVERSION TABLE**: Name of a resident table in the ZTBGBTCO file, which converts the characters received in the receiving file into the characters indicated in that table (it does not change the language of the data, 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 ZTBGBTCO file called Reception-conversion-table + (E/F). If it is ASCII it will be called Reception-conversion-table + (A/B). If two files in different languages are received, both tables will be applied. * **PARAMETER**: Data required for the macro file process. * **DELETE BUFFER AFTER TRANSMISSION**: If Y, the sending buffer or buffers are deleted at the end of the send presentation (recommended value) * **DELETE BUFFER AFTER RECEPTION**: If Y, the receiving buffer or buffers are deleted at the end of the receive presentation (recommended value). * **REQUEST DOWNLOAD ACKNOWLEDGEMENT (S/N)**. This is to confirm whether a remote download is correct, so the sender will not load if it does not know this data or the timeout has not elapsed. It is not possible to operate with sessions with specific buffers. Verify them. Values * ‘S’ - The endpoint that indicates this value, in its emissions, expects the remote side to confirm the remote download. * ‘N’ - Do not confirm downloads. * **WAIT TIME (MINUTES)**.: 00-99- Time that the sender waits without being able to perform a new load if the remote side does not send the correct download result * **SYNC.REC.NUM.**: Three-digit number indicating the maximum size (number of buffer records) of the synchronization burst. That is, the specified records will be sent and a confirmation from the remote side will be awaited. This parameter is imposed by the profile of the data-sending end. Recommendation: This value is tied to the transmission speed. A good synchronization can be, for example, about 20 messages for transmission length 4050 and about 50 for transmission length 252. * **OPERATION (S=SRV/C=CLI)**: It can have 2 values. * 'S' SERVER cannot request any request from the operator menu. * 'C' CLIENT can make any request. Recommendation: C * **TRACE (S/C/N)**: If you want to record the messages exchanged in this Session in the Trace file. It can have the following values: * S: Records all exchanged messages (recommended value when defining the session) * C: Records all Control messages (all except the SFPs). (recommended value when the session works well) * N: Does not record any message. * **START TIME (HHMMSS) and END TIME (HHMMSS)**: Time window for establishing a connection or starting a send or receive operation (from the local or remote side). When both fields contain zeros or blanks, it indicates that there is no time window, and operations can be performed whenever desired. Incoming calls that arrive with a margin of up to 5 minutes above or below the time window will be accepted (courtesy schedule). Recommendation: Do not code anything unless you want control over the time window. * **RETRY.TW.(X/E/R/N)**: Time-window retry to request send-receive. Indicates that a time-out will be launched to start these processes at the time indicated as the start. Allowed values are: * 'X' for send and receive * 'E' for send only * 'R' for receive only * 'N' never. ℹ️ Recommendation: If you use a time window, code X; otherwise, code N. * **NETNAME EXCII**: Name of the specific EXCI CONNECTION to use (see the [Definition and Management of Buffer Files](/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files.md)). * **CURRENT RECV BURST**.: Three-digit numeric value that determines the update burst, on reception, of the matrix buffer files. This parameter is valid for use by concurrent resources accessing the same matrix buffer file. It performs an update of the buffer file once the specified burst has been received and releases the file so other resources can use it. It is advisable to set this burst number low when there are many simultaneous or concurrent resources; on the other hand, if there are few or none, it is advisable to set it high. If zeros are specified, it is understood that integrity control in process concurrency is not desired and that the buffer is defined with SHR (2,3). Recommendation: 10 * **TCP-PX SEND BUFFER**: Applies only to outgoing TCP and PROXY connections. In fact, it comes into effect only when the connection is outgoing and we request a SEND. In that case data must be sent. Keep in mind that, if incoming connections occur, the TCP-PX send buffer does not take its value from here; it takes its value from the equivalent parameter at local environment level (the session to be used is not yet known and it is necessary to point to the server-child process buffer at that time). In current z/OS versions the maximum value is 262144. Larger values are allowed in case future z/OS versions permit them. If zeros are indicated, no send buffer is imposed on TCP-PX connections, and the value assumed is that of the IP stack. Recommendation: If you have few simultaneous connections, code the maximum value. In other cases, generally code the maximum value. Keep in mind that, if for example you connect and send to a remote side bursts of 50 messages of 4050, you will be placing 200,000 bytes in the buffer. * **TCP-PX RECEIVE BUFFER**: Applies only to outgoing TCP and PROXY connections. In fact, it comes into effect only when the connection is outgoing and we request a RECEIVE from the remote side. In that case data must be received. Keep in mind that, if incoming connections occur, the TCP-PX receive buffer does not take its value from here; it takes its value from the equivalent parameter at local environment level (the session to be used is not yet known and it is necessary to point to the server-child process buffer at that time). In current z/OS versions the maximum value is 262144. Larger values are allowed in case future z/OS versions permit them. If zeros are indicated, no receive buffer is imposed on TCP-PX connections, and the value assumed is that of the IP stack. Recommendation: Try to verify whether you can set maximum values (in line with x25 line speed). Keep in mind that, if for example you connect and receive from a remote side bursts of 50 messages of 4050, you will be placing 200,000 bytes in the buffer. * **USER PROGRAMS**O: Called by editran/G at the end of the pre/post send/receive and exception processes. These programs will be supplied by the user and will be called at the end of the corresponding presentation processes and in each exception procedure. The communication area passed to them contains all the information used by editran/G (profiles of the local and remote entities, application and presentation session of editran/G, and profile of the editran/P sessions). If you want to use a file in them, it must be included in the corresponding procedure. ## Fifth session screen. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:20:37 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | 1.- LOCAL PROXY LINES: GEN.SEL Y/N: N | | REF01: 001 REF02: 002 REF03: REF04: REF05: REF06: | | | | | | | | | | | | | | 2.- REMOTE TCP/IP LINES (TO GO WITH OR WITHOUT PROXY): GEN.SEL Y/N: N | | REF01: 002 REF02: 001 REF03: REF04: REF05: REF06: | | | | | | | | | | | | | | LINE SELECTION, VIEW SESSION LINES. | | EXIT, BACK | ----------------------------------------------------------------------------- ``` * **LOCAL CODE**: User Entity Identification Number for editran. With this number it will be recognized by the remote system connected through this session. It is your editran license code and the code by which the remote systems will see you. * **REMOTE CODE**: Identification Number of the remote Entity. It is the code provided by the remote system so that it can connect. * **APPLICATION**: Session application. * REFxx. Internal reference of the line (indicated when it is added or changes order with option 1.9). * **GENERIC SEL. (Y/N)**. Indicates whether more than 6 lines (Y) or up to 6 lines (N) can be used. In case of Y, the REF values of the second screen are not taken (it is explained below how it is done). ## Query and selection of local and remote lines From the fifth session screen, with PF5 line selection screen, and the appropriate panels are displayed over the valid local and remote lines for this session, where the lines shown can be consulted, selected and reordered: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:20:51 TRANSMISSION SESSION | ----------------------------------------------------------------------------- | LOCAL CGO..: 0 0009994 0 REMOTE CGO.: 0 0009998 0 APPLICATION.: ABEURC | | QUERY AND SELECTION OF LOCAL AND REMOTE LINES | | ------------------------------------------------ | | - INDICATE THE OWNER: (L)OCAL / (R)EMOTE | | - CHOOSE LINE TYPE..: (P)X (I)P | | - QUERIES-> ONLY IF YOU ENTERED THROUGH OPTION: DELETE / QUERY | | - SELECTION-> ONLY IF YOU ENTERED THROUGH OPTION: ADD / MODIFY | | | | | | WHEN ADDING A SESSION, THERE MUST PREVIOUSLY EXIST VALID LINES FOR | | THE INDICATED CONNECTION TYPE (BOTH LOCAL AND REMOTE). | | OTHERWISE, ACCESS THE CORRESPONDING MENU FIRST. | | | | | | OWNER (L)OCAL,(R)EMOTE.................: L | | LINE TYPE (I)P, (P)ROXY.....................: P | | | | | | EXIT, SELECT | ----------------------------------------------------------------------------- ``` The lines shown can be local (proxy) or remote (ip) * In all cases, the internal editran line number is shown. * In the case of local PX, ip + port of the local proxy * In the case of remote IPs, ip + port of the editran or remote proxy. To be able to communicate with a remote side we will need: * If the connection is IP, at least one remote IP line (regardless of whether that destination is a remote PROXY). We will reach that IP directly (in which case we will need nothing else) or through a local proxy (in which case we will need a local proxy line). For example, if we are in session modification and select local lines, a menu similar to the following appears: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:21:03 COMMUNICATION LINES | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | OWNER: L LINE TYPE.: P CODE.....: 0 0000000 0 | | S OWNER TYPE NUM LINE CHARACTERISTICS | | - --------- --- --- ------------------------------------------------------- | | LOCAL PX 001 010.055.000.017 -07775 | | LOCAL PX 002 010.055.000.017 -07779 | | LOCAL PX 003 010.055.000.017 -09999 | | LOCAL PX 004 010.055.000.052 -07781 | | | | | | | | | | | | | | | | | | | | | | EXIT, SELECT | ----------------------------------------------------------------------------- ``` In that menu, it shows all the data already mentioned and allows: * Changing the order of the first 6 lines of the session (only when adding/modifying). * Select for display, in which case the detail menu appears: Examples of the detail menus: ``` ----------------------------------------------------------------------------- | 24/06/2026 COMMUNICATION LINES EDITRAN 5.3 | | 12:21:16 PROXY OR TCP TYPE LINE | ----------------------------------------------------------------------------- | | | OWNER: L LINE TYPE.: P CODE.....: 0 0000000 0 REFERENCE NO.: 001 | | | | | | PROXY LINE: IP ADDRESS OF THE PROXY + PROXY PORT | | | | | | IP ADDRESS (DNS/IP ADDR) PORT | | ---------------------------------------------------------------- ------ | | 010.055.000.017 07775 | | | | | | MONITOR PX (S/N).....: S DIALOG PORT (LOG) PX....: 07770 | | | | | | | | | | | | EXIT | ----------------------------------------------------------------------------- ``` 👉 **PF6** From the second screen with PF6 view of the first 6 lines 'in plain'. Several menus are displayed with the different types that the session has Example. In case the second screen had the following data: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:22:29 SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | 1.- LOCAL PROXY LINES: GEN.SEL Y/N: N | | REF01: 001 REF02: 002 REF03: REF04: REF05: REF06: | | | | | | | | | | | | | | 2.- REMOTE TCP/IP LINES (TO GO WITH OR WITHOUT PROXY): GEN.SEL Y/N: N | | REF01: 002 REF02: 001 REF03: REF04: REF05: REF06: | | | | | | | | | | | | | | LINE SELECTION, VIEW SESSION LINES. | | EXIT, BACK | ----------------------------------------------------------------------------- ``` 👉 Pressing PF6 shows the data of the first 6 local proxy lines and the first 6 remote IP lines: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:22:39 TRANSMISSION SESSION | ----------------------------------------------------------------------------- | LOCAL CODE: 0 0009994 0 REMOTE CODE: 0 0009998 0 APPLICATION: ABEURC | | 1.- LOCAL PROXY LINES: GEN.SEL Y/N: N | | REF01: 001 REF02: 002 REF03: 000 REF04: 000 REF05: 000 REF06: 000 | | 01-REF.001-->010.055.000.017 -07775 | | 02-REF.002-->010.055.000.017 -07779 | | | | | | | | | | 2.- REMOTE TCP/IP LINES (TO GO WITH OR WITHOUT PROXY): GEN.SEL Y/N: N | | REF01: 002 REF02: 001 REF03: 000 REF04: 000 REF05: 000 REF06: 000 | | 01-REF.002-->172.022.242.195 -07778 | | 02-REF.001-->172.022.242.195 -07777 | | | | | | | | | | | | EXIT | ----------------------------------------------------------------------------- ``` For modification, if the presentation session state is different from "not loaded" in send and "initialized" in receive, the following confirmation screen is displayed to continue with the modification or deletion process. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:23:22 PRESENTATION SESSION | ----------------------------------------------------------------------------- | LOCAL CGO..: 0 0009994 0 REMOTE CGO.: 0 0009998 0 APPLICATION.: MINAYA | | | | ************************************************************ | | * * | | * THE PRESENTATION STATE OF THIS SESSION * | | * IS DIFFERENT FROM INITIALIZED * | | * * | | * TRANSMISSION STATE RECEPTION STATE * | | * -------------------- -------------------- * | | * 001--> SENDING 104--> FINISHED * | | * * | | * THE MODIFICATION MAY AFFECT STATE INTEGRITY * | | * * | | * MODIFICATION OF TRANSMISSION SESSIONS IS NOT ALLOWED * | | * * | | * CONTINUE (Y/N): N * | | ************************************************************ | | | | | ----------------------------------------------------------------------------- ``` If confirmation to continue is given, 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 you will abandon it. --- # 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-cics-en/operacion/onesait-editran-administrator/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.