George Two points:
1. You do not need the TELNETDEVICE statements since the names you are providing are set up by default. Please read that TELNETDEVICE tutorial post - carefully and tell me about anything you do not understand. That Table - it's 33 in my manual - is just telling you what is set up by default so only if you need to change the default do you need to use a TELNETDEVICE statement. 2. The reason you have an error is that there needs to be a comma between the first and second mode table entry names without any blanks. For example TELNETDEVICE 3278-2-E NSX32702,SNX32702 The missing comma means that the analysis "sees" a third positional parameter, PARM3, which doesn't belong on the statement. With the comma in place the two names all become one long parameter - as it needs to be. My advice in order to try to keep your life as simple as possible is to throw out all these TELNETDEVICE statements. Two more things: A. In case the Attachmate change does not help, we should be prepared in knowing what all of the PROFILE data set in the TN3270E procedure looks like so I would be obliged if you would post it. B. Mainly for curiosity but following up on our discussions concerning the RFC 2355 negotiation - and assuming there is a standard Attachmate configuration - I would like to know what "device type" you are actually using. You need to look for a line like PROTOCOL: TN3270E LOGMODE: SNX32702 DEVICETYPE: IBM-3278-2-E in a DISPLAY tcpip,tnserv,CONN,CONN=nnn command output. In any case, you should probably be familiar with the use of this command when looking into problems with your TN3270 connections. Chris Mason On Wed, 26 Jan 2011 12:04:58 -0500, George Rodriguez <[email protected]> wrote: >Hi Chris, > >Sorry for not getting back to you sooner. We found a tech-note in >Attachmate's database that seems to be helping the timeout problem. In the >next few days we are rolling it out to more than the 3 telnet terminals that >the change was applied to. > >I did make the following change to the telnet profile based on a table >(Table 26. Device type and logmode table) in the manual: > >TELNETDEVICE 3278-2-E NSX32702 SNX32702 >TELNETDEVICE 3278-3-E NSX32702 SNX32703 >TELNETDEVICE 3279-3-E NSX32702 SNX32703 >TELNETDEVICE 3278-4-E NSX32702 SNX32704 >TELNETDEVICE 3279-4-E NSX32702 SNX32704 >TELNETDEVICE 3278-5-E NSX32702 SNX32705 >TELNETDEVICE 3279-5-E NSX32702 SNX32705 > >but I'm getting these errors: > >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 26 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32702 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 27 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32703 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 28 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32703 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 29 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32704 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 30 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32704 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 31 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32705 >EZZ6035I TELNET DEBUG PROFILE WARNING,LINE: 32 MOD: EZBTMPRP > RCODE: 8043-00 Parameter not used for this statement. > PARM1: PARM2: TELNETDE PARM3: SNX32705 > >Can you help me out of this jam? > >Thanks... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
