Idaho State University

• Academics
• Prospective Students
• Current Students
• Faculty & Staff
• Alumni & Visitors

• Information
  • Access Security
    • Department Information
    • HP3000 Server Account Information
    • Network Services Account Information
    • Responsible Account Holder Information
    • Application System Responsibility
    • Department/Group Info
  • User Guide
    • Table of Contents
  • Networked Printers
  • Miscellaneous System Info
    • HP1 (HPe3000) Server Scheduled Down Time
    • Powerhouse Web Queue Management Values
    • Portal Web Services Availability Schedule
• Our Staff
  • Support by System
  • Primary Support
  • Backup Support
• Project Management
  • Staff Responsibilities
    • Support by System
    • Primary Support
    • Backup Support
• Information Technology Services
• DEACON Project

Enterprise Applications
Development Guidelines and Procedures

Job Scheduling

All Administrative data processing which can be assumed by the office which owns the data should be turned over to that office. All other production processing will be scheduled automatically through JobTime.

Processing

1. Critical Jobs
   1. Jobs may be designated critical by a customer, or IT staff member. Suspected abuses should be reported.
   2. Computer Operations will process priority jobs as soon as possible without impacting jobs currently in progress unless otherwise instructed by management.
   3. Critical jobs run after hours should be accompanied by a work request instructing the operator on who to call for problem resolution. Such work requests are often called "red work request" jobs. Critical jobs require immediate problem resolution regardless of the hour. In such cases the designated individual is required to be available to respond. If the individual is not available the backup analyst followed by the respective manager should be contacted.
   4. All events of abnormal end or abnormal condition with production processing are to be documented by a Job Rescue error action sheet or speed letter. This form is to accompany reports and will be distributed to the proper analyst.
2. Work Requests
   1. Work requests are only required on jobs that have special operator instructions (job dependencies, special forms, large printout, burst & trim, tapes, etc.).
   2. All work requests will be submitted to Computer Operations.
   3. Analysts will be notified by 8:30 a.m. if one of their jobs cancelled the night before.
   4. Work requests may instruct computer operations to call the customer or analyst submitting a job if the job should fail. In such cases the individual who submitted the job is required to be available to respond. If the individual is not available the backup analyst followed by the respective manager should be contacted.
   5. The analyst is responsible for following up on problems and making necessary changes to programs or documentation to avoid repetition of the error.
   6. If an after-backup job requires additional operator instructions a work request should be submitted. All such jobs, however, must be submitted with an input priority of 2 and explicitly state in the work request operator instructions that the job must run after backup.
   7. If computer operations receives a work request for a job needing special processing that does not clearly specify the need, they are to treat this as an error and not run the job listed on the work request. This should be very rare.
   8. Operations should not run any job which they know requires instructions, but for which no work request exists. A speed letter should be issued.
3. Stores and Restores

   All requests for assistance to store or restore files must be given to Computer Operations via a work request. Requests to restore all files in a group or account in order to circumvent file archival procedures will not be permitted without management approval.

4. Printing Charges

   Production logons are those logons for which a page count is produced automatically from daily log reports and charged to a predefined account number. Non-production logons and special charges are recorded as output produced and is billed manually. Techinical Services maintains lists which differentiate among production and non-production accounts. Non-production accounts are billed manually due to multiple customers per account or due to the need to charge cash when the report is picked up (such as for most students).

   Volume word processing (500 sheets or more) or volume multiple identical copies of any document should be performed by available campus printing services whenever possible. Procedures for passing data to these printing services are available. Those who cannot wait for campus printing services will be billed at volume rates.

   1. Production Logons

      1. Reports and all other output will be charged per sheet from the daily log report. (Service code 20 for all laser paper.)
      2. Labels are billed manually and appended to the automatic bill. A fixed charge per sheet of labels with a minimum charge will be manually billed.
      3. Scantron forms will be charged per sheet.
   2. Non-Production logons

      1. Reports and all other output will be charged per sheet from the daily log report. (Service code 20 for all laser paper.)
      2. A fixed charge per sheet of labels with a minimum charge will be manually billed.

For the current rates please contact the Help Desk at 282-HELP.