Serenji from George James Software

Caché's built-in web-server does not support preserved sessions, so debugging with Serenji is not possible on this URL. Use a real web-server instead.
Debugging is #($S(IsActive:"",1:"not "))#currently active on this CSP session (job #($J)#) in namespace #($ZU(5))#.

A cookie is not maintaining session information (%session.UseSessionCookie=0). To start debugging a page in your application, first set a link to the target page and then click on that link. The target may include a relative or absolute path, but not an http://hostname prefix. The page will open in a new browser window.

Open a new browser window from this one and run your CSP application in it. This procedure is essential to ensure that your application is served by the same job that you have enabled debugging on. If you start another browser task (e.g. from your desktop) its CSP interactions will lie within another session and will not be intercepted by Serenji.

Alternatively, first set a link to the target page and then click on that link. The target may include a relative or absolute path, but not an http://hostname prefix. The page will open in a new browser window. This facility must be used to debug private pages or those that require encoded parameters.


#(..EscapeHTML(%request.Get("StartURL")))#

The CSP Preserve-mode of this session (%session.Preserve) is #(%session.Preserve)#. If your CSP app changes %session.Preserve during its operation then Serenji might disconnect, because some Preserve-modes do not keep devices open between requests.

#(ErrorText)#

#(ErrorText)#

This page was last updated at #($ZTIME($P($H,",",2)))#. To check whether the status of debugging reported above is still accurate, push this button:

Changes made to the following settings while debugging is active will not take effect until it is disabled and re-enabled. For advanced debugging the following fields can be modified before the Enable Debugging button is pushed.

IP address or hostname of Serenji target
Port on which Serenji Sentry is listening
Debug at all stack levels, including CSP framework?
Routines not to break in even though source is present

List one per line as name or prefix*

CSP Control Page version 2.3   Server-side Routines version #($P($$VER^%SerenjD," ",2))#