Pedro - good to see that DC members were able to help. Now please set the "accepted answer" checkmark that only you (as OP) are able to set. If you're unsure where to look, see my screenshot below:

Maybe worth adding that the two MS packages can be run with command line options suitable for unattended use, e.g.

vcredist_x86.exe /passive /norestart

For a dialog box showing all the command line options:

vcredist_x86.exe /help

or

vcredist_x86.exe /?

I wish an unattended install of Cache would install these runtime prerequisites automatically for us. I think it does that when doing an interactive install, which would imply that the vcredist_x*.exe kits are already bundled inside the cache*.exe installer.

Robert, your first doc link is actually for $TEST. The link for LOCK is http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

You can use a 0 second timeout on the LOCK command. That way your process will proceed immediately and you can check the value of $TEST (either directly, or indirectly using the ELSE command or an argumentless IF) to discover if you got the lock(s) or not.

When processing the two pieces of a timestamp such as $ZTS it is safer to assign the timestamp once to a variable, then operate on that variable, e.g.  instead of

W (+$ZTS-47117*86400) + $J($P($ZTS,",",2),0,0)

use

S zts=$ZTS W (+zts-47117*86400) + $J($P(zts,",",2),0,0)

This avoids the edge case in the original code, where the first evaluation of $ZTS happens just before the midnight rollover and the second evaluation at or just after it.

Did you find it? The checkmark has now been set.

Any suggestions about how to make this facility more obvious to posters?

Eric, to mark your question as "answered" on Developer Community, please click the checkmark alongside the answer you (as author of the question) accept.

I'd also like to draw your attention to DC's facility for commenting on an answer (which is what I'm doing here). It's probably not obvious enough, meaning that you response to Alexander displays as a second answer to your original question.

Well done Rob!

Good to hear. Now please set the checkmark alongside Jamie's original answer, so your question shows in DC as having been answered.

Doc for 5.0 is available at http://docs.intersystems.com/documentation/cache/cache5docs/

At the bottom of that page I found this:

Using the Caché GBLOCKCOPY Routine —  This article describes the basics of running GBLOCKCOPY to copy globals.

The link is to a PDF. One of the use cases in the PDF is as follows:

Reclaim unused space in a database
If a large global is created then killed in a database, there may be a large excess of unused space in the database. This space can be removed by copying all the globals in the database to a new one, and then replacing the old database with the new database.

That's what I think you need to do. It sounds like you used GBLOCKCOPY to copy to a namespace in an existing database rather than to a fresh empty database.

Of course, you will need enough disk space to have the smaller new database alongside the big database until you have completed the copying.

Luca, any reason for recommending %Exists and having to use $LISTBUILD when you could go direct to %ExistsId ?

Are you able to use the beta of Atelier 1.1? See https://community.intersystems.com/post/atelier-11-beta-updates-%E2%80%…

So I've used my moderator superpowers to correct the first line of the post.

I'm not having much success finding docs for $system.CLS

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY… says:

but no mention of CLS. Nor does the %SYSTEM package contain a CLS class in the same way as it contains the ones listed above.

Rubens, your rule #2 says " Argument index starts from 0" but in your example the index starts at 1.