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.

When starting my CA Datacom Multi-User Facility (called MUF), I received an error with RC 60(146) about my Log file (LXX).

book

Article ID: 19029

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 starting my CA Datacom Multi-User Facility (called MUF), I received some error messages with RC 60(146):

DB02405I - PXX START 0 60(146) OPEN -0- D-1
DB02406I - PXX END - INVALID LOG CONTROL BLOCK
DB00501E - OPEN ERROR - RETURN CODE 60 (146) CXX=cxxname (LXX )

What do these errors mean, and how do I fix them?

Solution:

The RC 60(146) has this explanation:

Explanation: INVALID LOG CONTROL BLOCK
User Response: There is a JCL error or an INIT is needed.


What this means is that when the MUF opened the Log(LXX) file, it tried to validate control information in the file, but the control information was not what was expected. This could be the result of:


  1. Allocating the LXX file, but not running the INIT command;
  2. Using the wrong file/filename for the LXX;
  3. Some other program overwrote the LXX file with the wrong data.

If LXX is actually using the correct file/filename, in order to correct this, you will need to run a job to initialize (INIT) the LXX. Here is a z/OS sample for version 14.0:


//LXXINIT  EXEC PGM=DBUTLTY,REGION=6M
//         INCLUDE MEMBER=B14STLIB
//         INCLUDE MEMBER=B14DDOUT
//LXX      DD  DISP=SHR,DSN=your LXX file
//SYSIN    DD  *
    INIT AREA=LXX,BLKSIZE=32760,TSN=00000001,VARIABLE=YES
/*

Please be sure that the LXX file name is correct here. If you are using version 14.0 and SIMPLIFY mode, and have coded a value for the DSN_XXX filemask, be sure that this file matches that filemask.

For more information about initializing the LXX, please refer to the CA Datacom/DB DBUTLTY Reference Guide, in the section "INIT CXX/FXX/IXX/LXX/WXX/Data Area › INIT LXX (Format Log Area)."
For more information about the SIMPLIFY feature, please refer to the CA Datacom/DB Database and System Administration Guide, in the section "Introduction › Simplify Feature."

As always, please contact CA Technologies support for CA Datacom if you have further questions.

Environment

Release:
Component: CA90S