Running Message Manager
Trading Manager has been enhanced to create logs with more detailed information about failures while running Message Manager. Therefore it is critical that all reject files be examined to get additional information about errors.
| Error condition | Reason |
|---|---|
| System runs slow, high CPU utilization. | Could be caused by Max Threads parameter being set too high in the dtx.ini file. A lower setting allows the server to perform more useful work and less swapping between threads. |
| Random map failures due to not enough memory available | Could be caused by Max Threads parameter being set too high in the dtx.ini file. See the section titled "Analyzing Large Transmissions" for more memory reduction options. |
| Files do not show up in the PUT Post Office | Usually occurs when the path is not correctly defined in Partner Manager. A reject file and the Partner Manager Traffic Log provide specific error information. At times a reject file is not created; in that case the files might be found in the root of the server. The Partner Manager Traffic report will show the location where the files are written |
| Reject files getting created by StampAndSort containing partial files. | Occurs when files are written to the mail folder by an application other than the IBM Transformation Extender. See the section titled "Interfacing with non-IBM Transformation Extender systems for additional information. |
| System runs slow, low CPU utilization; most maps are in Resource pending state. | This is a configuration error. Avoid configuring maps that can cause them to become Resource Pending. See the section titled "Avoiding Resource Pending Configurations" for additional information. |
| File errors when writing to other servers. | If the paths are correct and/or the drive mappings have not been reset then it is most likely a permission problem. The Launcher user id must have write permissions on all the folders that are configured as PUT Post Offices. |
| Valid files fail X12 Validation. | Each new transaction/version combination is added, the EDI Wizard has to be executed to generate a new x12mail.mtt type tree that has to go into the folder where all the Message Manager sources are located. Next, the customer has to deploy the RunMaps system for the new transactions to go into effect on the server. Deploying MessageManager is not needed. |
| Tradelink errors even though the Trade Links have just been added to Partner Manager. | Message manager exports the Trade Links information at Launcher startup and each night at midnight. For new Trade Links to go in effect immediately, the export has to be triggered from the Message Manager Config. section in Partner Manager. The export has to be triggered using the Run Export Process on Demand feature from the Message Manager Config. section in Partner Manager. |
| Valid files are getting rejected by StampAndSort as invalid file names when they do conform to the Trading Manager standards | Message Manager is failing to access the database. Either RunMaps where not redeployed after correcting the update.mdq file or the database is not available. |