検索

質問
· 2025年11月23日

Production Status Details

Hi,

I want to get the status of a Production (Running, Stopped), Queue length, Time the Production started

I did this:

>zn "test"
>set status=##class(Ens.Director).GetProductionSummary(.pinfo)
>write status
1
>zwrite pinfo
pinfo("PKG.FoundationProduction")=$lb("Stopped","","",0)
pinfo("Report.Print.EnsemblePrintService")=$lb("Stopped","2021-02-09 23:15:57.538","2021-02-09 23:16:15.264",0)
pinfo("TC.hmf.Production")=$lb("Stopped","","",0)
pinfo("TC.hmf.System.Production")=$lb("Running","2025-10-30 10:18:24.057","",1)
 

When I run the System Management Portal (Interoperability>Production Configuration)  shows that for the namespace "test" there is this production:

"TC.hmf.System.Production"

The questions I have:

1. I understand that there is only one production per namespace.
What are the remaining lines?
If there is only one production, "TC.hmf.System.Production", how can I get the name of the production programmatically and then print that line only?

2. Method "GetProductionSummary" is not documented
"Running",C,"",1
I understand that it means the production is
Running
Started "Running","2025-10-30 10:18:24.057"
Queue Length 1
Correct?
What is the 3rd parameter? ("")

Thanks for any help

1 Comment
ディスカッション (1)1
続けるにはログインするか新規登録を行ってください
記事
· 2025年11月23日 1m read

Graphic view of DBsize with CSP

A previous attempt was assisted by an external Python method.
This is all classic CSP written with ISOS, JavaScript, HTML

Besides the graphic, you also get concrete numbers freshly collected from your local
instance or from remote instances that also installed the package. 

The final result

The processing steps 

  • A CSP page is called by its URL
  • In method OnPreHTTP
    • The System Query fills the temp table from %SYS
    • If the correct URL parameter is provided 
    • ?SERVER=IP-Address[:SuperServerPort[:Username[:Password]]]
    • Actual data are fetched from this server using the Native API for ObjectScript

GitHub

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
質問
· 2025年11月23日

Unit Test System in the InterSystems iris

Hello word!

I am new in this field and i am coming from the dot net and angular world.
So hello to everyone!

Im trying to understand the unit test in the vs code what is works in the community version at home (25.2).
I set the  ^UnitTestRoot to somewhere and setted the "unitest: enabled" setting in the settings.json file. 
But it is not work and can't run. Is't it scan? It is not a problem because i can run it dircetley with ##class(classname).RunTest() and it runs but doesn't contain anyting. The Restresult is exist but it is empty.
I think the system is does not understand that the test can find somewhere.
I use the %UnitTest.TestCase as baseclass and use it as at home where it is works.. so i'm stucked. 

Can anyone help me how I can create unittest in the 23.3 version?

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
記事
· 2025年11月21日 1m read

InterSystems IRIS Shells

Hi,

When we open a terminal in IRIS, we are entering the ObjectScript shell. Within this shell, we can execute IRIS commands, such as:

In other words, the ObjectScript command is executed in the current shell. But it's always good to remember that IRIS has other shells

  • SQL
  • Python
  • TSQL
  • MDX

One very interesting aspect is shortcuts. We can access these shells through their calls or via shortcuts, as shown in the table below:

 

Shell

Call

Shortcut

SQL

Do $SYSTEM.SQL.Shell()

:sql

Python

Do $SYSTEM.Python.Shell

:py

TSQL

Do $SYSTEM.SQL.TSQLShell()

:tsql

MDX

Do ##CLASS(%DeepSee.Utils).%Shell()

:mdx

Just like that:

Shell Python:

Shell SQL:

Shell TSQL:

Shell MDX:

 

These shells are extremely useful for running commands and tests. Having these shortcuts at hand saves a lot of time and they are very helpful when developing.

The documentation link
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCLI_shells provides a detailed look at these shells and their features. They have several interesting features that are worth exploring.

Til next time!!

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
記事
· 2025年11月21日 1m read

InterSystems IRIS - Shells

InterSystems IRIS - Shells

Olá,

Quando abrimos um terminal no IRIS estamos entrando no ambiente ObjectScript. Nele podemos executar comandos do IRIS, tais como:

Ou seja, o comando ObjectScript é executado no shell corrente. Mas é sempre bom lembrar que o IRIS tem outros shells:

  • SQL
  • Python
  • TSQL
  • MDX

Uma questão bem interessante são os atalhos. Podemos acessar estes shells pelas suas chamadas ou através de atalhos, conforme a tabela abaixo:

Shell

Chamada

Atalho

SQL

Do $SYSTEM.SQL.Shell()

:sql

Python

Do $SYSTEM.Python.Shell

:py

TSQL

Do $SYSTEM.SQL.TSQLShell()

:tsql

MDX

Do ##CLASS(%DeepSee.Utils).%Shell()

:mdx

 

Simples assim:

Shell Python:

Shell SQL:

Shell TSQL:

Shell MDX:

 

Estes shells são extremamente úteis para execução de comandos e testes. Ter estes atalhos à mão poupa bastante tempo e eles são muito úteis quando estamos desenvolvendo.

No link da documentação https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCLI_shells podemos ver em detalhes esses shells e suas características. Eles tem vários recursos interessantes que valem a pena serem explorados.

Até a próxima!

1 Comment
ディスカッション (1)2
続けるにはログインするか新規登録を行ってください