CTHRESH member being loaded from the DATALIB on a SYSVIEW COLD start

Products

• SYSVIEW Performance Management

Issue/Introduction

Customer was having an issue with the CTHRESH member being pulled from the DATALIB on a COLD start, instead of the site parmlib.

According to the documentation, when START=COLD is specified in the start proc, then the threshold and states members should be pulled from the parmlib.

Resolution

When a START=COLD is specified in the SYSVIEW startup proc, the DATALIB copy of the CTHRESH and CSTATES members will be used if the CICSDATA parmlib member has an option of 'WARM' for CTHRESH and CSTATES.

Change the CICSDATA parmlib member to have the options be 'COLD' for CTHRESH and CSTATES to load the members from the Site library parmlib on SYSVIEW startup.