Direct links to fixes
APAR status
Closed as fixed if next.
Error description
MEFG logs or traces are lost after reaching a maximum size. Expected Behavior: To archieve the logs/traces, to avoid losses of trace information.
Local fix
Create a script which renames the MEFG trace and log files. If only x versions are required to be stores, the script should also contain a delete of the older version after reaching a limit. Depending on the needs the new file names may include a counter or the date of rename. Below is a list of MEFG log/trace files: <mefg>/bin/restartServers.log <mefg>/bin/MEFGCommServer.log <mefg>/log/ftr/MEFGSwiftnet.log [<mefg>/log/ftr/MEFGSwiftnet.log.<ID>] <mefg>/log/scd/MEFGSwiftnetServerS<RA ID>.log [<mefg>/log/scd/MEFGSwiftnetServerS<RA ID>.log.<ID>] <mefg>/log/scd/MEFGCommServer.log [<mefg>/log/scd/MEFGCommServer.log.>ID>] <mefg>/log/scd/MEFGSwiftnetServerS<RA ID>.log. [<mefg>/log/scd/MEFGSwiftnetServerS<RA ID>.log.<ID>] <mefg>/log/ftr/MEFGSwiftnet.trc <mefg>/log/scd/MEFGSwiftnetServerS<RA Id>.trc <mefg>/log/scd/MEFGSwiftnetCmdServerS<RA Id>.trc For an active/active configuration, every RA will have a log/trace. Entries like [<mefg>/log/<sub dir>/<log name>.log.>ID>] means that there can be 1 - 3 roll over logs. During maintenance do: 1. StopAdapter 2. Run the rename script 3. Start Adapter It is not possible to do this during uptime of the adapter.
Problem summary
Users Affected: SI MEFG SWIFTNet7 customers that do not manually archive MEFG log and trace files Problem Description: SWIFTNet7 MEFG log and trace files can grow to up to 2 GB in size, after which the offset of the file within the application will roll to start of the files, which can lead to non sequencial log entries. Platforms Affected: All
Problem conclusion
Resolution Summary: The SWIFTNet7 MEFG startup scripts archive the log and trace files. The script moves these MEFG files to a directory under the MEFG log directory with the naming scheme log_MMDDYY_HHMMSS. Delivered In: 5020603_2
Temporary fix
Comments
APAR Information
APAR number
IT16515
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
524
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-08
Closed date
2017-06-01
Last modified date
2017-06-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
11 September 2023