Re: Trend issue

Rob,

Unfortunatly, I don't have any solutions for you but have concerns of my
own. We are running Trend and thinking of upgrading to 6.1 shortly. Was
wondering, did Trend put those emails or others into a "held" status? Also
did you issue a tell router show queue? Were the emails in a wait status?
If so, did you try issuing a route %servername% command and have the
emails route out?

Thanks for your time!

Kelly D. Sprunger
Systems Administrator | Lotus Notes Support
American General Financial Services
* kelly_sprunger@xxxxxxxxxxxxx
( 812.461.2511




rob@xxxxxxxxx
Sent by: domino400-bounces+kelly_sprunger=agfinance.com@xxxxxxxxxxxx
02/16/2009 08:10 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>


To
domino400@xxxxxxxxxxxx
cc

Subject
Trend issue






I noticed an email stuck in the mail.box on a server that was just
upgraded to i 6.1. It was from an internet user to some internal people.

Trend's SMDREAL had the messages below.

I was able to take those attachments out of the mail.box, put them into a
yahoo account email and send that in. This also got stuck in the mail.box

and generated these same messages.

Trends initial response was they could load that email on to other
platforms and not have this issue.

Object Type Library Attribute Text
VSAPI *SRVPGM TRENDMICRO CLE VSAPI8.700-1004

SMDreal status: PID (25860)
SMD version: 3.0.1.5403
Scan engine version: 8.700-1004 Virus pattern file version: 5.847.00

DSPSRVPGM VSAPI
Release service program created for . . . . . . : V4R2M0
Earliest release service program can run . . . . : V4R2M0
All modules were from Trend.
Service
Program Library Activation Signature
QC2UTIL1 QSYS *IMMED CB1F803582C31AC25B4DCBDD1B6D0948
QC2IFS QSYS *IMMED 6E2D63C42B8D16E74EA1DD08E3AF52EF
QLEAWI QSYS *IMMED 44F70FABA08585397BDF0CF195F82EC1
QP0LLIB1 QSYS *IMMED D8D7F0D3D3C9C2F14040404040404040
QP0LLIB2 QSYS *IMMED D8D7F0D3D3C9C2F24040404040404040
QP0ZCPA QSYS *IMMED D8D7F0E9C3D7C1404040404040404040
QP0WSRV1 QSYS *IMMED D8D7F0E6E2D9E5F14040404040404040
QSYPAPI QSYS *IMMED D8E2E8D7C1D7C9404040404040404040

MCH3601 Escape 40 02/16/09 08:20:48.251559 VSAPI
TRENDMICRO *STMT VSAPI TRENDMICRO *STMT
From module . . . . . . . . :
SCANBUFF
From procedure . . . . . . :
_ExecuteScript
Statement . . . . . . . . . : 1205
To module . . . . . . . . . :
SCANBUFF
To procedure . . . . . . . :
_ExecuteScript
Statement . . . . . . . . . : 1205
Thread . . . . : 0000008F
Message . . . . : Pointer not set
for location referenced.
Cause . . . . . : A pointer was
used, either directly or as a basing
pointer, that has not been set to
an address.
CEE9901 Escape 30 02/16/09 08:20:48.343178 QLEAWI
QSYS *STMT QP0WPINT QSYS *STMT
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 204
To module . . . . . . . . . :
QP0WSPTHR
5761SS1 V6R1M0 080215 Display Job Log GDIHQ
02/16/09 08:52:33 Page 3
Job name . . . . . . . . . . : SMDREAL User . . . . . . :
QNOTES Number . . . . . . . . . . . : 983054
Job description . . . . . . : NOTES01 Library . . . . . :
QUSRNOTES
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
To procedure . . . . . . . :
pthread_create_part2
Statement . . . . . . . . . : 19
Thread . . . . : 0000008F
Message . . . . : Application
error. MCH3601 unmonitored by VSAPI at
statement 0000001205, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
VSAPI SCANBUFF _ExecuteScript. The program
was stopped at the high-level
language statement number(s) 0000001205 at the
time the message was sent. If more

than one statement number is shown, the
program is an optimized ILE
program. Optimization does not allow a single
statement number to be determined.
If *N is shown as a value, it means the
real value was not available.
Recovery . . . : See the low level messages
previously listed to locate the
cause of the exception. Correct any errors,
and then try the request again.
CPF24A3 Escape 40 02/16/09 08:20:48.409395 QMHSNDPM

QSYS 0C05 QLEAWI QSYS *STMT
To module . . . . . . . . . : QLEDEH
To procedure . . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 204
Thread . . . . : 0000008F
Message . . . . : Value for call
stack counter parameter not valid.
Cause . . . . . : The value 3,
specified for call stack counter parameter,
is not valid. The value was
specified in parameter number 7 on the API.
Recovery . . . : Correct the
value for call stack counter parameter and
try the request again. This value
must be greater than or equal to 0 but
cannot be larger than the number of

entries on the call stack.
CEE9901 Diagnostic 30 02/16/09 08:20:48.413822 QLEAWI
QSYS *STMT QLESPI QSYS *STMT
From module . . . . . . . . : QLETOOL
From procedure . . . . . . : Q LE
CPF24A3_handler
Statement . . . . . . . . . : 9
To module . . . . . . . . . :
QLECRTTH
To procedure . . . . . . . :
LE_Create_Thread2__FP12crtth_parm_t
Statement . . . . . . . . . : 18
Thread . . . . : 0000008F
Message . . . . : Application
error. CEE9901 unmonitored by QP0WPINT at
statement 0000000019, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
QP0WPINT QP0WSPTHR pthread_create_part2. The
program was stopped at the
high-level language statement number(s)
0000000019 at the time the message
was sent. If more than one statement
number is shown, the program is an
optimized ILE program. Optimization does
not allow a single statement number

to be determined. If *N is shown as a
value, it means the real value was
not available. Recovery . . . : See
the low level messages previously
listed to locate the cause of the
exception. Correct any errors, and

then try the request again.

Rob Berendt