VERIFIED SOLUTION i

How to automate the CODE-1 Plus database load process/add to a workflow environment on the Unix/Linux platform

Products Affected:  CODE-1 Plus
Operating System: Linux, Unix

 
Please follow these steps to configure and run the automated CODE-1 Plus database load process using the dbload.wf workflow process (attached).  These scripts can be used in a workflow environment or can be used as a standalone process. 
 
1. Copy the dbload.wf, dbload.config and dbload.set scripts to the CODE-1 Plus bin area.
 
2. Modify the dbload.config script and change the appropriate location for your site.

       a)  # Path to input files
 PBCDDIR=$PBC1P/data; export PBCDDIR
 For example: PBCDDIR=/g1/indb; export PBCDDIR
 
       b)  # Path to output files
 Note: The database output directory MUST be present and writable
 PBDBDIR=$PBC1P/data; export PBDBDIR
 For example: PBDBDIR=/g1/outdb`; export PBDBDIR

        c)  # Path to log file
             PBDBLOGDIR=$PBDBDIR; export PBDBLOGDIR
             For example: PBDBLOGDIR=/g1/outdb; export PBDBLOGDIR
 
Note: The default input and output database areas are the CODE-1 Plus data directory.  Change these for your input and output locations. The default log file destination is the database output directory ($PBDBDIR). For each optional file required change the switch from 0 to 1.
 
3.  Please be sure to create the output directory where the database files will be loaded.  If the directory does not exist, the database load will fail with a message in the                 $PBC1P/bin/dbload.log file.  If the output directory does exist, all logging messages will go to the dbload.log file that you specified with the $PBDBLOGDIR environment           variable in the dbload.config script.
 

4.  Run the dbload.wf script from the $PBC1P/bin directory:
./dbload.wf
 
Note: If you need to run these scripts from a different location other than the C1P bin area, you will have to put in the full path for the setup script found in the dbload.wf script.
 
5.  If the dbload.wf completes successfully, the script will end and return with a status zero (0) so it can be checked by your next workflow statement.
 
 

 
UPDATED:  December 8, 2017