Generating Validation Procedures (gen_procs)

With the gen_procs utility you can convert existing Validation Procedures to 3.1-style, and regenerate them, on a per-study basis. Its use is not required, or necessarily recommended, for upgrades or new installations of Oracle Clinical.

This utility has the following syntax:

gen_procs { ALL | study_name } { FULL | INC } { CONVERT | GENERATE | PARSE } { 31 | 30 | ALL }

Choose one option from each set of qualifiers:

ALL | study_name— specifies the study you want to apply to. Enter either an individual study name or ALL to include all studies. This qualifier is not case-sensitive.

FULL | INC — specifies whether to perform full or incremental replication. You select FULL when running from the command line. INC is used when replication runs this command. This qualifier is case-sensitive.

CONVERT | GENERATE | PARSE — specifies the action you want to take. CONVERT works only for pre-3.1 Procedures; it converts the Procedure to 3.1-style, as well as generating and parsing as part of processing. PARSE works only with 3.1-style Procedures; it parses and recreates the package. GENERATE works for 3.0, 3.1, or ALL procedures; it also parses each package. PARSE and GENERATE are used primarily when the utility is called for replication.

31 | 30 | ALL — specifies the version of the Procedures to process.

LAGONLY | ALL —see the secton on lag variables in the chapter on creating Procedures in Oracle Clinical Creating a Study

The system creates a file named ora_errors.err in one of the following locations:

• If you specify a value for RXC_LOG, the system writes the error log to that directory.

• If you do not specify a value for RXC_LOG, the system writes the error log to the user's subdirectory under the directory specified in the PSUB_LOGS_DIRECTORY value in the OCL_STATE local reference codelist.

For more information , see:

• Running gen_procs on UNIX Systems
  
• Running gen_procs on Windows Systems
  

Running gen_procs on UNIX Systems

To run gen_procs on a UNIX platform:

1. Log on to the server as opapps.

2. Set environment variables for the database name and code environment; see Setting Environment Variables on the Command Line

3. Change the directory to $RXC_BIN.

4. Set the output directory (Optional):

   • C Shell command: setenv RXC_LOG usr_log_dir

   • Bourne Shell command: RXC_LOG=usr_log_dir export code_env

   If you do not specify a directory, the system places the files ora_errors.err and genprocs.log in the location specified as the value of PSUB_LOGS_DIR in the OCL_STATE local reference codelist.

5. Run the script. For example:

   gen_procs ALL FULL GENERATE ALL > gen_procs.log

   The system prompts for the database name and the username and password of any account that can execute a single procedure. You can use the RXC account.

   Oracle Clinical creates gen_procs.log in $RXC_BIN.

Running gen_procs on Windows Systems

To run gen_procs on Windows:

1. Log on to the server as opapps.

2. Set environment variables for the database name and code environment; see Setting Environment Variables on the Command Line

3. Set the output directory:

   set RXC_LOG=user_log_folder

4. Run the command file. For example:

   gen_procs ALL FULL GENERATE ALL > gen_procs.log

   The system prompts for the database name and the username and password of any account that can execute a single procedure. You can use the RXC account.

   Oracle Clinical creates genprocs.log in the current directory (%RXC_BIN%). Files ora_errors.err and genprocs.log are created in the RXC_LOG directory.