Chat now with support
Chat with Support

Stat 6.0 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

File Objects

Quest® Stat® supports change management for file type objects (also called flat files). In addition to the COBOL, COBOL CPY, SQR, and SQC file types Stat automatically supports, system administrators can configure Stat to support any other type of file object residing in your generic application environments or in a version control management repository (if any). This configuration includes defining working directories where users can modify file objects assigned to them.

Data Objects

Data objects are user-defined or third party data sets residing in your generic application environments that your system administrator has configured Quest® Stat® to support. You lock, archive, and migrate data objects the same way you do file objects. Stat currently supports data objects in generic application environments running on Oracle only.

Schema Objects

Quest® Stat® supports locking, archiving, and migrating schema object definitions on Oracle® databases and on Microsoft® SQL Server® 2005/2008.

Stat supports certain schema object definitions for generic application environments running on Oracle databases. If you are running your generic application on a supported Oracle database version 9i or higher, you can lock, archive, and migrate schema objects. For Oracle 8i databases, you can lock schema object types, buy you cannot archive or migrate them. Stat currently supports the following schema object types:

Although you cannot archive or migrate Oracle 8i schema object types, you can archive and migrate the SQL database scripts that create and alter the schema object definitions. After migrating a database script (which in Stat is treated as a file object), you or your database administrator can run the script and deploy the schema object definitions in the target environment.

The following schema objects may be archived from and migrated to Microsoft SQL Server 2005/2008 databases:

Object Locking and Reservations (Generic Applications)

Object locking is an important part of any change management practice since it coordinates all of the efforts of developers and prevents work from being overwritten. Stat supports logical locking of data objects and file objects in the Quest® Stat® Repository, which means that the lock shows up in the Stat application, but developers can still go directly into their application environments and make changes to the object even if the lock on the object isn’t theirs. As long as the developers use a CSR to modify objects, the coordination of development is maintained.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating