> 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.2.1-en/windows/gestor_perfiles.md). # Profile management ## General Introduction ### Purpose The purpose of the commands **cfgupt**, **ediperfi**, **igaperfi** and **modiperfi** is to provide the user with **editran/P** and **editran/G** a menu-driven management 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 Editran software *editran*. ### Audience This document is intended for users of the commands **cfgupt**, **ediperfi**, **igaperfi** and **modiperfi**. It is also intended for those responsible for administering **editran** in unattended mode. ### Definitions * **command file**: A file that contains commands to perform administrative operations. * **command**: An expression of the form "a = b" that indicates an elementary action to take. Also called 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**. It contains information related to administration of the editran/P system. It is useful for understanding the semantics of administrative operations performed with the software to which this manual belongs. * **editran/G User Manual**. It contains information related to administration of the editran/G system. It is useful for understanding the semantics of administrative operations performed with the software to which this manual belongs. ## Profile Registration ### Command file We will look here at 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 is ignored from the comment sign onward. The same file can simultaneously contain operations related to editran/P *and* editran/G. An operation is made up of a series of commands. Each command will assign a value to a field of a profile 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 by suitable values. It is important to identify the operation before indicating what it consists of. That is, the previous commands must always be placed first and before any other command of the same operation. Otherwise, the order of commands, except in specific cases, is irrelevant and may be entered as desired. In short, these lines must appear before any others in each operation to be carried out. With the previous commands we have indicated that we want to perform an addition, deletion, or modification using OPERATION, that we refer to editran/P or editran/G using 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* had been "B" we would be requesting a deletion. In this case, it would not have been necessary to indicate any more commands. For an addition or modification we can indicate as many commands as we want. If it turns out that we have not provided enough information, the corresponding command will display an error message. The following table indicates how to add, delete, and modify: *** | Operation | Command | | ------------ | ------------- | | Addition | OPERATION = A | | Deletion | 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 spaces and blank lines in the input file, but there can only be one space between words that identify a field of a profile. For example: ``` CODE LOCAL = 9991 ``` It is 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 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 editran/P local 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 that is possible. If the field contains information essential for adding the session, such as not having specified the REMOTE CODE or the APPLICATION, for example, the program will complain by generating the appropriate error message for the particular situation. There are fields that do not admit a default value but that do not contain essential information for adding the session, such as REMOTE NRI, for example. In such cases the field will remain 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 (that of editran/G is similar with the exception 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. It should be noted 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 = PRUEBA MODIFICATION. %%= ``` In a modification, those fields that are not specified will keep 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 list, it is worth pointing out a couple of details. First, it should be said that the names of each of the parameters almost always match 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 only led to having to type longer parameters, with the possibility of making a mistake when typing, have been removed. It is therefore advisable to keep this manual close at hand until you become familiar with the specific name of each parameter. Secondly, it is necessary to mention 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. ### Onesait Editran Local Profile Commands #### Operation * **Description:** Operation type to be performed. * **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 number of sessions * **Description**: It is the number of connections that can be active simultaneously. * **Values**: A number between 1 and 100. * **Example**: MAX NUMBER OF SESSIONS = 10 #### Local IP Address * **Description:** The 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 since 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:** Operation type to be performed. * **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 formatted accordingly. * **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 #### Application * **Description:** It is the code that identifies the application. * **Values:** An 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 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 (4.1, 5.0, etc.). * **Example:** VERSION NUMBER = 4.1 #### Calling end * **Description:** Who can initiate calls. * **Values:** L (local only), R (the remote) and X (either). In connections via PAD, calls are only allowed from the local end, since there is no inverse mechanism for addressing the PAD to the modem. * **Example:** CALLING END = X #### Traffic direction * **Description:** What direction the traffic has. * **Values:** E (send 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 a control message 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 synchronization of data sending. * **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:** The remote addresses are to be saved according to the connection order. * **Values:** S, N. * **Example:** SAVE ROTATIONS = N #### CRC * **Description:** Cyclic redundancy codes 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 #### Emission block * **Description:** Size of the transmission burst. * **Values:** A number of up to three digits. * **Example:** EMISSION BLOCK = 10 #### Buffer length * **Description:** Length of the records in the buffer files. * **Values:** Values between 252 and 4050. * **Example:** BUFFER LENGTH = 4050 #### Emission processes * **Description:** Identifies the process responsible for the pre- and post-emission phases. * **Values:** editran/G *or* editran/SW\*.\* * **Example:** EMISSION PROCESSES = editran/G #### Reception processes * **Description:** Identifies the process responsible for 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:** 2.2, 3.0 and 4.0. * **Example:** * CRYPTOGRAPHY VERSION = 2.2 #### Key change * **Description:** Indicates whether the key is changed with each transmission (assuming we use cryptography 2.2). * **Values:** S or N. * **Example**: KEY CHANGE = N #### Key management * **Description:** The editran/GC module is used to access auxiliary keys. Only available in cryptography version higher than 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 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:** 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:** 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:** S or N. * **Example:** USE SWIFT GATEWAY = N ### Commands for editran/G #### Operation * **Description:** Operation type to be performed. * **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 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 site for the presentation being defined. * **Values:** A number of up to 9 digits. If fewer digits are specified, the field will be formatted accordingly. * **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:** S or N. * **Example:** CRYPTOGRAPHY = Y #### Cryptography version * **Description:** Indicates the type of cryptographic process applied to the files. * **Values:** 2.2, 3.0 or 4.0 * **Example:** CRYPTOGRAPHY VERSION = 3.0 #### Confidentiality * **Description:** Algorithm used in the encryption of the information. * **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 auxiliary keys. Only available with cryptography version higher than 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 match the one 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 #### 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:** APPLICATION DESCRIPTION = A test #### Emission conversion table * **Description:** Name of the file containing the values of the characters that will be modified before emission. * **Values:** Alphanumeric string with a maximum length of 15. * **Example:** EMISSION CONVERSION TABLE = tablaemi #### Reception conversion table * **Description:** Name of the file containing the values of the characters that will be modified after reception. * **Values:** Alphanumeric string with a maximum length of 15. * **Example:** RECEPTION CONVERSION TABLE = tablarec #### Emission PRV * **Description:** Name of the user automation prior to emission. * **Values:** A name of an executable. * **Example:** EMISSION PRV = U\_PRVEMI #### Reception PRV * **Description:** Name of the user automation prior to reception. * **Values:** A name of an executable. * **Example:** RECEPTION PRV = U\_PRVREC #### Emission PST * **Description:** Name of the user automation after emission. * **Values:** A name of an executable. * **Example:** EMISSION PST = U\_PSTEMI #### Reception PST * **Description:** Name of the user automation after reception. * **Values:** A name of an executable. * **Example:** RECEPTION PST = U\_PSTREC #### Exception * **Description:** Name of the user automation in case of exception. * **Values:** A name of an executable. * **Example:** EXCEPTION = U\_EXCEPT #### Presentation session increment * **Description:** Indicates whether you want to increment the presentation session identifier. * **Values:** S or N. * **Example:** PRESENTATION SESSION INCREMENT = Y #### Load type * **Description:** The load type can be Normal or Cumulative. * **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 APP = PRUEBA #### Division criterion * **Description:** Load distribution among editran/P sessions if several are 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 (they are translated to *EBCDIC* those arriving in *ASCII*). A (they are translated to *ASCII* those arriving in *EBCDIC*). N (not translated). * **Example:** TRANSLATE ON RECEPTION = N #### Delimiter at reception * **Description:** Delimiter to use in fixed-file downloads. * **Values:** N (None), D (DOS) and U (UNIX). * **Example:** DELIMITER AT RECEPTION = 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:** S or N. * **Example:** CHECK SIGNATURES = N #### Confirm download * **Description:** With this option, sent transmissions are not considered finished until the notification from the remote side with the result of their download is received. * **Values:** S or N. * **Example:** CONFIRM DOWNLOAD = N The parameters corresponding to ***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 that are taken as the source of the transfer. * **Values:** A file name. Supports the use of wildcard characters. * **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:** 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 the files to be emitted. * **Values:** E (*EBCDIC*), A (*ASCII)* or N (*None*). * **Example:** ALPHABET = A #### Translate * **Description:** Translation selector between character sets. * **Values:** Y (it is 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 command line. It also 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 pass as arguments * dump sessions to a text file. #### Help In its first aspect, 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 that we can modify in profiles\[^2]: ``` usage: cfgupt [ -h | -H] [-r {[-a[ei]] | [-l] | [-e ...] [-i ...]} [-o]] | [-i] [-e] [-E= ...] [-I= ...] | [-f [-w]] -h: help (this one) -H: help (complete list of -E and -I commands) -r: dump sessions to 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 . -e: use 'cmd' as the -E option interpreter -i: use 'cmd' as the -I option interpreter -E=: set EDItran/P profile parameter 'xx' to 'yy' -I=: set EDItran/G profile parameter 'xx' to 'yy' -f: read commands from file -f -w: execute synchronously the commands read from file to see how to use -E and -I and return codes use the -H option. 'cfgupt -H' ``` 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 editran/G profile (-I); they can be mixed. op=A or B or M must be indicated according to whether it is an add, delete, or modification. profile=EDI or profile=IGA must also be indicated depending on whether an editran/P or editran/G profile is to be modified. Several operations can be indicated. An operation must be in 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. You cannot mix -E and -I with -f. The values that xx can take in -Exx=yy are: | | | | ------------------------------------------- | ----------------------- | | alphabet | ASCII/EBCDIC | | app | APP | | authentication | AUTHENTICATION | | auto | AUTOMATIC CALL | | autodisc | AUTOMATIC DISCONNECTION | | cclave | KEY CHANGE | | cryptography | CRYPTOGRAPHY | | codloc | LOCAL CODE | | codrem | REMOTE CODE | | compr | COMPRESSION | | conex | CONNECTION TYPE | | confidencial | CONFIDENTIALITY | | crc | CRC | | gclaves | KEY MANAGEMENT | | idacceso | ACCESS ID | | iploc | LOCAL IP ADDRESS | | ipproxy | PROXY IP ADDRESS | | iprem | REMOTE IP ADDRESS | | labelloc | LOCAL KEY LABEL | | labelrem | REMOTE KEY LABEL | | caller | CALLING END | | nomaplic | APP NAME | | nomloc | LOCAL NAME | | nomrem | REMOTE NAME | | op | OPERATION | | profile | PROFILE | | prcemi | EMISSION PROCESSES | | prcrec | RECEPTION PROCESSES | | proxy | EDITRAN PROXY | | rafaga | EMISSION BLOCK | | reint | 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 | TIMEOUT | | tinicio | START TIME | | toutdesc | DISCONNECTION TIMEOUT | | toutsinc | SYNCHRONIZATION TIMEOUT | | valip | VALIDATE REMOTE IP | | verscifrado | CRYPTOGRAPHY VERSION | | versrem | VERSION NUMBER | | | | | | | | The values that xx can take in -Ixx=yy are: | | | | | | ------------ | -------------------------- | | ackcarga | CONFIRM DOWNLOADS | | alphabet | ASCII/EBCDIC | | alffich | ALPHABET | | aplcedi | EDI APP | | app | APP | | authentica | AUTHENTICATION | | load | LOAD TYPE | | cryptography | CRYPTOGRAPHY | | clavelocal | LOCAL LABEL | | claveremota | REMOTE LABEL | | codloc | LOCAL CODE | | codrem | REMOTE CODE | | compres | COMPRESSION | | confidenc | CONFIDENTIALITY | | delimemi | DELIMITER | | delimrec | DELIMITER AT RECEPTION | | div | DIVISION CRITERION | | dstrec | RECEPTION DESTINATION | | ediff | CHECK SIGNATURES | | format | FORMAT | | gclaves | KEY MANAGEMENT | | incses | INC PRESENTATION SESSION | | longreg | RECORD LENGTH | | nomaplic | APPLICATION DESCRIPTION | | nomfich | FILE NAME | | nomloc | LOCAL NAME | | nomrem | REMOTE DESCRIPTION | | numses | EDI SESSIONS NUM | | op | OPERATION | | order | FILE ORDER | | profile | PROFILE | | present | PRESENTATION | | prvemi | EMISSION PRV | | prvrec | RECEPTION PRV | | pstemi | EMISSION PST | | pstrec | RECEPTION PST | | tablaemi | EMISSION CONVERSION TABLE | | tablarec | RECEPTION CONVERSION TABLE | | type | PROFILE TYPE | | translate | TRANSLATE | | traducrec | TRANSLATE ON RECEPTION | | usrexc | EXCEPTION | | verscifrado | CRYPTOGRAPHY VERSION | | versigarem | VIEW REMOTE IGA | 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 a command file If, on the other hand, we want to execute commands from files, we would invoke it as ***cfgupt -f**file*, where "file" is the file that contains the commands. A possible session would be: `cfgupt -fALTAS.cmd` After which, the operations contained in ALTAS.cmd will have been executed. ### Direct command input 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 first we register the session EJEMPLO and then delete 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: * "-E" is used to indicate commands intended for editran/P. * "-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 = EJEMPLO --(2) REMOTE CODE = 9991 --(3) APPL = 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 a session 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 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 will be assumed by default. Let's look at some usage examples below. The following line: cfgupt -r -eEJEMPLO Dumps the editran/P session "EJEMPLO" to standard output. If we had written: cfgupt -r -iEJEMPLO -oout the content 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 #### Tips As often happens, 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 you to specify which program will be responsible for executing operations for administering editran/P (normally ***ediperfi***). The "-i" option allows you to specify which program will be responsible for executing operations for administering editran/G (normally ***igaperfi***). The program ***cfgupt***, when it takes operations from the argument 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 specified. ### 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 Introduction Command for editran Profiles. > Use: ediperfi \[-h] \[-f\] > > \[-r {\[-a \[-V\] \[-R\] \[-n]] | \[-l] | \[-s\]} \[-o\]] > > -h: help (this one) > > -f\: name of the file with commands for > > profile modification. (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..8 > > -V\: Version of the file to dump > > Possible values for \ : 30, 31, 40, 41, 50 and 51 > > -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 to the syntax of ***cfgupt***, the usage examples for it are applicable almost directly (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 Introduction Command for Profiles *editran/G*. > > Usage: igaperfi \[-h] \[-f\] > > \[-r {\[-a \[-V\] \[-R\]] | \[-s\]} \[-o\]] > > -h: help (this one) > > -f\: name of the file with commands for > > profile modification. (default=stdin) > > -r: dump of editran/G presentations to file. > > -s\: editran/G presentation to dump. > > -a: dump all presentations to a file. > > -R\: Release of the file to dump. > > Valid values of \ 1..8 > > -V\: Version of the file to dump. > > Valid values of \ 30, 31, 40, 41, 50 and 51 > > -o\: name of the file in which > > the session will be dumped. (default=stdout) Given its similarity to the syntax of ***cfgupt***, the usage examples for it are applicable almost directly (restricted, of course, to the options available in ***igaperfi***). It is worth noting that both with ***igaperfi*** as well as with ***ediperfi*** it is possible to specify a direct operation (profile update from a command file) simultaneously with one or more inverse operations (dump to a text file of editran/P and editran/G sessions), something that is not possible with ***cfgupt***. ### Profile migration during installation The commands ***ediperfi*** e ***igaperfi*** can be used as a utility that enables portability of configuration files when editran software updates are needed. Updates to higher versions could cause old configuration files to be incompatible with the new installation; to preserve the initial configuration, we will use the commands with the options **-V** and **-R** discussed in the previous sections and that allow us to recover, in text format, the profiles defined for other editran versions. It is worth noting that the use of the commands for updating profiles from previous versions is intended as a help during the installation process, so it has some restrictions, which we describe. Old configuration files can only be dumped to text format in their entirety, that is, the options **-V** and **-R** are incompatible with **-s** and **-l**. However, the user can always edit the resulting text file if they want to make any changes before generating the new configuration files. In addition, it is advisable that the recovery of the old profiles be performed when there are still no profile files for the new installation. Below, the steps to follow are described with an example in which the editran Ver. 4.1 Rel. 7 profiles are recovered in a UNIX environment: \> cp editranp.cfg editranp.cfg.bak \> cp editrang.cfg editrang.cfg.bak It is advisable to keep a backup copy of the source files. \> ediperfi -r -a --V41 -r7 -operfiles.txt \> igaperfi -r -a --V41 -r7 -operfiles.txt Read the editran/P and editran/G profiles indicating the version and release to which the configuration files correspond, and dump the information into the command file *perfiles.txt*. Except for some specific cases that will be explained later, it is not necessary to modify this file. \> rm editranp.cfg \> rm editrang.cfg Delete the old profile files. \> ediperfi -fperfiles.txt \> igaperfi -fperfiles.txt Generate the profile files for the new installation. As mentioned in the usage example, there may be some cases in which it is not possible to port the old configuration without first making some changes to the command file. Let's explain some practical cases of these situations: * Profiles that may have been incorrectly registered in previous versions and that are validated in this version. * If the version update involved a change in the supported protocol, for example, from an X.25 version to TCP/IP, the user must modify the parameters of the network-level-dependent sessions. For example, in this case, the new values of LOCAL IP ADDRESS and REMOTE IP ADDRESS would have to be assigned. Migration aspects related to cryptography: * the file **ckds.des** from the old installation must be copied to the new one, since the sessions keep the keys they had before the update. * The file **ckds.rsa** from previous versions disappears. RSA key migration will be done using the migra\_rsa command. ### CFG\_PERFIL variable In principle, the commands ***ediperfi*** e ***igaperfi*** work with the configuration files located in the editran data directory (by default \/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 the previous version was installed in /opt/editran/v417 in a Unix environment with shell sh, go to the directory of the new installation and execute: \> CFG\_PERFIL=/opt/editran/v417/editranp.cfg \> ediperfi -r -a --V41 -r7 -operfiles.txt \> CFG\_PERFIL=/opt/Editran/v417/editrang.cfg ## MODIPERFI ### Introduction. The purpose of the command ***modiperfi*** is to provide the user with **editran/P** and from **editran/G** of a menu-driven management 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 the profiles. ### Usage The command ***modiperfi*** is based on the repeated use of the command ***cfgupt*** in the modify and delete modes of editran/P profiles or in the modify and delete modes of editran/G profiles. Thus, it adds the possibility of modifying the parameters of more than one session or more than one presentation in a single command line or deleting more than one profile. The program syntax is as follows: modiperfi \[-h] | {-o\ \[-r\] \[-a\] \[-l\] \[-s\|-p\] -m<-Exx=yy ...|-Ixx=yy ...>|} | {-b -o\ -s\|-p\} Where: * h: Help output on screen. * o\ is the argument with which the user specifies 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, they will write *G,* or F in the particular case of modifications to the editran/G profile referring to the parameters of the emission files\*.\* * c for changes referring to emission files, first modification is attempted, but if it fails, creation is attempted. * r\ is the argument that will be used to limit the sessions (if *P*has been written) 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*has been written) or presentations (if *G* or *F*), whose parameters are to be modified, that match the entered application code. It accepts the '\*' character as a wildcard, so 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*has been written) or presentations (if *G* or *F*) with the local code written after the "-l" identifier. 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 session(s) or presentation(s) match, or begin, in the case of using the '\*' character as a wildcard, with the literal entered after the "-s" or "-p" identifier. This argument must be consistent with the argument identified by "-o", the argument in which the option of the profiles to be modified is chosen. Thus, if in that argument you entered *P*, here you will write -s\ and if you wrote *G* or *F* now you will have to enter -p\. * m<-Exx=yy ...|-Ixx=yy ...|-Iorden=n ...> is the argument through which the user specifies 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 one, 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 emission file list. After that, the modification(s) to be made to the parameters of that file must be placed. * b is the argument by which it is identified that the profiles of one or several sessions or of one or several presentations are to be deleted. #### Modification of 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 described in detail in this user manual. If more than one parameter is to be modified, they should be placed one after another, separated by a space, and with quotes at the beginning and end of the series. In this case, the argument form 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\\\\" ...". With the exception of 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 corresponding to that argument will be modified. Once the command has been executed, the sessions or presentations being modified will be displayed 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 filtering by session name and presentation name, these being mandatory, and the only accepted arguments: -b -o\ -s\|-p\. Once the command has been executed, the sessions or presentations whose profiles are being deleted will be displayed on screen and at the end the number of sessions or presentations for which the task has been successfully completed. #### Application examples. Below are some examples of command use. 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 begins 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 begins 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 begins with '*PR*', with local code equal to *000011110* and with the 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 begins with '*PR*', with local code equal to *000011110* and with the 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 quotes 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 retry number 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 \\\\" 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** It will modify the field *reception destination* in the profile of all presentations, applying the value *.\destino* to that 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 *.\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 *reception destination* in the profile of all presentations whose remote code is *000002030* and whose application code begins with '*PR*', assigning it the value *.\destino*. * **modiperfi -oG -r203 -aPR\* -l1111 -m-Idstrec=.\destino** It 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 *.\destino*. * **modiperfi -oG -r000002030 -aPR\* -l1111 -pLOCAL -m-Idstrec=.\destino** It 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 *.\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 begins 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 quotes 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 list of emission files\*,\* 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"** It will modify the fields *file name* and *alphabet* in the first file in the emission file 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". **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 deregistered... EDITRAN TCP1 EDITRAN TCP2 EDITRAN TCP4 EDITRAN TCP5 4 presentations have been deregistered. --- # 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.2.1-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.