This suggests to me that perhaps CSQZPARM was enqueued by something, and the
started task idled out waiting for the enqueue to be released?

Try a 'd grs,c' perhaps?

Stabbing wildly in the dark,
Ian

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of P
Karthikeyan
Sent: Monday, 17 March 2003 21:08
To: [EMAIL PROTECTED]
Subject: MQSeries OS/390 QMGR Abend - CSQV086E - Reason 00E80100 -
Urgent



Hi,

Today we face the problem of queue managers getting abended with the
following error
messages:

 IEA995I SYMPTOM DUMP OUTPUT
 SYSTEM COMPLETION CODE=522
 TIME=15.21.01  SEQ=50409  CPU=0000  ASID=0045
  PSW AT TIME OF ERROR  077C1000   8DE01B1A  ILC 2  INTC 01
    ACTIVE LOAD MODULE           ADDRESS=0DE00F08  OFFSET=00000C12
    NAME=CSQYASCP
    DATA AT PSW  0DE01B14 - BF08AB0B  0A0194FE  90681F11
    AR/GR 0: 00000000/80000001   1: 00000000/0C3D41F8
          2: 00000000/FFFFFF7F   3: 00000000/80200080
          4: 00000000/00000000   5: 00000000/0C3D4000
          6: 00000000/00000000   7: 00000000/0BA2E040
          8: 00000000/0C3D41D0   9: 00000000/7F6F2690
          A: 00000000/8DE01008   B: 00000000/7F6F2560
          C: 00000000/0DE02007   D: 00000000/7F6F2560
          E: 8C74936E/00000000   F: 00000000/00000000
  END OF SYMPTOM DUMP
*CSQV086E +Q       MQSERIES ABNORMAL TERMINATION REASON=00E80100
 IEF450I MQZ1MSTR MQZ1MSTR - ABEND=S522 U0000 REASON=00000000
         TIME=15.21.11


On cheking the messages for CSQV086E & 00E80100,  it is stated that one of
the problem for
the could be that MQ unable to locate the CSQZPARM. But it is not the case.

The Queue manager comes up normally and stays active for around 30 mins ,
then abends with
the above mentioned error.

The environment is OS/390 V2R10 with MQ ver 2.1. This environment runs fine
for more than
1.5 years and we had not received this kind of problem. Also, we have not
applied any
maintainence recently  to suspect any problem related to maintainence.

Also, we face same problem in other subsystems in the LPAR.

We are suspecting that the problem could be due to TCPIP & WLM.

Have any one in the list faced similar problems? Any resolutions??

Thanks in Advance,
Karthik



***The information contained in this message is legally privileged and
confidential
information intended only for the use of the addressed individual or entity
indicated in
this message (or responsible for delivery of the message to such person). It
must not be
read, copied, disclosed, distributed or used by any person other than the
addressee.
Unauthorised use, disclosure or copying is strictly prohibited and may be
unlawful.
 Opinions, conclusions and other information on this message that do not
relate to the
official business of any of the constituent companies of the TATA
CONSULTANCY SERVICES
shall be understood as neither given nor endorsed by the Group. If you have
received this
message in error, you should destroy this message and kindly notify the
sender by e-mail.
Thank you.***

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to