AutoSys Job Script Validation Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy AutoSys job scheduling systems require manual creation and deployment of environment-specific JIL files, leading to inefficiencies, lack of transparency, and increased effort in job management, with limited options for querying and deploying jobs across multiple environments.
Innovation Solution
An AutoSys automation framework that enables the generation, updating, and deletion of jobs using a single script across multiple environments, along with a validation system for pre-deployment checks to ensure script validity, reducing manual effort and improving deployment efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual deployment of environment-specific JIL files is used, then job scheduling can be performed in AutoSysTM, but deployment efficiency is low and manual effort is high
Solution Approach 1:
The system enables self-service deployment by automatically generating environment-specific JIL files from a single source script. The deployment tooling automatically handles file generation, validation, and deployment to multiple environments without requiring manual intervention for each environment, thus improving productivity and reducing manual effort.
Solution Approach 2:
A universal deployment framework is implemented that can deploy jobs to multiple different AutoSysTM environments using a single source script. The system universally handles different environments (development, testing, production) through standardized processes, eliminating the need for separate manual deployment procedures for each environment.
2Adaptability or versatility
If separate JIL files are created for each environment, then environment-specific job scheduling is achieved, but script complexity and maintenance effort increase
Solution Approach 1:
The system segments the deployment process into distinct components: a single source script, automated generation logic, environment-specific parameters, and deployment metadata. This segmentation allows the source script to remain simple while environment-specific details are handled separately through automated generation, reducing overall complexity.
Solution Approach 2:
An intermediary automated generation system is introduced between the source script and the environment-specific JIL files. This intermediary automatically transforms the single source script into environment-specific configurations, eliminating the need for manual creation and maintenance of separate scripts for each environment.
3Reliability
If manual validation of JIL files is performed, then deployment errors can be detected, but validation time and effort increase
Solution Approach 1:
The system performs preliminary automated validation of JIL files before deployment. Validation rules and checks are executed automatically as part of the deployment process, detecting errors in advance of actual job execution. This preliminary action ensures reliability while minimizing validation time through automation.
Solution Approach 2:
The validation system provides immediate feedback on JIL file correctness through automated error detection and reporting. The system validates syntax, required parameters, and environment-specific configurations, providing clear feedback messages that guide corrections without requiring manual review, thus maintaining reliability while reducing validation time.
4Loss of information
If comprehensive job information is gathered manually, then complete job transparency is achieved, but information-gathering effort and time increase
Solution Approach 1:
The system implements self-service information gathering where the deployment tooling automatically collects and aggregates complete job information from multiple sources. This includes source script details, generated JIL file contents, environment configurations, and deployment status. The information is automatically assembled and made accessible without requiring manual searching through directories or systems.
Solution Approach 2:
A universal information aggregation mechanism is implemented that can retrieve complete job information across all environments through a single query interface. The system universally collects data from source scripts, generated files, deployment logs, and runtime status, providing comprehensive transparency without requiring separate manual gathering efforts for each environment or information type.
Data Source
AI summary
Apparatus and methods may include a method for validating a script. The script may be a script for firing a job in an Autosys™ application deployed in a predetermined environment. The validating may use a validation system. The method may include providing a plurality of pre-deployment validation utility actions. The plurality of pre-deployment utility actions may include permitting only insert (INS), update (UPD) and delete (DEL) as actions in the script. The permitting may use an action name review utility. The plurality of pre-deployment utility actions may include permitting only command (CMD) or box parameter types (BMT) in the script. The permitting may use a parameter type review utility. The plurality of pre-deployment utility actions may include specifying only NULL, FDR and LMCTR as project codes. The specifying may use a project code specifier utility.