UNIX for Dummies Questions & Answers

Okay I am not the best at UNIX, so please excuse this if it is a complete ID 10-T error (look at that for a moment...)

Logging in via telnet to the server, I want to create a cron job to run various "canned reports" in SAS on a regular basis. No problem, I have the directories, .profile locations, etc... but actually setting it up is CONFUSING.

Where do I go to type in the string 01 05 * * 6 <username> <profile> <att1> <att2> type field?

I have run crontab -e <userid> and it shows two jobs my admin set up for me... I hit "i" to insert a new line... but it only inserts one line (the entire command is 4 lines).

Please help me figure this out! And THANK YOU!!!

This is what I am trying to write in:

Code:

00 04 * * 5 ksh -c ". /directory/userid/.profile; nohup /sas_directory/sas /directory/userid/program.sas  -work /localhome/sastmp -log /directory/userid/program.log >/directory/userid/program.log 2>&1

Since the entire command is toooo long as you say, it is a good practice to put such things in shell scripts and add it your cronfile

I'm not quite sure I understand your issue.

The command you've given is only 1 line (albeit a long one) - what are the other 3? Or is it just wrapping on your screen?

You'd probably be better off putting it in a shell script anyway, and just calling the script from cron.

It's a WW2 tank gun!

Knowing what SAS and cron produce the end isn't a good idea also
so your script contains:

Code:

. /directory/userid/.profile; 
nohup /sas_directory/sas /directory/userid/program.sas  -work /localhome/sastmp -log /directory/userid/program.log

And your line :

Code:

00 04 * * 5 <path2yourscript>/script >/directory/userid/cron/program.log 2>&1

It's wrapping on the screen. I start writing it, it gets to the sas directory path (all the paths have at least 4-5 folders), and then returns to the first character of that row.

I have no idea how to write a shell script... or if I even have permission to do such a thing. IT keeps all permissions tightly pinned down at my company.

Not quite. ID 10-T = IDIOT. Nice way of insulting a "luser" to his or her face and then getting the response, "Oh, I think I've heard of that error!"

And you can also save locally your cronfile:

Code:

crontab -l>mylatest_cronfile

then edit with vi...
And load it again:

Code:

crontab mylatest_cronfile

And so you have a backup... Can be helpful sometimes...

vbe... what do you mean the end isn't a good idea?