IBM-WebSphere-Message-Broker-V8-0-System-Administration-(000-277).pdf - IBM 000-277 IBM WebSphere Message Broker V8.0 System Administration

IBM-WebSphere-Message-Broker-V8-0-System-Administration-(000-277).pdf

This preview shows page 1 - 3 out of 6 pages.

000-277 IBM IBM WebSphere Message Broker V8.0 System Administration
Image of page 1
Answer: A QUESTION: 48 A system administrator upgraded the WebSphere Message Broker runtime to the latest Fix Pack. After the upgrade, when the system administrator tries to start the broker BRK1, one of the execution groups EG1 does not start. The broker repeatedly shows BIP2060W in the broker syslogs on that execution group. The system administrator checked the install logs and finds that the Fix Pack was installed successfully. The system administrator searches the web for any known problems, but does not find any hits. The system administrator decides to capture a startup trace on the execution group to see if any diagnostic information can be detected. What should the system administrator do to initiate the trace? A. Enable trace from Toolkit B. mqsiservice -v C. mqsireadlog BRK1 -t -e EG1 -f -o trace.xml D. mqsichangetrace BRK1 -t -e EG1 -l debug -r Answer: D QUESTION: 49 A broker running on a UNIX box crashes for which a system administrator raises a ticket with IBM Support. The IBM Support team asks the system administrator to collect the diagnostic documents to investigate further. To do so, which command should the system administrator run?
Image of page 2
Image of page 3

You've reached the end of your free preview.

Want to read all 6 pages?

  • Fall '20
  • Middleware, IBM WebSphere, IBM WebSphere Message Broker

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture