Single Script Framework for AutoSys JIL File Generation
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 for job management, with limited options for querying and deploying jobs across multiple environments.
Innovation Solution
A single script framework generates JIL files for multiple environments, utilizing an AutoSys jobs table that includes job information, attributes, and SQL content to automate job creation, update, and deletion, providing a configurable interface and multi-factor validation for deployments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual deployment application is used to deploy JIL files, then deployment can be performed, but deployment time is excessive and manual effort is high
Solution Approach 1:
The system performs preliminary actions by pre-generating JIL files in a library using a single script framework before actual deployment. The files are prepared with environment-specific parameters already configured, so that during deployment only the selection and instantiation are needed, dramatically reducing deployment time and manual effort.
2Adaptability or versatility
If separate JIL files are created for each environment, then environment-specific requirements are met, but the number of files increases and maintenance effort increases
Solution Approach 1:
A single JIL file template serves multiple environments through parameterization. The framework allows one master JIL file to be instantiated across different environments (development, testing, production) by substituting environment-specific parameters, eliminating the need to maintain separate JIL files for each environment while still meeting environment-specific requirements.
Solution Approach 2:
The system changes parameters within a single JIL file template to adapt to different environments. By modifying parameter values (such as connection strings, environment names, configuration settings) rather than creating separate files, the system achieves environment-specific functionality while reducing file complexity and maintenance burden.
3Ease of operation
If JIL files are fully manually created, then flexibility is achieved, but standardization is lost and errors increase
Solution Approach 1:
The system performs self-service by automatically generating JIL files through a framework that uses stored templates and parameter substitution. The automated generation process ensures consistency and standardization while maintaining flexibility through configurable parameters, eliminating manual creation errors and establishing standardized formats without sacrificing operational flexibility.
4Loss of information
If job information is scattered across multiple files and directories, then detailed information is available, but transparency and ease of querying are reduced
Solution Approach 1:
The system merges scattered job information into a centralized JIL file library with a unified structure. All job definitions, parameters, and metadata are consolidated in one location rather than dispersed across multiple directories and files, improving transparency and making querying easier while preserving all necessary job detail information through the standardized template structure.
Data Source
AI summary
Apparatus and methods may include a method for using a single script framework to generate a plurality of JIL files. Each of the plurality of JIL files may be for use in one of a plurality of multiple environments. The methods may include providing, based on the jobs information, the jobs attribute values and the SQL content, parameters to create a job, update a job and/or delete a job. The providing may use an AutoSys™ jobs table. The AutoSys™ jobs table may include jobs information, jobs attribute values, and Sequel (SQL) content to be run.