> 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/linux/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** of a menu-free administration mechanism suitable for unattended administration. With these commands the user can add, delete, and modify presentations **editran/G** and sessions **editran/P**. The purpose of this document is to guide the user in 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.*\*\* Also those persons in charge of administering **editran** in unattended mode. ### Definitions * **command file**: A file that contains commands to perform administration operations. * **command**: An expression of the form "a = b" that indicates a basic action to take. Also called a parameter. * **operation**: A set of commands that constitute an add, a delete, or a modification for **editran**. ### Related documents The documents that can supplement this one are: * "**editran/P** *User Manual"*. Contains information related to administration of the editran/P system. It is useful for understanding the semantics of the administration operations carried out with the software to which this manual belongs. * "**editran/G** *User Manual"*. Contains information related to administration of the editran/G system. It is useful for understanding the semantics of the administration operations carried out with the software to which this manual belongs. ## Add Profiles ### 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 that make 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 will consist 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, the following commands must be written. **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 stating 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 short, these lines must appear before any others in each operation to be performed. With the above commands we have indicated that we want to perform an add, delete, 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 until the end of the operation will refer exclusively to that session or presentation. If *op* had been "B", we would be requesting a deletion. In this case it would not have been necessary to specify any more commands. For an add 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 display an error message. The following table shows how to add, delete, and modify: *** | Operation | Command | | ------------ | ------------- | | Add | OPERATION = A | | Delete | 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 blank spaces and empty lines in the input file, but there may only be one blank space between words that identify a profile field. For example: ``` CODE LOCAL = 9991 ``` This is wrong because there are three spaces between CODE and LOCAL. There should be only one blank space. As an example, we will mention the minimum operations to perform adds, deletes, and modifications. **To perform an add in editran/P we will do:** ``` OPERATION = A PROFILE = EDI SESSION = EXAMPLE REMOTE CODE = 1234 APP = PRUEB1 ... %%= ``` **To perform an add in editran/G we will do:** ``` OPERATION = A PROFILE = IGA PROFILE TYPE = P PRESENTATION = EXAMPLE REMOTE CODE = 1234 APP = PRUEBA ... %%= ``` **To perform an add of an output file for the previous presentation in editran/G we will do:** ``` OPERATION = A PROFILE = FILE PRESENTATION = EXAMPLE FILENAME = pruebas.dat ... %%= ``` **To perform an add of the local editran/P profile we will do:** ``` OPERATION = A PROFILE = LOC LOCAL CODE = 1234 ... %%= ``` In place of the ellipses, the values of the different fields are indicated (which will be described later). It should be noted that, in the case of an add, those fields that are not specified will take the default value, if this is possible. If the field contains information essential to add the session, such as not having specified the REMOTE CODE or the APPLICATION, the program will complain, generating the error message appropriate to the particular situation. There are fields that do not admit a default value but that do not contain information essential to add the session, such as, for example, REMOTE NRI. In such cases the field will remain unfilled (and it will be necessary to resort to a later profile modification operation, either through the menu or by using the appropriate command again). **To perform a deletion in editran/P (that of editran/G is similar except that a presentation is specified, not a session) we will do:** ``` OPERATION = B PROFILE = EDI SESSION = EXAMPLE %%= ``` **To delete one 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 = MODIFICATION TEST. %%= ``` In a modification, those fields that are not specified will retain their value. Below, we indicate the different parameters that can be in a command, as well as the values they can take. Before starting the list, it is worth noting a couple of details. First, it should be said that the names of each parameter 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 removed that were not essential to identify the field and that only led to having to type longer parameters, with the possibility of making some typing error. It is therefore advisable to keep this manual nearby until you become familiar with the exact name of each parameter. Second, it is necessary to note 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 of the parameters corresponds to. If you are not, you should consult the corresponding user manual. ### Commands for the local profile of Onesait ยท Editran #### Operation * **Description:** Type of operation to perform. * **Values:** A (add) or M (modification). * **Example:** OPERATION = A #### Profile * **Description:** Identifies that the operation will be performed on the local profile of editran/P\*.\* * **Values:** LOC (*LOCAL*). * **Example:** PROFILE = LOC #### Local Code * **Description**: It is the identification code of the local center. * **Values**: A number of up to 9 digits. If fewer digits are specified, it will be formatted accordingly. * **Example**: LOCAL CODE = 9991 #### Local name * **Description**: Descriptive name of the local entity. * **Values**: Alphanumeric string. * **Example**: LOCAL NAME = PC 23 #### Max sessions number * **Description**: It is the number of connections that can be active simultaneously. * **Values**: A number between 1 and 100. * **Example**: MAX SESSIONS = 10 #### Local IP address * **Description:** IP address of the local center. This parameter can be repeated up to three times. * **Values:** IP address or machine name in a domain. * **Example:** LOCAL IP ADDRESS = 140.30.5.3:7778 #### TCP Connection 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:** Type of operation to perform. * **Values:** A (add), 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 center for the session being defined. * **Values:** A number of up to 9 digits. If fewer digits are specified, the field will be properly formatted. * **Example:** LOCAL CODE = 7778 #### Local name * **Description:** Descriptive name of the local entity in the session being defined. * **Values:** Alphanumeric string. * **Example:** LOCAL NAME = MY PC #### Remote code * **Description:** It is the identification code of the remote center. * **Values:** A number of up to 9 digits. If fewer digits are specified, it will be formatted accordingly. * **Example:** REMOTE CODE = 9991 #### Remote name * **Description:** Descriptive name of the remote entity. * **Values:** Alphanumeric string. * **Example**: REMOTE NAME = CICS1 #### App * **Description:** It is the code that identifies the application. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APP = PRUEBA #### App name * **Description:** Descriptive name of the editran/P application. * **Values:** Alphanumeric string. * **Example:** APP NAME = PRUEBA #### Access ID * **Description:** Identifier that complements the ORIGIN-DESTINATION-APPLICATION tuple, containing a key used during the connection representing the DESTINATION of the incoming request. Numeric from 0 to 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 (only me), R (the remote), and X (anyone). In connections via PAD, the call is only allowed from the local end, since there is no reverse mechanism for addressing the PAD toward the modem. * **Example:** CALLING END = X #### Traffic direction * **Description:** Which direction the traffic goes. * **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, in which editran/P expects to receive from the remote a response message to one of the controls 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 expects to receive from the remote the response message to the data transmission synchronization message. * **Values:** A number of up to 3 digits. * **Example:** TIME OUT = 30 #### Retries * **Description:** maximum number of retransmission retries. * **Values:** A number. * **Example:** RETRIES = 3 #### Save rotations * **Description:** Whether remote addresses should 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 side. * **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 in the window during 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 in the window during 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 in the buffer files. * **Values:** Values between 252 and 4050. * **Example:** BUFFER LENGTH = 4050 #### Transmission processes * **Description:** Identifies the process responsible for the pre- and post-transmission phases. * **Values:** editran/G *or* editran/SW\*.\* * **Example:** TRANSMISSION 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 for 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 the auxiliary keys. Only available with 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 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 twice. * **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 access gateway to the SWIFT network. * **Values:** S or N. * **Example:** USE SWIFT GATEWAY = N ### Commands for editran/G #### Operation * **Description:** Type of operation to perform. * **Values:** A (add), B (delete) or M (modification). * **Example:** OPERATION = A #### Profile * **Description:** Identifies whether the operation will be performed on a Presentation or a File in 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 entity for the presentation being defined. * **Values:** A number of up to 9 digits. If fewer digits are specified, the field will be properly formatted. * **Example:** LOCAL CODE = 7778 #### Local name * **Description:** Descriptive name of the local entity in the presentation being defined. * **Values:** Alphanumeric string. * **Example:** LOCAL NAME = MY PC #### Remote code * **Description:** It is the identification code of the remote center. * **Values:** A number of up to 9 digits. If fewer digits are specified, it will be formatted accordingly. * **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 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:** 2.2, 3.0 or 4.0 * **Example:** CRYPTOGRAPHY VERSION = 3.0 #### Confidentiality * **Description:** Algorithm used to encrypt 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 side. It should correspond to the one indicated in the associated editran/P session. It is only used with remotes with version lower than 5.0. * **Values:** A (ASCII) or E (EBCDIC). * **Example:** ASCII/EBCDIC = E #### APPL * **Description:** It is the application code. * **Values:** Alphanumeric string of exactly 6 characters. * **Example:** APP = PRUEBA #### Application 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 character values to be modified before sending. * **Values:** Alphanumeric string with a maximum length of 15. * **Example:** EMISSION CONVERSION TABLE = tablaemi #### Reception conversion table * **Description:** Name of the file containing the character values to be modified after reception. * **Values:** Alphanumeric string with a maximum length of 15. * **Example:** RECEPTION CONVERSION TABLE = tablarec #### PRV sending * **Description:** Name of the user automatism prior to sending. * **Values:** The name of an executable. * **Example:** PRV SENDING = U\_PRVEMI #### PRV reception * **Description:** Name of the user automatism prior to reception. * **Values:** The name of an executable. * **Example:** PRV RECEPTION = U\_PRVREC #### PST sending * **Description:** Name of the user automatism after sending. * **Values:** The name of an executable. * **Example:** PST SENDING = U\_PSTEMI #### PST reception * **Description:** Name of the user automatism after reception. * **Values:** The name of an executable. * **Example:** PST RECEPTION = U\_PSTREC #### Exception * **Description:** Name of the user automatism in case of exception. * **Values:** The name of an executable. * **Example:** EXCEPTION = U\_EXCEPT #### Presentation session increment * **Description:** Indicates whether the presentation session identifier should be incremented. * **Values:** S or N. * **Example:** PRESENTATION SESSION INCREMENT = S #### Load type * **Description:** The load type can be Normal or Cumulative. * **Values:** N or A. * **Example:** LOAD TYPE = N #### Number of EDI sessions * **Description:** Number of editran/P sessions for a presentation. * **Values:** A number between 1 and 20. * **Example:** NUMBER OF EDI SESSIONS = 3 #### EDI APPL * **Description:** Application *e*ditran/P to use for this presentation. This field will be repeated as many times as editran/P sessions we want to specify, up to a maximum of 20. * **Values:** The name of an editran/P application. * **Example:** EDI APPL = PRUEBA #### 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 during file download. * **Values:** E (translated to *EBCDIC* those arriving in *ASCII*). A (translated to *ASCII* those arriving in *EBCDIC*). N (not translated). * **Example:** TRANSLATE ON RECEPTION = N #### Delimiter on reception * **Description:** Delimiter to use in the download of Fixed 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 #### Confirm download * **Description:** With this option, sent items are not considered complete until the notification from the remote side is received with the result of their download. * **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 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 wildcard characters. * **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 up to five digits. * **Example:** RECORD LENGTH = 80 #### Delimiter * **Description:** Delimiter used when loading files with Fixed format. * **Values:** N (None), D (DOS) and U (UNIX). * **Example:** DELIMITER = N #### Compression * **Description:** Use of file compression. * **Values:** F (compression is used) or N. * **Example:** COMPRESSION = F #### Alphabet * **Description:** Character set selector for the files to be sent. * **Values:** E (*EBCDIC*), A (*ASCII)* or N (*None*). * **Example:** ALPHABET = A #### Translate * **Description:** Translation selector between character sets. * **Values:** S (translated to *EBCDIC* if ALPHABET is A or to *ASCII* if ALPHABET is E). N (not translated). * **Example:** TRANSLATE = N ### Configuration update The command ***cfgupt*** is responsible for carrying out this task. It is responsible for interpreting command files and options on the command line. In addition, it allows dumping sessions **editran/P** and **editran/G** to a text file using the command syntax described above. It is usually invoked to: * get help * run a command file * run commands that we provide as arguments * dump sessions to a text file. #### Help In its first facet, when we invoke it as ***cfgupt -h*** it tells us how to use it, and when we invoke it as ***cfgupt -H*** it also tells us about the possible parameters 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 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 the file . -e: use 'cmd' as the interpreter for -E options -i: use 'cmd' as the interpreter for -I options -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) and can be mixed. op=A or B or M must be specified depending on whether it is an add, delete, or modify. profile=EDI or profile=IGA must also be specified depending on whether an editran/P or editran/G profile is being modified. Several operations can be specified. An operation must be of the form: -Eop=X -Eprofile=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 | | appl | APPL | | authentic | AUTHENTICATION | | auto | AUTOMATIC CALL | | autodisc | AUTOMATIC DISCONNECTION | | ckey | KEY CHANGE | | encryption | CRYPTOGRAPHY | | loccode | LOCAL CODE | | remcode | REMOTE CODE | | compress | COMPRESSION | | conn | CONNECTION TYPE | | confidential | CONFIDENTIALITY | | crc | CRC | | key management | KEY MANAGEMENT | | accessid | ACCESS ID | | locip | LOCAL IP ADDRESS | | proxyip | PROXY IP ADDRESS | | remoteip | REMOTE IP ADDRESS | | loclabel | LOCAL KEY LABEL | | remlabel | REMOTE KEY LABEL | | caller | CALLING END | | appname | APP NAME | | locname | LOCAL NAME | | remname | REMOTE NAME | | op | OPERATION | | profile | PROFILE | | sendprocs | SEND PROCESSES | | recvprocs | RECEIVE PROCESSES | | proxy | EDItran PROXY | | burst | SEND BLOCK | | retries | RETRIES | | rotate | SAVE ROTATIONS | | trafficdir | TRAFFIC DIRECTION | | serverclient | SERVER/CLIENT | | session | SESSION | | appsync | APP SYNCHRONIZATION | | use swift gateway | USE SWIFT GATEWAY | | buffer | BUFFER LENGTH | | endtime | END TIME | | timeout | TIME OUT | | starttime | START TIME | | disc timeout | DISCONNECTION TIMEOUT | | sync timeout | SYNCHRONIZATION TIMEOUT | | validateip | VALIDATE REMOTE IP | | encryptionversion | CRYPTOGRAPHY VERSION | | remversion | VERSION NUMBER | | | | | The values that xx can take in -Ixx=yy are: | | | ------------------------------------------- | -------------------------- | | ackload | CONFIRM DOWNLOADS | | alphabet | ASCII/EBCDIC | | filealphabet | ALPHABET | | ediapp | EDI APPL | | appl | APPL | | authenticate | AUTHENTICATION | | load | LOAD TYPE | | encryption | CRYPTOGRAPHY | | localkey | LOCAL LABEL | | remotekey | REMOTE LABEL | | loccode | LOCAL CODE | | remcode | REMOTE CODE | | compress | COMPRESSION | | confidenc | CONFIDENTIALITY | | senddelimiter | DELIMITER | | recvdelimiter | DELIMITER ON RECEPTION | | split | SPLIT CRITERION | | recvdest | RECEPTION DESTINATION | | signcheck | CHECK SIGNATURES | | format | FORMAT | | key management | KEY MANAGEMENT | | incses | PRES SESSION INC | | recordlen | RECORD LENGTH | | appname | APPLICATION DESCRIPTION | | file name | FILE NAME | | locname | LOCAL NAME | | remname | REMOTE DESCRIPTION | | number of sessions | EDI SESSIONS NUMBER | | op | OPERATION | | order | FILE ORDER | | profile | PROFILE | | present | PRESENTATION | | previous emission | PRE-EMISSION | | previous reception | PRE-RECEPTION | | post emission | POST-EMISSION | | post reception | POST-RECEPTION | | emission table | EMISSION CONVERSION TABLE | | reception table | RECEPTION CONVERSION TABLE | | type | PROFILE TYPE | | translate | TRANSLATE | | translate reception | TRANSLATE ON RECEPTION | | user exception | EXCEPTION | | encryptionversion | CRYPTOGRAPHY VERSION | | remote IGA version | VIEW REMOTE IGA | | | | | The 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, on the other hand, we want to execute commands from files, we will 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 specification 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 add the session EJEMPLO and then remove it. When specifying operations on the command 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 command line. As an example of the previous 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) APPLIC = 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 sessions file. It is also possible to dump the contents of editran/P and editran/G sessions to a text file. The generated file syntax 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 editran/P and editran/G configuration files (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 be dumped. "-ae" dumps the local profile and all editran/P sessions; "-ai" dumps all editran/G presentations. Both options can be specified at once or even in a single expression "-aei". > > -l: specifies that the local profile 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's 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 #### Tips As is usually the case, there are certain tricks that may be useful. One of them is to use the "-e" and "-i" options of ***cfgupt***. The option "-e" allows you to specify which program will be responsible for executing operations for editran/P administration (normally ***ediperfi***). The option "-i" allows you to specify which program will be responsible for executing operations for editran/G administration (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 >DUMP ``` after which, an invocation `>cfgupt -edump -Eop=B -Eperfil=EDI -Esesion=EJEMPLO`\ will leave in the DUMP file a command file equivalent to the options we have indicated. ### Errors The 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 all 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 Input Command. > > Usage: ediperfi \[-h] \[-f\] > > \[-r {\[-a \[-V\] \[-R\] \[-n]] | \[-l] | \[-s\]} \[-o\]] > > -h: help (this one) > > -f\: name of the file with profile modification commands. (default=stdin) > > modification > > -r: dump of editran sessions to a file. > > -s\: editran session to dump. > > -a: dump of all sessions and the local profile to a file. > > -l: dump of the local profile to a 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 with the syntax of ***cfgupt***, the usage examples for this one are practically directly applicable (restricted, of course, to the options available in ***ediperfi***). ### editran/G profiles The command ***igaperfi*** is responsible for interpreting (and executing) editran/G administration operations. Its syntax is as follows: > igaperfi: Unattended editran/G Profile Input Command. *editran/G*. > > Usage: igaperfi \[-h] \[-f\] > > \[-r {\[-a \[-V\] \[-R\]] | \[-s\]} \[-o\]] > > -h: help (this one) > > -f\: name of the file with profile modification commands. (default=stdin) > > modification > > -r: dump of editran/G presentations to a file. > > -s\: editran/G presentation to dump. > > -a: dump of all presentations to a file. > > -R\: Release of the file to dump. > > Valid values for \ 1..8 > > -V\: Version of the file to dump. > > Valid values for \ 30, 31, 40, 41, 50 and 51 > > -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 practically directly applicable (restricted, of course, to the options available in ***igaperfi***). It should be noted that with both ***igaperfi*** and 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 allows portability of configuration files when editran Software updates are needed. Updates to higher versions could cause the old configuration files to be incompatible with the new installation; to preserve the starting configuration we will use the commands with the options **-V** and **-R** discussed in previous sections and which allow us to recover in text format the profiles defined for other editran versions. It should be noted that using the commands to update profiles from earlier versions is intended as help during the installation process, so it has some restrictions, which we comment on below. 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 some changes before generating the new configuration files. In addition, it is advisable that recovery of the old profiles be done when profile files for the new installation do not yet exist. Below, the steps to follow are discussed with an example in which the editran profiles Ver. 4.1 Rel. 7 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 starting 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 to the command file *profiles.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 -fprofiles.txt \> igaperfi -fprofiles.txt Generate the profile files of 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. We will explain some practical cases of these situations: * Profiles that, by mistake, may have been registered in earlier versions and that are validated in this version. * If the version update implies a change in the supported protocol, for example, if moving from an X.25 version to a TCP/IP version, the user must modify the parameters of the sessions that depend on the network layer. For example, in this case, the new LOCAL IP ADDRESS and REMOTE IP ADDRESS values would have to be assigned. Migration aspects related to Cryptography: * the file **ckds.des** from the old installation must be copied into 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 that 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 of **editran/G** is a menu-unguided administration mechanism suitable for unattended administration. With this command the user can simultaneously modify as many parameters as desired in multiple sessions **editran/P** or in different presentations *editran/G,*\*\* as well as deregister the profiles. ### How to use The command ***modiperfi*** is based on the repeated use of the command ***cfgupt*** in the profile modification and deletion modes of editran/P or in the profile modification and deletion modes of editran/G. This thus adds the possibility of modifying the parameters of more than one session or more than one presentation on a single command line, or of deregistering 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 will specify whether they want to modify/deregister the editran/P profiles, in which case they will write *P* after the identifier "-o", if they want to modify/deregister the editran/G profiles, writing in this case *G,* or F for the special case of modifications in the editran/G profile referring to emission file parameters\*.\* * *c* for changes referring to emission files, first modification is attempted, but if that fails creation is attempted. * r\ is the argument that will be used to limit the sessions (if *P*was written) *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 with which the sessions (if *P*was written) *G* or *F*) whose parameters are to be modified will be filtered, matching the entered application code. It supports 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*was written) *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 modify/deregister, 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 modify is chosen. Thus, if in that argument *P*, here you will write -s\ and if *G* or *F* was written, now you will have to enter -p\. * 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 option *P*, *G* or *F*is chosen. 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 identifying 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 used to identify that the profiles of one or more sessions or one or more presentations are going to be deregistered. #### Modification of editran/P and editran/G profiles This command usage option allows filtering, in each case, according to four profile parameters. The way to do this, in each case, is the same as that used in the command ***cfgupt*** and is extensively detailed 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 quotation marks at the beginning and end of the series. In this case the form of the argument would be: -m"-Exx=yy -Exx=yy -Exx=yy ..." or -m"-Ixx=yy -Ixx=yy -Ixx=yy ...". If the value 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 others are optional. When an argument does not appear, it will not be filtered according to that parameter and all sessions or presentations will be modified with respect to that argument. 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 usage option allows filtering by session name and presentation name, both of which are mandatory and the only permitted arguments are: -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 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, applying the value *31* to that field in all of them. * **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 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 the 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 the session name *LOCAL*, assigning them the value *31* and *TCP001* respectively. As can be seen, when more than one *-Exx=yy* is entered, a space must be added between each one and the next as well as quotation marks at the beginning and end of the series. * **modiperfi -oP -r000002030 -m"-Eversrem=31 -Eaplic=TCP001 -Ereint=3"** Will modify the version, application code and maximum retry count 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=\\"Application 2023\\"" Modifies in the session *PRUEBA* the field *application name* assigning it the value *Application 2023*. Note that the new application name has been delimited with the characters \\" since it contains spaces. **Deletion of editran/p profiles** * **modiperfi -b -oP -sE\*** Will deregister 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 applying the value *.\destino* to that field in all of them. * **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 with 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 *.\destino*. * **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 *.\destino*. * **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 *.\destino*. * **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 more than one *-Ixx=yy* is entered, a space must be added between each one and the next as well as quotation marks at the beginning and end of the series. * **modiperfi -oF -r203 -aPR\* -l000011110 -pLOCAL -m"-Iorden=1 -Inomfich=nuevo.c"** 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 you want to specify 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 in the list of emission files in 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 the 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 the 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 the 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 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.2.1-en/linux/gestor_perfiles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.