Multi-factor validation for varying environments

Abstract

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.

What is claimed is: 
     
       1. A validation system for validating a script, said script for firing a job in an AutoSys™ application, the AutoSys™ application being deployed in a predetermined environment on an AutoSys™ server, said validation system comprising a processing device communicatively coupled to a non-transitory computer-readable medium, wherein the processing device is configured for executing program code stored in the non-transitory computer-readable medium to perform operations to validate the script, said validation system comprising:
 a plurality of pre-deployment validation utilities, wherein each of the plurality of pre-deployment validation utilities reviews the validity of a separate aspect of the script and, if the aspect of the script is found to be impermissible, returns an error message prior to deploying the script in the AutoSys™ application on the AutoSys™ server, the plurality of pre-deployment utilities comprising:
 an action name review utility, said action name review utility permitting only insert (INS), update (UPD) and delete (DEL) as actions in the script for use on the AutoSys TM server; 
 a parameter type review utility, said parameter type review utility that permits only command (CMD) or box parameter types (BMT) in the script for use on the AutoSys™ server; and 
 a project code specifier utility that enables a user to specify a project code associated with the script for use on the AutoSys™ server; 
 
 wherein each of said plurality of pre-deployment validation utilities reviews the script as part of the validating the script for use on the AutoSys™ server; and 
 wherein the script is further directed to a pre-determined deployment region that includes a production environment, and when said script is configured as a box for insertion of a second script therein and said script is validated, wherein said script is further configured to perform no actions other than to fire the second script such that the second script performs actions within the production environment, wherein said script fires said second script. 
 
     
     
       2. The validation system of  claim 1 , further comprising a job status utility that permits only NULL, INITIATE, COMPLETE or LOCK as status identifiers. 
     
     
       3. The validation system of  claim 2  wherein the job status utility does not permit a change of a job status from COMPLETE to LOCK. 
     
     
       4. The validation system of  claim 1 , further comprising a job name utility that prevents a job from being inserted into an AutoSys™ jobs table in electronic communication with the validation system when a name associated with the job being inserted currently exists in the AutoSys™ jobs table. 
     
     
       5. The validation system of  claim 4 , wherein the job name utility permits use of an update action or a delete action only when the job upon which the update action or the delete action is being deployed exists and is active within the system. 
     
     
       6. The validation system of  claim 1 , further comprising a box name utility that prevents the box from being inserted into an AutoSys™ boxes table in electronic communication with the validation system when a name associated with the box being inserted currently exists in the AutoSys™ boxes table. 
     
     
       7. The validation system of  claim 6 , wherein the box name utility permits use of an update action or a delete action only when a box upon which the update action or the delete action is being deployed exists and is active within the system. 
     
     
       8. The validation system of  claim 1 , wherein a job name associated with the job is limited to less than 64 characters. 
     
     
       9. The validation system of  claim 1 , wherein a box name associated with a box in which the job is contained is limited to less than 64 characters. 
     
     
       10. The validation system of  claim 1 , wherein, when a box in which the job is contained is under lock status, placing the job also under lock status. 
     
     
       11. The validation system of  claim 1 , wherein, when no scheduling conditions exist (DT_COND_TX=0), then the following fields in the job are null: a STRT_MINS field, a STRT_TM field, and a STRT_DY_NM field, and when at least one scheduling condition exists (DT_COND_TX=1), then a field STRT_DY_NM should not be null. 
     
     
       12. The validation system of  claim 1 , wherein, when no scheduling conditions exist (DT_COND_TX=0), then the following fields in the job are null: a STRT_MINS field, a STRT_TM field, and a STRT_DY_NM field, and when at least one scheduling condition exists (DT_COND_TX=1), then, either a STRT_MINS field or a STRT_TM field should be active, but not both the STRT_MINS field or the STRT_TM field. 
     
     
       13. A method for validating a script, said script for firing a job in an AutoSys™ application deployed in a predetermined environment on an AutoSys™ server, said validating using a validation system, said validation system comprising a processing device communicatively coupled to a non-transitory computer-readable medium, wherein the processing device is configured for executing program code stored in the non-transitory computer-readable medium to perform operations to validate the script, said method comprising:
 providing a plurality of pre-deployment validation utility actions, said plurality of pre-deployment utility actions comprising:
 permitting only insert (INS), update (UPD) and delete (DEL) as actions in the script for use on the AutoSys™ server, said permitting using an action name review utility; 
 permitting only command (CMD) or box parameter types (BMT) in the script for use on the AutoSys™ server, said permitting using a parameter type review utility; and 
 enabling a user to specify a project code associated with the script for use on the AutoSys™ server, said specifying using a project code specifier utility; 
 
 wherein each of said plurality of pre-deployment validation utility actions reviews the script as part of the validating the script for use on the AutoSys™ server; and 
 wherein the script is further directed to a pre-determined deployment region that includes a production environment, and when said script is configured as a box for insertion of a second script therein and said script is validated, wherein said script is further configured to perform no actions other than to fire the second script, such that the second script performs actions within the production environment, wherein said script fires said second script. 
 
     
     
       14. The method of  claim 13 , further comprising permitting only NULL, INITIATE, COMPLETE or LOCK as status identifiers, said permitting using a job status utility. 
     
     
       15. The method of  claim 14 , further comprising blocking a change of a job status from COMPLETE to LOCK, said blocking using the job status utility. 
     
     
       16. The method of  claim 13 , further comprising preventing a job from being inserted into an AutoSys™ jobs table when a name associated with the job being inserted currently exists in the AutoSys™ jobs table, said preventing using a job name utility. 
     
     
       17. The method of  claim 16 , further comprising permitting an update action or a delete action only when the job upon which the update action or the delete action is being deployed exists and is active within the system, said permitting the update action or the delete action using the job name utility. 
     
     
       18. The method of  claim 13 , further comprising preventing the box from being inserted into an AutoSys™ boxes table, said AutoSys™ boxes table in electronic communication with the validation system, when a name associated with the box being inserted currently exists in the AutoSys™ boxes table, said preventing using a box name utility. 
     
     
       19. The method of  claim 18 , further comprising permitting using an update action or a delete action when a box upon which the update action or the delete action is being deployed exists and is active within the system, said permitting the update action or the delete action using the box name utility. 
     
     
       20. The method of  claim 13 , wherein a job name associated with the job must be less than 64 characters. 
     
     
       21. The method of  claim 13 , wherein a box name associated with a box in which the job is contained must be less than 64 characters. 
     
     
       22. The method of  claim 13 , wherein, when a box in which the job is contained is under lock status, then placing the job also under lock status.