search cancel

CA7 MUF gets U0004 when using AL2MUFS1 member

book

Article ID: 204763

calendar_today

Updated On:

Products

Datacom DATACOM - AD Datacom/DB INFOCAI MAINTENANCE

Issue/Introduction

Installed Datacom/AD 15.1 for CA 7. Using the AXDATIN1 and AXDATIN2 members from Datacom/AD CUSMAC as SYSIN members, all works fine.

Replacing them with members AL2MUFS1 and AL2MUFS2 from CA 7 CAL2OPTN library, the MUF region cannot start:

DB00216E - ERROR IN SYSIN/SYSIPT DATA               
IEF450I CA7MUF AD15STRT - ABEND=S000 U0004 REASON=00000000 

Cause

The real error is the following:

08.09.58 STC03877 CA7MUF:DB01900I - *-------------------*OPTIONAL START-UP PARMS FOR AXDATIN1 --------------
08.09.58 STC03877 CA7MUF:DB01900I - XCF_FROM *,*,*,YES XCF RECEIVE FROM SYS, JOB, GROUP, ALLOW
08.09.58 STC03877 CA7MUF:DB01909E - * - ASTERISK POINTS NEAR ERROR
08.09.58 STC03877 CA7MUF:DB01911E - PARAMETER HAS INVALID VALUE

that triggers a:

08.09.58 STC03877 CA7MUF:DB00216E - ERROR IN SYSIN/SYSIPT DATA

at the end of the input cards.

In this specific case, the XCF_FROM card is considered invalid as the DBSIDPR macro (assembled on AXCUSNEW job, when running a new installation for Datacom/AD) is not set up to implement XCF connectivity.

Environment

Release : 15.1

Component : CA Datacom/AD

Resolution

Two possible solutions:

  1. If your MUF is running on a LPAR and a CA 7 address space running on a different LPAR needs to connect to this MUF, then you need to set up XCF connection as outlined on the "How to configure CA Datacom MUF for XCF use" article.
  2. If MUF and CA 7 are running on the same LPAR (so no XCF is required), you can comment the XCF_FROM card and change the 5th parameter in the TASKS card to 0; e.g. TASKS 500,60K,0,0,0