Stat 6.2 - User Guide

Object Locking

Quest® Stat® eliminates development conflicts by creating isolated work environments and managing access to objects. It also accelerates the development cycle by coordinating object development across all environments with its exclusive locking/reservation capabilities.

Through Stat, objects are secured at all times. In order to make changes to objects, a developer must first obtain a lock through Stat. Once an object is locked and assigned to a developer in Stat, that developer has sole rights to work on the object throughout its native computing environment.

Developers have the added advantage of receiving reservations for objects locked by other Stat users. When the objects become available, the next developer with a reservation is automatically notified and the reservation is then converted to a lock.

Migration Management

Quest® Stat® provides a number of change management utilities that greatly facilitate object migrations to and from PeopleSoft, Oracle, and generic application environments. When configuring Stat, system administrators define migration paths for specific purposes; for example, a standard path for updates and fixes, an emergency short-cut path for quick fixes, or a path designated for enhancements.

In Stat, migrating file objects entails moving them from the source file locations of one environment to the source file locations of another environment, or to users’ working directories. For PeopleSoft® proprietary objects, Stat first moves copies of the archived objects into a staging database, which serves as a temporary holding bin for objects. Stat then creates a PeopleSoft project, which contains references to the objects you just staged. At this point, depending on the configuration of the target database, Stat either logs on to PeopleSoft and completes the migration automatically, or you can complete the migration yourself by logging on to PeopleSoft and manually pushing the project into the target database.

In addition, Stat can also be set up to support auto-migrating archive sets to multiple environments distributed over a network. This is configured by system administrators who designate particular environments in a migration path as distribution environments and then associate them with lists of interrelated environments. This way, when you migrate an archive set to a distribution environment, Stat automatically migrates the archive set to all the other environments as well.

Impact Analysis

The Quest® Stat® Impact Analysis Wizard helps developers avoid costly rework and delays by identifying potential impacts on objects before changes are made. Once an object is associated with a Change/Service Request (CSR) the user can execute the wizard to do the following:

For more information, see Impact Wizard .

Project Management

Quest® Stat® projects let you manage business changes from one central location. By incorporating multiple Change/Service Requests (CSRs), activities, and tasks (the individual steps necessary to solve a problem or complete a request), a Stat project is an easy way to assemble and track a variety of activities for an enhancement or upgrade project. This is essential when a complex project encompasses multiple phases, requires a variety of resources, and crosses over service domains (logical business units).

Stat supports project management in a number of ways, including automated workflows, auto tasks, and Gantt charts.

For more information, see The Project Window .