Tweet
Since v5.2 we had noticed, that the active QSYSOPR user is locking his message queue "*EXCL Lock exclusive no read". We have ICBS (Fiserv Banking Software) and one of the base programs is going to *MSGW. Fiserv technicians blame QSYSOPR *msgq for this, so now we are not signing in with this user. We are monitoring with different user for Inq messages, using only DSPMSGQ QSYSOPR. Does anybody had a similar problem? I'm not sure, QSYSOPR is causing the problem.
-
-
V5R2 QSYSOPR Message Queue
m.baramova wrote: > Since v5.2 we had noticed, that the active QSYSOPR user is locking > his message queue "*EXCL Lock exclusive no read". > We have ICBS (Fiserv Banking Software) and one of the base programs > is going to *MSGW. Fiserv technicians blame QSYSOPR *msgq for this, > so now we are not signing in with this user. We are monitoring with > different user for Inq messages, using only DSPMSGQ QSYSOPR. Does > anybody had a similar problem? I'm not sure, QSYSOPR is causing the > problem. We are at 5.2 and have never signed on as QSysOpr. We currently have an operator level user id sign on and perform a ChgMsgQ msgq(qsysopr) dlvry(*break) sev(51) every time it signs on. bill
Comment