DDL00281 in RC/Migrator analysis invalid INDEXBP
Article ID: 8790
Updated On:
Products
Issue/Introduction
RC/Migrator for Db2 for z/OS (RCM) - or Quick Migration - analysis ends with:
DDL00281: Invalid INDEXBP. The bufferpool name must be one of:
BP0, BP1, ..., BP49
MIGRATOR ANALYSIS COMPLETED, RETURN CODE = 8
Cause
If RC/Migrator cannot determine the Db2 version it will default to Db2 v8. As the index DDL contains BUFFERPOOL BP8K0 that triggers the DDL00281 error,
since BP8K0 was not valid in Db2 v8.
When creating the strategy online the target SSID must be entered correctly. If it does not exist in the hlq.CDBAPARM(SETUPxx) parmlib member the user
will be prompted for the target Db2 version. If omitted, RCM will use V11R1M0.
ENTER TARGET DB2 VERSION
SSID nnnn not found in PARMLIB. The DB2 version
cannot be determined. Please enter a DB2 Version:
Target Version ==> (V11R1M0 is the default)
However, in batch JCL, it is possible to edit or omit the PARMFILE option TRGSSID and TRGVERS. The problem can happen if:
- No target TRGSSID is specified (only possible in Quick Migration)
or
- the Target SSID does not exist in hlq.CDBAPARM(SETUPxx) and no TRGVERS is specified in the JCL PARMFILE
Resolution
Make sure the JCL contains either a TRGSSID that is defined in hlq.CDBAPARM(SETUPxx) or TRGVERS
Additional Information
Analysis Screens / DB2 SSID Specifications
Target SSID
Indicates the ID of the Db2 subsystem to which the objects are to be migrated. A valid Db2 SSID must be entered. If the specified target Db2 SSID does not exist in the parmlib, a window appears, letting you specify the version of Db2 for which the DDL is written. This version is inserted into the jobstream as TRGVERS. For a list of all valid SSIDs and their locations, enter a question mark (?).
Feedback
