Across the Boards
Communications Device Drivers
Section 6 - MAINCON Driver Configuration
Page 224
cfSOFTWARE Confidential,
2000
6.2 MAINCON Panel A2, APPX and Troubleshooting (continued)
__________________
ACROSS-THE-BOARDS(r) Config
__________________
Page 2 of 2
--- Communications Trouble Shooting ---
Safe-character mode..................... N
Flicker check time (in 100ths second)... 0
Transaction via Keystroke............... N
Protocol Converter Send Options......... 0
APPX Block Size......................... 0
Reliable Link Pacing.................... 0
Maximum enter key retries............... 0
Duplicate protocol converter confirm.... N
N=Normal mode (default), Y=safe mode on, A=auto detect. Safe mode uses only
common characters to avoid 3270 translation problems. Safe mode is slower.
F10: write config to disk Esc: Exit PgUp: prior page
8. Safe Character Mode
Setting this switch to ‘Y’ will force APPX to connect in Disty/Safe Character mode. Setting ‘A’ allows
APPX to auto-drop to Dirty/Safe Character mode if needed. The default is ‘N’ (no Dirty/Safe Character
mode). This field may be overridden by the PPX-DIRTY-MODE field in the APPX control block.
See the
APPX Programmer’s Guide for a description of Dirty/Safe Character mode
.
9. Flicker Time
When transfering data over LU 2 type links, APPX will wait a specific amount of time after all other
indications that the data block has been received properly to insure that the mainframe and controller are
really done updating the 3270 buffer. This “Flicker Check” is normally dealt with automatically by code in
each device driver. In some cases, a longer flicker check is required. If this field is set to zero, the default
flicker check is used. If set to a non-zero value, the flicker check will be for the number of hundredths of
seconds specified in this field. The valid range of values for this field is 0 through 255.
10. Transaction Only
Setting this switch to ‘Y’ will force APPX to always begin the connect process by sending the transaction
code as keystrokes. Normally, APPX will look at the current 3270 buffer to determine if it is a formatted
screen, and if it is, APPX will send the transaction code as keystrokes. On an unformatted screen, APPX
will send the entire handshake immediately. In some environments this can be a problem. For example, if a
protocol converter being used (so that attributes are never visible), and the host environment has a character
defined in such a way as to cause the connect block to be rejected by the system (for example, if the CMS
command delimter is defined as one of the characters in the connect block, CMS will attempt to interpret
the connect block, and cause an error). Setting this switch to ‘Y’ may slightly lengthen the connect process,
but will prevent the host operating system from attempting to interpreting the connect block.
(24 páginas)
(26 páginas)
(16 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais