> 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/electronic-signature/graphical-interface/applications-presentation-sessions/general-application-parameters.md).
# General application parameters
## Presentation session
We register the presentation in option 7.2.3.1 (it is necessary that it exists in editran/G).
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN/FF ADMINISTRATOR |
| 18:59:34 PRESENTATION SESSION |
-----------------------------------------------------------------------------
| |
| A ---> ADD |
| |
| B ---> DELETE (PRESENT. SESSION AND ALL ITS ASSOCIATED RECORDS) |
| |
| C ---> QUERY |
| |
| M ---> MODIFY |
| |
| R ---> CREATE WITH COPY (SESSION RECORD AND POSSIBLE ASSOCIATED RECORDS) |
| |
| |
| |
| OPTION.......: C |
| LOCAL CODE.: 0 0009994 0 |
| REMOTE CODE: |
| APPLICATION...: |
| |
| |
-------------------------------------------------------------------------------
```
If a generic selection is made, the following screen will appear:
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN/FF ADMINISTRATOR |
| 19:00:05 PRESENTATION SESSIONS |
-----------------------------------------------------------------------------
| LOCAL CODE..: 0 0009994 0 REMOTE CODE.: * ******* * APPLICATION.: ****** |
| EMI OCS TIP ATT TEMPLATE |
| S PRESENTATION SESSION REC CRL SIG DET POLICY FTO LRECL TRA C |
| - ------------------------ --- --- --- --- ---------------- --- ----- --- - |
| 000099940A00099940EDTRFF E N P D F 00080 N N |
| 000099940A00099940EDTRF1 E N X A F 00080 N N |
| 000099940A00099940EDTRF2 E N P D pln-di-i-BES.xml F 00080 N N |
| 000099940A00099940EDTRF3 E N X A F 00080 N N |
| 000099940A00099940EDTRF4 E N X A F 00080 N N |
| 000099940A00099940EDTRF5 E N X A F 00080 N N |
| 000099940A00099940ESTEFF E N X A F 00080 N N |
| 000099940A00099940NORMA1 E N X D F 00080 N N |
| 000099940A00099940NORMA2 E N X A F 00080 N N |
| 000099940A00099940NORMA3 E N X A F 00080 N N |
| 000099940A00099940NORMA4 E N X A F 00080 N N |
| 000099940A00099940NORMA5 E N X A F 00080 N N |
| 000099940A00099940NORM20 E N X A F 00080 N N |
| QUERY PERFORMED. |
| EXIT, ADVANCE, SELECT |
-----------------------------------------------------------------------------
```
We select one of the rows.
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN/FF ADMINISTRATOR |
| 19:00:16 PRESENTATION SESSION |
-----------------------------------------------------------------------------
| USER:CICSSITD F-H:20210700-060300 |
| CGO LOCAL..: 0 0009994 0 CGO REMOTE.: A 0009994 0 APPLICATION.: EDTRFF |
| GENERAL PARAMETERS |
| APPLICATION TYPE (E/R).........: E |
| OCSP/CRL VERIFICATION (N/O/C/A)..: N |
| SIGNATURE TYPE (P/X)..............: P SIGNATURE MODE (A/C/D): D |
| XADES SIGNING TEMPLATE......: |
| XADES SIGNATURE VERIFICATION POLICY: |
| NAME OR DIRECTORY OF THE SIGNATURE FILES: |
| /u/edixd/firmas/ |
| DELETE IF IT EXISTS (Y/N).......: S ADAPT DOWNLOADED FILE (Y/N): N |
| PHYSICAL APPLICATION FILE NAME (DSN) .........: |
| |
| FORMATTING PARAMETERS FOR DOWNLOADED RECEIVED FILES: |
| DOWNLOAD FILE FORMAT (F/V/E): F RECORD LENGTH (1-32756)..: 00080 |
| RECEPTION TRANSLATION (A/E/N)...: N RECEPTION CONVERSION TABLE...: |
| REMOVE CARRIAGE RETURNS (Y/N): N RETURNS TO REMOVE IN HEXADEC.: |
| |
| EXIT |
-----------------------------------------------------------------------------
```
* **APPLICATION TYPE** (E/R): it can be sending or receiving.
* **OCSP/CRL VERIFICATION (N/O/C/A)**: verify whether certificates are revoked by accessing an OCSP server or by CRL (revocation list).
* **SIGNATURE TYPE (P/X)**: Indicates whether the signature follows the PKCS#7 standard (*Public-Key Cryptography Standards*) or the XAdES standard (*XML Advanced Electronic Signatures,* up to the XAdES - EPES protection level).
* **SIGNATURE MODE (A/C/D)**: Allows you to choose whether the signed data and the signature will be in the same file or in separate files. With Attached format the signature is contained in the signed file; with Detached the signature of each user will be contained in a signature file. Mode C is the one that implements the format chosen by Iberpay for the XAdES signature type.
* **XADES SIGNING TEMPLATE**: only for XAdES sending applications, indicates which XAdES signature template should be applied to the signatures of this application. If that template specifies a policy, the generated signatures will be XAdES-EPES type; if the template does not indicate that feature or if no template is specified, the signature will be XAdES-BES type. (\*)
* **XADES SIGNATURE VERIFICATION POLICY**: only for XAdES receiving applications, indicates the XML file that contains the policy with which the application's signatures must be validated. If specified, the signatures will be XAdES-EPES; otherwise they will be XAdES-BES. (\*)
* **NAME OR DIRECTORY OF THE SIGNATURE FILES**: specifies the name of the HFS file or USS directory that will contain the signatures. If the signature mode is Detached, only the name of a directory may be specified; the signature file will be called (within that directory) the same as the data file to be signed plus the corresponding extension for the signature type, “. xsig” or “. p7b”. When the signature is attached, a file name can be specified (which will contain the data and the signatures) following the rules used in editran/G. In this case, if a directory is entered, it will proceed as in Detached mode. It should be noted that the generated name must not exceed 44 characters in order to be sent by editran if the remote version is lower than 5.2.
The following parameters only apply to file reception.
* **DELETE IF IT EXISTS (Y/N)**: Allows the formatted file to be deleted if it exists.
* **ADAPT DOWNLOADED FILE (Y/N)**: Indicates that the received file is going to be formatted after signature verification.
* **PHYSICAL APPLICATION FILE NAME (DSN)** (Reception only) This is the name of the final destination of the received files. Because signed files cannot be translated or formatted, a process after signature verification will convert the original file into another transformed one. The file name must match the one included in the second editran/G session screen (option 2.3.4 of the editran general menu)
* **DOWNLOAD FILE FORMAT (F-V-E)**: (Fixed/Variable/Expanded): The formatted file will have fixed, variable, or expanded variable record format (RECFM=FB, VB or VS).
* **RECORD LENGTH (1-32756)**: Size of the record in the formatted file.
* **RECEPTION TRANSLATION (A-E-N):** Indicates the alphabet in which the formatted file is desired if it is translated.
* **RECEPTION CONVERSION TABLE:** Indicates the editran character conversion table that is applied to the file once translated.
* **REMOVE DELIMITERS (S/N)**. RECORD DELIMITER (HEXADECIMAL): Allows the delimiters placed by ASCII machines in text files to be removed. The hexadecimal values to be removed will be indicated. For a DOS file the delimiter is usually x’0D0A’ and for a UNIX file x’0A’. The characters will be removed in any position in the file because the filter is applied to an unformatted file. It should not be applied to files that are not text files. Once the sending of signed XML files comes into force, the formatting parameters for received files will not be necessary.
(\*) Only the name of the document is specified, which must reside in the “templates” / “policies” directory of the installation in USS. These directories will be created when the Java server is installed and contain the documents that allow signatures to be created and verified according to AGE criteria (*General State Administration*).
With signature mode ‘C’, the template to specify is: pln-di-e-unfich-BES.xml.
Any other template/policy that is to be used must be included in these directories.
---
# 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/electronic-signature/graphical-interface/applications-presentation-sessions/general-application-parameters.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.