How can we set 24X7 running on a dedicated machine in the server room to run a job submitted (via a 24X7 /SCRIPT AAA.JDL command) by any of the workstation of the network.

Thanks.

Mon Jul 31, 2000 4:02 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

Re: Remote submit

You can setup a "file-watch" job to monitor some predefined directory for AAA.JDL and as soon as it is found, run the 24x7 /SCRIPT command. This does not require any scripting. However, you face some concurrency problems as user B can override file created by user A before this file is executed.

For this sort of task you should install 24x7 Remote Controls on user workstations so they submit their jobs directly to the 24X7 running on a dedicated machine (24x7 server)

If you decide to stick with a file-based approach you can also make a more complicated job that monitors *.JDL files using file mask then you will need to write some script to find these files (you can use, for example, the Dir statement) and execute them one by one. Still concurrency is a problem.

: How can we set 24X7 running on a dedicated machine in the server room to run : a job submitted (via a 24X7 /SCRIPT AAA.JDL command) by any of the : workstation of the network.

: Thanks.

Mon Jul 31, 2000 5:17 pm

Luc Cloutier

Joined: 31 Jul 2000Posts: 10

Re: Remote submit

I am impressed about the speed and accuracy of your answer. You understood perfecly the kind of problem I'm having. Thanks !

The precise problem is that my users are running a VB application that creates .JDL files (They are all different: UserDateAndTime.JDL) in a unique network directory who becomes full of .JDL files. The semaphor trigger function works perfectly to find when a new .JDL appears because it works with wildcard (*.jdl). But the /SCRIPT switch does not allow me to "24X7 /SCRIPT *.jdl" to submit all those scripts.

Does installing the Remote Control Module on all my user workstation is the only way for me to submit a JDL directly to a 24X7 server ? And do I need a license for every workstation ?

: You can setup a "file-watch" job to monitor some predefined : directory for AAA.JDL and as soon as it is found, run the 24x7 /SCRIPT : command. This does not require any scripting. However, you face some : concurrency problems as user B can override file created by user A before : this file is executed.

: For this sort of task you should install 24x7 Remote Controls on user : workstations so they submit their jobs directly to the 24X7 running on a : dedicated machine (24x7 server)

: If you decide to stick with a file-based approach you can also make a more : complicated job that monitors *.JDL files using file mask then you will : need to write some script to find these files (you can use, for example, : the Dir statement) and execute them one by one. Still concurrency is a : problem.

Tue Aug 01, 2000 8:57 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

Re: Remote submit

That's correct, you cannot use "24X7 /SCRIPT *.jdl". But a script with FindFileFirst and FindFileNext in a loop (or Dir with GetToken in a loop) can do the trick. Still this is not a bulletproof solution, but it may work if your users create just a few files a day. So if once in a year you have a problem with duplicate or locked files, you may be able to live with this.

As for the user workstations, you need a separate license for every installation. Also consider the fact that the 24x7 Scheduler is rapidly moving in that direction. More a more features will added in a near future to support multi-user and Web-to-job functionality. The new version 2.3.0 is already changed to capture user and terminal information. Check it out.

: I am impressed about the speed and accuracy of your answer. You understood : perfecly the kind of problem I'm having. Thanks !

: The precise problem is that my users are running a VB application that : creates .JDL files (They are all different: UserDateAndTime.JDL) in a : unique network directory who becomes full of .JDL files. The semaphor : trigger function works perfectly to find when a new .JDL appears because : it works with wildcard (*.jdl). But the /SCRIPT switch does not allow me : to "24X7 /SCRIPT *.jdl" to submit all those scripts.

: Does installing the Remote Control Module on all my user workstation is the : only way for me to submit a JDL directly to a 24X7 server ? And do I need : a license for every workstation ?