MSIR.0600 No requests found to debug for JAN(US)DEB(UG) command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
(Automatically generated page update)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
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.  
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.
<p class="note"><b>Note:</b> When using JANUSDEBUG, the request to be debugged must be started '''before''' the JANUSDEBUG command is issued.


[[Category:Sirius Mods Messages]]
{{Template:MSIR.0600 footer}}
[[Category:MSIR.0600 - MSIR.0799]]

Latest revision as of 23:33, 3 March 2017

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: When using JANUSDEBUG, the request to be debugged must be started before the JANUSDEBUG command is issued. Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages