1. Upgrade Guide
  2. Set Up the Parametrized Submission Process
  3. Set Up PSUB

Set Up PSUB

The following steps are required to set up the parametrized submission process:

Parent topic: Set Up the Parametrized Submission Process

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 Set Up SAS for information about new OCL_STATE settings related to SAS configuration.

Parent topic: Set Up PSUB

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.

Parent topic: Set Up PSUB

Enable opapps to Use the at Command (UNIX Only)

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: /usr/lib/cron/at.allow
  2. Add the following line to the at.allow file:
    opapps

Parent topic: Set Up PSUB

Set Up Active Directory (Windows Only)

If you are running PSUB on a Windows server that is a primary domain controller running Active Directory:

  1. Add the PSUB account (typically opapps) to the domain.
  2. Reassign the following domain user privileges to the PSUB account, through the domain controller security policy and the domain security policy:
    • Load and unload device drivers
    • Act as part of operating system
    • Increase Quotas
    • Log on as a Service
    • Replace a process-level token

Parent topic: Set Up PSUB