TRANSFER Installation and Management Guide

X400 Importer Log
Troubleshooting
13198 Tandem Computers Incorporated 12–27
Sensitivity
Autoforwarded flag
Processing the body parts of a P2:
Text body parts
Message body parts
Encrypted body parts
Creating items for these body parts and attaching them as component items
Or, in the case of a Report Package or an IPN (Inter-Personal Notification), tracing
the importer’s progress as it creates a STATUS package and fills in the appropriate
fields
Giving the final status of import :
Success
Requeue for retry
Reject message (sends to the exporter to build an X.400 report)
Discard
Specific importer error messages sometimes come after the statement that the
importer has encountered an error, for example:
$SFIM (I2046) [1] PDU# 0,0,41635,1,1021: Error with P1 X400 Recip:
$SFIM (I2047) [1] PDU# 0,0,41635,1,1021: TRANSFER Error occurred: 4160
In other cases, the source of the error may be reported after the error is output:
$SFIM (I4026) [1] PDU# 0,0,41635,1,1021: TRANSFER Error occurred: 4160
$SFIM (I4052) [1] PDU# 0,0,41635,1,1021: Above Error problem with Subject of P2 Header
This inconsistency occurs because some routines are shared by many calling
routines, and the calling procedure is responsible for stating the area where the
error occurred after it completes.
In either case, the summary line gives the timestamp and looks like the following:
$SFIM (I0013) [1] PDU# 0,0,41635,1,1021: RETRYING Message due to above errors at...
or:
$SFIM (I0012) [1] PDU# 0,0,56623,1,1360: Message processed successfully at...