UNIX

I have set write access on the Banner test job submission server for programmers in $BANNER_HOME, which is /banner/TEST (TEST) on bjobtest.sys.oakland.edu.

In addition to the directories for the various Banner modules, the $BANNER_HOME directory contains two subdirectories named oakmods and oakdev; underneath those two subdirectories are partial "shadows" of the $BANNER_HOME directory. The oakmods directory contains any objects which are local modifications to baseline objects. The oakdev directory is where developers will place new objects that we create. For example, if we are creating a shell script that references Student data, it would be installed in $BANNER_HOME/oakdev/student/misc. If directories do not exist in oakdev for the module and object type you are working on, you may create them.

Previously, objects that were created by us were installed into an "oakland" subdirectory underneath the appropriate Banner module. For example, student processes were installed somewhere in $BANNER_HOME/student/oakland. These directories have been replaced by symbolic links to the new locations, meaning that if you search for, create, or link to an object in the prior location, the object will still be found.

When creating these subdirectories, please use the same directory names for your objects as are used in the baseline code tree. For example, objects in the Banner code tree are ultimately located in the following subdirectories:

  • c - C programs

  • cob - COBOL programs

  • forms - Oracle form source code

  • dbprocs - functions, procedures and packages

  • views - view source code

  • plus - SQL scripts (reports and jobs)

  • triggers - database triggers not related to workflow

  • misc - shell scripts and other objects that don't fall into one

Job output is NEVER to be stored anywhere under $BANNER_HOME.

When creating an object, you must make sure that the permissions are correct. The group should be set to "pgmr". If your object is a directory or a shell script, the permissions mode should be -rwxrwxr-x (775); if it is any other file, it should be -rw-rw-r-- (664). Use the following commands to set permissions:

  • . For setting the group: chgrp pgmr <file_or_directory_name>

  • . For directories and shell scripts: chmod 775 <file_or_directory_name>

  • . For other files: chmod 664 <file_name>

For files, you must also create a link in the $BANNER_LINKS directory. As an example for a Student shell script: 

cd $BANNER_LINKS
ln -fs ../oakdev/student/misc/myobject.shl

Please create a "symbolic link" as shown above. In the above command, the "-fs" switches indicate force the creation of a new link if one already exists, and make it a symbolic (or soft link). Please verify that the link was created correctly, especially if there was a previously existing link with the same name but a different target; occasionally, the "-f" switch may fail to replace the old link, but will not give a warning message to indicate it.