What is the max length or size of "msg_text" field that opcmsq can process / send in OA12.
is there some limitation of max length / size of "msg_text" field that can be processed / send via opcms command towards OML9 using OA12 agent ?
Tried to find that info in docs - but failed.
I don't think the queue file will be the problem. OBM is unlimited (I think).
How many chars can your command line support? How many chars do you want to send?
https://docs.microfocus.com/itom/Operations_Agent:12.14/opcmsgAPI isn't very helpful. Same with https://docs.microfocus.com/itom/Operations_Agent:12.14/opcmsg. How many chars do you need?
Remember also the setting [eaagt]OPC_MAX_MSG_LEN that limits the size of a message (this includes the event title, original text and various attributes). The default value of this setting is 1MB. See documentation at:
But if you plan to send messages of this size, you should probably think about alternatives.
I do not remember exactly - it was most probably a solution we use that captures some events (I think from BizTalk application) from Windows Eventlog and create message / incidents where message text is de-facto copy of text field of Windows Event. And customer was complaining that message is cut - and they do not see important part of text...
@Rotax - Hi Thierry, thanks for your input and of course nice to see you again 😉
Sorry, but I misunderstood the question. I thought you wanted to send a big event!
OPC_MAX_MSG_LEN would appear to work for most event fields except annotations. So if have a big annotation it looks like it will all get sent over to the OBM server (I had a 10MB annotation which arrived in the OBM event DB).
Conveniently the OBM console can only dispaly 100000 chars in it's annotation even though the data is sent to the server. There is a reassuring message "Note: the annotation exceeds the display limit and was truncated". But as mentioned the full annotation is stored in the database!
Typically windows event logs are not that large.
so you seee I originally asked one and half year ago.
I do not exactly remember what was the issue that time, but usually we got some troubles to send long-long BizTalk messages.
And target manager was and still is OML 9.22.190.
Anyway thanks for help and valued explanation.
Best regards / Marek