X.25 Questions

[Larry Martell]

I am attempting to connect a Sun 4/490 (running 4.1) to a Stratus via an
X.25 link. I am running version 6.0 of Sun's X.25 package, over an MCP
board.  I want to be able to login from one machine to the other using the
X.3/X.29 (aka PAD) facilities. I am able to get in but I am having some
problems. Maybe some of you out there have experienced and/or solved
similar ones.

Stratus ---> Sun problem:
When I connect from the Stratus to the Sun, I get the following:

stratus> call_thru 255 -gateway rmj_2_sun -address 1
calling gateway rmj_2_sun
Connection established.
call_thru: Invalid value for X3_DATA_FORWARD.  54
login:

I am able to login to the Sun. Hovever, the "call_thru: Invalid value for
X3_DATA_FORWARD.  54" message is displayed whenever I exit more and when I
leave vi. 

I cannot interrupt a command by pressing my intr key (it doesn't matter
what key it is). If I am running a command and press my intr key it has no
effect; the command continues to run. If I am typing a command and I hit
the intr key, however, then when I press return (not right away), the
system does not process the line. e.g.:

larry at st-andy=>ps ax ^C (return pressed here)

larry at st-andy=>

So it seems sometimes the key has an effect, and sometimes it doesn't. And
when it does have an effect, I have to press return, which I should not
have to do.

When I first login, before I have run more or vi, I must use the back
space key to erase a character, no matter what my erase character is set
to. When I hit the delete key (which is what my erase character is set to)
the system displays a ^, followed by an upsidedown question mark. But the
back space key does function like an erase character should (i.e. it
actually erases the character and moves the cursor back). After I have run
more or vi, however, the back space key moves the cursor back, doesn't
erase the character, and a control-h gets inserted into the input stream.
The delete key doesn't cause the cursor to move or erase any characters on
the screen, but it does remove characters from the input stream. So
running more or vi changes the way things work.

Sun ---> Stratus problem:

When I connect from the Sun to the Stratus I have somewhat similar
problems.  When I am at command level and I hit a function key that
generates multiple bytes, the Stratus does not perform the function; the
bytes generated by the key are displayed on the terminal. The function
keys all generate sequences of the type ^[[213z. When I hit return the
sequence is ecohed back as if it were part of the command, but without the
^[[. e.g.:

display_terminal_parameters^[[213z
command_processor: Invalid object name. display_terminal_parameters213z.

Like the Sun, when I hit the intr key on the Stratus (^C), it has no
effect; running commands continue to run. The Stratus does not treat it as
a special character:

^C
command_processor: Invalid object name. `03.

But, when I am in any full screen type program (e.g. the editor, an FMS
application), all function keys work fine. When I leave the program and go
back to command level, they no longer work.

I think it has something to do with the PAD parameters. I think they are
set by the local host during the call set-up. The Stratus does not allow
you to change any PAD paramaters. They don't even tell you what default
values they use. So when I am connected Stratus->Sun I cannot speak to the
PAD executive.  The Sun does allow you to modify PAD parameters. To speak
to the PAD executive you hit ^P. When I am connected Sun->Stratus at
command level (when stuff doesn't work), I can read and/or modify PAD
parameters:

^P
PAD> ?
[1] escape 1
[2] echo 1
[3] forward 2
[4] timeout 0
[5] padflowcontrol 0
[6] service 1
[7] breakaction 21
[8] datadelivery 0
[9] crpad 0
[10] linefold 0
[11] baudrate 3
[12] terminalflowcontrol 1
[13] linefeedinsert 4
[14] lfpad 0
[15] editcontrol 1
[16] chardelete 8
[17] bufferdelete 24
[18] displayline 18

I think it has something to do with parameter 3 or 4. Since everything
works ok in the editor or a form I wanted to look at the parameters in
those modes. When in the editor ^P has no effect at all. When I am in an
FMS application, ^P clears the screen. In either case, I cannot
interrogate the PAD. I have played around with diferent values for the
forward and timeout pramaters, but couldn't get it to work right.

I spoke to both Sun and Stratus and they each blamed the other.

If anyone has any suggesions at all, please reply here or by e-mail.

Thanks!

Larry Martell
uunet!st-andy!larry
212-668-9478