> 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/windows/gestor_perfiles.md). # Profile Management ## General Introduction ### Purpose The purpose of the commands [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** a menu-driven administration mechanism suitable for unattended administration. With these commands, the user can create, delete, and modify presentations **editran/G** and sessions **editran/P**. The purpose of this document is to guide the user in handling 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 containing commands to perform administration operations. * **command**: An expression of the form "a = b" that indicates an elementary action to be taken. Also called a parameter. * **operation**: A set of commands that make up a create, delete, or modification for **editran**. ### Related documents The documents that can supplement this are: * **Communications platform**. Contains information related to 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. * **Generic application interface**. Contains information related to 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 Registration ### Command file Here we will see the format of a command file. The file is made up of a sequence of operations to be performed: ``` -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 making up that operation will be executed. Comments are line-oriented, that is, the rest of the line from the comment sign onward is ignored. The same file can simultaneously contain operations related to editran/P *and* editran/G. An operation will be made up of a series of commands. Each command will assign a value to a profile field or identify the type of operation to be performed. To identify the type of operation to be performed, 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 with appropriate values. It is important to identify the operation before indicating what it consists of. That is, the above commands must always be entered first and before any other command in the same operation. Otherwise, the order of commands, except in specific cases, is irrelevant and they can be entered as desired. In summary, these lines must appear before any other in each operation to be performed. With the above commands, we have indicated that we want to perform a create, delete, or modification via OPERATION, that we are referring to editran/P or editran/G via PROFILE, and which presentation (in the case of editran/G) or session (in the case of editran/P) we are referring to. The rest of the commands up to the end of the operation will refer exclusively to that session or presentation. Yes *op* had it been "B" we would be requesting a deletion. In this case it would not have been necessary to specify any more commands. For a create or modification we can specify as many commands as we want. If it turns out that we have not provided enough information, the corresponding command will give an error message. The following table shows how to create, 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. The commands ignore whitespace and empty lines in the input file, but there can only be one space between words that identify a profile field. For example: ``` LOCAL CODE = 9991 ``` It's wrong because there are three spaces between CODE and LOCAL. There should be only one space. As an example, we will mention the minimum operations to perform creates, deletions, and modifications. **To perform a create in editran/P we will do:** ``` OPERATION = A PROFILE = EDI SESSION = EXAMPLE REMOTE CODE = 1234 APPLICATION = PRUEB1 ... %%= ``` **To perform a create in editran/G we will do:** ``` OPERATION = A PROFILE = IGA PROFILE TYPE = P PRESENTATION = EXAMPLE REMOTE CODE = 1234 APPLICATION = PRUEBA ... %%= ``` **To perform a create 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 a create of the local editran/P profile we will do:** ``` OPERATION = A PROFILE = LOC LOCAL CODE = 1234 ... %%= ``` In the 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 a create, those fields that are not specified will take the default value, if this is possible. If the field contains information essential to create the session such as, for example, not having specified the REMOTE CODE or the APPLICATION, the program will complain by generating the error message appropriate to the particular situation. There are fields that do not admit a default value but that do not contain fundamental information to create the session such as, for example, REMOTE NRI. In those cases the field will be left blank (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 (editran/G is similar except that a presentation is specified rather than 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 editran/P profile 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, those fields that are not specified will retain their value. Next, we indicate the different parameters that can be in a command, as well as the values they can take. Before starting with the enumeration, it is worth noting a couple of details. First of all, it should be said that the names of each of the parameters 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 and that would only lead to having to write longer parameters, with the possibility of making a typo, have been removed. 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 not, you should consult the corresponding user manual. ### Onesait Editran Local Profile Commands #### Operation * **Description:** Operation type to be performed. * **Values:** A (create) 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 local center identification code. * **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:** Local IP address of the 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 Timeout * **Description:** Time interval, expressed in seconds, in which editran waits to receive session data from the moment a remote socket connection is accepted. * **Values:** A number between 1 and 999. * **Example:** CONNECTION MODE = 015 ### Commands for editran/P #### Operation * **Description:** Operation type to be performed. * **Values:** A (create), B (delete) 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, it 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 for the session that is 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 that is 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 conveniently formatted. * **Example:** REMOTE CODE = 9991 #### Remote name * **Description:** Descriptive name of the remote entity. * **Values:** Alphanumeric string. * **Example**: REMOTE NAME = CICS1 #### Application * **Description:** It is the code that identifies the application. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APPLICATION = PRUEBA #### Application name * **Description:** Descriptive name of the editran/P application. * **Values:** Alphanumeric string. * **Example:** APPLICATION NAME = PRUEBA #### Access ID * **Description:** Identifier that complements the SOURCE-DESTINATION-APPLICATION tuple, containing a key used during the connection representing the DESTINATION of the incoming request. Numeric from 0-9. It 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 PAD connections, only the call from the local end is allowed, since there is no reverse mechanism for addressing 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:** S or N. * **Example:** AUTOMATIC CALL = S #### Automatic disconnection * **Description:** Automatic connection releases are generated when transmission or reception ends. * **Values:** S or N. * **Example:** AUTOMATIC DISCONNECTION = S #### Time out * **Description:** Time interval, expressed in seconds, with which editran/P waits to receive from the remote a response message to one of the control messages previously sent. * **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 retries in retransmission. * **Values:** A number. * **Example:** RETRIES = 3 #### Save rotations * **Description:** You want to store the remote addresses according to the order of connection. * **Values:** S, N. * **Example:** SAVE ROTATIONS = N #### CRC * **Description:** Cyclic redundancy checks are used in each transmitted message. * **Values:** S 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:** Minimum time of the window in which transmissions are allowed. * **Values:** A time expressed as HH:MM:SS or HHMMSS. * **Example:** START TIME = 00:00:00 #### End time * **Description:** Maximum time of the window in which 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 of 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:** S, 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 the auxiliary keys. Only available in cryptography versions above 3.0. * **Values:** S or N. * **Example:** KEY MANAGEMENT = N #### Confidentiality * **Description:** Algorithm used for data encryption. * **Values:** DES, TD2, TD3, AES, AE2 and AE3. * **Example:** CONFIDENTIALITY = TD3 #### Authentication * **Description:** Algorithm used in session key authentication. * **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:** Remote entity IP address. 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:** You want to check that the IPs of incoming TCP connections match those of the profile. * **Values:** S, N. * **Example:** VALIDATE REMOTE IP = N #### Editran Proxy * **Description:** The editran/PX module will be used as a proxy in TCP transmission. * **Values:** S, N. * **Example:** Editran proxy = N #### PROXY IP Address * **Description:** Editran Proxy IP address. 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 acting as a gateway to the SWIFT network. * **Values:** S or N. * **Example:** USE SWIFT GATEWAY = N ### Commands for editran/G #### Operation * **Description:** Operation type to be performed. * **Values:** A (create), B (delete) 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, it identifies the set formed by a local code, a remote code and an application. * **Values:** Alphanumeric string. * **Example:** PRESENTATION = EXAMPLE The parameters corresponding to ***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 for the presentation that is 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 that is 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:** S 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 information encryption. * **Values:** DES, TD2, TD3, AES, AE2 or AE3. * **Example:** CONFIDENTIALITY = AES #### 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 the auxiliary keys. Only available with cryptography version above 3.0. * **Values:** S 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 #### ASCII/EBCDIC * **Description:** Alphabet used on the remote. It should correspond to that indicated in the associated editran/P session. Only used with remotes with version lower than 5.0. * **Values:** A (ascii) or E (ebcdic). * **Example:** ASCII/EBCDIC = E #### Application * **Description:** It is the application code. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APPLICATION = PRUEBA #### Application description * **Description:** Description of the editran/G presentation application. * **Values:** Alphanumeric string. * **Example:** APPLICATION DESCRIPTION = A test #### Transmission conversion table * **Description:** Name of the file with the character values that will be modified before transmission. * **Values:** Alphanumeric string of maximum length 15. * **Example:** TRANSMISSION CONVERSION TABLE = tableemi #### Reception conversion table * **Description:** Name of the file with the character values that will be modified after reception. * **Values:** Alphanumeric string of maximum length 15. * **Example:** RECEPTION CONVERSION TABLE = tablarec #### PRV sending * **Description:** Name of the user automation prior to sending. * **Values:** A name of an executable. * **Example:** PRV SENDING = 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 sending * **Description:** Name of the user automation after sending. * **Values:** A name of an executable. * **Example:** PST SENDING = 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 #### INC presentation session * **Description:** Indicates whether the presentation session identifier should be incremented. * **Values:** S or N. * **Example:** INC PRESENTATION SESSION = S #### Load type * **Description:** The load type can be Normal or Accumulative. * **Values:** N or A. * **Example:** LOAD TYPE = N #### EDI sessions num * **Description:** Number of editran/P sessions for a presentation. * **Values:** A number between 1 and 20. * **Example:** EDI SESSIONS NUM = 3 #### EDI app * **Description:** Application *e*ditran/P to be used 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 APPLICATION = TEST #### Split criterion * **Description:** Load distribution among editran/P sessions if several are to be used. * **Values:** V (volume), F (file), N (none). * **Example:** SPLIT 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 (translated to *EBCDIC* those that arrive in *ASCII*). A (translated to *ASCII* those that arrive in *EBCDIC*). N (not translated). * **Example:** TRANSLATE ON RECEPTION = N #### Delimiter on reception * **Description:** Delimiter to use in the download of fixed-format files. * **Values:** N(None), D(DOS), and U(UNIX). * **Example:** DELIMITER ON RECEPTION = D #### Check signatures * **Description:** If the editran/FF functionality is contracted, verify that the files to be sent have not been modified and that their sending has been authorized. * **Values:** S or N. * **Example:** CHECK SIGNATURES = N #### Request download acknowledgment * **Description:** With this option, sent transfers are not considered finished until the result of their download is received from the remote side or until the wait time is exceeded. * **Values:** S or N. * **Example:** REQUEST DOWNLOAD ACKNOWLEDGMENT = N #### Download acknowledgment wait time * **Description:** Maximum minutes to wait to receive the download acknowledgment. * **Values:** A number between 1 and 99 (inclusive). * **Example:** DOWNLOAD ACKNOWLEDGMENT WAIT TIME = 5 The parameters corresponding to ***PROFILE = FILE*** are: #### File order * **Description:** editran/G presentations have an associated list of files for sending. This parameter identifies the file on which we perform the operation based on 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 that are taken as the source of the transfer. * **Values:** A file name. Supports the use of metacharacters. * **Example:** FILE NAME = .\origen\\\*.txt #### Format * **Description:** Describes how 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 at most five digits. * **Example:** RECORD LENGTH = 80 #### Delimiter * **Description:** Delimiter used when loading fixed-format files. * **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 files to be sent. * **Values:** E (*EBCDIC*), A (*ASCII)* or N (*None*). * **Example:** ALPHABET = A #### Translate * **Description:** Character set translation selector. * **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 performing 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 normally invoked to: * get help * run a command file * run commands that we pass as arguments * dump sessions to a text file. #### Help In its first mode, when we invoke it as ***cfgupt -h*** it shows its usage, and when we invoke it as ***cfgupt -H*** it also shows the possible parameters that 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 sessions to a text file. -ae: dump all sessions and the local editran/P profile. -ai: dump all editran/G presentations. -l: dump the local editran/P profile. -e: dump editran/P sessions -i: dump editran/G presentations. -o: dump sessions to file *outfile*. -e: use 'cmd' as the interpreter for -E options. -i: use 'cmd' as the interpreter for -I options. -f: read commands from file inputfile. -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. ``` To see how to use -E and -I and return codes, use the option `cfgupt -H`. The options -E\=\ set 'field' to 'value' in the editran/P profile (-E) or the editran/G profile (-I) and can be mixed. op=A or B or M must be specified depending on whether it is an add, delete, or modification. profile=EDI or profile=IGA must also be specified depending on whether an editran/P or editran/G profile is being modified. Various operations can be specified. An operation must be of 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 | | password change | PASSWORD CHANGE | | encryption | CRYPTOGRAPHY | | local code | LOCAL CODE | | remote code | REMOTE CODE | | compression | 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 key label | LOCAL KEY LABEL | | remote key label | REMOTE KEY LABEL | | calling endpoint | CALLING ENDPOINT | | app name | APP NAME | | local name | LOCAL NAME | | remote name | REMOTE NAME | | op | OPERATION | | profile | PROFILE | | prcemi | SENDING PROCESSES | | prcrec | RECEPTION PROCESSES | | proxy | EDITRAN PROXY | | burst | SENDING BLOCK | | retries | RETRIES | | rotac | SAVE ROTATIONS | | senttraf | TRAFFIC DIRECTION | | servcli | SERVER/CLIENT | | session | SESSION | | sicrap | APP SYNCHRONIZATION | | swiftp | USE SWIFT GATEWAY | | tampon | BUFFER LENGTH | | tfin | END TIME | | timeout | TIME OUT | | tinicio | START TIME | | toutdesc | DISCONNECTION TIMEOUT | | toutsinc | SYNCHRONIZATION TIMEOUT | | valip | VALIDATE REMOTE IP | | verscifrado | CRYPTOGRAPHY VERSION | | versrem | VERSION NUM | | The values that xx can take in -Ixx=yy are: | | | ------------------------------------------- | --------------------------------- | | acknowledgment | REQUEST DOWNLOAD ACKNOWLEDGMENT | | alphabet | ASCII/EBCDIC | | alfich | ALPHABET | | aplcedi | EDI APPLICATION | | application | APPLICATION | | authenticate | AUTHENTICATION | | load | LOAD TYPE | | encryption | CRYPTOGRAPHY | | clavelocal | LOCAL LABEL | | claveremota | REMOTE LABEL | | local code | LOCAL CODE | | remote code | REMOTE CODE | | compress | COMPRESSION | | confidenc | CONFIDENTIALITY | | delimemi | DELIMITER | | delimrec | DELIMITER ON RECEPTION | | div | SPLIT CRITERION | | dstrec | RECEPTION DESTINATION | | ediff | CHECK SIGNATURES | | format | FORMAT | | key management | KEY MANAGEMENT | | incses | INC PRESENTATION SESSION | | longreg | RECORD LENGTH | | app name | APPLICATION DESCRIPTION | | nomfich | FILE NAME | | local name | LOCAL NAME | | remote name | REMOTE DESCRIPTION | | numses | EDI SESSIONS NUM | | op | OPERATION | | order | FILE ORDER | | profile | PROFILE | | present | PRESENTATION | | prvemi | PRV SENDING | | prvrec | PRV RECEPTION | | pstemi | PST SENDING | | pstrec | PST RECEPTION | | tablaemi | SENDING CONVERSION TABLE | | tablarec | RECEPTION CONVERSION TABLE | | type | PROFILE TYPE | | toutacuse | DOWNLOAD ACKNOWLEDGMENT WAIT TIME | | translat | TRANSLATE | | translateonrec | TRANSLATE ON RECEPTION | | usrexc | EXCEPTION | | verscifrado | CRYPTOGRAPHY VERSION | | versigarem | VIEW REMOTE IGA | | Return values (to the system) are: | | | ---------------------------------- | - | | All good | 0 | | Argument error | 1 | | Operational error | 2 | | Error in ediperfi | 4 | | Error in igaperfi | 5 | #### Processing of a command file If we want to run commands from files, we will invoke it as ***cfgupt -f**file*, where "file" is the file containing the commands. A possible example would be: `cfgupt -fALTAS.cmd` After which, the operations contained in ALTAS.cmd will have been executed. ### Direct command entry In this case, the update is specified 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 create the EJEMPLO session and then delete it. When indicating operations on the command 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 command line. As an example of the previous notes, the file corresponding to the previous invocations of ***cfgupt*** would be: For the first invocation: For the first invocation: ``` -- *** begin of command file generated by cfgupt *** OPERATION = A --(0) PROFILE = EDI --(1) SESSION = EJEMPLO --(2) REMOTE CODE = 9991 --(3) APP = PRUEBA --(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 = EJEMPLO --(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 content 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 (using again the command ***cfgupt***). It can therefore be said that this option complements the one that allowed session updates 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 to be 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 to be dumped. The previous option and this one are mutually exclusive. > > -e\: specifies the editran/P session to be dumped. > > -i\: specifies the editran/G presentation to be dumped. > > -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 assumed by default. Let us now look at some usage examples. The following line: `cfgupt -r -eEJEMPLO` Dumps the editran/P session "EJEMPLO" to standard output. If we had written: `cfgupt -r -iEJEMPLO -oout` the contents of the editran/G presentation "EJEMPLO" 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 registered 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` #### Tricks As is often the case, there are certain tricks that can be useful. One of them is to use the "-e" and "-i" options of ***cfgupt***. The "-e" option allows indicating which program will be in charge of executing operations for the administration of editran/P (normally ***ediperfi***). The "-i" option allows indicating which program will be in charge of executing operations for the administration of editran/G (normally ***igaperfi***). The program ***cfgupt***, when it takes operations from the command line, builds 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 >VOLCADO ``` after which, an invocation `>cfgupt -evolcar -Eop=B -Eperfil=EDI -Esesion=EJEMPLO` will leave in the file VOLCADO 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 editran profile introduction command. 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 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 in which the session will be dumped. (default=stdout) ``` Given its similarity with the syntax of ***cfgupt***, the usage examples for this one are applicable almost directly (of course, restricting ourselves to the ***ediperfi***). ### editran/G profiles The command ***igaperfi*** is responsible for interpreting (and executing) editran/G administration operations. Its syntax is as follows: ``` igaperfi: Unattended editran/G profile introduction command. 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. Supposing that the previous version was installed in C:\editran521 in a command window, go to the directory of the new installation and execute: ```sh set CFG_PERFIL=C:\editran521\cfg\editranp.cfg ediperfi -r -a -V52 -r1 -operfilesP.txt set CFG_PERFIL=C:\editran521\cfg\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 menu-free 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 delete 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. Thus, it adds the possibility of modifying the parameters of more than one session or more than one presentation on a single command line or of deleting 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: Output the help on screen. -o\ is the argument with which the user will specify whether they want to modify/delete the editran/P profiles, in which case they will write *P* after the identifier "-o", if they want to modify/delete the editran/G profiles, writing in this case *G,* or F in the particular case of modifications in the editran/G profile referring to the emission file parameters\*.\* -c for changes referring to emission files, modification is attempted first, but if it fails creation is attempted. -r\ is the argument that will serve to limit the sessions (if *P*) or presentations (if *G* or *F*), whose parameters are to be modified, to those whose remote code matches the one entered. It is possible to enter only the significant digits. -a\ is the argument used to filter the sessions (if *P*) or presentations (if *G* or *F*), whose parameters are to be modified, that match the entered application code. 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 begins 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 be modified/deleted, to those whose sessions or presentations match, or begin 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 for the profiles to modify is chosen. Thus, if in that argument *P*, in this one -s\ will be written and if *G* or *F* was written, now -p\ must be entered. -m<-Exx=yy ...|-Ixx=yy ...|-Iorden=n ...> is the argument through which the user will specify the parameters they want to modify by assigning the value 'yy' to field 'xx'. 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 -Iorden=n, where n is the number that identifies the position of the file in the list of emission files. After that, the modification(s) to be made on the parameters of said file must be placed. -b is the argument by means of which it is identified that the profiles of one or several sessions and/or one or several presentations will be deleted. #### Modification editran/P and editran/G profiles This command use option allows filtering, in each case, according to four profile parameters. The way to do this, in each case, is the same as that used in the command ***cfgupt*** and is extensively detailed in this user manual. Access [its specific section](#actualización-de-configuración) to consult the field labels or parameters 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 quotes 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 to be given 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 modifications 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 regarding said 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. #### Deletion of editran/P and editran/G profiles This command use option allows: * Delete sessions (-oP) or presentations (-oG) applying combinations of the following filters: `modiperfi -b -o [-r] [-a] [-l] [-s]` * Delete sessions and presentations together, being able to filter 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 deleted 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** Will modify the field *version* in the profile of all EDITRAN/P sessions by applying the value *31* to said field. * **modiperfi -oP -r000002030 -m-Eversrem=31 o modiperfi -oP -r203 -m-Eversrem=31** 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** Will modify the field *version* in the profile of all sessions whose remote code is *000002030* and whose application code begins with '*PR*', assigning it the value *31*. * **modiperfi -oP -r000002030 -aPR\* -l1111 -m-Eversrem=31** Will modify the field *version* in the profile of all sessions whose remote code is *000002030*, whose application code begins with 'PR' and with local code equal to *000011110*, assigning it the value *31*. * **modiperfi -oP -r000002030 -aPR\* -l000011110 --sLOCAL -m-Eversrem=31** Will modify the field *version* in the profile of all sessions whose remote code is *000002030*, whose application code begins 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"** Will modify the fields *version* and *application code* in the profile of all sessions whose remote code is *000002030*, whose application code begins 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 entering more than one *-Exx=yy* a space must be added between each one and the next as well as quotes at the beginning and end of the series. * **modiperfi -oP -r000002030 -m"-Eversrem=31 -Eaplic=TCP001 -Ereint=3"** 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 values 31, TCP001 and 3 respectively. * modiperfi -oP --sPRUEBA -m"-Enomaplic=\\"Aplicacion 2023\\"" Modifies in session *PRUEBA* field *application name* assigning it the value *Application 2023*. Note that the new application name has been delimited with the characters \\" because it contains spaces. **Deletion of editran/P profiles** * **modiperfi -b -oP --sE\*** Will delete the profiles of the editran/P sessions whose names begin with "E". **Modification of editran/G profiles** * **modiperfi -oG -m-Idstrec=.\destino** Will modify the field *reception destination* in the profile of all presentations by applying in all of them the value *.\destination* to said field. * **modiperfi -oG -r000002030 -m-Idstrec=.\destino o modiperfi -oG -r203 -m-Idstrec=.\destino** will modify the field *reception destination* in the profile of all presentations whose remote code is *000002030,* assigning it the value *.\destination*. As can be seen, the remote code can be written in full or only the significant digits. * **modiperfi -oG -r000002030 -aPR\* -m-Idstrec=.\destino** Will modify the field *reception destination* in the profile of all presentations whose remote code is *000002030* and whose application code begins with '*PR*', assigning it the value *.\destination*. * **modiperfi -oG -r203 -aPR\* -l1111 -m-Idstrec=.\destino** Will modify the field *reception destination* in the profile of all presentations whose remote code is *000002030*, whose application code begins with 'PR' and with local code equal to *000011110*, assigning it the value *.\destination*. * **modiperfi -oG -r000002030 -aPR\* -l1111 -pLOCAL -m-Idstrec=.\destino** Will modify the field *reception destination* in the profile of all presentations whose remote code is *000002030*, whose application code begins with '*PR*', with local code equal to *000011110* and with the presentation name *LOCAL*, assigning it the value *.\destination*. * **modiperfi -oG -r203 -pM\* -m"-Iautentica=DES -Iusrexc=U\_EXCEPT"** Will modify the fields *authentication* and *exception* in the profiles of all presentations with remote code equal to *000002030* and whose presentation name begins with 'M', assigning them the values *DES* and *U\_EXCEPT* respectively. As can be seen, when entering more than one *-Ixx=yy* a space must be added between each one and the next as well as quotes at the beginning and end of the series. * **modiperfi -oF -r203 -aPR\* -l000011110 -pLOCAL -m"-Iorden=1 -Inomfich=nuevo.c"** Will modify the field *file name,* in the first file of the emission files list\*,\* in the profile of all presentations whose remote code is *000002030*, whose application code begins with '*PR*', with local code equal to *000011110* and with the presentation name *LOCAL*, assigning it the value *nuevo.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"** Will modify the fields *file name* and *alphabet* in the first file of the emission files list of the profile of all presentations whose remote code is *000002030*, assigning them the value *nuevo.c* and *N* respectively. **Deletion of editran/G profiles** * **modiperfi -b -oG -pPRUEBA** Will delete the editran/G profile of the presentation "PRUEBA". **Joint deletion of editran/P and editran/G profiles** * **modiperfi -b -r000002030** Will delete the Editran/P and editran/G profiles whose remote code is *000002030.* * **modiperfi -b -l000011110** Will delete the Editran/P and editran/G profiles whose local code is *000011110.* * **modiperfi -b -l000011110 -r000002030** Will delete the Editran/P and editran/G profiles whose local code is *000011110* and whose remote code is *000002030* **Output examples** Below, the screen outputs obtained from two commands are shown. * **modiperfi -oP -l204 -m"-Eversrem=31 -Ealfabeto=A"** Modifying the session(s)... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP3 EDITRAN TCP4 EDITRAN TCP5 GODELLO TCP1 6 session profiles have been modified. * **modiperfi -oG -l204 -pG\* -m"-Ialfabeto=A -Iusrexc=U\_EXCEPT"** Modifying the presentation(s)... GODELLO TCP1 A presentation profile has been modified. * **modiperfi -oF -r99991 -pE\* -m"-Iorden=1 -Inomfich=nuevo.c -Icompres=N"** Modifying the presentation(s)... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP4 EDITRAN TCP5 4 presentation profiles have been modified. * **modiperfi -b -oG -pE\*** The presentation(s) are being deleted... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP4 EDITRAN TCP5 4 presentations have been deleted. --- # 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/windows/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.