> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/operacion/reduced-profile-management.md). # Reduced profile management Selecting option 3 from the General Menu or =3, from any submenu. This option is a creation with an abbreviated copy of the presentation and transmission profiles. In a normal situation, the session, the remote entity, and the application would have to be created. With this option, the main parameters are shown (the most common ones) of an image session to create all the records mentioned above in a single pass (the remote entity and/or the application may exist or not exist, in which case they are created). For use, it is recommended to create “templates” as an image to be created, covering all the transmission situations of an entity, so that when a creation is required, the appropriate template is used. Regardless of what is indicated, the program tries to generate a correct image, that is, a session with the same remote. In case of modification, consultation, or special needs, access it through the usual editran options. The screen that allows presentation sessions to be managed is shown: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 18:24:04 REDUCED PROFILE MANAGEMENT | ----------------------------------------------------------------------------- | ********************************************************************** | | * THIS OPTION QUICKLY CREATES SESSION RECORDS OF * | | * PRESENTATION-TRANSMISSION-APPLICATION-REMOTE FROM SESSION * | | * PRESENTATION IMAGE. THE VALUES ARE SIMPLIFIED AND THOSE THAT * | | * DO NOT APPEAR TAKE THE VALUES FROM THE IMAGE. * | | * IT IS RECOMMENDED TO CREATE IMAGE TEMPLATES WITH DEFAULT VALUES, * | | * FOR EXAMPLE, IN CASES OF T.CONNECTION-CRYPTOGRAPHY-BUFFERS-ETC AND * | | * THUS COVER DIFFERENT COMBINATIONS THAT AVOID MODIFICATION * | | * OF THE RECORDS CREATED LATER. * | | * IN ANY CASE, YOU CAN CREATE IT AND THEN MODIFY WITH * | | * OTHER OPTIONS ENABLED FOR THIS PURPOSE THE DESIRED PARAMETERS. * | | ********************************************************************** | | | | PRES. SESSION TO CREATE: IMAGE SESSION | | LOCAL CODE.......: 0 0009994 0 0 0009994 0 | | REMOTE CODE......: | | APPLICATION.........: | | | | | ----------------------------------------------------------------------------- ``` An image session can be selected, either generically or specifically. In the case of generic selection: By selecting from the previous screen, or by specifying the codes from the first screen: a single screen is accessed that manages the creation: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 18:26:43 REDUCED PROFILE MANAGEMENT | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | LOCAL CODE..: 0 0009994 0 REMOTE CODE.: 0 0009998 0 APPLICATION.: ****** | | S PRESENTATION SESSION DESCRIPTION VER CRI V.CRI APL.TRANS | | - -------------------------- -------------------- --- --- ----- --------- | | 000099940 000099980 ABEURC SES:000099980-ABEURC 5.2 S 4.0 ABEURC | | 000099940 000099980 ABEURP S 5.3 S 4.0 ABEURP | | 000099940 000099980 ABEUR3 S 5.2 N 4.0 ABEUR3 | | 000099940 000099980 AESRSA SES:000099980-AESRSA 5.2 N 4.0 AESRSA | | 000099940 000099980 AE9994 ISSUANCE OF DEBTS 5.0 S 3.0 AE9994 | | 000099940 000099980 AE9998 RECEIPT OF DEBTS 5.2 S 4.0 AE9998 | | 000099940 000099980 AR9994 FORWARDING ISSU. DEBTS 5.0 S 3.0 AR9994 | | 000099940 000099980 AR9998 FORWARDING RECEIPT DEBTS 5.2 S 4.0 AR9998 | | 000099940 000099980 AUTOPR S 5.2 N 3.0 AUTOPR | | 000099940 000099980 A00000 KI.EGDI.Y%Y%X%D.H%H 5.0 N 2.2 A00000 | | 000099940 000099980 CE9994 ISSU. BILATERAL CHEQUES 5.0 S 3.0 CE9994 | | 000099940 000099980 CE9998 RECEIPT BILATERAL CHEQUES 5.2 S 4.0 CE9998 | | 000099940 000099980 CONFIR SES:000099980-CONFIR 5.0 N 3.0 CONFI1 | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 18:27:36 REDUCED PROFILE MANAGEMENT | ----------------------------------------------------------------------------- | LOCAL CODE..: 0 0009994 0 REMOTE CODE.: 0 0009998 0 APPLICATION.EDI/G: COSITA | | FILE PARAMETERS.: | | ISSU.APPLICATION FILE.: KI.EIDA.F50 | | RECEIPT APPLICATION FILE.: | | MACRO FILE PARAMETERS: | | ISSU BUFFER-TYPE (E/M/P/C/D): ZTBPFEL C RECEIPT BUFFER-TYPE (E/M/C/D): ZTBPFRL C | | EXCI NETNAME...: BATCZTBG | | CONNECTION PARAMS: TYPE(I=TCP/IP,Y=PROXY): Y | | IP1: 172.022.242.195 07778 | | EDI/P APPLICATION: COSITA SESSION ALIAS...: 000099940000099980COSITA | | PRESENTATION PARAMS...: | | RECEIPT.TRANS.(A/E/N): E | |-----------------------------------------------------------------------------| | CRYPTOGRAPHY PARAMS...: CRYPTOGRAPHY...: S CRYPTO VERSION..: 4.0 | | ENCRYPTION ALG...: TD3C AUTHENTICATION ALG.: RSA | | LOCAL SUBSYSTEM.: 4 REMOTE SUBSYSTEM: 4 | | LOCAL CLASS: | | REMOTE CLASS: | | | ----------------------------------------------------------------------------- ``` The fields shown are the following: * **ISSU.APPLICATION FILE**: Issuance application file. Takes the value of the image session by default. It probably needs to be modified. Only one file is taken. If you want to transmit more than one, access the appropriate option. It is probably the only field that will not be useful to you and that you will have to modify, if you have selected an appropriate image. * **RECEIPT.APPLICATION FILE:** **Receipt application file**. Takes the value of the image session by default. It probably does not need to be modified if a model with a blank value or a value formed by variables has been taken. Recommendation: Take an image session with a remote code identical to the one you want to create, containing a name with variables; you will probably not have to change the receipt application file. * **MACRO FILE PARAMS**: Macro file parameters. Takes the value of the image session by default. It probably does not need to be modified if a valid model has been taken. Recommendation: Take an image session with parameters equal to the one you want to create; you will probably not have to change the receipt application file. * **ISSU BUFFER-TYPE**: Issuing buffer and type. Takes the value of the image session by default. In the case of specific buffers, you will find limitations. Recommendation: Take an image session with a remote code identical to the one you want to create, with matrix or exci issuing buffer. It probably does not need to be modified. * **RECEIPT BUFFER-TYPE**: Receiving buffer and type. Takes the value of the image session by default. In the case of specific buffers, you will find limitations. Recommendation: Take an image session with a remote code identical to the one you want to create, with matrix or exci receiving buffer. It probably does not need to be modified. * **EXCI NETNAME**: Takes the value of the image session by default. In the case of excii buffers, it assumes the value described there. Recommendation: Take an image session with a remote code identical to the one you want to create, with exci buffers. It probably does not need to be modified. * **CONNECTION PARAMS: TYPE**: The connection type field, if the remote exists, is protected; therefore, the session to be created requires that the image session have the same type. From this field on, others are protected: * **IP1**: Remote IP addresses and ports: If the connection type is not the correct one (valid values: Connection type P-I-Y), they are protected. If the connection type is correct, they are unprotected, the values from the image session are taken by default, and modification is allowed. Recommendation: Take an image session with a remote code identical to the one you want to create; you probably will not have to change the remote IP addresses. * **EDI/P APPLICATION**: Editran/P application. Only a single application is allowed. The Editran/G application to be created is set by default. * **SESSION ALIAS**N. An alias composed of local code + remote code + application is assigned by default (all values taken from the session to be created). * **RECEIPT.TRANS.(A/E/N)**: Translate on receipt (A/E/N). The value from the image session is assigned by default; however, this is not a protected field. Recommendation: Take an image session with a remote code identical to the one you want to create. It probably does not need to be modified. * Regarding the fields that refer to cryptography, they are protected. Recommendation: Take an image session with a remote code identical to the one you want to create. Probably, the same cryptography is used, so only the necessary ones are unprotected: Probably, if you have selected an appropriate image, you will hardly have to modify anything in the session you want to create; in most cases, the issuance application file. That is why the creation of different templates (images) is recommended, to cover all transmission situations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/operacion/reduced-profile-management.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.