Student Affairs Technical Manual - UConn Health · Student Affairs Technical Manual 3 Using This Manual Conventions Used in This Manual Introduction Jenzabar has established a set

Student Affairs

Technical Manual

Copyright (c) 2001 Jenzabar, Inc. All rights reserved. You may print any part or the whole of this documentation to support installations of Jenzabar software. Where the documentation is available in an electronic format such as PDF or online help, you may store copies with your Jenzabar software. You may also modify the documentation to reflect your institution's usage and standards. Permission to print, store, or modify copies in no way affects ownership of the documentation; however, Jenzabar, Inc. assumes no responsibility for any changes you make. Filename: tmstuaff Distribution date: 01/16/1998 Contact us at www.jenzabar.com

Jenzabar CX and QuickMate are trademarks of Jenzabar, Inc. INFORMIX, PERFORM, and ACE are registered trademarks of the IBM Corporation Impromptu, PowerPlay, Scenario, and Cognos are registered trademarks of the Cognos Corporation UNIX is a registered trademark in the USA and other countries, licensed exclusively through X/Open Company Limited Windows is a registered trademark of the Microsoft Corporation All other brand and product names are trademarks of their respective companies

i

JENZABAR, INC. STUDENT AFFAIRS TECHNICAL MANUAL

TABLE OF CONTENTS

SECTION 1 - USING THIS MANUAL........................................................................................................... 1 Overview..................................................................................................................................................... 1

Purpose of This Manual.......................................................................................................................... 1 Intended Audience.................................................................................................................................. 1 How to Use This Manual ........................................................................................................................ 1 Product Differences ................................................................................................................................ 1 Structure of This Manual ........................................................................................................................ 1 Related Documents and Help ................................................................................................................ 2

Conventions Used in This Manual.............................................................................................................. 3 Introduction............................................................................................................................................. 3 Style Conventions................................................................................................................................... 3 Jenzabar-Specific Terms........................................................................................................................ 4 Keystrokes.............................................................................................................................................. 4

SECTION 2 - STUDENT AFFAIRS PROCESSES....................................................................................... 5 Overview..................................................................................................................................................... 5

Introduction............................................................................................................................................. 5 Purpose of Product................................................................................................................................. 5 Background Knowledge.......................................................................................................................... 5

Process Flow .............................................................................................................................................. 7 Diagram .................................................................................................................................................. 7 Process Description................................................................................................................................ 7

Application Relationships ........................................................................................................................... 8 Related Jenzabar CX Applications......................................................................................................... 8

SECTION 3 - STUDENT AFFAIRS TABLES AND RECORDS................................................................... 9 Overview..................................................................................................................................................... 9

Introduction............................................................................................................................................. 9 Alphabetical Organization....................................................................................................................... 9 What Is an SQL Table? .......................................................................................................................... 9 What Is a Jenzabar CX Table? .............................................................................................................. 9 What Is a Jenzabar CX Record?............................................................................................................ 9

Summary List of Tables and Records Used............................................................................................. 10 Introduction........................................................................................................................................... 10 Impact of Changes to Tables and Records.......................................................................................... 10 Common Tables and Records.............................................................................................................. 10 Shared Tables and Records................................................................................................................. 11 Student Affairs Tables and Records..................................................................................................... 11 Required Tables and Records.............................................................................................................. 12

Table and Record Relationships .............................................................................................................. 13 Entity Relationship Diagram (ID record)............................................................................................... 13

Schemas................................................................................................................................................... 14 Introduction........................................................................................................................................... 14 File Naming Conventions ..................................................................................................................... 14 Field Descriptions ................................................................................................................................. 14

Tables and Records ................................................................................................................................. 15 Introduction........................................................................................................................................... 15

SECTION 4 - STUDENT AFFAIRS MACROS AND INCLUDES............................................................... 21 Overview................................................................................................................................................... 21

ii

Introduction........................................................................................................................................... 21 Relationship Among Macros, Includes, and C Programs .................................................................... 21 General Installation Procedures ........................................................................................................... 21

Macros...................................................................................................................................................... 22 Introduction........................................................................................................................................... 22 Definition and Function......................................................................................................................... 22 How to Locate Macros.......................................................................................................................... 22 Applocate Program............................................................................................................................... 22 Enable Macros...................................................................................................................................... 23

Includes .................................................................................................................................................... 24 Introduction........................................................................................................................................... 24 Purpose ................................................................................................................................................ 24 Macro Dependency .............................................................................................................................. 24 How to Locate Includes ........................................................................................................................ 24 Associated Includes.............................................................................................................................. 24

SECTION 5 – JENZABAR CX PROGRAM FILES .................................................................................... 25 Overview................................................................................................................................................... 25

Introduction........................................................................................................................................... 25 Program Files Detailed ......................................................................................................................... 25 Definition File ........................................................................................................................................ 25 Example of a def.c File ......................................................................................................................... 26 mac.h Files ........................................................................................................................................... 28 Example of a mac.h File ....................................................................................................................... 28

SECTION 6 - EVENT ENTRY..................................................................................................................... 31 Overview................................................................................................................................................... 31

Introduction........................................................................................................................................... 31 Program Features Detailed .................................................................................................................. 31

Process Flow ............................................................................................................................................ 32 Diagram ................................................................................................................................................ 32 Data Flow Description .......................................................................................................................... 32 Program Relationships ......................................................................................................................... 32 Tables and Records Used.................................................................................................................... 32 Special Function Flags ......................................................................................................................... 33

Parameters ............................................................................................................................................... 34 Introduction........................................................................................................................................... 34 Parameter Syntax................................................................................................................................. 34 Parameters ........................................................................................................................................... 34

Program Screens and Windows............................................................................................................... 36 Introduction........................................................................................................................................... 36 Access .................................................................................................................................................. 36 Screen Files and Table/Record Usage ................................................................................................ 36

SECTION 7 - HEALTH ENTRY.................................................................................................................. 37 Overview................................................................................................................................................... 37



Parameters ............................................................................................................................................... 43 Introduction........................................................................................................................................... 43

iii

Parameter Syntax................................................................................................................................. 43 Parameters ........................................................................................................................................... 43


SECTION 8 - INCIDENT ENTRY................................................................................................................ 47 Overview................................................................................................................................................... 47





SECTION 9 - CAREER PLACEMENT ....................................................................................................... 55 Overview................................................................................................................................................... 55




Program Screens and Windows............................................................................................................... 60 Purpose ................................................................................................................................................ 60 Access .................................................................................................................................................. 60 Screen Files and Table/Record Usage ................................................................................................ 60

SECTION 10 - STUDENT ENTRY.............................................................................................................. 63 Overview................................................................................................................................................... 63



Parameters ............................................................................................................................................... 69

iv

Introduction........................................................................................................................................... 69 Parameter Syntax................................................................................................................................. 69 Parameters ........................................................................................................................................... 69


SECTION 11 - MENUS, SCREENS, SCRIPTS, AND REPORTS ............................................................. 77 Overview................................................................................................................................................... 77

Introduction........................................................................................................................................... 77 Directory Locations............................................................................................................................... 77

Student Affairs Menus .............................................................................................................................. 79 Introduction........................................................................................................................................... 79 Student Affairs Menu Flow Diagrams................................................................................................... 79 Student Affairs Menu Structure ............................................................................................................ 91 Menu Options ....................................................................................................................................... 92

PERFORM (Table Maintenance) Screens ............................................................................................. 113 Introduction......................................................................................................................................... 113 PERFORM screens ............................................................................................................................ 113

SQL Scripts ............................................................................................................................................ 119 Introduction......................................................................................................................................... 119 SQL Scripts......................................................................................................................................... 119

Csh Scripts ............................................................................................................................................. 120 Introduction......................................................................................................................................... 120 Csh Scripts ......................................................................................................................................... 120

ACE Reports........................................................................................................................................... 122 Introduction......................................................................................................................................... 122 Student Services ACE Reports .......................................................................................................... 122 Chapel/Convocation ACE Reports ..................................................................................................... 123 Housing/Events ACE Reports ............................................................................................................ 124 Health Services ACE Reports ............................................................................................................ 125 Health Services Table Maintenance ACE Reports ............................................................................ 125 Personal/Campus Incident ACE Reports ........................................................................................... 126 Student Placement ACE Reports ....................................................................................................... 126 Student Placement ACE Reports (Reports Menu)............................................................................. 127 Student Placement Table Maintenance ACE Reports ....................................................................... 128

Letters..................................................................................................................................................... 129 Introduction......................................................................................................................................... 129 Letters................................................................................................................................................. 129

SECTION 12 - CUSTOMIZING THE STUDENT AFFAIRS PROCESSES.............................................. 131 Overview................................................................................................................................................. 131

Introduction......................................................................................................................................... 131 Basic Information................................................................................................................................ 131 Implementation Process Checksheet................................................................................................. 131

Assessing the Student Affairs Setup...................................................................................................... 132 Introduction......................................................................................................................................... 132 Enabling Products .............................................................................................................................. 132 Chapel/Convocation Attendance........................................................................................................ 132 Events Scheduling.............................................................................................................................. 132 Placement of Housing and Incident Menus........................................................................................ 132 Personal/Campus Incidents ............................................................................................................... 132

Reviewing Data in Tables and Records ................................................................................................. 133 Introduction......................................................................................................................................... 133 Procedure ........................................................................................................................................... 133

v

Table and Record Information............................................................................................................ 133 Order of Table Information in This Section......................................................................................... 133 Table Setup Sequence ....................................................................................................................... 133

Building the Health Services Tables....................................................................................................... 135 Introduction......................................................................................................................................... 135 Access ................................................................................................................................................ 135 Allergy Table....................................................................................................................................... 135 Immunization Table ............................................................................................................................ 135 Medical History Table ......................................................................................................................... 135 Special Conditions Table.................................................................................................................... 135

Building the Personal/Campus Incident Tables ..................................................................................... 137 Introduction......................................................................................................................................... 137 Access ................................................................................................................................................ 137 Personal Incident Table...................................................................................................................... 137

Building the Career Placement Tables................................................................................................... 138 Introduction......................................................................................................................................... 138 Access ................................................................................................................................................ 138 Career Skills Table ............................................................................................................................. 138 Contact Table ..................................................................................................................................... 138 Position Type Table............................................................................................................................ 138

Building the Chapel/Convocation Tables ............................................................................................... 139 Introduction......................................................................................................................................... 139 Access ................................................................................................................................................ 139 Chapel/Convocation Event Table....................................................................................................... 139

SECTION 13 - STUDENT AFFAIRS MAINTENANCE PROCEDURES.................................................. 141 Overview................................................................................................................................................. 141

Introduction......................................................................................................................................... 141 Definitions ........................................................................................................................................... 141 Process............................................................................................................................................... 141

Session-Based Maintenance.................................................................................................................. 142 Introduction......................................................................................................................................... 142 Process............................................................................................................................................... 142 Adding Records .................................................................................................................................. 142 Updating Records............................................................................................................................... 143

Chapel/Convocation Session-Based Maintenance................................................................................ 144 Introduction......................................................................................................................................... 144 Process............................................................................................................................................... 144 Adding Initial Records......................................................................................................................... 144 Adding an Initial Table Entry............................................................................................................... 145 Checking Attendance Records.......................................................................................................... 145

SECTION 14 - PROGRAM ERRORS AND CRASH RECOVERY .......................................................... 147 Overview................................................................................................................................................. 147

Introduction......................................................................................................................................... 147 Error and Crash Recovery Procedures .................................................................................................. 148

Introduction......................................................................................................................................... 148 Core Dump Recovery ......................................................................................................................... 148

INDEX ....................................................................................................................................................... 151

Student Affairs Technical Manual 1 Using This Manual

SECTION 1 - USING THIS MANUAL

Overview

Purpose of This Manual

This manual provides technical information required to install, customize, and maintain the Student Affairs and Career Placement products of CX.

Intended Audience

This manual is for use by those individuals responsible for the installation, customization, and maintenance of CX.

How to Use This Manual

If you are not familiar with the processes and features of the Student Affairs and Career Placement products, read the manual for:

• Detailed reference information about how the products work • Procedures for customizing and maintaining the products

If you are familiar with the processes and features of the Student Affairs and Career Placement products and just need specific reference information or a procedure, look through the table of contents or index and refer to the pages you need.

Product Differences

This manual contains information for using all features developed for the Student Affairs and Career Placement products. Your institution may or may not have all the features documented in this manual.

Structure of This Manual

This manual contains both general reference information and procedures for installing, customizing, and maintaining the Student Affairs and Career Placement products. The organization of the manual is as follows:

Overview information: Section 1 - Information about using this manual Section 2 - Overview information about the products

Product reference information: Section 3 - Tables and records used in the products Section 4 - Macros and Includes Section 5 - CX program files Section 6 - Program used in the product (Event Entry) Section 7 - Program used in the product (Health Entry) Section 8 - Program used in the product (Incident Entry) Section 9 - Program used in the product (Career Placement) Section 10 - Program used in the product (Student Entry) Section 11 - Menus, screens, scripts, and reports

Product procedures: Section 12 - Procedures to install and customize your processes Section 13 - Procedures to maintain the products

Using This Manual 2 Student Affairs Technical Manual

Error reference/Recovery procedures: Section 14 - A reference of fatal and serious errors and recovery procedures

Reference information: Index

Related Documents and Help

The following resources are also available to assist you in installing, customizing, maintaining, and using the Student Affairs and Career Placement products:

QuickMate online help: QuickMate Installation Guide Getting Started User Guide

Technical manuals: Communications Management Technical Manual

UNIX-based help: Help command (<Ctrl-w>) in screens and menus

User guides: Getting Started User Guide Career Placement User Guide Student Affairs User Guide

Student Affairs Technical Manual 3 Using This Manual

Conventions Used in This Manual

Introduction

Jenzabar has established a set of conventions to help you use this manual. The list of conventions presented below is not exhaustive, but it includes the more frequently used styles and terms.

Style Conventions

Jenzabar technical manuals observe the following style conventions:

Boldface type Represents text that you type into the system (e.g., Type UNDG), command names (e.g., Finish), or keys you use to execute a command or function (e.g., <Enter>).

Bulleted lists Show items not ranked or without a sequential performance.

CAUTION: Indicates a caution or warning of a potential risk or condition.

<Enter> Represents the Enter, Return, Line Feed, or ↵ key on your keyboard.

Italic type Is used in any of these ways:

• To represent a new or key term • To add emphasis to a word • To cross-reference a section of text • To represent a variable for which you substitute another variable (e.g., substitute

filename with an appropriate filename)

<Key name> Represents a key that you must press.

Note: Indicates a note, tip, hint, or additional information.

Numbered lists Show ranking of items or sequence of performance.

Parentheses When used around a field name, indicate the field is unlabeled. The field description includes the location of the field.

Quotation marks Represent information written in this guide exactly as it appears on the screen.

Example: The message, "Now Running..." appears.

Using This Manual 4 Student Affairs Technical Manual

Jenzabar-Specific Terms

Some terms used in this manual may be unfamiliar to you, either because they are terms you have not used before or because Jenzabar has assigned a slightly different meaning to a familiar term. The following list identifies and explains the most common Jenzabar-specific terms:

Application One or more software programs that enable you to perform a particular procedure, such as entering student information.

Data Specific information you enter into fields on a particular data entry screen.

Enter To type information on a keyboard and execute by any of the following actions:

• Pressing the <Enter> key • Clicking on the OK button • Selecting Finish.

F key Any of the function keys located on your keyboard (e.g., <F1>).

Hot key The capitalized and underlined (or highlighted) letter of a command on a menu.

ID The number assigned to each student or organization associated with your institution (e.g., 12345).

Parameter A variable in the system that is given a constant value for a specific application (e.g., a date can be a parameter for producing a report).

Select To execute a command by any of the following actions:

• Performing the keystrokes • Pressing the hot key • Highlighting the command or option and pressing <Enter> • Clicking on the icon or button with the mouse

System The Jenzabar product, CX.

Keystrokes

When you see two keys separated by a dash (e.g., <Ctrl-c>), hold down the first key (<Ctrl>) while pressing the second (<c>).

Student Affairs Technical Manual 5 Processes

SECTION 2 - STUDENT AFFAIRS PROCESSES

Overview

Introduction

This section provides information on the purpose and process flow of Student Affairs.

Purpose of Product

The primary purpose of Student Affairs is to enable an institution to gather all necessary information, other than academic, about students attending the institution. The CX Student Affairs product assists the Student Affairs and Housing offices in maintaining information on campus life, student counseling, and personal incidents. Specifically, the product includes the following areas:

Student Advisor Contains display-only access to the following applications for viewing a student's academic progress at your institution:

• Degree Audit • Registration Entry • Transcript

Student Services Contains the following:

• The Student Entry application for maintaining a student's records • Options to add and update Student Services records for a session • Options to maintain Chapel/Convocation records

Housing/Events Contains the following:

• The Housing Entry application to quickly locate and maintain a student’s housing information

• Options to maintain and produce schedules of upcoming student, social, and cultural events on campus

Health Services Contains the Health Entry application for maintaining health services information.

Personal/Campus Incidents Contains options to maintain campus and personal incident information in order to collect data required by the Criminal Awareness Act.

Background Knowledge

The following list describes the necessary background information that you should know to implement and support the Student Affairs and Career Placement products:

UNIX Know the following about the UNIX operating system:

• Csh environment and commands • Editor commands (e.g., vi)

Processes 6 Student Affairs Technical Manual

INFORMIX-SQL Know about the following INFORMIX tools:

• SQL database • PERFORM screens • ACE reports

Jenzabar CX database tools and utilities Know how to use the following database tools:

• MAKE processor • Schemas • Macros • Includes • Program screens

Jenzabar CX Know the following about the Jenzabar CX standard product:

• CX directory structure • The menu processor • The CX database engine • The product update process

QuickMate features Know the following about the CX Graphical Server:

• Client/Server processing • Telnet settings • Keyboard settings • Mouse settings • GUI mode commands

C Programming If you want to modify any CX programs to meet unique needs at your institution, you must know how to use the C programming language and have an in-depth knowledge of the CX code.

Student Affairs policies and procedures Know answers to the following questions:

• What are your institution’s vehicle registration policies? • What are your institution’s immunization policies? • What are your institution’s residence policies? • What are your institution’s meal plan requirements? • Do you know the students’ local mail boxes?

Student Affairs Technical Manual 7 Processes

Process Flow

Diagram

The following diagram shows the process flow of the Student Affairs and Career Placement products.

Note: For more information about program interrelationships and detailed data flow diagrams, see the program sections in this manual.

Student Services Housing/Events - Maintain students’ records - Maintain students’ housing and - Add Student Services records vehicle registration information - Update Student Services records - Schedule and coordinate events Chapel/Convocation Health Services - Maintain meeting schedule - Maintain students’ health - Track students’ attendance Non-academic and medical visit history and absences Student data - Maintain health provider information

Support Services Personal/Campus Incidents (for California state Institutions) Maintain information about incidents on campus Student Advisor Display-only access to student academic information

Process Description

Each area of the Student Affairs and Career Placement products contribute to the non-academic information that the institution needs to gather about students. The Student Advisor area, designed for use by student counselors, is the exception.

Processes 8 Student Affairs Technical Manual

Application Relationships

Related Jenzabar CX Applications

The Student Affairs product interacts with several other applications and products in CX. The following list describes the interrelationships:

Admissions Users of the Admissions product gather initial student data that the Student Affairs product uses. Student Affairs builds upon such initial records.

Career Placement Career Placement gathers students’ credential information from records of Student Affairs.

Financial Aid Certain types of financial aid may depend upon a student’s resident status. Such information appears in Housing records.

Registration Users of the Registration product can change fees that are assessed from Student Affairs data.

Student Affairs Technical Manual 9 Tables and Records

SECTION 3 - STUDENT AFFAIRS TABLES AND RECORDS

Overview

Introduction

This section provides reference information about each table and record associated with the Student Affairs and Career Placement products. It also provides definitions of SQL and CX table and record terminology and differentiates among common, shared, and product-specific tables and records.

Alphabetical Organization

The tables and records appear in alphabetical order in this section.

What Is an SQL Table?

In a relational SQL database, a table is an organized set of any kind of data, regardless of its purpose for validation or information maintenance. The basic unit of organization of a table is a column, that is, a category of data. A table can have multiple columns and multiple rows of data.

Columns

Rows

ID

391569012345098754591320941783490100840917892955712309

Full Name

Browning, Allan T.Smith, Roxanne N.Dobrowski, George S.Jennings, Christina A.Brown, Garrett L.Cummings, Charles C.

FA96FA96FA96SP97FA96SP97

Sess

What Is a Jenzabar CX Table?

A table in CX contains information that remains static and is denoted with the _table extension. For example, the State table, named st_table, contains the list of the states in the United States of America. On the CX menu, you can access most tables in Table Maintenance menus.

What Is a Jenzabar CX Record?

A record in CX is a table containing information that changes on a regular basis and is denoted with the _rec extension. For example, the Alternate Address record, named aa_rec, contains any other addresses where students can be contacted, such as a summer address. You access records in CX program screens and windows, scroll screens, and PERFORM screens. SQL makes no distinction between tables and records; all sets of data are tables.

Tables and Records 10 Student Affairs Technical Manual

Summary List of Tables and Records Used

Introduction

Tables and records used in Student Affairs can be divided into the following categories: • Common • Shared • Product-specific

Among these categories, some tables and records are required, while others are optional.

Impact of Changes to Tables and Records

If you make changes to schemas for any tables or records, you must reinstall each associated product or module.

Common Tables and Records

Modules in the Student Affairs and Career Placement products use several tables and records that are common throughout CX. These tables and records are:

Note: For additional information about these common tables and records see the CX System Reference Technical Manual unless otherwise noted.

