OASIS Programming Guide

The following are programming suggestions for OASIS. These are not hard and fast rules, but represent the way the majority of OASIS programs were done during the initial conversion effort.

  1. Unless otherwise specified, all output should use mixeed case text.
  2. The START paragraph should be names START-PROC.
  3. The FINISH paragraph should be named FINISH-PROC.
  4. All parameters (except SIS version) should be named with a prefix of PARM.
  5. The DB2 version of the SIS database should be named SISVER. It should only contain PROD, INST or TEST.
  6. SISVER should always be the last parameter.
  7. Term input should be in CCYYT format, with a displacement (e.g., (-1, +0, +1, etc.) being acceptable.
  8. Terms should be validated in the START procedure. Use the standard term fetch routine for this.
  9. Terms should always be referred to as terms rather than quarters or semesters.
  10. If any batch transactions are produced by the program, use the standard utility to insure the batch header is unique.
  11. Detect no students selected and set a return code of 05 in the FINISH procedure.
  12. Output should go to standard print files, named PRTFLxx.
  13. Easytrieve Plus reports should have names of RPTx.
  14. The START procedure should display program name and all parameters input into the program through the MACRO statement. In addition, any values derived from them or other sources that are critical to program operation should always bee displayed.
  15. Easytrieve Plus has a default of LIST ON. Leave it. By default, the program listing goes to SYSPRINT. This is the reason for redirection of all user output.
  16. Use program comments that indicate how pieces of the program function. Do not try to explain in detail how the program works.
  17. Try to fit output into 80 characters where possible.
  18. For reports, use SPACE 1 unless not feasible.
  19. Please do not use BEFORE-BREAK, BEFORE-LINE or AFTER-LINE. These cause problems for many of our personnel.
  20. In the standard program header, explain file usage rather than merely listing the file's name. Also be sure to include DB2 tables in this section.

OIT--Applications Support


Last Modified: Tuesday, 28-Nov-2000 14:54:24 CST

©1999 All Rights Reserved