AllAccepted answers
Robert Cemper · Oct 29, 2021

In past, I have seen so many "re-invented wheels" on COS that were mostly kind of remakes of
existing packages or solutions. Though this is impressive from a coding point of view,
it is just a waste of energy from point of view of a project AND its maintenance.

I had similar experiences with SQL that was refused by "experienced" programmers
insisting on horrible $ORDER() / $QUERY() constructs almost un-supportable, to gain
a few microseconds of performance on a weekly report. 

The deeper reason: nobody explained it and trained them.
That's the behaviour to avoid. 

Robert Cemper · Oct 29, 2021

some hints.

  • use the opportunity to separate data from code. So you have already a new IRIS.DAT with all globals
  • create a fresh IRIS.DAT to be used just for routine (classes, ... )
  • now you should have a clean start of your IRIS instance
  • check if the globals are visible as expected, but neither classed not routines.
  • now open 1 Studio on Caché and 1 on your target IRIS namespace
  • next you can move all classes, routines, ... by drag&drop from Caché Studio to IRIS Studio
  •  
  • this last step could also be an XMLExport of all code and XML input but you miss eventually required adjustments.
Robert Cemper · Oct 26, 2021

Hi @Vic Sun , @Akshay Pandey :
Just to complete this discussion.
From Terminal I could run Py also from a JOB, and over CPIPE without problems.
From Studio Output all this FAILS.
Which makes clear that the process behind Studio is far away from being a normal
IRIS/Caché process and just good for editing and compiling.  FullStop.

I would even assume that running COS commands was not planned but rather an accident that happened 20 yerars ago.

 

Robert Cemper · Oct 26, 2021

I spent quite a while on the subject of python. Also the asynchronous $ZF(-2) + error log

write $zf(-2,"C:\Users\cemper\AppData\Local\Microsoft\WindowsApps\pythonw3.9.exe <c:\temp\in.py 1>c:\temp\5out.txt 2>c:\temp\5er.txt")

And the error from WINDOWS was always: the program can not be executed
A further reason to use Embedded Python!

in.pyw is simply

print("success")
exit()
 

Robert Cemper · Oct 25, 2021

you can do it from SMP > SystemOperation > Databases > .....
or from Terminal, Namespace %SYS

%SYS>do ^DATABASE
 
 
 1) Create a database
 2) Edit a database
 3) List databases
 4) Delete a database
 5) Mount a database
 6) Dismount a database
 7) Compact globals in a database
 8) Show free space for a database
 9) Show details for a database
10) Recreate a database
11) Manage database encryption
12) Return unused space for a database
13) Compact free space in a database
14) Defragment a database
15) Show background database tasks
 
Option? 2
Database directory? ?
 
1) c:\intersystems\iris\mgr\
2) c:\intersystems\iris\mgr\ens\
3) c:\intersystems\iris\mgr\ens\ensenstemp\
4) c:\intersystems\iris\mgr\enslib\
5) c:\intersystems\iris\mgr\irislib\
6) c:\intersystems\iris\mgr\irislocaldata\
7) c:\intersystems\iris\mgr\iristemp\
8) c:\intersystems\iris\mgr\user\
 
Database directory? 8 c:\intersystems\iris\mgr\user\
 
 1)* Directory:                      c:\intersystems\iris\mgr\user\
 2)* Block size (bytes):             8192
 3)* Mirror DB Name:
 4)* Mirror Set Name:
 5)  Current Size (MB):              11
 6)  Max size (MB), 0=Unlimited:     0
 7)  Expansion size (MB), 0=Default: 0
 8)  Resource name:                  %DB_USER
 9)  Preserve global attributes:     Nein
10)  Global journal state:           Ja
11)  New global collation:           IRIS standard
12)  New global growth block:        50
13)  New global pointer block:       16
14)  Read Only:                      Nein
15)* Encrypted:                      Nein
 
Field number to change?