> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/open-v5.3-en/linux/gestor_perfiles.md). # Profile Management ## General Introduction ### Purpose [cfgupt](#actualización-de-configuración), [ediperfi](#perfiles-de-editranp), [igaperfi](#perfiles-de-editrang) and [modiperfi](#modiperfi) is to provide the user with **editran/P** and **editran/G** of a menu-driven administration mechanism suitable for unattended administration. With these commands the user can add, delete, and modify presentations **editran/G** and sessions **editran/P**. The purpose of this document is to guide the user in the handling of the update commands delivered with the Software of *editran*. ### Audience This document is intended for users of the commands **cfgupt**, **ediperfi**, **igaperfi** and **modiperfi**. Also for those responsible for administering **Editran** in unattended mode. ### Definitions * **command file**: A file that contains commands to perform administration operations. * **command**: An expression of the form "a = b" indicating an elementary action to take. Also called a parameter. * **operation**: A set of commands that constitute an addition, deletion, or modification for **editran**. ### Related documents The documents that can complement this one are: * "**editran/P** *User Manual"*. Contains information related to the administration of the editran/P system. It is useful for understanding the semantics of the administration operations performed with the software to which this manual belongs. * "**editran/G** *User Manual"*. Contains information related to the administration of the editran/G system. It is useful for understanding the semantics of the administration operations performed with the software to which this manual belongs. ## Profile Additions ### Command File We will see here the format of a command file. The file is made up of a sequence of operations to perform: ``` -- This is a comment... Operation 1 %%= Operation 2 -- This too... %%= ... Operation N %%= ``` Where *%%=* is the end of the operation. It is at this point that the commands that make up that operation will be executed. Comments are line-oriented, that is, the rest of the line after the comment sign is ignored. The same file can simultaneously contain operations related to editran/P *and* editran/G. An operation will consist of a series of commands. Each command will assign a value to a profile field or identify the type of operation to perform. To identify the type of operation to perform, it is necessary to write the following commands. **For an editran/P session:** > OPERATION = *op* > > PROFILE = *profile* > > SESSION = *session* **For an editran/G presentation:** > OPERATION = *op* > > PROFILE = *profile* > > PROFILE TYPE = *type* > > PRESENTATION = presentation The words in *italics* must be replaced by appropriate values. It is important to identify the operation before indicating what it consists of. That is, the above commands must always be placed first and before any other command in the same operation. Otherwise, command order, except in specific cases, is irrelevant and they can be placed as desired. In summary, these lines must appear before any others in each operation to be performed. With the above commands we have indicated that we want to perform an addition, deletion, or modification via OPERATION, that we refer to editran/P or editran/G via PROFILE, and to which presentation (in the case of editran/G) or session (in the case of editran/P) we refer. The rest of the commands up to the end of the operation will refer exclusively to that session or presentation. Yes *op* if it had been "B" we would be requesting a deletion. In this case it would not have been necessary to specify any more commands. For an addition or modification we can specify as many commands as we wish. If it turns out that we have not provided enough information, the corresponding command will return an error message. The following table shows how to add, delete, and modify: | Operation | Command | | ------------ | ------------- | | High | OPERATION = A | | Low | OPERATION = B | | Modification | OPERATION = M | The possible values of PROFILE can be LOC if we want to update the local profile, EDI if it is an editran/P session, IGA if it is an editran/G presentation, and FILE for the output files associated with an editran/G presentation. Commands ignore whitespace and blank lines in the input file, but there can only be one blank space between words that identify a profile field. For example: ``` LOCAL CODE = 9991 ``` This is wrong because there are three spaces between CODIGO and LOCAL. There should be only one blank space. As an example, we will mention the minimum operations to perform additions, deletions, and modifications. **To perform an addition in editran/P we will do:** ``` OPERATION = A PROFILE = EDI SESSION = EXAMPLE REMOTE CODE = 1234 APP = PRUEB1 ... %%= ``` **To perform an addition in editran/G we will do:** ``` OPERATION = A PROFILE = IGA PROFILE TYPE = P PRESENTATION = EXAMPLE REMOTE CODE = 1234 APP = PRUEBA ... ``` **To perform an addition of an output file for the previous presentation in editran/G we will do:** ``` OPERATION = A PROFILE = FILE PRESENTATION = EXAMPLE FILE NAME = pruebas.dat ... %%= ``` **To perform an addition of the local editran/P profile we will do:** ``` OPERATION = A PROFILE = LOC LOCAL CODE = 1234 ... %%= ``` In place of the ellipses the values of the different fields are indicated (which will be described later). It should be noted that, in the case of an addition, those fields that are not specified will take the default value, if this is possible. If the field contains essential information to add the session, such as, for example, not having specified the REMOTE CODE or the APPLICATION, the program will complain about it by generating the error message appropriate to the particular situation. There are fields that do not allow a default value but that do not contain fundamental information to add the session, such as, for example, REMOTE NRI. In such cases the field will remain unfilled (and it will be necessary to resort to a later profile modification operation, either through the menu or by using the appropriate command again). **To perform a deletion in editran/P (the one for editran/G is similar except that a presentation is specified, not a session) we will do:** ``` OPERATION = B PROFILE = EDI SESSION = EXAMPLE %%= ``` **To delete some of the files of an editran/G presentation we will do:** ``` OPERATION = B PROFILE = FILE PRESENTATION = EXAMPLE FILE ORDER = 3 %%= ``` Normally we will not indicate anything else when performing a deletion. Note that the local profile of editran/P cannot be deleted. **To perform a modification in editran/G we will do:** ``` OPERATION = M PROFILE = IGA PROFILE TYPE = P PRESENTATION = EXAMPLE RECEPTION DESTINATION = .\nnewdestination -- This is the modification %%= **To perform a modification in the local profile we will do:** OPERATION = M PROFILE = LOC -- We modify the local code LOCAL CODE = 4321 LOCAL NAME = TEST MODIFICATION. %%= ``` In a modification, fields not specified will retain their value. Below, we indicate the different parameters that can be in a command, as well as the values they can take. Before starting the listing, it is worth noting a couple of details. First, it should be said that the names of each parameter almost always coincide with the names associated with the same field in the editran/P and editran/G menus. However, in some cases, in order to simplify, some words have been abbreviated and others that were not essential to identify the field have been removed, and which only led to having to type longer parameters, with the possibility of making a typing error. It is therefore advisable to keep this manual close at hand until you become familiar with the exact name of each parameter. Secondly, it is necessary to comment that the parameters are not described exhaustively; only a brief description of the field and an example of use are given. If you are already familiar with *editran/P* and *editran/G,* you will have no problem identifying what each parameter corresponds to. If you are not, you should consult the corresponding user manual. ### Commands for local profile of Onesait · Editran #### Operation * **Description:** Type of operation to perform. * **Values:** A (addition) or M (modification). * **Example:** OPERATION = A #### Profile * **Description:** Identifies that the operation will be performed on the local profile of editran/P\*.\* * **Values:** LOC (*LOCAL*). * **Example:** PROFILE = LOC #### Local Code * **Description**: It is the identification code of the local center. * **Values**: A number of up to 9 digits. If fewer digits are specified it will be formatted accordingly. * **Example**: LOCAL CODE = 9991 #### Local name * **Description**: Descriptive name of the local entity. * **Values**: Alphanumeric string. * **Example**: LOCAL NAME = PC 23 #### Max sessions number * **Description**: It is the number of connections that can be active simultaneously. * **Values**: A number between 1 and 100. * **Example**: MAX SESSIONS NUMBER = 10 #### Local IP Address * **Description:** IP address of the local center. This parameter can be repeated up to three times. * **Values:** IP address or machine name in a domain. * **Example:** LOCAL IP ADDRESS = 140.30.5.3:7778 #### TCP Connection TOUT * **Description:** Time interval, expressed in seconds, in which editran waits to receive session data from the moment the connection of a remote socket is accepted. * **Values:** A number between 1 and 999. * **Example:** CONNECTION MODE = 015 ### Commands for editran/P #### Operation * **Description:** Type of operation to perform. * **Values:** A (addition), B (deletion), or M (modification). * **Example:** OPERATION = A #### Profile * **Description:** Identifies that the operation will be performed on a session *editran/P.* * **Values:** EDI (editran/P). * **Example:** PROFILE = EDI #### Session * **Description:** Mnemonic that easily identifies an editran/P session, that is, identifies the set formed by a local code, a remote code, and an application. * **Values:** Alphanumeric string. * **Example:** SESSION = EXAMPLE #### Local code * **Description:** Code that will identify the local site for the session being defined. * **Values:** A number of up to 9 digits. If fewer digits are specified the field will be properly formatted. * **Example:** LOCAL CODE = 7778 #### Local name * **Description:** Descriptive name of the local entity in the session being defined. * **Values:** Alphanumeric string. * **Example:** LOCAL NAME = MY PC #### Remote code * **Description:** It is the identification code of the remote center. * **Values:** A number of up to 9 digits. If fewer digits are specified it will be formatted accordingly. * **Example:** REMOTE CODE = 9991 #### Remote name * **Description:** Descriptive name of the remote entity. * **Values:** Alphanumeric string. * **Example**: REMOTE NAME = CICS1 #### App * **Description:** It is the code that identifies the application. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APP = PRUEBA #### App name * **Description:** Descriptive name of the editran/P application. * **Values:** Alphanumeric string. * **Example:** APP NAME = PRUEBA #### Access ID * **Description:** Identifier that complements the ORIGIN-DESTINATION-APPLICATION tuple, containing a key used during the connection representing the DESTINATION of the incoming request. Numeric 0-9. Must match at both ends of the session. * **Values:** 0 to 9. * **Example:** ACCESS ID = 0 #### Version number * **Description:** Version of the remote editran/P. * **Values:** A version (5.0, 5.1, etc.). * **Example:** VERSION NUMBER = 5.3 #### Calling end * **Description:** Who can initiate calls. * **Values:** L (only me), R (the remote), and X (anyone). In connections via PAD, calls are only allowed from the local end, since there is no reverse mechanism for addressing from the PAD to the modem. * **Example:** CALLING END = X #### Traffic direction * **Description:** What direction the traffic has. * **Values:** E (transmit only), R (receive), and X (both). * **Example:** TRAFFIC DIRECTION = X #### Automatic call * **Description:** Automatic connection requests are generated when the start of transmission or reception is requested. * **Values:** Y or N. * **Example:** AUTOMATIC CALL = S #### Automatic disconnection * **Description:** Automatic connection releases are generated when transmission or reception ends. * **Values:** Y or N. * **Example:** AUTOMATIC DISCONNECTION = S #### Timeout * **Description:** Time interval, expressed in seconds, with which editran/P waits to receive from the remote a response message to a previously sent control message. * **Values:** A number of up to 3 digits. * **Example:** TIME OUT = 30 #### Synchronization timeout * **Description:** Time interval, expressed in seconds, in which editran/P waits to receive from the remote the response message to the data transmission synchronization message. * **Values:** A number of up to 3 digits. * **Example:** TIME OUT = 30 #### Retries * **Description:** maximum number of retransmission retries. * **Values:** A number. * **Example:** RETRIES = 2 #### Save rotations * **Description:** It is desired to save the remote addresses according to the connection order. * **Values:** Y, N. * **Example:** SAVE ROTATIONS = N #### CRC * **Description:** Cyclic redundancy codes are used in each transmitted message. * **Values:** Y or N. * **Example:** CRC = S #### Server/client * **Description:** Operating mode. * **Values:** S (server) or C (client, normally). * **Example:** SERVER/CLIENT = C #### ASCII/EBCDIC * **Description:** Alphabet used on the remote. * **Values:** A (ASCII) or E (EBCDIC). * **Example:** ASCII/EBCDIC = E #### Compression * **Description**: Compressed data transmission. * **Values**: S, N, L, or V. * **Example**: COMPRESSION = N #### Start time * **Description:** Earliest time in the window when transmissions are allowed. * **Values:** A time expressed as HH:MM:SS or HHMMSS. * **Example:** START TIME = 00:00:00 #### End time * **Description:** Latest time in the window when transmissions are allowed. * **Values:** A time expressed as HH:MM:SS or HHMMSS. * **Example:** * END TIME = 23:59:59 #### Transmission block * **Description:** Size of the transmission burst. * **Values:** A number of up to three digits. * **Example:** TRANSMISSION BLOCK = 10 #### Buffer length * **Description:** Length of the records in the buffer files. * **Values:** Values between 252 and 4050. * **Example:** BUFFER LENGTH = 4050 #### Transmission processes * **Description:** Identifies the process in charge of the pre- and post-transmission phases. * **Values:** editran/G or editran/SW. * **Example:** TRANSMISSION PROCESSES = editran/G #### Reception processes * **Description:** Identifies the process in charge of the pre- and post-reception phases. * **Values**: editran/G or editran/SW. * **Example:** RECEPTION PROCESSES = editran/G #### Cryptography * **Description:** Data encryption during transmission. * **Values:** Y, N. * **Example:** CRYPTOGRAPHY = S #### Cryptography version * **Description:** Version of the cryptographic processes used. * **Values:** 3.0 and 4.0. * **Example:** * CRYPTOGRAPHY VERSION = 4.0 #### Key management * **Description:** The editran/GC module is used to access auxiliary keys. Only available with cryptography version higher than 3.0. * **Values:** Y or N. * **Example:** KEY MANAGEMENT = N #### Confidentiality * **Description:** Algorithm used for data encryption. * **Values:** TD3, AES, AE2 and AE3. * **Example:** CONFIDENTIALITY = AE3 #### Authentication * **Description:** Algorithm used in the authentication of session keys. * **Values:** DES or RSA. * **Example:** AUTHENTICATION = RSA #### Local key label * **Description:** Label associated with a key stored in the CKDS file or a proprietary subsystem in editran/GC. * **Values:** Alphanumeric string of up to 14 characters. * **Example:** LOCAL KEY LABEL = LABELRSAPC0020 #### Remote key label * **Description:** Label associated with a key stored in the CKDS file or a remote subsystem in editran/GC. * **Values:** Alphanumeric string of up to 14 characters. * **Example:** REMOTE KEY LABEL = LABELRSACICS01 #### Remote IP Address * **Description:** IP address of the remote entity. This parameter can be repeated up to six times. * **Values:** An IP address. * **Example:** REMOTE IP ADDRESS = 123.30.10.5:7778 #### Validate remote IP * **Description:** It is desired to check that the IPs of incoming TCP connections match those in the profile. * **Values:** Y, N. * **Example:** VALIDATE REMOTE IP = N #### Editran Proxy * **Description:** The editran/PX module will be used as a proxy in TCP transmission. * **Values:** Y, N. * **Example:** Editran Proxy = N #### Proxy IP address * **Description:** IP address of the Editran Proxy. This parameter can be repeated up to two times. * **Values:** An IP address. * **Example:** PROXY IP ADDRESS = 123.30.10.5:7778 #### Use SWIFT gateway * **Description:** The session transmits to an editran that is functioning as a gateway to the SWIFT network. * **Values:** Y or N. * **Example:** USE SWIFT GATEWAY = N ### Commands for editran/G #### Operation * **Description:** Type of operation to perform. * **Values:** A (addition), B (deletion), or M (modification). * **Example:** OPERATION = A #### Profile * **Description:** Identifies whether the operation will be performed on a Presentation or a File of editran/G. * **Values:** IGA (Presentation), FILE(File). * **Example:** PROFILE = IGA #### Presentation * **Description:** Mnemonic that easily identifies an editran/G presentation, that is, identifies the set formed by a local code, a remote code, and an application. * **Values:** Alphanumeric string. * **Example:** PRESENTATION = EXAMPLE The corresponding parameters for ***PROFILE = IGA*** are: #### Profile type * **Description:** Identifies whether the operation will be performed on a Remote, an Application, or a Presentation. * **Values:** R (*Remote*), A (Application) or P(*Presentation*). * **Example:** PROFILE TYPE = P #### Local code * **Description:** Code that will identify the local site for the presentation being defined. * **Values:** A number of up to 9 digits. If fewer digits are specified the field will be properly formatted. * **Example:** LOCAL CODE = 7778 #### Local name * **Description:** Descriptive name of the local entity in the presentation being defined. * **Values:** Alphanumeric string. * **Example:** LOCAL NAME = MY PC #### Remote code * **Description:** It is the identification code of the remote center. * **Values:** A number of up to 9 digits. If fewer digits are specified it will be formatted appropriately. * **Example:** REMOTE CODE = 9991 #### Remote description * **Description:** Descriptive name of the remote entity. * **Values:** Alphanumeric string. * **Example:** REMOTE DESCRIPTION = CICS1 #### Remote iga version * **Description:** It is the version of the remote editran/G. * **Values:** A valid version of editran/G. * **Example:** REMOTE IGA VERSION = 5.1 #### Cryptography * **Description:** Use of cryptography * **Values:** Y or N. * **Example:** CRYPTOGRAPHY = S #### Cryptography version * **Description:** Indicates the type of cryptographic process applied to the files. * **Values:** 3.0 or 4.0 * **Example:** CRYPTOGRAPHY VERSION = 4.0 #### Confidentiality * **Description:** Algorithm used in the encryption of the information. * **Values:** TD3, AES, AE2 or AE3. * **Example:** CONFIDENTIALITY = AE3 #### Authentication * **Description:** Algorithm to authenticate the sending entity. * **Values:** DES, RSA. * **Example:** AUTHENTICATION = RSA #### Key management * **Description:** The editran/GC module is used to access auxiliary keys. Only available with cryptography version higher than 3.0. * **Values:** Y or N. * **Example:** KEY MANAGEMENT = N #### Local label * **Description:** Label associated with a key stored in the CKDS file or a proprietary subsystem in editran/GC. * **Values:** Alphanumeric string of length 14 (label) or 1 (subsystem). * **Example:** LOCAL KEY LABEL = LABELRSAPC0020 #### Remote label * **Description:** Label associated with a key stored in the CKDS file or a remote subsystem in editran/GC. * **Values:** Alphanumeric string of length 14 (label) or 1 (subsystem). * **Example:** REMOTE KEY LABEL = LABELRSACICS01 #### App * **Description:** It is the application code. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APP = PRUEBA #### App description * **Description:** Description of the editran/G presentation application. * **Values:** Alphanumeric string. * **Example:** APP DESCRIPTION = A test #### Transmission conversion table * **Description:** Name of the file with the character values that are to be modified before transmission. * **Values:** Alphanumeric string of maximum length 15. * **Example:** TRANSMISSION CONVERSION TABLE = tablaemi #### Reception conversion table * **Description:** Name of the file with the character values that are to be modified after reception. * **Values:** Alphanumeric string of maximum length 15. * **Example:** RECEPTION CONVERSION TABLE = tablarec #### Transmission PRV * **Description:** Name of the user automation prior to transmission. * **Values:** A name of an executable. * **Example:** PRV EMISSION = U\_PRVEMI #### PRV reception * **Description:** Name of the user automation prior to reception. * **Values:** A name of an executable. * **Example:** PRV RECEPTION = U\_PRVREC #### PST emission * **Description:** Name of the user automation after emission. * **Values:** A name of an executable. * **Example:** PST EMISSION = U\_PSTEMI #### PST reception * **Description:** Name of the user automation after reception. * **Values:** A name of an executable. * **Example:** PST RECEPTION = U\_PSTREC #### Exception * **Description:** Name of the user automation in case of exception. * **Values:** A name of an executable. * **Example:** EXCEPTION = U\_EXCEPT #### Load type * **Description:** The load type can be Normal or Cumulative. * **Values:** N or A. * **Example:** LOAD TYPE = N #### EDI session count * **Description:** Number of editran/P sessions for a presentation. * **Values:** A number between 1 and 20. * **Example:** EDI SESSION COUNT = 3 #### EDI app * **Description:** Application *e*ditran/P to use for this presentation. This field will be repeated as many times as editran/P sessions we want to specify, up to a maximum of 20. * **Values:** A name of an editran/P application. * **Example:** EDI APP = TEST #### Division criterion * **Description:** Load distribution between editran/P sessions if several are going to be used. * **Values:** V (volume), F (file), N (none). * **Example:** DIVISION CRITERION = F #### Reception destination * **Description:** The name of the directory or file where the received file(s) will be placed. * **Values:** A directory or file name. * **Example:** RECEPTION DESTINATION = .\destino #### Translate on reception * **Description:** Translation selector between character sets in file downloads. * **Values:** E (are translated to *EBCDIC* those arriving in *ASCII*). A (are translated to *ASCII* those arriving in *EBCDIC*). N (not translated). * **Example:** TRANSLATE ON RECEPTION = N #### Reception delimiter * **Description:** Delimiter to use in the download of fixed files. * **Values:** N (None), D (DOS) and U (UNIX). * **Example:** RECEPTION DELIMITER = D #### Check signatures * **Description:** If the editran/FF functionality is contracted, verify that the files to be emitted have not been modified and that their sending has been authorized. * **Values:** Y or N. * **Example:** CHECK SIGNATURES = N #### Request download acknowledgment * **Description:** With this option, the sent transfers are not considered finished until the remote side returns the result of its download or until the waiting time is exceeded. * **Values:** Y or N. * **Example:** REQUEST DOWNLOAD ACK = N #### Download ack wait time * **Description:** Maximum waiting minutes to receive the download acknowledgment. * **Values:** A number between 1 and 99 (inclusive). * **Example:** DOWNLOAD ACK WAIT TIME = 5 The corresponding parameters for ***PROFILE = FILE*** are: #### File order * **Description:** editran/G presentations have an associated list of files for emission. This parameter identifies the file on which we perform the operation according to its order in the list. It is only taken into account when the operation is delete or modify. * **Values:** Numeric. * **Example:** FILE ORDER = 5 #### File name * **Description:** Set of files with the same characteristics taken as the source of the transfer. * **Values:** A file name. Supports the use of metacharacters. * **Example:** FILE NAME = .\origen\\\*.txt #### Format * **Description:** Describes the way in which the information to be transmitted will be organized. * **Values:** F (Fixed), V (Variable), H (Hybrid) and B (Binary). * **Example:** FORMAT = F #### Record length * **Description:** Length of the records in the application files. * **Values:** A number of up to five digits. * **Example:** RECORD LENGTH = 80 #### Delimiter * **Description:** Delimiter used in loading files with Fixed format. * **Values:** N (None), D (Dos) and U (UNIX). * **Example:** DELIMITER = N #### Compression * **Description:** Use of file compression. * **Values:** F (compression is used) or N. * **Example:** COMPRESSION = F #### Alphabet * **Description:** Character set selector for the files to be emitted. * **Values:** E (*EBCDIC*), A (*ASCII)* or N (*None*). * **Example:** ALPHABET = A #### Translate * **Description:** Translation selector between character sets. * **Values:** S (translated to *EBCDIC* if ALPHABET is A or to *ASCII* if ALPHABET is E). N (not translated). * **Example:** TRANSLATE = N ### Configuration update The command ***cfgupt*** is responsible for carrying out this task. It is responsible for interpreting command files and options on the argument line. In addition, it allows dumping sessions **editran/P** and **editran/G** to a text file with the command syntax described above. It is usually invoked to: * get help * run a command file * run commands that we give as arguments * dump sessions to a text file. #### Help In its first role, when we invoke it as ***cfgupt -h*** it informs us of its use, and when we invoke it as ***cfgupt -H*** it also informs us of the possible parameters we can modify in profiles: ```bash cfgupt -h usage: cfgupt [-h|-H] [-r { [-a[ei]] | [-l] | [-e ...] [-i ...] } [-o] ] | [-i] [-e] [-E] [-I] | [-f] -h: help. -H: help (complete list of -E and -I commands). -r: dump of sessions to a text file. -ae: dump of all sessions and of the local editran/P profile. -ai: dump of all editran/G presentations. -l: dump of the local editran/P profile. -e: dump of editran/P sessions -i: dump of editran/G presentations. -ofichout: dump sessions to the file *fichout*. -ecmd: use 'cmd' as the interpreter for -E options. -icmd: use 'cmd' as the interpreter for -I options. -ffichin: read commands from file fichin. -Exx=yy: set editran/P profile parameter 'xx' to 'yy'. -Ixx=yy: set editran/G profile parameter 'xx' to 'yy'. To see how to use -E and -I and return codes, use the -H option. ``` The -E\=\ options set 'field' to 'value' in the editran/P profile (-E) or the editran/G profile (-I); they can be mixed. op=A or B or M must be specified depending on whether it is an add, delete, or modification. Also profile=EDI or profile=IGA must be specified depending on whether an editran/P or editran/G profile is to be modified. Several operations can be specified. An operation must have the form: -Eop=X -Eperfil=X -Exx=yy ... The start of another operation or the end of arguments indicates the end of the current operation. -E and -I cannot be mixed with -f. | The values that xx can take in -Exx=yy are: | | | ------------------------------------------- | ----------------------- | | alphabet | ASCII/EBCDIC | | application | APPLICATION | | authentic | AUTHENTICATION | | auto | AUTOMATIC CALL | | auto-disconnect | AUTOMATIC DISCONNECTION | | key change | KEY CHANGE | | encryption | CRYPTOGRAPHY | | local code | LOCAL CODE | | remote code | REMOTE CODE | | compress | COMPRESSION | | connection | CONNECTION TYPE | | confidential | CONFIDENTIALITY | | crc | CRC | | key management | KEY MANAGEMENT | | access id | ACCESS ID | | local IP address | LOCAL IP ADDRESS | | proxy IP address | PROXY IP ADDRESS | | remote IP address | REMOTE IP ADDRESS | | local label | LOCAL KEY LABEL | | remote label | REMOTE KEY LABEL | | caller | CALLING END | | application name | APPLICATION NAME | | local name | LOCAL NAME | | remote name | REMOTE NAME | | op | OPERATION | | profile | PROFILE | | emission processes | EMISSION PROCESSES | | reception processes | RECEPTION PROCESSES | | proxy | EDITRAN PROXY | | burst | EMISSION BLOCK | | retry | RETRIES | | rotation | SAVE ROTATIONS | | traffic direction | TRAFFIC DIRECTION | | server/client | SERVER/CLIENT | | session | SESSION | | app sync | APP SYNCHRONIZATION | | swiftp | USE SWIFT GATEWAY | | buffer | BUFFER LENGTH | | tfin | END TIME | | timeout | TIMEOUT | | tinicio | START TIME | | toutdesc | DISCONNECTION TIMEOUT | | toutsinc | SYNCHRONIZATION TIMEOUT | | valip | VALIDATE REMOTE IP | | encrypted version | CRYPTOGRAPHY VERSION | | versrem | VERSION NUM | | The values that xx can take in -Ixx=yy are: | | | ------------------------------------------- | -------------------------- | | acknowledgment | REQUEST DOWNLOAD ACK | | alphabet | ASCII/EBCDIC | | file alphabet | ALPHABET | | EDI app | EDI APP | | application | APPLICATION | | authenticate | AUTHENTICATION | | load | LOAD TYPE | | encryption | CRYPTOGRAPHY | | local key label | LOCAL LABEL | | remote key label | REMOTE LABEL | | local code | LOCAL CODE | | remote code | REMOTE CODE | | compress | COMPRESSION | | confidential | CONFIDENTIALITY | | emission delimiter | DELIMITER | | reception delimiter | RECEPTION DELIMITER | | division | DIVISION CRITERION | | reception destination | RECEPTION DESTINATION | | check signatures | CHECK SIGNATURES | | format | FORMAT | | key management | KEY MANAGEMENT | | incses | INC SESSION PRES | | record length | RECORD LENGTH | | application name | APPLICATION DESCRIPTION | | file name | FILE NAME | | local name | LOCAL NAME | | remote name | REMOTE DESCRIPTION | | number of sessions | EDI SESSION COUNT | | op | OPERATION | | order | FILE ORDER | | profile | PROFILE | | presentation | PRESENTATION | | prvemi | PRV EMISSION | | prvrec | PRV RECEPTION | | pstemi | PST EMISSION | | pstrec | PST RECEPTION | | emission conversion table | EMISSION CONVERSION TABLE | | reception conversion table | RECEPTION CONVERSION TABLE | | type | PROFILE TYPE | | download ack wait time | DOWNLOAD ACK WAIT TIME | | translate | TRANSLATE | | translate on reception | TRANSLATE ON RECEPTION | | usrexc | EXCEPTION | | encrypted version | CRYPTOGRAPHY VERSION | | versigarem | REMOTE IGA VERSION | | The return values (to the system) are: | | | -------------------------------------- | - | | All good | 0 | | Argument error | 1 | | Runtime error | 2 | | Error in ediperfi | 4 | | Error in igaperfi | 5 | #### Processing of a command file If we want to run commands from files, we invoke it as ***cfgupt -f**file*, where "file" is the file containing the commands. A possible session would be: `cfgupt -fALTAS.cmd` After that, the operations contained in ALTAS.cmd will have been executed. ### Direct command indication In this case, the update is indicated directly on the command line, as in: `cfgupt -Eop=A -Eperfil=EDI -Esesion=EJEMPLO -Ecodrem=9991 -Eaplic=PRUEBA` `cfgupt -Eop=B -Eperfil=EDI -Esesion=EJEMPLO` Where we first add the EJEMPLO session and then remove it. When specifying operations on the argument line, the same rules apply as when writing them in a command file. The only additional notes are: * The "-E" is used to indicate commands intended for editran/P. * The "-I" is used to indicate commands intended for editran/G. Each possible parameter in a command file has an associated option on the argument line. As an example of the above notes, the file corresponding to the previous invocations of ***cfgupt*** would be: For the first invocation: ``` -- *** begin of command file generated by cfgupt *** OPERATION = A --(0) PROFILE = EDI --(1) SESSION = EXAMPLE --(2) REMOTE CODE = 9991 --(3) APPLICATION = TEST --(4) -- End of operation. (5 commands sent) %%= -- *** total: 5 commands sent -- *** end of command file generated by cfgupt *** ``` For the second invocation: ``` -- *** begin of command file generated by cfgupt *** OPERATION = B --(0) PROFILE = EDI --(1) SESSION = EXAMPLE --(2) -- End of operation. (3 commands sent) %%= -- *** total: 3 commands sent -- *** end of command file generated by cfgupt *** ``` #### Dump to sessions file. It is also possible to dump the contents of editran/P and editran/G sessions to a text file. The syntax of the generated file is the same as that used for unattended profile updates (that is, from an input file), so the command files obtained in this way can be modified for later incorporation into the configuration files of editran/P and editran/G (making use of the command again ***cfgupt***). It can therefore be said that this option complements the one that allowed sessions to be updated from a text file. The syntax of the command ***cfgupt*** in this case is as follows: `cfgupt -r {[-a[ei] | [-l] | [-e][-i]}[-o]` where: > -r: indicates that a dump operation is requested. > > -a\[ei]: specifies that all sessions are dumped. "-ae" dumps the local profile and all editran/P sessions; "-ai" dumps all editran/G presentations. Both options can be specified at the same time or even in a single expression "-aei". > > -l: specifies that the local profile is dumped. The previous option and this one are mutually exclusive. > > -e\: specifies the editran/P session to dump. > > -i\: specifies the editran/G presentation to dump. > > -o\: specifies the file to which the sessions will be dumped. If it does not exist, it is created. If it already exists, the sessions are appended to the end of that file. If this option is not specified, standard output is used by default. Let's now look at some usage examples. The following line: `cfgupt -r -eEJEMPLO` Dumps the editran/P session "EXAMPLE" to standard output. If we had written: `cfgupt -r -iEJEMPLO -oout` the contents of the editran/G presentation "EXAMPLE" would be dumped to the file *out*. The following example shows how several sessions and presentations would be dumped: `cfgupt -r -eEJEMPLO1EDI -iEJEMPLO1IGA -e-EJEMPLO2EDI -iEJEMPLO2IGA -oout` If any of the sessions is not defined in the corresponding configuration file, an error message will be generated. If we wanted to dump the local profile and all defined editran/P sessions: `cfgupt -r -ae -oout` If we wanted to dump the local profile: `cfgupt -r -l -oout` If we wanted to dump all defined editran/G presentations: `cfgupt -r -ai -oout` Finally, to dump the contents of the profile files to a file we would write the following: `cfgupt -r -aei -oout` #### Tips As usually happens, there are certain tricks that may be useful. One of them is to use the "-e" and "-i" options of ***cfgupt***. The "-e" option makes it possible to specify which program will be responsible for executing operations for administration of editran/P (normally ***ediperfi***). The "-i" option makes it possible to specify which program will be responsible for executing operations for administration of editran/G (normally ***igaperfi***). The program ***cfgupt***, when taking operations from the argument line, constructs a command file that it passes to the appropriate interpreter (***ediperfi*** or ***igaperfi*** normally). However, we can create the following "script" in the file *dump*: ```sh #!/bin/sh cat \>DUMP ``` after which, an invocation `cfgupt -evolcar -Eop=B -Eperfil=EDI -Esesion=EJEMPLO` will leave in the file DUMP a command file equivalent to the options we have indicated. ### Errors Error messages may be due to problems in ***cfgupt*** or in the interpreters. In any case, the codes returned to the system are those indicated in the help (zero if everything goes well, non-zero if there are problems). ### editran/P Profiles The command ***ediperfi*** is responsible for interpreting (and executing) editran/P administration operations. Its syntax is as follows: ``` ediperfi: Unattended Input Command for editran Profiles. Usage: ediperfi [-h] [-f] [-r {[-a [-V] [-R] [-n]] | [-l] | [-s]} [-o]] -h: help (this) -f: name of the file with profile modification commands. (default=stdin) -r: dump of editran sessions to file. -s: editran session to dump. -a: dump of all sessions and the local profile to file. -l: dump of the local profile to file -R: Release of the file to dump Possible values for : 0..7 -V: Version of the file to dump Possible values for : 41, 50, 51, 52, 53 -n: do not dump sessions without network data -o: name of the file to which the session will be dumped. (default=stdout) ``` Given its similarity to the syntax of ***cfgupt***, the usage examples for this one are practically directly applicable (restricted, of course, to the options available in ***ediperfi***). ### editran/G Profiles The command ***igaperfi*** is responsible for interpreting (and executing) editran/G administration operations. Its syntax is as follows: ``` igaperfi: Unattended Input Command for editran/G Profiles. Usage: igaperfi [-h] [-f: Release of the file to dump. Valid values for : 0..7 -V: Version of the file to dump. Valid values for : 41, 50, 51, 52, 53 -o/cfg). However, when they are used to migrate profiles from previous versions, the old configuration files should be copied to the directory where the programs are located unless the CFG\_PERFIL variable is used to define the full path of the file to be migrated. Below is an example of migration using the variable. Assuming that the previous version was installed in /opt/editran/v521 in a Unix environment with sh shell, go to the directory of the new installation and run: ```sh CFG_PERFIL=/opt/editran/v521/editranp.cfg ediperfi -r -a -V52 -r1 -operfilesP.txt CFG_PERFIL=/opt/Editran/v521/editrang.cfg igaperfi -r -a -V52 -r1 -operfilesG.txt ``` ## Modiperfi ### Introduction. The purpose of the command ***modiperfi*** is to provide the user with **editran/P** and from **editran/G** of a non-menu-driven administration mechanism suitable for unattended administration. With this command the user can modify, simultaneously, as many parameters as desired in multiple sessions **editran/P** or in different presentations *editran/G,*\*\* as well as unregister the profiles. ### How to use The command ***modiperfi*** is based on the repeated use of the command ***cfgupt*** in the profile modification and deletion modes of editran/P or in the profile modification and deletion modes of editran/G. This makes it possible to modify the parameters of more than one session or more than one presentation in a single command line or to unregister more than one profile. The program syntax is as follows: ```bash modiperfi [-h] | {-o [-r] [-a] [-l] [-s|-p] -m<-Exx=yy ...|-Ixx=yy ...>|} | {-b -o [-r] [-a] [-l] [-s]} | {-b [-r] [-l]} ``` Where: -h: Help on screen. -o\ is the argument with which the user will specify whether they want to modify/unregister the editran/P profiles, in which case they will write *P* after the identifier "-o", or if they want to modify/unregister the editran/G profiles, in which case they will write *G,* or F for the special case of modifications in the editran/G profile referring to the parameters of the output files\*.\* -c for changes referring to output files, first it tries to modify, but if it fails it tries to create. -r\ is the argument that will serve to limit the sessions (if *P*) or presentations (if *G* or *F*), whose parameters you want to modify, to those whose remote code matches the one entered. It is possible to enter only the significant digits. -a\ is the argument with which the sessions (if *P*) or presentations (if *G* or *F*), whose parameters you want to modify, that match the entered application code, will be filtered. It admits the '\*' character as a wildcard, so that when it is used, the command will modify the profiles of as many sessions or presentations whose application starts with the letters preceding the asterisk. -l\ is the argument that will restrict the changes to the sessions (if *P*) or presentations (if *G* or *F*) with the local code written after the identifier "-l". It is possible to enter only the significant digits. -s\|-p\ is the appropriate argument to filter either the sessions or the presentations to modify/unregister, to those whose session(s) or presentation(s) match, or start in the case of using the '\*' character as a wildcard, with the literal entered after the identifier "-s" or "-p". This argument must be consistent with the argument identified as "-o", the argument in which the option of the profiles to be modified is chosen. Thus, if in that argument you entered *P*, in this one you will write --s\ and if you wrote *G* or *F* now you will have to enter -p\. -m<-Exx=yy ...|-Ixx=yy ...|-Iorder=n ...> is the argument through which the user will specify the parameters they want to modify by assigning the value 'yy' to the 'xx' field. As with the previous one, this argument must be consistent with the one in which the option *P*, *G* or *F*. For the first, editran/P profiles, -Exx=yy will be written, and for the second and third, editran/G profiles and file parameters, -Ixx=yy. In the specific case of *F*, the first -Ixx=yy must be the one referring to the order of the file to be modified; therefore -Iorder=n, where n is the number that identifies the file position in the output-files list. Then the modification(s) to be made on the parameters of said file must be placed. -b is the argument used to identify that the profiles of one or several sessions and/or one or several presentations are going to be unregistered. #### Modification of editran/P and editran/G profiles This command usage option allows filtering, in each case, according to four profile parameters. The way to do this, in each case, is the same as is used in the command ***cfgupt*** and is described in detail in this user manual. Go to [its specific section](#actualización-de-configuración) to consult the field or parameter labels that xx can take in -Exx=yy and/or Ixx=yy. If more than one parameter is to be modified, they will be placed one after another, separated by a space, and with quotation marks at the beginning and end of the series. In this case the form of the argument would be: -m"-Exx=yy -Exx=yy -Exx=yy ..." or -m"-Ixx=yy -Ixx=yy -Ixx=yy ...". If the value that you want to assign to a parameter contains spaces, that value must be delimited with the characters **\\"** as follows: -m"-Exx=\\"yy\\"..." ..." or -m"-Ixx=\\"yy\\" ...". Except for the option argument, identified with "-o", and the modification argument, identified with "-m", all the others are optional. When an argument does not appear, it will not be filtered according to that parameter and all sessions or presentations with respect to that argument will be modified. Once the command has been executed, the sessions or presentations being modified will be shown on screen and at the end the number of sessions or presentations in which the profile has been successfully modified. #### Unregistering editran/P and editran/G profiles This command usage option allows: * Unregister sessions (-oP) or presentations (-oG) applying combinations of the following filters: `modiperfi -b -o [-r] [-a] [-l] [-s]` * Unregister sessions and presentations together, allowing filtering by local code and/or remote code: `modiperfi -b [-r] [-l]` Once the command has been executed, the sessions or presentations whose profiles are being unregistered will be shown on screen and at the end the number of sessions or presentations in which this task has been successfully achieved. #### Application examples. Below are some examples of using the command. In each case, the command line itself will appear first and then the execution it performs: **Modification of editran/P profiles** * **modiperfi -oP -m-Eversrem=31** It will modify the field *version* in the profile of all EDITRAN/P sessions, applying the value *31* to that field. * **modiperfi -oP -r000002030 -m-Eversrem=31 o modiperfi -oP -r203 -m-Eversrem=31** It will modify the field *version* in the profile of all sessions whose remote code is *000002030,* assigning it the value *31*. As can be seen, the remote code can be written with all its digits or only with the significant ones. * **modiperfi -oP -r203 -aPR\* -m-Eversrem=31** It will modify the field *version* in the profile of all sessions whose remote code is *000002030* and whose application code starts with '*PR*', assigning it the value *31*. * **modiperfi -oP -r000002030 -aPR\* -l1111 -m-Eversrem=31** It will modify the field *version* in the profile of all sessions whose remote code is *000002030*, whose application code starts with 'PR' and with local code equal to *000011110*, assigning it the value *31*. * **modiperfi -oP -r000002030 -aPR\* -l000011110 --sLOCAL -m-Eversrem=31** It will modify the field *version* in the profile of all sessions whose remote code is *000002030*, whose application code starts with '*PR*', with local code equal to *000011110* and with session name *LOCAL*, assigning it the value *31*. * **modiperfi -oP -r203 -aPR\* -l1111 --sLOCAL -m"-Eversrem=31 -Eaplic=TCP001"** It will modify the fields *version* and *application code* in the profile of all sessions whose remote code is *000002030*, whose application code starts with '*PR*', with local code equal to *000011110* and with session name *LOCAL*, assigning them the value *31* and *TCP001* respectively. As can be seen, when introducing more than one *-Exx=yy* a space must be added between each one and the next, as well as quotation marks at the beginning and end of the series. * **modiperfi -oP -r000002030 -m"-Eversrem=31 -Eaplic=TCP001 -Ereint=3"** It will modify the version, application code and maximum number of retries fields in the profile of all sessions whose remote code is 000002030, assigning them the values 31, TCP001 and 3 respectively. * modiperfi -oP --sPRUEBA -m"-Enomaplic=\\"Aplicacion 2023\\"" Modifies in the session *PRUEBA* the field *application name* assigning it the value *Application 2023*. Note that the new application name has been delimited with the characters \\" since it contains spaces. **Unregistering editran/P profiles** * **modiperfi -b -oP --sE\*** Will unregister the profiles of the editran/P sessions whose names begin with "E". **Modification of editran/G profiles** * **modiperfi -oG -m-Idstrec=.\destino** It will modify the field *receiving destination* in the profile of all presentations, applying in all of them the value *.\destino* to that field. * **modiperfi -oG -r000002030 -m-Idstrec=.\destino o modiperfi -oG -r203 -m-Idstrec=.\destino** will modify the field *receiving destination* in the profile of all presentations whose remote code is *000002030,* assigning it the value *.\destino*. As can be seen, the remote code can be written in full or only the significant digits. * **modiperfi -oG -r000002030 -aPR\* -m-Idstrec=.\destino** It will modify the field *receiving destination* in the profile of all presentations whose remote code is *000002030* and whose application code starts with '*PR*', assigning it the value *.\destino*. * **modiperfi -oG -r203 -aPR\* -l1111 -m-Idstrec=.\destino** It will modify the field *receiving destination* in the profile of all presentations whose remote code is *000002030*, whose application code starts with 'PR' and with local code equal to *000011110*, assigning it the value *.\destino*. * **modiperfi -oG -r000002030 -aPR\* -l1111 -pLOCAL -m-Idstrec=.\destino** It will modify the field *receiving destination* in the profile of all presentations whose remote code is *000002030*, whose application code starts with '*PR*', with local code equal to *000011110* and with presentation name *LOCAL*, assigning it the value *.\destino*. * **modiperfi -oG -r203 -pM\* -m"-Iautentica=DES -Iusrexc=U\_EXCEPT"** It will modify the fields *authentication* and *exception* in the profiles of all presentations with remote code equal to *000002030* and whose presentation name starts with 'M', assigning them the values *DES* and *U\_EXCEPT* respectively. As can be seen, when introducing more than one *-Ixx=yy* a space must be added between each one and the next, as well as quotation marks at the beginning and end of the series. * **modiperfi -oF -r203 -aPR\* -l000011110 -pLOCAL -m"-Iorden=1 -Inomfich=nuevo.c"** It will modify the field *file name,* in the first file in the output-files list, in the profile of all presentations whose remote code is *000002030*, whose application code starts with '*PR*', with local code equal to *000011110* and with presentation name *LOCAL*, assigning it the value *new\.c*. **Specifying the order of the file whose parameters are to be specified is mandatory.** * **modiperfi -oF -r000002030 -m"-Iorden=1 -Inomfich=nuevo.c -Ialffich=N"** It will modify the fields *file name* and *alphabet* in the first file in the output-files list of the profile of all presentations whose remote code is *000002030*, assigning them the value *new\.c* and *N* respectively. **Unregistering editran/G profiles** * **modiperfi -b -oG -pPRUEBA** Will unregister the editran/G profile of the presentation "PRUEBA". **Joint unregistering of editran/P and editran/G profiles** * **modiperfi -b -r000002030** Will unregister the editran/P and editran/G profiles whose remote code is *000002030.* * **modiperfi -b -l000011110** Will unregister the editran/P and editran/G profiles whose local code is *000011110.* * **modiperfi -b -l000011110 -r000002030** Will unregister the editran/P and editran/G profiles whose local code is *000011110* and whose remote code is *000002030* **Output examples** Below are the screen outputs obtained from two commands. * **modiperfi -oP -l204 -m"-Eversrem=31 -Ealfabeto=A"** Modifying session(s)... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP3 EDITRAN TCP4 EDITRAN TCP5 GODELLO TCP1 The profiles of 6 sessions have been modified. * **modiperfi -oG -l204 -pG\* -m"-Ialfabeto=A -Iusrexc=U\_EXCEPT"** Modifying presentation(s)... GODELLO TCP1 The profile of one presentation has been modified. * **modiperfi -oF -r99991 -pE\* -m"-Iorden=1 -Inomfich=nuevo.c -Icompres=N"** Modifying presentation(s)... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP4 EDITRAN TCP5 The profiles of 4 presentations have been modified. * **modiperfi -b -oG -pE\*** The presentation(s) are being unregistered... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP4 EDITRAN TCP5 4 presentations have been unregistered. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/open-v5.3-en/linux/gestor_perfiles.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.