> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/tips-miscellaneous/no-java-debug-console.md).

# There's no "Show Java Debug Console" option in my Lotus Notes client

The Show Java Debug Console menu is considered an Advanced Menu in Notes 8 and higher and if enabled, it is available under the Tools menu. Click on the below image for a bigger display.

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFmn-NSlJ2HRl2GU3B%2F-MlFmzz_emLv8-MTgj3P%2Fimage.png?alt=media\&token=3e5c79c4-4d11-4d56-9115-9bb8c99bf55b)

If you have Lotus Notes, Lotus Domino Designer® client and Domino Administrator client installed on your workstation, but the Show Java Debug Console menu does not appear in the Tools menu, then you need to enable the Advanced Menus by selecting View (1) -> Advanced Menus (2) in Notes (see below image). After that, the Show Java Debug Console menu will appear under the Tools menu as in the above image. 

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFmn-NSlJ2HRl2GU3B%2F-MlFn1KjRNCNlc2e60NG%2Fimage.png?alt=media\&token=cb917565-6743-4411-8879-b9a94d7f80ba)

If you have a Notes-Only installation on your workstation then the Advanced Menus are **not available** by default. In this case, the following parameter can be supplied in your notes.ini file which will enable access to advanced menu actions: MenusAdvanced=1

In Lotus Notes 6 or 7, the Show Java Debug Console menu is found in File > Tools > Show Java Debug Console.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.swingsoftware.com/pdf-converter-for-notes/tips-miscellaneous/no-java-debug-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.