Tag Archives: unix server

Mainframe Printing Method

(Where do I change my printer settings?)

Normally a user requests a print job from her terminal session, but that does not mean the Winet terminal program will handle print job. There are usually three methods that a mainframe or Unix server can use to get a report or job to print at your PC using Winet.

  1. The print job is sent to the Winet LPD print server program using the selected queue setup.
  2. The print job is sent to the Winet (socket or IP) Print Server program.
  3. The print job is sent to the Winet terminal program (E.g. InetVTx00 or Inet3270) using either

  1. the “80 Column Host Printer” setup (primary or default jobs)
  2. the “132 Column Host Printer” setup (secondary or compressed jobs)
  3. the “RTF Host Printer” setup (when RTF data is detected)

If you need to change something for your printer, you need to change it in the correct Winet program. So you need to know which Winet program receives the print jobs.

The easiest way to find out is to start both InetLPDHID_LPD_OVERVIEW and InetPrintServerHID_PRINTSERVER_OVERVIEW (socket), request a print job, and watch to see which program shows a new job or attempt to print. If the job prints with no activity in either print server, it is most likely your Winet terminal emulator (e.g. InetVTx00 or Inet3270) that has handled it.

Font changes:

Some types of printing don’t support font selections. Only with GDIPrintingTypeGDI (with Use Device Font not selected) and Inet FormatPrintingTypeInet (with Default Font used) you may specify the fonts from within Winet. (See Types of printing used by WinetPrintingTypes for more detail.)

See also some hints on configuring your 3287 printer3287printer.

More at:

Printing general informationPrintingGenInf and Multiple printing configurations (Which printer do I have to set up?) PrintingConfig.

Terminal Type and Configuration

Explanation of Terms

Winet comes with seven (7) terminal emulation programs: VTx00, 3270, 5250, T27, Uts60, HP, D211 (not all of them will be unlocked by your licence file). We like to call these the 7 different families of terminal emulators. Each program can be loaded with a configuration to specify some settings for this family to more closely emulate a certain old hardware terminal or to fit function key requirements of a specific application on the mainframe (or Unix server host).

E.g.: InetVTx00 comes with configurations to emulate VT100, VT220, VT300, ANSI, SCO-ANSI and a Linux console.

The title bar (top blue bar) of each emulator will display first the name of the Inet terminal emulation program and next the name of the active configuration.

Mostly when we talk of terminal type, we refer to the string (name) passed by telnet to the remote host (mainframe, server or Unix box), telling it which terminal you are using. This name will affect what type of instructions the host will send to your terminal and what it will expect of your terminal. The terminal type is a string that identifies the model of the terminal. The terminal type is one of the settings saved in a configuration and you may change it as required.

Depending on your Unix (or other) host, you might want to set the terminal type to something like vt220, VT100, ansi, ANSI or sco-ansi or whatever. (Unix is case sensitive.) A few popular options are listed in the drop down box under the Setup | Telnet | Terminal Type option in your terminal emulator, but you may also manually edit the strings as required.

You can easily create your own custom configurations by using the File | Save As option in your terminal emulator. You may have an unlimited number of configurations for each terminal emulator on your PC, connecting to the same or to different hosts (mainframes).

The configuration is used as a key in the registry to store all the settings for the emulator. The configuration to use is specified with the /t=configuration command line option in each short cut.

See also: