go to post John Murray · May 29, 2018 Thanks for posting the 1.2 info Joyce.Beta testers upgrading from a previous version may find useful additional info in my earlier post here.
go to post John Murray · May 29, 2018 This seems to have been addressed in Atelier 1.2. Using build 118 from the beta repo I get the following when testing a connection to a server installed with Minimal security (which somewhat surprisingly is still an option when installing IRIS 2018.1.1)To resolve this I must enable another authentication method (e.g. Password) on the /api/atelier web app:Probably a good idea to deselect Unauthenticated. Even though Atelier doesn't seem to allow anonymous connection to /api/atelier REST service I guess it'd be possible to do this directly.
go to post John Murray · May 25, 2018 I switched to my upgraded 1.1 workspace and tried a couple of times launching Eclipse with 'eclipse -clean' but still get the errors. It's not critical for me, as it was only a play workspace. But it might matter more to other folk if they have the same experience.
go to post John Murray · May 25, 2018 Update: starting with a fresh Eclipse workspace seems to be helping...For the record, it seems 1.2 has appeared in the Beta repo that's documented at https://download.intersystems.com/download/atelier.csp#plugin - https://atelier.artifactoryonline.com/atelier/updates/beta/latest/
go to post John Murray · May 23, 2018 I'm not sure that GBLOCKCOPY is able to cope with you specifying the same filepath for the source and destination databases.GBLOCKCOPY doc for 2008.1 is here.
go to post John Murray · May 22, 2018 Where are you running the GBLOCKCOPY? If on your 2014 environment I think you'll be having the same problem as when you just tried to mount the database there. GBLOCKCOPY needs to mount it before it can copy block from it to your new database.Most likely, your original database has 2KB blocks. Your problem then is, 2014 can't mount any databases with 2KB blocks. The last version supporting 2KB block databases was 2011.1. See here.
go to post John Murray · May 16, 2018 Do you have login credentials for WRC Online at http://wrc.intersystems.com/ ?Once you have logged in, use the "Online Distributions" link. You'll need to contact your InterSystems account manager to request a license key.Alternatively, get your hands on InterSystems IRIS in the cloud here.
go to post John Murray · May 16, 2018 Might be wise to amend your code so you check the status code returned by each of the methods you're calling.
go to post John Murray · May 15, 2018 The TROLLBACK command doesn't automatically release LOCKs that were acquired within the transaction. The TROLLBACK documentation is a bit confusing in this regard. At one point it says this:Then later on the same page this text seems to say that both TROLLBACK and TCOMMIT do release locks.Jordi, in your example:TSTARTDo ##class(MyTable).%OpenId(<TableID>, 4) (This internally is creating a Lock +^User.MyTable(<TableID>)TROLLBACK (This action removes the previous lock)I don't think it's the TROLLBACK that's releasing the lock, but rather the destruction of the oref that the %OpenId method created. Indeed, if tested exactly as you wrote it that oref doesn't even get stored in a local variable, so ceases to exist as soon as the method call completes.
go to post John Murray · May 14, 2018 @Ponnumani Gurusamy - when your Atelier problem is solved and you are able to save and run the sample routine you showed us in your screenshot, what do you predict the output will be?
go to post John Murray · May 14, 2018 I also recommend that you look at this YouTube playlist of useful videos about Atelier.
go to post John Murray · May 14, 2018 First you need to create an Atelier Project, which is a type of Eclipse project suitable for containing MACs, classes and other InterSystems code entities.From the File menu, select New, then Atelier Project.The RemoteSystemsTempFiles project isn't an Atelier Project. You can learn more about RemoteSystemsTempFiles here.
go to post John Murray · May 11, 2018 The old Google group isn't owned or managed by InterSystems, and previous attempts to get whoever does manage it to do anything to tackle the potential confusion etc have been unsuccessful. There are several other posts here on DC about this. For example:https://community.intersystems.com/post/automatic-crossposting-developer-community-google-group-user-intersystemsdcFor others, search DC for the term "Google".
go to post John Murray · May 9, 2018 That's the doc for the %SYS.Task package. One row above it in the Documatic explorer panel you'll find the link to the %SYS.Task class. Here's a link to the online copy for 2017.1http://docs.intersystems.com/cache20171/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25SYS.TaskI'm seeing ExportTasks and ImportTasks methods, both inherited from %SYS.TaskSuper
go to post John Murray · May 9, 2018 Did you find the ExportTasks and ImportTasks classmethods of %SYS.TaskSuper, which AFAIK is the superclass of all tasks?http://docs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25SYS.TaskSuper#METHOD_ExportTasksI haven't tried them myself, but at first sight they look promising.
go to post John Murray · May 3, 2018 I disagree with your assertion that you can't call at a tag in a way that you can call from the top:USER>zpYJM w !,"Runs in ",$namespace,! q ;SUB ; A subroutine tag w !,"SUB^YJM runs in ",$namespace,! q USER>zn "samples" SAMPLES>d SUB^|"USER"|YJM SUB^YJM runs in SAMPLES SAMPLES>I find it confusing that you talk about calling a routine in a namespace. As I see it you're fetching it from another namespace (i.e. the one the routine lives it), but you're running it in your current namespace.You also need to be aware of what happens if the code you fetch from the other namespace makes its own calls to other code. Here's an illustration:USER>zpYJM w !,"Runs in ",$namespace,! q ;SUB ; A subroutine tag w !,"SUB^YJM runs in ",$namespace,! q ;Test1 ; w !,"About to call local line label YJM",! d YJM q ;Test2 ; w !,"About to call a line label in a specific routine",! d SUB^YJM q USER>d Test1^YJM About to call local line label YJM Runs in USER USER>d Test2^YJM About to call a line label in a specific routine SUB^YJM runs in USER USER>zn "SAMPLES" SAMPLES>d Test1^|"USER"|YJM About to call local line label YJM Runs in SAMPLES SAMPLES>d Test2^|"USER"|YJM About to call a line label in a specific routine d SUB^YJM ^<NOROUTINE>Test2+2^YJM *YJMSAMPLES 2d0> SAMPLES 2d0>q SAMPLES>
go to post John Murray · May 3, 2018 I didn't expect D ["SAMPLES"]YJM^YJM to work, but that's the syntax you used in your earlier comment. Probably a typo.I agree, it's interesting that the older-style square-bracket extended reference syntax doesn't work in this context. You have to use the newer-style vertical-bar syntax.
