#Terminal

5 Followers · 221 Posts

Posts that relate to discussions on utilizing the Terminal tool.

Question Eduard Lebedyuk · Feb 11

When I build docker containers my build log usually looks like this:

#9 24.94 Using 'iris.cpf' configuration file
#9 25.82
#9 27.55 Starting Control Process
#9 27.55 Global buffer setting requires attention.  Auto-selected 25% of total memory.
#9 27.55 Allocated 4999MB shared memory
#9 27.55 3915MB global buffers, 391MB routine buffers
#9 29.84 This copy of InterSystems IRIS has been licensed for use exclusively by:
#9 29.84 No local key detected, trying license server.
#9 29.84 Copyright (c) 1986-2026 by InterSystems Corporation
#9 29.
2
0 74
Question Scott Roth · Jan 7

I was trying to see if we could connect to another Server, we use to execute external scripts using %Net.SSH.Session.

TESTCLIN>set sshSession = ##class(%Net.SSH.Session).%New()

TESTCLIN>set user = <omitted>

TESTCLIN>set host = <omitted>

TESTCLIN>set privateKey = "/nfs/data/ssh/<omitted>"
TESTCLIN>set publicKey = "/nfs/data/ssh/<omitted>.pub"
TESTCLIN>Set statusConnection = sshSession.Connect(host)

TESTCLIN>set statusAuth = sshSession.
2
0 100
Question Jean Millette · Oct 15, 2025

Can someone help me understand what type of user error (?) is going on here please?

One one system, I write out a group of $c() values and get the expected results:

USER>for i=250:1:260 { write i," ", $c(i),! }
250 ú
251 û
252 ü
253 ý
254 þ
255 ÿ
256 Ā
257 ā
258 Ă
259 ă
260 Ą

USER>w $zv
IRIS for Windows (x86-64) 2023.1.4 (Build 580U) Fri Apr 19 2024 11:16:07 EDT
USER>

On another system, I get some unexpected results:

USER>for i=250:1:260 { write i," ",$c(i),!
4
1 157
Question Yone Moreno Jiménez · Aug 5, 2025

Hello, how are you?

First of all thanks for your time reading this question.

We are investigating how to validate the indexes of a global. We have read:

https://docs.intersystems.com/irisforhealth20251/csp/docbook/DocBook.UI…

And:

https://docs.intersystems.com/irisforhealth20251/csp/documatic/%25CSP.D…

We want to validate the inxedes of the global titled "Ens.Util.LogD". We have executed on the ObjectScript terminal, on the desired namespace:

ESBSSCC>set tSC = $SYSTEM.OBJ.

2
0 135