Why is the BMC Parameter ICPRTF not recognized as a Global Parameter BY DBCOPY being invoked by DBA when run in CA Native Mode?

book

Article ID: 52829

calendar_today

Updated On:

Products

CA Distributed Database Management CA Database Analyzer for DB2 for Oracle CA Database Analyzer (IMS Tools) CA Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC CA Compress Data Compression (IMS Tools) CA Database Analyzer for IMS for z/OS CA Database Copier for IMS for z/OS CA Database Organizer for IMS for z/OS CA Mainframe Extended Terminal Manager (IMS Tools) CA High Performance Recovery for IMS for z/OS CA Database Organizer (IMS Tools) CA Mainframe Program Restart Manager for IMS for z/OS CA Secondary Index Builder for IMS for z/OS CA Secondary Index for IMS for z/OS

Issue/Introduction

Description:

After Global Parameter Processing begins the message IDI1105E UNDEFINED KEYWORD - "ICPREF" is produced.

Solution:

ICPREF is not a DBA keyword so putting it in the DBA global parameters will not work.

The IDIPARM DDname in a conventional job step points to a PDS whose members are distributed in our PARMLIB. Those members are specific to the functions of DBCOPY and DBA. When a job step has a IDIPARM DDname that is an in-stream set of control cards. Each function reads and interprets the statements for its own execution. The keyword ICPREF applies to DBCOPY but DBA does not recognize it and an error is produced.

To use global parameters the recommendation would be to find the PARMLIB dataset distributed with the products and point to it with IDIPARM DD. Customize the members DBCCOPY and DBAANALZ with any desired global parameters.

Environment

Release:
Component: DBA