Configuring thread history

Several parameters are required to configure PARMGEN.

About this task

For information about PARMGEN, see the Implementation scenarios in the IBM® Documentation.

Procedure

  1. Log into PARMGEN.
  2. Use the instructions in the "Customizing the configuration profiles" step in the implementation scenario to edit the LPAR RTE configuration profile in the RTE's %RTE_HILEV%.%RTE_NAME% dataset and enable the following thread history parameters:
    • Verify that KD2_PFnn_HIS_START is set to Y.
    • Set KD2_PFnn_HIS_STORE to the value that includes THVSAM. If other options (for example, VSAM, SEQ) are included, make sure to set the dependent parameters such as KD2_PFnn_HIS_LOGn.
  3. Set the following parameters to YES:
    • KD2_PFnn_THRDHIS_LOG_NUM
    • KD2_PFnn_THRDHIS_LOCK_CNTN
    • KD2_PFnn_THRDHIS_LOCK_SUSP
    • KD2_PFnn_THRDHIS_SCAN_SUMM
    • KD2_PFnn_THRDHIS_SORT_SUMM
    Note: These parameters can be configured in PARMGEN, but they are not yet implemented for use with thread history in the Enhanced 3270UI.
  4. Run the PARMGEN $PARSE and SUBMIT steps. The jobs that need to run will depend on your SMP/E maintenance and upgrade scenario. For example, you might just need to run the KCIJPW2R job, or you might need to run allocation jobs such as ALLOCDS, TCRV&dbid, and/or HCRV&dbid. Consult the IBM Documentation page on SMP/E maintenance and upgrade scenarios.
  5. Verify that the COPT&dbid file is generated correctly. Check that the THRD parameters are set according to the values you set in KD2_PFnn_THRDHIS_* in PARMGEN: 
    THRDLOG(7)
THRDDATASET(D01OMPE.VTS5815.DBA9.RKTH*)
THRDSQL(YES)
THRDCONT(YES)
THRDSUSP(YES)
THRDSCAN(YES)
THRDSORT(YES)
  6. Verify that all data sets mentioned in COPT&dbid member have been generated.