Sun Java System Messaging Server 6.3 Administration Guide

ProcedureTo Manually Start and Stop Channels

  1. Set the mm_debug=5 in the option.dat file in directory /msg-svr-base/config in order to provide substantial debugging information.

  2. Add the slave_debug and master_debug keywords to the appropriate channels in the imta.cnf file in directory /msg-svr-base/config.

    1. Use the slave_debug keyword on the inbound channel (or any channel where the message is switched to during the initial dialog) from the remote system that is sending the message with the message part. In this example, the slave_debug keyword is added to the tcp_local channel.

    2. Add the master_debug keyword to the other channels that the message passed through and were identified in Identify the Channels in the Message Path would be added to the conversion and tcp_intranet channels.

    3. Run the command imsimta restart dispatcher to restart the SMTP server.

  3. Use the imsimta qm stop and imsimta qm start commands to manually start and stop specific channels. For more on information by using these keywords, see 26.2.7 Starting and Stopping Individual Channels.

  4. To start the process of capturing the message files, have the end user resend the message with the message part.

  5. When the message enters a channel, the message will stop in the channel if it has been stopped with the imsimta qm stop command. For more information, see Step Step 3.

    1. Copy and rename the message file before you manually run the next channel in the message’s path. See the following UNIX platform example:

      # cp ZZ01K7LXW76T7O9TD0TB.00 ZZ01K7LXW76T7O9TD0TB.KEEP1

      The message file typically resides in directory similar to /msg-svr-base/data/queue/destination_channel/001. The destination_channel is the next channel that the message passes through (such as: tcp_intranet). If you want to create subdirectories (like 001, 002, and so on) in the destination_channel directory, add the subdirs keyword to the channels.

    2. It is recommended that you number the extensions of the message each time you trap and copy the message in order to identify the order in which the message is processed.

  6. Resume message processing in the channel and enqueue to the next destination channel in the message’s path. To do so, use the imsimta qm start command.

  7. Copy and save the corresponding channel log file (for example: tcp_intranet_master.log-*) located in directory /msg-svr-base/log. Choose the appropriate log file that has the data for the message you are tracking. Make sure that the file you copy matches the timestamp and the subject header for the message as it comes into the channel. In the example of the tcp_intranet_master.log-*, you might save the file as tcp_intranet_master.keep so the file is not deleted.

  8. Repeat steps 5 - 7 until the message has reached its final destination.

    The log files you copied in Step Step 7 should correlate to the message files that you copied in Step Step 5. If, for example, you stopped all of the channels in the missing message part scenario, you would save the conversion_master.log-* and the tcp_intranet_master.log-* files. You would also save the source channel log file tcp_local_slave.log-*. In addition, you would save a copy of the corresponding message file from each destination channel: ZZ01K7LXW76T7O9TD0TB.KEEP1 from the conversion channel and ZZ01K7LXW76T7O9TD0TB.KEEP2 from the tcp_intranet channel.

  9. Remove debugging options once the message and log files have been copied.

    1. Remove the slave_debug and the master_debug keywords from the appropriate channels in the imta.cnf file in directory / msg-svr-base /config.

    2. Reset the mm_debug=0, and remove log_message_id=1 in the option.dat file in directory / msg-svr-base /config.

    3. Recompile the configuration by using imsimta cnbuild.

    4. Run the command imsimta restart dispatcher to restart the SMTP server.