Set Up Parameterized Submissions

The Parameterized Submission process (PSUB) schedules and runs jobs, reports, and batch processing for Oracle Clinical. In order to support using Oracle Real Application Clusters (RAC), the implementation of PSUB changed in Oracle Clinical 5.0.

You must start one PSUB service for each Oracle Clinical database on the same server as the database.

For more information, see:

• Create Directories and Enter Values in OCL_STATE Local Reference Codelist
  
• Enable Users to Submit PSUB Jobs
  
• Enable opapps to Use the at Command
  
• Start the PSUB Service
  
• Customize the PSUB Service (Optional)
  
• Test the PSUB Installation
  

Create Directories and Enter Values in OCL_STATE Local Reference Codelist

1. Create several directories on the PSUB server.
2. Enter paths of the new directories in the OCL_STATE local reference codelist, with a few related values.
   See the "Setting Up Batch Job File Viewing" section of the "Setting Up File and Image Viewing" chapter of the Oracle Clinical Administrator's Guide for more information.

Note:

See Integrate SAS (Optional) for information about new OCL_STATE settings related to SAS configuration.

Enable Users to Submit PSUB Jobs

Beginning in Release 5.0, PSUB users no longer need:

• their own OS account
• a user name beginning with OPS$
• their own directory for PSUB outputs under their own OS account home. (Instead PSUB outputs are stored temporarily in a user specific directory under PSUB root folder specified inPSUB_LOGS_DIR entry of the OCL_STATE local reference codelist. Then they are uploaded into database and can be viewed.)

New Users

To add new users:

1. Use the ocl_add_user.sql script, indicating which new users need to run PSUB jobs.

   See the Oracle Clinical Administrator's Guide for more information.

Existing Users

If you are upgrading from a pre-5.0 version of Oracle Clinical, to give users who need to run PSUB jobs access to the opapps account:

1. Use the migration script oclupg50migrateusers.sql.
   See the Oracle Clinical Administrator's Guide for more information.

PSUB Administrator User

You can give a user the role RXC_VWJOBS (new in 5.0) to allow him or her to:

• View all users' jobs
• View the output from those jobs.
• Stop any job.

The following scripts can grant this role to a user:

• ocl_add_user—Use this script for new users.
• ocl_grant_revoke_rxc_vwjobs.sql—Use this script for existing users. (This script can also be used to revoke the role.)

See the Oracle Clinical Administrator's Guide for more information.

Enable opapps to Use the at Command

To use the at command to schedule jobs on behalf of another user, the owner’s user account must be listed in the at.allow file. The owner is opapps.

To edit the at.allow file:

1. Change to the appropriate directory location depending on your operating system and open the at.allow file:
   • Oracle Linux x86-64: /etc/at.allow
   • Oracle Solaris SPARC: /usr/lib/cron/at.allow
   • HP-UX Itanium: /usr/lib/cron/at.allow
2. Add the following line to the at.allow file:
   opapps

Start the PSUB Service

The Installer automatically installs the PSUB service on the database server. You must start it using on set of instructions below.

Instructions for stopping PSUB manually are included in the Oracle Clinical Administrator's Guide.

To start the PSUB service on UNIX:

1. Log in as the opapps user. By default, the opapps uses the C shell.
2. Set up the environment:

   opa_setup <database_name> <code_environment>
   

   For example, where prod is the database name:

   opa_setup prod 54

3. Go to the PSUB location:
   cd $RXC_PSUB
4. Start the PSUB service:
   start_psub database_name code_environment wallet_alias

   For PSUB, wallet_alias is the same as the database name. For example:

   start_psub prod 54 prod

   where prod is the connect string for the database instance to which the PSUB service connects;

   where 54 is the name of the code environment;

   where wallet_alias is the name of the Wallet specified during installation. By default it is the same as the database name.

5. If there are any errors, check the following log files in the $RXC_CENTRAL_LOG directory:
   • rxcpsd_instance_environment_1.log
   • rxcpsd_instance_environment_2.log

Customize the PSUB Service (Optional)

1. Customize the PSUB service as follows:
   • Automatic Startup — By default, the PSUB service does not start automatically when you restart a server computer. However, you can configure the PSUB service to start automatically.
   • Job Numbering — You can change Oracle Clinical's default job numbering algorithm.

For more information about managing and customizing the PSUB service, see the Oracle Clinical Administrator's Guide.

Test the PSUB Installation

To test your PSUB installation:

1. Open Oracle Clinical.
2. Submit a 3GL job such as Batch Validation or a PL/SQL job such as Study Unfreeze.
3. Verify that Oracle Clinical creates the log and output files by clicking on the View log and View output buttons.

If you encounter problems or errors, review the messages in the PSUB log files created in the following directory:

$RXC_ROOT/log