> From: Beverly Wilson > I'm not even certain that Viaduct supports login > scripting. It probably does, but I've not looked at it > for much beyond data import/export scripting.
It does. ViaDuct was my favorite emulator in the early 90's until I found wIntegrate, and that was my favorite until the later 90's when I found AccuTerm. :) All support scripting. The problem is that they're all different. So if you send ESC:"FOO" to any one of the emulators, it might do something nice or it might lock it up. That's the chance you take and fine-tuning the scripts to play nice if they hit the wrong emulator is what I call "the hard way". You may get it right with some experimenting but it could be time consuming to get it just right. > If I understand how the "easy way" would work, the > user would ask for a new connection/login from the > emulator. In response, the emulator runs a script, > prompting for userid, password, then passing it to the > server. As I see it, no emulator scripts are required. However, if you're already using scripts, then sure, you can do all of this automatically. I'm sure someone here can offer services to script this out with you. Without using scripts - Every site is different, but generally a user will open the emulator, see a login prompt, then manually enter user/password. What I'm suggesting is one of at least three methods: 1) When the user does a login with their user/psw, rather than putting them into MAIN, your user can manually or automatically connect into a different account which will then save their terminal preference. 2) Let users login with a different ID depending on their emulator (I don't like this but it's easy). 3) When they login, just display a prompt for which emulator they're using. The setting or prompt can be in a .profile or similar server-side config file. That's not all that elegant, and sure we want to automate such things, but sometimes the fastest and cheapest solution is to just ask the user a simple question rather than trying to make the environment smart enough to figure it out. Using the above methods, you don't need to worry about scripts in the clients - everything is on the server and there aren't any new security issues. I hope that helps. If you email I'll be happy to take this offline. I won't do the scripting but perhaps we can chat out the best solution for your environment. Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
