Automatic steps consist of pre-defined commands executed by Stat. These include running DataMover scripts and any custom commands defined by your system administrator. For post migration steps, two additional automatic steps are compiling COBOL files and creating project build scripts.
For more information on automatic steps, see the book, Stat 5.5.0:System Administration, Chapter 5, “Service Domain-Specific Maintenance.”
To execute an automatic step, click Run. Depending on the step, Stat may prompt you to specify additional parameters.
Running Data Mover Scripts
When this step is triggered, Stat uses your PS operator ID and password to log in to the PeopleSoft environment (by default, the target environment of the migration) and runs the selected .dms file. Before executing the step, however, Stat displays the DataMover Variables dialog box. Here you can specify a different environment, which .dms file you want to run, and the location of the script files. For a default location, Stat appends the subdirectory “\script” to the PeopleSoft Home Directory (PS_HOME) defined in the PeopleSoft Configuration Manager.
The default script location is based on the registry entry for the version of PeopleSoft that you were last working in. If you are working with multiple versions of PeopleSoft, for example, 8.14 and 8.17, the default location is the 'current' entry in the registry. So, if you are migrating across PS 8.17 environments, but the current entry in the registry is for 8.12, then the entry for 8.12 is the default script location.
After specifying the variables you want, click Run to execute the step. You can run this step for each .dms file included in the migration, or you can run this step for the same file but in a different environment or script location.
Running Custom Command Migration Steps
Custom commands are operating system commands executed by the client server that Stat is running on. When a custom command step is triggered, Stat opens the Custom Command Variables window. Here you can edit the command by adding or replacing parameters as needed, or you can run the command directly.
When defining a command, system administrators can include predefined parameters and user and server-based parameters that have been defined in Stat. This provides a convenient way to specify values commonly invoked by operating system commands, such as server names and download directories. In addition, parameters offer a way to
secure sensitive information by encrypting values that you do not want visible to users, such as passwords.
Predefined parameters specify values used to login to a target environment during a migration (database name, user name and password), whereas user and server-based parameters generally invoke values specific to the users and file servers defined in Stat.
Also, certain parameters may be defined so that their values are different depending on which user or server they are being applied to. For more information on pre and post migration step parameters, see the book, Stat 5.5.0: System Administration, Chapter 4,
“General Maintenance Tables”.
To edit a custom command migration step:
1 In the Command with parameters field, enter the command you want Stat to run.
If you want to include parameters in the definition of the command, click the location where you want to insert the parameter and then double-click the parameter you want to insert. When included in a command, parameters are enclosed in double % signs, for example, “%%GL_PWD%%”.
Certain users and servers may have parameters that have been defined exclusively for them, or the value of a particular parameter may be different depending on which user or server it is being applied to. When the Stat Command Editor is first opened, the parameters are listed as they have been defined for the local client server and the current user. If you want to include parameters defined for a different server, click the Server field and select the server you want. Although you cannot select a different user in the User field, when a user executes the command when performing a pre or post migration step, they will have the option of inserting their own parameters or overriding default values.
2 If the command you want to execute opens a window, specify if you want the window minimized, maximized, or normal size.
This value is saved and used at run time.
3 Click Interpret >>.
The Interpreted Command field displays how the command is interpreted by the client server. Null values and encrypted values are enclosed in angle brackets.
Encrypted values are not displayed but replaced with asterisks.
4 (Optional) Verify that you defined the command properly by selecting the server you want to use to test the step in the Server field.
Note This is for testing purposes only. During execution of the step a user can select a different server.
5 Click OK.
Creating Project Build Scripts
The Create Project Build Script step is a post migration step applicable for PeopleSoft versions 8 and higher only. When this step is triggered, Stat uses your PeopleSoft operator ID and password to log into the PeopleSoft environment that is the target of the migration and creates the build script for the project that was used during the migration.
Stat uses the PeopleSoft command line statement to accomplish this and the build settings from the Windows registry to generate the SQL script for Create or Alter. The build script is placed in the location specified for build settings in your PeopleSoft configuration.
Compiling Cobol Files
When this post migration step is triggered, Stat automatically launches the PeopleSoft COBOL Compile program, either CBLBLD for NT or pscbl.mak for Unix. Your system administrator defines the default server and variables required to run the compiler. For Unix, these variables include the PeopleSoft home directory and the Cobol Compile directory. For Windows servers, these variables also include the drive and directory where the compile is to take place. If you want to specify a different server and variables, you can do so in the Cobol Compile Variables dialog box, which Stat opens when you click Run.
After specifying the variables you want, click Preview to see how the object will be compiled. If satisfied with the results, click Run to execute the step.