Here's a fix for the sysreq problem

[Scott Klement <klemscot@xxxxxxxxxxxx>]

The problem with SYSREQ not working just looks like a "silly" mistake.  
in session.c, the "header.h5250.flags" variable is being set twice, and
the "opcode" variable isn't being set at all. 

(from session.c, the "tn5250_session_handle_aidkey" function:)

   case TN5250_SESSION_AID_SYSREQ:
      This->read_opcode = 0; /* We are out of the read */
 
      header.h5250.flowtype = TN5250_RECORD_FLOW_DISPLAY;
      header.h5250.flags    = TN5250_RECORD_H_SRQ;
      header.h5250.flags    = TN5250_RECORD_OPCODE_NO_OP;
  
see the problem?  it should be:

      header.h5250.flowtype = TN5250_RECORD_FLOW_DISPLAY;
      header.h5250.flags    = TN5250_RECORD_H_SRQ;
      header.h5250.opcode   = TN5250_RECORD_OPCODE_NO_OP;
                  --------  <--- opcode rather than flags.

Can someone put this in CVS?


+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---