> 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-ims-en/firma-electronica/funciones-interactivas-de-onesait-editran-ff/consulta-de-log-de-onesait-editran-ff.md). # Onesait Editran/FF log query This screen is accessed with option 1.1 of the Editran/FF menu. ``` ------------------------------------------------------------------------------ | DD/MM/YY SIGNATURE MANAGEMENT EDITRAN/FF | | HH:MM:SS LOG QUERY | ------------------------------------------------------------------------------ | | | | | | | LOCAL CODE : 0 9998 0 | | | | REMOTE CODE : 0 9994 0 | | | | APPLICATION : EDTRF* | | | | DATE (DD/MM/YY): / / | | | | TIME (HH:MM:SS): : : | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` This option allows you to query the messages generated by the file-signing processes. These messages are recorded in a cyclic file where each record is dated. If we do not enter any data on this screen, the query will show the most recent messages from the entire installation. To narrow the search, we can select by the date they were generated or by the application session with which they are associated. If we enter a date and time, the first messages recorded from that date onward are shown. If local code, remote code or application, or part of them, is entered (wildcards \* are allowed), the messages matching that pattern will be shown, plus the messages that, because they are general, were not recorded with any associated session. After pressing \, the query will be shown on the next screen. ``` 27/06/26 14:08:07 LOG QUERY EDITRAN/FF PRESENTATION SESSION DATE TIME SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 14:32:06 ZTBFBR10: 004-Info: No rule has been found that applies to the f SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:19:05 START OF SIGNATURE VERIFICATION IN XADES MODE SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:19:25 FILE VERIFIED CORRECTLY: DSN=KI.EGDI.R01 SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:19:25 SIGNATURE VERIFICATION COMPLETED SUCCESSFULLY SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:56:14 START OF SIGNATURE VERIFICATION IN XADES MODE SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:56:34 FILE VERIFIED CORRECTLY: DSN=KI.EGDI.R01 SIGNATURE VERIFICATION PROCESS. 000099980 000099940 EDTRF3 27/06/2026 16:56:34 SIGNATURE VERIFICATION COMPLETED SUCCESSFULLY FILE SIGNING PROCESS. 000099980 000099940 EDTRFF 14/02/2026 11:48:32 START OF THE SIGNING PROCESS IN XADES MODE FILE SIGNING PROCESS. 000099980 000099940 EDTRFF 14/02/2026 11:49:30 SIGNED APPLICATION FILE: DSN=KI.EGDI.SEPA.CAJA4.XML FILE SIGNING PROCESS. 000099980 000099940 EDTRFF 14/02/2026 11:49:30 DATA FILE SIGNING COMPLETED SUCCESSFULLY ``` Two lines are shown for each message. The first line shows the signing process (sending or receiving files), the associated Editran session, and the recording date. The second line shows the explanatory text of the message. --- # 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-ims-en/firma-electronica/funciones-interactivas-de-onesait-editran-ff/consulta-de-log-de-onesait-editran-ff.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.