Use 'Return' instead: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_creturn
In general, if you're trying to exit a method and return a value to the caller, 'Return' is the best way to do that, as 'Quit' also has functionality for control flow (such as breaking out of WHILE loops).
Hmm, that's not what I would have expected. I'm going to ask around and see if there's something I'm missing here, but in the meantime can you try running TUNE TABLE on this table and see if that changes the behavior/query plans at all? https://docs.intersystems.com/iris20253/csp/docbook/DocBook.UI.Page.cls…
Comparing the two, it does look like the slower query is performing a full table scan for some reason, which is very odd. What type of index is row_status_idx? If it is not a bitmap index, could you try adding an additional bitmap index on the field (or changing the type of the index to bitmap)?
Thanks for checking that! Is this the query plan for the slow or fast version of the query, or are the query plans identical between them?
A couple questions:
1. Do you have an index on row_status? If not, then filtering on that with values that don't exist in the table likely results in a full table scan, though it is odd that the third query would be faster if this is the case.
2. Can you show us the query plans of the four queries? (see https://docs.intersystems.com/iris20253/csp/docbook/Doc.View.cls?KEY=GS… ) This might help us figure out what is going wrong.
Glad it worked out!
My guess is that there is a permissions deficiency in his account that is not obvious. It is possible for a lack of %Admin_Operate:U can deny access to certain pages in the Management Portal; see the following documentation https://docs.intersystems.com/iris20252/csp/docbook/DocBook.UI.Page.cls…
"It controls access to various pages in the Management Portal, including the System Operation page."
Are you certain that there are no permissions differences between his account and others'? You mentioned using a test account with the same permissions - was this test account cloned from your colleague's?
Another possibility is that he is attempting to access a different page in the management portal than you are. Not all pages in the Management Portal are created equal - I would try sending him a "clean" link to the Management Portal landing page to make sure he isn't trying to access a page he doesn't have permissions on.
If neither of these avenues of investigation bear fruit (and no one else here comes up with another answer), I would contact Support - they have the most experience dealing with permissions minutiae.
I hope this helps and that you can get this resolved soon - permissions issues can be very frustrating, speaking from personal experience.
What version of IRIS/Cache was this class imported from? In 2024.1, the %Collection.ListOfObj class doesn't have a parameter called 'Collection': https://docs.intersystems.com/iris20241/csp/documatic/%25CSP.Documatic…;
I am fairly sure you can just remove it without issue.
Do $System.Security.Login("<username>") will work for this, assuming you don't have any custom security configuration that prevents this workaround.
I would recommend reporting this on the docs feedback page: https://docs.intersystems.com/irislatest/csp/docbook/Doc.Feedback.cls&n…;
In my experience they are very responsive to this kind of feedback
One way to do this would be to make use of the 'iris merge' command with a CPF file: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…;
The CPF file in question can run $SYSTEM.Obj.Load as an Action, for example:
[Actions]
Execute:Namespace="USER",ClassName=%SYSTEM.OBJ,MethodName="Load",Arg1="/home/irisowner/dev/cls/TestClass.xml",Arg2="ck"
So the steps here would be:
1. Define a CPF file that loads the classes you need
2. Create a unix script that runs 'iris merge <instance name> <CPF file location>'
Hi Jerry,
Without knowing more about the specific query plan and IRIS setup it would be hard to know what's going on - I would highly recommend reaching out to the WRC about this if you are able. I will note that TUNE TABLE has had significant functionality improvements since IRIS version 2021.2 (see https://community.intersystems.com/post/20212-sql-feature-spotlight-sma…) , it's possible you are missing a bug fix; again WRC would be the best point of contact. Best of luck!
Following up on this from a recent customer conversation: the current best practices that we have settled on has been disabling exportselectivity as in Ben De Boe's post (https://community.intersystems.com/post/cicd-iris-sql), alongside ensuring AdaptiveMode is turned on (https://docs.intersystems.com/iris20243/csp/docbook/Doc.View.cls?KEY=RA…). For now this will ensure that initially collected stats aren't overwritten, and once table statistics are collected automatically this should be completely "hands off".
Great breakdown - just adding that in the terms of the documentation, the "right side" of the && operator in this case is "1". The = sign and everything after it is part of another operation and is not considered in this context.
Didn't realize that, sorry! I should have done more testing myself. I did some more research and found a way to do this in an object-oriented fashion: https://community.intersystems.com/post/get-property-maxlen
I've confirmed that this works on a 2024.1.1 instance with the following steps:
set cdef = ##class(%Dictionary.ClassDefinition).%OpenId("<class name>")
Set count = cdef.Properties.Count()
for i = 1:1:count {if cdef.Properties.GetAt(i).Name = "<Property Name>" {w cdef.Properties.GetAt(i).Parameters.GetAt("MAXLEN")}}
For defining a fixed length string field in a class definition, you can use the MINLEN and MAXLEN parameters in tandem: https://docs.intersystems.com/iris20231/csp/documatic/%25CSP.Documatic…
This will not pad the string automatically, however, you would need to pad it to the desired length before saving an instance of the class.
To retrieve the MAXLEN, this answer to an earlier question may be helpful : https://community.intersystems.com/post/getting-parameters-cleanly-prop…
So the call might look something like:
$$$defMemberArrayGet(class,$$$cCLASSproperty,prop,$$$cPROPparameter,"MAXLEN")
EDIT: These macros aren't available on recent versions, here's an object-oriented way to do it (that's cleaner anyway):
I've confirmed that this works on a 2024.1.1 instance with the following steps:
set cdef = ##class(%Dictionary.ClassDefinition).%OpenId("<class name>")
Set count = cdef.Properties.Count()
for i = 1:1:count {if cdef.Properties.GetAt(i).Name = "<Property Name>" {w cdef.Properties.GetAt(i).Parameters.GetAt("MAXLEN")}}
Thanks @Benjamin De Boe! Is there a particular value you'd recommend setting StayConnected to to minimize query latency while still refreshing the connection within the user expiry window? This is a high usage application so we are pretty concerned about query and connection performance.
Hello,
The Feature Tracker task is a built-in task that sends weekly feature usage reports to InterSystems. For more information, see the following documentation: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…
As for the specific error you received when running it, I am not sure. I will confer with the developers and get back to you when I have an answer. In the meantime, though, it should not have any effect on other IRIS functionality.
Thirding this - I have been getting the same error but on a Postgres database in my case. I wasn't able to find a workaround other than selecting my column as an integer, which obviously isn't an option in Don's case.
I don't think you actually need VS Code to do this - you should be able to call the routine using RunLegacyTask, which lets you write code as part of the task instance definition.
One way to accomplish what you are describing is to use a temporary global: https://docs.intersystems.com/iris20231/csp/docbook/Doc.View.cls?KEY=GG…
This allows you to store data in the IRISTEMP database that you can then retrieve like any other global. For example, if I were debugging a piece of code, I could write the following into the relevant Method:
SET ^CacheTempNP($INCREMENT(^CacheTempNP)) = <some debug value>
Then later ZWRITE ^CacheTempNP to see what I have logged.
(Note: In the documentation, we recommend using a global mapping to set up your own naming convention for temporary globals instead of using the ^CacheTemp prefix. While I still recommend doing that if you plan to use temporary globals in non-testing code, just using ^CacheTemp instead is fine for debugging.)
Rather than trying to assign some combination of predefined roles to accomplish what you are looking for, I would suggest defining a new role and assigning to it the privileges that you need. This documentation page has a guide on doing so: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=GS…
That being said, is there something that your users need to do that is not covered by the %EnsRole_Administrator role?
For more details on the Interoperability > Manage > Deployment Changes category, both the 'Deploy' and 'History' options are controlled by the %Ens_Deploy resource, so your users would need a role with Use on %Ens_Deploy. You can see what resources control a given item in the management portal by clicking on the whitespace next to the item and viewing the 'System Resource(s)' and 'Custom Resource' listings. For more information on resources and privileges, see this documentation: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=GS… . So, any role with %Ens_Deploy, e.g. %EnsRole_Administrator, should give you access.
I hope this helps!
The first error means that you aren't calling the method/routine correctly. See the <NOLINE> error code in this doc page: https://docs.intersystems.com/iris20231/csp/docbook/Doc.View.cls?KEY=RE… . Are you sure $$ConvertToMTime is the right name?
As for the second error: unlike most other programming languages, just calling a routine/method does not work in M/ObjectScript. Every line of code must use a command; in this case what you are looking for is the DO command: https://docs.intersystems.com/iris20231/csp/docbook/Doc.View.cls?KEY=RC…
So, when calling a method/routine, you would write 'do ConvertToMTime(h,m,s)'
I'm not sure about TABLOCK specifically, but there are a couple other features that might help you solve this:
First, there is the LOCK TABLE statement: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=RS…
There's also the objectscript LOCK command: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=RC…
You could use either of these to block the method while other instances of it are running and prevent the race condition. I'm not sure how efficient this method would be compared to TABLOCK, but it would fix the bug.
I hope this helps!
I'm not entirely clear on the question you are asking - if you just need to add quotes to a string, you can do so by escaping with another quotation mark. For example,
set b = """Cat""" // That's 3 quotation marks in a row on each side: one to open/close the string, two to add the quote character to the string
set c = b
w c
"Cat"
If you are asking how to display the quotes without actually adding quotes to the string, I'm not sure if that's possible - would need a more experienced dev to chime in.
I got an answer to this question internally and am reposting it here. From Daniel Bissex:
Using the MDX COUNT function is the slower of two options. We also have a provided Distinct plugin to address exactly this inefficiency:
https://docs.intersystems.com/iris20231/csp/documatic/%25CSP.Documatic.cls?LIBRARY=%25SYS&PRIVATE=1&CLASSNAME=%25DeepSee.PlugIn.DistinctThis uses our %KPI() function syntax, more detailed description of the calling options can be found here:
https://docs.intersystems.com/iris20231/csp/docbook/Doc.View.cls?KEY=D2RMDX_percentK
This reduced the runtime from ~5 minutes to about two seconds! The linked documentation is for IRIS 2023.1, but these functions are available in 2022.1 as well.
I actually already have the calculated measures defined in the cube itself and not in the pivot table - apologies for being unclear.