fteShowLoggerDetails

Use the fteShowLoggerDetails command to display the details of a particular Managed File Transfer logger.


Purpose

You must run the fteShowLoggerDetails command on the same system as the logger. It displays the status of the logger process controller and the logger queue manager, which we can use to help with problem determination. The fteShowLoggerDetails command lists the following details for a particular Managed File Transfer logger:

  • Logger controller status.
  • Logger restarts within interval
  • Total logger restart count
  • Logger availability status
  • Logger queue manager name
  • Logger queue manager transport type
  • Logger queue manager last status reported (applies to binding transport mode only)

Specify the optional -p parameter for this command only if you want to use a set of configuration options different from your default set. See MFT configuration options on Multiplatforms for more information.

For a list of the possible logger status values and their meanings, see MFT logger status values.

For a list of the possible status values for the logger process controller and their meanings, see MFT logger process controller status values.

From IBM MQ Version 9.0.4, the output of the command displays connection information that the logger is using to connect to the queue manager.

If the logger is connected in clients mode, the output for:

    Last Status Reported
    Is shown as UNKNOWN

    Status details
    Is shown as Information about the queue manager is not available because the logger has a client connection to queue manager.


Syntax

fteShowLoggerDetails

fteShowLoggerDetails -p configuration_optionslogger_name


Parameter

    -p configuration_options
    Optional. This parameter determines the set of configuration options that is used to issue the request to display the details of an logger. Use the name of a non-default coordination queue manager as the input for this parameter. The command then uses the set of properties files associated with this non-default coordination queue manager.

    If we do not specify this parameter, the set of configuration options based on the default coordination queue manager is used.

    logger_name
    Required. The name of the Managed File Transfer logger that you want to display.

    -? or -h
    Optional. Displays command syntax.


Example

In this example, a started logger, issuing the fteShowLoggerDetails command locally to the logger:

fteShowLoggerDetails LOGGER1 
5724-H72 Copyright IBM Corp. 2008, 2020. ALL RIGHTS RESERVED
Logger Controller Information:
    Status:                              STARTED
    Status Details:                      The logger process controller has
                                         started the logger process.
    Logger Restarts within Interval:     0
    Total Logger Restart Count:          0

Queue Manager Information:
    Name:                                QM_gbthink
    Transport:                           Bindings
    Last Status Reported:                AVAILABLE
    Status Details:                      The queue manager is available.

In this example, a logger waiting due to an unavailable queue manager, issuing the fteShowLoggerDetails command locally to the logger:

fteShowLoggerDetails LOGGER2
5724-H72 Copyright IBM Corp. 2008, 2020. ALL RIGHTS RESERVED
Logger Controller Information:
    Status:                              WAITING
    Status Details:                      The logger process controller is
                                         waiting for the queue manager to
                                         become available before starting the
                                         logger.
    Logger Restarts within Interval:     0
    Total Logger Restart Count:          0

Logger Availability Information:
    Status:                              STOPPED
    Status Details:                      The logger has been stopped. It was
                                         shut down in a controlled manner.

Queue Manager Information:
    Name:                                QM_gbthink
    Transport:                           Bindings
    Last Status Reported:                UNAVAILABLE (Last Error MQRC: 2059)
    Status Details:                      The queue manager is unavailable. It
                                         might be that the queue manager has
                                         not been started or an incorrect
                                         queue manager name has been
                                         configured. Look up the MQ reason code
                                         reported against the status to
                                         understand the problem.

In this example on z/OS, a running logger (not registered with ARM):

fteShowLoggerDetails loggerv8
5655-MFT, 5724-H72 Copyright IBM Corp. 2008, 2020. ALL RIGHTS RESERVED
Logger Controller Information: 
    Controller Type:                     z/OS Automatic Restart Manager (ARM)
    Registered with ARM:                 No
    Restarted:                           n/a

Queue Manager Information: 
    Name:                                FT8E
    Transport:                           Bindings
    Last Status Reported:                AVAILABLE
    Status Details:                      The queue manager is available.

In this example on z/OS, a logger that is not running, or running on a different system:

fteShowLoggerDetails loggerv8
5655-MFT, 5724-H72 Copyright IBM Corp. 2008, 2020. ALL RIGHTS RESERVED
Logger Controller Information: 
    Controller Type:                     UNKNOWN

Queue Manager Information: 
    Name:                                FT8E
    Transport:                           Bindings
    Last Status Reported:                UNKNOWN
    Status Details:                      Information about the queue manager is 
                                         not available, either because the 
                                         logger is not running, or the logger 
                                         is running on a different system.


Return codes

    0
    Command completed successfully.

    1
    Command ended unsuccessfully.