Endevor

  • 1.  ELIB REPORTING ON SPACE ISSUES

    Posted Dec 07, 2015 05:26 PM

    We have been running the following and am unable to produce reports on an Elib that we know has no space left:

         1.) BC1PNLST INQUIREs on our ELIBS

         2.) BCELIBRT to report any ELIBS that have space constrains on them.

     

    I am unable to get this ELIB to go through the report.  What are we doing wrong in our reporting?



  • 2.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 07, 2015 05:29 PM

    Is there anyone who knows how ELIBS work and how to get a report produced if they need adjustments? -I have looked at all the documentation I can find, but still have a lot of questions.



  • 3.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 08, 2015 12:15 PM

    Hi Christine,

     

    If you still have more questions, please share the exact error messages you are encountering (either here or with CA Support). The answer should fit the condition you are encountering....Best, Dana



  • 4.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 08, 2015 12:51 PM

    I am working on a different Production Problem unrelated to this right now.  Can I respond to you later?

     

    Christine Howe

    Highmark Health Services

    Mainframe System Support

    717 302-9735



  • 5.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 09, 2015 11:00 PM

    Yes, no problem.  We can discuss other options too, if you like.



  • 6.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 07, 2015 08:00 PM

    You might try:

     

    //*



  • 7.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 08, 2015 03:40 AM

    Hi Christine,

     

    The JCL you are running would help but BC1PNLST is the wrong utility program. It is BC1PNLIB that you need:-

     

    //NDVRELIB EXEC PGM=BC1PNLIB

    //ELIB     DD DISP=SHR,DSN=xxxxx.xxxx

    //SYSPRINT DD SYSOUT=*                       

    //BSTERR   DD SYSOUT=*                            

    //SYSUDUMP DD SYSOUT=*    

    //SYSIN    DD *                              

      INQUIRE  DDNAME=ELIB                       

      OPTION   ANALYZE                           

      .                                          

    /*                                           

     

    Stuart



  • 8.  Re: ELIB REPORTING ON SPACE ISSUES
    Best Answer

    Broadcom Employee
    Posted Dec 08, 2015 04:48 AM

    Hi Christine,

     

    Can you run :

    1 - IDCAMS LISTC against the ELIB.

    //LSTCVSAM EXEC PGM=IDCAMS                                    

    //ODD001   DD SYSOUT=*                                                                         

    //SYSPRINT DD SYSOUT=*                                        

    //IDD001   DD DISP=OLD,DSN=xxxxx.xxxx   

    //SYSIN    DD *                                               

    LISTCAT                                   -                  

    ENTRY(xxxxx.xxxx)   -                  

    OUTFILE(ODD001)                           -                  

    ALL                                                         

     

    2 - Follows Stuart's recommendation, ie:

    //NDVRELIB EXEC PGM=BC1PNLIB

    //ELIB     DD DISP=OLD,DSN=xxxxx.xxxx

    //SYSPRINT DD SYSOUT=*                       

    //BSTERR   DD SYSOUT=*                            

    //SYSUDUMP DD SYSOUT=*    

    //SYSIN    DD *                              

      INQUIRE  DDNAME=ELIB                       

      OPTION   ANALYZE                           

      .                                          

    /*    

     

    Let me know if this help to resolve your case.

     

    Regards,

    Ollivier 



  • 9.  Re: ELIB REPORTING ON SPACE ISSUES

    Posted Dec 08, 2015 06:49 AM

    Hi there,

     

    i made a REX/X running a full inquire for specified ELIBs. The REX/X analyses the inquire and gives me recommendations for a lib if necessary. e.g. free space becomes low, lib has directory overflows, lib has extents etc. I have another REX/X, getting the same input. This REX/X submits a job for every lib which needs reorganisation. You can use this REX/X to allocate new libs, too. You can use this REX/X to change the format of a lib (eg. from VSAM to BDAM, from VSAM to PDSE or whatever you like), too.

     

     

    Example:

    //WRNDLIBC EXEC PGM=IKJEFT01

    //SYSTSPRT DD  SYSOUT=*                                                  

    //ISPPROF  DD  DSN=&&PROFILE,DISP=(NEW,DELETE,DELETE),                   

    //             SPACE=(CYL,(1,1,20)),UNIT=SYSDA,                          

    //             DCB=(RECFM=FB,LRECL=80)                                   

    //ISPLOG   DD  DSN=&&LOG,DISP=(MOD,DELETE,DELETE),UNIT=SYSDA,            

    //             SPACE=(1,1)                                               

    //SYSEXEC  DD  DISP=SHR,DSN=your exec-libs

    //ISPPLIB  DD  DISP=SHR,DSN=your panel-libs

    //ISPMLIB  DD  DISP=SHR,DSN=your message-libs

    //ISPSLIB  DD  DISP=SHR,DSN=your skeleton-libs

    //ISPTLIB  DD  DISP=SHR,DSN=your table-libs

    //* ----------------------------------------------------------------- *  

    //SYSTSIN  DD  *                                                         

    ISPSTART CMD(%WRNDLIBC)                                                  

    //SYSIN    DD  *                                                         

    * ENTW                                                                   

    NDV.***1.DELTA     N B 4200 600 160000                           

    NDV.***2.DELTA     N B 3600 600 480000                           

    NDV.***1.BASE       N B 1000 200 108000                           

    NDV.***2.BASE       N B 1000 200 108000                           

     

    1. word is the name of the lib

    2. word is (Y/N) wether your're using LSERV

    3. word is the format of the lib: BDAM, VSAM, PDS or PDSE

    4. word is primary space in cylinder

    5. word is secondary space in cylinder

    6. word is the number of expected member for the lib

     

    Regards,

    Willi