DUAS: "O_TYPE_MU name not found for ID" when using Logical Queues to submit Jobs
search cancel

DUAS: "O_TYPE_MU name not found for ID" when using Logical Queues to submit Jobs

book

Article ID: 199667

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

When launching Jobs via a Logical / Physical Batch Queue Architecture where the Submission Node has a Logical queue pointing to several Execution nodes with a Physical queue each.
The Jobs all start in a Management Unit called TLDTRAIT which points to the local node on each of them.

What occurs is that when Jobs run on an Execution Node where the ID (record on u_fxmu60.dta) of the Management Unit TLDTRAIT (T000000008) is different than the one of the Submission Server (T000000002) the following errors are logged in the Slave node upon each Uproc Execution:


|ERROR|X|IO |pid=p.t| xn_get_extended_name      | O_TYPE_MU name not found for ID <T000000002>
|ERROR|X|IO |pid=p.t| o_io_cache_data_provider_ | Error getting Name for <T000000002>: 600

This makes the universe.log unreadable but has no impact in the executions.

 

Environment

Release : 6.x

Component : DOLLAR UNIVERSE

Cause

Wrong Management Unit ID used on u_fmsb60.dta Execution Node.

Resolution

Workaround:

Ignore the error messages or create all the Management Units at the same time on all the Execution nodes sp that the Management Unit ID is the same everywhere.

In order to find out the Management Unit ID, launch the following command:

universe -getid -type MU -name THE_MU_NAME

 

Solution:

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Dollar.Universe.Application.Server
Dollar Universe 6.10.61 - Available