There are a number of ways to connect a display with a linux system running on s390/s390x. Here are some basic ways:
The simplest is to start an xserver on your NT system (ex. Hummingbird Exceed), then ssh/telnet in to the system do export your DISPLAY setting (ex. "export DISPLAY=NTsystems.ip.or.host:0.0") and then run your X app (ex. xclock). Some ssh clients allow you to do X forwarding so you don't have to type the export display manually each time. Putty that comes with sles-8 is one that does so. To enable this, start a new session, enter your ip and check "ssh" as the protocol type, then in the Categories menu on the left, go to "Connection->SSH->tunnels". At the very top is the X forwarding settings. Check the box and enter the value of what you would normally set your DISPLAY variable to if you had to type it in manually. Then you have to go back to the "Session" category panel, enter in a "Saved Session" name and hit the "save" button. Now whenever you load that particular sesion profile and "open" it. You automatically enable X forwarding for that session. If you don't save the session with forwarding turned on, then you'll have to manually set it each time which would be practically same as exporting your DISPLAY manually each time. Yet another method that makes use of an X server on the NT side is xdm. This one brings up a full desktop environment and as Mr. Post said is quite resource intensive. Much of the Linux side of this setup is explained in the "X Window System" chapter of the SLES-8 administration manual (admin_en.pdf). The NT (X server) side of the configuration would differ depending on your X server app. On my Hummingbird Exceed, at the least I usually have to go into xconfig, change my communication type to XDMCP-query and specify the ip/hostname of the client side (i.e. the s390 linux system). Another option made available on SLES-8 is use of vncserver. This may be the most versatile since it is simple to set up, starts you off with a (twm?) desktop environment and allows reconnection. It's resource usage is probably similar to xdm (not really sure). On the s390 linux system, just make sure the vncserver package is installed and issue "vncserver" from the command line of any regular session. By default, this usually starts display :1 on that system. For the NT side you need to find the vnc-3.3.3 r9_x86_win32.tgz package from the SLES-8 cd1 dosutils and somehow extract the vncserver.exe (either expand the tgz on a linux system, or use the untgz dosutils tool that also comes with the SLES-8 install cds). Once you have the vncserver.exe, just run "vncviewer linux.system.ip:1" and you should be able to connect to the vncserver you started on the s390 host. This worked for me on Win 2000. I assume the executable would work fine with NT. If not, you can also try to access the X display with the latest java enabled browser. The url would be something like http://linux.system.ip:5801 (this works for the most part, but seems to be prone to hanging; closing the browser and reconnecting usually restores the display okay). - Mark Ver Disclaimer: My email may say ibm, but these are my thoughts and my thoughts alone.
