Job Simulate – 06/09
It is possible to 'simulate' the run of a job. When a job is simulated, the system acts as though the job actually ran, except that the command line isn't actually executed.
More>>
Job Dependencies – 05/07
Two very powerful features of GECS are the ability for jobs to be configured to repeat and the ability for jobs to run in a specific sequence using job or batch dependencies. More>>
Moving Batches Between Environments – 02/07
At some point you may need to move batches from one system to another—for instance, from your QA/Dev environment to your production environment. To do this, you will use a tool from the command line in order to save your batch into a single file that contains all of the jobs, schedules, variables, and batch dependencies. More>>
System Monitor / Watchdog Batch – 01/07
To help ensure your GECS System is always running appropriately, using a few simple steps, you can create a batch file to monitor each of your GECS components. You can also set up and send SMTP email messages from a command line in order to test email addresses and servers. More>>
Creating a Mail Group – 01/07
Set up your Event Definition to automatically “send alerts to” or “send mail to” a group of users. Set up different groups and specify which group should be notified for which Event. More>>
Run One Job that Schedules a Batch Containing 50 Jobs – 01/07
It may be necessary to gather 50 jobs into one because of dependencies and sequences, because of On Demand jobs, or in order to simplify views. The command line utility named GECSBATS.EXE can be used to schedule a batch of jobs in the background via a command line or GECS job. More>>
MORE TECH TIPS>>
|
