Document ID: 12324
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Problem
Observations
Solution
Related Information
Introduction
This document discusses a failure caused by an incorrect definition in the Unformatted System Services message table number 10 (USSMSG10).
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Problem
In this document, the failure is caused by an incorrect definition in the USSMSG10: it is set to Systems Network Architecture (SNA) Character String (SCS) format instead of 3270 Data Stream (3270DS) format. The customer is attempting to connect from a LAN Workplace TN3270E extended client, but is unable to get the USSMSG10 display to flow back to the client (resulting in a blank display).
The logical unit (LU) name is LUHCB001. Everything works fine when the customer specifies the actual application through the LOGAPPL parameter on the LU (ACT/SESS); but, using the USS table, the LU is stuck in the P-BIND state.
Observations
LU LUHCB001 is in P-BIND state when attempting to connect using USSMSG10 display, as shown below.
lu name client-ip:tcp state model frames in out idle for 1 LUHCB001 168.183.53.97:1037 P-BIND 327802E 7 5 0:1:30 2 LUHCB002 168.183.53.97:1030 ACT/NA 327802E 4 3 2:33:56 3 LUHCB003 168.183.53.97:1031 ACT/NA 327802E 4 3 2:33:50
LU LUHCB001 is in ACT/SESS state when attempting to connect to a specific application, as shown below.
lu name client-ip:tcp state model frames in out idle for 1 LUHCB001 168.183.53.97:1041 ACT/SESS 327802E 33 25 0:0:13 2 LUHCB002 168.183.53.97:1030 ACT/NA 327802E 4 3 2:46:15 3 LUHCB003 168.183.50.7:1463 ACT/NA 327802E 10 8 0:8:55
The LUGROUP Major Node is shown below.
CISCOLU1 VBUILD TYPE=LUGROUP
*
LUCISCO1 LUGROUP
3279S4E LU DLOGMOD=SNX32704, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327905E LU DLOGMOD=SNX32705, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327904E LU DLOGMOD=SNX32704, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327903E LU DLOGMOD=SNX32703, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327902E LU DLOGMOD=SNX32702, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327902E LU DLOGMOD=SNX32702, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327805E LU DLOGMOD=SNX32705, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327804E LU DLOGMOD=SNX32704, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327803E LU DLOGMOD=SNX32703, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327802E LU DLOGMOD=SNX32702,LOGAPPL=UHCANVAS, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327802 LU DLOGMOD=D4C32782, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327803 LU DLOGMOD=D4C32783, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327804 LU DLOGMOD=D4C32784, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
327805 LU DLOGMOD=D4C32785, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
@ LU DLOGMOD=D4C32782, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
* STATOPT='LUGROUP FOR CISCO CIP CARD '
Solution
This client is not running TN3270E—it is simply TN3270. The user gets confused by the “-E” at the end of a model type, as in “IBM-3278-5-E.” That “-E” refers to Extended 3270 Datastream, which has nothing to do with the TN3270 protocol layer.
Therefore, the client needs its USSMSG10 in 3270DS format, not in SCS. Entries such as these are technically incorrect:
327905E LU DLOGMOD=SNX32705, X
USSTAB=USSUHC, X
SSCPFM=USSSCS
The 0 in 327905E indicates that it is a TN3270 client (or a TN3270E that does not ask for Bind-image). Such clients need 3270DS on the system services control points-logical unit (SSCP-LU) session, which means that this:
-
SSCPFM=USS3270 must be specified.
-
The USSTAB parameter must point to a file which contains the USSMSG10 laid out in 3270DS.
Many users already have USSMSG10s laid out in both datastreams (the 3270DS form is needed for local non-SNA devices, which is what TN3270 looks like).
The user can use the CIP TN3270 server code release with automatic translation (cip22-15, or interims 206-171 and later) to rectify this problem. This code was added to detect the mismatch and convert automatically. When it finds the mismatch, it also converts the inbound back from 3270DS to SCS, so it is essential that the two parameters agree, as shown below.
-
Prior to 206-171:
Models xxxxSxx Models xxxx0xx USSTAB->SCS data USSTAB->3270 data SSCPFM=USSSCS SSCPFM=USS3270
-
206-171 and later:
Any model Models xxxx0xx only USSTAB->SCS data USSTAB->3270 data SSCPFM=USSSCS SSCPFM=USS3270
Related Information
- tn3270 Server (Telnet 3270) Support Page
- Technology Support
- Product Support
- Technical Support - Cisco Systems
| Updated: Sep 09, 2005 | Document ID: 12324 |