═══ 1. General Help for the Connection Profile Editor ═══ Use the connection profile editor to create, change, or delete information in a connection profile. A connection profile is a set of parameters that tell Distributed Application/2 how to connect to a particular destination. When a new connection is opened, Distributed Application/2 checks the connection profile for the specified destination to determine: o Which protocol to use o Where the destination program is located o How to start it The connection profile also contains protocol-specific information for the protocol to be used. Connection profiles are gathered and stored in a connection profile file. The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. Note: The settings in the connection profiles for the client (initiator) and server (acceptor) should match. One way to accomplish this is to use a LAN server to share the same copy of the connection profile file. This will ensure that both sides are using the correct information for each connection. You can copy a connection profile from one connection profile file to another by doing the following: 1. Start two copies of the connection profile editor. Use one copy of the connection profile editor to open the source file and the other copy to open the target file. 2. Once you have both files open, use the right mouse button to drag the profile you want to copy from the source file and then release the mouse button to drop it on the target file. Do this for each profile you want to copy. Note: Dragging the connection profile from one connection profile file to another copies the profile; it does not remove the profile from the source file. For more information about the supported protocols, refer to: o Named pipes documentation o NetBIOS documentation o APPC documentation ═══ 1.1. Named Pipes Documentation ═══ Refer to the following documentation for more information about named pipes: IBM* OS/2* 2.0 Application Design Guide (S10G-6260) IBM OS/2 2.0 Programming Guide Volume 1 (S10G-6261) IBM OS/2 2.0 Programming Guide Volume 2 (S10G-6494) IBM OS/2 2.0 Programming Guide Volume 3 (S10G-6495) IBM OS/2 2.0 Control Program Programming Reference (S10G-6263) ═══ 1.2. NetBIOS Documentation ═══ For more information about IBM* NetBIOS, refer to the IBM LAN Technical Reference (SC30-3383). For more information about Novell* NetWare* NetBIOS, refer to the Novell NetBIOS Emulator Developer's Guide for NetWare Requester for OS/2 V.2.0. ═══ 1.3. APPC Documentation ═══ Refer to the IBM APPC Programming Reference (S04G-1025) for more information about APPC. ═══ 2. Help for Duplicate Drag Attempt ═══ Each connection profile must have a unique symbolic name. You can do one of the following: o Enter a new symbolic name for the connection profile o Replace the existing connection profile in the target file with the profile from the source file Then select one of the following push buttons: o OK to continue copying the connection profile o Cancel to cancel the drag attempt ═══ 3. Help for Enter New Symbolic Name ═══ Select this radio button to rename the connection profile with a new symbolic name because there is an existing connection profile in the target file using that symbolic name. ═══ 4. Help for Replace Existing Profile ═══ Select this radio button to replace the existing connection profile in the target file with the connection profile from the source file. ═══ 5. Help for Common Page ═══ Use the Common page of the notebook to specify: o Symbolic name of the connection profile o Communication protocol to use o Security o Millisecond wait for open To complete this page: 1. Specify a unique symbolic name. 2. Select one of the protocols. 3. Review the other fields and change them as necessary. All fields are provided with defaults that you can use. 4. When you have completed defining the connection profile and you want to keep your changes, select the OK push button on the bottom of the notebook. If you do not want to keep your changes, select the CANCEL push button on the bottom of the notebook. For more information about the supported protocols, refer to the following documents: Named pipes IBM OS/2 2.0 Application Design Guide (S10G-6260) IBM OS/2 2.0 Programming Guide Volume 1 (S10G-6261) IBM OS/2 2.0 Programming Guide Volume 2 (S10G-6494) IBM OS/2 2.0 Programming Guide Volume 3 (S10G-6495) IBM OS/2 2.0 Control Program Programming Reference (S10G-6263) NetBIOS IBM LAN Technical Reference (SC30-3383) Novell NetBIOS Emulator Developer's Guide for NetWare Requester for OS/2 V.2.0 APPC IBM APPC Programming Reference (S04G-1025) ═══ 6. Help for Named Pipes/NetBIOS Page ═══ If your connection is using the NetBIOS protocol, use the Named Pipes/NetBIOS page of the notebook to specify: o NetBIOS server machine o NetBIOS maximum sessions o Program name o Program parameters o Program operating in foreground or background o Program type is queued or non-queued If your connection is using the named pipes protocol, use this page of the notebook to specify the same fields. Note: If your connection is using the named pipes protocol and you selected the Named pipes radio button on the Common page of the notebook, the NetBIOS server machine and the NetBIOS maximum sessions fields are not available for you to enter information. For more information about named pipes or NetBIOS, refer to the following documents: Named pipes IBM OS/2 2.0 Application Design Guide (S10G-6260) IBM OS/2 2.0 Programming Guide Volume 1 (S10G-6261) IBM OS/2 2.0 Programming Guide Volume 2 (S10G-6494) IBM OS/2 2.0 Programming Guide Volume 3 (S10G-6495) IBM OS/2 2.0 Control Program Programming Reference (S10G-6263) NetBIOS IBM LAN Technical Reference (SC30-3383) Novell NetBIOS Emulator Developer's Guide for NetWare Requester for OS/2 V.2.0 ═══ 7. Help for APPC Pages ═══ Use the APPC pages of the notebook to specify: o TP Name o SNA mode name o Local LU identifier o PLU identifier o Partner type o Data conversion o Milliseconds in send state while in idle Note: There are two pages of information for you to fill out for the APPC protocol. For more information about APPC, refer to the IBM APPC Programming Reference (S04G-1025). ═══ 8. Help for File ═══ Select this menu bar choice to: o Create a new file o Open a file that you saved with Save as o Save information in a file you specify ═══ 9. Help for New ═══ Select this menu choice to create a new connection profile file. When you select New, the connection profile editor displays "Untitled" at the top of the window. (You name the file when you save it.) ═══ 10. Help for Open ═══ Select this menu choice to open and view a connection profile file you previously saved with Save or Save as. Note: The file you specify must be a connection profile file created with the connection profile editor. The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. ═══ 11. Help for Save ═══ Select this menu choice to store the connection profile file you are editing. After the file is saved, the text remains in the window so that you can continue editing it. If you are editing a new file, select the Save or Save as choice to display the Save as window so that you can name the file you are editing. Note: The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. ═══ 12. Help for Save As ═══ Select this menu choice to name and save a new connection profile file, or to save an existing connection profile file under a different name, in a different directory, or on a different disk. Note: The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. ═══ 13. Help for Open Dialog ═══ 1. Select the arrow to the right of the Drive list to display all of the drives on your system. 2. Select a drive from the Drive list. 3. Select a directory from the Directory list. 4. Select a file name from the File list or type in a file name in the Open filename field and then select the Open push button to display the file you want to edit. Note: You can only open a connection profile file with the connection profile editor. The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. ═══ 14. Help for Save As Dialog ═══ 1. Select the arrow to the right of the Drive list to display all of the drives on your system. 2. Select a drive from the Drive list. 3. Select a directory from the Directory list. 4. Type the name of the file you want to save in the Save as filename field and select the Save push button. Note: The name of the connection profile file must be IBMDABB.CP if you want Distributed Application/2 to use it at run time. ═══ 15. Help for Actions ═══ Select this menu bar choice to: o Display the settings of a connection profile o Create another connection profile using the defaults provided o Copy a selected connection profile o Delete one or all connection profiles ═══ 16. Help for Settings ═══ Select this menu choice to display the settings of a selected connection profile. You can display the settings of a connection profile by doing one of the following: o Selecting Settings... from the Actions menu bar choice. o Pressing the second mouse button while the mouse is positioned over a connection profile icon in the connection profile editor window, and then selecting Settings from the pop-up menu. o Double-clicking on the connection profile icon in the window. o Pressing Enter after you have selected a connection profile icon in the window. ═══ 17. Help for Create Another ═══ Select this menu choice to create a new connection profile using the default values supplied by the connection profile editor. You can create another connection profile by doing one of the following: o Selecting Create another... from the Actions menu bar choice. o Pressing the second mouse button while the mouse is positioned over a connection profile icon in the connection profile editor window, and then selecting Create another... from the pop-up menu. Note: Selecting the Create another... pull-down choice does not use the same settings as the connection profile you have selected. It uses the default values as settings supplied by the connection profile editor. If you want to create a new connection profile using the same settings as the connection profile you have selected, use the Copy... pull-down choice from the Actions menu bar choice. ═══ 18. Help for Copy ═══ Select this menu choice to create a new connection profile using the same settings values as the connection profile you have selected. You can copy a connection profile by doing one of the following: o Selecting Copy... from the Actions menu bar choice. o Pressing the second mouse button while the mouse is positioned over a connection profile icon in the connection profile editor window, and then selecting Copy... from the pop-up menu. ═══ 19. Help for Delete All ═══ Select this menu choice to delete all of the connection profiles in the file. ═══ 20. Help for Delete ═══ Select this menu choice to delete a selected connection profile. You can delete a connection profile by doing one of the following: o Selecting Delete from the Actions menu bar choice. o Pressing the second mouse button while the mouse is positioned over a connection profile icon in the connection profile editor window, and then selecting Delete from the pop-up menu. ═══ 21. Help for Help ═══ Select this menu bar choice to obtain the following types of help: Help index Displays an index of help topics General help Displays help on application windows Keys help Displays help on valid keys Help is also available under the Using Help menu bar choice for using the online help facility. ═══ 22. Help for Help Index ═══ Select this menu choice to use the help index. You can use the index in two ways: o To select a topic from a list of all help topics o To search for a topic by selecting Search from the Services pull-down. ═══ 23. Help for General Help ═══ Select this menu choice to obtain an overview of the connection profile editor. ═══ 24. Help for Keys Help ═══ Select this menu choice to obtain help for the key definitions. ═══ 25. Keys Help ═══ Select a topic to get keys help on: o Help keys o System keys o Window keys o Editing keys o Application keys ═══ 25.1. Help Keys ═══ These are the help window key definitions: F1 Displays help Esc Displays the previous window Alt+F4 Exits help ═══ 25.2. System Keys ═══ These are the system key definitions: F1 Displays help F3 Closes the program window F10 Goes to or from the menu bar Arrow keys Move among the choices on the menu bar, pull-down menus, radio buttons, push buttons, and tabs on the notebook End Goes to the last choice in a pull-down menu Esc Cancels a pull-down menu or the system menu Home Goes to the first choice in a pull-down menu PgUp Scrolls the contents of the window up one screen PgDn Scrolls the contents of the window down one screen Underlined letter (mnemonic) Calls the associated action Cursor left Moves the cursor left in the viewing area Cursor right Moves the cursor right in the viewing area Cursor up Moves the cursor up in the viewing area Cursor down Moves the cursor down in the viewing area Alt Goes to or from the menu bar Alt+Esc Switches to the next program, including full-screen programs Alt+Tab Switches to the next program that runs in a window Alt+F4 Closes the window Alt+F5 Restores the window Alt+F6 Changes the active window in an application Alt+F7 Moves the window Alt+F8 Sizes the window Alt+F9 Minimizes the window Alt+F10 Maximizes the window Alt+Up Arrow Moves from the tab to the page of the notebook Alt+Down Arrow Moves from the page to the tab of the notebook Ctrl+Esc Switches to the Task list Ctrl+F6 Changes the active secondary window in an application Shift+Esc or Alt+Spacebar Goes to or from the system menu Shift+Esc or Alt Goes to or from the system menu of a text window. ═══ 25.3. Window Keys ═══ Enter Completes the window Esc Cancels the window Spacebar Performs the task assigned to the selected push button Tab Moves to the next entry field, selection field, push button, tab on a notebook, or hypertext phrase. ═══ 25.4. Editing Keys ═══ Backspace (left arrow delete) Deletes the character to the left of the cursor Del or Delete Deletes the character to the right of the cursor End or Ctrl+Right arrow key Moves to the end of a field Home or Ctrl+Left arrow key Moves to the beginning of a field Shift+Print Screen Prints the information currently displayed. ═══ 25.5. Application Keys ═══ F1 Displays help F3 Exits the connection profile editor ═══ 26. Help for Using Help ═══ Select this menu choice to see a description of the types of help provided for this application and to learn how to get help. ═══ 27. OK ═══ Select this push button to save the changes you made in the connection profile and close the notebook. To save the settings for the connection profile into a file, select Save from the File menu bar choice. ═══ 28. Cancel ═══ Select this push button to exit the window without keeping your changes. ═══ 29. Help for Help ═══ Use the Connection Profile Settings notebook to specify, change, or delete the settings of a connection profile. For more information about the pages of the notebook, see: o Help for Common Page o Help for Named Pipes/NetBIOS Page o Help for APPC Pages ═══ 30. Help for Symbolic Name ═══ Specify a symbolic name in the Symbolic name field to represent this destination. This is the name that the client uses to identify the server. The symbolic name must be: o No more than 8 characters long o Contain characters A-Z and 0-9 Each connection profile must have a unique symbolic name. This is a required field. No default is provided. ═══ 31. Help for Program Name ═══ Specify the name and extension of the server program. Distributed Application/2 only uses this program name for NetBIOS and named pipes connections. If you are using NetBIOS or named pipes, this field is required. ═══ 32. Help for Program Parameters ═══ Specify the parameters to pass to the server program. This field is optional and is only used for NetBIOS and named pipes connections. ═══ 33. Help for Foreground ═══ Select this radio button to have the server program run in the foreground. Selecting Foreground will allow the server program to be able to accept user input or display information to the user. ═══ 34. Help for Background ═══ Select this radio button if you want the server program to run in the background. ═══ 35. Help for Queued ═══ Select this radio button if your server program is designed to accept connections from multiple clients. You would select the Queued radio button if you want only the first connection from a client to cause the server program to start. Subsequent connections from clients will be directed to this running server until the server terminates. ═══ 36. Help for Non-queued ═══ Select this radio button if your server program is designed to accept connections from only one client. You would select the Non-queued radio button if you want each connection from a client to start a new copy of the server program. ═══ 37. Help for None ═══ Select this radio button if you do not want Distributed Application/2 to perform any security checking. ═══ 38. Help for UPM ═══ Select this radio button if you want Distributed Application/2 to use User Profile Management (UPM) to confirm that a user is logged on. Security is performed differently for each of the protocols. Named pipes No security support is provided. NetBIOS Asks UPM for the remote logon userid and password for the remote machine named in the NetBIOS server machine field. If no such remote logon is active, the values for an active local or domain logon are used. A remote logon can become active via a "LOGON userid /P=password /N=remote node" UPM command or via a UPM User Logon Profile. APPC Similar to NetBIOS, but is implemented by APPC. See the APPC Programming Reference for details for allocation with Security=SAME. ═══ 39. Help for Named Pipes ═══ Named pipes is a form of OS/2 interprocess communication that uses file-system calls to transfer data between processes running on the same workstation. Select the Named pipes radio button if your connection uses the named pipes protocol. If your connection uses named pipes, when you have completed the fields on the Common page of the notebook, select the Named Pipes/NetBIOS tab of the notebook to complete the fields that apply to named pipes. For more information about named pipes, refer to the following documents: IBM OS/2 2.0 Application Design Guide (S10G-6260) IBM OS/2 2.0 Programming Guide Volume 1 (S10G-6261) IBM OS/2 2.0 Programming Guide Volume 2 (S10G-6494) IBM OS/2 2.0 Programming Guide Volume 3 (S10G-6495) IBM OS/2 2.0 Control Program Programming Reference (S10G-6263) ═══ 40. Help for NetBIOS ═══ NetBIOS is a communication programming interface that supports peer-to-peer connections between applications running on a Local Area Network (LAN). Select the NetBIOS radio button if your connection uses the NetBIOS protocol. If your connection uses NetBIOS, when you have completed the fields on the Common page of the notebook, select the Named Pipes/NetBIOS tab of the notebook to complete the fields that apply to NetBIOS. For more information about IBM NetBIOS, refer to the IBM LAN Technical Reference (SC30-3383). For more information about Novell NetWare NetBIOS, refer to the Novell NetBIOS Emulator Developer's Guide for NetWare Requester for OS/2 V.2.0. ═══ 41. Help for APPC ═══ APPC is Advanced Program-to-Program Communication. It is a protocol that implements the IBM Systems Network Architecture (SNA) LU 6.2 protocol. Select the APPC radio button if your connection uses the APPC protocol. If your connection uses APPC, when you have completed the fields on the Common page of the notebook, select the APPC tab of the notebook to complete the fields on both APPC notebook pages. For more information about APPC, refer to the APPC Programming Reference (S04G-1025). ═══ 42. Help for Millisecond Wait for Open ═══ Select how long you want Distributed Application/2 to wait for the connection to open before it returns an error. The range is from -1 to 600,000 milliseconds. If you set this timer to -1, it is the same as setting it indefinitely. Note: If you are receiving many time-out errors, try increasing this value. Warning: This time is approximate, and your program should not depend on it for precision timing. ═══ 43. Help for NetBIOS Server Machine ═══ Specify the name of the NetBIOS server machine. This is the same name specified when the NetBIOS daemon on the server machine was started. The name of the NetBIOS server machine must be: o Unique in the network o No more than 8 characters long o Contain characters A-Z and 0-9 This is a required field. No default is provided. ═══ 44. Help for NetBIOS Maximum Sessions ═══ Distributed Application/2 supports the IBM* NetBIOS 3.0 interface (API) and the IBM LAN Server NetBIOS API. You can designate the NetBIOS API that Distributed Application/2 will use. If you enter a 0 in the NetBIOS maximum sessions field, Distributed Application/2 uses the IBM LAN Server NetBIOS API. (You must use this API if you are using the Novell* NetWare* NetBIOS emulator.) The maximum sessions value is systemwide for this type of NetBIOS. The number of maximum sessions is set up during your system configuration, such as in your CONFIG.SYS file. See IBM LAN Server NetBIOS API for more information about specifying the NetBIOS maximum sessions value. If you set NetBIOS maximum sessions to a value from 1 to 126, Distributed Application/2 uses the IBM NetBIOS 3.0 API. See IBM NetBIOS 3.0 API for more information about specifying the NetBIOS maximum sessions value. ═══ 44.1. IBM NetBIOS 3.0 API ═══ Specify the number of NetBIOS sessions Distributed Application/2 will use to communicate. Distributed Application/2 reserves the sessions the first time its services are called within a program. Any subsequent Distributed Application/2 connection that is opened within the program will use one of these reserved sessions. The number of sessions affects the number of clients a server can communicate with. Based on the number of sessions you specify, Distributed Application/2 will obtain the same number of NetBIOS names and twice the number of NetBIOS commands. The range is 1 to 126 sessions. If a program only has one connection active at a time, set the number of sessions to 1. Note: You may want the value in this field to be different for client and server machines. This is the only field that could be different for the client or server machine, depending upon the design of your application or network. For example, if your application has 1 server attached to 3 clients, you would set the number of sessions on the server side to 3 and the client side to 1. ═══ 44.2. IBM LAN Server NetBIOS API ═══ If you are using the Novell* NetWare* NetBIOS emulator, it emulates the IBM LAN Server NetBIOS API. Therefore, you must set the NetBIOS maximum sessions value to 0. The IBM LAN Server NetBIOS API, also called the NetBIOS Submit API or the IBM LAN Manager NetBIOS API, is described in the IBM OS/2 LAN Server Version 2.0 Application Programmer's Reference (S04G-1046). Note: Also, if you are using the Novell NetWare NetBIOS emulator, then both the client and server must have it installed for Distributed Application/2. ═══ 45. Help for TP Name ═══ Specify a Transaction Program (TP) name. APPC uses the TP name to locate the TP definition in Attach Manager. Use Communications Manager to configure the TP definition for APPC. The TP name must be: o No more than 64 characters long o Contain characters A-Z, a-z, and 0-9 The TP name can contain the @, #, and $ characters. It can also contain a slash (/) in the first character position for IMS commands. ═══ 46. Help for SNA Mode Name ═══ Specify the Systems Network Architecture (SNA) mode name to describe the properties of the session. Use Communications Manager to define the mode name. The SNA mode name must be: o No more than 8 characters long o Contain characters A-Z, a-z, and 0-9 The SNA mode name can contain the @, #, and $ characters. Note: The names SNASVCMG and CPSVCMG cannot be used as the SNA mode name. ═══ 47. Help for Local LU Alias Name ═══ Specify the local logical unit (LU) alias name. This field is optional. If you don't specify a local LU alias name, Distributed Application/2 will use the default defined in Communications Manager. The local LU alias name must be: o No more than 8 characters long o Contain characters A-Z, a-z, and 0-9 The local LU alias name can contain the @, #, and $ characters. ═══ 48. Help for Local LU Pool Identifier ═══ Specify a 3-character identifier if you want to use any local LU whose alias starts with those 3 characters. This is an optional field. The local LU pool identifier must be: o Exactly 3 characters long o Contain characters A-Z, a-z, and 0-9 The local LU pool identifier can contain the @, #, and $ characters. Warning: If the LUs in the pool are dependent LUs, make sure no other APPC application running in your machine uses any of them by name. ═══ 49. Help for Fully Qualified PLU Name ═══ Specify the fully qualified Partner Logical Unit (PLU) name. This is a required field if you selected the Name radio button. The fully qualified PLU name must be: o Unique in the network o No more than 17 characters long o Contain characters A-Z and 0-9 The fully qualified PLU name can contain the @, #, and $ characters. It can also contain 1 imbedded period (.) to delimit the netid and LU name portions. ═══ 50. Help for Local LU Alias ═══ Select this radio button if you want to specify a local logical unit (LU) alias name rather than an LU pool ID. ═══ 51. Help for Pool ID ═══ Select this radio button if you want to specify a local logical unit (LU) pool ID. ═══ 52. Help for Name ═══ Select this radio button to if you want to specify a fully qualified Partner Logical Unit (PLU) name. ═══ 53. Help for PLU Alias ═══ Select this radio button if you want to specify a Partner Logical Unit (PLU) alias name rather than a fully qualified PLU name. ═══ 54. Help for PLU Alias Name ═══ Specify the Partner Logical Unit (PLU) alias name. This field is required if you selected the Alias radio button. The PLU alias name must be: o No more than 8 characters long o Contain characters A-Z, a-z, and 0-9 The PLU alias name can contain the @, #, and $ characters. Note: This alias must also be configured in Communications Manager. ═══ 55. Help for Partner Code Page ═══ If you selected the Character data conversion radio button, you must specify the code page of the server machine in the Partner code page field. This tells Distributed Application/2 the type of character data conversion to perform. Note: If you want to check the code pages that Distributed Application/2 supports as the active code page in the local machine, see Local Machine Code Pages. From the ASCII or EBCDIC table, do the following: 1. Find the language the server machine will use. 2. Select the code page that corresponds to that language from the following ASCII or EBCDIC table. 3. Specify that code page in the Partner Code Page field. The following table lists ASCII code pages supported by Distributed Application/2. ┌────────────────────┬───────────────┐ │Language │ASCII Code Page│ ├────────────────────┼───────────────┤ │Canadian-French │863 │ ├────────────────────┼───────────────┤ │Multilingual │850 │ ├────────────────────┼───────────────┤ │Norwegian │865 │ ├────────────────────┼───────────────┤ │Portuguese │860 │ ├────────────────────┼───────────────┤ │US English │437 │ └────────────────────┴───────────────┘ The following table lists EBCDIC code pages supported by Distributed Application/2. ┌────────────────────┬───────────────┐ │Language │EBCDIC Code │ │ │Page │ ├────────────────────┼───────────────┤ │Austrian/German │273 │ ├────────────────────┼───────────────┤ │Danish/Norwegian │277 │ ├────────────────────┼───────────────┤ │English and Japanese│931 │ │Extended │ │ ├────────────────────┼───────────────┤ │Finnish/Swedish │278 │ ├────────────────────┼───────────────┤ │French │297 │ ├────────────────────┼───────────────┤ │Italian │280 │ ├────────────────────┼───────────────┤ │Japanese (Katakana) │930 │ │Extended │ │ ├────────────────────┼───────────────┤ │Japanese (Latin) │939 │ │Extended │ │ ├────────────────────┼───────────────┤ │Korean Extended │933 │ ├────────────────────┼───────────────┤ │Multilingual │500 │ ├────────────────────┼───────────────┤ │S-Chinese Extended │935 │ ├────────────────────┼───────────────┤ │Spanish │284 │ ├────────────────────┼───────────────┤ │T-Chinese Extended │937 │ ├────────────────────┼───────────────┤ │UK English │285 │ ├────────────────────┼───────────────┤ │US English │037 │ └────────────────────┴───────────────┘ ═══ 55.1. Local Machine Code Pages ═══ The following table lists code pages that can be the active code page of the local machine. These are the code pages supported by Distributed Application/2. ┌────────────────────┬───────────────┐ │Language │ASCII Code │ │ │Pages │ ├────────────────────┼───────────────┤ │Canadian-French │863 │ ├────────────────────┼───────────────┤ │International │850 │ ├────────────────────┼───────────────┤ │Japanese │932 │ ├────────────────────┼───────────────┤ │Japanese Extended │942 │ ├────────────────────┼───────────────┤ │Korean │934 │ ├────────────────────┼───────────────┤ │Korean Extended │944 │ ├────────────────────┼───────────────┤ │Norwegian │865 │ ├────────────────────┼───────────────┤ │Portuguese │860 │ ├────────────────────┼───────────────┤ │T-Chinese │938 │ ├────────────────────┼───────────────┤ │T-Chinese Extended │948 │ ├────────────────────┼───────────────┤ │US English │437 │ └────────────────────┴───────────────┘ ═══ 56. Help for Distributed Application/2 ═══ Select this radio button if both client and server programs are written using the Distributed Application/2 APIs. ═══ 57. Help for Native APPC - No Confirmation ═══ Select this radio button if the server program is written using direct APPC calls and does not use confirmations. ═══ 58. Help for Native APPC - Confirmation ═══ Select this radio button if the server program is written using direct APPC calls and uses confirmations. Refer to the online Distributed Application/2 Programming Guide and Reference for more information about the types of supported confirmations. ═══ 59. Help for No Character Data Conversion ═══ Select this radio button if you want Distributed Application/2 to treat all data as binary data and perform no character conversions. ═══ 60. Help for Character Data Conversion ═══ Select this radio button if you want Distributed Application/2 to perform character conversions. If you select the Character data conversion radio button, you must specify a code page in the Partner code page field. ═══ 61. Help for Millisecond Wait ═══ Use this field to specify the time interval for Distributed Application/2 to check if the partner needs to send data. This field applies only when the partner type is Distributed Application/2. It does not apply to native APPC partners. The range is 50 to 1,000 milliseconds. Note: The lower this time interval is set, the more responsive your application will seem, but it will be using more system resources. The higher this time interval is set, the less responsive your application will seem, but it will be using less system resources. Therefore, if responsiveness is more important to you than the amount of system resources, set it low. Conversely, if responsiveness is less important to you than the amount of system resources, set it high. ═══ ═══ Trademark of International Business Machines Corporation ═══ ═══ Trademark of Novell,