Metastorm Integration Manager 8.5.1 Hotfix 8 (8.5.1.008)
The following issue is resolved in this Hotfix:
SR-12212010-0009 (PF2566 )
On z/OS after several GDG file transfers, the file transfer service failed
with the following error message:
FTF::readFileToQueue():103:XMOALLOC failed to allocate memory:RC(20,0)
The following issues were resolved in previous 8.5.1 hotfixes and are
cumulative in this distribution. (All patches do not apply to all operating
systems.)
PF2260
The Directory Monitor functionality on HP-NSK was enhanced to support
Guardian files. (The HP-NSK directory monitory now supports Unstructured
Edit Files. HP-NSK Relative, Entry-Sequenced, and Key-Sequence file types
are not part of this solution.) Enhancements were made to both the MIM
Directory Monitor on the HP-NSK MIM Node and the MIM Process Monitor on
the Enterprise. (On the Process Monitor, there are new entries on the
Directory Monitor Instance page). User documentation is provided in PDF
format with this hotfix.
PF2262
The Directory Monitor Service terminated on HP NonStop in debug mode.
(Debug can be set on the Directory Monitor Instance page in the
Advanced section or in the MIM Registry in the DirectoryMonitorService.xml)
PF2332
The Directory Monitor Service failed at runtime in Identify mode due
to an invalid default value in the DirectoryMonitorTemplate.xml for
useAltUserAuth and passIdentityContext.
SR-08112010-0004 (PF2351)
The File Transfer Service on the i5/OS with the source type of
stream data and the destination type of PFDTA produced corrupt records.
The error depended on the file, record, and message size, therefore not
all transfers would result in corrupt data. (The transfer that identified
this issue was a large source file of streamed data, a destination file
type of PFDTA, and an xmfile policy that used a record type of fixed.)
SR-09102010-0009 (PF2336)
The File Transfer Service produced an invalid status error of:
"Internal Error: An error condition has already occured".
The processing that identifed this issue was deleteSource(). The
error occurred even when the deleteSource was successful.
SR-08132010-0010 (PF2321)
The FTF, FTFPING, or FTFEND command-lines were not properly handling
the -LQM option from a client node.
PF2322
The FTFPING command, when run on a client node, was not properly
defaulting the SQM and DQM to that client node.
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 153 General Questions
- 149 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 33 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories