Ok, now we’re getting serious.
I’d put this proc in for your Send Succeed proc
and then compare the process log to both the smat file and output file.
You’ll probably need to up your process log size.
If you don’t need to see the full message, I’d change the proc to something like:
echo $module Sucessful Send: [crange [msgget $mh] 0 200]
or
echo $module Sucessful Send: [lindex [split [msgget $mh] r] 0]
If that doesn’t help, the next thing I would suggest is creating an EO config to enable fset.
Good luck!
-mh
######################################################################
# Name: ftp_send_succeed
# Purpose:
# UPoC type: tps
# Args: tps keyedlist containing the following keys:
# MODE run mode (”start”, “run” or “time”)
# MSGID message handle
# ARGS user-supplied arguments:
#
#
# Returns: tps disposition list:
#
#
proc ftp_send_succeed { args } {
keylget args MODE mode
global HciSite HciConnName HciSiteDir
set procname [lindex [info level [info level]] 0]
set module “$HciSite/$HciConnName/$procname: ”
set dispList {}
switch -exact — $mode {
start {
# Perform special init functions
# N.B.: there may or may not be a MSGID key in args
}
run {
keylget args MSGID mh
echo $module Sucessful Send: [msgget $mh]
lappend dispList “CONTINUE $mh”
}
time {
# Timer-based processing
# N.B.: there may or may not be a MSGID key in args
}
shutdown {
# Doing some clean-up work
}
default {
error “$module Unknown mode ‘$mode'”
}
}
return $dispList
}