ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Does Endevor have a utility to report on ELIB datasets integrity?

book

Article ID: 200211

calendar_today

Updated On:

Products

Endevor Software Change Manager (SCM) Endevor Software Change Manager - Natural Integration (SCM) Endevor Software Change Manager - ECLIPSE Plugin (SCM) Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

Is there an Endevor Utility report  that will or can identify if ELIBs are not allocated correctly and/or check the integrity of the file and members? 

 

 

Environment

Release : 18.1 18.0 

Component : CA Endevor Software Change Manager

 

Resolution

Use the ANALYZE option to validate the integrity of specified ELIB data sets. To do this code the INQUIRY statement with the ANALYZE option using the BC1PNLIB utility. The analysis verifies the integrity of each member in the directories and ensures that the allocation bit map is valid. Damaged members, if any, are identified, as are misallocated pages. The ANALYZE function must run in dedicated mode, and locks the library while sweeping it.

To verify the integrity of an ELIB library, use JCL and control statements similar to the following sample

//STEP1     EXEC PGM=NDVRC1,PARM=BC1PNLIB       

//STEPLIB   DD DISP=SHR,DSN=YOUR.V181.CSIQAUTU   

//          DD DISP=SHR,DSN=YOUR.V181.CSIQAUTH   

//CONLIB    DD DISP=SHR,DSN=YOUR.V181.CSIQLOAD   

//BSTERR   DD SYSOUT=*                          

//SYSPRINT DD SYSOUT=*                          

//SYMDUMP  DD DUMMY                             

//SYSUDUMP DD DUMMY                             

//ELIB     DD DISP=SHR,DSN=YOUR.ELIB.DELTA.FILE 

//SYSIN    DD *                                 

 INQUIRE  DDNAME=ELIB                                     

 OPTION ANALYZE  .                        

The report produced by the analyze function can contain the following messages:

*** ORPHAN: MEMBER= PAGE= NEXT= PREV= STAMP= BYTES USED=

The page or range of pages in the message are marked as occupied in the allocation bit map, but are not associated with any members in the data set header, allocation map, or directory pages.

*** MEMBER= STAMP= PAGE= FOUND MEMBER= STAMP=

Part of the member identified in the MEMBER=, STAMP=, and PAGE= fields has been overlaid by the member identified in the FOUND MEMBER= and following STAMP= fields.

*** MEMBER= STAMP= LIDPAGES= ACTUAL PAGES=

The member identified in the MEMBER= and STAMP= fields is listed in the directory as occupying the number of pages in the LIDPAGE= field, but the analysis utility has determined that it actually occupies the number of pages in the ACTUAL PAGES= field.

*** PAGE= OF MEMBER= IS FREE. NEXT= PREV= STAMP= BYTES USED=

The allocation map shows the named page to be free, but the directory associates the same page with the member identified in the MEMBER= and STAMP= fields, and shows that the page contains the number of bytes in the BYTES USED= field. The immediately preceding and subsequent pages in the directory are shown in the PREV= and NEXT= fields. The location of the directory entry with this information is shown in a message like this sample:

*** E-LIB DIR CHUNK= 1ST PAGE

For more information on Endevor Elibs you can view the documentaiton:

v18.0:  https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-0/administrating/setting-up-elib-data-sets.html

v18.1:  https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-1/administrating/setting-up-elib-data-sets.html