ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexiSeries, OpenVMS, HP-NSSConnection to channel fails (upgraded OS from v7.1 to v7.3)

Post new topicReply to topic
Connection to channel fails (upgraded OS from v7.1 to v7.3) View previous topic :: View next topic
Author Message
GLaenen
PostPosted: Tue Apr 10, 2018 4:15 am Post subject: Connection to channel fails (upgraded OS from v7.1 to v7.3) Reply with quote

Newbie

Joined: 10 Apr 2018
Posts: 4

''
Since past weekend we encounter an issue with a failing channel immediatly after the connection is initiated (happens only on our PRODUCTION environment, while on TEST environment everything is running without any problems)

running MQ version 8 on iSeries
the past weekend the OS was upgraded from v7.1 to v7.3.

Since then the connection from a windows server to iSeries is no longer working (Connection to channel fails).

The following information is available from iSeries (none from the windows server).

The job AMQRMPPA indicated in red fails since the upgrade to OS v7.3.
In the first line present there, we see an error generated from serviceprogram LIBMQMR_R which is a part of the MQ package (and according to me the rootcause of the failure of the channel).
Failure happens during the connection initiation.

Any input would be greatly appreciated

Details from logging (level of Queue Manager)
Code:
04/10/18 10:47:00 - Process(553.1) User(QMQM) Jobname(854163/QMQM/RUNMQCHI  ) 
                    Host(PRODANTW.rze.de.db.com)                               
                    VRMF(8.0.0.8) QMgr(PRODANTW02)                             
                                                                             
AMQ9604: Channel 'PRODANTW02.CLIENT' terminated unexpectedly                   
                                                                             
EXPLANATION:                                                                   
                                                                               
  Cause . . . . . :   The process or thread executing channel                 
'PRODANTW02.CLIENT' is no longer running. The check process system call       
returned 545284357 for process 61504.                                         
  Recovery  . . . :   No immediate action is required because the channel entry
has been removed from the list of running channels. Inform the system         
administrator who should examine the operating system procedures to determine
why the channel process has terminated.                                       
                                                                             
----- amqxfddx.c : 877 -------------------------------------------------------
04/10/18 10:47:00 - Process(553.1) User(QMQM) Jobname(854163/QMQM/RUNMQCHI  )
                    Host(PRODANTW.rze.de.db.com)                             
                    VRMF(8.0.0.8) QMgr(PRODANTW02)                           
                                                                             
AMQ6184: An internal WebSphere MQ error has occurred.                         
                                                                             
EXPLANATION:                                                                 
                                                                             
  Cause . . . . . :   An internal MQ error has occurred on queue manager     
PRODANTW02 and the MQ error recording routine has been called. The failing   
process is process 553.                                                       
  Recovery  . . . :   Use the standard facilities supplied with your system to
