Mentor Tech Source is the result of 25 plus years of extensive experience in providing Hybrid Model Staffing and Engineering Services in the ever evolving Software Economy. ![]() ![]() Open support tickets with Computer Associates when required Backup definitions (jobs, VM, resources) Validate product end-of-life and compatibility matrix Assist development teams with job definitions (create/update/delete) software version, servers, network, ports, DB, etc.) Create and maintain up-to-date documentation (architecture i.e. Provide 365, 24/7 support in order to deliver a stable scheduling environment to the client Troubleshoot components/services whenever necessary (AWA, WCC, EEM, agents) and resolve any incident related to AutoSys Manage agent configuration (update agentparm as required) Manage EEM (security) configuration (update policies as required) Manage WCC (GUI) configuration (update config files as required) Manage AWA (scheduler) configuration (update config files as required) Also best practice is to run sendevent commands on the Autosys Event processor server so that if you are running dual server high availability and the system rolls over to single server mode, the sendevent command works after the roll over.- Install/update scheduler software (including fix/patches, SP, etc.) for AWA. This command has to be ran as the Autosys superuser account. The command is sendevent -E CHANGE_STATUS -s INACTIVE -J job_c. If job_c is inactive, job_a sees that starting condition as FALSE, but job_c will run the next time its starting conditions are met. In earlier versions you can run a job on the S of job_a that will change the status of job_c to INACTIVE. If it is R11, the newest version, you can set look back dependencies on job_a to only run if job_c has ran to S within X hours. The SAP Job Scheduling service awaits response for the synchronous job from the action endpoint for the specified duration. One or more authentication steps in the backup process are failing because they are attempting to use a password which is no longer valid. The solution depends on the version of Autosys you are using. Scheduled Vault backups no longer run after an account used by the backup process had a password change. Jobm is run via the OPC scheduler on the mainframe, which communicates job completion to Autosys. Is there an Autosys command that can be used to reset the status of job_m in the table? If not, is there a better method of enforcing this dependency than the one outlined above? 1 We have an Autosys job (let's call it joba) that has a 3am time dependency and is also supposed to await successful completion of a mainframe job (jobm, which in our case is always successful). Day 1 3am: job_c starts, sees no status change for job_m within the last 6 hoursĭay 1 4:02am: job_a runs following completion of job_cĭay 2 3am: job_c starts, sees no status change for job_m within the last 6 hoursĭay 2 5:02am: job_a runs following completion of job_c Our current proposed workaround is to have a job (job_c) that periodically checks the table and only complete if the status of job_m was changed in the last 6 hours. Day 1 4am: job_m completesĭay 1 4:01am: job_a runs, since Day 1 4am run of job_m was successfulĭay 2 3am: job_a runs, since Day 1 4am run of job_m was successful ![]() As a result, the job dependency will always be met after the first ever successful run of job_m, even though we are only interested in job_m runs on the same day. This status is not automatically cleared. My understanding of how Autosys works is that it writes an entry into a table in its database when job_m completes, and when job_a checks its dependencies, it looks in this table to see the status of job_m. Job_m is run via the OPC scheduler on the mainframe, which communicates job completion to Autosys. We have an Autosys job (let's call it job_a) that has a 3am time dependency and is also supposed to await successful completion of a mainframe job (job_m, which in our case is always successful).
0 Comments
Leave a Reply. |