I think this has something to do with ECP timeout. Please start management portal and check System -> Configuration -> ECP settings.
Default timeout = 1200 seconds (maybe you'll find there a value of 600).

Yes, you may do so, but I told everything I know about ECP

Does the other instance use the same license? All instances must use the multi server option

Do you mean this?:

S sub1=111,sub2=444
S TAB(""_sub1_""","""_""_sub2_"")=""

zw TAB
TAB("111"",""444")=""
 

Another possibility to get freespace is to compact the database:

%SYS> Do ^DATABASE -> Compact globals in a database

You could also use the class  %SYS.Journal.File

Example:
Set JournalFile = ##class(%SYS.Journal.File).%OpenId(EXISTING_JOURNAL_FILE)
Set JournalRecord = JournalFile.FirstRecordGet()
While (JournalRecord '= "") {
  Here you can program your search criteria example:
  If JournalRecord.%IsA("%SYS.Journal.SetKillRecord") {
   insert your code
}
}

Check documentation for further hints.
 

The documentation might be a little bit long, so I try to make it short. If you write down some kind of logic in COS and save it, then you'll get a routine. The easiest  way to create a routine is this, using a terminal session: ZR<ret><tab>WRITE $H<ret>ZS<space>MYROUTINE. (<this are the corresponding control characters>)Doing so, you'll get an INT file called MYROUTINE.INT. You can see it using %RD in a terminal session in the namespace where you saved the routine. You can run it using the command DO ^MYROUTINE or GO ^MYROUTINE

A routine may contain some labels (some name ended with a TAB) which you can use as functions or procedures. A routine is comparable with a class but you can't instanciate a routine like you can do with a class and it does not contain methods or classmethods.

Global is an array stored on disk. It is a nice datastructure to save your data. A routine can write, store or delete some data stored in Global.

Hope this helps to make the things clear to you

Did you check if checkbox named 'Enable long strings' is enabled (checked)? (ManagementPoral -> Configuration -> Memory and startup)?

Placed on wrong place, see above :-)

Hello Paras,

to understand the way Caché distinguishes between the files, you can use the special variable $ZIO. This returns the full filename.

Example: SET FILE="ABC.TXT" O FILE:"N" USE FILE SET FULLFILE=$ZIO USE $PRINCIPAL WRITE $ZIO
If you run this example in two separate terminal sessions then you see, that the version number is incremented. When you do this in the same terminal session and don't close the file then the version number is NOT incremented. The fileversion will be incremented, when the file has been closed (... USE FILE SET FULLFILE=$ZIO CLOSE FILE OPEN FILE:"N" USE FILE SET FULLFILE=$ZIO...).
When you check the content of FULLFILE you'll find the full filename including the version number.

When another process does the same, another file handle is created and if you check $ZIO then you'll see, that this process is using another file version.

At first sight it might be very cool to have code for methods in a few  lines. It is the way of programming we had in the past times. I can't recommend to use this way of coding, because it makes it very hard to read and understand the logic of code. I grew up with this kind of coding so I am very familiar with this but I am happy that Caché gives me the way to code in a modern style. When I look into my old programs, which consist of this kind of coding, then I always feel to read ugly code. I would like to change it immediately. Forget it to compact the code in one line. Put it into more lines and avoid postconditionals. If-statements are more readable and you don't have to think about what the code will do.

Nice satiric article 

Hi Paul,

what is your intention to do so? What kind of error do you get?

How would you do that with PowerShell?:

PS C:\InterSystems\Cache\bin> .\csession mycache -"U" user "##class(test.OsCall).inString(""""""abd"""""")"

<INVALID ARGUMENT>>
PS C:\InterSystems\Cache\bin>

Combination of escape-characters doesn't work like these "##class.....(\`"abd\`")" or "##class....(`"abd`")"

compared to CMD:

C:\Users\me> .\csession myCache -"U" user "##class(test.OsCall).inString(""""""abd"""""")"  //see Seans good answer

Argument read: abd  (this comes from my Caché-class, so this environment works properly)

Instead of using $ZSEARCH you can use the query FileSet in class %File:

ClassMethod getFiles(pDir As %String, pMask As %String)
{
   set dir=##class(%File).NormalizeDirectory(pDir)
   set result=##class(%ResultSet).%New("%File:FileSet")
   do result.Execute(dir,pMask)
   while result.Next() {
      write !,result.GetDataByName("Name")
   }
}

You can do this using Caché Object Script:

S DBDIR="directory_of_database"
S DBOBJ=##class(SYS.Database).%OpenId(DBDIR)
S DBOBJ.ReadOnly=0  //switch to read/write mode
S STA=DBOBJ.%Save()

S DBOBJ.ReadOnly=1  //switch to read only mode
S STA=DBOBJ.%Save()