record the problem identifier and to save any generated output files. Use     
either the MQ Support site:                                                   
http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant
(ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is 
already available.  If you are unable to find a match, contact your IBM support
center.  Do not discard these files until the problem has been resolved.       
  Technical Description . . . . . . . . :   None.                             
----- amqxfddx.c : 930 --------------------------------------------------------
04/10/18 10:47:00 - Process(553.1) User(QMQM) Jobname(854163/QMQM/RUNMQCHI  ) 
                    Host(PRODANTW.rze.de.db.com)                               
                    VRMF(8.0.0.8) QMgr(PRODANTW02)                             
                                                                               
AMQ9604: Channel 'PRODANTW02.CLIENT' terminated unexpectedly                   
                                                                               
EXPLANATION:                                                                   
                                                                               
  Cause . . . . . :   The process or thread executing channel                 
'PRODANTW02.CLIENT' is no longer running. The check process system call       
returned 545284357 for process 61504.                                         
  Recovery  . . . :   No immediate action is required because the channel entry
has been removed from the list of running channels. Inform the system         
administrator who should examine the operating system procedures to determine
why the channel process has terminated.                                       


Details from job AMQRMPPA
Code:

...
MCH3601 Esc 40 10:46:44  Pointer not set for location referenced.                                  10/04/18 LIBMQMR_R   LIBMQMR_R
                          Cause . . . . . :   A pointer was used, either directly or as a basing                                 
                            pointer, that has not been set to an address.                                                         
                          Thread  . . . . :   00003DEB                                                                           
*NONE   Inf    10:46:44  FDC  XY353001 -                                                           10/04/18 QP0ZCPA     QP0ZCPA   
                            xehAS400ConditionHandler (1077960969:15612:4:MCH3601:CPF9999:.)                                       
                          Thread  . . . . :   00003DEB                                                                           
CPF9861 Inf 00 10:46:44  Output file P000061504 created in library QMQM.                           10/04/18 QLIOUTFL    LIBMQMAS_R
                          Thread  . . . . :   00003DEB                                                                           
CPF9862 Inf 00 10:46:44  Member P000061504 added to output file P000061504 in                      10/04/18 QLIOUTFL    LIBMQMAS_R
                            library QMQM.                                                                                         
                          Thread  . . . . :   00003DEB                                                                           
CPF9861 Inf 00 10:46:44  Output file S000061504 created in library QMQM.                           10/04/18 QLIOUTFL    LIBMQMAS_R
                          Thread  . . . . :   00003DEB                                                                           
CPF9862 Inf 00 10:46:44  Member S000061504 added to output file S000061504 in                      10/04/18 QLIOUTFL    LIBMQMAS_R
                            library QMQM.                                                                                         
                          Thread  . . . . :   00003DEB                                                                           
CPD000D Inf 30 10:46:44  Command QSYS/DSPJOBLOG not safe for a multithreaded job.                  10/04/18 QCATRS      QC2SYS   
                          Cause . . . . . :   The current job is multithreaded, and command                                       
                            QSYS/DSPJOBLOG cannot be used safely in a multithreaded job. Action 2 will                           
                            be taken. Possible actions are: 2 -- Processing of the command will                                   
                            continue. 3 -- This message will be followed by escape message CPF0001.                               
                            Command processing will end. Recovery  . . . :   Do not attempt to run the                           
                            command in a multithreaded job. Technical description . . . . . . . . :                               
                            Commands that are not threadsafe should not be used in a multithreaded job.                           
                            Use the Display Command (DSPCMD) command to determine whether a command is                           
                            threadsafe and what action will be taken by the command analyzer if the                               
                            command is not threadsafe. If the multithreaded job action is *SYSVAL,                               
                            system value QMLTTHDACN is used to determine the action taken by the command                         
                            analyzer.                                                                                             
                          Thread  . . . . :   00003DEB                                                                           
CPC2191 Com 00 10:46:44  Object P000061504 in QMQM type *FILE deleted.                             10/04/18 QLIDLOBJ    QC2SYS   
                          Thread  . . . . :   00003DEB                                                                           
CPC2191 Com 00 10:46:44  Object S000061504 in QMQM type *FILE deleted.                             10/04/18 QLIDLOBJ    QC2SYS   
                          Thread  . . . . :   00003DEB                                                                           
CEE9901 Esc 30 10:46:44  Application error.  MCH3601 unmonitored by LIBMQMR_R at                   10/04/18 QLEAWI      QP0WPINT 
                            statement 0000000638, instruction X'0000'.                                                           
                          Cause . . . . . :   The application ended abnormally because an exception                               
                            occurred and was not handled.  The name of the program to which the                                   
                            unhandled exception is sent is LIBMQMR_R CMQXRSRV_R rriMQIServerCall. The                             
                            program was stopped at the high-level language statement number(s)                                   
                            0000000638 at the time the message was sent.  If more than one statement                             
                            number is shown, the program is an optimized ILE program.  Optimization does                         
                            not allow a single statement number to be determined.  If *N is shown as a                           
                            value, it means the real value was not available. Recovery  . . . :   See                             
                            the low level messages previously listed to locate the cause of the                                   
                            exception.  Correct any errors, and then try the request again.                                       
                          Thread  . . . . :   000000F0                                                                           
CPF1164 Com 00 10:46:44  Job 918202/QMQM/AMQRMPPA ended on 10/04/18 at 10:46:44;                   10/04/18 QWTMCEOJ    *EXT     
                            233,740 seconds used; end code 0 .                                                                   
                          Cause . . . . . :   Job 918202/QMQM/AMQRMPPA completed on 10/04/18 at 10:46:44                         
                            after it used 233,740 seconds processing unit time. The maximum temporary                             
                            storage used was 33 megabytes. The job had ending code 0. The job ended                               
                            after 1 routing steps with a secondary ending code of 0.  The job ending                             
                            codes and their meanings are as follows:  0 - The job completed normally. 10                         
                            - The job completed normally during controlled ending or controlled                                   
                            subsystem ending. 20 - The job exceeded end severity (ENDSEV job attribute).                         
                            30 - The job ended abnormally. 40 - The job ended before becoming active. 50                         
                            - The job ended while the job was active. 60 - The subsystem ended                                   
                            abnormally while the job was active. 70 - The system ended abnormally while                           
                            the job was active. 80 - The job ended (ENDJOBABN command). 90 - The job was                         
                            forced to end after the time limit ended (ENDJOBABN command). Recovery  . .                           
                            . :   For more information, see the Work management topic collection in the                           
                            Systems management category in the IBM i Information Center,                                         
                            http://www.ibm.com/systems/i/infocenter/.                                                 ;           

Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Apr 10, 2018 4:53 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25236
Location: Ohio, USA

Which version of MQ 8 are you running? The IBM site says you need to be on 8.0.0.4 to use i 7.3

I'd also check the kernel configuration between TEST and PROD - the error is complaining about threading models and (if my limited recollection of IBM i is correct) that's controlled at the OS level and sounds like the sort of thing that would be set differently between TEST and PROD.

Finally, and assuming you're 8.0.0.4 or higher, raise a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
GLaenen
PostPosted: Tue Apr 10, 2018 5:22 am Post subject: Reply with quote

Newbie

Joined: 10 Apr 2018
Posts: 4

Current version is V8.0.0.8 (p800-008-171121)

meanwhile a PMR is raised.
Back to top
View user's profile Send private message
GLaenen
PostPosted: Mon Apr 16, 2018 5:28 am Post subject: Reply with quote

Newbie

Joined: 10 Apr 2018
Posts: 4

As a final update:

issue is solved
rootcause was a wrong jar file on the calling server.
Error as described above is still present, but channel keeps in running state now after the connection is established.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexiSeries, OpenVMS, HP-NSSConnection to channel fails (upgraded OS from v7.1 to v7.3)
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.