SCHEDULED JOBS Scheduled Jobs are maintained by the OTIS DBA section; the primary mechanism for scheduling database jobs is by UNIX crontab. The developer is responsible for creating the SQL to be run by the crontab, creating the UNIX scripts for executing the SQL, and consulting with the DBA section to ensure the UNIX code will function in the DEP environment. All code must be reviewed and approved by the OTIS DBA section. The following rules apply to Scheduled Jobs: Scheduled Job are mandatory. Scheduled Job names must begin with the schema name for which the job is being run. It cannot exceed 30 characters. It should be made up of real words. It must contain a section at the top with comments on when the script was written, who wrote it, and a description of the function that the script performs. If the script is one of several used for a purpose then all script names should be declared in the top comment section along with the order in which the current script is run in relation to the other scripts. examples are PA_LOAD_PERMIT_DATA, CRA_CALCULATE_FEES. The Scheduled Job includes underscores in of spaces. When the Scheduled Job name is only one word, it must not be an . The executed SQL code must be stored in a database procedure or database package. The Scheduled Job must execute under the schema account which owns the database procedure or package. The Scheduled Job may contain UNIX commands to create files, ftp files, and/or remove files only from the directory location where the scripts are stored. Exceptions may be made if a business case is presented and approved by the OTIS DBA section. Developers are responsible for testing the UNIX shell scripts from their own UNIX account on the DEP development database server before submitting them to be added to the crontab. SQL CODING STANDARDS and GUIDELINES Database object SQL and PL SQL code is maintained by the developer and is expected to adhere to general best-practice coding standards. There are multiple references online for those consulted for the standards/guidelines found below are: Burleson Consulting:
SCHEDULED JOBS Scheduled Jobs are maintained by the OTIS DBA section; the primary mechanism for scheduling database jobs is by UNIX crontab. The developer is responsible for creating the SQL to be run by the crontab, creating the UNIX scripts for executing the SQL, and consulting with the DBA section to ensure the UNIX code will function in the DEP environment. All code must be reviewed and approved by the OTIS DBA section. The following rules apply to Scheduled Jobs: Scheduled Job are mandatory. Scheduled Job names must begin with the schema name for which the job is being run. It cannot exceed 30 characters. It should be made up of real words. It must contain a section at the top with comments on when the script was written, who wrote it, and a description of the function that the script performs. If the script is one of several used for a purpose then all script names should be declared in the top comment section along with the order in which the current script is run in relation to the other scripts. examples are PA_LOAD_PERMIT_DATA, CRA_CALCULATE_FEES. The Scheduled Job includes underscores in of spaces. When the Scheduled Job name is only one word, it must not be an . The executed SQL code must be stored in a database procedure or database package. The Scheduled Job must execute under the schema account which owns the database procedure or package. The Scheduled Job may contain UNIX commands to create files, ftp files, and/or remove files only from the directory location where the scripts are stored. Exceptions may be made if a business case is presented and approved by the OTIS DBA section. Developers are responsible for testing the UNIX shell scripts from their own UNIX account on the DEP development database server before submitting them to be added to the crontab. SQL CODING STANDARDS and GUIDELINES Database object SQL and PL SQL code is maintained by the developer and is expected to adhere to general best-practice coding standards. There are multiple references online for those consulted for the standards/guidelines found below are: Burleson Consulting:
STD-14121501.2.0.docx