Replies

I certainly hope that the mystery parties who have been moderating that site are reaching out to Google in order to get it reinstated.  There was certainly a lot of valuable information on that site!

You can use $system.OBJ.Load() or LoadDIr() to load source from disk.

Personally, I would do this via Source Control and not via Studio.  The approach to this will depend on your source control structures, etc, but the easiest way to handle this for me would be:

1) Make sure that everything in my package was checked into my branch, e.g. /MyApp/cls/MyFirstPackage/...

2) Since my source tree is structured according to package names, I would copy /MyApp/cls/MyFirstPackage/... to /MyApp/cls/MySecondPackage/... 

3) Check in /MyApp/cls/MySecondPackage/... into source control

4) Check out /MyApp/cls/MySecondPackage/... 

5) Do a Find & Replace in /MyApp/cls/MySecondPackage/... to replace all instances of "MyFirstPackage" with "MySecondPackage"

6) Diff /MyApp/cls/MySecondPackage/...  and make sure all replacements are desired

7) Check in /MyApp/cls/MySecondPackage/... 

8) Run my build routine to pull all of /MyApp/cls/MySecondPackage/...  into my namespace and Compile it (or just use $system.OBJ.LoadDir() if you don't already have a build routine)

Voila!  Package is duplicated and all checked into source control ready for further changes :) The above process should only take a couple of minutes.

The lock controls the source control hooks, so anything relying on the hooks should prevent changes to items under source control.  Parts of the Ensemble Management Portal and the DeepSee portal tie in the hooks for that namespace, so I can see there being a possible interplay there.  I have never used the "Deploy Production Changes" utility so I can't say for certain if the source control lock is coming into play there.

You should work through this with Managed Services to find a resolution. 

No - CCR is not a 'released product'.  But there are implementation sites partnering with InterSystems that use it.  

Scott,

See the Documatic for the following methods in %Studio.SourceControl.ISC:

classmethod Lock(Admin As %Boolean = 0) as %Status

Lock the source control hooks for this instance.

The default setting will be "Locked". Passing a '1' for the Admin parameter will set the instance to AdminLocked.

See Locked for more details.

classmethod Locked() as %String

Returns value that shows whether or not this instance is "Locked"

Return values are:

  • "": Instance has never been Locked or Unlocked (default)
  • 0: Instance is Unlocked
  • 1: Instance is Locked
  • 2: Instance is AdminLocked

When the instance is Locked or AdminLocked, no changes can be made via Studio. It is possible to change from Locked to NotLocked via different UIs. When an instance is AdminLocked it should only be possible to unlock it via the Unlock method.

classmethod Unlock() as %Status

Unlock the source control hooks for this instance.

Andreas - should this be cross-posted on the InterSystems Compatibility blog?

http://blog.intersystems.com/compatibility/

My guess is that there may be some people who follow that who might miss this significant announcement on the Developer Community.  I know I missed this when it was originally posted.