Object script analog of RCOPY

Question

Question

Anna Golitsyna · Oct 8, 2021

I am trying to figure out the best ObjectScript analog to mimic, more or less, the %RCOPY functionality. What would be ObjectScript method(s) if any to copy a routine from the current namespace to another one and compile it there?

Product version: Caché 2017.1

Discussion (12)1

Log in or sign up to continue

Marc Mundt · Oct 8, 2021

It's a bit clunky, but you could use %SYSTEM.OBJ::ExportToStream in the source namespace followed by %SYSTEM.OBJ::LoadStream in the target namespace.

1 0

Anna Golitsyna · Oct 8, 2021

Marc, a slight variation on your idea, tested whether targetRtn exists or not. Thanks again!

zn "A"
s currRtn=(##class(%Routine).%OpenId(rtnName))
s stream=currRtn.Read()
zn "B"
s targetRtn=(##class(%Routine).%OpenId(rtnName))
s sc=targetRtn.Write(stream)
d targetRtn.Save()

0 0

Stephen Head · Oct 11, 2021

Probably a bit old-fashioned and maybe too simple, but this still works:

x "zl @rtn zn tns zs @rtn"

where rtn is the routine name and tns contains the name of the 'to' namespace.

1 0

score 1 · Answer 1 · 2021-10-08T12:29:48-04:00

I would recommend package mapping, unless you have a reason for the code to be different in the same routine between the namespaces? I have used package mapping for a while so it should be an option in older versions as well:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

score 0 · Answer 2 · 2021-10-08T12:36:22-04:00

That would make the routine from namespace A immediately available in namespace B as is. The goal is to have routines in two namespaces different until the time comes for the programmer to make them the same via an RCOPY analog. It is also a "per routine" job used for synchronizing.

score 0 · Answer 3 · 2021-10-08T14:32:48-04:00

Anna Golitsyna · Oct 8, 2021

Thanks! Let's see if there are less "clunky" ways

0 0

score 0 · Answer 4 · 2021-10-09T02:41:56-04:00

Robert Cemper · Oct 9, 2021

What's bad about using %RCOPY if you want it ?

0 0

score 1 · Answer 5 · 2021-10-09T04:30:29-04:00

Eduard Lebedyuk · Oct 9, 2021

I think OP needs non-interactive approach.

1 0

score 0 · Answer 6 · 2021-10-11T10:31:28-04:00

Anna Golitsyna · Oct 11, 2021

Robert, it does not trigger source control and yes, I'd like it non-interactive too.

0 0

score 0 · Answer 7 · 2021-10-11T17:29:38-04:00

Also %RCOPY preserves date modified of the original routine, and I'd rather preserve it. So far other listed approaches do not preserve it.

score 0 · Answer 8 · 2021-10-11T16:00:19-04:00

Yes, that works and assigns the time of copy as the date modified. Thanks, Stephen! BTW, in my experience at least some old-fashioned commands are faster than their modern equivalents though in this case the speed is not an issue.

score 0 · Answer 9 · 2021-10-12T02:52:12-04:00

Alexey Maslov · Oct 12, 2021

That approach works only for *.INT routines. Don't you use *.MAC and *.INC as well?

0 0