ANNOYING Shortcut problem in Windows

At my job I can connect to a mainframe for CICS access OR Unix System Services (via Hummingbird). The only difference in getting to one or the other is the TCP Port setting in Session Properties. I tried setting up two shortcuts on my desktop (which of course started out with the same TCP Port). I then edited the Session Properties for one shortcut, changed the TCP Port, and saved. You guessed it, the properties for the other shortcut were changed also.

Bottom line, Microsoft, they’re ought to be a way to set up two icons that differ only in port number, so if I want to go the CICS I can click on one, and if I want to go to USS I can click on the other, thus saving me from having to edit the Session Properties every time I want to switch.

Anyone know what it is?

Sounds more like a Hummingbird issue than anything Windows is doing wrong. You appear to have two shortcuts pointing to exactly the same thing, so naturally they share the same settings. But, perhaps with Hummingbird you can save the settings in files and then modify each shortcut to load the appropriate settings. Assuming you’re talking about the Host Explorer product, a quick Google on “host explorer” “command line options” finds this page which suggests that you can.

Are you using Hummingbird for both the mainframe and Unix?

“Session Properties” is something that belongs to Hummingbird - None of my desktop shortcuts for PuTTY or Attachmate have properties like that - they just point to a connectoid in the application’s directory. I’m guessing your shortcuts are actually pointing to the same thing in Hummingbird, which is why you have to diddle with ports each time.

Thanks.

Now for another problem. When I get to USS, nothing that I type is displayed. Commands work, I just can’t see them when I type. Also, when I try vi, I get an error something including the words “disabled for cursers” (don’t have the error in front of me now), and vi will not work. Can I fix this with say the display or terminal properties?

Actual error message: “Terminal dumb has insufficient capabilities for Curses.”

“All your base…” anyone?

Is there an I.T. support department at your company?

All curses are disabled for Vi, otherwise the whole mess would have shrivelled up and blown away under a hail of curses years ago.