PT391E PARMLIB MEMBER RCQ NOT FOUND - DEFAULTS WILL BE USED

Products

• RC/Query for DB2 for z/OS

Issue/Introduction

After applying maintenance, users receive warning message PT391E when accessing RC/Query.

Environment

Release : 20.0

Cause

This change in behavior can be accounted for by the changes implemented with PTF LU08030 and the unification of Product Parmlib processing. Whenever a user tries to access a product, the STATUS command is automatically issued. If a product specific parmlib member does not exist then the results are displayed on the screen, informing the user that default values will be used. This is just a warning and needs no action. This PTF unified the behavior across all the Db2 tools.

So if no RCQ member exists in CDBAPARM, then when a user enters the RC/Query panels, warning message PT391E is issued and the STATUS results are displayed on the screen.

Resolution

To circumvent the issuing of these warning messages when a product specific Parmlib member does not exist, for example for RC/Query, you can do one of the following:

1. Access EP Edit Parmlib Members from the Products Main Menu and create a member with default values. The default values will automatically be populated when entering a particular product parmlib member. 

2. Create an RCQ member in CDBAPARM containing a single blank line.

Option 1, populating a new member with default values, is the recommended resolution.

Now, with the new RCQ Parmlib member, when a user enters the RC/Query panels the above messages will no longer be issued.