AS/400 Emulation Technical Summary
Terminals emulated:
IBM 5251-11, 5291-1, 5292-2, 3196-A1, 3179-2, 3180-2, 3477-FG, and 3477-FC
Terminal emulation features:
- Multiple, simultaneous sessions to different hosts
- Scalable fonts/resizable windows, including Full Screen mode
- Choice of screen fonts
- Full Drag & Drop keyboard mapping - you can map any key from the emulated terminal onto any key on your Macintosh keyboard
- On-line help and Balloon Help
- Choice of background and text colors
- Color mapping
- Movable status bar
- WatchMe automatic macro script recorder
- Drag & Drop, HotKeys, HotSpots, keyboard macros, custom session or floating toolbars
- Text attribute mapping - you can make host text attributes on the terminal appear with the text attributes and color that you prefer
Character sets:
- 18 National Replacement Character sets
File transfer methods supported:
- FTP (Via web browser or third party FTP Client)
Connections methods supported on:
- Telnet over TCP/IP
- TCP/IP over PPP dial in connection
- Serial or USB connection
- Any third party CTB connection tools (Macintosh only)
5250E support
WebTerm conforms to the RFC 2877 (“5250 Telnet Enhancements”) specification, published in July 2000. This updated specification of the TN5250 protocol enables clients (such as WebTerm) to negotiate both terminal and printer Device Names through “Telnet Environment Options Negotiations” defined in RFC 1572.
Enabling & Inhibiting Extended Mode
Extended Mode is enabled by default. If your host requests that 5250E be used, WebTerm responds willingly unless you have changed the default settings and inhibited this mode. Most hosts will still allow the connection if you choose to Inhibit Extended Mode, but features made possible by 5250E (printing, for example) may not be available. You probably should not use the Inhibit option unless you are trying to work around known problems. The Inhibit Extended Mode setting is located in the Telnet Options section of the Telnet dialog.
Terminal Device Naming
To specify a device name for a terminal session, use the Display Name field found in the Telnet dialog in WebTerm Administrator. This parameter is given to the host during the telnet negotiation process if 5250E mode is in effect. The host may choose to accept this name. If it chooses not to, it may specify another name or reject the session completely (and disconnect). In the generic AS/400 login screen, the device name ultimately given to the session is visible in the “DISPLAY….” field, normally in the top right of the screen. If the name you specified is visible there, then the name requested has been used; otherwise the host has decided to use another name.
Note that opening multiple sessions with the same Display Name setting may not be allowed by the host. A typical result of attempting to create a new session with a Display Name that is already in use is a disconnected session. To avoid this problem, either do not specify a device name (taking the name assigned by the host), or create a separate session file for each session required to run simultaneously.
5250E Printing
The enhancements for 5250E provide for a “companion” printer session so that display sessions can print to a local printer on the PC. WebTerm’s print module (which also handles the 3270-standard “IBM 3287” printer) supports the 5250-standard “IBM 3812” printer. As with 3287 printing (but unlike VT terminal printing) 3812 print sessions use a second Telnet stream for the printer session, running independently of the display stream. To use WebTerm’s IBM 3812 printer in conjunction with a 5250 session, turn on the companion printer option and provide a device name for this session. Both of these parameters are configured in the General Terminal Settings panel for 5250 sessions.
After establishing a display session, WebTerm opens the companion print session if so configured, and print jobs on the AS/400 can be directed to the device name specified for the printer (NOT the Display Name). WebTerm’s print module handles the incoming print data, formats it appropriately for your locally configured printer, and present the standard Windows print dialog to the user before printing the job. The Print stream employs the same security scheme used in the companion display stream, so if SSL or SSH are used for the display session, they are also used for the print session.
|
|
