Direct links to fixes
APAR status
Closed as program error.
Error description
SSP configured to write log events to syslog, messages greater than ~1k are being fragmented before being written to the network interface (by SSP, it would seem). This is causing issues for script(s) that are parsing the log events and expect to find messages on separate lines without (unnecesasry, in this case) fragmentation.
Local fix
STRRTC- 368531 SD/SD No Workaround Available
Problem summary
SSP log messages greater than 1000 bytes are being fragmented before writing to syslog. When forwarding SSP log information to syslogd using the syslogd parameters in <ssp>/bin/log.properties, the messages get split into 1000 byte chunks. This can cause a problem with downstream applications that parse the messages.
Problem conclusion
Added support for a new parameter, syslogd.maxmsglength=<value>, in the <ssp>/bin/log.properties file which overrides the default 1000 byte message length.
Temporary fix
Added configuration option for writing larger buffers to Syslog.
Comments
Fix included in SSP3417.
APAR Information
APAR number
IC90460
Reported component name
STR SECURE PROX
Reported component ID
5725D0300
Reported release
340
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-02-25
Closed date
2013-05-01
Last modified date
2013-05-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
STR SECURE PROX
Fixed component ID
5725D0300
Applicable component levels
R341 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PNW","label":"IBM Sterling Secure Proxy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.4","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
01 May 2013