HP 3000 Manuals HP 3000 Manuals
The PTCONFIG File When Pass Thru is started, it looks for a configuration filecalled PTCONFIG, which specifies your rolling softkeysand 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 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 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.
PTCONFIG File Syntax The following illustrates the syntax of the PTCONFIG file. Items in slanted type are replaced by user-supplied values. Items in square brackets are optional. The curly braces around the SOFTKEYS values indicate that you must select one of them. The next section in this chapter, "Elements of the PTCONFIG File," explains all the items in the syntax illustration. See appendix D for a sample configuration file. ___________________________________________________________ | | | SOFTKEYS: {8} | | {16} | | | | *LEVEL n (Comment, not part of the required syntax.)| | BEGIN | | Fn: softkey function ["softkey label"] | | Fn: softkey function ["softkey label"] | | . | | . | | . | | SFn: softkey function ["softkey label"] | | SFn: softkey function ["softkey label"] | | . | | . | | . | | END | | | | *LEVEL n (Comment, not part of the required syntax.)| | BEGIN | | . | | . | | . | | END | | | | *OPTIONS (Comment, not part of the required syntax.)| | option: option value | | option: option value | | . | | . | | . | ___________________________________________________________
NOTE ASIAN USERS: Only the softkey label and comments in the PTCONFIG filemay be translated into native language. The rest of the PTCONFIG file must remain in English.
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 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 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. 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. 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 | | fileinstead 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 andprints 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. | | | ------------------------------------------------------------------------------------------ Table 2-1. Softkey Functions Provided by Pass Thru (cont.) ------------------------------------------------------------------------------------------ | 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. | | | | 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. | | | ------------------------------------------------------------------------------------------ Table 2-1. Softkey Functions Provided by Pass Thru (cont.) ------------------------------------------------------------------------------------------ | SRK IBM 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. | | | ------------------------------------------------------------------------------------------ Table 2-2. PTCONFIG File Options ------------------------------------------------------------------------------------------ | | | Clear screen counter.The entire screen is repainted if the number of | | CLSCR: n rows modified by the host is greater than n. If the number of rows | | modified by the host is less than or equal to n, only the modified | | rows are repainted. The value of n can be from 0 through 43 lines. | | The default is 18 lines. The following values are recommended: 18 | | for 24-line screens, less than 10 for 12-line screens, and greater | | than 30 for 43-line screens. | | | | (for Asian users) Double-Byte Character Set indicator.Specifying | | DBCS: {YES} DBCS: YES allows Pass Thru to support Asian 16-bit DBCS | | {NO} functionality. Specifying DBCS: NO disables DBCS support. The | | default value is DBCS: NO. | | | | Keyboard enable timer. The value of n is the number of seconds the | | KET: n terminal will wait for a keyboard enable. The value of n can be | | from 0 through 28800 seconds. The default is 28800 seconds (eight | | hours). | | | | By specifying a KET value, you can limit the number of times the | | screen is repainted. An HP terminal screen might be painted up to | | three times before the final screen is painted if the host uses | | several transmissions to complete one screen. The recommended KET | | value is 30 seconds, which usually causes the screen to be painted | | only once. | | | | If you have set the KET, and the screen is still repainted more than | | once, it may be due to the IBM application that is currently running. | | | | Leading blanks. Specifying LB: YES causes Pass Thru to send leading | | LB: {YES} blanks as they are read from the HP terminal screen on a | | {NO} field-by-field basis. Specifying LB: NO causes Pass Thru to convert | | leading blanks to nulls, thus left justifying data in each field that | | contains leading blanks. LB: NO is the default and is equivalent to | | the LBNULL softkey function, described earlier in this chapter. | | | | For more information on leading blanks, and on the interaction | | between the LB, TB, and TN options, see "Leading Blanks, Trailing | | Blanks, and Trailing Nulls," later in this chapter. | | | ------------------------------------------------------------------------------------------ Table 2-2. PTCONFIG File Options (cont.) -------------------------------------------------------------------------------------- | The number of lines per page for SNA IMF printer emulation.The value | | PAGE: n of n can be from 1 through 99 for LU.T1 and LU.T3 printers. The | | default value is 1, meaning one line per page, which causes form | | feeds to be treated as new lines. Printing will continue on the next | | line instead of advancing to the next page. | | | | The SNA Character String (SCS)SVF (Set Vertical Format)control code | | may set the page length to values greater than 99 but less than or | | equal to 102 for LU.T1 printer emulation. See appendix B of this | | manual for more information about SCS control codes. | | | | The receive timer for the printer. The value of n is the number of | | PRT: n seconds Pass Thru will wait to receive printer data from the IBM | | host. If Pass Thru receives no data from the host before the timer | | expires, it closes the current spool file and opens a new one to | | continue receiving data from the host. The spool file can then be | | sent to the printer. This option allows you to obtain printer output | | while you are still in your Pass Thru session. The default PRT value | | is zero, which means that no timer has been set, and Pass Thru will | | wait indefinitely for data from the host. When using the default | | value, use the SEND CLOSE commandto close the spool file while the | | printer is active. See "Entering Printer Commands and Adjusting Page | | Length," in chapter 6. | | | --------------------------------------------------------------------------------------
NOTE If you do not specify the PRT option in the PTCONFIG file, spool files will not be closed until you issue the SEND CLOSE command, or until the Pass Thru session for the printer is cancelled, released, or unbound.
Table 2-2. PTCONFIG File Options (cont.) --------------------------------------------------------------------------------------------- | | | Trailing blanks. Specifying TB: YES causes Pass Thru to send trailing | | TB: {YES} blanks for non-null characters sent by the host. Specifying TB: NO | | {NO} causes Pass Thru to convert trailing blanks to nulls. TB: YES is the | | default and is equivalent to the TBNULL softkey function, described | | earlier in this chapter. | | | | For more information on trailing blanks, and on the interaction between | | the LB, TB, and TN options, see "Leading Blanks, Trailing Blanks, and | | Trailing Nulls," later in this chapter. | | | | TIMEOUT: n Specifies session timeout value in seconds. If Pass Thru receives no | | input from the terminal before n seconds have passed, the session is | | terminated. The value of n can be from 0 through 32000 seconds. The | | default is 0, indicating that no timeout will occur. | | | | Trailing nulls. Specifying TN: YES causes Pass Thru to convert | | TN: {YES} trailing nulls to blanks before sending data to the host. TN: NO has | | {NO} no effect and is the default. TN: YES is equivalent to the TNBLANK | | softkey function, described earlier in this chapter. | | | | See "Leading Blanks, Trailing Blanks, and Trailing Nulls," later in | | this chapter. | | | | Allows SNA IMF to send an UNBINDto the host, if the Pass Thru session | | UNBIND:{YES} is terminated while the LU-LU session is still active (bound). The | | {NO} UNBIND will be sent in place of the LUSTAT "device powered off." The | | UNBIND: YES option causes SNA IMF to send an UNBIND (type '01') if it | | terminates while an active LU-LU session exists. The spool file closes | | when an UNBIND is sent for LU.T1 and LU.T3 sessions. The default value | | is UNBIND: NO. To communicate with an IBM AS/400, UNBIND must be set to | | NO. | | | --------------------------------------------------------------------------------------------- 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-3 lists the PTCONFIG file options that affect null character translation. Table 2-3. PTCONFIG File Options for Null Translation ------------------------------------------------------------------------------------------ | | | PTCONFIG effect | | file option | | | | 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-4 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-4. Softkey Functions for Null Translation ------------------------------------------------------------------------------------------- | | | softkey function effect equivalent | | PTCONFIG | | file option | | | | LBNULL Converts leading blanks to nulls on a LB: NO | | field-by-field basis before transmitting | | the data to the host. | | | | TBNULL Transmits trailing blanks for each non-null TB: YES | | character that has been modified with a | | blank before transmitting the data to the | | host. | | | | TNBLANK Converts trailing nulls to blanks before TN: YES | | sending the data to the host. | | | ------------------------------------------------------------------------------------------- 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 parameterspecified 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-5 for information on how the LB, TB, and TN options interact. LB, TB, and TN Options with MDT and Non-MDT Terminals The 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 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.
NOTE 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 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 orderand the field address are transmitted along with the AID and cursor position, but no Start Field orderfollows the field address, the IBM host interprets it as the ERASE EOF functionand erases the field (fills it with nulls). See appendix E for AID codes and 3270 Buffer Control Orders.Figure 2-1. 3270 Request/Response Unit (RU) Table 2-5 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-5: ABC = the non-null, non-blank data transmitted by the host. XYZ = the non-blank data typed by the user. 0 = 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 ("0000000") 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 functionby typing "_______" (a field of blanks). ERASE EOF causes the IBM host to erase everything in the field (replace it with nulls). Table 2-5. Interaction of LB, TB, and TN Options --------------------------------------------------------------------------------------------- | | | Data received Data typed Data sent to Data sent to | | from IBM host at HP terminal host from HP host from HP | | MDT terminal non-MDT terminal | | | | Case #1: ABC0000 XYZ____ XYZ XYZ | | 00ABC00 __XYZ__ XYZ XYZ | | LB: NO 0000ABC ____XYZ XYZ XYZ | | TB: NO 0000000 _______ _______ No data | | TN: NO ABC____ XYZ____ XYZ XYZ | | __ABC__ __XYZ__ XYZ XYZ | | ____ABC ____XYZ XYZ XYZ | | _______ _______ _______ No data | | | | Case #2: ABC0000 XYZ____ XYZ XYZ | | 00ABC00 __XYZ__ __XYZ __XYZ | | LB: YES 0000ABC ____XYZ ____XYZ ____XYZ | | TB: NO 0000000 _______ _______ No data | | TN: NO ABC____ XYZ____ XYZ XYZ | | __ABC__ __XYZ__ __XYZ __XYZ | | ____ABC ____XYZ ____XYZ ____XYZ | | _______ _______ _______ No data | | | | Case #3: ABC0000 XYZ____ XYZ XYZ | | 00ABC00 __XYZ__ XYZ XYZ | | LB: NO 0000ABC ____XYZ XYZ XYZ | | TB: YES 0000000 _______ _______ No data | | TN: NO ABC____ XYZ____ XYZ____ XYZ____ | | __ABC__ __XYZ__ XYZ__ XYZ__ | | ____ABC ____XYZ XYZ XYZ | | _______ _______ _______ No data | | | | Case #4: ABC0000 XYZ____ XYZ XYZ | | 00ABC00 __XYZ__ __XYZ __XYZ | | LB: YES 0000ABC ____XYZ ____XYZ ____XYZ | | TB: YES 0000000 _______ _______ No data | | TN: NO ABC____ XYZ____ XYZ____ XYZ____ | | __ABC__ __XYZ__ __XYZ__ __XYZ__ | | ____ABC ____XYZ ____XYZ ____XYZ | | _______ _______ _______ No data | | | - - | ABC = host-transmitted data | | XYZ = data typed by the user | | 0 = null | | _ = blank | | | --------------------------------------------------------------------------------------------- Table 2-5. Interaction of LB, TB, and TN Options (cont.) --------------------------------------------------------------------------------------------- | | | Data received Data typed Data sent to Data sent to | | from IBM host at HP terminal host from HP host from HP | | MDT terminal non-MDT terminal | | | | Case #5: ABC0000 XYZ____ XYZ____ XYZ____ | | 00ABC00 __XYZ__ XYZ__ XYZ__ | | LB: NO 0000ABC ____XYZ XYZ XYZ | | TB: NO 0000000 _______ _______ No data | | TN: YES ABC____ XYZ____ XYZ XYZ | | __ABC__ __XYZ__ XYZ XYZ | | ____ABC ____XYZ XYZ XYZ | | _______ _______ ERASE EOF No data | | | | Case #6: ABC0000 XYZ____ XYZ____ XYZ____ | | 00ABC00 __XYZ__ __XYZ__ __XYZ__ | | LB: YES 0000ABC ____XYZ ____XYZ ____XYZ | | TB: NO 0000000 _______ _______ _______ | | TN: YES ABC____ XYZ____ XYZ XYZ | | __ABC__ __XYZ__ __XYZ __XYZ | | ____ABC ____XYZ ____XYZ ____XYZ | | _______ _______ ERASE EOF No data | | | | Case #7: ABC0000 XYZ____ XYZ____ XYZ____ | | 00ABC00 __XYZ__ XYZ__ XYZ__ | | LB: NO 0000ABC ____XYZ XYZ XYZ | | TB: YES 0000000 _______ _______ No data | | TN: YES ABC____ XYZ____ XYZ____ XYZ____ | | __ABC__ __XYZ__ XYZ__ XYZ__ | | ____ABC ____XYZ XYZ XYZ | | _______ _______ _______ No data | | | | Case #8: ABC0000 XYZ____ XYZ____ XYZ____ | | 00ABC00 __XYZ__ __XYZ__ __XYZ__ | | LB: YES 0000ABC ____XYZ ____XYZ ____XYZ | | TB: YES 0000000 _______ _______ _______ | | TN: YES ABC____ XYZ____ XYZ____ XYZ____ | | __ABC__ __XYZ__ __XYZ__ __XYZ__ | | ____ABC ____XYZ ____XYZ ____XYZ | | _______ _______ _______ No data | | | - - | ABC = host-transmitted data | | XYZ = data typed by the user | | 0 = 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. Localized Softkeys 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 for an example of a PTCONFIG file. English and Asian Language Support English-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"
![[]](../../pic3k/M011498/FFN53c50.gif)