Process Number: 41	Revision Date: 11/9/2001 11:46:03 AM
Revision #: 16	Back | Access Password:

EPOS/treg Registration Problems

Office Responsible:

DCS - District - Computing Services

Process Type:

internal

Position Title:	Sr. Programmer Analyst		Author:	JMoody
Cross Trained Staff:	rdoidge	Manager:	rdoidge	Vice Pres.:	RTemple

Timeline (Deadlines or Time-Constraints) :

as requested

What must be done before this process is started:

Students call registration office and report problem with telephone registration (or grades). Registration office calls us.

Which processes are waiting for this process:

Students trying to register (or get grades)

Source documents or communication with information needed for this process:

Scripts and voice recordings.

What is the end-result of this process, or the hand-off

Students able to register (or get grades).

What steps must be taken independent of the computer system (Manual Process)

First check what can be locally, such as setup parameters, translate tables, scripts, Datatel`s TGRM screen and our own custom programs in Datatel. If the problem can`t be resolved locally, contact EPOS (see ProcessNo 57). After epos upgrade to Encore 6.2 in June, 2001, improper setting of setup paramters (FLDNET?) caused disk overruns and loss of Student logging. We fixed problem with hanging messages and lines staying "busy", by updating script to increase buffer size (see ProcessNo 20).

Which steps must be taken on a computer (Electronic Process):

To record events, use ROAM log screen, then follow the log to identify processes called and the parameters they`re passed. To fix problem with "no such phrase" being spoken for course name, updated translate table from ROAM maintenance screen. To fix problem with "no such phrase" being spoken for error message, updated Datatel`s TRGM screen.

Related Documents to Process (e.g. Datatel documentation, Government code books, etc.)

Datatel`s TREG manual (TREG.pdf). TRGM, column Treg Msg# shows recording played on errors. Epos line numbers and hunt groups defined in DCS folder, ETR documentation.

Notes (Cautions, suggestions for improvement, etc.)

Create an incident log?