Activating the XMANAGER Level Set For Single Xmanager

Products

• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - Administration Suite
• Database Management for DB2 for z/OS - Recovery Suite
• Database Management for DB2 for z/OS - SQL Performance Suite
• Database Management for DB2 for z/OS - Utilities Suite
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

After installing the Release 20.0 of the product and then applying additional maintenance which included PTF LU01290 concerning activation of the "LEVEL SET" of my XMANAGER task. How to activate the new level set which is 20.0.01? This is not a SYSPLEX (It's a single XMANAGER on a single stand-alone production LPAR). Here is the response to the ACTIVATE LEVELSET command:

PXM0107 MODIFY TEXT = ACTIVATE LEVELSET(20.0.01)                                
PXM1100 XMANAGER ACTIVATE COMMAND PROCESSING BEGINNING                          
PXM1107 XMANAGER CF LIST STRUCTURE MUST BE DEFINED AND ALLOCATED AT STARTUP FOR THE ACTIVATE COMMAND
PXM1190 XMANAGER ACTIVATE COMMAND PROCESSING COMPLETE   

This is confusing as the  customization documentation states: "A coupling facility list structure is needed only when you group Xmanagers together in a sysplex environment". I did create and allocate an XMANAGER configuration file via DD PXMCNFG. 

These are the messages seen in the XMANAGER log:

PXM1029 XMANAGER ERROR OCCURRED QUERYING CF FOR THE CF LIST STRUCTURE RC=X'0C' RSN=X'00000144'  XMID=0002
PXM1026 XMANAGER CF LIST STRUCTURE CADBT_LVLSET_001 IS NOT DEFINED   XMID=0002
PXM1025 XMANAGER CONFIGURATION FILE LEVEL SET RECORD WAS NOT UPDATED. XMID=0002 
PXM1000 XMANAGER LEVEL SET STATUS: ACTIVE=20.0.00  MAINT=20.0.01  HIGHEST ACTIVE=20.0.00  HIGHEST MAINT=20.0.01                  PXM1023 ENVIRONMENT INITIALIZATION FOR XMANAGER LEVEL SET PROCESSING HAS COMPLETED                                                         Is it important to activate this new level set 20.0.01? 

 

     

Environment

Release : 20.0

Component : Execution Manager

Resolution

The problem was caused by XSYS=Y parm in a single Xmanager. Turning this parm off(XSYS=N) resolves the problem. The following can be read in the xmanager comment:

2) **Supply a value for XSYS. A value of 'Y' will enable Xmanager cross-system communication support. A value  of 'N' will start the Xmanager with cross-system  **                   **  communication support disabled. Cross-system communication support can only be enabled for those LPARS that are members of a sysplex complex.          **                 *** The default value for XSYS is 'Y'***