PXM1046 XMANAGER ERROR GROUP xxxxxxxx HIGHEST ACTV LVL SET 20.0.00 IS LESS THAN XMAN HIGHEST ACTV LVL 20.0.10 XMID=nnnn
Article ID: 402511
Updated On:
Products
Issue/Introduction
During a disaster recovery exercise, the Xmanager started tasks for the Database Management Solutions for Db2 for z/OS tools on LPAR 1 failed to start after the IPL and received the following error:
PXM1046 XMANAGER ERROR: GROUP xxxxxxxx HIGHEST ACTV LVL SET 20.0.00 IS LESS THAN XMAN HIGHEST ACTV LVL 20.0.10 XMID=nnnn
Questions:
1) How can this problem be fixed automatically after IPL?
2) Why did this error occur for the Xmanager started tasks on LPAR 1 but not for the Xmanager started tasks on LPAR 2?
Resolution
Reviewing the provided Xmanager log, the problem is that the Level Set list structure CADBT_LVLSET_001 on LPAR 1 is defined and allocated, see message PXM1131.
It also contains information for group xxxxxxxx. The group entry for xxxxxxxx in the list structure has the highest active level set 20.0.00, see PXM1046 message.
The Xmanager configuration file hlq.lpar.Nnnnn.PXMCNFG contains the highest active Level Set for the Xmanager. The group highest active Level Set must be greater
than or equal to the Xmanagers highest active Level Set for the Xmanager to start. If it is not, message PXM1046 is issued and the Xmanager will terminate. It appears
that the Level Set list structure was previously used and still allocated from a prior use of the disaster recovery Sysplex.
To migrate and start properly on a disaster recovery LPAR the following steps are recommended:
1. Migrate the Xmanager configuration files to the disaster recovery LPAR.
2. Make certain the Level Set list structure is defined and empty (deallocated) before starting any Xmanager tasks that will use the list structure.
The "SETXCF FORCE, STRUCTURE, STRNAME=CADBT_LVLSET_001" command will deallocate the list structure.
3. Start the Xmanagers that use the list structure. The information in the Xmanager configuration file will be used to populate the Level Set list structure with the correct information.
The Xmanager log from LPAR 2 displayed the following details:
1. PXM1131 message that states that the Xmanager allocated the Level Set list structure CADBT_LVLSET_001.
2. PXM1040 message showing that the group entry and Xmanagers entries were added to the list structure.
The group active Level Set and highest active Level Set were set in the list structure using the Xmanagers active Level Set and highest active Level Set from the Xmanager configuration file.
3. PXM10000 message shows the desired active level set 20.0.10
Upon review of the four Xmanager started tasks from LPAR 2 the following was noted:
PXM1000 XMANAGER LEVEL SET STATUS: ACTIVE=20.0.10 MAINT=20.0.10 HIGHEST ACTIVE=20.0.10 HIGHEST MAINT=20.0.10 XMID=nnnn
PXM1131 XMANAGER CF LIST STRUCTURE CADBT_LVLSET_001 HAS BEEN ALLOCATED XMID=nnnn xxxxxxxx ' WAS ADDED XMID=nnnn
PXM1001 ENVIRONMENT INITIALIZATION FOR XMANAGER CONFIGURATION FILE HAS STARTED HAS STARTED XMID=nnnn
PXM1003 XMANAGER CONFIGURATION FILE DD=hlq.lpar.Nnnnn.PXMCNFG WILL BE USED.
PXM1040 XMANAGER COUPLING FACILITY LIST 0 ENTNM='nnnnnnnn ' WAS ADDED XMID=nnnn
The Xmanagers started successfully on LPAR 2 because the Level Set list structure was not allocated and the Level Set details were populated from the Xmanager configuration files.
The Xmanagers failed to start successfully on LPAR 1 because the Level Set list structure existed with sale data.
The "SETXCF FORCE, STRUCTURE, STRNAME=CADBT_LVLSET_001" command must be used to deallocate the list structure.
Feedback
