MSIR.0600 No requests found to debug for JAN(US)DEB(UG) command: Difference between revisions
Jump to navigation
Jump to search
(Created page with "A JANUSDEBUG command was issued but there were no requests found that were accessible by the user who issued the command and that matched any qualifiers on the JANUSDEBUG command...") |
m (1 revision) |
(No difference)
| |
Revision as of 16:41, 9 November 2010
A JANUSDEBUG command was issued but there were no requests found that were accessible by the user who issued the command and that matched any qualifiers on the JANUSDEBUG command. The most common cause of this message is that a user is attempting to debug a public (no login required) request but the PUBLIC keyword was not specified in the JANUS WEB DEBUG rule for the URL. It is generally easiest to debug requests if a login is required, even if ultimately the requests will be public, since requiring a login makes it east to match up the web thread and the debugging 3270 thread -- they have the same userid.
Note that when using JANUSDEBUG, the request to be debugged must be started before the JANUSDEBUG command is issued.