Append Run Control ID to Process Scheduler Output Files

Description

This code will take report files generated from process scheduler and append the run control id to the filename. Because most output is generated with the process name as the filename, adding the run control ID will help users understand the different sets of parameters that were used to generate it.

Here is what is contained in this project:

• An app engine program that will walk through the process scheduler process requests.
• It will determine the run control id of each process request from the appropriate table
• It will determine the current output file name, and then append the run control ID to the end
• It will rename the file using the OS API calls
• It will keep track of the maximum process instance it has run against.

Downloading the Project

Here is how you can download this project for your own use:

The current version of the PeopleTools objects can be installed in your environment using the following attachment . Here are the instructions for how the installers work. Also, at the bottom of this wiki page are attachments for the other revisions in the source code repository.

Any other objects can be downloaded directly from the pshome folder in the source tree

Bugs/Feature Requests

You can find the tickets for AppendRunCntlToFile here.

If you have any issues following along or find other problems (that are not already mentioned), you can create a new ticket (requires registration).

Source

You can browse through the source code here. A good place to start is the GS_REN_REPT PeopleCode. If you'd like to install the project locally in your own environment, an installer is attached at the bottom of this page.

Registered users can check out AppendRunCntlToFile from  here using Subversion.

Recent Changes

[15] by larry.grey on 2010/06/17 00:12:00

Initial code to look at parameters from run control tables.

[14] by larry.grey on 2010/06/17 00:04:58

New project AppendRunCntlToFile, created by larry.grey