 |
» |
|
|
|
When Pass Thru is started, it looks for a configuration file
called PTCONFIG, which specifies your rolling softkeys and other
Pass Thru options. If this file is not found, the rolling softkeys
are assigned the default functions. If the PTCONFIG file is not
in your group and account, use a file equation to allow access to
another PTCONFIG file. See Appendix D “Sample PTCONFIG File” for a sample PTCONFIG file. | | | |  | NOTE: Pass Thru printer sessions run as system processes and,
therefore, always access PTCONFIG.PUB.SYS. If you specify a different PTCONFIG file (for
printer sessions), it will have no effect. | | | | |
You can use the PTCONFIG file to define all the functions,
levels, and labels for your terminal function keys. Define these
keys in a way that is most useful for you. When specifying function
keys with levels, remember to include the rolling and jumping functions
in each level to allow Pass Thru to change the level for you. If
you use terminals without shifted function key support (8-function
key terminals), define functions for eight function keys in your
PTCONFIG file. If you use terminals that support shifted function
keys (16-function key terminals), define functions for 16 function
keys. | | | | | NOTE: If you use both 8- and 16-function key terminals, make
sure you define the function keys for both types of terminals. The
example in Appendix D “Sample PTCONFIG File” of this manual shows a PTCONFIG
file for both 8- and 16-function key terminals. If you attempt to
use a terminal without first configuring the correct set of function
keys (8 or 16) in your PTCONFIG file, only the menu key for function
key one will appear on your terminal. | | | | |
Elements of the PTCONFIG File | |
This section describes all the softkey function definitions
and the options that may be included in the PTCONFIG file. - SOFTKEYS: n
Required. Function key set
selector. The value of n can be either
8 (for terminals with eight function keys) or
16 (for terminals with 16 function keys). Appendix C “Pass Thru Terminal and Printer Specifications” lists the number of function keys available for terminals that
are supported by Pass Thru. - *LEVEL n
Comment indicating the level of softkey functions.
The value of n can be an integer from 1 through 6, for terminals
with 16 function keys, or from 1 through 12, for terminals with
8 function keys. - BEGIN
Required. Level begin indicator.
All function key assignments listed before END are treated as one level. Those listed after
END belong to the next level of function keys. You
must put BEGIN and END statements around each level of softkey functions. - END
Required. Level end indicator.
Any function key assignments listed before END are treated as one level. Those listed after
END belong to the next level of function keys. You
must put BEGIN and END statements around each level of softkey functions. - Fn
Required. Function key indicator. The value of
n is an integer from 1 through 8. (Only F2 through F8 are allowed). - SFn:
Shifted function key indicator. The value of n is
an integer from 1 through 8. On terminals that support 16 function
keys, the [SHIFT] key can be used with the eight function keys to allow
an additional eight function keys. For example, the value
SF2 indicates the shifted function key, [SHIFT]-[f2]. - softkey function
A softkey function is the attention identifier (AID) or function of a
function key. The softkey functions provided by Pass Thru are listed
in Table 2-1 “Softkey Functions Provided by Pass Thru”. - softkey label
Optional function key label definition. If this
value is not specified, the system default will be used. The default
function key labels and functions are listed in Chapter 5 “Using Terminals with Pass Thru” Up to eight characters per function key are allowed.
Enclose this value in double quotes. - *OPTION
Comment describing the effects of the configured options. - option: option value
The PTCONFIG file options and their values are listed in Table 2-2 “PTCONFIG File Options for Null Translation”.
Table 2-1 Softkey Functions Provided by Pass Thru CLEAR | IBM 3278 [CLEAR] key. Moves the cursor to home position, clears the screen, and
sends a CLEAR KEY PRESSED message to the IBM host. | CLPRT | Closes the local print spool
file (LOGIMF) and prints it while your session is still active.
Then a new LOGIMF file is opened. This softkey function works independently
of the PTCONFIG PRT option, described later in this chapter. If you
need to send your output to a disc file instead of a spool file,
enter the following file equation at the MPE colon prompt before
you start your Pass Thru session: (This is the only file equation
that works. | | FILE LOGIMF,NEW;DEV=DISC;REC=-133,,,ASCII;NOCCTL;SAVE | EXIT | Ends Pass Thru for your terminal only
and returns the terminal to MPE control. | | LBNULL | Causes Pass Thru to convert leading blanks
to nulls for transmission to the IBM host. This function is equivalent
to the LB: NO option, described later in this section. See "Leading
Blanks, Trailing Blanks, and Trailing Nulls," later in
this chapter. | | LEVEL1 | Rolls the function keys to level 1. | | LEVEL2 | Rolls the function keys to level 2. | .
.
. | .
.
. | | LEVEL12 | Rolls the function keys to level 12, if level
12 exists. If level 12 does not exist, this function rolls the function
keys over to level 1. | | MENU | Displays the Pass Thru softkey menu and
prints this prompt on your terminal's screen: ENTER 1-24, PA1, PA2, PA3, CLEAR, SRK, PRINT, CLPRT, and EXIT. Answer this prompt by entering the number of
an IBM PF key or the character string for the softkey you want. | | MPEXLCIP | SNA IMF/XL only.
Suspends your Pass Thru session and creates an MPE XL command interpreter
process. A colon prompt will appear on your screen, and you can
enter MPE commands. To return to your suspended Pass Thru session, type EXIT at the MPE colon prompt. See "Using the
MPE Command Interpreter from Pass Thru," in Chapter 5 “Using Terminals with Pass Thru” | | NEXT | Rolls the function keys to the next level. | | PA1 | IBM 3278 [PA1] (program aid 1) key. | | PA2 | IBM 3278 [PA2] (program aid 2) key. | | PA3 | IBM 3278 [PA3] (program aid 3) key. | | PF1 | IBM 3278 [PF1] (program function 1) key. | | PF2 | IBM 3278 [PF2] (program function 2) key. | .
.
. | .
.
. | | PF24 | IBM 3278 [PF24] (program function 24) key. | | PRINT | Sends a copy of the internal
screen image to a spooled output file called LOGIMF. The format
of the internal screen image is determined by the format parameter you specify in the info string when you start
Pass Thru. This function is equivalent to the IBM 3278 local print
key. | | If you need to send your
output to a disc file instead of a spool file, enter the following
file equation at the MPE colon prompt before you start your Pass
Thru session: (This is the only file equation that works.) | | FILE LOGIMF,NEW;DEV=DISC;REC=-133,,,ASCII;NOCCTL;SAVE | | RESET | The IBM 3278 [RESET] key. This function unlocks the keyboard and enables input.
This function issues the RESET3270 intrinsic, described in the SNA IMF Programmer's
Reference Manual. | | STATUS | Displays status information about your
LU-LU session. See "Displaying SNA Session Status Information," in Chapter 5 “Using Terminals with Pass Thru” | | SRK | BM 3278 [SYS REQ] (system request) key. Sends a special protocol sequence
to the SSCP. | | TBNULL | Causes Pass Thru to send trailing blanks for
non-null characters sent by the host. This function is equivalent
to the TB: YES option, described later in this section. See "Leading
Blanks, Trailing Blanks, and Trailing Nulls," later in
this chapter. | | TNBLANK | Causes Pass Thru to convert trailing
nulls to blanks before sending data to the host. This function is
equivalent to the TN: YES option, described later in this section. See "Leading
Blanks, Trailing Blanks, and Trailing Nulls," later in
this chapter. |
See Table 2-2 “PTCONFIG File Options for Null Translation” for PTCONFIG file options. Leading Blanks, Trailing Blanks, and Trailing Nulls | |
IBM terminals make a distinction between null characters and
blanks. The HP 700/94 terminal now has a ROM module (part #5062-1306)
that allows it to support null characters, but all the older HP
terminals represent null characters as blanks. Because older HP
terminals cannot type nulls or distinguish between nulls and blanks
in terminal memory, SNA IMF provides several softkey functions and
PTCONFIG file options to help resolve any communication difficulties
caused by null character translation. | | | | | NOTE: If you are using an HP 700/94 terminal with the ROM
module for null support, you do not need any of the softkey functions
or PTCONFIG file options described in this section. | | | | |
Table 2-2 “PTCONFIG File Options for Null Translation” lists the PTCONFIG file options
that affect null character translation. Table 2-2 PTCONFIG File Options for Null Translation PTCONFIG File Option | Effect |
|---|
TB: YES (default) | Transmits trailing blanks for each non-null
character that has been modified with a blank before transmitting
the data to the host. | TB: NO | Converts all trailing blanks to nulls
on a field-by-field basis before transmitting data to the host. | LB: YES | Transmits leading blanks as they are
read from the HP terminal screen on a field-by-field basis. | LB: NO (default) | Converts leading blanks to nulls on a
field-by-field basis before transmitting the data to the host. | TN: YES | Converts trailing nulls to blanks before
sending the data to the host. | TN: NO (default) | Has no effect, since the user cannot
type nulls. |
Table 2-3 “Softkey Function for Null Translation” lists the softkey functions that
affect null character translation. It also lists, for each softkey
function, the PTCONFIG file option that has the same effect. Table 2-3 Softkey Function for Null Translation Softkey Function | Effect | Equivalent PTCONFIG File Option |
|---|
LBNULL | Converts leading blanks to nulls on a
field-by-field basis before transmitting the data to the host. | LB: NO | TBNULL | Transmits trailing blanks for each non-null
character that has been modified with a blank before transmitting the
data to the host. | TB: YES | TNBLANK | Converts trailing nulls to blanks before
sending the data to the host. | TN: YES |
The state of the LBNULL, TBNULL, and TNBLANK softkeys overrides the values specified for the LB, TB, and TN options in your PTCONFIG file. If an asterisk
appears on your terminal screen next to the softkey label, the softkey
function is turned on. To turn it off, press the softkey, and the
asterisk will disappear. To turn it back on, press the softkey again. When the LBNULL softkey is turned on, it overrides the BLANKS parameter specified in the info string of the RUN TTSSON command that starts Pass Thru. The BLANKS parameter in the info string has the same effect as
the LB: YES option in the PTCONFIG file. The TB and TN options cannot be specified in the info string.
See Chapter 3 “Starting Pass Thru” In operations that use both the TB and LB options, the TB option is always processed before the LB option. Using both options can affect the integrity
of a null or blank field. See Table 2-4 “Interaction of LB, TB, and TN Options” for information
on how the LB, TB, and TN options interact. LB, TB, and TN Options with MDT and Non-MDT TerminalsThe LB, TB, and TN options can have different effects, depending
on whether you are using an MDT (Modified Data Tag) terminal or
a non-MDT terminal. (See Appendix C “Pass Thru Terminal and Printer Specifications” for a list
of MDT and non-MDT terminals that can be used with Pass Thru.) An MDT terminal has a tag associated with each field on the
screen. When you type data into a field, the tag is set to indicate
that data in that field has been modified. Then, when the HP 3000
receives data from the MDT terminal, it transmits to the IBM host
only the data that has been modified. The fields in a non-MDT terminal screen have no tags to indicate whether
the data in them has been modified. When the HP 3000 receives
data from a non-MDT terminal, it compares each field with its corresponding
field in the internal screen image to see if any data has been changed.
Then, it transmits to the IBM host any data that differs from the
data in the internal screen image. When the IBM host sends null characters, the nulls are translated
to blanks for your HP terminal. If you are using a non-MDT terminal,
and you type some blanks into a field that previously contained
nulls, the HP 3000 compares the data from your terminal
with the internal screen image and finds no difference. The data
appears to be unchanged, so the HP 3000 transmits no data
to the IBM host. | | | | | NOTE: A ROM module (part #5062-1306) is now available for
the HP 700/94 terminal that allows it to support nulls just as an
IBM 3278 display station does.If you are currently using non-MDT terminals, you should
consider upgrading to MDT terminals. MDT terminals will transmit
blanks that have been typed over nulls. They will also improve performance, because
data from the terminal does not have to be compared with the internal
screen image before it can be sent to the host. | | | | |
Figure 2-1 “3270 Request/Response Unit (RU)” shows part of an RU (Request/Response
Unit) that the HP 3000 sends to the IBM host during a Pass
Thru session. The AID and the cursor position are always transmitted, even
if no data is being sent. Therefore, when "no data" is
sent to the IBM host, it means that only the AID and cursor position
are sent. If the Set Buffer Address order and the field address are
transmitted along with the AID and cursor position, but no Start
Field order follows the field address, the IBM host interprets it
as the ERASE EOF function and erases the field (fills it with nulls).
See Appendix E “3270 Bit Assignment and Character
Translation Tables” for AID codes and 3270 Buffer Control
Orders. Figure 2-1 3270 Request/Response Unit (RU) Table 2-4 “Interaction of LB, TB, and TN Options” shows the interaction among the
LB, TB, and TN options on MDT and non-MDT terminals. The first
column is the data that the HP 3000 receives from the IBM
host. The second column is the data that the user types over the
data from the host. The third and fourth columns show what the HP 3000
transmits back to the IBM host after the user at the terminal types
in data and presses the [ENTER] key. The third column is from an MDT terminal, and the
fourth column is from a non-MDT terminal. Legend for Table 2-4 “Interaction of LB, TB, and TN Options”: ABC = the non-null, non-blank data transmitted by the host.
XYZ = the non-blank data typed by the user.
~ = null
^ = blank | | | | | NOTE: In Cases 6 and 8 (LB: YES and TN: YES), if a non-MDT terminal user presses the [ENTER] key after receiving host data and before typing any new
data, a field of nulls ("~~~~~~~") received from
the IBM host will be transmitted back to the host as a field of
blanks ("^^^^^^^"). The data is changed whether
or not the user types anything into the field. | | | | |
In Cases 5 and 6, when TB: NO and TN: YES are specified, an MDT terminal can emulate the
ERASE EOF function by typing "^^^^^^^" (a field
of blanks). ERASE EOF causes the IBM host to erase everything in
the field (replace it with nulls). Table 2-4 Interaction of LB, TB, and TN Options | Data Received from IBM Host | Data Typed at HP Terminal | Data Sent to Host from HP MDT Terminal | Data Sent to Host from HP non-MDT Terminal |
|---|
Case # 1: LB: NO TO: NO TN: NO | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ XYZ XYZ ^^^^^^^ XYZ XYZ XYZ ^^^^^^^ | XYZ XYZ XYZ No data XYZ XYZ XYZ No data | Case # 2: LB: YES TO: NO TN: NO | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ ^^XYZ ^^^^XYZ ^^^^^^^ XYZ ^^XYZ ^^^^XYZ ^^^^^^^ | XYZ ^^XYZ ^^^^XYZ No data XYZ ^^XYZ ^^^^^XYZ No data | | Case # 3: LB: NO TO: YES TN: NO | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ XYZ XYZ ^^^^^^^ XYZ^^^^ ^^XYZ ^^^^XYZ ^^^^^^^ | XYZ XYZ XYZ No data XYZ^^^^ XYZ^^ XYZ^^ No data | Case # 4: LB: YES TO: YES TN: NO | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ ^^XYZ ^^^^XYZ ^^^^^^^ XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ | XYZ ^^XYZ ^^^^XYZ No data XYZ^^^^ ^^XYZ^^ ^^^^XYZ No data | Case # 5: LB: NO TO: NO TN: YES | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ XYZ^^ XYZ ^^^^^^^ XYZ XYZ XYZ ERASE EOF | XYZ^^^^ XYZ^^ XYZ No data XYZ XYZ XYZ No data | Case # 6: LB: YES TO: NO TN: YES | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ XYZ ^^XYZ ^^^^XYZ ERASE EOF | XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ XYZ ^^XYZ ^^^^XYZ No data | Case # 7: LB: NO TO: YES TN: YES | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ^^^^ XYZ^^ XYZ ^^^^^^^ XYZ^^^^ XYZ^^ XYZ ^^^^^^^ | XYZ^^^^ XYZ^^ XYZ No data XYZ^^^^ XYZ^^ XYZ No data | | Case # 8: LB: YES TO: YES TN: YES | ABC~~~~~~ABC~~~~~~ABC~~~~~~~ABC^^^^^^ABC^^^^^^ABC^^^^^^^ | XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^XYZ^^^^^^XYZ^^^^^^XYZ^^^^^^^ | XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ | XYZ^^^^ ^^XYZ^^ ^^^^XYZ ^^^^^^^ XYZ^^^^ ^^XYZ^^ ^^^^XYZ No data | ABC = host-transmitted data XYZ = data typed by the user ~ = null ^ = blank |
General PTCONFIG File Rules | |
The following general rules apply to the PTCONFIG file: Invalid softkey functions are not accepted. If you specify an invalid softkey function, an error message will appear. You must specify a function key set selector (
SOFTKEYS: 8 or SOFTKEYS: 16) at the beginning of each set of function key assignments.
All function key assignments following the SOFTKEYS set selector are treated as one set until another
SOFTKEYS set selector appears. A terminal with 16 function keys can have a maximum
of 6 levels of softkey functions. A terminal with eight function
keys can have a maximum of 12 levels of softkey functions. Each level of softkey functions is enclosed by
BEGIN and END. The option assignment (option: option value) can appear anywhere. Comments are preceded by an asterisk (*). Characters
between the asterisk and the end of the line are ignored. Blank
lines are ignored and can be used to separate statements. You cannot assign a function to the [f1] key; it is reserved for the menu key. However, if your
terminal supports shifted function keys, you can assign a function
to the shifted [f1] key. If the PTCONFIG file defines only SOFTKEYS:8, and you use Pass Thru on a terminal that supports
16 function keys, the menu key will be the only usable softkey.
To avoid potential problems, always define both 8- and 16-function
key sets in your PTCONFIG file.
| | | | | NOTE: Pass Thru always reserves the [f1] key for the menu key and overwrites whatever you may have
defined for [f1] in the PTCONFIG file. | | | | |
Asian PTCONFIG File Considerations | |
The following considerations apply to PTCONFIG files created
for Asian language users. When Pass Thru is started, the program looks for a file named PTCONFIG,
which specifies your rolling softkeys and other Pass Thru options.
If this file is not found, the softkeys are labeled with the default functions.
The default softkey labels are in American English. If you want
localized softkey labels, you must specify the labels in the PTCONFIG
file. The localized 16-bit label (or mixed 8- and 16-bit label) can
be up to 8 bytes long (or 4 DBCS characters long). | | | | | NOTE: ASIAN USERS: Only the softkey label and comments in the PTCONFIG file may be translated
into native language. The rest of the PTCONFIG file must remain
in English. | | | | |
Here is an example of a small PTCONFIG file: SOFTKEYS:8 *LEVEL ONE | | | BEGIN | | F2:SRK | "localized label" | | F3:CLEAR | "localized label" | F4:PRINT | "localized label" | F5:CLPRT | "localized label" | F6:STATUS | "localized label" | | F7:TBNULL | "localized label" | F8:EXIT | "localized label" | END | |
You can customize the softkey labels by typing the localized label between the quotation marks (as shown in the above
example) with an editor, using an Asian terminal in its Asian mode. The softkey label is limited to 8 bytes or 4 DBCS characters
in length. Mixing of 8- and 16-bit data is also allowed when the
label does not exceed 8 bytes. See Appendix D “Sample PTCONFIG File” for
an example of a PTCONFIG file. English and Asian Language SupportEnglish-only applications are supported when the DBCS: YES option is specified in the PTCONFIG file. However,
if you are using English-only applications, set Pass Thru to use
a PTCONFIG file that specifies DBCS: NO. This practice ensures that your English-only
applications perform at their best. Use separate PTCONFIG files
to support English-only and Asian-only applications. Use file equations
to redirect one of the PTCONFIG files. Here are some examples: To run English-only Pass Thru, specify the following: :FILE PTCONFIG.PUB.SYS=PTCONFIG.PUB.SYS :RUN TTSSON.PUB.SYS;INFO="CONFIG=node#class;DEVID=T" To run Asian Pass Thru, specify the following: :FILE PTCONFIG.PUB.SYS=PTCONFIG.ASIA.SYS or :FILE PTCONFIG.PUB.SYS=PTASIA.PUB.SYS :RUN TTSSON.PUB.SYS;INFO="CONFIG=node#class;DEVID=T" |
