Idaho State University

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

EnterApp

• 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

Naming Conventions

Production Accounts

Production accounts for applications on HP3000 systems are as follows: (HP Account - HP System)

1. ADMIN - HP1, generally for all users who own a student information related database system.
2. AD2 - HP1, generally for all customers who own a financial information related database system.
3. ADMIN2 - HP2, generally for all customers who own a system which does not fit into categories 1 and 2 above and cannot be placed on HP1 for other special circumstances possibly related to system resources, security, etc..
4. ISU - HP1 for all customers who do not own an application system but who have need to access student and/or financial information systems.

System Code Prefix

All files established for a system including databases, sequential files, KSAM files, program files, stream job files, etc., shall have names beginning with a two character system code normally the same as the MIS project number. For example, the Payroll system has names beginning with 'PR'. Wherever possible a maximum of 7 characters should be used in naming any MPE file. Program files which interface with another system should be named with two system codes, the first being the system maintaining primary responsibility for the program, e.g. AIBIXXX. However, Computer Operations will not schedule jobs based on the second system code.

Powerhouse File Types

To aid in identifying procedures using Powerhouse products (QUIZ, QUICK, and QTP) the third and fourth characters will often be used (this applies only to procedures using these products). The following breakdown should be followed: [The payroll system code 'PR' is being used in these examples. This list is complete with groups in () for storing production procedures.]

	PRQDB 	- Dictionary, Compiled (PROD),
	PRDBQU	- Dictionary, Main Source 
	          (SOURCEPR - HP2),
	PRDBQS	- Dictionary, Source for Security 
	          Definitions (SOURCEPR - HP2),
	PRDBQF	- Dictionary, Source for File and
	          Record Definitions (SOURCEPR - HP2),
	PRDBQE	- Dictionary, Source for Element 
	          Definitions (SOURCEPR - HP2),
	PRQUXXX	- QUICK Screen, Source (SOURCEPR - HP2),
	PRQSXXX	- QUICK Screen, Compiled (PRODQ),
	PRQRXXX	- QUIZ Report, Source 
	          (PRODQ or customer's group),
	PRQTXXX	- QTP Processor, Source (PRODQ),
	PRQKXXX	- QKGO (QUICK), Compiled (PRODQ).
	PRWUXXX	- PHWeb Screen, Source (SOURCEPR - HP2),
	PRWSXXX	- PHWeb Screen, Compiled (PRODQ),
	PRWHXXX	- PHWEb HTML Page, Source (HTML),

The last letter should be 'J' for streamx/batch jobs (JOBS).

Other File Types

The following will be used as naming conventions for the stated file types.

	PRXXX    - COBOL, Compiled (PROD),
	PRXXXS   - COBOL, Source (SOURCEPR - HP2),
	PRXXXF   - View3000, Forms File (VFORM),
	PRXXXSCR - View3000, Form Name [PRXXXSCR1, 
	           PRXXXSCR2, ... for multi. forms],
	PRXXXFF  - View3000, Fast/Compiled Forms 
	           File (FORM),
	PRXXXE   - Environment File, Compiled (FORM),
	PRXXX	 - COBOL, Customer Documentation (DOC),
	PRXXXJ   - COBOL Stream/Batch Job 
	           (JOBS, Customer group),
	PRXXXF   - Laser Printer Form File (FORM).

Program Numbering Scheme

In addition you may find it useful on large systems to include an additional numbering scheme for file types mentioned above for COBOL program files.

	PR0XX - Maintenance Screens,
	PR1XX - Customer Screens,
	PR2XX - Batch Updates,
	PR3XX - Monthly Reports,
	PR4XX - Quarterly Reports,
	PR5XX - Yearly Reports,
	PR6XX - Clear Procedures.

Flat/Text Files

Permanent flat/text files should follow naming conventions also, i.e., a file used in PR200 should be named PR200F. If this file is built by QUIZ and used in PR200 it would be named PR200QF. Files used by multiple programs should be named for the first program in the sequence. Use temporary files when possible to save disk space. KSAM key files should be named the same as the data file followed by the letter K.

Database Diagram

Database figures should be named consistently beginning with the two character system code, followed by DIAG, and a number if necessary. The Diagram should be named PRDIAG. New files should be created in the appropriate system directory of

y:\adminsys-share\sysdoc

of the CWIS server running NT using TAS (NTCWIS). The currently supported flowcharting software will be determined by management.

Group Utilization

The following are groups within all production accounts used for production processing and the descriptions of the files which should be placed therein:

ACCMD

This group holds all command files related to applications and processes within this account.

ANALYST

This group shall contain all files which are in a state of transition. These are files waiting to be placed into production or being taken out of production but are to be held for a period of time as backup to new procedures. Files taken out of production should so indicate with a final character of 'O' for 'Old' when possible. All files should begin with the first two characters of the system or occasionally the initials of the individual creating the file. This is the home group for production account's MGR user. The group must be kept relatively clean.

CWIS

This group generally holds files transferred to CWIS for web access.

DCTRL

This group should no longer be used with management approval.

DOC

This group shall contain any program documentation, help files, or other material intended to provide online instruction. Data in this group can be read by anyone on the system.

FORM

This group shall contain all forms and environments to a production program. Included are VFAST, PENV and any other form or environment file used by a production program.

HTML

This group holds HTML documents linked to Powerhouse Web applications.

JOBS

This group has been given execute only access to ANY logged on user allowing us to place batch jobs here so departments can run through STREAMX but cannot view or change. All batch jobs written and/or maintained by Computer Center staff should be placed in this group. In particular, QTP jobs and other jobs for which additional security is required should reside here.

MAINT

This group is intended to contain any file which will be used to support the maintenance of an application system. No file in this group will be used in a production procedure. These are jobs run by the IT staff member responsible for the system.

ODBC

This group generally holds files that assist in the access of databases through Minisoft's ODBC product.

PROD

This group contains all compiled COBOL programs which the user will run. The user will have execute access only to this group. Powerhouse compiled data dictionaries will also be kept in this group.

PRODQ

This group shall contain all production compiled QUICK screens, QKGO files, and any other on-line Powerhouse program files run by a customer. This group should contain all on-line QUIZ and QTP program files written and/or maintained by Computer Center staff. This is used to prevent customers from unintentionally damaging critical on-line programs. Although this group is logically used the same as PROD it will serve to separate COBOL and Powerhouse application software.

PUB

This group contains all data files, databases, KSAM files, or other files which must be available for read and write access to one or more customers. Permanent data files should not reside in the customer's group unless they are created by the user and/or are unsupported by the Computer Center or must reside there for security reasons. All critical data must be stored in an IMAGE database in PUB to provide proper data security and integrity.

SHTML

This group holds files that are to be transferred to CWIS or UX7 for web access through a secure server.

SLEEPER

This group holds batch jobs that scheduled for launching through JobTime.

SOLD

This group will be used to store previous versions of program source code. Use the CHECKOUT and CHECKIN procedures mentioned earlier in the document.

SYVEMENU

This group holds main menu files for use with Security/3000 software from VESoft.

USEJOBS

This group holds special USE files for utilization with Streamx programs.

USEPH

This group holds special USE files for utilization with QUIZ and QTP programs.

VEMENU

This group holds non-main menu files for use with Security/3000 software from VESoft.

Following are groups in the DESIGN account other than personal work groups.

ACCMD

This group is here for consistency to provide temporary storage for command files until they can be placed into a production account.

ANALYST

This group has been established for consistency between systems. It should typically not contain any files. It is the home group for the MGR.DESIGN user. Files stored in this group will be moved soon into a production account. For example, a job to be stored in DCTRL.ADMIN may temporarily reside here.

DOC

This group is here for consistency to provide a temporary storage for user documentation until it can be placed in the DOC group of a production account.

FORM

This group has been established to provide a temporary place in which to store files during their development and test stages which will eventually reside in the FORM group of a production account.

HTML

This group holds HTML documents linked to Powerhouse Web applications.

JOBS

This group is here for consistency to provide temporary storage for user jobs until they can be placed into a production account.

MAINT

This group is here for consistency to provide temporary storage for files to go into MAINT of a production account.

PROD

This group has been established to provide a temporary place in which to store files during their development and test stages which will eventually reside in the PROD group of a production account.

PRODQ

This group has been established to provide a temporary place in which to store files during their development and test stages which eventually reside in the PRODQ group of a production account.

PUB

This group will house test databases and data files. Names of test databases should be identical to their production counterpart. Please keep in mind the need to determine disk utilization by system. Powerhouse dictionaries should not have fully qualified database names. Passwords should remain the same between production and test databases to facilitate use of a single dicitonary file.

SOLD

This group will be used to store previous versions of program source code. Old object code should be purged. A hard copy listing, using SCOMPARE, will be made showing the differences between old and new versions of any program. This listing will be maintained in a filing cabinet. This may be used in lieu of keeping an entire copy of the former file. Use the CHECKOUT and CHECKIN procedures mentioned earlier in the document.

SOURCExy

This group will contain all source code created for an application system such as database schemas, COBOL source code, Powerhouse QUICK screen source files, and Powerhouse dictionary source files (xy indicates system code).

SYSDOC

This group shall contain any systems documentation which is intended to be read and maintained by IT staff members exclusively. Any systems documentation which should also be read by customers will be kept in the DOC group of a production account.

VFORM

This group will contain all VFORM source files used in preparing VFAST files for production V/3000 screens.

Other groups, not documented here, are described in the LOGONS file of the Project Management System.