These warnings suggest a performance problem with the CPU and disk bottlenecks. 

If you are running very intensive processes, you should see these warnings go away after they finish. However, if you keep seeing them continuously, I recommend going deeper and analyzing the performance. 

Analyzing the performance takes time, and it's not always easy for non-experts. There is a great series of articles written in this community that can help with this: 

https://community.intersystems.com/post/intersystems-data-platforms-capa...

If you don't want to go through all these series and can easily increase the system resources, it would be an easy way to probe and solve the problem ;-). What I mean by increasing system resources is by adding more CPUs and faster disks. Nowadays, with Virtual machines and cloud systems, this is quite simple. 

And let me insist again, if this is a production system, you may want to open a WRC problem for extra help. Having the disk too stressed will end in User/Application pauses. 

As it is not a class method you need either to create/open an object for the class or rewrite the method as ClassMethod (instead of Method). But as the SetSensor call is also pointing to the same object (See do ..SetSensor), the simplest would be to create/open the object:

set obj=##class(Package.YourClass).%New()
do obj.ResponseTimeCurrentMonth("USER")

You may also need to add some Writes to the terminal to see something. For example:

write  !,"Date:",InDate
write  !, "time taken:",timeTaken


    

Hi Andy, 

If you have problems with production servers, I advise contacting Support directly. (Looking at the question's date, you may have contacted us already).

The issue you show here is not common and can be related to file permissions (reinstalling may help) or a product bug. To diagnose the problem, Support may need to ask you for more details, logs, etc. 

I am a little surprised you asked this :-P ..... and the answer, as you can imagine, is using the magical $Z functions! 

In this case, searching a little you can find: 

$ZISWIDE (ObjectScript)

Checks whether a string contains any 16-bit wide characters. 

See: 

https://docs.intersystems.com/iris20221/csp/docbook/Doc.View.cls?KEY=RCO...

I think playing with other functions could give you what we are looking for here.

Therefore, now that we have a utility that can check if something is Unicode or not, the rest would be to do a routine to read all the globals and check for the content with this function. I have seen routines getting all the globals and looping before but don't have it handy.

This programmatic way of looping and checking all the globals gives you more control and allows you to find where there is something not expected. But, as it takes some time to write if the original question is something you just want to do once, a backup + restore seems quicker and simpler.

There isn't any flag telling whether a database is Unicode or not inside the database file. If a Unicode database has no UNICODE characters, it will be accessible by an 8-bit version without problems. 

If you want to know if a database has wide characters (Unicode chars), you could try to read all the globals inside an 8-bits instance and wait for a <WIDE CHAR> error. In order to read all the globals, there are several alternatives, like building a small routine, doing a backup and/or restore, exporting/importing globals, etc. Of course, there are more elegant ways to check the globals and data than expecting an error. 

Kevin, 

You should run it over the weekend, if the system is busy, the operation may take longer or not fully complete. 

See notes from the documentation: 

Compacting a Database

The compact database operation is designed to run concurrently with normal database activity. The operation does consume some system resources, however, and may not complete if the system is under extremely high load. For these reasons, InterSystems recommends running this and other database reorganization operations (including compacting and defragmenting globals) during off-peak hours, and running only one such operation on a system at a time.

Hola Hector, 

Maybe another javascript error is causing the problem and that's why you are not reaching to the console.log line. 

In order to find the problem I would keep simplifying the page, remove code from above, down, etc... until it works. Being a CSP page is not affecting, as the output seen by the browser would be html. 

Another tip would be ti open the console window and checking for other errors. Also look at the code from the browser, not the one from the server. That will give you where the problem is. 

If you keep getting problem, even after simplifying the page, please paste it here so I can have a look and try to reproduce it locally. Of course if this becomes something urgent, you should open a WRC problem with support. 

Jose Antonio, 

I am not sure to understand what you are trying to do. When you use the SQL Gateway connections you will map an external table into one particular namespace. If you have several, you will have several different table names in several namespaces. 

 Then you can use those table names in your SELECT FROM queries, you will need to move to the particular namespace before launching the query (using ZN)

If I understand correctly, the main problem is that the tablepane loses the focus once the PDF is loaded. So the idea is to give it back. 

 - First of all, you need to set the tablepane to work with the arrow keys (probably you already have it, if not this is the first thing to do). 

- Then you need to monitor the PDF iframe, and once it is loaded, change the focus to the tablepane in the parent page. 

iframe.attachEvent("onload", function(){ }) is the way to do iframe onload events in IE, this function should set the focus in the tablepane. As an example the function maybe something like: 

function myFunction() { 
            document.getElementById("tablepane").focus(); 
        } 

I hope this helps! 

On Eclipse Oxigen I setup in Preferences -> DevStyle -> Color Themes: 

Workbench : Dark Gray (Darkest Dark)

Editor: Darkest Dark

Then, I needed to edit the file in the Atelier directory: 

 .metadata/.plugins/org.eclipse.core.runtime/.settings/com.intersystems.atelier.core.ui.prefs
 

which is a little bit different than previous comments.

Then added a slightly different background (not so dark) which matches with General 

Studio_Color_BG_false=24,28,31
Studio_Color_BG_true=37,37,37
Studio_Color_brace=255,255,255
Studio_Color_bracket=255,255,255
Studio_Color_classmethodname=189,214,255
Studio_Color_classname=210,81,81
Studio_Color_collationname=189,214,255
Studio_Color_cosBitlogicOperator=210,81,81
Studio_Color_cosClassName=239,191,143
Studio_Color_cosCommandWordDeprecated=210,81,81
Studio_Color_cosCommandword=210,81,81
Studio_Color_cosDollarName=210,81,81
Studio_Color_cosDollarNameDeprecated=210,81,81
Studio_Color_cosEmbedDelim=0,128,0
Studio_Color_cosEmbeddingStartOrEnd=210,81,81
Studio_Color_cosExtrinsic=210,81,81
Studio_Color_cosGlobalname=141,203,226
Studio_Color_cosGlobalname_bold=true
Studio_Color_cosIOFormat=255,255,255
Studio_Color_cosJsonBrace=255,255,255
Studio_Color_cosJsonBracket=255,255,255
Studio_Color_cosJsonKeyword=210,81,81
Studio_Color_cosKeyword=210,81,81
Studio_Color_cosLabel=210,81,81
Studio_Color_cosLabelname=141,203,226
Studio_Color_cosLocalname=136,214,255
Studio_Color_cosMacroArgsAnything=136,214,255
Studio_Color_cosMacroCall=210,81,81
Studio_Color_cosOperator=255,255,255
Studio_Color_cosPPCommand=141,203,226
Studio_Color_cosPPFunc=210,81,81
Studio_Color_cosPattern=210,81,81
Studio_Color_cosSQLFieldName=210,81,81
Studio_Color_cosstring=255,198,0
Studio_Color_csqlIdentifier=255,198,0
Studio_Color_delim=255,255,255
Studio_Color_foreignkeyname=121,171,255
Studio_Color_htmlAttributeName=121,171,255
Studio_Color_htmlAttributeValue=255,255,255
Studio_Color_indexname=189,214,255
Studio_Color_indexpropertyname=255,255,255
Studio_Color_jsKeyword=141,203,226
Studio_Color_jsOperator=255,255,255
Studio_Color_jsString=255,198,0
Studio_Color_jsonString=255,198,0
Studio_Color_methodname=255,255,255
Studio_Color_name=255,255,255
Studio_Color_number=129,180,71
Studio_Color_parameter=121,171,255
Studio_Color_parametername=189,214,255
Studio_Color_paren=255,255,255
Studio_Color_propertyname=189,214,255
Studio_Color_queryname=189,214,255
Studio_Color_sqlstring=255,255,128
Studio_Color_storagename=189,214,255
Studio_Color_triggername=189,214,255
Studio_Color_udlDocComment=201,222,12
Studio_Color_udlKeyword=80,175,226
Studio_Color_udlMCKeywordName=255,255,255
Studio_Color_udlMCKeywordValue=129,180,71
Studio_Color_udlNumericLiteral=129,180,71
Studio_Color_udlStringLiteral=255,198,0
Studio_Color_xdataname=189,214,255
Studio_Color_xmlAttributeName=255,255,255

The ^MONMGR utility just send mails based on the severity of the messages in the cconsole.log. In order to find the severity in the cconsole.log you can look at the number after the date and process id. 

11/14/16-00:39:09:735 (74654) 2 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon still on pass 1112
11/14/16-00:40:40:865 (74654) 0 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon completed a pass.

In that case we can see severity 2 for the first message and 0 for the second one (The OK one). As the default severity level in ^MONMGR is 2, it will only send mails when it's 2 or higher.  Note that you can change this level from the MONMGR menu, but lowering to 0 or 1 will give you lots of messages which probably you don't want. 

Anyway, after getting any 2 level message, the recommendation is to review the logs and find what caused the problem. If is a puntual error and was solved by itself (like the one you described) you should not worry. If you keep getting such messages my recommendation is to investigate and contact with Intersystems support if you need help.