| Each utility listed below describes the problem it is designed to solve. For details on how the tool functions (syntax, return codes, error messages, etc.) click on the name of the script listed that solves that particular problem.
Automate file transfers on any O/S with verification and error reporting
Since file corruption generally decreases the original file size, this script uses file size comparison as a basis for file corruption detection. Once a minimum file size is defined, this process will match the size of the file to be transferred against the specified amount. If the size of the file does not exceed the defined minimum, the transfer is cancelled.
|
|
|
Copies and processes (rcp) files from one directory to another. Compares the size of the files with minimum sizes defined by a parameter. If the files match the specific minimum size, moves them to another directory. If the files does not match and the time period expired (specified by a parameter) has expired, the process is killed.
|
Automate file uploads with error reporting
Scheduled backups are essential in every business setting, as is the ability to automate scheduled file uploads into a backup location. These tools can be incorporated with a scheduler to transfer a working file to a backup location on a regular basis with error reporting for easy troubleshooting.
|
|
|
Issues a put command within FTP to a file with error checking and reporting.
|
|
|
|
|
|
|
Issues a Mput command within FTP to a group of files with error checking and reporting. This tool allows for the transfer of an entire directory.
|
Automate renaming of files
With this script, you can automate this process of renaming files. If desired, it will automatically rename the original file with an .old extension.
|
|
|
Substitutes a given string within a file name. Renames the old file with an .old extension if desired.
|
AutoSys specific – Filewatch job using wildcard and terminate at a specific time instead of term_run_time.
When the arrival of a file is used as a trigger for further processing, but the name is random or changes, use this tool to allow filename wildcarding. This tool also allows you to terminate the filewatch job at a specific time, instead of term_run_time.
|
|
|
Allows Filewatch to use filename wildcarding and to also terminate at a specific time, instead of AutoSys' term_run_time.
|
AutoSys specific - Reset all JIL to INACTIVE
On occasion, it may become necessary to reset all JIL within a production environment to INACTIVE. With this utility, you can automatically place all jobs to the status of INACTIVE.
|
|
|
Resets all JIL to INACTIVE. Also verifies that a job is not ON_ICE. If ON_ICE, the program asks if you would still like to place job ON_ ICE.
|
Check for the size of a file that should always be consistent
When a file is generated from another process, it may not always complete correctly or have complete data. When the file's dependant process runs anyway, this can cause a chain of errors to occur. This utility prevents this by checking on the size of the file before it is sent to another process.
|
|
|
Checks file size. If the file size is less than the desired minimum, an error report is generated.
|
Check header files for changes within a specified time
A file needs to be updated every two days, but you're not sure if its companion process completed the update. If the file is not updated on that specific date, the information it may pass to another process could be out-of-date and cause a series of problems. With this tool, you can check the header of the file to ensure it was modified by the correct date, before the file is sent to a downstream process.
|
|
|
Checks if there are delimiters in the file header. If there are delimiters, prints name of file and date. This is useful when you desire a check to see if a header changed within a file at a specific time.
|
Check record lengths of a particular file
It may be necessary to verify the length of records in a particular file. For example, in bank records, the account length must be an exact number of digits. This script performs that functionality in an accurate and efficient manner.
|
|
|
Checks each record to see if it is a specified length.
|
Delete files on a remote system with error reporting
The ability to maintain multiple systems from one central location enables efficient systems administration. With this script, a user with the appropriate access rights can delete files on any remote machine. Any errors encountered during this process can be printed for troubleshooting purposes.
|
|
|
Issues a delete command within FTP to a file and wraps error checking into the routine, printing a report if there are any errors during the deletes.
|
Retrieve files from a remote system without a user name or password
Have you ever needed access to a certain server just so you can retrieve a file? Instead of waiting for a login user name and password, you can use the generic login information. The generic name and password allow for read-only access, and are created by UNIX administrators. Since users cannot make any changes to the files using the generic access ID and password, this information can usually be provided immediately by the system administrator and eliminates any down time. Any errors encountered during this process can be printed for troubleshooting purposes.
|
|
|
Issues a get command within FTP to a file and wraps error checking into the routine, printing a report if there are any errors during the get.
|
Shut down a process at a given time
It is often necessary to shut down a particular process at a given time (e.g. 12:00pm). This script will perform that functionality with error checking. The process will automatically finish at that specified time with a normal shutdown. If the process shuts down early, the script will assume there is a problem and will return an exit code so that the error can be determined.
|
|
|
Cleanly shutdown processes at a specific time. If process ends early, assumes a problem and gives an exit code in an error report.
|
Solve complex copying needs
It may be necessary to set up jobs that have complex copying needs. For example, you may need to copy a series of files and if one file fails to copy the process is interrupted. Below are three different copy utilities.
|
|
|
Copies specified files, single or multiple, from one directory to another, even if a failure occurs in a single file copy. At the end of the file transfer, a report will print any errors. |
|
|
|
Copies database records from one file to another.
|
|
|
|
Copies (rcp) files from one directory to another on a remote machine. Wraps the rcp command with error checking to make sure the program exits properly and prints a report if errors occur.
|
Solve complex scheduling needs
Every environment has interfaces that have complex scheduling needs. Some interfaces need to run repetitively, immediately after a stable point has been reached. This utility will automate this process.
|
|
|
Repetitively reruns an interface when it reaches a stable point and can be restarted.
|
Some interfaces need to run repetitively until the interface reaches certain circumstances that would prevent the next run of the interface. The second utility has the capability to solve this problem.
|
|
|
Reruns an interface until the interface exists with a certain exit code. This means that a situation has arisen that would compromise the environment if the interface reran at that time.
|
On occasion, it is necessary to run an interface that is dependent on another condition. The user can set up a specific time the interface runs, while still keeping the earlier dependencies, so the interface will run at the specific time desired.
|
|
|
Reruns an interface based upon the conditions being met and/or during the time window. This will allow the interface to not run at a time when the conditions have been met, but the conditions were met outside the specified time window.
|
SQL made easy
This utility allows a user to execute SQL commands easily and provides a detailed report of any errors.
|
|
|
Simulates SQL, but gives better error reporting and can automate the SQL process.
|
Watch for unwanted files
In most organizations, various file naming conventions are used. When incorporated with scheduled jobs, this tool allows for file watching.
|
|
|
Checks the name of a file header until it changes, or a shutdown time is specified. Useful in checking to see if a filename has changed within a specified time.
|
This second tool can check to make sure that the file trailer contains only characters and no numbers. If an unwanted file name is detected, then an alarm will appear. Since you can define the shutdown time of these processes, you can prevent them from running beyond the job's time frame.
|
|
|
Checks trailer string until changed or shutdown time; also checks to make sure file is current. Useful for matching trailers within separate files.
|
© 2002 Stirling Systems Group, LLC
All Rights Reserved.
|
