Hello to all the Cache Experts out there and Happy Friday!
The company I work for uses Cache 2017.1.3 and we have been seeing intermittent errors in the Cache Error Trap when an SQL query runs. The error message looks like the error is occurring within the cached query routine that Cache auto-generates. Unfortunately, when I pulled up the routine in the SMP System Explorer, I only found an obj version, so was unable to look at any code.
Here is the error: Note: the .cls375 part will be different based on the different SQL queries that run, since that part of the cached query routine name is auto-generated. Also, the generated method can be different, again, based on the SQL query that is run - since the methods in the cached query routines are also auto-generated.
<EXTERNAL INTERRUPT>%0AmBk1^%sqlcq.{namespace}.cls375.1
So my questions for the Cache Developer Experts out there are:
a) have any of you seen this type of issue before? If yes, how did you resolve?
b) any idea how to get the *.INT (or *.MAC) code associated with the *.obj version of the auto-generated cached query routine so I can see the code which might also give me some clues as to what is causing the error?
c) Does anyone have any idea about what the <EXTERNAL INTERRUPT> error is? Could that be happening due to a timeout?
Most of the SQL queries are very simple/basic SQL - an example is below.
Set sql="SELECT DISTINCT PrintBy FROM appPkg.appTable WHERE (Status <> '1' AND Status <> '4')"
Set resultSet=##class(%ResultSet).%New()
Set status=resultSet.Prepare(sql)
Set status=resultSet.Execute()
While(resultSet.Next()) {
// loop and do stuff
}
Much Thanks in Advance for any thoughts, ideas, feedback, suggestions.
Best Regards and Go Team!!!
