Autosys Job
Moderators: chulett, rschirm, roy
Autosys Job
Can anyone direct me to good website that gives information about how to develope an autosys job and how scripts are used in autosys job. I can't find proper information on the internet. I need to develop an autosys job that gives an e-mail notification when an incremental load is complete in production.
Thanks
Thanks
Regards
Kashif Khan
Kashif Khan
Seems to me you have at least two choices. What people typically 'schedule' is a script that wrappers the dsjob command. If you want to build that functionality into the script itself, that would be one answer that is not AutoSys specific.
Otherwise, I would think it would be trivial to just tell them they need to perform the notification themselves on job completion. It should all be built into the tool.
Otherwise, I would think it would be trivial to just tell them they need to perform the notification themselves on job completion. It should all be built into the tool.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I understand I need to have a script to do a Email notification. I do have the script almost ready. But I believe there is a GUI kind of autosys tool that is exactly same like datastage and it has various icons to perform various functions like we have stages in Datastage. I want to read about that GUI interface autosys tool. I don't have any knowledge about it.
Regards
Kashif Khan
Kashif Khan
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It appears you can do the e-mail notification in at least three places;
1. Wrap your DataStage in a Sequence and do the e-mail from the Sequence.
2. Wrap the DataStage job in a UNIX script and do the e-mail notification from the UNIX script.
3. Call the DataStage job from Autosys and have Autosys manage the e-mail notification.
To me, a UNIX script is the method of last resort since the functionality is buried in code and other established methods are probably available.
The other two choices depend on the philosophy of your company using DataStage/Autosys. What is the purpose of Autosys at your site? Is it to schedule, run and notify? Or just schedule and run? If so, then I would code the notify in a Sequence.
My first choice is to always have a given tool at a given site do the job it was purchased to do. In other words, I try to use Sequences for integral units of work and not as a scheduling tool if a scheduling tool is available. I use a Sequence to schedule and accomplish multiple tasks when no scheduling tool is available (in concert with cron).
I would echo Chulett in that you need to find out if the Autosys boys will do the notify for you. If you have Autosys then supposedly you would also have an established Autosys infrastructure for some level of Job success/failure notification. Find out if this includes e-mail notifications.
1. Wrap your DataStage in a Sequence and do the e-mail from the Sequence.
2. Wrap the DataStage job in a UNIX script and do the e-mail notification from the UNIX script.
3. Call the DataStage job from Autosys and have Autosys manage the e-mail notification.
To me, a UNIX script is the method of last resort since the functionality is buried in code and other established methods are probably available.
The other two choices depend on the philosophy of your company using DataStage/Autosys. What is the purpose of Autosys at your site? Is it to schedule, run and notify? Or just schedule and run? If so, then I would code the notify in a Sequence.
My first choice is to always have a given tool at a given site do the job it was purchased to do. In other words, I try to use Sequences for integral units of work and not as a scheduling tool if a scheduling tool is available. I use a Sequence to schedule and accomplish multiple tasks when no scheduling tool is available (in concert with cron).
I would echo Chulett in that you need to find out if the Autosys boys will do the notify for you. If you have Autosys then supposedly you would also have an established Autosys infrastructure for some level of Job success/failure notification. Find out if this includes e-mail notifications.
Re: Autosys Job
Hi,
You have write a unix shell script. Within this you write command
mail -s <Subject> -b <abc.dat> -t xyz@pqr.com
Suppoose this script name is www.sh
Now call this www.sh from your autosys schedule like this -
insert_job: job_type: c
command: www.sh
machine:
#owner:
permission: gx,mx,ge,me
condition:
description:
std_out_file: /asyslogs/$AUTO_JOB_NAME.$AUTORUN.$$.out
std_err_file: /asyslogs/$AUTO_JOB_NAME.$AUTORUN.$$.err
alarm_if_fail: 1
profile:
job_load: 1
priority: 1
You need read some books or some documents to use autosys. Its a very good tool for scheduling.
Thanks -
Pranab Das
You have write a unix shell script. Within this you write command
mail -s <Subject> -b <abc.dat> -t xyz@pqr.com
Suppoose this script name is www.sh
Now call this www.sh from your autosys schedule like this -
insert_job: job_type: c
command: www.sh
machine:
#owner:
permission: gx,mx,ge,me
condition:
description:
std_out_file: /asyslogs/$AUTO_JOB_NAME.$AUTORUN.$$.out
std_err_file: /asyslogs/$AUTO_JOB_NAME.$AUTORUN.$$.err
alarm_if_fail: 1
profile:
job_load: 1
priority: 1
You need read some books or some documents to use autosys. Its a very good tool for scheduling.
Thanks -
Pranab Das
Re: Autosys Job
Maybe so. We use Control-M and I've never felt the need to read any books about it - we've got dedicated "peoples" for that. They read the books. I tell them what I need.pranabdas wrote:You need read some books or some documents to use autosys. Its a very good tool for scheduling.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers