Endevor element LL command returns "LIST MBR NOT FOUND"

Products

• Endevor

Issue/Introduction

After moving an element from stage 'D' to stage 'T' , getting "LIST MBR NOT FOUND" when doing an LL command.  Had no problems doing the LL command before the move.   Further checking found other elements in 'T' stage cannot be viewed either. 

The Move processor shows that the listing was successfully copied to the stage 'T' listing library -

   C1X0012I  STEP COPYLIST INVOKING PROGRAM CONLIST
   C1X0013I  PARM=COPY
   C1G0000I     DATA SET iprfx.iqual.T.LISTLIB
   C1G0000I     MEMBER XCMNT090
   C1G0132I  ELEMENT VVLL 0125 WRITTEN TO DATA SET
   C1X0010I  STEP COPYLIST PROGRAM CONLIST COMPLETED, RC=0000

Any ideas what is wrong?

Environment

Release : All Supported Releases

Resolution

A "LIST MBR NOT FOUND" normally indicates that the Listing library in the element's Component List is not pointing to the correct Listing library.  

1)  Run a PRINT ELEMENT with OPTION COMPONENTS: 

    //PRTCMPLS EXEC PGM=NDVRC1,DYNAMNBR=1500,         
    //         PARM='C1BM3000',REGION=4096K           
    //C1PRINT  DD SYSOUT=*                            
    //C1MSGS1  DD SYSOUT=*                            
    //SYSOUT   DD SYSOUT=*                                    
    //BSTIPT01 DD *                                   
      PRINT ELEMENT   'xxxxxxxx'                        
       FROM ENV       'xxxxxxxx'                            
            SYSTEM    'xxxxxxxx'                              
            SUBSYSTEM 'xxxxxxxx'                       
            TYPE *                                    
            STAGE *                                   
       OPTIONS COMPONENTS                           
      .                                                 
    /*

2)  In the ---  OUTPUT COMPONENTS  ---  section of the element's Component List report, verify the Listing library is correct for the stage the element was moved to.  In this example:  ENDV.STMF03.T.LISTLIB

• If the Listing library is still pointing to the previous Listing library, the Move processor needs to be updated to code MONITOR=COMPONENTS on the Output libraries of all the relevant copy steps.

See  How to Monitor Components in a Move Processor

From the doc:

"Should you want a move processor to replace the OUTPUT components of the existing component list with the new output components that are the result of the move processor, then MONITOR=COMPONENTS should be coded only on the OUTPUT files of the steps in the processor. When BC1PMVCL gets executed as the last step of the processor, it automatically replaces the existing OUTPUT components with the newly captured output components."

Also review the MLODNNL sample Move processor in the doc on how to code the MONITOR=COMPONENTS on the DD statements.

3)  To correct the element's current Component List, there are a couple of options:

• Regenerate the element at the current stage

• If regenerating is not an option, use the Search and Replace utility to update the element's component list and change the output data set names. Specifically see the  Update Output Data Set Name in Component List  section of the doc.

 

If the Listing library in the Component List report is correct, retain the Move processor output and the element's Component List report and open a case with Broadcom support.