ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Is CAMASTER Really Required for CA Datacom to Work?

book

Article ID: 19515

calendar_today

Updated On:

Products

Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD Disk Backup and Restore - MVS DISK BACKUP AND RESTORE- ADD-ON OPTIO DISK BACKUP AND RESTORE Ideal CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware

Issue/Introduction

Description:

When CAIRIM runs, the Program Call PC Routine, DBPCCPR initializes and then DBPCSPR initializes. If CAMASTER does not initialize successfully BEFORE CAIRIM begins, it is possible for DBPCCPR to be successful, but DBPCSPR to fail. If CA Datacom isn't defined to utilize XCF communications, it IS possible for the Multi-User Facility (MUF) to come up and run successfully even though CAMASTER isn't initialized.

Solution:

CA recommends that CAMASTER be initialized prior to running CAIRIM to initialize the Program Call PC routine, DBPCSPR. DBPCSPR runs in the CAMASTER address space to support special requirements, such as XCF communications, RRS for two-phase processing, running DBUTLTY from a non-APF authorized library. If CAMASTER fails to initialize, then DBPCSPR will fail to initialize and if the applications using CA Datacom are running in a different LPAR than the Multi-User Facility, the jobs will not run.

DBPCCPR, supports Datacom/DB and Datacom/AD 14.0 normal MUF requirements. CAIRIM installs DBPCCPR during the IPL process, or later. If DBPCCPR is not installed at the time of the first MUF execution, MUF dynamically does the install from the STEPLIB/JOBLIB that MUF is using.
DBPCCPR supports all MUF functions, basic DBUTLTY functions, and MUF user interface requirements.

Reference materials, CA Datacom/DB Database and System Administration Guide for 14.0, pages 165-166.

Even though CA recommends the CAMASTER be initialized prior to running CAIRIM to initialize both Program Call PC routine programs, DBPCCPR and DBPCSPR, it is possible for MUF to come up successfully if the applications using Datacom/AD are run locally and not in another LPAR.

See an example of errors you can get if this is the scenario:


  DB90150I - DATACOM DBCR4PR  2011/03/18-1055 14.0
  DB90154I - DATACOM DBPCCPR  2012/06/25-1213 14.0 RO47507
  DB90151I - DATACOM INITIALIZATION SUCCESSFUL
  CAS9130I - MODULE DBCR4PR  COMPLETE, RC=00
  DB90150I - DATACOM DBCR4PR  2011/03/18-1055 14.0
  DB90154I - DATACOM DBPCSPR  2012/06/25-1213 14.0 RO47507
  DB90155E - ERROR DEFINE RETCODE -036 RSNCODE 632
  DB90152E - DATACOM PARM SYNTAX ERROR (D)
  DB90153E - DATACOM INITIALIZATION FAILED 
  CAS9140E - INIT ERROR: CADATACOM            VER BD14, INIT ROUTINE
             RC=0008

Therefore, because most applications that use Datacom/DB or Datacom/AD communicate via XCF or likely will need the capability of residing in another LPAR than the MUF, we recommend that CAMASTER be initialized prior to running CAIRIM.

Environment

Release: DATABB00200-14-Datacom/AD
Component: