Team,
I got a request from the client, where they need to monitor specific job flows on WCC.
I thought that global commands would be helpful on this case, but they need too many jobs/flows included.
Please see below the list of jobs / commands and let me know if you have another solution to accomplish their needs.
They want to create a specific global command for each box/job:
The Box Batches need to be added |
autorep -J n%|grep RU |
autorep -J n%|grep FA |
autorep -J cpa6% | grep 'FA' |
autorep -J cpa6% | grep 'RU' |
autorep -J cpa6% | grep 'SU' |
autorep -J n%new%tab%pl%daily% |
autorep -J n%new%tab%aff%daily% |
autorep -J n%new%tab%cl%daily% |
autorep -J n%icams% |
autorep -J n%chg%batch% |
autorep -J n%synch%ref% |
autorep -J n%capis% |
autorep -J npa6%daily% |
autorep -J npa6%dcs% |
autorep -J b7a6%ex%daily% |
autorep -J b7a6%ex%adp |
autorep -J b7a6%ex%Monday |
autorep -J b7a6%ex%monday |
autorep -J b7a6%ex%adp |
autorep -J b7a6%ex%daily |
autorep -J npa6%monthly |
autorep -J cpa6p1bxd_daily_other_process -q |
autorep -J cpa6p1bxd_morning_daily_jobs |
autorep -J cpa6p1bxd_daily |
autorep -J cpa6p1bxd_daily_remits |
autorep -J cpa6p1bxd_daily_audit |
autorep -J cpa6p1bxd_daily_process |
autorep -J cpa6p1bxd_daily_referrals |
autorep -J cpa6p1bxd_blmfld_print |
autorep -J cpa6p1bxd_daily_finish |
autorep -J cpa6%cp900* |
autorep -J cpa6p1bxw_amtsum_weekend |
autorep -J cpa6p1bxw_status_file_process |
autorep -J cpa6p1bxw_weekly_chargeoffs |
autorep -J cpa6p1bxm_mthly_allowable_feed |
autorep -J cpa6p1bxm_monthly_jobs |
autorep -J cpa6p1bxm_get_claims_data |
autorep -J cpa6p1bxm_single_source_feed |
Autosys 12.x
WCC 12.X
The solution you have is probably the best even though it is cumbersome.
there are other options I will list out below but all have their drawbacks as well.
Options 1:
You could modify all of the jobs so add a group attribute or application attribute
this would allow you to then run a single autrep command and use the -I or -B command line switch to pull all of the jobs at once.
Note:
The downside is that someone could use the same field to do a send event command and start all of the jobs at once.
Also, this may take considerable effort to modify all of the jobs.
Option 2:
Create a View for all of the jobs in WCC.
Note:
The downside to this is, depending on the actual number of jobs this could impact the performance of WCC or just be very slow.
Option 3:
Use REST AWES calls to return the job information.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0-01/reference/ae-web-services/manage-jobs.html#concept.dita_8cb4206f2f55b41de21ff673ae1441b79c4bdc2d_GETAEWSjobruninfomethodRetrieveJobRunInformationofaSingleorMultipleJobs
Example 1:
curl -X GET "https://<AEWS_SERVER>:9443/AEWS/job-run-info?filter=runStartTime%3E2023-04-05" -H "accept: application/json"
curl -X GET "https://<AEWS_SERVER>:9443/AEWS/job-run-info?filter=runStartTime%3E2023-04-05%3Bapplication%3Dabcd" -H "accept: application/json"