Team,

The Web Sphere MQ in RDT installation continuously gives an error message "*IEF882E CSQ1MSTR CSQ1MSTR IS WAITING FOR A REPLY TO IEF238D". The problem seems to be storage related as its unable to allocate one of the file due to unavailable volume (as shown below). We are new to this Mainframe operations world. Can you help us in fixing this problem.

IKJ56221I DATA SET CSQARC1.CSQ1.B0000027 NOT ALLOCATED, VOLUME NOT AVAILABLE+
IKJ56221I VOLUME  NECESSARY TO SATISFY YOUR REQUEST NOT ON SYSTEM, AND CANNOT BE
IEF244I CSQ1MSTR CSQ1MSTR - UNABLE TO ALLOCATE 1 UNIT(S)  530
        AT LEAST 1 OFFLINE UNIT(S) NEEDED.
IEF877E CSQ1MSTR NEEDS 1 UNIT(S)  531
FOR CSQ1MSTR SYS00010
FOR VOLUME PRIVAT-   1
OFFLINE, NOT ACCESSIBLE
0300-0318
:
IEF878I END OF IEF877E FOR CSQ7MSTR CSQ1MSTR SYS00010
04 IEF238D CSQ7MSTR - REPLY DEVICE NAME OR 'CANCEL'.
IEF882E CSQ1MSTR CSQ1MSTR IS WAITING FOR A REPLY TO IEF238D 

What version of RD&T are you using?  What version of z/OS are you using?  What sysp did you use to ipl?  Is volume PRIVAT included in your devmap ?

RDzJohn

Hi John,

We are using RDT System z 9.0 product and z/OS Version 01.13

We have used IPL parm 0a82aw (all sub system warm start)

 We have also verified devmap file and do not see PRIVAT volume included. Also I can see PUBLIC, USER00, USER01 are included. Could you please explain list of values to be to be included to add the PRIVAT volume.

Thanks,

Gopal

Are you using the appliance?

RDzJohn

Hi John,

Yes, the directory is named appliance where we have the devmaps and zVolume placed. Hope that is what you would like to confirm.

Regards,

Gopal

We do not support the appliance through this forum.  You will need to contact the person that supplied your system to you.  My recollection is that the appliance provides a PRIVAT volume.  If it wasn't supplied as part of your appliance, that is likely your problem.

RDzJohn

I apologize for the misdirection.  I checked with our appliance team and it turns out this is not related to anything we've done in our appliance configuration.  It is a base configuration error with the MQ that you have on your system.  While we don't support the z/OS software stack through this forum and therefore can't provide detailed help for MQ, there are a couple of quick things you might try.  You could create a new volume named PRIVAT and add it to your devmap configuration.  Init it and vary it online and MQ should see it when it starts up.  The better way to fix this is to dig into the MQ configuration and see what it is looking for on PRIVAT and change the configuration so it looks elsewhere.

RDzJohn