> 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/log-query-editran-ff.md). # Log query ยท Editran/FF This screen is accessed with option 1.1 of the Editran/FF menu (option 7 of the main Editran menu). ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN MANAGER | | 18:56:47 EDITRAN/FF LOG QUERY | ----------------------------------------------------------------------------- | | | | | | | | | LOCAL CODE.........: | | | | REMOTE CODE........: | | | | EDITRAN/G APPLICATION.: | | | | DATE (DD/MM/YYYY)...: / / | | | | TIME (HH:MM:SS)......: : : | | | | | | | | | | | | | ----------------------------------------------------------------------------- ``` This option allows you to query the messages generated by file signing processes. These messages are stored in a cyclic file where each record is dated. If no data is entered on this screen, the query will show the most recent messages from the entire installation. To refine 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 are shown. If local code, remote code or application, or part of them, is filled in (wildcards \* are allowed), the messages that match that pattern plus the messages that, because they are general, were not recorded with any associated session, will be shown. After pressing \, the query will be displayed on the next screen. ``` 19/06/2024 15:55:28 EDITRAN/FF LOG QUERY SESSION: ************************ DATE-TIME: **/**/****-**:**:** PRESENTATION SESSION DATE TIME ========================== ========== ======== FILE FORMATTING PROCESS. 000000000 000000000 000000 01/02/2024 11:11:51 ADAPTATION PROCESS NOT REQUIRED SIGNATURE VERIFICATION PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:12:07 START OF SIGNATURE VERIFICATION IN XADES MODE SIGNATURE VERIFICATION PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:12:32 ZTBFBR10: 016-Error checking rules. No rule has been met SIGNATURE VERIFICATION PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:12:33 ZTBFBR10: CHECK FILE ZTBFFSAL, ERROR EXISTS FILE FORMATTING PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:12:34 ZTBFBR12: ERROR: RECORD DELIMITERS DO NOT MATCH FILE SIGNING PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:14:10 START OF THE SIGNING PROCESS IN XADES MODE FILE SIGNING PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:14:10 ERROR GENERATING THE SIGNATURE FOR DSN=KI.EIDA.FFN43.TRANSFER.OK2 FILE SIGNING PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:14:10 ZTBFBE00: 097-Could not extract the certificate key from the store FILE SIGNING PROCESS. 000099990 V00099910 XADEST 01/02/2024 11:14:20 START OF THE SIGNING PROCESS IN XADES MODE EXIT, BACK, FORWARD ``` For each message, two lines are displayed. The first line shows the signing process (sending or receiving files), the associated Editran/G session, and the recording date. The second line shows the message explanatory text. --- # 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/log-query-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.