Skip to Main Content
Return to Navigation

Enabling the Source-Delete Diagnostic Feature

The source-delete diagnostic feature is designed as optional, and you can activate it or deactivate it for each staging job in the following parameter file: HCM_HANDLEDETES_SETUP.txt.

Each staging job in the parameter file has the HANDLEDELETES value defaulted to 'N,' which means the source delete diagnostic logic will not execute when you run the staging jobs.

You can set the HANDLEDELETES value equal to 'Y' if you want your staging job to identify source deletes.

The HANDLEDELETES value is read every time the staging job runs and will execute according to your setting.

The following steps are required to implement and configure the source-delete diagnostic feature in the Campus Solutions warehouse staging jobs. These steps must be completed even if you do not plan to use the source-diagnostic feature.

  1. Copy the delivered parameter file, HCM_HANDLEDETES_SETUP.txt, to the same directory as the $PARAM_FILE_DIR environment variable.

    Note: The parameter files must be placed in the same directory as the $PARAM_FILE_DIR environment variable. If a staging job is not present in the parameter file, the HANDLEDELETES value is treated as 'N' at runtime.

  2. Open the parameter file and set the HANDLEDELETES value equal to 'Y' if you want the staging job to identify source deletes, or leave as 'N' if you do not want the staging job to identify source deletes.

  3. In IBM WebSphere DataStage Designer, open the job JC_DeleteStrat_SequentialRun.

  4. Click the Run button on the toolbar and in the Job Run Options window set the Source Category job parameter equal to HCM_OWS for HCM staging jobs.

  5. Click the run button.

    This job performs the initial setup required to implement the source-delete diagnostic feature, and only needs to be run once as instructed above.

    If you have activated the source-delete diagnostic feature for staging jobs, this job populates delete hashed files with data from their corresponding CRC hashed files.

    If you have deactivated the source-delete diagnostic feature for staging jobs, this job stores the job name and the job Start Date time in the hashed file. This data is used when a staging job is aborted.