Process Number: 218	Revision Date: 6/9/2003 3:35:00 PM
Revision #: 3	Back | Access Password:

Restore Custom Envision Code

Office Responsible:

DCS - District - Computing Services

Process Type:

internal

Position Title:	Datatel System Administrator		Author:	bnoble
Cross Trained Staff:	jmoody	Manager:	rkeith	Vice Pres.:

Timeline (Deadlines or Time-Constraints) :

Typically after Datatel patches are loaded

What must be done before this process is started:

Patch update installed in target account; Error message such as "XARF02 missing" reported, when custom screen, such as XOBN, invoked.

Which processes are waiting for this process:

Custom screens function properly for users.

Source documents or communication with information needed for this process:

Custom code move definitions (MDEF) in custom application (e.g. XST). We maintain our source code in a custom application to ensure its preserved, when Datatel applications (e.g. ST) are updated. The MDEF identifies the screens, selects and code that are to be moved as one group. For example, the XARF02 move defintion identifies the XOBN screen and its report program.

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

Custom screens execute properly in application accessible to user (e.g. ST).

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

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

1) Invoke Toolkit for custom application (e.g., TM XST) 2) Use MTST to move to "higher" app (e.g., from XST to ST) 3) Within MTST, Select move definition 4) Check move messages, recompile in target application. 5) Check list definitions (PGLS) - the initial copy seems to work ok, but there seems to be a problem with automatic updates. 5) Check custom screen execution. 6) Repeat for other move definitions - all MDEF definitions we keep in live should be executed after a patch update.

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

Notes (Cautions, suggestions for improvement, etc.)

MTST is used after a patch update, to move from custom app to Datatel app. Two other Move/copy utilities: MDEV to move from Datatel to custom app (e.g., from ST to XST) (e.g., to save any work done in ST before a patch update.) MLIV to move between accounts (e.g. test to live).