Ticket #515 ( Closed )

Short Description Data Stream Protocol Problem
Entered By: dcrawford@yalesecurity.com When: 2000-05-17 14:47:12 Build: 2.0.6F
Categories Type: Problem   Department: Product   Category: TN3270 Connection
Description
Getting this in our logs:

F4 0004 DFH3481I SS30 CSNE 13:09:59 3270 DATA STREAM 
PROTOCOL VIOLAT   13:09:59

F4 0004 
ION                                                         
   13:09:59

F4 0004 RPL      SS30,    ,13:09:59,00200064 50520400 
020000AD 00675   13:09:59

F4 0004 12C 00000000 0000010C 00500598 
00230000                        13:09:59

F4 0004                             08004000 00000000 
00000000 00000   13:09:59

F4 0004 000 00000000 00000000 00000000 
00750B04                        13:09:59

F4 0004                             82001000 00000040 
A0000004 10800   13:09:59

F4 0004 000 00000000 00000100 00000000 
000390A0                        13:09:59

F4 0004                             
00000000                           13:09:59

F4 0004 TCTTE    SS30,    ,13:09:59,E2E2F3F0 91F20007 
00750B08 00000   13:09:59

F4 0004 000 00000000 00000000 00750CC4 
FF000000                        13:09:59

F4 0004                     
 
Append By: WindSurfer  When: 2000-05-17 15:36:14  New Status: Pending Customer
Comment
Any way you can reproduce in diagnostic mode and get us the 
surfdiag.log, or an equivalent trace from the host?

I can't see any recognizable 3270 datastream orders in the 
information provided...
Append By: dcrawford@yalesecurity.com  When: 2000-05-17 15:40:36  New Status: Pending IE
Comment
This problem is extremely intermittent.  I don't want to 
run diagnostics mode for a long period of time due to the 
log file size.   I don't really know how to proceed.
Append By: WindSurfer  When: 2000-05-17 15:59:39  New Status: Pending Customer
Comment
Check with your MF admin folks, as there is probably way 
more detail available for this error if a flag is set on, or 
the right log entry is viewed.  Lets concentrate on getting 
the diagnostic info from the MF, since it is the one 
detecting the error.
Append By: dcrawford@yalesecurity.com  When: 2000-06-14 08:21:55  New Status: Closed
Comment
Unable to reproduce.