• Accomplishment record (accomp_rec) • Addressee record (addree_rec) • Addressing record (adr_rec) • ADR table (adr_table) • Alternate Address table (aa_table) • Business record (bus_rec) • Church record (church_rec) • Contact record (ctc_rec) (See Communications Management Technical Manual) • Contact table (ctc_table) • Country table (ctry_table) • County table (cty_table) • Denomination table (denom_table) • Education record (ed_rec) • Employment record (emp_rec) • Ethnic table (ethnic_table) • Event record (evnt_rec) • Examination record (exam_rec) • Facility table (facil_table) • Faculty record (fac_rec) • Handicap table (hand_table) • Hold record (hold_rec) • Hold table (hold_table) • ID record (id_rec) • Interest record (int_rec) • Involvement record (involve_rec) • Military record (milit_rec) • Occupation table (occ_table) • Office table (ofc_table) • Profile record (profile_rec)


• Relationship record (relation_rec) • Relationship table (rel_table) • Site record (site_rec) • State table (st_table) • Tickler record (tick_rec) • Tickler table (tick_table) • Title table (title_table) • User Identification table (userid_table) • Zip Code table (zip_table)

Shared Tables and Records

Some tables and records used in Student Affairs originate, or are more frequently used, within other CX product areas. These tables and records, and their originating product areas, are:

Note: For additional information, see the technical manual for the primary product area. If multiple products are shown, the primary product is listed first.

• Admissions record (adm_rec) − Recruiting/Admissions

• Program Enrollment record (prog_enr_rec) − Recruiting/Admissions − Registration

• Satisfactory Academic Progress record (sap_rec) − Financial Aid

• School record (sch_rec) − Recruiting/Admissions − Registration

• Secondary Relationship record (relsec_rec) − Recruiting/Admissions − Financial Aid − Institutional Advancement − Registration

• Student Academic record (stu_acad_rec) − Registration

• Student Statistics record (stu_stat_rec) − Registration

Student Affairs Tables and Records

Programs in the Student Affairs and Career Placement products use the following Student Affairs tables and records. File information about these tables and records is in this section.

• Allergy record (allergy_rec) • Allergy table (allergy_table) • Career Position record (career_pos_rec) • Career record (career_rec) • Career Skills record (career_skl_rec) • Chapel record (chap_rec) • Chapel table (chap_table) • Grade Message record (grdmsg_rec) • Health record (health_rec) • Immunization record (immune_rec) • Immunization table (immune_table) • Insurance record (insure_rec)


• Interviewee record (intvwee_rec) • Interviewer record (intvwer_rec) • Medical History record (medhist_rec) • Medical History table (medhist_table) • Personal Incident record (stupers_rec) • Personal Incident table (stupers_table) • Position Skills record (pos_skl_rec) • Special Conditions record (speccond_rec) • Special Conditions table (speccond_table) • Student Services record(stu_serv_rec)

Required Tables and Records

The following tables and records are required to run the features of the Student Affairs and Career Placement products:

• id_rec • profile_rec • stu_serv_rec


Table and Record Relationships

Entity Relationship Diagram (ID record)

The following diagram shows the relationship between the ID record (id_rec) and the records used by the Student Affairs and Career Placement products.

id_rec

prog_enr_rec

allegry_rec

insure_rec

immune_rec

medhist_rec

speccond_rec

adm_rec

chap_rec

evnt_rec

profile_rec

stupers_rec

health_rec

site_rec

stu_stat_rec

sap_rec

grdmag_rec

stu_acad_rec

stu_serv_rec

ctc_rec

bus_rec

career_pos_rec

pos_skl_rec

career_rec career_skl_rec intvwer_rec intvwee_rec emp_rec


Schemas

Introduction

Schema files define the structure of database files and associated fields in the CX data dictionary. You can access schema files associated with the Student Affairs and Career Placement products in the following directory paths:

• $CARSPATH/schema/matric • $CARSPATH/schema/student

File Naming Conventions

CX makes distinctions in the naming of schemas. For schema files containing definitions of CX tables, the UNIX filename begins with the letter t followed by characters describing the English name of the table (e.g., tst for the State table). For schema files containing definitions of CX records, the UNIX filename describes the English name of the record (e.g., id for ID record).

The first line in a schema file, after revision information, specifies the INFORMIX database table that the schema defines. For example, st_table (State table) is specified in the tst schema file.

Field Descriptions

Schema files contain descriptions of each field defined in a table or record. You can view descriptions of fields in Student Affairs tables and records by accessing the schema files.


Tables and Records

Introduction

The following list identifies the tables and records that originate from the Student Affairs and Career Placement products. The list includes the filenames, location, purpose, and association of each table and record with programs and other tables and records.

Allergy record Maintains records of an individual’s allergies.

UNIX filename: allergy

Informix filename: allergy_rec

Schema location: $CARSPATH/schema/matric

Program interrelationships: hentry

Product interrelationships: Student Affairs

Allergy table Maintains a list of codes that describe allergies.

UNIX filename: tallergy

Informix filename: allergy_table




Career record Maintains records of an individual’s career.

UNIX filename: career

Informix filename: career_rec

Schema location: $CARSPATH/schema/student

Program interrelationships: placement

Product interrelationships: Career Placement

Career Position record Maintains records of requirements and skills for a position.

UNIX filename: careerpos

Informix filename: career_pos_rec





Career Skills record Maintains records of an individual’s skills.

UNIX filename: careerskl

Informix filename: career_skl_rec




Chapel/Convocation record Tracks a student’s attendance and absences from Chapel/Convocation events.

Note: Student Affairs contains three Csh scripts for processing Chapel/Convocation records, including:

− Add Attendance/Absence (chapadday) − Check Attendance Record (chapel) − Add Initial Records (chapadinit)

UNIX filename: chap

Informix filename: chap_rec


Program interrelationships: None


Chapel/Convocation Event table Maintains the Chapel/Convocation meeting dates for each session.

Note: Before you add new records of Chapel/Convocation events for a session, you must query all records for the session. When you query these records, the system automatically assigns the next available meeting number to your new record.

UNIX filename: tchap

Informix filename: chap_table


Program interrelationships: None


Grade Message record Maintains records of grade mailer messages with students.

UNIX filename: grdmsg

Informix filename: grdmsg_rec


Program interrelationships: stuentry

Product interrelationships: Student Affairs, Registration


Health record Maintains records of the health services performed for an individual.

UNIX filename: health

Informix filename: health_rec




Immunization record Maintains records of an individual’s immunizations.

UNIX filename: immune

Informix filename: immune_rec




Immunization table Maintains a list of codes that describe immunizations.

UNIX filename: timmune

Informix filename: immune_table




Insurance record Maintains records of an individual’s medical insurance.

UNIX filename: insure

Informix filename: insure_rec




Interviewee record Maintains records of interviewees.

UNIX filename: intvwee

Informix filename: intvwee_rec





Interviewer record Maintains records of interviewers.

UNIX filename: intvwer

Informix filename: intvwer_rec




Medical History record Maintains records of an individual’s medical history.

UNIX filename: medhist

Informix filename: medhist_rec




Medical History table Maintains a list of medical conditions that can be in an individual’s medical history.

UNIX filename: tmedhist

Informix filename: medhist_table




Personal Incident record Maintains records of incidents occurring on campus.

Note: Your institution must maintain records of personal and campus incidents as required by Public Law 101-542, the Criminal Awareness Act.

UNIX filename: stupers

Informix filename: stupers_rec


Program interrelationships: incdentry


Personal Incident table Defines codes that describe incidents.

UNIX filename: tstupers

Informix filename: stupers_table


Program interrelationships: incdentry



Position Skills record Maintains records of skills a position requires.

UNIX filename: posskl

Informix filename: pos_skl_rec




Special Conditions record Maintains records of an individual’s special medical conditions.

UNIX filename: speccond

Informix filename: speccond_rec




Special Conditions table Maintains a list of special medical conditions.

UNIX filename: tspeccond

Informix filename: speccond_table




Student Services record Stores student information that is external to academic, including vehicle registration, housing, and student government information.

Note: Student Affairs contains two SQL scripts for adding or updating Student Services records to students’ ID and Profile records for a session. They are as follows:

− Add Student Services record(addstuserv) − Update Student Services record(updstuserv)

UNIX filename: stuserv

Informix filename: stu_serv_rec


Program interrelationships: iibentry, placement, stuentry

Product interrelationships: Career Placement, Student Affairs

Student Affairs Technical Manual 21 Macros and Includes

SECTION 4 - STUDENT AFFAIRS MACROS AND INCLUDES

Overview

Introduction

This section provides reference information about macros and includes used to set up the Student Affairs and Career Placement products.

Relationship Among Macros, Includes, and C Programs

For all elements of the product other than C programs, m4 macros contain the definitions of features that have been designed to be modified for each institution. These macros, located under $CARSPATH/macros, are passed through the m4 processor.

CX contains an alternative method for the setting of features in C programs. Macros in the source code of C programs are not passed through the m4 processor because the C compiler has its own preprocessor, the cc.

To provide the same apparent functionality to C programs, a section in the include source directory has been allocated for a type of include file that acts as an intermediary between the m4 processor and the cc preprocessor. In operation, m4 macros are defined whose output is a valid cc macro. These m4 macros are placed in the include files. Then the include files are translated and the appropriate cc macro is placed in the include file. The installed include file is included by the C compiler at compile time so that the result of the compilation is influenced by the m4 macro.

General Installation Procedures

See the CX Implementation and Maintenance Technical Manual, for general procedures on setting and installing changes to macros and includes.

Macros and Includes 22 Student Affairs Technical Manual

Macros

Introduction

CX contains macros that define specific values used throughout the Student Affairs and Career Placement products. The macros and includes enable you to change the available options and functionality of the Student Affairs and Career Placement products without having to modify C code. By modifying macros, you can customize your implementation of the Student Affairs and Career Placement products and make the products easier to maintain.

Definition and Function

A macro is an instruction that causes the execution of a pre-defined sequence of instructions in the same source language. A macro consists of uppercase letters and underscores and is used in place of a text string within source files. CX expands the macro to the longer text during the installation process for a file. CX uses the following kinds of macros:

• Enable - Allow you to enable a feature of CX • DBS_COMMON - Allow you to define database values in screens • Periodic - Allow you to make changes on a periodic basis

Macros can perform one of the following functions: • Define defaults on a screen (_DEF) • Define valid values in a field (_VALID or _INCL) • Enable system modules (ENABLE_MOD) • Enable system features (ENABLE_FEAT) • Establish a valid value for an include

How to Locate Macros

To modify Student Affairs and Career Placement macros, access the following files: • $CARSPATH/macros/custom/placement • $CARSPATH/macros/custom/student

To access Common macros, access the $CARSPATH/macros/custom/common file.

Applocate Program

You can also locate macros using the applocate program. Applocate checks the descriptions of macro files for the product you specify and lists each file that it locates in a separate file in your home directory.

Note: To locate the macros used in Student Affairs and Career Placement, using Applocate, you must specify the product names:

• STUDENT/SERVICES

Follow these steps to run the Applocate program.

1. Select Utility Menu from the CX menu. The Utilities: Main menu appears.

2. Select File Options. The Utilities: File Options menu appears.

3. Select Locate Macro Values. The Locate Macro Values screen appears.

4. Select Table Lookup in the Macro Category field. A list of module names appears in a Table Lookup box.

5. Select a module name (e.g., STUDENT/SERVICES), and click OK. The Table Lookup box

Student Affairs Technical Manual 23 Macros and Includes

disappears.

6. Select Finish. The Output Parameters and Scheduling window appears.

7. Enter the following: • In the Time field, enter NOW • In the Background field, enter Y

8. Select Finish.

The system creates the file, applocate.out, and sends it to your home directory. Enable Macros

The following lists the Student Affairs enable macros located in the student macro file:

ÈNABLE_FEAT_CHAPEL’,`Y’ Defines whether to display the menu options dealing with chapel/convocation attendance on the Student Services menu. The macro’s default setting, Y, specifies that the Chapel/Convocation option appears on the Student Management: Student Services menu.

ÈNABLE_FEAT_EVENTS’,`Y’ Defines whether to display the menu options dealing with the scheduling of single or group events on the Housing/Events menu. The macro’s default setting, Y, specifies that the Event Scheduling option appears on the Student Services: Housing/Events menu.

ÈNABLE_FEAT_INCIDENT’,`Y’ Defines whether to display the menu options dealing with personal incidents on the Student Management: Main menu. The macro’s default setting, Y, specifies that the Personal/Campus Incident option appears on the Student Management: Main menu.

ÈNABLE_FEAT_STUSERV’,`N’ Defines whether to place housing and incident submenus on the Student Management: Student Services menu. The macro’s default setting, N, specifies that the Personal/Campus Incident and Housing/Events options will appear in the Student Management: Main menu. When the macro is set to Y, the Personal/Campus Incident and Housing/Events menus appear as submenus of the Student Management: Student Services menu.

The following lists the Placement enable macros located in the placement macro file:

‘ENABLE_FEAT_SITE_PLAC’, ‘N’ Defines whether the site logic will be used by the Placement program.

‘ENABLE_FEAT_PLAC_TICKLER’, ‘Y’ Defines whether the Tickler program (the automatic scheduling of Contact records) is to be used by the Placement office. The macro’s default setting, Y, specifies that the Tickler option appears on the Communications Management menu.

‘PLAC_ACE_DEF’, ‘ltrplace’ Defines the default letter ACE report most commonly used by the Placement office. Use ltrplace if letters are sent more often to students. Use ltrbus if letters are sent more often to businesses.

Macros and Includes 24 Student Affairs Technical Manual

Includes

Introduction

The Student Affairs and Career Placement products contain includes, which determine the features that are enabled in the products. An include can be either a compile option that enables or disables a feature, or a default value for a feature.

To enable a feature in the Student Affairs and Career Placement products, you must define an include in $CARSPATH/include/custom. To disable an include, comment out the include in the same file. See the CX System Reference Technical Manual, for more information on enabling and disabling includes. By modifying includes, you can customize your implementation of the Student Affairs and Career Placement products and make the products easier to maintain.

Purpose

An include allows you to activate or deactivate features in C programs without changing the C code. You can also specify compilation values for an entry program in the Student Affairs and Career Placement products.

Macro Dependency

Includes have a dependency on macros. Normally, you do not directly modify includes for the product. You must modify a corresponding macro value and then reinstall the include.

How to Locate Includes

To locate a Student Affairs or Career Placement include, access the $CARSPATH/include/custom file.

Note: For more information about using the MAKE processor and modifying includes, see the CX System Reference Technical Manual.

Associated Includes

The following list describes the modifications that may be required for the Student Affairs and Career Placement includes:

placement Contains customized values commonly used in the Placement program, including (for example):

• Office code for Development office • Contact record status code • Contact record code

Student Affairs Technical Manual 25 Program Files

SECTION 5 – JENZABAR CX PROGRAM FILES

Overview

Introduction

This section provides reference information about the files that relate to most CX programs. By understanding the file structure and the contents of the files, you can locate most of the information you need about any program.

Program Files Detailed

This section contains details about the following files:

Note: All other files for each CX program are standard C programming files with standard components and structure.

def.c The def.c file contains the declaration of external variables (including structures) that must be available to all source files in the program. These variables can also be initialized in this file. As with other C source files, the files also contain comments. The makedec command uses the def.c file to create the dec.h file.

mac.h The mac.h file contains preprocessor include and define statements, typedef statements, and structure template definition statements. The file also contains macro substitution defines and declarations of structures. This file is included in all source files during compilation through use of the dec.h file.

Definition File

Every program uses a definition (def.c) file, located in one of the following paths: • $CARSPATH/src/common/<program> • $CARSPATH/src/matric/<program> • $CARSPATH/src/regist/<program> • $CARSPATH/src/stuserv/<program> • $CARSPATH/src/placement/<program>

The def.c file for a screen-oriented program can contain the following information: • Includes for a mac.h file • Declaration of global variables and structures used throughout the program • Structure and non-structure screen binds (i.e., program buffer to screen buffer binds) • Ring menu definitions • Prompt line information • Program parameters • Declarations of dynamic memory (dmms, dmls, and dmlts) in relation to functionality within

libdmm (the dynamic memory management package) • Screen pointers

The def.c file for a non-screen-oriented program can contain the following information: • Includes for a mac.h file • Global program variables • Includes for schema files def.c files • Form pointers that provide the location for forms • Sqlda pointers that bind the file structure to the form • dmm, dml, and dmlt definitions

Program Files 26 Student Affairs Technical Manual

• Program parameters • Declarations of functions so the compiler can handle a call of that function

Example of a def.c File

The following is an edited excerpt from the def.c file for the Student Affairs program placement. It illustrates the common components of a standard CX def.c file.

Note: The legend for the file contents directly follows this example.


#include "mac.h" 1 /* ----- Common Related Records ----- */ #include <schema/common/iddef.c> /* ----- Business Related Records ----- */ #include <schema/common/busdef.c> 2 #include <schema/student/careerposdef.c> /* ----- Other Variable Definitons ----- */ int db_open = FALSE; /* DB was Opened? */ int init_scr_position = TRUE; /* Set to the top of the scroll region */ int posskl_current_rec; /* POSSKL Current record in the List */ int posskl_last_rec; /* POSSKL Last record in the List */ char sitecode[SITECODESIZE]; /* Buffer for Site Code Function */ 3 char tickcode[TICKCODESIZE]; /* Buffer for Tick Code Function */ char progcode[PROGSIZE]; /* Buffer for Program Code Function */ char bus_scr_path[40]; /* Business Process - Screen Path String Pointer */ char ctc_scr_path[40]; /* Business Process - Screen Path String Pointer */ char crpos_scr_path[40]; /* Business Process - Screen Path String Pointer */ /* ----- Structure Definitions ----- */ struct id_type id_rec; /* Business and Student Process */ struct intvwee_type intvwee_rec; /* Business Process */ struct profile_type profile_rec; /* Student Process */ 4 struct emp_type emp_rec; /* Placement Process */ /* ----- Employment DMM Definition ----- */ DMM_DEF(emp_dmm, struct emp_type); /* ----- Screen definitions and buffers grouped by screen ----- */ SCREEN *bus_scr = (SCREEN*)NULL; /* Business Screen */ SCREEN *crpos_scr = (SCREEN*)NULL; /* Career Position Screen */ /* ----- Parameter Type Structure Definition and Variable Sizes ----- */ struct param_type param_list[] = { {'p', progcode, PRM_CHAR, PROGSIZE - 1, PRM_REQUIRED, PLABEL, PDESCR}, {'t', tickcode, PRM_CHAR, TICKCODESIZE - 1, PRM_REQUIRED, TLABEL, TDESCR}, {'L', sitecode, PRM_CHAR, SITECODESIZE - 1, PRM_REQUIRED, LLABEL, LDESCR} }; int max_params = (sizeof(param_list)/sizeof(struct param_type)); /* ----- Database Files for Business and Student Processing ----- */ struct esql_dbfile_type filelist[] = { {ID_REC, id_fields, ID_NO, "id", FILE_CLOSE}, {BUS_REC, bus_fields, BUS_NO, "bus_no", FILE_CLOSE}, {CRPOS_REC, crpos_fields, CRPOS_NO, "crpos_no", FILE_CLOSE}, }; int filesize = ECFILE_SIZE(filelist); /* ----- Employment Menu Option Definition ----- */ SCR_MENUSTART(emp_mnuoptlst) SCR_MENUOPT2(0,"Business processing",'B',SCR_GMENABLE,(char *)NULL,NULL), 5 /* ----- getset Menu Definition ----- */ SCR_MENUSTART(menu_getset) SCR_MENUOPT2(0, NULL, SCR_DONE, SCR_GMENABLE, NULL, NULL), SCR_MENUOPT2(0, NULL, SCR_ABORT, SCR_GMENABLE, NULL, NULL), SCR_MENUEND; int menu_getset_size = SCR_MENUSIZE(menu_getset); /* ----- Scroll Career Position scget Menu Definition ----- */ SCR_MENUSTART(scrpos_menu_scget) SCR_MENUOPT2(0, NULL, SCR_DONE, SCR_GMENABLE, NULL, NULL), SCR_MENUSTART(scrpos_menu_scget) SCR_MENUOPT2(0, NULL, SCR_DONE, SCR_GMENABLE, NULL, NULL), d"), SCR_MENUOPT2(0, "Update Position", SCR_KEYU, SCR_GMENABLE, "Update Position. ", "update"), SCR_MENUEND; int scrpos_menu_scget_size = SCR_MENUSIZE(scrpos_menu_scget); int scareer_menu_scget_size = SCR_MENUSIZE(scareer_menu_scget); nt scareer_menu_scget_size = SCR_MENUSIZE(scareer_menu_scget); /* ----- Interviewer scget Menu Definition ----- */ SCR_MENUSTART(intvwer_menu_scget) SCR_MENUOPT2(0, NULL, SCR_DONE, SCR_GMENABLE, NULL, NULL), SCR_MENUOPT2(0, "schedule interviews", SCR_KEYN, SCR_GMENABLE, "Schedule Int erviews.", "meeting"), SCR_MENUEND; int intvwer_menu_scget_size = SCR_MENUSIZE(intvwer_menu_scget);


/* ----- Define the Size of the Business Process Menu Structure ----- */ int bus_proc_menu_size = SCR_MENUSIZE(bus_proc_menu);

