View utility

Display the contents of the specified "version" of an MTA log file.

Syntax
imsimta view file-pattern

Restrictions
Must have read access to the requested file.

A file name pattern for which MTA log file to display. A complete file path may be specified. Or if merely a file name (sans unique id) is specified, the utility will look in the MTA log directory,.

Description
The  utility may be used to display a  specified "version" of an MTA log file. MTA log files have a    appended to the file name to allow for  the creation of multiple "versions" of the log file; on UNIX,  the    is appended to the very end of the  file name (the end of the file extension). The  utility understands these unique ids and can display the  contents of the particular file corresponding to the requested  "version" of the file.

The default, if no offset switch is specified, is to display the most recent "version" of the file.

This switch is used to specify displaying the  th "version" of the file (starting counting from 0). For instance, to display the earliest (oldest) "version" of the  file, specify

This switch is used to specify displaying the  th from the last "version" of the file (starting decrementing from 0 as  the most recent version). For instance, to display the most recent (newest) "version" of the file, specify

Examples
fat_main: watch_connect failed: Connection refused The above example shows displaying the most recent Job Controller log  file, and finding logged therein that the Watcher though enabled  (  in Unified  Configuration, or    in legacy configuration) was  apparently not running (which is what the error message shown in that  log file indicates). 13:00:16.79: Checking for TLS usage 13:00:16.79: Initializing TLS library 13:00:16.98: SMTP options read and set 13:00:16.98: Debug output enabled, system mail.domain.com, process 6597.1, SMTP client version V8.0 compiled Aug 11 2014 11:38:29 13:00:16.98: Oracle Communications Messaging Server shared library version 8.0.0.0.0 linked 11:42:42, Aug 7 2014 13:00:16.98:     max concurrent threads 10, jobs/thread 10 13:00:16.98: ( 2) tcp_intranet running 13:00:16.98: ( 2) tcp_intranet -- delivering /opt/sun/comms/messaging64/data/queue/tcp_intranet/004/ZZi0Z6h0Ykfc0.00 13:00:30.29: waiting for 1 threads to exit, or 5400 seconds 13:00:32.31: ( 2) tcp_intranet finished. did 1 messages 13:00:32.31: ( 2) No more hosts, ending connections 13:00:32.31: All message processing completed. 13:00:16.98: Initializing message dequeue via quc_rinit, file "/opt/sun/comms/messaging64/data/queue/tcp_intranet/004/ZZi0Z6h0Ykfc0.00" 13:00:16.98: Reading first To: address 13:00:16.98: log_queue_entry called. 13:00:16.98:  Originator address john.doe@domain.com 13:00:16.98:  Recipient address jane.doe@domain.com 13:00:16.98:  Original recipient address rfc822;jane.doe@domain.com 13:00:16.98: Forced routing to host1.domain.com 13:00:16.98: Setting up connection to "host1.domain.com", initial mailbox "jane.doe" 13:00:16.98: No connection currently open 13:00:16.98: Opening new connection for host1.domain.com ...etc... The above example shows displaying two   files containing    output, the  (currently) oldest (which in this case is "controller" thread output),  and the (currently) next-to-oldest (which in this case is output from a  delivery thread, processing a particular message file).
 * 1) imsimta view -l=0 job_controller.log
 * 1) imsimta view -f=0 tcp_intranet_master.log
 * 1) imsimta view -f=1 tcp_intranet_master.log

See also:
 * MTA transaction logging
 * debug Option
 * master_debug Option
 * slave_debug Option
 * MTA command line utilities