fteStopDatabaseLogger (stop the stand-alone database logger)
The fteStopDatabaseLogger command stops the stand-alone database logger.
Purpose
The fteStopDatabaseLogger command is supported on WebSphere® MQ File Transfer Edition Version 7.0.1 and later.
Use the fteStopDatabaseLogger command to stop the stand-alone database logger. The stand-alone database logger is a stand-alone Java™ application that runs on the same system as the coordination queue manager and the database.Additional notes about stopping the stand-alone database logger
The fteStopDatabaseLogger command sends a message to the command queue used by the stand-alone database logger. If you run fteStopDatabaseLogger while the stand-alone database logger is not running, a command message is still placed on the queue. When the stand-alone database logger is next started, the logger immediately receives this command message, and shuts down. If you have issued many stop commands to a stand-alone database logger that is not running, you must repeatedly start the logger until all the stop commands have been consumed. Alternatively, you can clear the command queue to remove all pending commands.
If your stand-alone database logger is running as a Windows service, running the fteStopDatabaseLogger command stops the Windows service.
Some error conditions, typically accompanied by message BFGDB0038E, prevent the stand-alone database logger from reading commands. To stop a stand-alone database logger in this state, use your operating system facilities to end the process (for example, the UNIX kill command or the Windows Task Manager). The XA transaction protocol used by the stand-alone database logger ensures that no messages are lost when the process is ended.
Syntax
fteStopDatabaseLogger >>-fteStopDatabaseLogger--+----------------------------+--------> '- -p -configuration options-' >--+---------------------+--+---------------------+-------------> '- -qm -queue manager-' '- -cq -command queue-' >--+-----------------+----------------------------------------->< '-properties file-'
Parameters
- -p (configuration options)
- Optional. Determines the set of configuration options that is used to stop the stand-alone database logger. Use the name of a set of configuration options as the value for the -p parameter. By convention this value is the name of a coordination queue manager. If you do not specify this parameter, the default set of configuration options is used.
- -qm (queue manager)
- Optional. By default, the command queue used by the stand-alone database logger is assumed to be on the coordination queue manager specified by the -p parameter (or its default). If it is necessary to send stand-alone database logger commands to a command queue located elsewhere, the -qm parameter can be used to specify an alternative destination. In all cases, note that the command connects to the command queue manager implied by the -p parameter, regardless of the ultimate destination of the message.
- -cq (command queue)
- Optional. Specifies the command queue to which the stop message is sent. In most cases, stand-alone database loggers use the default queue name and this parameter is not necessary.
- properties file
- Optional. By default, the stand-alone database logger's properties file is assumed to be located in the coordination queue manager's directory. You can optionally supply your own fully qualified path to a properties file containing the required properties for the stand-alone database logger to run. If you specified a properties file for the fteStartDatabaseLogger command, specify the same properties file for this command.
- -? or -h
- Optional. Displays command syntax.
Example
In this example, a stand-alone database logger with command queue, FTE.LOGGER2.COMMAND on queue manager PLUTO, is stopped.fteStopDatabaseLogger -qm PLUTO -cq FTE.LOGGER2.COMMAND
Return codes
- 0
- Command completed successfully.
- 1
- Command ended unsuccessfully.