We are running HIS connecting via DLC to our ISeries mainframe.
THis connection works great for a period of time and then suddenly disconnects. Has anyone had similar issues. I enclose a snippit from an Windows event log.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:32:43
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command TRANSMIT_I_FRAME (0BH) failed with error MEMORY_LOCK_FAILED (69H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:34:16
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command TRANSMIT_I_FRAME (0BH) failed with error UNKNOWN_ERROR (A1H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Information
Event Source: SNA Server
Event Category: None
Event ID: 38
Date: 27/01/2005
Time: 10:34:16
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
APPC session deactivated abnormally
Qualifier = 0003
Connection = CSTANLEY
LU alias = LOCAL
PLU alias = CSTANLEY
Mode name = QPCSUPP
Session ID = 00000000000000A1
LFSID = 1020B
Client Domain = CHARLES-STANLEY
Client User = snamiddle
Client Machine = CSSNA02
EXPLANATION
An APPC session has been deactivated abnormally. The qualifier listed above corresponds to one of the following:
0002 The session was deactivated because of a temporary (Retry) error, and may be retried. This could occur if the SNA connection has failed, which would be indicated by an Event 23. See if an Event 23 has occurred and follow the action plan outlined with that event.
0003 The session was deactivated because of a permanent (No retry) error, such as a parameter mismatch. Contact the administrator of the partner LU's system to determine which parameters are mismatched.
0004 The session was deactivated because the Host Integraton Server SNA Service detected a protocol violation by the partner LU. Contact the administrator of the partner LU's system.
0005 An APPC or CPIC application was running on a client machine and the client lost it's LAN session to the Host Integration Server, *or* the session was deactivated as the result of a TP_ENDED(Hard) issued at the local LU. If the problem was caused by a lost LAN session, see the client username and machine above, and capture a Microsoft Network Monitor (or similar) trace of a dropped session and provide the trace to Microsoft support personnel.
Event Type: Warning
Event Source: SNA APPC Application
Event Category: None
Event ID: 90
Date: 27/01/2005
Time: 10:34:16
User: CHARLES-STANLEY\snamiddle
Computer: CSSNA02
Description:
APPC protocol violation:
Sense data = 0C001110
TP_ID = 00000000D83AC800
Conv_ID = 00C853C0
EXPLANATION
A protocol violation was detected on an APPC conversation. The TP_ID and Conv_ID in this message were shown on a previous message. The conversation failure is reported to the local TP with a return code of AP_CONV_FAILURE_NO_RETRY. The SNA sense data provides detail about the error type.
ACTION
See "IBM Systems Network Architecture: Formats" for an explanation of the sense data.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:35:26
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command READ (31H) failed with error MEMORY_LOCK_FAILED (69H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 560
Date: 27/01/2005
Time: 10:39:27
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Read from mailslot or socket failed, rc = 10055
EXPLANATION
A Win32 ReadFile() or winsock recvfrom() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 561
Date: 27/01/2005
Time: 10:56:57
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Write to mailslot or socket failed, rc = 1453
EXPLANATION
A Win32 WriteFile() or winsock sendto() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 561
Date: 27/01/2005
Time: 10:56:57
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Write to mailslot or socket failed, rc = 1453
EXPLANATION
A Win32 WriteFile() or winsock sendto() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."
THis connection works great for a period of time and then suddenly disconnects. Has anyone had similar issues. I enclose a snippit from an Windows event log.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:32:43
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command TRANSMIT_I_FRAME (0BH) failed with error MEMORY_LOCK_FAILED (69H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:34:16
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command TRANSMIT_I_FRAME (0BH) failed with error UNKNOWN_ERROR (A1H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Information
Event Source: SNA Server
Event Category: None
Event ID: 38
Date: 27/01/2005
Time: 10:34:16
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
APPC session deactivated abnormally
Qualifier = 0003
Connection = CSTANLEY
LU alias = LOCAL
PLU alias = CSTANLEY
Mode name = QPCSUPP
Session ID = 00000000000000A1
LFSID = 1020B
Client Domain = CHARLES-STANLEY
Client User = snamiddle
Client Machine = CSSNA02
EXPLANATION
An APPC session has been deactivated abnormally. The qualifier listed above corresponds to one of the following:
0002 The session was deactivated because of a temporary (Retry) error, and may be retried. This could occur if the SNA connection has failed, which would be indicated by an Event 23. See if an Event 23 has occurred and follow the action plan outlined with that event.
0003 The session was deactivated because of a permanent (No retry) error, such as a parameter mismatch. Contact the administrator of the partner LU's system to determine which parameters are mismatched.
0004 The session was deactivated because the Host Integraton Server SNA Service detected a protocol violation by the partner LU. Contact the administrator of the partner LU's system.
0005 An APPC or CPIC application was running on a client machine and the client lost it's LAN session to the Host Integration Server, *or* the session was deactivated as the result of a TP_ENDED(Hard) issued at the local LU. If the problem was caused by a lost LAN session, see the client username and machine above, and capture a Microsoft Network Monitor (or similar) trace of a dropped session and provide the trace to Microsoft support personnel.
Event Type: Warning
Event Source: SNA APPC Application
Event Category: None
Event ID: 90
Date: 27/01/2005
Time: 10:34:16
User: CHARLES-STANLEY\snamiddle
Computer: CSSNA02
Description:
APPC protocol violation:
Sense data = 0C001110
TP_ID = 00000000D83AC800
Conv_ID = 00C853C0
EXPLANATION
A protocol violation was detected on an APPC conversation. The TP_ID and Conv_ID in this message were shown on a previous message. The conversation failure is reported to the local TP with a return code of AP_CONV_FAILURE_NO_RETRY. The SNA sense data provides detail about the error type.
ACTION
See "IBM Systems Network Architecture: Formats" for an explanation of the sense data.
Event Type: Warning
Event Source: SNA DLC Link Service
Event Category: None
Event ID: 233
Date: 27/01/2005
Time: 10:35:26
User: NT AUTHORITY\SYSTEM
Computer: CSSNA02
Description:
A DLC (802.2) command READ (31H) failed with error MEMORY_LOCK_FAILED (69H).
EXPLANATION
An error code which is not explicitly handled by Host Integration Server 2000 has been returned by the DLC driver.
This could be due to network card mis-configuration or hardware problems.
ACTION
Contact network support personnel, and supply the reported error information.
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 560
Date: 27/01/2005
Time: 10:39:27
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Read from mailslot or socket failed, rc = 10055
EXPLANATION
A Win32 ReadFile() or winsock recvfrom() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 561
Date: 27/01/2005
Time: 10:56:57
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Write to mailslot or socket failed, rc = 1453
EXPLANATION
A Win32 WriteFile() or winsock sendto() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."
Event Type: Warning
Event Source: SNA Base Service
Event Category: None
Event ID: 561
Date: 27/01/2005
Time: 10:56:57
User: CSSNA02\snaadmin
Computer: CSSNA02
Description:
Write to mailslot or socket failed, rc = 1453
EXPLANATION
A Win32 WriteFile() or winsock sendto() call failed. The return code is shown.
ACTION
Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the "Microsoft Host Integration Server Online Books."