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

Appendix D: Systems Documentation

The purpose of the Systems Documentation for the Emergency Preparedness plan is to have a document for each system which would enable a person familiar with an HP3000 but unfamiliar with our systems to know where to go to get documentation for our systems. The documentation listed should be adequate to direct a person to all files which comprise the system. The following items should be included: Systems Overview, Image Schema, Powerhouse Schema, Processing Sequence, KSAM file rebuilds, Schema diagram, File index, User Documentation, and any other pertinent documentation file related to the overall system. This list should be kept on the CWIS server in a file named y:/sysadmin-share/sysdoc/yy/yybook.wpd (yy = system code). Following is an example:

Idaho State University (system name) Documentation

An index for access to applications, such as a list of command files and/or Security 3000 menus, should also be placed here if not provided by the file index system report.

(hpaccount = HP 3000 account on which the system resides.)