SCR_MENUSTART(crpos_proc_menu) SCR_MENUOPT2(0, "Update", UPDATE_OPT, SCR_GMENABLE, "Update Position Detail. SCR_MENUEND; /* ----- Define the Career Position Process Menu Definition ----- */ DML_START(crpos_proc_menu_dml) DML_LEVEL(SCR_MENU), DML_END; DML_DEF(crpos_proc_menu_dml); /* ----- Student Process Menu Definition ----- */ SCR_MENUSTART(stu_proc_menu) SCR_MENUOPT2(0, "Query", QUERY_OPT, SCR_GMENABLE, "Query on a Student/Alum R ecord.", "query"), SCR_MENUEND; /* ----- Define the Size of the Business Process Menu Structure ----- */ int stu_proc_menu_size = SCR_MENUSIZE(stu_proc_menu); /* ----- Define the Employment Placement Process Menu Definition ----- */ 5 DML_START(emp_proc_menu_dml) DML_LEVEL(SCR_MENU), DML_END; DML_DEF(emp_proc_menu_dml); /* ----- Define Size of the Employment Placement Process Menu Structure ----- */ /* ----- Define Size of the Employment Placement Process Menu Structure ----- */ int emp_proc_menu_size = SCR_MENUSIZE(emp_proc_menu); /* ----- Menu Option List Definitions ----- */ char menu_opt_list[] = { BUS_OPT, /* 'B' */ CRPOS_OPT, /* 'P' */ CTC_OPT, /* 'T' */ EXIT_OPT, /* 'E' */ MENU_OPT, /* 'M' */ (char)NULL /* ' ' */ };

Legend for the def.c file: 1. mac.h include 2. schema file def.c’s 3. other program variables 4. structure definitions 5. other definitions

mac.h Files

Every program uses a macro header (mac.h) file, located in one of the following paths • $CARSPATH/src/common/<program> • $CARSPATH/src/matric/<program> • $CARSPATH/src/regist/<program> • $CARSPATH/src/stuserv/<program> • $CARSPATH/src/placement/<program>

The mac.h file for a screen-oriented program can contain the following information: • Includes related to system header files • Includes related to CX library and other application processes • Includes for schema files mac.h files • Program constant definitions (i.e., #define statements) • Structure definitions

Example of a mac.h File

The following is an edited excerpt from the mac.h file for placement. It illustrates the common components of a standard CX mac.h file.


Note: The legend for the file contents directly follows this example. /* ----- Include Header Files ----- */ #include <applic/placement.h> #include <custom/placement.h> /* ----- Common Related Records ----- */ #include <schema/common/idmac.h> /* ----- Business Related Records ----- */ #include <schema/common/busmac.h> #include <schema/student/careerposmac.h> 1 /* ----- Student Related Records ----- */ #include <schema/common/profilemac.h> #include <schema/student/progenrmac.h> /* ----- Placement Related Records ----- */ #include <schema/common/empmac.h> /* ----- Business/Student Related Records ----- */ #include <schema/common/ctcmac.h> /* ----- Buffer Size Definitions ----- */ #define BUFSIZE 255 /* String Size */ #define SITECODESIZE 5 /* String Size */ /* ----- Parameter Labels Definitions ----- */ #define PLABEL "program code" /* program code parameter */ #define LLABEL "site code" /* site code parameter */ /* ----- Parameter Description Definitions ----- */ #define PDESCR "Program code?" /* PLABEL */ #define LDESCR "Site code?" /* LLABEL */ /* ----- Menu Option Definitions ----- */ #define NULL_OPT ' ' #define EMP_OPT 'L' /* ---- Placement Error Checking Definitions ----- */ #define PLAC_MENU 1 /* No error, Go back to the Placement Main Menu */ #define PLAC_STAT 1 /* Stop the Subfunction, Continue Placement Process*/ 2 /* ----- Other Constant Definitions ----- */ /* ----- Other Constant Definitions ----- */ #define CARSDB "CARSDB" /* database environment variable */ /* ----- Business/Student Screen Path Definitions ----- */ #define CTC_SCR "placement/placement/ctc" /* Contact Screen */ /* ----- Business Screen Path Definitions ----- */ #define BUS_SCR "placement/placement/bus" /* Business Record Screen */ #define CRPOS_SCR "placement/placement/crpos" /* Career Position Screen */ /* ----- Student Screen Path Definitions ----- */ #define STUDENT_SCR "placement/placement/student" /* Student Screen */ #define CAREER_SCR "placement/placement/career" /* Career Screen */ /* ----- Employment Screen Path Definitions ----- */ #define QEMP_SCR "placement/placement/qemp" /* Query Employment Screen */ /* ----- Employment Screen Path Definitions ----- */ #define QEMP_SCR "placement/placement/qemp" /* Query Employment Screen */ #define EMP_SCR "placement/placement/emp" /* Employment Screen */ /* ----- Business Screen Group Definitions ----- */ #define IDGRP "idgrp" /* id group on bus or student screen */ #define BUSGRP "busgrp" /* bus group on the bus screen */ /* ----- Student Screen Group Definitions ----- */ #define STUDGRP "studentgrp" /* student group on student screen */ #define CAREERGRP "careergrp" /* career group on the career screen */ #define CRSKLGRP "crsklgrp" /* career skill group on the crskl screen */ /* ----- Employment Screen Group Definitions ----- */ #define QEMPGRP "qempgrp" /* employment group on query employment screen */


Legend for the mac.h file: 1. includes for header files 2. includes for schema files

Student Affairs Technical Manual 31 Event Entry

SECTION 6 - EVENT ENTRY

Overview

Introduction

This section provides reference information about the Event Entry program. The Student Affairs product uses Event Entry to enter and maintain information pertaining to an event.

Program Features Detailed

This section contains details about the following features of the Event Entry program: • Process flow • Parameters • Program screens

Event Entry 32 Student Affairs Technical Manual

Process Flow

Diagram

The following diagram shows the flow of data in the Event Entry program.

Enter event information

Generate reports ofevents

Update eventinformation

Data Flow Description

The following describes the data flow in the Event Entry program.

1. The user enters event information using Event Entry screens.

2. The user obtains reports of scheduled events using Event Entry report menu options.

3. The user updates event information as necessary.

Program Relationships

The following programs use Event Entry. • libentry

Tables and Records Used

The eventry program uses the following Common and Event Entry tables and records.

Note: For information about the Common tables and records, see the CX System Reference Technical Manual. For information about the Event Entry tables and records, see the section Student Affairs Tables and Records in this manual.

Common tables and records • evnt_rec


Event Entry tables and records • None

Special Function Flags

The following records used by Event Entry have special function flags.

evnt_rec ENT_LOCK - Locks the Event record so other users cannot select or update at the same time.


Parameters

Introduction

CX contains parameters and compilation values for executing the Event Entry program. You can specify parameters to compile Event Entry in a specified manner at the time of execution.

Note: You can also specify compilation values with the includes for the Student Affairs product that affect the Event Entry program.

Parameter Syntax

You can display eventry parameters by entering the following: eventry -, The following is the correct usage for running the Event Entry program from the UNIX shell:

eventry [-d] [-m menuname] [-f form_selected] [-t today] [-L site] [-P scr_path] [-a] [-F] [-M menu_title] [-q] [-D debug_level] [-S pause_level] [-w idtype_screen]

Parameters that appear in brackets are optional. Parameters that do not appear in brackets are required.

Parameters

The following lists the parameters for running Event Entry.

-d Optional - Specifies access to Event Entry in display-only mode.

-m menuname Optional - Specifies the name of the menu screen you want to access directly, where menuname represents the menu name. The default value in Event Entry is evmenu.

Example: eventry -m evmenu

-f form_selected Optional - Specifies the name of the form you want to access directly, where form_selected represents the form name.

Example: eventry -f xxxx

-t today Optional - Specifies the effective date for changes to data, where today represents the data you specify.

Example: eventry -t 09/01/2000

-L site Optional - Specifies your site code, where site represents the site code you specify.

Example: eventry -L cars

-P scr_path Optional - Specifies the path for the Event Entry screens, where scr_path represents the path where the Event Entry screens reside on your system. The default in Event Entry is common/progscr/eventry/.

-a Optional - Specifies that Event Entry will automatically enter Query mode.


-F Optional - Specifies that Event Entry will force you to query the database for a record before you can enter Insert mode.

-M menu_title Optional - Specifies a change to the ring menu title, where menu_title represents the title you specify.

Example: eventry -M Event Entry

Note: This parameter applies only to character mode ring menus.

-q Optional - Specifies that you can select additional restrictions for querying an event’s record. When you select the ID Lookup command in Query mode, you can specify that the search for an event’s record be based on one of the following records:

• id_rec • site_rec

-D debug_level Optional - Specifies the level of debug messages to be displayed, where debug_level represents the message level (1-9). To receive more messages, you must specify a higher level.

-S pause_level Optional - Specifies the level of pauses for Event Entry, where pause_level represents the pause level (1-9). To have more pauses, you must specify a lower number.

-W idtype_screen Optional - Specifies the path for the ID-Type window, where idtype_screen represents the path and filename of the ID-Type window. The default in Event Entry is Lib/libids/type.c.


Program Screens and Windows

Introduction

Event Entry has screens and windows for performing the following interactive functions: • Entering or updating information pertaining to an event, including a description, location,

sponsor, and scheduled date and time • Entering report parameters to produce reports of event information

Access

The screen and window files for Event Entry are located in the following directory path: • $CARSPATH/modules/common/progscr/eventry

Note: You can access windows from each program screen in Event Entry.

See the CX System Reference Technical Manual for information about common windows that appear in Event Entry.

Screen Files and Table/Record Usage

The Event Entry screens and windows appear in the following files and use the indicated tables and records.

events Contains the Events Scheduling - Event Entry screen.

Access: $CARSPATH/modules/common/progscr/eventry

Tables/Records: • bldg_table • evnt_rec • facil_table • id_rec

events_q Contains the Events Scheduling - Event Entry screen.


Tables/Records: • evnt_rec • facil_table • id_rec

evmenu Contains the Events Scheduling - Event Entry screen.


Tables/Records: None

evntlst Contains the Events Scheduling - Event Entry screen.


Tables/Records: • evnt_rec

Student Affairs Technical Manual 37 Health Entry

SECTION 7 - HEALTH ENTRY

Overview

Introduction

This section provides reference information about the Health Entry program. The Student Affairs product uses Health Entry to maintain records pertaining to a student’s medical history and the health services provided by the institution.


This section contains details about the following features of the Health Entry program: • Process flow • Parameters • Program screens • Detail windows

Health Entry 38 Student Affairs Technical Manual

Process Flow

Diagram

The following diagram shows the flow of data in the Health Entry program.

Enter student healthinformation

Generate studenthealth reports

Perform tablemaintenance

Update student healthinformation


The following describes the data flow in the Health Entry program.

1. The user enters students’ health information using Health Services Entry screens.

2. The user obtains students’ health reports using health report menu options.

3. The user performs table maintenance of health tables as necessary.

4. The user updates students’ health information as necessary.


The following programs use Health Entry:


• libentry


The Health Entry program uses the following Common and Health Entry tables and records:

Note: For information about the Common tables and records, see the CX System Reference Technical Manual. For information about the Health Entry tables and records, see the section Student Affairs Tables and Records in this manual.

Common tables and records • addree_rec • adr_rec • ctc_rec • ctry_table • cty_table • denom_table • emp_rec • ethnic_table • facil_table • hold_rec • hold_table • id_rec • occ_table • ofc_table • profile_rec • relation_rec • rel_sec • rel_table • st_table • stu_serv_rec • tick_table • title_table • userid_table

Health Entry tables and records • allergy_rec • allergy_table • hand_table • health_rec • immune_rec • immune_table • insure_rec • medhist_rec • medhist_table • speccond_rec • speccond_table


The following records used by Health Entry have special function flags:

ctc_rec • ENT_SCSTART - Provides an alternate sorting of the Contact records. Checked at the

entry of a scrolling region.


• ENT_SGGET - Filters out Contact records that are not of interest or should not be seen. Checked during the retrieval of each row within a scrolling region.


• ent_spec_func - Enables the sorting and filtering logic available on detail windows.

Note: The ent_spec_func function uses the setup information from the entsel_table and entselcrit_table.

The ent_spec_func function requires the setting of special function flags ENT_SCSTART and ENT_SCGET for the table in the filename array. At entry of the scroll region, ENT_SCSTART sorts the Contact records based upon the current sort criteria. When retrieving rows for display, ENT_SCGET checks the rows and displays or skips them.

emp_rec • ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region

via a PTP (process-to-process) connection to ID Entry (identry).

hold_rec • ENT_VALUEPERM -

id_rec • ENT_FLGET - Triggers when the system reads an ID record from the database and after

the system copies the rec_c buffer into the rec_p buffer.

Note: The function ignores return statuses.

• ENT_FLUPD - Triggers after the system updates an ID record. When the function returns a non-ENT_OK status, the system stops the update process for the table. The return status tells the system that only a partial update will be committed to the database.

• idperm - Performs a table lookup to verify that a user's UID or GID is entered in the idperm_table for the office code on the id_rec or associated profile_rec being updated.

Note: The idperm function requires the use of the ENT_FLGET and ENT_FLUPD special flags.

The idperm function does not allow the system to update the database with any changes to the id and profile columns on the screen.

medhist_rec • ENT_SCSTART - Provides an alternate sorting of the Medical History records. Checked at

the entry of a scrolling region. • ENT_SGGET - Filters out Medical History records that are not of interest or should not be

seen. Checked during the retrieval of each row within a scrolling region. • ent_spec_func - Enables the sorting and filtering logic available on detail windows.


The ent_spec_func function requires the setting of special function flags ENT_SCSTART and ENT_SCGET for the table in the filename array. At entry of the scroll region, ENT_SCSTART sorts the Medical History records based upon the current sort criteria. When retrieving rows for display, ENT_SCGET checks the rows and displays or skips them.

profile_rec • ENT_AUTOINS - Allows the user to add Profile records without modifying the default

values. If this flag is not used, the system adds a Profile record only when a user changes a column value within the record.

• ENT_FLGET - Triggers when the system reads a Profile record from the database and after the system copies the rec_c buffer into the rec_p buffer.

Note: This event ignores return statuses.


• ENT_FLUPD - Triggers after the system updates a Profile record. When the function returns a non-ENT_OK status, the system stops the update process for the table. The return status tells the system that only a partial update will be committed to the database.

relation_rec • ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region


relsec_rec • ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region



Parameters

Introduction

CX contains parameters and compilation values for executing the Health Entry program. You can specify parameters to compile Health Entry in a specified manner at the time of execution.

Note: You can also specify compilation values with the includes for the Student Affairs product that affect the Health Entry program.

Parameter Syntax

You can display Health Entry parameters by entering the following: hentry -, The following is the correct usage for running the Health Entry program from the UNIX shell:

hentry [-d] [-m menuname] [-o ofc_added_by] [-f form_selected] [-t today] [-P scr_path] [-M] [-F] [-D debug_level] [-S pause_level] [-e menu_title] [-q] [-w idtype_screen]


Parameters

The following lists the parameters for running Health Entry:

-d Optional - Specifies access to Health Entry in display-only mode.

-m menuname Optional - Specifies the name of the menu screen you want to access directly, where menuname represents the menu name. The default is idmenu.

Example: hentry -m idmenu

-o ofc_added_by Optional - Specifies your office code, where ofc_added_by represents the office code you specify. The default is NOFC.

Example: hentry -o NOFC


Example: hentry -f health_1

-t today Optional - Specifies the effective date for changes to data, where today represents the date you specify.

Example: hentry -t 09/15/2000

-P scr_path Optional - Specifies the path for the Health Entry screens, where scr_path represents the path where the Health Entry screens reside on your system. The default is common/identry/.

Example: hentry -P common/identry/

-M


Optional - Specifies that Health Entry will not automatically enter query mode.

-F Optional - Specifies that Health Entry will force you to query the database for a record before you can enter insert mode.


-S pause_level Optional - Specifies the level of pauses for Health Entry, where pause_level represents the pause level (1-9). To have more pauses, you must specify a lower number.

-e menu_title Optional - Specifies a change to the ring menu title, where menu_title represents the title you specify.

Example: hentry -M Health Services


-q Optional - Specifies that you can select additional restrictions for querying an individual’s record. When you select the ID Lookup command in query mode, you can specify that the search for an individual’s record be based on one of the following records:

• ID record (id_rec) • Profile record (profile_rec) • Health record (health_rec)

-w idtype_screen Optional - Specifies the path for the ID-Type window; where idtype_screen represents the path and filename of the ID-Type window. The default is Lib/libids/type.c.

Example: hentry -w $CARSPATH/src/Lib/libids/type.c



Introduction

Health Entry has screens and windows for performing the following interactive functions: • Entering Health records for students • Accessing either the ID Entry for Health Provider or Health Services for Students screens • Entering an ID record describing a health provider

Access

The screen and window files for Health Entry are located in the following directory path: • $CARSPATH/modules/matric/progscr/hentry

Note: You can access windows from each program screen in Health Entry.

See the CX System Reference Technical Manual for information about common windows that appear in Health Entry.


The Health Entry screens and windows appear in the following files and use the indicated tables and records:

allergy Contains the Allergic Reactions detail window.

Access: $CARSPATH/modules/matric/progscr/hentry/allergy

Tables/Records: • allergy_rec • allergy_table

health_1 Contains the Health Services for Students screen.

Access: $CARSPATH/modules/matric/progscr/hentry/health_1

Tables/Records: • ctry_table • ethnic_table • hand_table • health_rec • id_rec • profile_rec • st_table • title_table

hmenu Contains the Health Services menu screen.

Access: $CARSPATH/modules/matric/progscr/hentry/hmenu



immune Contains the Immunizations detail window.

Access: $CARSPATH/modules/matric/progscr/hentry/immune

Tables/Records: • immune_rec • immune_table

insure Contains the Insurance detail window.

Access: $CARSPATH/modules/matric/progscr/hentry/insure

Tables/Records: insure_rec

medhist Contains the Medical Visit History detail window.

Access: $CARSPATH/modules/matric/progscr/hentry/medhist

Tables/Records: • id_rec • medhist_rec • medhist_table

provide_1 Contains the ID Entry for Health Provider screen.

Access: $CARSPATH/modules/matric/hentry/progscr/provide_1

Tables/Records: • cty_table • ctry_table • ethnic_table • id_rec • occ_table • profile_rec • st_table • title_table

speccond Contains the Special Conditions detail window.

Access: $CARSPATH/modules/matric/progscr/hentry/speccond

Tables/Records: • speccond_rec • speccond_table

Student Affairs Technical Manual 47 Incident Entry

SECTION 8 - INCIDENT ENTRY

Overview

Introduction

This section provides reference information about the Incident Entry program. The Student Affairs product uses Incident Entry to maintain records of personal and campus incidents as required by Public Law 101-542.


This section contains details about the following features of the Incident Entry program: • Process flow • Parameters • Program screens • Detail windows

Incident Entry 48 Student Affairs Technical Manual

Process Flow

Diagram

The following diagram shows the flow of data in the Incident Entry program.

Enter incidentinformation

Generate incidentreports


Update incidentinformation


The following describes the data flow in the Incident Entry program.

1. The user enters students’ incident information using Incident Entry screens.

2. The user obtains students’ incident reports using incident report menu options.

3. The user performs table maintenance of incident tables as necessary.

4. The user updates students’ incident information as necessary.


The following programs use Incident Entry.


• libentry


The incdentry program uses the following Common and Incident Entry tables and records.

Note: For information about the Common tables and records, see the CX System Reference Technical Manual. For information about the Incident Entry tables and records, see the section Student Affairs Tables and Records in this manual.

Common tables and records • id_rec • profile_rec • zip_table

Incident Entry tables and records • stupers_rec


The following records used by Incident Entry have special function flags.

id_rec • ENT_LOCK - Locks the ID record so other users cannot select or update at the same time.

profile_rec • ENT_LOCK - Locks the Profile record so other users cannot select or update at the same

time.

stupers_rec • ENT_LOCK - Locks the Personal Incident record so other users cannot select or update at

the same time. • ENT_SCSTART - Provides an alternate sorting of the Personal Incident records. Checked

at the entry of a scrolling region. • ENT_SGGET - Filters out Personal Incident records that are not of interest or should not be


Note: The ent_spec_func function uses the setup information from the entsel_table and entselcrit table.

Note: The ent_spec_func function requires the setting of special function flags ENT_SCSTART and ENT_SCGET for the table in the filename array. At entry of the scroll region, ENT_SCSTART sorts the Personal Incident records based upon the current sort criteria. When retrieving rows for display, ENT_SCGET checks the rows and displays or skips them.


Parameters

Introduction

CX contains parameters and compilation values for executing the Incident Entry program. You can specify parameters to compile Incident Entry in a specified manner at the time of execution.

Note: You can also specify compilation values with the includes for the Student Affairs product that affect the Incident Entry program.

Parameter Syntax

You can display incdentry parameters by entering the following: incdentry -, The following is the correct usage for running the Incident Entry program from the UNIX shell:

incdentry [-d] [-m menuname] [-f form_selected] [-t today] [-L site] [-P scr_path] [-a] [-F] [-M menu_title] [-q] [-D debug_level] [-S pause_level] [-w idtype_screen]


Parameters

The following lists the parameters for running Incident Entry.

-d Optional - Specifies access to Incident Entry in display-only mode.

-m menuname Optional - Specifies the name of the menu screen you want to access directly, where menuname represents the menu name. The default is incdmenu.

Example: incdentry -m incdmenu


Example: incdentry -f health_1


Example: incdentry -t 09/15/2000

-L site Optional - Specifies your site code, where site represents the site code you specify.

Example: incdentry -L cars

-P scr_path Optional - Specifies the path for the Incident Entry screens, where scr_path represents the path where the Incident Entry screens reside on your system. The default is stuserv/incdentry/.

Example: incdentry -P stuserv/incdentry/


-a Optional - Specifies that Incident Entry will automatically enter Query mode.

-F Optional - Specifies that Incident Entry will force you to query the database for a record before you can enter insert mode.


Example: incdentry -M Incident Entry



• ID record (id_rec) • Profile record (profile_rec)


-S pause_level Optional - Specifies the level of pauses for Incident Entry, where pause_level represents the pause level (1-9). To have more pauses, you must specify a lower number.


Example: incdentry -w $CARSPATH/src/Lib/libids/type.c



Introduction

Incident Entry has screens and windows for performing the following interactive functions: • Maintaining records of personal incidents • Setting parameters to produce a report of a student’s incidents • Setting parameters to list totals of all crimes recorded on campus • Querying Personal Incident records • Maintaining a table of incidents • Printing the contents of the Personal Incident table

Access

The screen and window files for Incident Entry are located in the following directory paths: • $CARSPATH/modules/stuserv/progscr/incdentry

Note: You can access windows from each program screen in Incident Entry

See the CX System Reference Technical Manual for information about common windows that appear in Incident Entry.


The Incident Entry screens and windows appear in the following files and use the indicated tables and records.

incd Contains the Personal/Campus Incident Form screen.

Access: $CARSPATH/modules/stuserv/progscr/incdentry

Tables/Records: • aa_table • ctry_table • cty_table • ethnic_table • id_rec • profile_rec • st_table • suffix_table • title_table • zip_table

incdmenu Contains the Incident Entry menu.




stupers Contains the Personal/Campus Incident Record detail window.


Tables/Records: • id_rec • sess_table • stupers_rec • stupers_table

Student Affairs Technical Manual 55 Career Placement

SECTION 9 - CAREER PLACEMENT

Overview

Introduction

This section provides reference information about the Career Placement program. The Student Affairs product uses Career Placement to enter and maintain business, student, and employment placement information that is necessary to match participants with available positions.


This section contains details about the following features of the Career Placement program: • Process flow • Parameters • Program screens • Detail windows

Career Placement 56 Student Affairs Technical Manual

Process Flow

Diagram

The following diagram shows the flow of data in the Career Placement program.


Enter businessinformation

Enter student careergoal information

Enter contacts

Enter interviewschedule information

Update informationabout available

positions




The following describes the data flow in the Career Placement program.

1. The user enters business information including available positions at a business.

2. The user enters students’ career goal information using Career Placement screens.

3. The user enters contacts to track correspondence with the business.

4. The user enters schedule information about interviewers and interviewees.

5. The user updates information about available positions at a business.

6. The user performs table maintenance of placement tables as necessary.


The following programs use Career Placement. • None


The placement program uses the following Common and Career Placement tables and records.

Note: For information about the Common tables and records, see the CX System Reference Technical Manual. For information about the Career Placement tables and records, see the section Student Affairs Tables and Records in this manual.

Common tables and records • bus_rec • ctc_rec • emp_rec • id_rec • profile_rec • progenr_rec

Career Placement tables and records • career_rec • career_pos_rec • career_skl_rec • intvwee_rec • intvwer_rec • pos_skl_rec • site_rec


The following records used by Career Placement have special function flags: None


Parameters

Introduction

CX contains parameters and compilation values for executing the Career Placement program. You can specify parameters to compile Career Placement in a specified manner at the time of execution.

Note: You can also specify compilation values with the includes for the Student Affairs product that affect the Career Placement program.

Parameter Syntax

You can display placement parameters by entering the following: placement -, The following is an example of the correct usage for running the Career Placement program from the UNIX shell:

placement -p “UNDG” -t “ADM” -L “CARS” Parameters that appear in brackets are optional. Parameters that do not appear in brackets are required.

Parameters

The following lists the parameters for running Career Placement.

-p Required - Specifies a program code.

Example: placement -p

-t Required - Specifies a tickler code.

Example: placement -t

-L Required - Specifies a site code

Example: placement -L



Purpose

Career Placement has screens and windows for performing the following interactive functions: • Entering or updating business information • Entering or updating student/alumni information • Entering or updating employment information

Access

The screen and window files for Career Placement are located in the following directory paths: • $CARSPATH/src/placement/placement/SCR • $CARSPATH/modules/placement/progscr/placement

Note: You can access windows from each program screen in Career Placement.

See the CX System Reference Technical Manual for information about common windows that appear in Career Placement.


The Career Placement screens and windows appear in the following files and use the indicated tables and records.

bus Contains the Student/Alumni Placement - Business Form screen.

Access: $CARSPATH/modules/placement/progscr/placement

Tables/Records: • aa_table • bus_rec • ctry_table • id_rec • st_table • title_table • zip_table

career Contains the Career Goal window.


Tables/Records: • career_rec • pos_type_table

crpos Contains the Position window.


Tables/Records: • career_pos_rec • deg_table • major_table • pos_type_table


crskl Contains the Career Goal Skills window.


Tables/Records: • career_skl_rec • cr_skl_table

ctc Contains the Contacts screen.


Tables/Records: • ctc_rec • ctc_table • id_rec

emp Contains the Student/Alumni Placement window.


Tables/Records: • emp_rec • id_rec • occ_table

intvwee Contains the Schedule Interview window.


Tables/Records: • id_rec • intvwee_rec

intvwer Contains the Interview Schedule window.


Tables/Records: • id_rec • intvwer_rec

posskl Contains the Position Skills window.


Tables/Records: • cr_skl_table • pos_skl_rec

qemp Contains the Student/Alumni Placement - Employment Query Form screen.


Tables/Records: id_rec


scareer Contains the Career Goal Listing window.


Tables/Records: • career_rec • pos_type_table

scrpos Contains the Position Listing window.


Tables/Records: • career_pos_rec • pos_type_table

student Contains the Student/Alumni Placement - Placement Form screen.


Tables/Records: • cl_table • conc_table • ctry_table • cty_table • deg_table • ethnic_table • id_rec • major_table • minor_table • profile_rec • prog_enr_rec • prog_table • st_table • title_table • zip_table

Student Affairs Technical Manual 63 Student Entry

SECTION 10 - STUDENT ENTRY

Overview

Introduction

This section provides reference information about the Student Entry program. The Student Affairs and Career Placement products use Student Entry to build on a student’s records initially entered by the Admissions office and to enter housing and vehicle registration records. You access the Student Entry program to enter student services data, such as housing and vehicle registration information.


This section contains details about the following features of the Student Entry program: • Process flow • Parameters • Program screens • Detail windows

Student Entry 64 Student Affairs Technical Manual

Process Flow

Diagram

The following diagram shows the flow of data in the Student Entry program.

Update student's IDand Profile records

Enter or update studentservices data

Generate studentreports


The following describes the data flow in the Student Entry program:

1. The user updates a student’s ID and Profile records initially entered by the Admissions office using Student Entry screens.

2. The user enters or updates student services data, such as housing and vehicle registration records.

3. The user obtains student reports, such as the Student Profile report, using report menu options in the Student Entry program.


The following programs use Student Entry: • libentry


The Student Entry program uses the following Common and Student Entry tables and records:

Note: For information about the Common tables and records, see the CX System Reference Technical Manual. For information about the Student Entry tables and records, see the section Student Affairs Tables and Records in this manual.


Common tables and records • accomp_rec • addree_rec • adr_rec • bus_rec • church_rec • ctc_rec • ctc_table • ed_rec • emp_rec • exam_rec • fac_rec • hold_rec • id_rec • int_rec • involve_rec • milit_rec • profile_rec • relation_rec • relsec_rec • sap_rec • tick_rec • zip_table

Student Entry tables and records • adm_rec • grdmsg_rec • prog_enr_rec • sch_rec • site_rec • stu_acad_rec • stu_serv_rec • stu_stat_rec


The following records used by Student Entry have special function flags:

accomp_rec • ENT_SCSTART - Provides an alternate sorting of Accomplishment records. Checked at

the entry of a scrolling region. • ENT_SGGET - Filters out Accomplishment records that are not of interest or should not be

seen. Checked during the retrieval of each Accomplishment record within a scrolling region.

ctc_rec • ENT_SCSTART - Provides an alternate sorting of the Contact records. Checked at the

entry of a scrolling region. • ENT_SGGET - Filters out Contact records that are not of interest or should not be seen.

Checked during the retrieval of each row within a scrolling region.





ed_rec ENT_FLUPD - ENT_SCWRITE -

emp_rec ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region via a PTP (process-to-process) connection to ID Entry (identry).

grdmsg_rec • ENT_SCSTART - Provides an alternate sorting of the Grade Message records. Checked at

the entry of a scrolling region. • ENT_SGGET - Filters out Grade Message records that are not of interest or should not be



The ent_spec_func function requires the setting of special function flags ENT_SCSTART and ENT_SCGET for the table in the filename array. At entry of the scroll region, ENT_SCSTART sorts the Grade Message records based upon the current sort criteria. When retrieving rows for display, ENT_SCGET checks the rows and displays or skips them.

hold_rec ENT_FORCELOAD - ENT_VALUEPERM -

id_rec • ENT_FLGET - Triggers when the system reads an ID record from the database and after


Note: The function ignores return statuses. • ENT_FLUPD - Triggers after the system updates an ID record. When the function

returns a non-ENT_OK status, the system stops the update process for the table. The return status tells the system that only a partial update will be committed to the database.

• idperm - Performs a table lookup to verify that a user's UID or GID is entered in the idperm_table for the office code on the id_rec or associated profile_rec being updated.

Note: The idperm function requires the use of the ENT_FLGET and ENT_FLUPD special flags.

The idperm function does not allow the system to update the database with any changes to the id and profile columns on the screen.


profile_rec • ENT_FLGET - Triggers when the system reads a Profile record from the database and after


Note: This event ignores return statuses.

• ENT_FLUPD - Triggers after the system updates a Profile record. When the function returns a non-ENT_OK status, the system stops the update process for the table. The return status tells the system that only a partial update will be committed to the database.

• ENT_AUTOINS - Allows the user to add Profile records without modifying the default values. If this flag is not used, the system adds a Profile record only when a user changes a column value within the record.

prog_enr_rec • ENT_FORCELOAD -

relation_rec ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region via a PTP (process-to-process) connection to ID Entry (identry).

relsec_rec ENT_ADDID - Allows the ability to add or update an ID from within the related scroll region via a PTP (process-to-process) connection to ID Entry (identry).

sap_rec • ENT_SCSTART - Provides an alternate sorting of the Satisfactory Academic Progress

records. Checked at the entry of a scrolling region. • ENT_SGGET - Filters out Satisfactory Academic Progress records that are not of interest or

should not be seen. Checked during the retrieval of each row within a scrolling region. • ent_spec_func - Enables the sorting and filtering logic available on detail windows.



site_rec ENT_AUTOINS - Allows the user to add new Site records without modifying the default values. If this flag is not used, the system adds a Site record only when a user changes a column value within the record.

stu_acad_rec • ENT_SCSTART - Provides an alternate sorting of the Student Academic records. Checked

at the entry of a scrolling region. • ENT_SGGET - Filters out Student Academic records that are not of interest or should not

be seen. Checked during the retrieval of each row within a scrolling region.





stu_serv_rec • ENT_SCSTART - Provide an alternate sorting of the Student Service records. Checked at

the entry of a scrolling region. • ENT_SCGET - Filters out Student Services records that are not of interest or shouldn't be




tick_rec ENT_AUTOINS - Allows the user to add new Tickler records without modifying the default values. If this flag is not used, the system adds a Tickler record only when a user changes a column value within the record.


Parameters

Introduction

CX contains parameters and compilation values for executing the Student Entry program. You can specify parameters to compile Student Entry in a specified manner at the time of execution.

Note: You can also specify compilation values with the includes for the Student Affairs product that affect the Student Entry program.

Parameter Syntax

You can display Student Entry parameters by entering the following: stuentry -, The following is the correct usage for running the Student Entry program from the UNIX shell:

stuentry [-d] [-T tick] [-o ofc_added_by] [-m menuname] [-f form_selected] [-t today] [-L site][-P scr_path] [-a] [-F] [-M menu_title] [-q] [-p prog] [-k] [-D debug_level] [-S pause_level] [-w idtype_screen]


Parameters

The following lists the parameters for running Student Entry:

-d Optional - Specifies access to Student Entry in display-only mode.

-T tick Optional - Specifies a default tickler code, where tick represents the tickler code you specify. The default is REG (Registrar).

Example: stuentry -T REG

-o ofc_added_by Optional - Specifies your office code, where ofc_added_by represents the office code you specify. The default is REG (for Registrar).

Example: stuentry -o REG

-m menuname Optional - Specifies the name of the menu screen you want to access directly, where menuname represents the menu name. The default is stumenu.

Example: stuentry -m stumenu


Example: stuentry -f studata_1


Example: stuentry -t 09/15/1995

-L site


Optional - Specifies your site code, where site represents the site code you specify.

Example: stuentry -L cars

-P scr_path Optional - Specifies the path for the Student Entry screens, where scr_path represents the path where the Student Entry screens reside on your system. The default is regist/progscr/stuentry/.

Example: stuentry -P regist/progscr/stuentry/

-a Optional - Specifies that Student Entry will automatically enter query mode.

-F Optional - Specifies that Student Entry will force you to query the database for a record before you can enter insert mode.


Example: stuentry -M Student Services



• ID record (id_rec) • Profile record (profile_rec) • Program Enrollment record (prog_enr_rec) • Site record (site_rec)

-p prog Optional - Specifies your program code, where prog represents the program code you specify to check student permissions.

Example: stuentry -p UNDG

-k Optional - Specifies that Student Entry will check student permissions.


-S pause_level Optional - Specifies the level of pauses for Student Entry, where pause_level represents the pause level (1-9). To have more pauses, you must specify a lower number.


Example: stuentry -w $CARSPATH/src/Lib/libids/type.c



Introduction

Student Entry has screens and windows for performing the following interactive functions: • Entering or updating information about a church in which a student is a member • Adding or updating a record for a student’s graduation • Entering information about a student’s parents • Entering or updating a student’s ID and profile information • Adding or updating a record that contains a student’s academic program information • Entering information about a school that a student attended or is currently attending, or

about a school from which your institution recruits students • Adding or updating a student’s housing information • Adding graduation information to a student’s academic program information • Selecting a form in which to enter an aspect of a student’s information

Access

The screen and window files for Student Entry are located in the following directory paths: • $CARSPATH/modules/regist/progscr/stuentry • $CARSPATH/modules/Lib/progscr/libentry

Note: You can access windows from each program screen in <Program>.

See the CX System Reference Technical Manual for information about common windows that appear in XXXX.


The Student Entry screens and windows appear in the following files and use the indicated tables and records:

church_1 Contains the Data Entry - Church Form screen.

Access: $CARSPATH/modules/Lib/progscr/libentry

Tables/Records: • church_rec • ctry_table • denom_table • id_rec • st_table • zip_table


grad_1 Contains the Data Entry - Graduation Form screen.

Access: $CARSPATH/modules/regist//progscr/stuentry

Tables/Records: • cty_table • ctry_table • id_rec • prog_enr_rec • sess_table • st_table • title_table

parent_1 Contains the Data Entry - Parent Form screen.


Tables/Records: • aa_table • ctry_table • cty_table • ethnic_table • id_rec • profile_rec • rel_table • relation_rec • st_table • suffix_table • title_table • zip_table

progenr_1 Contains the Data Entry - Program Enrollment screen (screen 1 of 2).

Access: $CARSPATH/modules/regist/progscr/stuentry

Tables/Records: • acad_stat_table • cat_table • cl_table • conc_table • ctry_table • cty_table • deg_table • ethnic_table • id_rec • major_table • minor_table • profile_rec • prog_enr_rec • prog_table • sess_table • site_rec • st_table • subprog_table


• title_table • transfrm_table • zip_table

progenr_2 Contains the Data Entry - Program Enrollment screen (screen 2 of 2).


Tables/Records: • acad_stat_table • cl_table • conc_table • ctry_table • cty_table • currenr_table • degree_table • entrtype_table • ethnic_table • id_rec • major_table • minor_table • profile_rec • prog_enr_rec • prog_table • reason_table • sess_table • st_table • subprog_table • title_table • transfrm_table • zip_table

sch_1 Contains the Data Entry - School Form screen.


Tables/Records: • aa_table • cacode_table • ctry_table • cty_table • denom_table • id_rec • sch_rec • st_table • zip_table

site Contains the Site detail window.


Tables/Records: • site_rec


stuacad Contains the GPA/Session detail window.


Tables/Records: • cl_table • prog_table • stu_acad_rec • subprog_table

studata_1 Contains the Data Entry - Student Data Form screen.


Tables/Records: • aa_table • ctry_table • cty_table • ethnic_table • id_rec • priv_table • profile_rec • prog_enr_rec • site_rec • st_table • title_table • zip_table

stuhsg_1 Contains the Housing Data Entry - Student Housing Form screen.


Tables/Records: • bldg_table • ctry_table • cty_table • facil_table • id_rec • profile_rec • sess_table • st_table • stu_serv_rec • title_table

stumenu Contains the Data Entry - Form Menu.




stuserv Contains the Residence Hall detail window.


Tables/Records: • bldg_table • facil_table • sess_table • stu_serv_rec

stustat Contains the GPA Totals detail window.


Tables/Records: • prog_table • sess_table • stu_stat_rec

Student Affairs Technical Manual 77 Menus, Screens, Scripts, and Reports

SECTION 11 - MENUS, SCREENS, SCRIPTS, AND REPORTS

Overview

Introduction

This section provides reference information on the following features of the Student Affairs and Career Placement products:

• Menu source files • Menu option files • PERFORM screens • SQL scripts • Csh scripts • ACE reports • Letters

Directory Locations

The features detailed in this section are located in the following directory paths:

Menu source files $CARSPATH/menusrc/student/health $CARSPATH/menusrc/student/housing $CARSPATH/menusrc/student/incident $CARSPATH/menusrc/student/placement $CARSPATH/menusrc/student/stuserv

Menu option files $CARSPATH/menuopt/matric/others $CARSPATH/menuopt/matric/reports $CARSPATH/menuopt/matric/screens $CARSPATH/menuopt/placement/informers $CARSPATH/menuopt/placement/others $CARSPATH/menuopt/placement/reports $CARSPATH/menuopt/placement/screens $CARSPATH/menuopt/placement/scripts $CARSPATH/menuopt/stuserv/informers $CARSPATH/menuopt/stuserv/others $CARSPATH/menuopt/stuserv/reports $CARSPATH/menuopt/stuserv/scripts

PERFORM screens $CARSPATH/modules/matric/screens $CARSPATH/modules/placement/screens $CARSPATH/modules/stuserv/screens

SQL scripts $CARSPATH/modules/stuserv/informers

Csh scripts $CARSPATH/modules/common/scripts $CARSPATH/modules/stuserv/scripts

Menus, Screens, Scripts, and Reports 78 Student Affairs Technical Manual

ACE reports $CARSPATH/modules/matric/others $CARSPATH/modules/matric/reports $CARSPATH/modules/placement/others $CARSPATH/modules/placement/reports $CARSPATH/modules/stuserv/others $CARSPATH/modules/stuserv/reports

Letters $CARSPATH/modules/matric/others $CARSPATH/modules/matric/reports $CARSPATH/modules/placement/others $CARSPATH/modules/placement/reports $CARSPATH/modules/stuserv/others $CARSPATH/modules/stuserv/reports


Student Affairs Menus

Introduction

The CX menu source (menusrc) directory path contains definitions of the CX menu structure. Specifically, the $CARSPATH/menusrc/student directory path contains definitions for Student Affairs and Career Placement menus. The following directories corresponding to Student Affairs and Career Placement appear in this path:

• $CARSPATH/menusrc/student/health • $CARSPATH/menusrc/student/housing • $CARSPATH/menusrc/student/incident • $CARSPATH/menusrc/student/placement • $CARSPATH/menusrc/student/stuserv

Each directory above contains a menudesc file, which describes what menu options appear in a menu. Specific menu options, however, are defined in the menu option (menuopt) directory path.

Student Affairs Menu Flow Diagrams

The following diagrams illustrate how the Student Affairs menus and menu options appear on the standard product.

Student Management Menu Flow - Chart 1


Master Menu

StudentManagement:

Main Menu

Registrar MainMenu

StudentAdvising menu

Financial AidMain Menu

StudentServices Menu

Housing/Events Menu

HealthServices Menu

SeeRegistrationTechnicalManual

See DegreeAudit or

RegistrationTechnicalManuals

See FinancialAid Technical

Manual

See chart 3

See chart 4

See chart 5

Process

Terminator

Connector

Manualoperation

Stored data

Report/Output

Display

Manual input

Predefinedprocess

Personal/Campus

Incident MenuSee chart 6

StudentPlacement

MenuSee chart 7

Student Services Detail Diagram - Chart 3


StudentServices menu

Students byAdvisor

Counts andLists

Counts byClass Report

GPA Reports

Residence HallNo Shows

Student ProfileReport

Data Entry

VehicleRegistrations

StudentInvolvement

Report

UpdateStudentService

Chapel/Convocation

Menu

Add StudentServiceRecord

Data Entry -Form Menu

Reportparameters

Report

Reportparameters

Report

Reportparameters

Report

Reportparameters

Report

Reportparameters

Reportparameters

Reportparameters

Recordparameters

Recordparameters

See chart3a

Updates dataentry

parameters

Reportparameters

Report

Report

Report

Report

Adds StudentService

record(s)

UpdatesStudentService

record(s)

Data entryparameters


Chapel/Convocation Detail Diagram - Chart 3a


Chapel/Convocation

Menu

CheckAttendance

Records

MaintainAttendance

Record

AddAttendance/

Absence

AttendanceDetail Report

TotalAttendance

Report

AttendanceNot Required

Add InitialRecords

Missing InitialRecord

SelectAbsenceLetters

Print AbsenceLetters

MaintainMeeting Table

CreateAbsenceLetters

Recordparameters

Recordparameters

Recordparameters

Reportparameters

Report

Reportparameters

Reportparameters

Letterparameters

Letterparameters

Letterparameters

Adds Chapel/Convocation

records

Reportparameters

Report

Report

Report

CreatesAbsence

letters

LPS Process:Print Absence

Letters

Meeting TableReport

UpdatesAttendance

records

ChecksAttendance

records

AddsAttendance/

Absencerecords

Adds Contactrecords

Reportparameters

UpdatesChapel/

ConvocationTable

Tableparameters

Report

Recordparameters

Addressingparameters

Labelparameters


Housing/Events Detail Diagram - Chart 4


Housing/Events Menu

ResidenceReport

HousingPreference

Forms

Room/BoardAgreement

Form

Print HousingLetters

Counts andLists

Housing DataEntry

DisplayStudent Data

Counts byClass Report

AvailableHousingReport

Housing WaitList

GPA Reports

Off CampusHousingReport

Reportparameters

Letterparameters

Reportparameters

Reportparameters

Reportparameters

Reportparameters

Updates dataentry

parameters

Recordparameters

Report

Report

EventsScheduling

CreatesHousing

PreferenceLetters

Reportparameters

Data entryparameters

ScheduledEvents Report

DisplayStudent Data -

Form Menu

Adds/updatesdata entry

parameters

Report


Labelparameters

Letterparameters

Creates Room/Board

AgreementLetters


Labelparameters

File to bePrinted - LPS

Screen

LPS process:Prints housing

letters

Report

Report

Reportparameters

Report

Report

Recordparameters

Queries/adds/updates Event

record

Reportparameters

Report


Health Services Detail Diagram - Chart 5

HealthServices Menu

ImmunizationsReport

SpecialConditions

Report

MedicalHistory Report

Medical VisitsReport

TableMaintenance

Allergy Report

HealthServices Entry

HealthServices Form

Menu

Reportparameters

Report

Reportparameters

Report

Reportparameters

Report

Reportparameters

Report

Healthservices entry

parameters

Updates healthservices entry

parameters

Reportparameters

Report

Allergy Table

Allergy TableReport

ImmunizationTable

ImmunizationReport

MedicalHistory Table

MedicalHistory Report

SpecialConditions

Table

SpecialConditions

Report

Tableparameters

Queries/adds/updates table

entries

Reportparameters

Report

Tableparameters


entries

Tableparameters


entries

Tableparameters


entries

Reportparameters

Report

Reportparameters

Report

Reportparameters

Report

Personal/Campus Incident Detail Diagram - Chart 6


Personal/Campus

Incident Menu

CriimeStatisticsReport

Query/ResolveIncidents

Incident Table

Incident TableReport

Incident Report

MaintainIncidents

Reportparameters

Report

Queryparameters

Tableparameters

Reportparameters

Report

Incident entry

Queries/adds/updates StudentPersonal Incident

record(s)

Reportparameters

Report


entries

Queries/resolvesStudentPersonalIncidentrecord(s)

Student Placement Detail Diagram - Chart 7


StudentPlacement

Menu

Student/AlumPlacement

DisplayTranscripts

DisplayRegistrations

Print Courses byStudent

Query by Form

Communications Management (NOTE: See theCommumications Management Technical

Manual for information about this menu option.)

Seechart 7a

Reports Menu Seechart 7b

TableMaintenance

Seechart 7c

Programparameters

EmploymentPlacement

Options menu Placementparameters

Queries/adds/updates

placementparameters

Displayparameters

Transcript data

Displayparameters

Registrationdata

Reportparameters

Report

Query by Form Detail Diagram - Chart 7a


Query by FormMenu

BusinessInformation

BusinessPositions

Student CareerGoals

Student CareerSkills

InterviewerSchedule

IntervieweeSchedule

EmploymentInformation

Displays availablepositions andrequired skills

Displays careergoals, enrollment,

and profileinformation

Displays businessbackgroundinformation

Displays studentswith certain skills

Displays sign-upand interviewer

schedules

Displaysscheduled dates

and times ofinterviewees

Displays astudent's

employmenthistory

Reports Detail Diagram - Chart 7b


Reports Menu

InterviewCalendar

InterviewPositions

Career Skills

CompanyPositions

CompanyInformation

InterviewSchedule

Interviewee

CompanyStudent Match

StudentCompany

Match

AlumniDirectory

Students byMajor

Employers ofAlumni

Reportparameters

Reportparameters

Reportparameters

Reportparameters

Reportparameters

Reportparameters

Reportparameters

Report

Report

RecentGraduates

Reportparameters

Reportparameters

Students byAccomplish

Students byInvolvement

Report

Reportparameters

Report

Report

Reportparameters

Report

Report

Reportparameters

Reportparameters

Report

Reportparameters

Report

Report

Report

Report

Report

ReportReport

parameters

Report


Table Maintenance Detail Diagram - Chart 7c

TableMaintenance

Menu

Contact

Contact Report

Position TypeTable

Position Type

Career SkillsTable Report

Career SkillsTable

Tableparameters

Reportparameters

Report

Tableparameters

Reportparameters

Report

Tableparameters


entries

Reportparameters

Report


entries


entries

Student Affairs Menu Structure

The following menu source (menusrc) directories correspond to the Student Affairs menus on the CX menu system. Each directory and subdirectory that follows contains a menudesc file, which specifies what menu options appear in a menu. Specific menu options, however, are defined in the menu option (menuopt) directory path. For more information, see Menu Options in this section.

Student Management: Student Services Menu Menu source directory: $CARSPATH/menusrc/student/stuserv/ Subdirectory:

Student Services: Chapel/Convocation Menu Menu source directory: $CARSPATH/menusrc/student/stuserv/chapel/

Student Services: Housing/Events Menu Menu source directory: $CARSPATH/menusrc/student/housing/

Student Management: Health Services Menu Menu source directory: $CARSPATH/menusrc/student/health/ Subdirectory:

Health Services: Table Maintenance Menu Menu source directory: $CARSPATH/menusrc/matric/health/tables/

Student Management: Personal/Campus Incident Menu Menu source directory: $CARSPATH/menusrc/student/incident/


Student Management: Student Placement Menu Menu source directory: $CARSPATH/menusrc/student/placement/ Subdirectories:

Student Placement: Query by Form Menu Menu source directory: $CARSPATH/menusrc/student/placement/query

Student Placement: Communications Management Menu Menu source directory: $CARSPATH/menusrc/student/placement/commgmt

Note: For additional information about this menu, see the Communications Management Technical Manual.

Student Placement: Reports Menu Menu source directory: $CARSPATH/menusrc/student/placement/reports

Student Placement: Table Maintenance Menu Menu source directory: $CARSPATH/menusrc/student/placement/tables

Menu Options

The following list associates each Student Affairs program, screen, and script menu option and corresponding menuopt file and identifies the menuopt locations and what the menu option accesses:

Note: The following menus and options are listed in the order in which they appear on the standard CX menu structure. Italicized parameters indicate those that a user can enter or change.

Student Management: Student Services menu Note: This submenu is available if the macro ENABLE_FEAT_STUSERV is set to Y.

Data Entry Accesses: $CARSPATH/src/regist/stuentry (Program)

File: $CARSPATH/menuopt/regist/programs/stue

Parameters Passed: • -a (Pass parameter to automatically enter Query mode) • -F (Pass parameter to force query attempt before allowing Insert mode) • -L (Site code to be used) • -D (Debug_level 3)

Student Profile Report Accesses: $CARSPATH/modules/stuserv/reports/stusvprof (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/stusvprof

Parameters Passed: • Identification number • Program code


Students by Advisor Accesses: $CARSPATH/modules/stuserv/reports/stubyadv (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/stubyadv

Parameters Passed: • Session code • Calendar year • Program code • Subprogram code • Student academic status

Counts and Lists Accesses: $CARSPATH/modules/stuserv/others/countrpt (ACE report)

File: $CARSPATH/menuopt/stuserv/others/countrpt

Parameters Passed: • Primary sort column • Secondary sort column • Session code • Calendar year • Program code • Subprogram code • Student academic status • Identification number of advisor • Y/N (New page after each primary sort column?) • Y/N (Summary report?)

Counts by Class Report Accesses: $CARSPATH/modules/stuserv/others/classsort (ACE report)

File: $CARSPATH/menuopt/stuserv/others/classsort



GPA Reports Accesses: $CARSPATH/modules/stuserv/others/gpasort (ACE report)

File: $CARSPATH/menuopt/stuserv/others/gpasort

Parameters Passed: • Primary sort column • Secondary sort column • GPA column • Session code • Calendar year • Program code • Subprogram code • Student academic status • Identification number of advisor • C/P (Count or percent?) • Y/N (New page after each primary sort column?) • Y/N (Summary report?)

Residence Hall No Shows Accesses: $CARSPATH/modules/stuserv/reports/servacad (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/servacad

Parameters Passed: • Session code • Calendar year • Program code

Vehicle Registrations Accesses: $CARSPATH/modules/stuserv/reports/autos (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/autos

Parameters Passed: • Session code • Calendar year

Student Involvement Report Accesses: $CARSPATH/modules/stuserv/reports/involve (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/involve

Parameters Passed: • Session code • Calendar year • Program code • Involvement code


Add Student Service Record Accesses: $CARSPATH/modules/stuserv/informers/addstuserv (SQL script)

File: $CARSPATH/menuopt/stuserv/informers/addstuserv


Update Student Service Accesses: $CARSPATH/modules/stuserv/scripts/updstuserv (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/updstuserv

Parameters Passed: • Session to be copied • Year to be copied • Session to be updated • Year to be updated

Student Services: Chapel/Convocation menu Note: This submenu is available if the macro ENABLE_FEAT_CHAPEL is set to Y.

Add Initial Records Accesses: $CARSPATH/modules/stuserv/scripts/chapadinit (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/chapadinit

Parameters Passed: • Session code • Academic year • Program code • Subprogram code • Student academic status

Attendance Not Required Accesses: $CARSPATH/modules/stuserv/reports/chapnoadd (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/chapnoadd



Check Attendance Record Accesses: $CARSPATH/modules/stuserv/scripts/chapel (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/chapel

Parameters Passed: • Session • Academic year • Date

Maintain Attendance Record Accesses: $CARSPATH/modules/stuserv/screens/chap (PERFORM screen)

File: $CARSPATH/menuopt/stuserv/screens/chap

Parameters Passed: None

Add Attendance/Absence Accesses: $CARSPATH/modules/stuserv/scripts/chapadday (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/chapadday

Parameters Passed: • Session code • Calendar year • Date • Y/N (Y=Attendance records;N=Absence records)

Attendance Detail Report Accesses: $CARSPATH/modules/stuserv/reports/chapdtl (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/chapdtl

Parameters Passed: • Session code • Calendar year • Date of last chapel/convocation to be considered • Number of absences to be considered • Y/N (Print attendance record comments?) • Y/N (Include fully exempted students in totals?)

Total Attendance Report Accesses: $CARSPATH/modules/stuserv/reports/chaptot (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/chaptot

Parameters Passed: • Session code • Calendar year • Date to determine last meeting to be tabulated • Y/N (Include fully exempted students in totals?)


Missing Initial Record Accesses: $CARSPATH/modules/stuserv/reports/chapmiss (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/chapmiss


Select Absence Letters Accesses: $CARSPATH/modules/stuserv/scripts/chapadctc (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/chapadctc

Parameters Passed: • Session code • Calendar year • Date of last chapel/convocation to be considered • Minimum number of absences required to add contact

Create Absence Letters Accesses: $CARSPATH/modules/common/scripts/ltbrun (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/ltrchapel

Parameters Passed: • Contact resource code • Date to be printed and expanded on the letters • Select date • Session code • Calendar year • Program code • Date of last chapel/convocation to be considered

Print Absence Letters Accesses: $CARSPATH/src/util/lps (Utility)

File: $CARSPATH/menuopt/utilities/programs/lps.chapel

Parameters Passed: • Standard Letter Production System

Maintain Meeting Table Accesses: $CARSPATH/modules/stuserv/screens/tchap (PERFORM screen)

File: $CARSPATH/menuopt/stuserv/screens/tchap


Meeting Table Report Accesses: $CARSPATH/modules/stuserv/reports/tchap (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/tchap



Student Services: Housing/Events menu

Display Student Data Accesses: $CARSPATH/src/regist/stuentry (Program)

File: $CARSPATH/menuopt/regist/programs/stue.d

Parameters Passed: • -a (Pass parameter to automatically enter Query mode. Passed if the macro

ENABLE_FEAT_AUTOMODE is set to Y) • -F (Pass parameter to force query attempt before allowing Insert mode. Passed if

the macro ENABLE_FEAT_FORCEQUERY is set to Y.) • -d (Pass parameter to limit to display only) • -L (Site code to be used) • -D (Debug_level 3)

Housing Data Entry Accesses: $CARSPATH/src/regist/stuentry (Program)

File: $CARSPATH/menuopt/regist/programs/stusrv

Parameters Passed: • -f (Name of desired form instead of using a menu)

Residence Report Accesses: $CARSPATH/modules/stuserv/reports/housing (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/housing


Housing Preference Forms Accesses: $CARSPATH/modules/common/scripts/ltbrun (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/ltrhsgfrm

Parameters Passed: • Date to be printed on the form • Session code • Calendar year • Y/N (Use bulk mail processing?)

Room/Board Agreement Form Accesses: $CARSPATH/modules/common/scripts/ltbrun (Csh script)

File: $CARSPATH/menuopt/stuserv/scripts/ltrrmbrd

Parameters Passed: • Date to be printed on the form


• Session code • Calendar year • Y/N (Bulk mail processing?)


Print Housing Letters Accesses: $CARSPATH/src/util/lps (Utility)

File: $CARSPATH/menuopt/utilities/programs/lps.hsg

Parameters Passed: • Standard Letter Production System

Counts and Lists Accesses: $CARSPATH/modules/stuserv/others/countrpt (ACE report)

File: $CARSPATH/menuopt/stuserv/others/countrpt


Counts by Class Report Accesses: $CARSPATH/modules/stuserv/others/classsort (ACE report)

File: $CARSPATH/menuopt/stuserv/others/classsort


Available Housing Report Accesses: $CARSPATH/modules/stuserv/reports/roomlist (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/roomlist



Off Campus Housing Report Accesses: $CARSPATH/modules/stuserv/reports/offcampus (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/offcampus


Housing Wait List Accesses: $CARSPATH/modules/stuserv/reports/waitlist (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/waitlist


GPA Reports Accesses: $CARSPATH/modules/stuserv/others/gpasort (ACE report)

File: $CARSPATH/menuopt/stuserv/others/gpasort

Parameters Passed: • Primary sort column • Secondary sort column • GPA column • Session code • Calendar year • Program code • Subprogram code • Student academic status • Identification number of advisor • C/P (Count or percent?) • Y/N (New page after each primary sort column?) • Y/N (Summary version?)

Events Scheduling Note: This menu option is available if the macro ENABLE_FEAT_EVENTS is set to

Y.

Accesses: $CARSPATH/src/common/eventry (Program)

File: $CARSPATH/menuopt/common/programs/eventry


ENABLE_FEAT_AUTOMODE is set to Y.) • -F (Pass parameter to force query attempt before allowing Insert mode. Passed if

the macro ENABLE_FEAT_FORCEQUERY is set to Y.) • -D (Debug_level 3) • -f (Name of desired form instead of using a menu)


Scheduled Events Report Note: This menu option is available if the macro ENABLE_FEAT_EVENTS is set to

Y.

Accesses: $CARSPATH/modules/common/others/eventrpt (ACE report)

File: $CARSPATH/menuopt/common/others/eventrpt

Parameters Passed: • Beginning date • Ending date • Sort column

Student Management: Health Services menu

Health Services Entry Accesses: $CARSPATH/src/matric/hentry (Program)

File: $CARSPATH/menuopt/matric/programs/hse



the macro ENABLE_FEAT_FORCEQUERY is set to Y.) • -D (Debug_level 3)

Allergy Report Accesses: $CARSPATH/modules/matric/others/allergy (ACE report)

File: $CARSPATH/menuopt/matric/others/allergy

Parameters Passed: • Identification number • Allergy code • Sort column

Immunizations Report Accesses: $CARSPATH/modules/matric/others/immune (ACE report)

File: $CARSPATH/menuopt/matric/others/immune

Parameters Passed: • Identification number • Immunization code • Sort column

Special Conditions Report Accesses: $CARSPATH/modules/matric/others/speccond (ACE report)

File: $CARSPATH/menuopt/matric/others/speccond

Parameters Passed: • Identification number


• Special condition code • Sort column


Medical History Report Accesses: $CARSPATH/modules/matric/others/mhpast (ACE report)

File: $CARSPATH/menuopt/matric/others/mhpast

Parameters Passed: • Identification number • Visit code • Y/N (Include other information?) • Beginning date for selecting visits • Ending date for selecting visits • Sort column • Y/N (Subtotal count after each sort break?)

Medical Visits Report Accesses: $CARSPATH/modules/matric/others/mhfuture(ACE report)

File: $CARSPATH/menuopt/matric/others/mhfuture

Parameters Passed: • Identification number • Visit code • Beginning date for scheduled visits • Ending date for scheduled visits • Sort column • Y/N (Subtotal count after each sort break?)

Health Services: Table Maintenance Menu

Allergy Table Accesses: $CARSPATH/modules/matric/screens/tallergy (PERFORM screen)

File: $CARSPATH/menuopt/matric/screens/tallergy


Allergy Table Report Accesses: $CARSPATH/modules/matric/reports/tallergy (ACE report)

File: $CARSPATH/menuopt/matric/reports/tallergy


Immunization Table Accesses: $CARSPATH/modules/matric/screens/timmune (PERFORM screen)

File: $CARSPATH/menuopt/matric/screens/timmune


Immunization Report Accesses: $CARSPATH/modules/matric/reports/timmune (ACE report)

File: $CARSPATH/menuopt/matric/reports/timmune



Medical History Table Accesses: $CARSPATH/modules/matric/screens/tmedhist (PERFORM screen)

File: $CARSPATH/menuopt/matric/screens/tmedhist


Medical History Report Accesses: $CARSPATH/modules/matric/reports/tmedhist (ACE report)

File: $CARSPATH/menuopt/matric/reports/tmedhist


Special Conditions Table Accesses: $CARSPATH/modules/matric/screens/tspeccond (PERFORM screen)

File: $CARSPATH/menuopt/matric/screens/tspeccond


Special Conditions Report Accesses: $CARSPATH/modules/matric/reports/tspeccond (ACE report)

File: $CARSPATH/menuopt/matric/reports/tspeccond


Student Management: Personal/Campus Incident menu Note: This submenu is available if the macro ENABLE_FEAT_INCIDENT is set to Y.

Maintain Incidents Accesses: $CARSPATH/src/stuserv/incdentry (Program)

File: $CARSPATH/menuopt/stuserv/programs/incdentry



the macro ENABLE_FEAT_FORCEQUERY is set to Y.) • -D (Debug_level 3) • -f (Name of desired form instead of using a menu)

Incident Report Accesses: $CARSPATH/modules/stuserv/reports/stupers (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/stupers

Parameters Passed: • Identification number of student • Session code • Calendar year


• Incident code • Incident status


Crime Statistics Report Accesses: $CARSPATH/modules/stuserv/reports/crimestats (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/crimestats

Parameters Passed: • Calendar year

Query/Resolve Incidents Accesses: $CARSPATH/modules/stuserv/screens/stupers (PERFORM screen)

File: $CARSPATH/menuopt/stuserv/screens/stupers


Incident Table Accesses: $CARSPATH/modules/stuserv/screens/tstupers (PERFORM screen)

File: $CARSPATH/menuopt/stuserv/screens/tstupers


Incident Table Report Accesses: $CARSPATH/modules/stuserv/reports/tstupers (ACE report)

File: $CARSPATH/menuopt/stuserv/reports/tstupers


Student Management: Student Placement Menu Note: This submenu is available if the macro ENABLE_MOD_STU_PLACEMENT is set to

Y.

Student/Alum Placement Accesses: $CARSPATH/src/placement/placement (Program)

File: $CARSPATH/menuopt/placement/programs/placement

Parameters Passed: • -p program (Program code) • -L (Site code) • -t (Tick code)

Display Transcripts Accesses: $CARSPATH/src/regist/trans (Program)

File: $CARSPATH/menuopt/regist/programs/trns.d

Parameters Passed: • -d (Display-only mode) • -f (Transcript form code) • -L (Site value)


Display Registrations Accesses: $CARSPATH/src/regist/regent (Program)

File: $CARSPATH/menuopt/regist/programs/regent.d

Parameters Passed: • -p program (Student program) • -L (Site code) • -F (Registration finish functionality) • -m (Main menu options to be disabled) • -e (Enrollment menu options to be disabled) • -r (Registration menu options to be disabled) • -d (Display-only mode)

Print Courses by Student Accesses: $CARSPATH/modules/regist/reports/stucrs (ACE report)

File: $CARSPATH/menuopt/regist/reports/stucrs

Parameters Passed: • Identification number of student • Program code • Y/N (Print dropped and withdrawn classes?)

Student Placement: Query by Form Menu

Business Information Accesses: $CARSPATH/modules/placement/screens/business (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/business


Business Positions Accesses: $CARSPATH/modules/placement/screens/careerpos (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/careerpos


Student Career Goals Accesses: $CARSPATH/modules/placement/screens/career (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/career


Student Career Skills Accesses: $CARSPATH/modules/placement/screens/skills (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/skills



Interviewer Schedule Accesses: $CARSPATH/modules/placement/screens/intvwer (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/intvwer


Interviewee Schedule Accesses: $CARSPATH/modules/placement/screens/intvwee (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/intvwee


Employment Information Accesses: $CARSPATH/modules/placement/screens/employ (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/employ


Student Placement: Communications Management Menu Note: For additional information about this feature, see the Communications Management

Technical Manual.

Student Placement: Reports Menu

Interviewee Accesses: $CARSPATH/modules/placement/reports/intvwee (ACE report)

File: $CARSPATH/menuopt/placement/reports/intvwee

Parameters Passed: • Starting date • Ending date • Identification number of interviewee

Interview Schedule Accesses: $CARSPATH/modules/placement/reports/intvwer (ACE report)

File: $CARSPATH/menuopt/placement/reports/intvwer

Parameters Passed: • Starting date • Ending date • Identification number of interviewer

Interview Calendar Accesses: $CARSPATH/modules/placement/reports/intvwcal (ACE report)

File: $CARSPATH/menuopt/placement/reports/intvwcal

Parameters Passed: • Starting date


• Ending date

Interview Positions Accesses: $CARSPATH/modules/placement/others/intvwrpt (ACE report)

File: $CARSPATH/menuopt/placement/others/intvwrpt

Parameters Passed: • Beginning date • Sort column

Career Skills Accesses: $CARSPATH/modules/placement/others/careerrpt (ACE report)

File: $CARSPATH/menuopt/placement/others/careerrpt

Parameters Passed: • Beginning available date • Ending available date • Sort column

Company Positions Accesses: $CARSPATH/modules/placement/reports/posbus (ACE report)

File: $CARSPATH/menuopt/placement/reports/posbus

Parameters Passed: • Beginning date for available positions

Company Information Accesses: $CARSPATH/modules/placement/others/busrpt (ACE report)

File: $CARSPATH/menuopt/placement/others/busrpt

Parameters Passed: • Sort column

Company Student Match Accesses: $CARSPATH/modules/placement/reports/compstu (ACE report)

File: $CARSPATH/menuopt/placement/reports/compstu

Parameters Passed: • Identification number of company • Beginning date for available positions

Student Company Match Accesses: $CARSPATH/modules/placement/reports/stucomp (ACE report)

File: $CARSPATH/menuopt/placement/reports/stucomp

Parameters Passed: • Identification number of student • Beginning date for available positons


Employers of Alumni Accesses: $CARSPATH/modules/placement/reports/alumempr(ACE report)

File: $CARSPATH/menuopt/placement/reports/alumempr

Parameters Passed: • Y/N (Summary report?)

Alumni Directory Accesses: $CARSPATH/modules/placement/reports/alumdir (ACE report)

File: $CARSPATH/menuopt/placement/reports/alumdir

Parameters Passed: • Beginning year • Ending year

Students by Major Accesses: $CARSPATH/modules/placement/reports/stumajor (ACE report)

File: $CARSPATH/menuopt/placement/reports/stumajor


Recent Graduates Accesses: $CARSPATH/modules/placement/reports/gradalum (ACE report)

File: $CARSPATH/menuopt/placement/reports/gradalum

Parameters Passed: • Graduation session • Graduation year • Program code • Subprogram code

Students by Accomplish Accesses: $CARSPATH/modules/placement/reports/stuaccomp (ACE report)

File: $CARSPATH/menuopt/placement/reports/stuaccomp

Parameters Passed: • Accomplishment code • Accomplishment session • Accomplishment year


Students by Involvement Accesses: $CARSPATH/modules/placement/reports/stuinvl (ACE report)

File: $CARSPATH/menuopt/placement/reports/stuinvl

Parameters Passed: • Involvement code • Date

Student Placement: Table Maintenance Menu

Career Skills Table Accesses: $CARSPATH/modules/placement/screens/tcrskl (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/tcrskl


Career Skills Table Report Accesses: $CARSPATH/modules/placement/reports/tcrskl (ACE report)

File: $CARSPATH/menuopt/placement/reports/tcrskl


Contact Accesses: $CARSPATH/modules/common/screens/tctc (PERFORM screen)

File: $CARSPATH/menuopt/common/screens/tctc


Contact Report Accesses: $CARSPATH/modules/common/reports/tctc (ACE report)

File: $CARSPATH/menuopt/common/reports/tctc

Parameters Passed: • Beginning tickler code • Ending tickler code

Position Type Table Accesses: $CARSPATH/modules/placement/screens/tptype (PERFORM screen)

File: $CARSPATH/menuopt/placement/screens/tptype


Position Type Accesses: $CARSPATH/modules/placement/reports/tptype (ACE report)

File: $CARSPATH/menuopt/placement/reports/tptype



PERFORM (Table Maintenance) Screens

Introduction

Student Affairs and Career Placement use PERFORM screens for displaying maintenance tables and some records. You can access the screen files in the following directory paths:

• $CARSPATH/modules/matric/screens • $CARSPATH/modules/placement/screens • $CARSPATH/modules/stuserv/screens

PERFORM screens

The following lists the PERFORM screens used in Student Affairs and Career Placement:

Note: In the following list, descriptions of PERFORM screens include: − Screen title − Purpose of the screen − Tables used in the screen − Master/detail relationships, if applicable

Allergy Table Enables you to view, add, and update allergy codes.

Menu Access: Health Services: Table Maintenance menu. Allergy Table option.

File: tallergy

Note: This is a maintenance table.

Tables/Records Used:None

Business Record Enables you to display the positions available with a business and the skills required of each position.

Menu Access: Student Placement: Query by Form menu. Business Information option

File: business

Tables/Records Used: • bus_rec • career_pos_rec • cr_skl_table • ctry_table • id_rec • pos_skl_rec • pos_type_table • st_table • title_table


Career Skills Table Enables you to maintain the data associated with a code and the description of the skills that an individual possesses.

Menu Access: Student Placement: Table Maintenance menu. Career Skills Table option.

File: tcrskl



Chapel/Convocation Attendance Record Enables you to view, add, or update records of students’ attendance and absence from chapel or convocation events.

Menu Access: Student Services: Chapel/Convocation Menu: Maintain Attendance Record option

File: chap

Tables/Records Used: • chap_rec • chap_table • id_rec • sess_table • st_table • title_table

Chapel/Convocation Event Table Enables you to view, add, or update information for chapel/convocation events in the Chapel/Convocation Event table

Menu Access: Student Services: Chapel/Convocation menu. Maintain Meeting Table option.

File: tchap

Tables/Records Used: • chap_table • sess_table

Contact Table Note: For information about this common screen, see the CX System Reference Technical

Manual.


Employment Record Enables you to display positions held by students or alumni and the business who employs them.

Menu Access: Student Placement: Query by Form menu. Employment Information option.

File: employ

Tables/Records Used: • emp_rec • ctry_table • id_rec • st_table • title_table) • occ_table

Immunization Table Enables you to view, add, and update immunization codes.

Menu Access: Health Services: Table Maintenance menu. Immunization Table option.

File: timmune



Interviewer Schedule (Interviewee Schedule) Enables you to query for dates and times of student interview schedules.

Menu Access: Student Placement: Query by Form menu. Interviewee Schedule option.

File: intvwee

Tables/Records Used: • id_rec • intvwee_rec • intvwer_rec • career_pos_rec

Interviewer Schedule (Interviewer Schedule) Enables you to query for dates and times of interview sign-up schedules and interview schedules.

Menu Access: Student Placement: Query by Form menu. Interviewer Schedule option.

File: intvwer

Tables/Records Used: • id_rec • intvwer_rec • career_pos_rec

Medical History Table Enables you to view, add, and update medical history codes.

Menu Access: Health Services: Table Maintenance menu. Medical History Table option.

File: tmedhist




Personal Incident Table Enables you to view, add, and update incident codes.

Menu Access: Student Management: Personal/Campus Incident menu. Incident Table option.

File: tstupers



Personal/Campus Incident Record Enables you to view, add, or update records of personal and campus incidents as required by Public Law 101-542, the Criminal Awareness Act.

Menu Access: Student Management: Personal/Campus Incident menu. Query/Resolve Incidents option.

File: stupers

Tables/Records Used: • id_rec • st_table • stupers_rec • stupers_table • title_table

Position Identification Enables you to query on business positions and the skills required for each postion.

Menu Access: Student Placement: Query by Form menu. Business Positions option.

File: careerpos

Tables/Records Used: • career_pos_rec • cr_skl_table • deg_table • id_rec • major_table • pos_skl_rec • pos_type_table

Position Type Table Enables you to maintain the data associated with a code and the description of the position that is available in a business industry.

Menu Access: Student Placement: Table Maintenance menu. Position Type Table option.

File: tptype




Special Conditions Table Enables you to view, add, and update special medical condition codes.

Menu Access: Health Services: Table Maintenance menu. Special Conditions Table option.

File: tspeccond



Student Identification (Student Career Goals) Enables you to query on student career goals, student enrollment information, and profile information.

Menu Access: Student Placement: Query by Form menu. Student Career Goals option.

File: career

Tables/Records Used: • career_rec • cl_table • conc_table • ctry_table • deg_table • ethnic_table • id_rec • major_table • minor_table • pos_type_table • profile_rec • prog_enr_rec • prog_table • st_table • title_table

Student Identification (Student Career Skills) Enables you to query for students with certain skills.

Menu Access: Student Placement: Query by Form menu. Student Career Skills option.

File: skills

Tables/Records Used: • career_skl_rec • cl_table • conc_table • cr_skl_table • ctry_table • deg_table • ethnic_table • id_rec • major_table • minor_table • profile_rec • prog_enr_rec • prog_table


• st_table • title_table


SQL Scripts

Introduction

The Student Affairs and Career Placement products contain SQL scripts that perform queries and produce reports from database records. The scripts are located in the following directory paths:

• $CARSPATH/modules/stuserv/informers

Note: Csh scripts can call ACE reports and SQL scripts. Such ACE reports and SQL scripts do not reside on the CX menu system.

SQL Scripts

The following lists the SQL scripts provided with Student Affairs and Career Placement:

addstuserv Initiates a process that adds a Student Services record for each student who has a Student Academic record for the session specified and does not have a Student Services recordfor the same session.

CAUTION: The script creates Student Services records from Student Academic records when you initially set up Student Affairs. If you use this script after implementation, use caution and be sure that the Student Affairs office knows that the records must be updated and verified.

Menu Access: Student Management: Student Services menu. Add Student Service Record option.

Tables/Records Used: • acad_cal_rec • stu_acad_rec • stu_serv_rec


Csh Scripts

Introduction

The Student Affairs and Career Placement products contain Csh scripts to automate the processing of information. Csh scripts are UNIX-based program statements that can execute a series of SQL scripts or reports. The Student Affairs Csh scripts are located in the following directory paths:

• $CARSPATH/modules/common/scripts • $CARSPATH/modules/stuserv/scripts

Csh Scripts

The following list associates a Student Affairs menu option with the corresponding Csh script and provides a description of the script:

Note: In the following list, descriptions of Csh scripts include: − Purpose of the script − Menu access option, if applicable − A list of ACE reports used, if applicable − A list of SQL statements used, if applicable − A list of tables used, if applicable

chapadctc Creates Contact records for students who have absences from chapel/convocation for the specified session and year.

Menu Access: Student Services: Chapel/Convocation menu. Select Absence Letters menu option.

Reports: A report that creates output from Contact records added successfully.

chapadday Adds attendance or absence information to the database by adding an Attendance or Absence record for each student in the specified session and year.

Menu Access: Student Services: Chapel/Convocation menu. Add Attendance/Absence menu option.

Reports: A report that creates output from Attendance or Absence records added successfully.

chapadinit Adds attendance requirement information to students’ records by adding Chapel/Convocation records for all full-time, registered students. Allows you to determine which students are required to attend chapel/convocation events and which students are exempt.

Note: You should run this script at the beginning of a session.

Menu Access: Student Services: Chapel/Convocation menu. Add Initial Records menu option.

Reports: A report that creates output from initial Chapel/Convocation records added successfully.


chapel Verifies that the date for the chapel and/or convocation exists in the Meeting table. You can also use the Check Attendance Records process to add individual Chapel/Convocation records.

Note: Use this Csh script before using the chapadday script or the Chapel/Convocation Attendance Record PERFORM screen.

Menu Access: Student Services: Chapel/Convocation menu. Check Attendance Records menu option.

Reports: A report that verifies the date entered by the user.

SQL Scripts: • An SQL script that verifies and prints the student’s name entered by the user. • An SQL script that calculates and prints absences. • An SQL script that adds Chapel/Convocation records (chap_rec).

Tables/Records Used: • chap_rec • chap_table • id_rec • stu_acad_rec

ltbrun Creates letters and/or labels in an LPS output file or creates a requested word processor merge file along with possible labels.

Menu Access: Student Services: Chapel/Convocation menu. Create Absence Letters menu option.

Reports: A report that reports the next action if debug is on.

ltbrun Creates forms and/or labels in an LPS output file or creates a requested word processor merge file along with possible labels.

Menu Access: Student Services: Housing/Events menu. Housing Preference Forms menu option.


ltbrun Creates forms and/or labels in an LPS output file or creates a requested word processor merge file along with possible labels.

Menu Access: Student Services: Housing/Events menu. Room/Board Agreement Form menu option.


updstuserv Updates new Student Services records with old Student Services records for the specified session and year using the ACE to SQL capability.

Menu Access: Student Management: Student Services menu. Update Student Service menu option.


ACE Reports

Introduction

CX contains ACE reports for easy reporting of Student Affairs and Career Placement database information. The ACE reports are grouped in the following categories:

• Student Services • Chapel/Convocation • Housing/Events • Health Services • Health Services Table Maintenance • Personal/Campus Incident • Student Placement • Student Placement Reports • Student Placement Table Maintenance

Student Services ACE Reports

The following lists the reports accessed from the Student Management: Student Services menu.

‘No Show’ Students Assigned Housing Provides a list of students with an academic registration status of No Show for the specified session and year.

Menu Access: Student Services menu: Residence Hall No Shows option

File: $CARSPATH/modules/stuserv/reports/servacad

Parameters for Student Services Count Report Provides a list of student counts sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Student Services menu: Counts and Lists option

File: $CARSPATH/modules/stuserv/others/countrpt

Parameters for Student Services Cumulative GPA Report Provides a list of students’ GPAs sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Student Services menu: GPA Reports option

File: $CARSPATH/modules/stuserv/others/gpasort

Parameters for Student Services Report by Classification Provides a list of student counts by classification and sex and sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Student Services menu: Counts by Class Report option

File: $CARSPATH/modules/stuserv/others/classsort

Student Involvement Report Provides a list of students (who are registered for a specified session, year, and program) with a specified involvement.

Menu Access: Student Services menu: Student Involvement Report option

File: $CARSPATH/modules/stuserv/reports/involve


Student Profile Report Provides the activity and academic information that a student has accumulated in their Student Services and Student Academic records.

Note: This report is meant to assist with non-academic counseling.

Menu Access: Student Services menu: Student Profile Report option

File: $CARSPATH/modules/stuserv/reports/stusvprof

Student Vehicle Report Provides a list a students with registered vehicles for the specified session and year.

Menu Access: Student Services menu: Vehicle Registrations option

File: $CARSPATH/modules/stuserv/reports/autos

Students by Advisor Provides a list of students by advisor for a specified program, session, and year.

Menu Access: Student Services menu: Students by Advisor option

File: $CARSPATH/modules/stuserv/reports/stubyadv

Chapel/Convocation ACE Reports

The following lists the reports accessed from the Student Services: Chapel/Convocation menu.

Chapel/Convocation Table Report Provides a list of chapel/convocation meeting numbers and the date of the meetings for the specified session and year.

Menu Access: Chapel/Convocation menu: Meeting Table Report option

File: $CARSPATH/modules/stuserv/reports/tchap

Chapel Absence Report Provides a list of students with equal to or greater than specified absences from chapel/convocation.

Menu Access: Chapel/Convocation menu: Attendance Detail Report option

File: $CARSPATH/modules/stuserv/reports/chapdtl

Chapel Total Report Provides a list of students and their total attendance of chapel/convocation events for the specified session and year.

Menu Access: Chapel/Convocation menu: Total Attendance Report option

File: $CARSPATH/modules/stuserv/reports/chaptot

Missing Initial Chapel Records Report Provides a list of students who have attendance or absence records, but do not have an initial Chapel/Convocation record for the specified session.

Menu Access: Chapel/Convocation menu: Missing Initial Record option

File: $CARSPATH/modules/stuserv/reports/chapmiss

Students Not Receiving Chapel/Convocation Records Provides a list of students who are not required to attend chapel/convocation.

Menu Access: Chapel/Convocation menu: Attendance Not Required option

File: $CARSPATH/modules/stuserv/reports/chapnoadd


Housing/Events ACE Reports

The following lists the reports accessed from the Student Services: Housing/Events menu.

Available Student Housing Report Provides a list of rooms with vacancies for the specified session and year.

Note: The report makes a side note for each room that has more occupants than specified in the Facility table.

Menu Access: Housing/Events menu: Available Housing Report option

File: $CARSPATH/modules/stuserv/reports/roomlist

Events Sorted by Provides information on all events scheduled within the specified date range. You must choose a column (e.g., evnt for Event) from the Event table in which to sort the report.

Menu Access: Housing/Events menu: Scheduled Events Report option

File: $CARSPATH/modules/common/others/eventrpt

Parameters for Student Services Count Report Provides a list of student counts sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Housing/Events menu: Counts and Lists option

File: $CARSPATH/modules/stuserv/others/countrpt

Parameters for Student Services Cumulative GPA Report Provides a list of students’ GPAs sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Housing/Events menu: GPA Reports option

File: $CARSPATH/modules/stuserv/others/gpasort

Parameters for Student Services Report by Classification Provides a list of student counts by classification and sex and sorted in specified primary and/or secondary column(s) from students’ ID, Profile, and/or Student Services records.

Menu Access: Housing/Events menu: Counts by Class Report option

File: $CARSPATH/modules/stuserv/others/classsort

Student Residence Report Provides a list of students by assigned resident hall. The report also provides students’ meal plan information.

Menu Access: Housing/Events menu: Residence Report option

File: $CARSPATH/modules/stuserv/reports/housing

Students Living Off Campus Provides a list of students who have been approved to live off-campus for the specified session and year.

Menu Access: Housing/Events menu: Off Campus Housing Report option

File: $CARSPATH/modules/stuserv/reports/offcampus


Waiting List for Student Housing Provides a list of students (for the specified session and year) who have a housing status of Reserved or Wait, have an intended housing status of Resident, and have no assigned residence hall.

Menu Access: Housing/Events menu: Housing Wait List option

File: $CARSPATH/modules/stuserv/reports/waitlist

Health Services ACE Reports

The following lists the reports accessed from the Student Management: Health Services menu.

Allergy Report Provides allergy information for a specified student or for all students with Allergy records.

Menu Access: Health Services menu: Allergy Report option

File: $CARSPATH/modules/matric/others/allergy

Immunization Report Provides immunization information for a specified student or for all students with Immunization records.

Menu Access: Health Services menu: Immunizations Report option

File: $CARSPATH/modules/matric/others/immune

Medical Revisit Report Provides a list of all documented medical revisit information about the specified student or all students.

Menu Access: Health Services menu: Medical Visits Report option

File: $CARSPATH/modules/matric/others/mhfuture

Past Medical History Report Provides a list of all documented medical history information about the specified student or all students.

Menu Access: Health Services menu: Medical History Report option

File: $CARSPATH/modules/matric/others/mhpast

Special Conditions Report Provides special health condition information for a specified student or for all students with special conditions.

Menu Access: Health Services menu: Special Conditions Report option

File: $CARSPATH/modules/matric/others/speccond

Health Services Table Maintenance ACE Reports

The following lists the reports accessed from the Health Services: Table Maintenance menu.

Allergy Table Report Provides a list of entries in the Allergy table.

Menu Access: Table Maintenance menu: Allergy Table Report option

File: $CARSPATH/modules/matric/reports/tallergy


Immunization Table Report Provides a list of entries in the Immunization table.

Menu Access: Table Maintenance menu: Immunization Report option

File: $CARSPATH/modules/matric/reports/timmune

Health Services Special Conditions Table Report Provides a list of entries in the health services visit code table.

Menu Access: Table Maintenance menu: Special Conditions Report option

File: $CARSPATH/modules/matric/reports/tspeccond

Medical History Table Report Provides a list of entries in the Medical History table.

Menu Access: Table Maintenance menu: Medical History Report option

File: $CARSPATH/modules/matric/reports/tmedhist

Personal/Campus Incident ACE Reports

The following lists the reports accessed from the Student Management: Personal/Campus Incident menu.

Crime Statistics Report Provides a list of totals of all crimes recorded on campus for a specified year. The report can be used to report campus crime statistics as reported by law.

Menu Access: Personal/Campus Incident menu: Crime Statistics Report option

File: $CARSPATH/modules/stuserv/reports/crimestats

Incident Report Provides a list of recorded incidents for a specified student, or all recorded incidents for all students.

Menu Access: Personal/Campus Incident menu: Incident Report option

File: $CARSPATH/modules/stuserv/reports/stupers

Personal Incident Table Report Provides a list of entries in the Personal Incident table.

Menu Access: Personal/Campus Incident menu: Incident Table Report option

File: $CARSPATH/modules/stuserv/reports/tstupers

Student Placement ACE Reports

The following lists the reports accessed from the Student Management: Student Placement menu.

Student Course Report Provides a list of courses taken by a specified student over the course of their higher education experience. The report displays the current status of the course and other notes about the course.

Menu Access: Student Placement menu: Print Courses by Student option

File: $CARSPATH/modules/regist/reports/stucrs


Student Placement ACE Reports (Reports Menu)

The following lists the reports accessed from the Student Placement: Reports menu.

Accomplishment Roster Provides the name and address of students with a specified accomplishment in a specified session and year. The report is sorted by state, city, and name.

Menu Access: Reports Menu: Students by Accomplish option

File: $CARSPATH/modules/placement/reports/stuaccomp

Alumni by Employer Provides a list of alumni employed by companies.

Menu Access: Reports Menu: Employers of Alumni option

File: $CARSPATH/modules/placement/reports/alumempr

Alumni Directory Provides a list of all alumni by class year.

Menu Access: Reports menu: Alumni Directory option

File: $CARSPATH/modules/placement/reports/alumdir

Company Information Report Provides a list of businesses sorted by a user-selected sort field.

Menu Access: Reports Menu: Company Information option

File: $CARSPATH/modules/placement/others/busrpt

Company Positions Available Provides a list of available positions within a business sorted by businesses.

Menu Access: Reports Menu: Company Positions option

File: $CARSPATH/modules/placement/reports/posbus

Company Student Career Match Report Provides a report matching student career goals with company needs.

Menu Access: Reports Menu: Company Student Match option

File: $CARSPATH/modules/placement/reports/compstu

Interview Calendar Provides a calendar by date of interview.

Menu Access: Reports Menu: Interview Calendar option

File: $CARSPATH/modules/placement/reports/intvwcal

Interview Report Provides a list of positions with their interview dates sorted by a user specified sort field.

Menu Access: Reports Menu: Interview Positions option

File: $CARSPATH/modules/placement/others/intvwrpt

Interview Schedule Provides schedule(s) of interviewer(s) by interviewer(s) and date range(s).

Menu Access: Reports Menu: Interview Schedule option

File: $CARSPATH/modules/placement/reports/intvwer


Interviewee Schedule Provides a list of interviewees (selected by date) and their scheduled interviews and interviewers.

Menu Access: Reports Menu: Interviewee option

File: $CARSPATH/modules/placement/reports/intvwee

Involvement Roster Provides a list of students or alumni with a specific involvement that will aid in finding qualified students/alumni for certain positions.

Menu Access: Reports Menu: Students by Involvement option

File: $CARSPATH/modules/placement/reports/stuinvl

Recent Graduates Eligible for Alumni File Provides a list of recent graduates who are eligible to have Alumni records created for them.

Menu Access: Reports Menu: Recent Graduates option

File: $CARSPATH/modules/placement/reports/gradalum

Student Career Goals and Skills Report Provides career skills for each student sorted by a user-selected sort field.

Menu Access: Reports Menu: Career Skills option

File: $CARSPATH/modules/placement/others/careerrpt

Student Company Career Match Report Provides a report matching company positions to students with the same career goal as the available positions.

Menu Access: Reports Menu: Student Company Match option

File: $CARSPATH/modules/placement/reports/stucomp

Student Roster by Major Provides a roster of students sorted by their majors.

Menu Access: Reports Menu: Students by Major option

File: $CARSPATH/modules/placement/reports/stumajor

Student Placement Table Maintenance ACE Reports

The following lists the reports accessed from the Student Placement: Table Maintenance menu.

Career Skill Codes Table Provides a list of entries in the Career Skills table.

Menu Access: Table Maintenance menu: Career Skills Table Report option

File: $CARSPATH/modules/placement/reports/tcrskl

Contact Table Report Provides a list of contacts either for a specific tickler or for all ticklers.

Menu Access: Table Maintenance menu: Contact Report option

File: $CARSPATH/modules/common/reports/tctc

Position Types Code Table Provides a list of entries in the Position Type table.

File: $CARSPATH/modules/placement/reports/tptype


Letters

Introduction

CX contains standard letters for the correspondence needs of the Student Affairs and Career Placement products.

Letters

Business Letters File: $CARSPATH/modules/stuserv/reports/ltrbus

Chapel Absence Letters The following menu options are used to create, generate, and print chapel absence letters. To do so, they are run in the order shown.

• Select Absence Letters - creates Contact records for students who have absences from chapel/convocation for the specified session and year

• Create Absence Letters - generates Absence letters from Select Absence Letters process information

• Print Absence Letters - schedules printing of Absence letters, using LPS

File: $CARSPATH/modules/stuserv/reports/ltrchapel

Housing Preference Forms The following menu options are used to generate and print housing preference forms and letters. To do so, they are run in the order shown.

• Housing Preference Forms - generates Housing Preference forms for the Housing office

• Print Housing Letters - schedules printing of Housing Preference forms, using LPS

File: $CARSPATH/modules/stuserv/reports/ltrhsgfrm

Placement Letters File: $CARSPATH/modules/placement/reports/ltrplace

Room/Board Agreement Forms The following menu options are used to generate and print room/board agreement forms. To do so, they are run in the order shown.

• Room/Board Agreement Form - generates Room/Board Agreement forms for the Housing office

• Print Housing Letters - schedules printing of Room/Board Agreement forms, using LPS

File: $CARSPATH/modules/stuserv/reports/ltrrmbrd

Student Affairs Technical Manual 131 Customizing

SECTION 12 - CUSTOMIZING THE STUDENT AFFAIRS PROCESSES

Overview

Introduction

This section provides procedures for setting and installing the features of the Student Affairs and Career Placement products. The following procedures are included:

• Assessing institutional needs for product setup • Reviewing data in tables and records • Changing default field values in macros

Basic Information

This section contains detailed procedures specific to the Student Affairs and Career Placement products. For information on performing basic procedures, such as using the MAKE processor and reinstalling options, refer to the following resources:

• Database Tools and General Utilities course notebook • CX System Reference Technical Manual

Implementation Process Checksheet

The implementation process checksheets for Career Placement and Student Affairs show the general phases in the process to customize and install features of these products. The checksheets define the tasks you must complete to install the products and the correct sequence for the tasks.

Use the procedures in this section to help you complete your implementation of Student Affairs and Career Placement.

Customizing 132 Student Affairs Technical Manual

Assessing the Student Affairs Setup

Introduction

CX provides several ways to implement the options of the Student Affairs and Career Placement products. After assessing the needs of your institution, you can change the default settings of the Student Affairs and Career Placement enable macros and reinstall the products.

This section lists and describes the features that you must assess before you can modify the macros.

Enabling Products

The default setup in CX provides the Student Affairs product as enabled. If your institution wants to include Health and Student Services menus in Student Affairs, such as tutor service entry, you must enable the associated Matriculation module. To enable the Matriculation module, you must change the default setting of the macro, ENABLE_MOD_MATRICULATION, from N to Y.

Chapel/Convocation Attendance

The Student Affairs product’s default setup provides the Student Services: Chapel/Convocation menu, accessed from the Student Management: Student Services menu, for the entering and scheduling of chapel/convocation events and the tracking of student attendance of such events. If the institution does not want the Student Affairs office to have such options, you must change the setting of the macro, ENABLE_FEAT_CHAPEL, from Y to N.

Events Scheduling

The Student Affairs product’s default setup provides options in the Student Services: Housing/Events menu for entering and scheduling single and group events. If the institution does not want the Student Affairs office to have such options, you must change the setting of the macro, ENABLE_FEAT_EVENTS, from Y to N.

Placement of Housing and Incident Menus

The Student Affairs product’s default setup also places the Housing/Events and Personal/Campus Incident menus in the Student Management: Main menu. If your institution wants to incorporate these menus as submenus in the Student Management: Student Services menu, you must change the setting of the macro, ENABLE_MOD_STUSERV, from N to Y.

Note: If your institution wants only the campus security office to access the Student Services: Personal/Campus Incidents menu, you should to keep this menu as a separate menu.

Personal/Campus Incidents

The Student Affairs product’s default setup provides the Student Services: Personal/Campus Incidents menu to assist you in maintaining records of personal and campus incidents as required by Public Law 101-542, the Criminal Awareness Act. If your institution does not want to use CX to maintain such records, you must change the setting of the macro, ENABLE_FEAT_INCIDENT, from Y to N.


Reviewing Data in Tables and Records

Introduction

After assessing features of Student Affairs and setting the appropriate enable macros, you must review the setup of CX tables and records.

Procedure

The following procedure provides the steps to review the values of the CX tables and records.

1. For each Student Affairs and Career Placement table, review the codes supplied with CX. Determine whether the codes meet the needs of your institution. Make updates as appropriate.

2. Review the institution’s records converted from the previous Student Affairs and Career Placement system. Determine whether the records need to be updated to meet the needs of CX reports. Make updates as appropriate.

Table and Record Information

For more information about the tables and records in the Student Affairs product, see the section Student Affairs Tables and Records in this manual.

Order of Table Information in This Section

Information about the setup of these tables appears in the following order in this manual: • Tables that require modification appear first, in the order of implementation recommended

by CARS • Tables that do not require modification appear after the required tables, in alphabetical

order

Table Setup Sequence

The following lists the sequence in which you should set up the Student Affairs and Career Placement tables. Information about setting up each of the tables below follows in this section. The Student Affairs tables appear in the following menus:

• Health Services: Table Maintenance menu • Student Management: Personal/Campus Incident menu • Student Placement: Table Maintenance menu • Student Services: Chapel/Convocation menu

Note: For reference information about the tables listed below, see the Student Affairs Tables and Records section in this manual.

1. Allergy table (allergy_table)

2. Immunization table (immune_table)

3. Medical History table (medhist_table)

4. Special Conditions table (speccond_table)

5. Personal Incident table (stupers_table)

6. Career Skills table (cr_skl_table)

7. Contact table (ctc_table)


8. Position Type table (pos_type_table)

9. Chapel/Convocation Event table (chap_table)


Building the Health Services Tables

Introduction

The processes in the Student Affairs products use the Health Services tables to maintain health information. You must build these tables before performing any Health Services processing.

Access

You access the Health Services tables from the Health Services: Table Maintenance menu.

Allergy Table

The following lists the fields in the Allergy table in the order in which you complete them. To access this table, select Allergy Table from the Health Services: Table Maintenance menu, then select Finish.

Code A code that Identifies a type of allergy (e.g., PEN).

Description A description of the allergy whose code appears in the Code field (e.g., Penicillin).

Immunization Table

The following lists the fields in the Immunization table in the order in which you complete them. To access this table, select Immunization Table from the Health Services: Table Maintenance menu, then select Finish.

Code A code that Identifies a type of immunization (e.g., POLI).

Description A description of the immunization whose code appears in the Code field (e.g., Polio).

Medical History Table

The following lists the fields in the Medical History table in the order in which you complete them. To access this table, select Medical History Table from the Health Services: Table Maintenance menu, then select Finish.

Code A code that Identifies a type of medical condition (e.g., HART).

Description A description of the medical condition whose code appears in the Code field (e.g., Irregular heart activity).

Special Conditions Table

The following lists the fields in the Special Conditions table in the order in which you complete them. To access this table, select Special Conditions Table from the Health Services: Table Maintenance menu, then select Finish.

Code A code that Identifies a type of special condition (e.g., VRGO).


Description A description of the special condition whose code appears in the Code field (e.g., Vertigo).

Type A code indicating a type of special condition. Valid codes are:

• A (Academic) • P (Physical)


Building the Personal/Campus Incident Tables

Introduction

The processes in the Student Affairs product use the Personal/Campus Incident tables to maintain records of personal and campus incidents as required by Public Law 101-542, the Criminal Awareness Act. You must build these tables before performing any Personal/Campus Incident processing.

Access

You access the Personal/Campus Incident tables from the Student Management: Personal/Campus Incident menu.

Personal Incident Table

The following lists the fields in the Personal Incident table in the order in which you complete them. To access this table, select Incident Table from the Student Management: Personal/Campus Incident menu, then select Finish.

Code A code that Identifies a type of incident (e.g., POL, DORM).

(Incident Code Text) Text for the personal incident code appearing in the Code field appears in this unlabeled field to the right of the Code field (e.g., Police, Dormitory).

Priority An integer indicating the priority value for ranking the incident (e.g., 0).

Note: The priority sort takes lower integers (e.g., 0) to be higher priority than higher integers (e.g., 100).

Crime Report A code indicating whether this incident type should be included in the Crime Report. The following are valid values:

• N (No) • Y (Yes)


Building the Career Placement Tables

Introduction

The processes in the Career Placement product use the Career Placement tables to maintain information about your institution’s student placement service. You must build these tables before performing any Career Placement processing.

Access

You access the Career Placement tables from the Student Placement: Table Maintenance menu.

Career Skills Table

The following lists the fields in the Career Skills table in the order in which you complete them. To access this table, select Career Skills Table from the Student Placement: Table Maintenance menu, then select Finish.

Code A code that Identifies a type of skill (e.g., TYPE).

Text A description of the skill code that appears in the Code field (e.g., Typing).

Contact Table

To access this table, select Contact from the Student Placement: Table Maintenance menu, then select Finish.

Note: See the CX System Reference Technical Manual for additional information about this common table.

Position Type Table

The following lists the fields in the Position Type table in the order in which you complete them. To access this table, select Position Type Table from the Student Placement: Table Maintenance menu, then select Finish.

Position Type Code A code that Identifies a type of position (e.g., SECR, PROG).

Description A description of the code that appears in the Position Type Code field (e.g., secretary, programmer).


Building the Chapel/Convocation Tables

Introduction

The processes in the Student Affairs and Career Placement products use the Chapel/Convocation tables to enter and schedule chapel/convocation events and track student attendance of such events. You must build these tables before performing any Chapel/Convocation processing.

Access

You access the Chapel/Convocation tables from the Student Services: Chapel/Convocation menu.

Chapel/Convocation Event Table

The following lists the fields in the Chapel/Convocation Event table in the order in which you complete them. To access this table, select Maintain Meeting Table from the Student Services: Chapel/Convocation menu, then select Finish.

Note: Before adding new records for a session, query on all records for the session, and the meeting number will default to the next available value.

Session A code that Identifies the session during which the chapel/convocation event is to occur (e.g., FA).

Year The calendar year during which the chapel/convocation event is to occur (e.g., 2000).

Date The date (mm/dd/yyyy) for the chapel/convocation event.

Meeting # The meeting number for the chapel/convocation event (e.g., 9).

Note: A 0 is used only for a null date.

Maximum Meeting # Display only - The maximum meeting number.

Student Affairs Technical Manual 141 Maintenance Procedures

SECTION 13 - STUDENT AFFAIRS MAINTENANCE PROCEDURES

Overview

Introduction

This section provides procedures you need to maintain the Student Affairs product, including: • Adding new Student Services records or updating existing Student Services records to

students’ records for the next session • Adding initial Chapel/Convocation records for the next session

The maintenance procedures are organized in two groups in this section: • Annual • Session-based

The Student Affairs product contains only session-based maintenance procedures. The Career Placement product contains no maintenance procedures.

Definitions

The following defines the two types of maintenance procedures that you must perform in order to keep your database accurate and CX functioning properly.

Annual You must perform these procedures annually.

Session-based You must perform these procedures at the beginning, middle, or end of each session.

Process

This list shows the general phases for maintaining Student Affairs. It identifies the order in which you should perform the maintenance procedures included in this section.

1. Perform session-based maintenance procedures.

2. Perform annual maintenance procedures, if any.

Maintenance Procedures 142 Student Affairs Technical Manual

Session-Based Maintenance

Introduction

You must add and/or update Student Servicesrecords to students’ records prior to the beginning of a new session. Student Affairs provides a method for adding new Student Services records and for updating Student Services records from previous sessions.

Process

This list shows the general phases that take place when you add and update Student Services records to a student’s ID and Profile records.

1. Add Student Services records for all summer and pre-registered students.

2. Add, or copy from previous sessions, Student Services records for all students registered in previous sessions.

Note: The following are guidelines for copying previous Student Services records: • If less than half of students’ records have to be updated, use the Update Student

Services Record process, which copies records from a previous session • If more than half of students’ records have to be updated, use the Add Student

Services Record process, which adds new records

Adding Records

The following is a list of the steps to use the addstuserv SQL script to add Student Services records to students’ records for the current session. The script adds Student Services records to all students who have a current Academic record but do not have a Student Services record.

Note: If more than half of students’ records have to be updated, use this procedure, which adds new records. If less than half of students’ records have to be updated, use the Updating Records procedure in this section, which copies records from a previous session. The addstuserv script does not overwrite existing Student Services records.

1. From the Student Management: Student Services menu, select Add Student Service Record. The Add Student Service Record screen appears with the cursor in the Session field.

2. Enter the session code for the current session, then press <Tab>. The cursor moves to the Academic Year field.

3. Enter the institutional year for the current session, then select Finish. The Output Parameters and Scheduling window appears.

4. Complete the fields on the Output Parameters and Scheduling window, then select Finish. CX schedules or initiates the addstuserv script. When the process completes successfully, CX sends you mail titled: “INFORMER finished successfully.”

Note: See the Getting Started User Guide for information how to complete the Output Parameters and Scheduling window.


Updating Records

This lists the steps to use the updstuserv SQL script to update student service information in students’ records by copying Student Services records from a previous session. The script updates Student Services records in the current session with information from a previous session that you specify.

Note: If less than half of students’ records have to be updated, use this procedure, which copies records from a previous session. If more than half of students’ records have to be updated, use the Adding Records procedure in this section, which adds new records.

1. From the Student Management: Student Services menu, select Update Student Service. The Update Student Service screen appears with the cursor in the Old Session field.

2. Enter the code for the session to be copied, then press <Tab>. The cursor moves to the Old Year field.

3. Enter the year (yyyy) to be copied. The cursor moves to the New Session field.

4. Enter the code for the session to be updated, then press <Tab>. The cursor moves to the New Year field.

5. Enter the year (yyyy) to be updated, then select Finish. The Output Parameters and Scheduling window appears.

6. Complete the fields on the Output Parameters and Scheduling window, then select Finish. CX schedules or initiates the updstuserv script. When the process completes successfully, CX sends you mail titled: “INFORMER finished successfully.”


Maintenance Procedures 144 Student Affairs Technical Manual

Chapel/Convocation Session-Based Maintenance

Introduction

Before the Student Affairs office can maintain Chapel/Convocation information for a session, you must add initial Chapel/Convocation records to students’ records. You must also add a record to the Chapel/Convocation table for the session.

Process

This list shows the general phases that take place when you add initial Chapel/Convocation records.

1. Use the chapaddinit script to add initial Chapel/Convocation records for the new session. The script enters filler Chapel/Convocation records with no date for each student, session, and year.

2. Enter a record in the Chapel/Convocation Event table for the session.

3. Use the Check Attendance Records feature to check that the date of the meeting in the records exists in the Chapel/Convocation Event table.

Adding Initial Records

This lists the steps to use the chapadinit script to add initial Chapel/Convocation records to students’ records. The script adds Chapel/Convocation records for all full-time, registered students for the session. Each student must have a Chapel/Convocation record in order for CX to determine who is required to attend chapel and/or convocation events.

1. From the Student Services: Chapel/Convocation menu, select Add Initial Records. The Add Initial Records screen appears with the cursor in the Session field.

2. Enter the session code for the current session, then press <Tab>. The cursor moves to the Academic Year field.

3. Enter the instructional year (yyyy). The cursor moves to the Program field.

4. Enter the program code, then press <Tab>. The cursor moves to the Subprogram field.

Note: Leave this field blank to select all programs.

5. Do you want to add initial Chapel/Convocation records for all subprograms? • If yes, leave this field blank • If no, do one of the following:

− Enter the code for the subprogram you want − Enter an asterisk to use as a wildcard to select a group of subprograms you want

(e.g., ENG*)

6. Press <Tab>. The cursor moves to the Status field.

7. If necessary, enter a specific academic status code, then select Finish. The Output Parameters and Scheduling window appears.

8. Complete the fields on the Output Parameters and Scheduling window, then select Finish. CX schedules or initiates the chapadinit script. When the process completes successfully, CX sends you mail titled: “Addition of Initial Chapel Records finished successfully.”



Adding an Initial Table Entry

This lists the steps to add an initial Chapel/Convocation Event table entry for the session.

1. From the Student Services: Chapel/Convocation menu, select Maintain Meeting Table, then select Finish. The Chapel/Convocation Event Table screen appears.

2. Select Query, then press <Esc>. CX queries all existing records.

Note: Before you add new records for a session, you must query all records for the session so that CX defaults the meeting number to the next available value when you add a record.

3. Select Add. The cursor moves to the Session field.

4. Enter the following: • The new session • The year • The date for the meeting

5. Press <Esc>. CX saves your field entries.

6. Select Exit, then press <Enter>. The Student Services: Chapel/Convocation menu appears.

Checking Attendance Records

The following lists the steps to use the chapel script to verify that the date for the chapel and/or convocation exists in the Chapel/Convocation Event table. Use the script before the Student Affairs office begins to maintain Chapel/Convocation records.

Note: You can use uppercase and/or lowercase entries for each of your responses to questions CX asks you, except for the session code (e.g., FA for Fall).

1. From the Student Services: Chapel/Convocation menu, select Check Attendance Records, then select Finish. The prompt, “Enter Session for chapel attendance (FA):” appears.

2. Enter the session code (e.g., FA) in uppercase letters for which you are checking records, then press <Enter>. The prompt, “Enter Academic Year for chapel attendance (1995):” appears.

3. Enter the instructional year (e.g., 1997) for which you are checking records, then press <Enter>. The prompt, “Enter date for chapel attendance (mm/dd/yyyy)” appears.

4. Enter the date (mm/dd/yyyy) of the chapel/convocation event, then press <Enter>. The message, “NOTE: The date entered next will not be included for checking absences” appears.

Note: The date must exist in the Chapel/Convocation Event table. • The system checks the number of Chapel/Convocation records, and the message

(for example), “Number of Chapels is 2” appears. • The question, “Do you want to add chapel attendance records?” appears.

5. Enter N, then press <Enter>.

6. Enter Q, then press <Enter>.

7. Press <Enter>. The Student Services: Chapel/Convocation menu appears.

Student Affairs Technical Manual 147 Errors and Crash Recovery

SECTION 14 - PROGRAM ERRORS AND CRASH RECOVERY

Overview

Introduction

This section provides the following: • Crash recovery procedures

Note: Refer to the Student Affairs User Guide and the Career Placement User Guide for a list of the more common status, field error, and warning messages that can occur when menu users execute the programs in Student Affairs.

Errors and Crash Recovery 148 Student Affairs Technical Manual

Error and Crash Recovery Procedures

Introduction

The procedures to recover from a crash are organized by the seriousness of the error.

Core Dump Recovery

The following procedure describes the steps to recover from a core dump of an entry program.

1. Access the program screens directory for the entry program.

Example: % cd/$CARSPATH/modules/regist/stuentry/progscr

2. Reinstall each program screen file.

Example: % make reinstall F=<filename>

Note: You can also reinstall all of the screens by entering the following: − % make reinstall F=all

3. Attempt to execute the entry program. Did the reinstall of the program screens fix the error? • If yes, you are done • If no, go to step 4

4. Access the source code directory of the entry program.

Example: % cd/$CARSPATH/src/regist/stuentry

5. Reinstall the source code for the entry program.

Example: % make reinstall

6. Attempt to execute the entry program. Did the reinstall of the program source code fix the error?

• If yes, you are done • If no, go to step 7

7. In the source code for the entry program, delete the old compiled code for the entry program.

Example: % make cleanup

8. Reinstall the entry program source code.

Example: % make reinstall

9. Attempt to execute the entry program. Did the deletion of the old code and reinstallation of the program source code fix the error?

• If yes, you are done • If no, go to step 10

10. Review the libraries for the entry program. In the source code for the entry program, review the file, Makefile. In the file, search for the parameter, ADDLIBS, which identifies the libraries that you must reinstall.

Example: % vi Makefile

/ADDLIBS

Student Affairs Technical Manual 149 Errors and Crash Recovery

11. Reinstall the libraries for the entry program, then reinstall the source for the entry program.

Example: % cd <to appropriate library>

% make reinstall

% cd/$CARSPATH/regist/stuentry

% make reinstall

Note: You must reinstall the source program to include any library changes.

12. Attempt to execute the entry program. Did the reinstallation of the libraries for the entry program fix the error?

• If yes, you are done • If no, call JenzabarSupport Services

Student Affairs Technical Manual 151 Index

INDEX ‘ ‘No Show’ Students Assigned Housing report,

122

A Absence information, 120 Academic advisor, 5 Academic record, 142 accessing

ACE reports, 77 Allergy table, 135 Career Placement tables, 138 Career Skills table, 138 Chapel/Convocation Event table, 139 Chapel/Convocation tables, 139 Contact table, 138 Csh scripts, 77, 120 eventry program, 36 Health Services tables, 135 hentry program, 45 Immunization table, 135 incdentry program, 52 includes, 24 macros, 22 Medical History table, 135 menu option files, 77, 92 menu source files, 77, 79 menudesc file, 79 PERFORM screen files, 113 Personal Incident table, 137 Personal/Campus Incident tables, 137 placement program, 60 Position Type table, 138 schemas, 14 screen files, 77 Special Conditions table, 135 SQL scripts, 77, 119 stuentry program, 71

Accomplishment Roster report, 127 ACE reports, 121–28 Add Attendance/Absence menu option, 96 Add Initial Records menu option, 95 Add Student Service Record menu option, 95 adding

Chapel records, 144 Chapel table entry, 145 Student Services records, 142

addstuserv SQL script, 119 Admissions product, 8 Allergic Reactions detail window, 45 Allergy record, 15 Allergy Report, 125 Allergy Report menu option, 102

Allergy table, 15, 135 fields, 135

Allergy Table menu option, 104 Allergy Table Report, 125 Allergy Table Report menu option, 104 Allergy Table screen, 113 Alumni by Employer report, 127 Alumni Directory menu option, 111 Alumni Directory report, 127 applocate program, 22 assessing product setup, 132 Attendance Detail Report menu option, 96 Attendance information, 120 Attendance Not Required menu option, 95 Available Housing Report menu option, 100 Available Student Housing Report, 124

B background knowledge needed, 5 Business Information menu option, 108 Business Positions menu option, 108 Business Record screen, 113

C Campus incidents. See Maintain Incidents

screen Career Goal Listing window, 62 Career Goal Skills window, 61 Career Goal window, 60 Career Placement

parameters, 59 program, 55

Career Placement product, 8 Career Placement screens, 60 Career Position record, 15 Career record, 15 Career Skill Codes Table report, 128 Career Skills menu option, 110 Career Skills record, 16 Career Skills table, 138

fields, 138 Career Skills Table menu option, 112 Career Skills Table Report menu option, 112 Career Skills Table screen, 114 changing

default settings, 132 chapadctc Csh script, 120 chapadday Csh script, 120 chapadinit Csh script, 120 Chapel Absence Report, 123 chapel Csh script, 121 Chapel records

adding initial, 144 Chapel Total Report, 123

Index 152 Student Affairs Technical Manual

Chapel/Convocation attendance, 132 Chapel/Convocation Attendance Record screen,

114 Chapel/Convocation Event table, 16, 139

fields, 139 Chapel/Convocation Event Table screen, 114 chapel/convocation events

checking table entries, 145 Chapel/Convocation record, 16 Chapel/Convocation records, 121

checking, 121 Chapel/Convocation Table Report, 123 Check Attendance Record menu option, 96 columns

table, 9 Company Information menu option, 110 Company Information Report, 127 Company Positions Available report, 127 Company Positions menu option, 110 Company Student Career Match Report, 127 Company Student Match menu option, 110 Contact menu option, 112 Contact Report menu option, 112 Contact Table Report, 128 Contact Table screen, 114 Contacts screen, 61 conventions, 3 core dump recovery, 148 Counts and Lists menu option, 93, 100 Counts by Class Report menu option, 93, 100 Create Absence Letters menu option, 97 Crime Statistics Report, 126 Crime Statistics Report menu option, 107 Criminal Awareness Act, 116 Csh scripts, 120

chapadctc, 120 chapadday, 120 chapadinit, 120 chapel, 121 ltbrun, 121 updstuserv, 121

customizations screen changes, 1

D data dictionary, 14 Data Entry - Church Form screen, 71 Data Entry - Form Menu screen, 74 Data Entry - Graduation Form screen, 72 Data Entry - Parent Form screen, 72 Data Entry - Program Enrollment screen (screen

1 of 2), 72 Data Entry - Program Enrollment screen (screen

2 of 2), 73 Data Entry - School Form screen, 73

Data Entry - Student Data Form screen, 74 Data Entry menu option, 92 data flow descriptions

Career Placement program, 58 Event Entry program, 32 Health Entry program, 38 Incident Entry program, 48 Student Entry program, 64

database tools background knowledge, 6

dec.h files, 25 def.c files, 25–28

example, 26 default settings, changing, 132 definition

macro, 22 definition files. See def.c definitions

SQL tables, 9 detail windows

Allergic Reactions, 45 GPA Totals, 75 GPA/Session, 74 Immunizations, 46 Insurance, 46 Medical Visit History, 46 Personal/Campus Incident Record, 53 Residence Hall, 75 Site, 73 Special Conditions, 46

diagrams entity relationship, 13 menu flow, 79 process flow, 7, 32, 38, 48, 56, 64

directory path. See accessing Display Registrations menu option, 108 Display Student Data menu option, 98 Display Transcripts menu option, 107 dmls, 25 dmlts, 25 dmms, 25 documents, related, 2

E Employers of Alumni menu option, 111 Employment Information menu option, 109 Employment Record screen, 115 enable macros, 23 enabling product, 132 Event Entry


Events Scheduing - Event Entry screen, 36 Events scheduling, 132 Events Scheduling - Event Entry screen, 36


Events Scheduling menu option, 101 Events Sorted by report, 124

F fees assessed, 8 field descriptions, 14 fields

Allergy table, 135 Career Skills table, 138 Chapel/Convocation Event table, 139 Immunization table, 135 Medical History table, 135 Personal Incident table, 137 Position Type table, 138 Special Conditions table, 135

filenames Informix

allergy_rec, 15 allergy_table, 15 career_pos_rec, 15 career_rec, 15 career_skl_rec, 16 chap_rec, 16 chap_table, 16 grdmsg_rec, 16 health_rec, 17 immune_rec, 17 immune_table, 17 insure_rec, 17 intvwee_rec, 17 intvwer_rec, 18 medhist_rec, 18 medhist_table, 18 pos_skl_rec, 19 speccond_rec, 19 speccond_table, 19 stu_serv_rec, 19 stupers_rec, 18 stupers_table, 18

UNIX allergy, 15 career, 15 careerpos, 15 careerskl, 16 chap, 16 grdmsg, 16 health, 17 immune, 17 insure, 17 intvwee, 17 intvwer, 18 medhist, 18 posskl, 19 speccond, 19 stupers, 18

stuserv, 19 tallergy, 15 tchap, 16 timmune, 17 tmedhist, 18 tspeccond, 19 tstupers, 18

files database, 14 dec.h, 25 def.c, 25–28 mac.h, 25 schema, 14

Financial Aid product, 8 flow chart. See process flow, product

G GPA Reports menu option, 94, 101 GPA Totals detail window, 75 GPA/Session detail window, 74 Grade Message record, 16

H Health Entry

parameters, 43 program, 37 screens, 45

Health record, 17 Health Services, 5 Health Services Entry, 102 Health Services Entry menu option, 102 Health Services for Students screen, 45 Health Services menu, 45 Health Services Special Conditions Table

Report, 126 Health Services: Table Maintenance Menu, 91,

104 Housing and Incident menus

placement, 132 Housing Data Entry - Student Housing Form

screen, 74 Housing Data Entry menu option, 98 Housing Preference Forms menu option, 98 Housing Wait List menu option, 101 Housing/Events, 5

I ID Entry for Health Provider screen, 46 Immunization record, 17 Immunization Report, 125 Immunization Report menu option, 104 Immunization table, 17, 135

fields, 135 Immunization Table menu option, 104 Immunization Table Report, 126


Immunization Table screen, 115 Immunizations detail window, 46 Immunizations Report menu option, 102 implementing product, 132 Incident Entry


Incident Entry menu, 52 Incident Entry screens, 52 Incident Report, 126 Incident Report menu option, 105 Incident Table menu option, 107 Incident Table Report menu option, 107 INFORMIX-SQL

background knowledge, 6 installing features, 133 Insurance detail window, 46 Insurance record, 17 Interactive Degree Audit, 5 Interview Calendar menu option, 109 Interview Calendar report, 127 Interview Positions menu option, 110 Interview Report, 127 Interview Schedule menu option, 109 Interview Schedule report, 127 Interview Schedule window, 61 Interviewee menu option, 109 Interviewee record, 17 Interviewee Schedule menu option, 109 Interviewee Schedule report, 128 Interviewer record, 18 Interviewer Schedule (Interviewee Schedule)

screens, 115 Interviewer Schedule (Interviewer Schedule)

screen, 115 Interviewer Schedule menu option, 109 Involvement Roster report, 128

J Jenzabar CX

background knowledge, 6

L letters, 129 ltbrun Csh script, 121

M mac.h files, 25 macros, 21–24

relationships, 21 Maintain Attendance Record menu option, 96 Maintain Incidents menu option, 105 Maintain Meeting Table menu option, 97 maintenance procedures, 145 maintenance tables. See PERFORM screens

manual background knowledge, 5 conventions, 3 how to use, 1 purpose, 1 structure, 1

Medical History record, 18 Medical History Report menu option, 104, 105 Medical History table, 18, 135

fields, 135 Medical History Table menu option, 105 Medical History Table Report, 126 Medical History Table screen, 115 Medical Revisit Report, 125 Medical Visit History detail window, 46 Medical Visits Report menu option, 104 Meeting Table Report menu option, 97 menu options

Add Attendance/Absence, 96 Add Initial Records, 95 Add Student Service Record, 95 Allergy Report, 102 Allergy Table, 104 Allergy Table Report, 104 Alumni Directory, 111 Attendance Detail Report, 96 Attendance Not Required, 95 Available Housing Report, 100 Business Information, 108 Business Positions, 108 Career Skills, 110 Career Skills Table, 112 Career Skills Table Report, 112 Check Attendance Record, 96 Company Information, 110 Company Positions, 110 Company Student Match, 110 Contact, 112 Contact Report, 112 Counts and Lists, 93, 100 Counts by Class Report, 93, 100 Create Absence Letters, 97 Crime Statistics Report, 107 Data Entry, 92 Display Student Data, 98 Display Transcripts, 107 Employers of Alumni, 111 Employment Information, 109 Events Scheduling, 101 GPA Reports, 94, 101 Health Services Entry, 102 Housing Data Entry, 98 Housing Preference Forms, 98 Housing Wait List, 101 Immunization Report, 104 Immunization Table, 104


Immunizations Report, 102 Incident Report, 105 Incident Table, 107 Incident Table Report, 107 Interview Calendar, 109 Interview Positions, 110 Interview Schedule, 109 Interviewee, 109 Interviewee Schedule, 109 Interviewer Schedule, 109 Maintain Attendance Record, 96 Maintain Incidents, 105 Maintain Meeting Table, 97 Medical History Report, 104, 105 Medical History Table, 105 Medical Visits Report, 104 Meeting Table Report, 97 Missing Initial Record, 97 Off Campus Housing Report, 101 Position Type, 112 Position Type Table, 112 Print Absence Letters, 97 Print Courses by Student, 108 Print Housing Letters, 100 Query/Resolve Incidents, 107 Recent Graduates, 111 Residence Hall No Shows, 94 Residence Report, 98 Room/Board Agreement Form, 98 Scheduled Events Report, 102 Select Absence Letters, 97 Special Conditions Report, 102, 105 Special Conditions Table, 105 Student Career Goals, 108 Student Career Skills, 108 Student Company Match, 110 Student Involvement Report, 94 Student Profile Report, 92 Student/Alum Placement, 107 Students by Accomplish, 111 Students by Advisor, 93 Students by Involvement, 112 Students by Major, 111 Total Attendance Report, 96 Update Student Service, 95 Vehicle Registrations, 94

menudesc file, 79 menuopts. See menus menus, 78–105

Health Services, 45 Health Services: Table Maintenance, 91, 104 Incident Entry, 52 Student Management: Health Services, 91,

102 Student Management: Personal/Campus

Incident, 91, 105

Student Management: Student Placement, 92, 107

Student Management: Student Services, 91, 92

Student Placement: Communications Management, 92, 109

Student Placement: Query by Form, 92, 108 Student Placement: Reports, 92, 109 Student Placement: Table Maintenance, 92,

112 Student Services: Chapel/Convocation, 91, 95 Student Services: Housing/Events, 98 Student Services: Housing/Events Menu, 91

menusrc. See menus Missing Initial Chapel Records Report, 123 Missing Initial Record menu option, 97

O Off Campus Housing Report menu option, 101

P parameters

Career Placement, 59 Event Entry, 34 Health Entry, 43 Incident Entry, 50 passed by menuopts, 79 Student Entry, 69

Parameters for Student Services Count Report, 122, 124

Parameters for Student Services Cumulative GPA Report, 122, 124

Parameters for Student Services Report by Classification, 124

Parameters for Student Services Report by Classification report, 122, 124

Past Medical History Report, 125 PERFORM screens, 105–17 Personal Incident record, 18 Personal Incident table, 18, 137

fields, 137 Personal Incident Table Report, 126 Personal Incident Table screen, 116 Personal/Campus Incident Form screen, 52 Personal/Campus Incident Record detail

window, 53 Personal/Campus Incident Record screen, 116 Personal/Campus incidents, 132 Personal/Campus Incidents, 5 pointers

form and sqlda, 25 Position Identification screen, 116 Position Listing window, 62 Position Skills record, 19 Position Skills window, 61


Position Type menu option, 112 Position Type table, 138

fields, 138 Position Type Table menu option, 112 Position Type Table screen, 116 Position Types Code Table report, 128 Position window, 60 Print Absence Letters menu option, 97 Print Courses by Student menu option, 108 Print Housing Letters menu option, 100 procedures

adding initial Chapel records, 144 adding initial Chapel table entry, 145 adding Student Services records, 142 checking Chapel table, 145 core dump recovery, 147–49 reviewing table, record data, 133 updating Student Services records, 143

process adding initial chapel/convocation records, 144 adding/updating Student Services records,

142 process checksheet, 131 process flow

Career Placement, 56 Event Entry, 32 Health Entry, 38 Incident Entry, 48 product, 7 Student Entry, 64

processes, 5–8 product

background knowledge, 5 process flow, 7 purpose, 5 related products, 8

product setup setting, 132

programs applocate, 22 Career Placement, 55 Event Entry, 31 Health Entry, 37 Incident Entry, 47 Student Entry, 63

Public Law 101-542, 116

Q Query/Resolve Incidents menu option, 107 QuickMate


R Recent Graduates Eligible for Alumni File report,

128

Recent Graduates menu option, 111 records, 14–19

Allergy, 15 Career, 15 Career Position, 15 Career Skills, 16 Chapel/Convocation, 16 field descriptions, 14 Grade Message, 16 Health, 17 Immunization, 17 Insurance, 17 Interviewee, 17 Interviewer, 18 Medical History, 18 Personal Incident, 18 Position Skills, 19 required, 12 reviewing data, 133 Special Conditions, 19 Student Services, 19

recovery, core dump, 147–49 references. See documents, related Registration Entry, 5 Registration product, 8 related documents, 2 reports. See ACE reports

‘No Show’ Students Assigned Housing, 122 Accomplishment Roster, 127 Allergy Report, 125 Allergy Table Report, 125 Alumni by Employer, 127 Alumni Directory, 127 Available Student Housing Report, 124 Career Skill Codes Table, 128 Chapel Absence Report, 123 Chapel Total Report, 123 Chapel/Convocation Table Report, 123 Company Information Report, 127 Company Positions Available, 127 Company Student Career Match Report, 127 Contact Table Report, 128 Crime Statistics Report, 126 Events Sorted by, 124 Health Services Special Conditions Table

Report, 126 Immunization Report, 125 Immunization Table Report, 126 Incident Report, 126 Interview Calendar, 127 Interview Report, 127 Interview Schedule, 127 Interviewee Schedule, 128 Involvement Roster, 128 Medical History Table Report, 126 Medical Revisit Report, 125


Missing Initial Chapel Records Report, 123 Parameters for Student Services Count

Report, 122, 124 Parameters for Student Services Cumulative

GPA Report, 122, 124 Parameters for Student Services Report by

Classification, 122, 124 Past Medical History Report, 125 Personal Incident Table Report, 126 Position Types Code Table, 128 Recent Graduates Eligible for Alumni File, 128 Special Conditions Report, 125 Student Career Goals and Skills Report, 128 Student Company Career Match Report, 128 Student Course Report, 126 Student Involvement Report, 122 Student Profile Report, 123 Student Residence Report, 124 Student Roster by Major, 128 Student Vehicle Report, 123 Students by Advisor, 123 Students Living Off Campus, 124 Students Not Receiving Chapel/Convocation

Records, 123 Waiting List for Student Housing, 125

Residence Hall detail window, 75 Residence Hall No Shows menu option, 94 Residence Report menu option, 98 reviewing table/record data, 133 Room/Board Agreement Form menu option, 98 rows

table, 9

S Schedule Interview window, 61 Scheduled Events Report menu option, 102 schemas, 14 screens. See PERFORM screens

Allergy Table, 113 Business Record, 113 Career Placement, 60 Career Skills Table, 114 Chapel/Convocation Attendance Record, 114 Chapel/Convocation Event Table, 114 Contact, 61 Contact Table, 114 Data Entry - Church Form, 71 Data Entry - Form Menu, 74 Data Entry - Graduation Form, 72 Data Entry - Parent Form, 72 Data Entry - Program Enrollment (screen 1 of

2), 72 Data Entry - Program Enrollment (screen 2 of

2), 73 Data Entry - School Form, 73

Data Entry - Student Data Form, 74 Employment Record, 115 Event Entry, 36 Events Scheduling - Event Entry, 36 Health Entry, 45 Health Services for Students, 45 Housing Data Entry - Student Housing Form,

74 ID Entry for Health Provider, 46 Immunization Table, 115 Incident Entry, 52 Interviewer Schedule (Interviewee Schedule),

115 Interviewer Schedule (Interviewer Schedule),

115 Medical History Table, 115 Personal Incident Table, 116 Personal/Campus Incident Form, 52 Personal/Campus Incident Record, 116 Position Identification, 116 Position Type Table, 116 Special Conditions Table, 117 Student Entry, 71 Student Identification (Student Career Goals),

117 Student Identification (Student Career Skills),

117 Student/Alumni Placement - Business Form,

60 Student/Alumni Placement - Employment

Query Form, 61 Student/Alumni Placement - Placement Form,

62 Select Absence Letters menu option, 97 session-based maintenance

Chapel/Convocation, 145 Student Services, 143

setting features, 133 Site detail window, 73 Special Conditions detail window, 46 Special Conditions record, 19 Special Conditions Report, 125 Special Conditions Report menu option, 102,

105 Special Conditions table, 19, 135

fields, 135 Special Conditions Table menu option, 105 Special Conditions Table screen, 117 SQL

table definition, 9 SQL scripts, 119

addstuserv, 119 Student Advisor, 5 Student Affairs

ACE reports, 121–28 associated products, 8


customizing, 133 letters, 129 macros, 21–24 maintenance, 145 menus, 78–105 PERFORM screens, 105–17 processes, 5–8 purpose, 5 records, 14–19 SQL scripts, 119 tables, 14–19

Student Career Goals and Skills Report, 128 Student Career Goals menu option, 108 Student Career Skills menu option, 108 Student Company Career Match Report, 128 Student Company Match menu option, 110 Student Course Report, 126 student data

credentials, 8 financial aid, 8 initial entry, 8

Student Entry parameters, 69 program, 63

Student Entry screens, 71 Student Identification (Student Career Goals)

screen, 117 Student Identification (Student Career Skills)

screen, 117 Student Involvement Report, 122 Student Involvement Report menu option, 94 Student Management: Health Services menu,

102 Student Management: Health Services Menu, 91 Student Management: Personal/Campus

Incident menu, 105 Student Management: Personal/Campus

Incident Menu, 91 Student Management: Student Placement

Menu, 92, 107 Student Management: Student Services menu,

92 Student Management: Student Services Menu,

91 Student Placement: Communications

Management Menu, 92, 109 Student Placement: Query by Form Menu, 92,

108 Student Placement: Reports Menu, 92, 109 Student Placement: Table Maintenance Menu,

92, 112 Student Profile Report, 123 Student Profile Report menu option, 92 Student Residence report, 124 Student Residence Report, 124 Student Roster by Major report, 128

Student Services, 5 maintenance, 143

Student Services Cumulative GPA report, 124 Student Services record, 19. See Add Student

Service Record screen adding, 142 updating, 143

Student Services: Chapel/Convocation menu, 95

Student Services: Chapel/Convocation Menu, 91

Student Services: Housing/Events menu, 98 Student Services: Housing/Events Menu, 91 Student Vehicle Report, 123 Student/Alum Placement menu option, 107 Student/Alumni Placement - Business Form

screen, 60 Student/Alumni Placement - Employment Query

Form screen, 61 Student/Alumni Placement - Placement Form

screen, 62 Student/Alumni Placement window, 61 Students by Accomplish menu option, 111 Students by Advisor menu option, 93 Students by Advisor report, 123 Students by Involvement menu option, 112 Students by Major menu option, 111 Students Living Off Campus report, 124 Students Not Receiving Chapel/Convocation

Records report, 123 syntax

schema names, 14

T tables

Allergy, 15, 135 Career Skills, 138 Chapel/Convocation Event, 16, 139 columns, 9 field descriptions, 14 Immunization, 17, 135 Medical History, 18, 135 Personal Incident, 18, 137 Position Type, 138 required, 12 reviewing data, 133 rows, 9 sequence in implementation, 133 Special Conditions, 19, 135

Total Attendance Report menu option, 96 Transcript, 5

U UNIX



table names, 14 Update Student Service menu option, 95 updating

Student Services records, 143 updstuserv Csh script, 121 utilities


V Vehicle Registrations menu option, 94

W Waiting List for Student Housing report, 125 windows

Career Goal, 60 Career Goal Listing, 62 Career Goal Skills, 61 Interview Schedule, 61 Position, 60 Position Listing, 62 Position Skills, 61 Schedule Interview, 61 Student/Alumni Placement, 61