立即与支持人员聊天
与支持团队交流

Stat 6.3 - 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

Object Management (Generic Applications)

Although Quest® Stat® is designed as a complete change management solution for PeopleSoft® and Oracle® Applications, this support can be extended to other file-based (i.e., generic) applications. This is done by system administrators who define in Stat the connection pathways and source directories of the application servers or databases, as well as the types of objects that Stat will support. Once these configuration parameters are in place, users can lock, archive, and migrate objects in generic application environments the same way they do objects in PeopleSoft and Oracle Applications environments.

In Stat, any action you take involving an object is handled and recorded on its associated CSR, including editing, archiving, or migrating it to other environments. Also, Stat lets you place a lock on an object once you associate it with a CSR. Object locking promotes coordination between developers by ensuring that they do not overwrite each other’s work.

For generic applications, there are three classes of objects that you can associate with CSRs:

Classification of Supported Objects

Although Quest® Stat® is designed as a complete change management solution for PeopleSoft® and Oracle® Applications, this support can be extended to other file-based (i.e., generic) applications. This is done by system administrators who define in Stat the connection pathways and source directories of the application servers or databases, as well as the types of objects that Stat will support. Once these configuration parameters are in place, users can lock, archive, and migrate objects in generic application environments the same way they do objects in PeopleSoft and Oracle Applications environments.

In Stat, any action you take involving an object is handled and recorded on its associated CSR, including editing, archiving, or migrating it to other environments. Also, Stat lets you place a lock on an object once you associate it with a CSR. Object locking promotes coordination between developers by ensuring that they do not overwrite each other’s work.

For generic applications, there are three classes of objects that you can associate with CSRs:

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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级