Chat now with support
Chat with Support

Stat 6.1 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Updating CSR Migration Paths with Additional Environments

You can add environments to existing migration paths that are already associated with CSRs. You then have the option of updating the migration path on selected CSRs to include the new environments.

Follow the instructions in the section Migration Path Diagram to add environments to the migration path.
Click Add new env. to CSR.
Select the Update option for each CSR you want to update.
Optionally, select the Update Objects List option if you want to copy the objects from either the Base or Development environment to the newly added environments. Then select Base or Dev.

Post Migration Steps

The Post Migration Steps Maintenance table defines the actions to be taken on certain types of objects in an archive set after it has been migrated. Post migration steps are either manual or automatic, meaning they are performed either by users or by Stat.

Post migration steps security is controlled by the following user class rights:

The Post Migration Steps Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Post Migration Steps.


If selected, activates the value in Stat

Post Migration Step
(Required Value)

The type of step. Options include Custom Command, Run DMS, Create Project Build Script, Compile Cobol, and Manual.

Step Name
(Required Value)

The name of the step

Object Class
(Key Value)

The class of object for which the step is defined. Options include data objects and file object for all three change management modules supported by Stat, as well as PeopleSoft Proprietary objects.

Object Type
(Key Value)

The object type the step is associated with (if any)

Target Env.

The target environment the step is associated with (if any)

Run Per

If selected, specifies that the step should be run only once for a particular CSR, migration, or target environment. This option is used to prevent a step from being run multiple times when it should be run only once. The default option is Migration.

(Required Value)

A number that determines per object type the sort order for the step on the post migration checklist. Steps with a lower number are displayed at the top of the list.

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user that who updated this record

Predefined Automatic Steps

Stat can execute three predefined, automatic post migration steps: Create Project Build Script, Compile COBOL, and Run DataMover Script.

When this step is triggered, Stat logs into the target PeopleSoft environment of the migration and creates the project build script for the project used during the migration. Stat uses the command line statement to launch PeopleSoft. It uses the PeopleSoft build settings from the Windows registry to generate the SQL script for create or alter. This step is applicable for PeopleSoft versions 8 and higher only.

When this step is triggered, Stat automatically launches the PeopleSoft COBOL Compile program, either CBLBLD for NT or pscbl.mak for Unix. When executing this step, Stat uses the following file server variables:

Except for the definition of the operating system, all of these settings can be changed at the time of execution.

When this step is triggered, Stat logs in to the PeopleSoft environment (by default, the target environment of the migration) using the user’s PS operator ID and password and runs the selected Data Mover script. By default, Stat uses the .dms file in the subdirectory “\script,” which is appended to the PeopleSoft Home Directory (PS_HOME) defined in the PeopleSoft Configuration Manager. All of these settings can be changed at the time of execution.

Defining a Custom Command

You can define automatic post migration steps in the form of custom commands. These are operating system commands executed by the client server Stat is running on. All drive mappings and file paths are relative to the client server.

In the Post Migration Step Maintenance window, click New and specify the object class and object type of the automatic step you want to create.
In the Automatic Post Migration Step field, select Run Custom Command.
Click Apply to save your work.
Click Define Command.


The current year, 2-digit format



The current year, 4-digit format



The current month, 2-digit format



The current day of month, 2-digit format



The current day of week



The current hour, 2-digit format



The current minutes, 2-digit format



The current seconds, 2-digit format



The target environment of the migration



The name of the PeopleSoft project used in the migration



The service domain that the CSR belongs to



The CSR ID number



The object type the post migration step is defined for


In the Command with parameters field, enter the command you want Stat to run.
(Optional) In the SSH time-out in seconds field, specify a longer connection timeout amount.
(Optional) Click Interpret Command.
The Interpreted Command field displays how the command is interpreted by the client/server. Be aware, however, that certain variables can only be resolved when the user opens the Command Editor window during a migration. When the Command Editor window is opened by a system administrator through the maintenance window, the following restrictions apply:
(Optional) Click Run Command.
NOTE: When the Command Editor window is opened by a system administrator through the maintenance window, the Run Command button is limited the same way as the Interpret Command button in terms of resolving certain types of variables. See the list of restrictions in the preceding step.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating