- Oct 10, 1999
- 26,001
- 1,484
- 126
At my job, I'm what they call a BatchAdmin. One of our responsibillities, is to provide support for the Operators when batch jobs fail. Every batch job that we support has what we call a "runsheet". These runsheets are basicly little FYI and HOWTO instructions for each batch job. They are supposed to include any input, output, archived, and temp files that any job uses. A list of all nested executables/scripts, as well as the path & name of the executable that the job runs. These runsheets have about 100 fields, and they are all important since anything missing from the runsheet, can cause big problems in the event of a job failure.
One project my boss has me doing currently, is looking through our job scheduler, and then making a list of all jobs for a certain "Event" (think of it as a bigass group of jobs, we have several events with 150+ jobs in them.) Once the list is made, I go through every line of the code checking what files it uses, what resources it uses, what other boxes it connects to, etc (the batch jobs are all ksh scripts, they average about 500 lines each, and there are several thousand of them.) For each and every job, I'm updating at least 15 fields on the runsheets (the runsheets often haven't been updated in 5 years, while the jobs tend to be updated at least once or twice a year to keep up with software rollouts.) I am one of 2 people in my group that can script in the Korn shell. The other person can write some pretty good code, however, he's a slow typer, so he doesn't script very often.
Cliffs: I go through thousands of lines of code to update our documentation at work.
One project my boss has me doing currently, is looking through our job scheduler, and then making a list of all jobs for a certain "Event" (think of it as a bigass group of jobs, we have several events with 150+ jobs in them.) Once the list is made, I go through every line of the code checking what files it uses, what resources it uses, what other boxes it connects to, etc (the batch jobs are all ksh scripts, they average about 500 lines each, and there are several thousand of them.) For each and every job, I'm updating at least 15 fields on the runsheets (the runsheets often haven't been updated in 5 years, while the jobs tend to be updated at least once or twice a year to keep up with software rollouts.) I am one of 2 people in my group that can script in the Korn shell. The other person can write some pretty good code, however, he's a slow typer, so he doesn't script very often.
Cliffs: I go through thousands of lines of code to update our documentation at work.
Facebook
Twitter
Instagram