You can use the GECS Administrator Web Client to monitor and manage your GECS jobs.
Retry a Failed Job
Use the "Retry on Return Code" field to retry a failed job.
You can enter text in the Batch Metadata field. This text can then be used for filtering job views to make it faster and easier to find your GECS jobs.
Creating an FTP Job
File Transfer jobs execute FTP commands between the GECS Windows Agent and your FTP, FTPS, FTPES, SFTP or SCP server. Traditional FTP commands such as GET, PUT are supported.
Using Encrypted Credentials
GECS can automate your jobs securely by allowing you to define credentials with encrypted passwords. These credentials can be used when GECS launches a job.
SQL Query Samples
This document contains a variety of sample SQL Queries that customers have requested in the past. These samples are provided as a starting point for your own custom reporting if you need details outside of the lists offered using the GECS Administrator program.
Web Browser Client - Batch Studio
The v4.80 Web Browser Client contains a Batch Studio organizational tool used to create, illustrate, and arrange GECS batch jobs into logical job streams.
Notification lists make it easy to store, share, change and reuse email and user group information.
Fine Tuning and Maintaining GECS
Here are some ways to keep GECS running at maximum performance.
Pause GECS with a Scheduled Job
You can schedule a job via GECS that launches a batch file to cause the GECS components (system manager and controller) to temporarily pause for a predetermined amount of time.
Invite GECS Users to Access the Web Client
You can configure GECS to send email to your GECS users inviting them to access the GECS Web Client Administrator.
Scan Output Through a File
In most cases the scan output fields will be sufficient to determine the return code based on the captured output, but in some situations you might need more flexibility. In this case you can use a scan file by specifying the file name.
Resources represent hardware, software, or other things (hardware or software, physical or logical) that are needed by jobs. Resources are limited in quantity either because only certain GECS Agents have them or there is a limited quantity of them on the system. Consequently, resources are either assigned to specific Agents or they are system wide resources.
WRK (pronounced work) files are one of the most powerful features of GECS. WRK files are used to add jobs or batch jobs to the GECS system without using the GECS Client programs.
FTP Trigger Files
Jobs and depend on the presence or absence of single or multiple files. The trigger files can be entered in either standard drive/subdirectory format or in FTP format.
Manging Service Level Agreements (SLAs)
GECS can indicate that batches are governed by an SLA and the system will ensure that the batch completes before the required time. GECS allows you to define the SLA Time, the time before which the batch must be complete, in one of 3 different ways.
Change File Names with FTP
ECS Agents have the ability to rename files when they are transfered with MGET or MPUT using FTP.
Change Name Utility
The change job name utility, GECSCNUM, can be used to allow you to change the job name/number of an existing job and or batch.
GECS has the ability to use user defined custom Variables. These Variables work much like substitution Variables except they are pre-definded by the user.
Connection Strings for SQL Jobs
ODBC connection information can be entered in the ODBC connection directly, using a connection string without needing to create an ODBC DSN locally on each agent computer for SQL Jobs or SQL variables.
Batch Summary Report Utility
The Batch Summary Report Program, GECSSUMM, produces a list of jobs for a range of batches and summarizes the number of times the jobs ran successfully or failed during the date range specified.
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.
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
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
To help ensure your GECS System is always running appropriately, GECS ships with a "Watchdog" utility. This program installs a Windows service that periodically pings the System Manager program and sends an email if the System Manager program fails to respond to the ping. More>>
Creating Notification Lists
Notification lists make it easy to store, share, change and reuse email and user group information. The Notification List entries can be GECS users, email addresses or the names of other GECS Notification Lists. More>>
Run One Job that Schedules a Batch Containing 50 Jobs
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>>
Multiple job records and multiple event definition records can be updated at the same time when using the GECS v3.60 Windows Administrator Client program. When using the bulk update feature, only the fields that you enter information into will be changed.
GECS Events writing to a file
Global ECS can write job event notifications to external files. This can be helpful when using separate system management software to monitor jobs or job statuses.