What do you mean by "productdescription" ?

When Ensemble runs on Windows its background processes typically run with whatever Windows credentials the Ensemble service (see Windows Service Control Manager) is set to "Log on as". If that is LocalSystem then your background processes won't be able to access UNC paths.

For more information, see my post here. 

If my answer here resolves your question please click the checkmark alongside it above.

There's a flaw in your original idea of eliminating the comma from two $H-format timestamps and then comparing them with the "greater than" operation. For most of a 24 hour period the resulting $TR(dollarH,",") is 10 digits long, but from midnight until 00:00:09 it is only 6 digits long, from 00:00:10 to 00:01:39 it is 7, from 00:01:40 to 00:16:39 it is 8 and from 00:16:40 to 02:46:39 it is 9 long.

A working alternative would be to compute $P(dollarH,",")*86400+$P(dollarH,",",2) for each and compare the results, which are the number of seconds since midnight at the start of 31st December 1840.

if you need to compare a $H-format timestamp against the current time don't use $P($H,",")*86400+$P($H,",",2) as one of the expressions because there's a small possibility that your two fetches of $H will fall either side of midnight. Instead, fetch $H once, store it in a variable, then process that variable.

What is your question?

I didn't see any mention of a "USA and Europe" restriction on the website information.

Any reason for not including, say, Canada?

Has CCR become a released product?

Like most DC posts nowadays, this one got auto-crossposted to the intersystems-public-cache Google Group. When I checked this morning there were 5 responses from people trying to help the original poster. But since those answers don't automatically feed across to DC I'm drawing attention to them here. Because unless the OP knows to look there they may never see them.

https://groups.google.com/forum/#!topic/intersystems-public-cache/fngd5…

If you are trying to get the output of the command, one way is to use a pipe device. See this post.

Answered in comments.

Answered by the OP in comments.

Here are some initial suggestions / comments (no particular priority):

1. Standardize on capitalization in naming. For example classnames EX.example and Sample.Classes, and property names name and Location.
2. Use singular for your classname, e.g. Class rather than Classes
3. Use meaningful classnames, e.g. Sample.Employee rather than Sample.Classes
4. Use meaningful method names. e.g. insert or Insert rather than hello
5. Avoid namespace switching unless really necessary. Presumably in your case the Sample.Classes class is in the USER namespace and the EX.example is somewhere else (maybe you wrote it in your SAMPLES namespace).
6. For a REST interface, consider returning results in a structured form, e.g. JSON.
7. Make good use of indenting. Perhaps you already have done this and the post to DC has mangled it.
8. Avoid using Z-commands, $Z-functions and $Z if non-Z equivalents are available. For example, SET $NAMESPACE="USER" instead of ZN "USER". Note that you can also preserve the current $NAMESPACE value using NEW $NAMESPACE which will automatically reinstate the value when the stack level is exited.

I hope this is a useful start.