Wow, such a wide specter of tasks to be automated. Here is how you can do it.
1. To create a "void" job, create job of JAL script type with the script like containing comments only, like one on the next line
//
That's all. It can have any schedule 2. Have you tried 24x7 GUI MacroRecorder?
You can also build a VBSCript job that will run in 24x7 but use Word COM automation to manipulate word activity?
Also take a look at 24x7 InputBox JAL statement that can be used create list of questions presented to the operator. Input type for these question can be defined as YES/NO, this will require from the operator to enter Y or N for each question or cancel the dialog (causing job failure and stop) 3. Sure you can create your "custom" triggers. Most common way to do it is to create an "asynchronous" script job that starts on "on startup". Such job runs in the background, never stops and instantly checks/monitors the desired events. If such event is detected the job either does the required processing itself or calls some other job, batch, or script to respond to the detected evens. Using this method you can implement virtually any event monitoring, monitor files, directories, other programs, use DDE to talk to other programs, call external functions using CALL, check NT event logs, check data in a database, etc... : Hi !! : I have these three questions which might be suggestions for possible
: features(if not in place today), that I will try to explain with three
: different use cases. : 1) My father is a very old man, with a weak heart, and takes regularly up to
: seven different medicines. Some of them must be taken every 8 hours, some
: other once a day, some every second day. One reason why I was evaluating
: 24x7 is as a forecast engine, just to calculate the scheduling of these
: seven medicines and print out a report in advance.
: The question is how can I create "void" jobs?, I mean jobs that
: neither are execution calls nor sql commands nor vbscripts ? . Without the
: possibility of a void job I get error when execution occurs, since so far
: I have created empty execution jobs. I could of course create the
: executing of a DOS "dir" command, or similar harmless
: executions, but maybe there is a more elegant solution. : 2) The network administrator at the company where I work has a list of tasks
: that have to be performed at regular intervals. Those tasks that can be
: performed by software, can perfectly be taken care of by 24x7. Those tasks
: that require human intervention are so far managed manually: we make check
: lists in word and print them out so that the person in charge can write a
: mark on a checkbox next to every activity. It'd be nice if 24x7 could also
: take care of those manual jobs, by providing a user interface for those
: checking boxes, and reporting which ones are still unperformed, so that
: all regular activites ( both automatical and those that required human
: intervention) could be managed by the same program. : 3)As I understood,24x7 supports 6 different types of triggers: Time
: watch,File watch,Process watch,Email watch,User watch, and System watch. I
: would like to know if there is support for users creating
: "drivers" to create "custom" triggers. For example: in
: the same PC where 24x7 is running I have a program who monitors constantly
: temperature in an industrial oven. When temperature goes over a certain
: limit then the system start a series of measures to get it back to normal.
: That control system has "hooks" so that I could propagate the
: alarm to other interested programs. Since that control system cannot send
: email, I thought of coupling it to 24x7 to trigger the sending of an email
: when an alarm event occurs. This "coupling" between the two
: systems can be via hardware ( by reading a bit in an input port line until
: it changes status) or by software ( DDE messaging, MSQUEUE or something).
: Does 24x7 have support for the creation of new triggers...like a
: "driver" or something ? : Thanks, : Ariel/
|
