Runtime licenses

General Macro Scheduler discussion

Moderators: Dorian (MJT support), JRL

Post Reply
mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Runtime licenses

Post by mightycpa » Sat Jan 27, 2018 5:33 pm

How do I install/use the runtime licenses?

EDIT: Let me get specific about my question. Using the runtime, is there a way to run a script from the command line?

How do you keep track of number used?
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Runtime licenses

Post by Marcus Tettmar » Mon Jan 29, 2018 4:30 pm

Yes, they work exactly like regular licenses, so the command line is the same. The only differences is they have no editing features. But running works the same as the version you've known and loved for years.

You will see in your account how many you are licensed for. You'll need to keep track but will get a warning if the system detects more than the allowed number of instances.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Mon Jan 29, 2018 4:35 pm

I do this: msrt demo.scp

where both files are in the same folder and nothing happens.

but if I do this: msched demo.scp

it runs

So there has to be more to it.
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Runtime licenses

Post by Marcus Tettmar » Mon Jan 29, 2018 4:40 pm

msrt is the compiler. Nothing to do with the client runtimes which come with Enterprise. We may be at cross purposes. Never the less - msched.exe is just Macro Scheduler. And whichever version of Macro Scheduler (runtime or not) you use it is still msched.exe and whichever version you have msched.exe scriptname or msched.exe scriptfile.scp will run a macro.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Mon Jan 29, 2018 4:50 pm

OK, so what you appear to be saying is that all we have to do is install MacroScheduler using the installer, the install is business as usual, and once installed, we just run a script like this:

msched demo.scp

So just out of curiosity, how does Macro Scheduler distinguish the Editor from the Runtime?
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Mon Jan 29, 2018 4:52 pm

Maybe I only have the editor locally... that could be the problem. Let me look at that.
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Runtime licenses

Post by Marcus Tettmar » Mon Jan 29, 2018 5:00 pm

It doesn't.

We offer something called Runtime Clients which come with the Enterprise Pack. I have no idea whether you have those or not. These are additional to your regular license. Runtime Clients will not let you create or edit macros. But they can still RUN macros in THE SAME WAY that a regular version does.

So it depends WHAT You install. If you have msrt.exe you must have the Pro version. So when you run msched.exe you have access to the editor etc. But to run a macro on the command line just pass it on the command line as you are. If you want to edit it add -EDIT to the command line.

If, however, you own an Enterprise Pack and happen to have the runtime client version, when you install THAT you will be able to run macros but will have no editor, and won't be able to create macros.

But in-so-far as running via the command line you won't see any difference.

Still not really sure which version you are actually referring to.

If you have ONE Pro License you can't just install that any old place - you still only have a ONE USER license. So it is not just a case of installing that where you want a "runtime". Instead just compile the macro and then put the .exe on the target machine and run THAT and you don't have to install Macro Scheduler at all.

Perhaps we need to rewind, find out what you actually want to do and what you have access to?
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Mon Jan 29, 2018 5:15 pm

I have a PRO license personally, my company has the Enterprise license. I was looking in the wrong folder, I keep the two sets of files separate. I logged in, found the correct license, and I think I'm good to go now.

Don't worry, if I have trouble, I'll be back.
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Mon Jan 29, 2018 5:33 pm

Yes, that works a lot better.

I notice there's a compile button on the runtime, but when I try it, it stops me because I don't have the compiler installed. (I installed the runtime on a second machine.)

The Enterprise product page isn't 100% clear, does this version include the compiler? It describes Enterprise as an add-on for Pro, so I'm assuming YES.

Is there a way to install both the compiler and runtime, but not the editor? I could go into a long story about WHY, but trust me when I say that we need it to be this way on certain machines.
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Runtime licenses

Post by Marcus Tettmar » Mon Jan 29, 2018 5:37 pm

The runtime version does not have the compiler.

Only Pro has the compiler.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

mightycpa
Automation Wizard
Posts: 343
Joined: Mon Jan 12, 2004 4:07 pm
Location: Vienna, VA

Re: Runtime licenses

Post by mightycpa » Thu Feb 01, 2018 1:09 am

Hi Marcus,

Is logging available in runtime? I don't really see that. It would be useful.

Similarly, I notice that the runtime does not have the ability to step through a script. I would ask that you think about including that ability or the logging, and let me explain why we would find that ability useful.

In our environment, development is done on a development server. That's where the Pro Version is installed. Using our configuration management system, we deploy our code to a test server, including MS scp files. These files are run using the runtime on that server. In our test environment, they like to throw a lot of scenarios at our applications, and usually the first couple of times, they find problems. It is difficult sometimes to create the same data on a development server as we have on the test server.

After our code passes muster in test, then we promote to production. MS .scp files are run there using the runtime as well.

What would be useful is either the ability to step through a script and examine the variable values, or to enable logging, just like we do in PRO, even if we can't necessarily do anything about it in test or prod. It's just a diagnostic step that would be great to have access to, especially if something goes wrong in prod. Our environment structure doesn't allow the promotion of exe files, so we can't use logging in that wy to accomplish what I'm suggesting.

What do you think?
"A facility for quotation covers the absence of original thought." - Lord Peter Wimsey

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Runtime licenses

Post by Marcus Tettmar » Thu Feb 01, 2018 2:29 pm

Yes, if you run the script via the command line you can specify a log file in the usual way:

msched.exe scriptname_or_file /LOGFILE=c:\bla\log.txt

See:
https://www.mjtnet.com/manual/index.htm ... ptions.htm

Right now to debug you'd need Macro Scheduler Standard but I will consider your points about allowing debugging in the runtimes.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts