UNIX Job Setup Request

To be completed by the Developer and submitted to ETL Administration (ITEAETLAdmin@exchange.purdue.edu).

This is the 2-4 character identifier for the system. It will also be the name of the directory beneath the $HOME directory for AUTOPCA, AUTODBA, AND THE "OPER" accounts. E.g., "HR" or "UD" or "ECOM"

System Name

Project Name

This is an area within the system that helps you logically group a piece of the system. E.g., "totcomp" or "giving" or "bowltix"

Base Job Name

This is created by combining the System Name with the Project Name and some meaningful identifier. E.g., "hr_totcomp_analyze_tables" or "ud_giving_load" or "ecom_bowltix_purge"

Purpose Submitted By

This should be a short description of the job, such as "Analyzes all the Total_Comp tables", or "Loads the Giving Data" or "Weekly purge of Bowltix records." The name of the person submitting the form

Date Submitted

The date the form was created

Date Needed

The date the job should go into production

Job Components
Machine Where Files Exist
The name of the machine on which the files exist.

Directory Name
/bin /ctl /doc /lib /log /mail /par /scripts /sql /tmp /stage Command to Execute:

UNIX File Name(s)

Any files that contain executables, such as compiled C code. Any SQL*Loader control script file. Extension will be .ctl Any documentation for the job. Extension will be .doc or .txt Any executables that are shared. Any files that are written by the job. Any mail files that are created, or files of recipients that are created by a job Any parameter files for Oracle exports. Extension will be .par Any UNIX script files. Extension will be .ksh or .sh Any SQL*Plus script files. Extension will be .sql Any files that are created by the AutoSys job and can be overwritten these are temporary output files from the job All files that are to be "promoted" to the next level of development (to QA or Production)

$JOBBASE/ ___ yes ___ no

Database Object Migration Request Attached?

/opt/scribd/conversion/tmp/scratch2422/65850717.doc

Page 1 of 4

08/23/11

/opt/scribd/conversion/tmp/scratch2422/65850717.doc

Page 2 of 4

08/23/11

To be completed by the Developer:

Test Job Setup Information

File Location AUTODBA Test Job Name Machine TST_ (what attributes the production job should have) Directory

Production Job Setup Information

AUTOSYS Production Job Name PRD_

Date/Time Dependent?

___yes ___no

Schedule Time

___ Every Day ___Mon ___Tue ___Wed ___Thurs ___Fri ___Sat ___Sun
Time of day the job should be scheduled

Starting Condition Execute on Machine Command to Execute Minimum Run Time

This might be null or based on completion of a different job Name of production machine

$JOBBASE/
Null unless want job to fail unless it runs this long (minutes)

Maximum Run Time

Null unless want job to fail if it runs longer than this (minutes)

Send ALARM Standard Input File Standard Output File Standard Error File

___yes $JOBBASE/ $JOBBASE/ $JOBBASE/

___no should an alarm be sent to the console if the job fails

Execute Permissions Group World

YES

Edit

Expected Results
Results
Include specific outcome and auditing information to determine if the job has completed normally

Who will review

The name of the person who is responsible for determining if the results are correct.

Problem Resolution Information:

Potential Errors Instructions

/opt/scribd/conversion/tmp/scratch2422/65850717.doc

Page 3 of 4

08/23/11

Include specific errors that could happen

And if there are any specific instructions for the operations staff, such as "restart the job" or send an e-mail message to an individual

To be completed by the Production Control Supervisor Completed By Date

/opt/scribd/conversion/tmp/scratch2422/65850717.doc

Page 4 of 4

08/23/11