USER GUIDE
Version 2.6
See chapter 5 for a description of how to use and define function keys
------------------------------------------------------------------------- TN <line state> <session state> <insert mode> <last key> -------------------------------------------------------------------------
X-WRONG INPUT :
User enters data which is not legal. As an
example if the cursor is not placed on an
input field. If non numeric data is entered in a
numeric field the text "(numeric)" is added to
X-WRONG INPUT.
Move the cursor or press RESET, to release the error
situation. On a real 3270 screen, the user must
press the RESET key.
The most useful mode will in most cases be mode 2 (applet).
where
Mocha TN3270 will pop up as a window frame, which is movable, and also can be scaled on the page.
If the signed CAB file version is use, it is possible with IE 4/5 to overrule the security limitation. See file TN32703.HTML
Following syntax is used in this chapter:
# This is a comment line
name=value
Example of a simple file:
#Configuration file for Mocha TN3270
color_cursor=#203048
keyboard_bar=true
keyfile=keys.new
The different types of names are given in chapter 4.3 - 4.24.
<HTML> <HEAD> <TITLE> Mocha TN3270 example </TITLE> </HEAD> <BODY> <APPLET CODE="tn3270.class" WIDTH=700 HEIGHT=500> <param name=host value="ibm"> <param name=port value="23"> <param name=color_cursor value="#203047"> <param name=keyboard_bar value="true"> <param name=type value="applet"> </APPLET> </BODY> </HTML>CODE parameter must always be "tn3270.class". It is the name of the master file for the binary Mocha TN3270 product. WIDTH and HEIGHT gives the size of the applet. If running in mode 3 as a pop-up window, state the WIDTH and HEIGHT to 1.
Just as for the configuration file in chapter 4.1, each parameter is build of a name and a value. In the example above parameter host is given value ibm. It is very important to remember <> around each line, and the value must be surrounded with "".
Syntax:
Frame is a pop-up window.
Syntax:
Syntax:
Syntax:
Syntax:
Default is false.
Syntax:
Default is true.
SYNTAX:
Default is false.
Syntax:
where
The syntax is the same as used in the HTML language.
Example:
Syntax:
where
The syntax is the same as used in the HTML language.
Example:
Syntax:
where
The syntax is the same as used in the HTML language.
Syntax:
where
The syntax is the same as used in the HTML language.
Syntax:
Default is 600 x 600.
Syntax:
Default is 100,75.
Syntax:
Default port is 23. The host name can either be a name or an Internet address as 198.66.23.11
Syntax:
Default is true.
Syntax:
Default is IBM-3278-2-E
SYNTAX:
Default is 32
SYNTAX:
Default is false
Either Mocha W32 TN3270 can be configurated to use SOCKS Version 4 protocol, or it can be defined to send an ASCII connect sequence to the Proxy Telnet Server.
SYNTAX:
proxy_syntax defines how to format the connect sequence send to the proxy host.
Example:
Mocha TN3270 will connect to myproxy port 911, and send the connect sequence: <LF>Connect wintermute:23<CR><LF>
It is also possible to enter the login sequence to the proxy host from the keyboard. Just define the value of proxy_syntax as "\015" or " ".
From version 1.5 of Mocha TN3270 it is possible to use the SOCKS protocol.
Use parameters
proxy_socks=true
proxy_port=1080
If SOCKS protocol is used, Proxy Syntax can be left unused. Any text in this field is send as USERID in the SOCKS Connect request. Some proxy servers uses this field as identification, and Guest could be a possible entry.
As the use of a host name, which must use DNS to be resolved can give a security violation in the browser, it is a good idea to define the parameter host as a raw ip address, as 152.1.1.1.
SYNTAX:
name=ebcdic_file value=<file name>
Default is tn3270.ebc
green | : unprotected normal intensity |
red | : unprotected intensified |
blue | : protected, normal intensity |
white | : protected, intensified |
Modern applications can use extended attributes, which gives even more colors.
SYNTAX:
where
SYNTAX:
Default is Courier
SYNTAX:
Default is false
The default configuration file is named "keys", and should exist in the same catalog as the *.class files of Mocha TN3270.
Syntax for file "keys":
The pc-key's are:
fxx | : xx is 1 .. 12 | (function key f1 - f12) |
Fxx | : xx is 1 .. 12 | (shift + function key f1 - f12) |
cfxx | : xx is 1 .. 12 | (ctrl + function key f1 - f12) |
CFxx | : xx is 1 .. 12 | (shift + ctrl + function key f1 - f12) |
HOME | ||
END | ||
PGUP | ||
PGDN | ||
ESC | ||
RETURN |
PF1 - PF24 | |
INSERT | |
ERASEF | (erase current field) |
ERASEINPUT | (erase all input fields) |
CLEAR | (clear the screen, and inform the host about it) |
STARTF | (go to start of current field) |
ENDF | (go to end of current field) |
BTAB | (go to previous field) (normal shift TAB will also work) |
TAB | (go to next field) (normal TAB key will also work) |
NL | (go to first field on next line) |
RESET | (reset keyboard) |
ENTER |
Example of a "keys" file:
# TN3270 keymap # # <pc - key> <3270 key> f1 PF1 f2 PF2 cf5 INSERT cf6 ERASEF cf7 ERASEINPUT cf8 CLEAR ..
pc-Key 3270-key pc-key 3270-key ----------------------- ----------------------------- f1 PF1 crtl f1 PA1 f2 PF2 ctrl f2 PA2 f3 PF3 ctrl f3 PA3 f4 PF4 ctrl f4 - f5 PF5 ctrl f5 INSERT f6 PF6 ctrl f6 ERASE FIELD f7 PF7 ctrl f7 ERASE INPUT f8 PF8 ctrl f8 CLEAR f9 PF9 ctrl f9 - f10 PF10 ctrl f10 - f11 PF11 ctrl f11 PF10 f12 PF12 ctrl f12 PF22 pc-Key 3270-key pc-key 3270-key ----------------------- ----------------------------- shift f1 PF13 crtl shift f1 - shift f2 PF14 ctrl shift f2 - shift f3 PF15 ctrl shift f3 - shift f4 PF16 ctrl shift f4 - shift f5 PF17 ctrl shift f5 - shift f6 PF18 ctrl shift f6 - shift f7 PF19 ctrl shift f7 - shift f8 PF20 ctrl shift f8 - shift f9 PF21 ctrl shift f9 - shift f10 PF22 ctrl shift f10 - shift f11 PF23 ctrl shift f11 - shift f12 PF24 ctrl shift f12 -'-' is not used.
pc-Key 3270-key ------------------------ HOME GOTO START FIELD END GOTO END OF FIELD PGUP BACK TAB PGDN TAB ESC RESET KEYBOARD
The syntax of the file is :
# This is a comment
<ebcdic value> <ascii value>
Example:
# part of a file 40 20 81 a 82 b 83 c 84 d
Remark it is possible to write ASCII value either as a 2 digit hex number or an ASCII character. In the example a hex value 0x83 from the Host is translated to ascii character 'c'.
If identical ASCII values are defined for more than one ebcdic character, the last will be valid, when translating from ASCII to ebcdic. If as an example ebcdic 0x50 should be translated to an ASCII space it is important to put the line
0x50 0x20
before
0x40 0x20
Otherwise Users input when pressing the space bar will be wrong. A value of 0x40 should be expected.
Mocha TN3270 comes with 2 layouts:
See also 4.22, parameter ebcdic_file.
0 1 2 3 4 5 6 7 8 9 A B C D E F 0 SP SP & - { } \ 0 1 / a j ~ A J 1 2 b k s B K S 2 3 c l t C L T 3 4 d m u D M U 4 5 e n v E N V 5 6 f o w F O W 6 7 g p x G P X 7 8 h q y H Q Y 8 9 ` i r z I R Z 9 A ! | : B . $ , # C < . % @ D ( ) _ ' E + ; > = F | - ? "SP = space
0 1 2 3 4 5 6 7 8 9 A B C D E F 0 SP SP & - æ å \ 0 1 / a j A J 1 2 b k s B K S 2 3 c l t C L T 3 4 d m u D M U 4 5 e n v E N V 5 6 f o w F O W 6 7 g p x G P X 7 8 h q y H Q Y 8 9 ` i r z I R Z 9 A # ø : B . Å , Æ C < * % Ø D ( ) _ ' E + ; > = F ! ^ ? "
SP = space
If parameter "license_key" is not given, the program will run in Demo mode, and display a banner in the title line. There will be no limitations on functionality.