Topic
  • 6 replies
  • Latest Post - ‏2013-11-06T16:18:39Z by zGuy
zGuy
zGuy
5 Posts

Pinned topic DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

‏2013-11-05T18:09:48Z |

I am working on a RDT instance and continue to get " DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO

     * IEF238D" displayed in the MVS console. 

 

Looking into the log of DBGMASTR .. I've found:

11.27.14 STC00723  IEF244I DBAGMSTR DBAGMSTR - UNABLE TO ALLOCATE 1 UNIT(S)  876         

   876                     AT LEAST 1 OFFLINE UNIT(S) NEEDED.                            

11.27.14 STC00723  IEF877E DBAGMSTR NEEDS 1 UNIT(S)  877                                 

   877             FOR DBAGMSTR SYS00010                                                 

   877             FOR VOLUME PRIVAT-   1                                                

   877             OFFLINE, NOT ACCESSIBLE                                               

   877             0AA3                                                                  

 

My initial attempts were to try to being AA3 online. However this isnt even a device im using in the devmap. I was not confident this would solve my problem, and it did not, as the console explained the volume "HAS NO LOGICAL PATH"

Any insight or help would be appreciated. 

Thanks,                     

 

 

 

  • RDzJohn
    RDzJohn
    272 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-05T18:19:46Z  

    Check your device map file and see which volume is mounted on device AA3.  It should be volume PRIVAT.  Make sure this volume is good by using an alcckd command as follows:   alcckd /yourdir/PRIVAT -rs  If it doesn't come back as good, you will need to recreate it.

     

    RDzJohn

  • zGuy
    zGuy
    5 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-05T20:16:02Z  

    Hi John, 

    Appreciate the response. My thoughts were the same, however there is no reference to either the device or volume "PRIVAT". Excuse my error, as this is not RDT but zPDT (April 2013 Dist). 

    While I understand these are not the same products, they do share the devmap structure in common. 

    Devices and Volumes specific to DB2 v10 are followed:
    device 0AB1 3390 3390 /home/zos/1303/fddba1.bin
    device 0AB2 3390 3390 /home/zos/1303/fddba2.bin
    device 0AB3 3390 3390 /home/zos/1303/fddba3.bin
     

    Any ideas how this is getting the AA3 device or where this could be coming from?

  • RDzJohn
    RDzJohn
    272 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-05T20:21:24Z  
    • zGuy
    • ‏2013-11-05T20:16:02Z

    Hi John, 

    Appreciate the response. My thoughts were the same, however there is no reference to either the device or volume "PRIVAT". Excuse my error, as this is not RDT but zPDT (April 2013 Dist). 

    While I understand these are not the same products, they do share the devmap structure in common. 

    Devices and Volumes specific to DB2 v10 are followed:
    device 0AB1 3390 3390 /home/zos/1303/fddba1.bin
    device 0AB2 3390 3390 /home/zos/1303/fddba2.bin
    device 0AB3 3390 3390 /home/zos/1303/fddba3.bin
     

    Any ideas how this is getting the AA3 device or where this could be coming from?

    This is not a DB2 error.  The DBAGMSTR job is looking for some space.  Your VATLSTxx probably points to the PRIVAT volume which it thinks is at device AA3.  Since it isn't there, allocation gives you its standard IEF877E message.  Bottom line is you need to make some space available on your system.

     

    RDzJohn

  • RDzDoug
    RDzDoug
    5 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-05T20:25:22Z  
    • zGuy
    • ‏2013-11-05T20:16:02Z

    Hi John, 

    Appreciate the response. My thoughts were the same, however there is no reference to either the device or volume "PRIVAT". Excuse my error, as this is not RDT but zPDT (April 2013 Dist). 

    While I understand these are not the same products, they do share the devmap structure in common. 

    Devices and Volumes specific to DB2 v10 are followed:
    device 0AB1 3390 3390 /home/zos/1303/fddba1.bin
    device 0AB2 3390 3390 /home/zos/1303/fddba2.bin
    device 0AB3 3390 3390 /home/zos/1303/fddba3.bin
     

    Any ideas how this is getting the AA3 device or where this could be coming from?

    In the readme notes there is  section on a new esoteric called DBARCH which is used for DB2 .  There are instructions for adding volumes to that esoteric and I believe that is where the reference for AA3 is coming from.  If you have the readme, take a look at that under the section "Allocating DB2 archive logs into an esoteric device".  I don't have a sys to test this on and I'm no HCD expert, but this looks like the right direction to pursue.

  • zGuy
    zGuy
    5 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-05T20:33:24Z  

    Thanks guys, ill check it out!

  • zGuy
    zGuy
    5 Posts

    Re: DBAGMSTR DBAGMSTR IS WAITING FOR A REPLY TO * IEF238D

    ‏2013-11-06T16:18:39Z  
    • RDzJohn
    • ‏2013-11-05T20:21:24Z

    This is not a DB2 error.  The DBAGMSTR job is looking for some space.  Your VATLSTxx probably points to the PRIVAT volume which it thinks is at device AA3.  Since it isn't there, allocation gives you its standard IEF877E message.  Bottom line is you need to make some space available on your system.

     

    RDzJohn

    Hi John,

     

    Is there a resource you would suggest that would explain the process of allocating more space to the system. I have generated additional volumes, would this be as simple to add to the VATLST?

     

    Thanks,