May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Postemsg and wpostemsg (TME) commands

News Recommended Links Reference TEC Documentation TEC Rules Programming

Typical Errors

"Error creating a connection to the Event Server" Tips Humor Etc

Event instances can be sent from the command line, or from a script, using the postemsg (non-TME) or wpostemsg (TME) command.  Typically the executable is located at /opt/tivoli/lcf/bin/platform/bin/postemsg. On TMF server you have a set of executables, one for each platform in lcf_bundle directory


This command is not installed in the default lsf install so you need to copy it manually

Both commands have the same form. Here is the wpostemsg.

 wpostemsg [-S server][-f configuration_file][-m message][-r severity][attribute=value...] class source

For example,

  wpostemsg -m 'from us' disk=C: NT_Diskfull NT 

These commands are extremely helpful for testing.

The UNIX logfile and the Windows event adapters can be reconfigured to read from a log file and create events from that input. This provides an easy way to generate events in TEC.

Recall that adapters detect, format, and send event instances to the server. By reconfiguring the logfile adapter, a separate application detects an occurrence of interest and writes an entry into a logfile. The detection is not done by the logfile adapter. But once that entry has been made, the logfile adapter can be configured to read from it, format it with the guidance of a format file, and send it into TEC.

If there is need to monitor something for which an adapter does not exist, and writing to a logfile doesn't work for this application, then it is possible to write a custom adapter using the Event Integration Facility (EIF). The application programming interface consists of function calls written in the programming language C. Writing custom adapters is beyond the scope of this course.

The main functions of an event adapter are to detect, format, and send event instances to the server. The detection of events is application-specific. The formatting of events is done consistently with the BAROC definition. Sending events is controlled by configuration parameters. It is also possible to suppress events not deemed relevant to a given site.

Tivoli provides several event adapters with TEC. Other vendors also have created adapters for their products. In addition to event adapters, there are several other sources of event instances such as Tivoli Plus Partners, the CLI, IBM Tivoli Monitoring, extended logfile adapters, and custom adapters.

The wpostemsg command  posts an event to the event server using Tivoli endpoint communication to a Tivoli Enterprise Console gateway or non-Tivoli communication directly to the event server. It sends an event to an event server using Tivoli endpoint communication to a Tivoli Enterprise Console gateway.  communication is on I use a port 5580. You can do it with the scripts too. See for example discussion about postemsg on mainframes:

I use a REXX script from the "dawns of time" that just opens up a socket connection to the TEC server on port 5580 and sends the event.

This command requires the installation of a Tivoli endpoint on the same system where you are running the command.

You need to provide the correct environment before executing the command by sourcing   Command should be run as root to Tivoli user.

If you have distributed an adapter to the endpoint, this command can be found in the $LCF_BINDIR/../bin directory.

wpostemsg [-S server | -f configuration_file] [-m message] [-r severity] [attribute=value...] class source


If you are using wpostemsg on a system that is configured both as an endpoint and as a managed node, you might want to create a shell alias for the endpoint version of the command. The following examples show how you might do this:

Make sure your PATH does not include both versions of the command.


Assigns a value to any valid attribute. The attribute should be one defined for the event class. Separate multiple attribute=value expressions with spaces.
Specifies the class of the event. It must match a class that is configured at the server. Classes are defined by the adapter and are listed in the adapter BAROC file. If any blank spaces are in the class name, enclose the class name in double quotation marks.
Specifies the source of the event. If any blank spaces are in the source name, enclose the source name in double quotation marks.
-f configuration_file
Specifies the name of the configuration file. To send directly to the event server, specify SOCKET transport in your configuration file. See the IBM Tivoli Enterprise Console Event Integration Facility Reference for more information about configuration files.
-m message
The text of the event, in double quotation marks.
-r severity
Specifies a severity. The severity must be one defined for the event class.
-S server
Specifies the DNS name of the event server. Enter @EventServer to have events submitted to the locally named event server of the Tivoli Enterprise Console gateway. To indicate a remote server, specify @EventServertmr, where tmr is the name of a Tivoli region. If you do not specify the -S or -f option, the event is sent to the event server defined by the Tivoli Enterprise Console gateway.

If portmapper is running on the event server, you can specify a TCP/IP host name or IP address instead. This results in non-Tivoli communication between the Tivoli Enterprise Console gateway and the event server.


The following example for UNIX environments sends a test message that displays an Su_Failure event of severity WARNING on the event consoles:
wpostemsg -r WARNING -m "su login failure." Su_Failure LOGFILE

See Also

postemsg, postzmsg, TECAgent, wpostemsg (endpoint version), wpostemsg (managed node version), wpostzmsg (managed node version), wsetemsg

Typical Errors

 Error creating a connection to the Event Server

Making connections to the event server

The following scenarios can occur when there are problems connecting to the event server:

IBM - postzmsg and postemsg "error creating a connection to the Event Server" errors

postzmsg gets "error creating a connection to the Event Server"
and postemsg sometimes gets tec_put_event failed errno 38
Neither postemsg or postzmsg is using -f for config file.




The default location for a cache file will be /etc/Tivoli/tec on unix and %systemroot%\system32\drivers\etc\Tivoli on Windows.

Error 38 is returned by the EIF code when an event can't be sent to TEC and it also can't be cached for some reason.

The postzmsg error is also because the event is unable to be written to the cache file. Normally, the reason is permissions on the cache directory or cache file. In order for the event to be cached, the file does not have to exist but the directory path to it does. EIF will not create directories. The user should try opening permissions wide open on the cache directory location and the file.

Under normal circumstances using postemsg no cache file is used. But if the connection to the server is down, then the 'e' commands have the same problem.  The 'z' commands have the problem in normal circumstances due to the way the EEIF handles caching.

With the EEIF, events are always written to the cache and a separate thread is used to send the events to the server.  The advantage of this is that when the EEIF is used in a long running adapter, the cache can be automatically emptied when connection to the server is restored without requiring an additional event.



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019