OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / com / utils / pmfterm / pmfterm.hlp (.txt) < prev next >

Wrap

OS/2 Help File | 1993-02-10 | 26.9 KB | 846 lines

ΓòÉΓòÉΓòÉ 1. About PMFTERM Emulation ΓòÉΓòÉΓòÉ PMFTERM is a general purpose terminal emulator for OS/2. PMFTERM provides FTTERM color emulation, as well as DEC VT100, ANSI and line-mode TTY support. Support for multiple font sizes, automatic logon keying (Autokeys) as well as color selection for FTTERM emulation is provided, as well as screen print, cut and paste. Two file transfer protocols are supported, IND$FILE and XMODEM. File transfers can be invoked by pulldown menus or by the command line interface programs PSEND and PRECEIVE. ΓòÉΓòÉΓòÉ 2. Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ You can customize any number of emulation profiles for PMFTERM. These profiles are saved in the OS2.INI system file and can be selected by a pulldown menu item or by specifying the name of the profile to be used on the PMFTERM command line. The customizable values are: Emulation type Number of data bits Number of stop bits Communications port File transfer protocol Line speed Parity FTTERM protocol converter type FTTERM host type Autokey Sequences For more information on selecting a terminal profile, see Selecting Profiles. ΓòÉΓòÉΓòÉ 3. About the Autokeys Dialog ΓòÉΓòÉΓòÉ The Logon Key Definitions dialog is used to define a set of keystrokes which are to be sent to the host system during initial connect processing. For each "Send" key definition a corresponding "Response" definition must be provided. PMFTERM processes the Send and Response entries sequentially until a blank entry is found, at which time autokey processing terminates. During autokey processing a dialog box is display which provides a visual indication of the progress of the logon process. More information may be found in: Manual Connect Only Entering Autokey Information ΓòÉΓòÉΓòÉ 4. Deleting Profiles ΓòÉΓòÉΓòÉ You may delete individual profiles via the Profile Delete pulldown. You may enter the profile to be deleted via the keyboard (case is ignored and is set to upper case) or the mouse. You may select Cancel at any time to abort the process. ΓòÉΓòÉΓòÉ 5. Color Selection for FTTERM Emulation ΓòÉΓòÉΓòÉ You may find that it is difficult to see all of the FTTERM colors when working with an 8507 monochrome display, a PS/2 Model P70 plasma display or sometimes with a PS/2 Model L40SX, depending on the level of the installed display drivers. If this is the case, you can change any or all of the four basic 3270 data stream colors via the Customize pulldown menu. If the Colors menu item is not selectable, go to the Profiles pulldown and select a terminal profile which specifies FTTERMC emulation. The FTTERM Color Selection dialog box contains a set of radio buttons which indicate which of the 4 basic 3270 colors is to be changed, a set of color buttons corresponding roughly to the 8 basic AVIO colors and a number of pushbuttons at the bottom to control updating and saving of the changes. To modify a color, push the radio button corresponding to the color to be changed (in order they correspond to Green, Red, Blue and White), push the button in the "To" group for the new color and then push the "Set" button. When all the desired changes have been made, push the "Ok" button to exit the dialog. To write the changes to the OS2.INI file, push "Save". The "Reset" button will reset the colors to the PMFTERM default colors, but will not update OS2.INI unless you select "Save". ΓòÉΓòÉΓòÉ 6. File Transfer ΓòÉΓòÉΓòÉ PMFTERM implements IND$FILE and XMODEM (both checksum and CRC) file transfers. Because of the differences between the 7171 protocol converter and the 3708, it is very important that the Terminal Settings be set to reflect the proper machine type. Also, the TSO/CMS settings must be correct for IND$FILE to work correctly. IND$FILE via Pulldown menus You can invoke IND$FILE from the File pulldown menu or from the PSEND/PRECEIVE commands. Selecting the File Send or Receive options presents the following dialog box. IND$FILE via PSEND/PRECEIVE You may also use the PSEND/PRECEIVE commands provided with PMFTERM to invoke file transfer from the command line. PSEND/PRECEIVE have identical syntax to the the OS/2 CM SEND/RECEIVE commands for IND$FILE. PSEND/PRECEIVE default to host session "I" instead of "A". The PCASSI package from OS2TOOLS provides an excellent interface to the standard SEND/RECEIVE commands. You may use PCASSI in one of two ways with PMFTERM. Either rename the PSEND/PRECEIVE commands to SEND/RECEIVE if you do not have any other IBM SEND/RECEIVE command installed on your system, or use the PCASSI50.CUS customization file with PCASSI 3.0 or above. PCASSI50 customizes PCASSI to use PSEND/PRECEIVE through host session "I". Refer to the PCASSI package documentation for more information. Recovering from IND$FILE errors During file transfer (IND$FILE and XMODEM) the following status dialog is maintained: A number of "hangs" can occur during IND$FILE file transfer. In general, the problems will occur on file downloads and are caused by parity problems or lost characters during the receive operation. PMFTERM will "beep" whenever a parity or framing error is detected by the OS/2 COM device driver, and if the host screen is not correctly received in 40 seconds will issue the "Host has not responded in 40 seconds". Corrective action for this condition is: 1. Switch to the host session. 2. If the host screen is blank, minimize and then maximize the host window. You should see what looks like garbage on the screen. 3. Hit CTRL-R to reset the keyboard, followed by CLEAR. The file transfer should now resume. You may minimize the PMFTERM window to an icon if you wish. If the above recovery action does not seem to work, you must abort the file transfer by following these instructions: 1. First cancel the PMFTERM file transfer interface, either via the "Cancel" button on the Send/Receive dialog or by Ctrl-Break if using PSEND/PRECEIVE. Note: It can take 30-40 seconds to cancel the file transfer, since PMFTERM must wait for host download screens to be completely received in some situations. 2. If the host "Ready" prompt does not appear in 30-40 seconds, activate the PMFTERM window and Minimize/Maximize it. You should see some strange looking characters on the screen, or a screen that starts with the character "A", "B", "C" or "<" . Hit the F2 key. 3. If the sequence "C???q" appears next, where ??? can be any character, hit the Enter key and the Ready prompt will appear. Strange characters during IND$FILE PMFTERM disables screen updates during IND$FILE file transfers. However, if you move, resize, minimize/maximize or in any other way cause the PMFTERM window to be altered during transfers you will be regaled with large amounts of what appears to be garbage flowing over your terminal emulation screen. This is normal. If it bothers you, just minimize the PMFTERM session until the file transfer completes. XMODEM File Transfers When the Terminal Settings indicate that file transfer is via XMODEM the procedure for file transfer is almost identical to IND$FILE. Selecting the File Send or Receive options presents the following dialog box. 1K Send will be used if this checkbox is turned on. You must be certain that the receiving system supports XMODEM CRC with 1K blocks! The PSEND/PRECEIVE command interface may still be used. However, PSEND/PRECEIVE for XMODEM requires that the following syntax be followed: PSEND pcfilename [s:] (X [1K]) PRECEIVE pcfilename [s:] (X) The right parenthesis is optional, but the left parenthesis is required. The "s" is optional and is the host session ID ("I" is the default). The "X" signifies XMODEM and may be in upper or lower case. The only command line operand allowed with XMODEM is "1K", which forces PMFTERM into 1024 byte Send mode (instead of 128 byte mode). If 1K mode is selected, CRC mode is also enforced. You must be certain that the receiver supports 1024 byte blocks. Otherwise, the Send operation will be aborted by the receiving system. PMFTERM attempts to use XMODEM CRC protocol, but will operate in XMODEM checksum protocol if CRC is not allowed by the other end. Ten (10) attempts are made at three (3) second intervals to establish CRC mode. After that, Checksum mode is established. PMFTERM will accept either 128 byte blocks (CRC or Checksum mode) or alternatively, 1024 (1K) byte blocks for file download. 1K blocks are also referred to by some BBS's as "Y-modem 1K", but in actuality this is really Xmodem 1K with CRC mode. Either CRC or Checksum will be used as defined by the receiver. Also, the line characteristics are set to 8 data bits, 1 stop bit and no parity (8-N-1) for the duration of XMODEM file transfers, and are reset to their original settings upon completion of the transfer. Therefore, you may operate your terminal emulations with 7 data bits and parity enabled and still perform XMODEM transfers. The same status dialog is displayed as with IND$FILE during XMODEM transfers. ΓòÉΓòÉΓòÉ 7. Help for Keys ΓòÉΓòÉΓòÉ The keyboard mapping for VT100 and FTTERMC emulation closely follows the FTTERM 2.1 keyboard mapping, with a few exceptions made at the request of FORUM contributors. For ANSI and TTY modes the keyboard behaves in the same manner as a Teletype KSR 33 (including all CTRL keys). The "3270" emulations (VT100/FTTERMC) use the following: Clear HOME (All keyboards) PAUSE (Enhanced Keyboard) Enter Right CTRL (Enhanced Keyboard) Pad ENTER (Enhanced Keyboard) ENTER (AT Keyboard) Return ENTER (Enhanced Keyboard) CTRL+ENTER (AT Keyboard) Erase EOL END (All Keyboards) PF1-PF12 F1-F12 (Enhanced Keyboard) F1-F10, Shift+F1, Shift+F2 (AT Keyboard) PA1 CTRL+F1 or ALT+INS (All Keyboards) PA2 CTRL+F2 or ALT+HOME (All Keyboards) Reset CTRL+"R" (3708/7171 Implementation) In addition to the 3270 key functions defined above, the following CTRL combinations are implemented in VT100: 5842 CommandCTRL+N (5842 command mode) XON/XOFF CTRL+S/CTRL+Q (Use with care!) SI CTRL+O Break CTRL+C (Not a line break...send the char.) ΓòÉΓòÉΓòÉ 8. PMFTERM Main Window Help ΓòÉΓòÉΓòÉ This is the help for the pmfterm main window. ΓòÉΓòÉΓòÉ 8.1. File Menu Pulldown ΓòÉΓòÉΓòÉ This pulldown control file Send and Receive operations. The protocol to be used for the file transfer is defined in the current terminal settings profile. For more information, refer to: Setting Profiles for PMFTERM File Transfer ΓòÉΓòÉΓòÉ 8.2. Print Screen ΓòÉΓòÉΓòÉ The current screen contents are copied to the Print Manager application default queue using a simple ASCII data stream. Nulls are converted to blanks, trailing data is stripped and an ASCII CR/LF sequence is appended to the data. No check is made to ensure that the screen is not being updated during the screen print. Note: This does not imply that LPT1 is the target device! You may have assigned some other printer to the default queue in the Print Manager! ΓòÉΓòÉΓòÉ 8.3. Capture ΓòÉΓòÉΓòÉ When you check the Capture menu item incoming data from the communications line is captured in raw format and saved in a 64K byte buffer. If the buffer fills it is wrapped to the beginning and data is lost. Selecting the Capture menu item again causes the contents of the buffer to be written to the clipboard, where it can be pasted into an editor and saved to a file. ΓòÉΓòÉΓòÉ 8.4. Host Print in FTTERMC Mode ΓòÉΓòÉΓòÉ When PMFTERM is configured for FTTERMC emulation on the 3174/3708 it is possible to redirect host LU1/LU3 print data streams to the OS/2 print spooler. The 3174/3708 must be appropriately configured, as well as the host VTAM/NCP and application definitions. When PMFTERM receives the DLE-DC2 ASCII host sequence it opens the printer data stream defined as the default printer. This is the same printer as is used for PMFTERM Print Screen. All host print data is dumped unmodified to the output printer, which is assumed to be ProPrinter compatible. Since PMFTERM cannot detect the end of the print data stream it is necessary for the user to monitor the status of the print job. This can be done via the host application, ie. SDSF if TSO, RSCS QUERY commands if VM, etc. To aid in monitoring the status of the print job, PMFTERM sounds a short beep (similar to the beep issued when a line error occurs) at the end of each page sent to the OS/2 Spooler. The print job is closed and sent to the print spooler when the user selects Close Host Print from the File menu pulldown, or when PMFTERM is terminated. ΓòÉΓòÉΓòÉ 8.5. Settings Pulldown ΓòÉΓòÉΓòÉ This menu controls the Terminal Settings. Options are provided to Set Up Profiles for PMFTERM Delete PMFTERM Profiles Initialize OS2.INI to remove ALL PMFTERM Profiles. ΓòÉΓòÉΓòÉ 8.6. Exit PMFTERM ΓòÉΓòÉΓòÉ This option unconditionally exits PMFTERM. The telephone connection is dropped. You will be given an option to continue PMFTERM execution, or to terminate PMFTERM with or without saving the current window position. ΓòÉΓòÉΓòÉ 8.7. Initiate Connection ΓòÉΓòÉΓòÉ You may select one of the following actions: Connect Hang up the telephone and restart the connection. Execute the autokey sequences if any are defined. This option must also be used when the Manual Connect option is selected to activate the connection. Abort Connect The autokey sequences are aborted. The connection to the telephone network remains active. Hangup. The telephone is hung up (goes on-hook) at once. ΓòÉΓòÉΓòÉ 8.8. Clipboard Operations ΓòÉΓòÉΓòÉ Standard PM Mark, Copy and Paste functions are provided on the Edit pulldown menu item. Text can be marked with the mouse or via the keyboard. To mark text via the keyboard select Edit Mark. A selection rectangle will appear starting at the current cursor position. Size the rectangle with the keyboard arrow keys and hit Enter to complete the selection process. If you have problems (due to bugs) while marking text, maximize PMFTERM's window and use the keyboard instead of the mouse to mark the text. I have some bugs in this area still. Edit Copy or Ctrl+Ins can be used to copy the selected text to the clipboard. You might also occasionally observe that a selection rectangle or small cursor-like line appears when switching to PMFTERM from another PM application using mouse button 1. If this happens, just hit the left mouse button again while in the PMFTERM client window and the selection will be reset. Paste is activated when the clipboard is found to contain data in the clipboard CF_TEXT format. When you select Edit Paste from the pulldown (or use the Shift+Ins key combination) the contents of the clipboard are typed into the host session, starting at the cursor location. Depending on the emulation in effect the data is translated to match the behavior of the keyboard, for example in FTTERMC emulation a 0D "return" character should be treated as a "new line" character, but in TTY line mode the 0D should be treated as an "enter". All "new line" 0A characters are ignored by Paste. ΓòÉΓòÉΓòÉ 8.9. Color Selection ΓòÉΓòÉΓòÉ When using FTTERMC emulation it is possible to change the basic 3270 data stream colors to make the screen more visible on monochrome and plasma displays. Refer to Color Selection for FTTERM Emulation General Description and How to Select FTTERM Colors for information on how to do this. Note: This selection is only applicable to FTTERM emulation. It is not possible to change the colors for ANSI emulation. ΓòÉΓòÉΓòÉ 8.10. Font Selection ΓòÉΓòÉΓòÉ PMFTERM will attempt to present the first 16 AVIO (Advanced Video Input Output) fonts supported on your particular display via this pulldown. Whenever you change the specified font the new setting will be saved in OS2.INI. In some cases (and under OS/2 1.2) PMFTERM will not be able to communicate with the display driver. In this case you will only be given the option of "Large" and "Small" EGA fonts, rather than a full selection of all the supported fonts. In that case you will need a new display driver. ΓòÉΓòÉΓòÉ 9. Working with Profiles ΓòÉΓòÉΓòÉ Profiles are saved in OS2.INI. When a profile is retrieved it replaces the in-memory terminal profile. Unless the manual connect. option is selected the current connection is aborted and a new connection is established using the new terminal settings and autokeys. If manual connect is selected, only the in-memory terminal profile is updated but the connection continues using the previous settings. ΓòÉΓòÉΓòÉ 9.1. Profile Name ΓòÉΓòÉΓòÉ This box contains the names of all of the current profiles. The active profile is highlited. You may select the profile to be used by clicking on the profile name with the mouse and then clicking on Retrieve, by using the arrow keys to move up and down in the list and then hitting Enter, or by typing the name of the desired profile and hitting Enter. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.2. Retrieving a Profile ΓòÉΓòÉΓòÉ This button causes the profile specified in the profile name to be retrieved from OS2.INI. If the specified profile does not exist, the terminal settings are set to the PMFTERM default (FTTRMIIN). For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.3. Terminal Emulations ΓòÉΓòÉΓòÉ Emulation Description FTTERMC This is the IBM PC/Host File Transfer Program 3270 emulation protocol. It is primarily designed for use with the IBM 3708/3174AEA and 7171 protocol converters. The IND$FILE (Release 1.1.1) file transfer protocol is supported. Colors can be remapped to accomodate monochrome and plasma displays. When working with a 3708/3174 it is imperative that the Typeahead and Enhanced Null/Blank options be enabled (the operator information area will show "TYP N/B". Toggle this setting with the <ESC>t sequence. ANSI PMFTERM provides ANSI-compatible data stream processing. All CTRL-key combinations are supported. ANSI color and cursor positioning data streams are supported. This emulation is useful for accessing many BBS's. XMODEM, XMODEM CRC and XMODEM 1K are supported for file transfer. VT100 DEC VT100(R) emulation can be used for access to IBM 7171 protocol converters which do not have the FTTERM TDT's installed, as well as for access to any ASCII host supporting VT100 protocol. Both IND$FILE and XMODEM are supported. TTY Line-mode ASCII emulation is supported for access to ASCII hosts. All CTRL-key combinations are supported, as is XMODEM file transfer. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.4. Line Speeds ΓòÉΓòÉΓòÉ You may select line speeds of 300, 1200, 2400, 4800, 9600 and 19,200 BPS. The PC/AT does not support speeds of 19,200 and damage to the serial adapter may result if it is operated at this speed. Although PMFTERM may work with MNP modems using compression, it is recommended that for the full-screen (FTTERMC, ANSI and VT100) emulations compression be disabled. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.5. Parity Selection ΓòÉΓòÉΓòÉ Select Even, Odd or None for parity. Regardless of the selection PMFTERM will revert to None for the duration of XMODEM file transfers, and then restore the user-selected parity at the completion of the file transfer. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.6. Setting the Data Bits ΓòÉΓòÉΓòÉ Generally, 7 data bits will be selected for FTTERM and VT100. 7 or 8 may be selected for ASCII hosts. PMFTERM will switch to 8 data bits during XMODEM file transfers and restore the user-selected data bit setting when the transfer is complete. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.7. Setting the Stop Bits ΓòÉΓòÉΓòÉ Select 1 stop bit for 1200 BPS and above. 2 stop bits may be used for 300 BPS and (sometimes) for 1200 BPS). For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.8. Communications Device Number ΓòÉΓòÉΓòÉ COM1-4 may be selected on PS/2 hardware and on some clones when supported by OS/2. PC/AT hardware only supports COM1 and COM2. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.9. File Transfer Protocol ΓòÉΓòÉΓòÉ PMFTERM supports IND$FILE Release 1.1.1 protocol, XMODEM, XMODEM CRC and XMODEM 1K file transfer protocols. Regardless of the user-specified number of data bits, stop bits and parity PMFTERM will temporarily switch to 8/1/N during XMODEM transfers. For IND$FILE to work correctly the following options must be set correctly: Host System Type Protocol Converter Type For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.10. Host System Type ΓòÉΓòÉΓòÉ The host system (VM/CMS or MVS TSO) must be set here. This information is used during IND$FILE file transfer, and is ignored if XMODEM is set. To switch from one setting to another during a logon session, ie. through IBM Information Network or through multi-session host software you must do the following: 1. Log off the previous host session 2. Select the Settings pulldown 3. Change the Host Type to match the new session 4. Select Keys... 5. Check the Manual Connect option 6. Hit OK on the Logon Key Definitions and Terminal Settings screens If you are not using the PSEND/PRECEIVE command line interface you may alternatively just change the host type on the IND$FILE file selection dialog window. This change is only used for the duration of the current file transfer, however. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.11. Protocol Converter Type ΓòÉΓòÉΓòÉ For FTTERM emulation, this setting must match the protocol converter being used at the host. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.12. Setting a Default Profile ΓòÉΓòÉΓòÉ By checking Default and Save the current terminal settings become the PMFTERM defaults. When you invoke PMFTERM without specifying a profile name the name DEFAULT is used for the settings. If you do not save the current settings this checkbox has no effect. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.13. Save the Profile ΓòÉΓòÉΓòÉ The current terminal settings are written to OS2.INI. If the Default box is checked the settings are saved twice, first under the name specified in the Profile Name combination box and then under the name DEFAULT For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.14. Activate the Profile ΓòÉΓòÉΓòÉ Click on OK to activate the current settings. Remember to hit the Retrieve button if you have just typed a new profile name. The phone line will be dropped and reenabled and the Autokey sequences will be run unless the Manual Connect option is selected. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 9.15. Abort Profile Selection ΓòÉΓòÉΓòÉ The Terminal Settings window is closed and the in-memory terminal settings will be reset to their previous state. For general information on PMFTERM Profiles see Setting Profiles for PMFTERM ΓòÉΓòÉΓòÉ 10. Autokey Definitions ΓòÉΓòÉΓòÉ This dialog is used to define a set of host key sequences which are used during Connect processing. The Logon Key Definition dialog is displayed. ΓòÉΓòÉΓòÉ 10.1. Defining Host Sequences ΓòÉΓòÉΓòÉ Send Definitions You may enter any valid character in the Send definitions. Autokey processing will complete when an empty Send field is encountered. Normally you would enter modem control sequences, logon information, etc. in the Send fields. The "\" backslash character is used to denote certain escape-type sequences: \t or \> Send a tab sequence to the host \d Send a Ctrl-N (IBM 5841) to the host \r Send a carriage return to the host \n Send a new line to the host \c Send a CTRL-C sequence to the host \e Send an ESC character to the host \w Wait one second \< Send a BACKTAB key (FTTERMC only) \o Send a CTRL-E (used for R<O>LM switches \\ Send the backslash character PMFTERM proceeds sequentially through the autokey sequences until a null entry is found. For each entry the data in the "Send" field is typed into the emulation session, and PMFTERM waits for the data in the "Response" field to appear in the client window. If the response information is already on the host screen the scan will be satisfied immediately. When the data is found, PMFTERM proceeds to the next "Send" item and the process is repeated. Response Definitions Any ASCII data may be entered into the Response definitions. Note that the host screen is searched repeatedly for the Response data from row/column 0/0 to 24/79. If the data is found then processing continues with the next Send field. Residual data on the screen can, therefore, cause a premature exit of the Response search if it satisfies the Response criteria. Autokey processing completes when an empty Response item is encountered. ΓòÉΓòÉΓòÉ 10.2. Accept Autokey Values ΓòÉΓòÉΓòÉ Selecting OK causes the autokey definitions and the Manual Connect setting to be stored in the In-memory profile. Control is returned to the Terminal Settings dialog. ΓòÉΓòÉΓòÉ 10.3. Cancel Autokey Definition ΓòÉΓòÉΓòÉ The in-memory profile image is restored to match its value upon invocation of the Logon Key Definitions dialog and control is returned to the Terminal Settings dialog. ΓòÉΓòÉΓòÉ 11. Forcing Manual Connection ΓòÉΓòÉΓòÉ This selection will suppress the PMFTERM connect processing which normally occurs when OK is selected from the Terminal Settings dialog. The default action is to hang up the telephone, reenable Data Terminal Ready and proceed with the autokey processing. Manual Connection is useful when editing terminal settings while a connection is in progress, or for correcting errors in the Host type, file transfer protocol, etc. Warning: PMFTERM frequently refers to the in-memory contents of the Terminal Settings during execution. If you change the Terminal Settings with Manual Connect Only set you could cause unpredictable results until you reestablish the host connection using the Connect pulldown menu. ΓòÉΓòÉΓòÉ 12. Deleting Individual Profiles ΓòÉΓòÉΓòÉ You may delete an individual profile from OS2.INI by selecting it as described in Specifying the Profile to Delete and then clicking on DELETE. ΓòÉΓòÉΓòÉ 12.1. Specifying the Profile to Delete ΓòÉΓòÉΓòÉ You may select the profile to be deleted via the cursor keys, the mouse or by overtyping the name of the profile in the combo box. ΓòÉΓòÉΓòÉ 13. FTTERM Color Selection ΓòÉΓòÉΓòÉ This dialog lets you change the FTTERM colors. Refer to Color Selection for FTTERM Emulation a general description. ΓòÉΓòÉΓòÉ 13.1. Saving the FTTERM Colors ΓòÉΓòÉΓòÉ Clicking on this button will write the current color selection to OS2.INI. PMFTERM always attempts to retrieve a color selection set from OS2.INI at startup, and if none is found will revert to the initial PMFTERM FTTERM color defaults. ΓòÉΓòÉΓòÉ 13.2. Activate the New FTTERM Colors ΓòÉΓòÉΓòÉ The current color selection is activated. No changes are written to OS2.INI. The changes will affect all new output to the screen, so you might wish to clear the screen to cause a repaint from the host system to see if the colors are what you desire. ΓòÉΓòÉΓòÉ 13.3. Restore PMFTERM Default Colors ΓòÉΓòÉΓòÉ The colors settings are restored to their initial defaults. Description Color Normal Unprotected Green Intensified Unprotected Red Normal Protected Blue Intensified Unprotected White To permanently effect a Reset you must save the FTTERM settings. ΓòÉΓòÉΓòÉ 13.4. Abort Color Change ΓòÉΓòÉΓòÉ The FTTERM color selection is cancelled. Some of the host colors may have already been changed, requiring a Reset or a restart of PMFTERM to restore your original color choices. ΓòÉΓòÉΓòÉ 13.5. Using the color buttons for FTTERM ΓòÉΓòÉΓòÉ To change a color: 1. Select the color to be changed from the choices under Set Color 2. Select the new color to be assigned to that host attribute (for example, Intensified Unprotected from the choices under To 3. Select Save If you make a mistake, or want to restore the colors to their initial "factory defaults" just select Reset. ΓòÉΓòÉΓòÉ 14. File Selection for File Transfer ΓòÉΓòÉΓòÉ This dialog provides interactive definition of the file transfer parameters for IND$FILE and XMODEM. Use the list boxes or the entry fields to enter the host (for IND$FILE) and OS/2 file names, as well as other file transfer options. ΓòÉΓòÉΓòÉ 14.1. OS/2 Filename ΓòÉΓòÉΓòÉ You may overtype the full OS/2 path and file name, or select the file to be send/received via the dialog box. No syntax checking is done if you type the file name. PMFTERM just verifies its existence for Send operations and opens it for output for Receive. ΓòÉΓòÉΓòÉ 14.2. Host Filename ΓòÉΓòÉΓòÉ Enter the filename for the host file. No syntax checking is done to verify that the filename is either a valid TSO or CMS file name. For example, in TSO you must specify the userid prefix and surround the file name in apostrophes if PREFIX is on and you want to use a high-level dataset name qualifier other than your own userid. ΓòÉΓòÉΓòÉ 14.3. IND$FILE Options ΓòÉΓòÉΓòÉ Check or fill in the following file transfer options: RECFM Host record format, either V, F or U. This field is not validated and may contain any value to be passed to the IND$FILE command. IND$FILE will give a syntax error if this field is present during an attempt at Receiving a file. LRECL This contains the logical record length. It is limited only by the host operating system and is not checked for validity. IND$FILE will give a syntax error if this field is present during an attempt at Receiving a file. ASCII ASCII translation of the data will be done. IND$FILE's internal translation table will be used. Codepage and NLS are ignored. CRLF IND$FILE will append a CR and LF sequence to each line of data. ASCII translation is assumed. This option must be specified correctly in order for the APPEND option to work properly. APPEND The data is appended to the end of the host or OS/2 file. If the ASCII option is specified during a Receive PMFTERM will check the end of the OS/2 file for an ASCII EOF (hex 1A) and will overlay it if one is found. ΓòÉΓòÉΓòÉ 14.4. Other IND$FILE Options ΓòÉΓòÉΓòÉ Any text entered in this field will be appended to the IND$FILE command. PMFTERM will provide parentheses before the other options if needed (ie. host type is VM). No checking is done. Use this field to specify DASD space information, etc. ΓòÉΓòÉΓòÉ 14.5. Host Operating System ΓòÉΓòÉΓòÉ This setting must match the host operating environment. It is used in formatting the IND$FILE command syntax, and by PSEND and PRECEIVE in interpreting the command line to ensure the correct file transfer command. This selection is initialized to the value from the current terminal profile, and may be changed for the duration of a single (menu-driven) file transfer. ΓòÉΓòÉΓòÉ 14.6. OS/2 File Specification ΓòÉΓòÉΓòÉ Use the file selection dialog items to completely specify the name of the OS/2 file to send or receive. You may also key the full file specification in the PC File area. ΓòÉΓòÉΓòÉ 14.7. Force 1024 XMODEM Block Size ΓòÉΓòÉΓòÉ PMFTERM will accept 1024 byte blocks on all Receive operations. Since the use of 1024 byte blocks is defined by the sender use this selection to tell PMFTERM that the receiving host supports 1024 byte blocks. Note: Selecting this option on a Send to a host which only supports 128 byte XMODEM will result in a file transfer failure.