Main News Suggestions Training Tech Tips Upgrades
   
    Go to Recent GECS Tech Tips
     
 


There may be several reasons why someone would need to create one GECS job that schedules a GECS Batch containing 50 Jobs. Reasons may include:

1. Dependency issues – a batch of jobs may contain job dependencies to allow the batch to run in a specific sequence. This batch may need to start and before all of the jobs in this batch complete, a new instance of this same batch may need to start again.

 
 
2. On Demand jobs – a batch may contain many jobs
 

that only run on demand. It is best not to have jobs waiting in the pending queue that may not need to run very often.

3. Simplify Views – 50 or more jobs displayed in a view may use up a lot of space on your computer screen. If you have many jobs within your GECS batches you could have one job pending that schedules your batches of many jobs, then when the batch completes your single job can reschedule and only create the many jobs from the batch when it is time for the batch jobs to run.

The GECS command line utility named GECSBATS.EXE can allow you to run one job that schedules a batch of 50 jobs.

This utility can be used to schedule a batch of jobs in the background via a command
line or GECS job.

The Schedule Batch Jobs program is started with the name of the desired Batch passed on the command line. The program will immediately schedule the designated batch. You must also specify the beginning and ending date range for the jobs to be submitted. Entering values of 00/00/0000 will indicate ‘today’.

You must also specify the first instance number to be used for the jobs. Entering an instance number of ‘0’ will cause the program to use the next available number. Lastly
you need to specify the GECS user name of the submitter. The program will not stop and prompt for Batch Variables. If any are defined for the Batch, the default values for the variables will be used. This will allow the scheduling of a Batch to be automated (run unattended) as a GECS job.

GECSBATS.EXE [/N] batch begdate enddate instance user
The ability to run GECSBATS.EXE has enormous potential for automating the scheduling of individual batches. These executable programs can be run as standard GECS jobs. By running GECSBATS.EXE as a job, it is possible to daisy chain batches. Consider creating a batch which has as its last step, an item which will run GECSBATS.EXE passing the name of the next batch to run. In this way, you can create dependent batches.

The optional /N command line option causes a number to be added to the end of the batch portion of the job number when the batch is submitted. The number will cause the batch to be unique in the system.

For example, if you submit the APPLE batch, the batch portion of the job number would be APPLE0. If you submit it again, the batch portion would be APPLE1. The numeric portion can range from 0 to 999. If the batch portion is 17 characters or less in length, the number is added to the end. If the batch portion is longer than 17, the last 3 characters are overwritten by the number. Normally a batch should not be scheduled until the previous submission is complete.

This allows a batch to be submitted multiple times such that they overlap without the
submissions stepping on each other.

The GECSBATS program is a Windows command line program that is installed with the Controller/DBMS.

 
 
 

Tech Tips by Category

[+/-] Administration (1)

Moving Batches Between Environments - 02/07

[+/-] Monitoring (2)

System Monitor / Watchdog Batch – 01/07

Viewing Multiple GECS Environments – 01/07

[+/-] Notification (3)

Creating a Mail Group – 01/07

Notifying Users via Internet Mail – 05/05

Web Clients – 07/03

[+/-] Scheduling (5)

Simulating Job Runs - 06/09

Job Dependencies – 05/01

Schedule a Batch via a Job – 01/07

Update Jobs in Bulk – 01/07

Activate Jobs Remotely – 09/02

[+/-] Security (2)

Auditing – 08/06

Using Networking / No Networking – 12/06

[+/-] Utilities (0)

Coming Soon!

If you have an idea for a Tech Tip, send us an email.