home *** CD-ROM | disk | FTP | other *** search
Wrap
ΓòÉΓòÉΓòÉ 1. Setup Commands ΓòÉΓòÉΓòÉ This chapter describes the Communications Manager setup commands. Each command description includes the purpose of the command, a syntax diagram, a list of parameters, a discussion of the options, remarks, and examples. CMSETUP can be invoked from the OS/2 command line or the Communications Manager/2 folder on the desktop. For more information on installation, refer to Workstation Installation and Configuration Guide and IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide. To view the list of setup commands, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 1.1. CMREPL ΓòÉΓòÉΓòÉ CMREPL Purpose Allows you to replace the name of the default startup configuration with the name of a different configuration. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMREPLΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇconfigurationΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Specifies the drive for the command you want to process. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ Specifies the exact location of the command you want to process. ΓòÉΓòÉΓòÉ <hidden> configuration ΓòÉΓòÉΓòÉ The name of the configuration that will become the new default startup configuration for Communications Manager. Do not include the file extension. Any file extension is ignored and assumed to be .CFG. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ CMREPL can be executed from the Communications Manager/2 folder or from the command line. To execute CMREPL from the Communications Manager/2 folder, select Replace Default Configuration. When you execute CMREPL from the command line, you can issue the command with or without the configuration parameter. Executing CMREPL without the configuration parameter has the same result as selecting Replace Default Configuration from the Communications Manager/2 folder (a Presentation Manager window appears). CMREPL can be executed from any directory; however, the new default configuration must be in the \CMLIB directory prior to executing CMREPL. Use the following sequence of commands to stop Communications Manager, change the default configuration, and start Communications Manager using the new default configuration: 1. CMSTOP 2. CMREPL configuration 3. CM Only a verified IBM Communications Manager. file may be specified as the new default configuration when using CMREPL. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CMREPL usage: o To execute CMREPL with a command line parameter, type: CMREPL MYNEW.CFG o To execute CMREPL without a command line parameter, type: CMREPL ΓòÉΓòÉΓòÉ 1.2. CMLAN ΓòÉΓòÉΓòÉ CMLAN Purpose Allows you to install a redirected workstation. The configuration file is upgraded if it is from a previous version of Communications Manager. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMLANΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γö£ΓöÇ/IΓöÇΓöÇ configurationΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/DΓöÇΓöÇ [drive]ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇ/QΓöÇΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇ/KΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/RΓöÇΓöÇ response_fileΓöÇΓöÇΓö¼ΓöÇ/GΓöÇΓöÇ general_pathΓöÇΓö¼ΓöÇΓöÿ Γö£ΓöÇ/L1ΓöÇ log_file1ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/L2ΓöÇ log_file2ΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/QΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Specifies the drive for the command you want to process. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ Specifies the exact location of the command you want to process. ΓòÉΓòÉΓòÉ <hidden> /I configuration ΓòÉΓòÉΓòÉ Allows you to install or update IBM Communications Manager/2 Version 1.1 based on the specified configuration file. CONFIGURATION is a mandatory subparameter and is a fully qualified configuration file name that must have an extension of .CFG. You must enter either a colon or a space after the parameter. You do not need to enter the file extension on the command line. The configuration file option is mutually exclusive of the other options. When you specify this option, the setup processor installs according to the specified configuration file without requiring that you enter configuration services. You are returned to the command line after you exit the installation program. The specified configuration file is then copied to the \CMLIB subdirectory and upgraded if necessary. ΓòÉΓòÉΓòÉ <hidden> /D drive ΓòÉΓòÉΓòÉ Allows you to remove an installed Communications Manager on your machine. This option removes the Communications Manager executable code, the Communications Manager/2 folder, and the CONFIG.SYS updates. The Communications Manager configuration files and audit trail file are not removed. You do not have to type the blank or specify the disk drive. The default disk drive is the current drive. This request is rejected if Communications Manager is running. This request is also rejected if the drive specified does not contain Communications Manager or if the drive is not specified and Communications Manager is not installed on any drive. Note: /d is optional, if /d is used with /q then it is required. ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Indicates that Communications Manager should be deleted from the specified drive on your machine. ΓòÉΓòÉΓòÉ <hidden> /Q ΓòÉΓòÉΓòÉ When specified with the /d parameter, indicates that the deletion of files is done in "quiet" mode (without windows). ΓòÉΓòÉΓòÉ <hidden> /K ΓòÉΓòÉΓòÉ Allows you to request that features not needed by the default configuration file be removed. The default configuration file and contents of the target drive are compared, and any unneeded features are removed. This parameter is not supported if CMLAN was invoked from install diskettes/images. This request is rejected if Communications Manager is running with a configuration other than the default configuration. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Allows you to display the command line syntax on your screen. The command line syntax is displayed when any unrecognized parameters are entered. ΓòÉΓòÉΓòÉ <hidden> /R response_file ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Allows you to request the following installation actions based on the specified response file: o Install IBM Communications Manager. on a drive with no Communications Manager o Upgrade a previous Communications Manager release to IBM Communications Manager/2 Version 1.1 (including installation and configuration) o Configuration change with installation of additional features if necessary o Configuration change without installation o Re-install Communications Manager o Remove communication features (based on the default configuration) Response_file is a mandatory sub-parameter and is a fully qualified response file name that must have an extension of .RSP. This extension need not be entered on the command line. You must use a blank or colon after the /R parameter. The response file parameter is mutually exclusive of the previous parameters. Response files are processed when Communications Manager is installed and configured using the /R parameter. For more information on response files and remote installation, refer to the online IBM Communications Manager/2 Version 1.1 Response File Reference. ΓòÉΓòÉΓòÉ <hidden> /G ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the path to a directory on the server that can contain a general response file or other data files. You may not specify a diskette drive. ΓòÉΓòÉΓòÉ <hidden> /L1 ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the fully qualified name of the file into which the log file for remote installation and configuration is to be copied. ΓòÉΓòÉΓòÉ <hidden> /L2 ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the fully qualified name of the file into which the installation log file is to be copied. ΓòÉΓòÉΓòÉ <hidden> /Q ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. When specified with the /R parameter, indicates that response file processing is done in "quiet" mode (without windows). ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Command line parameters for this command are not case sensitive. You must use a colon or a space after any of the key parameter letters. If Communications Manager is not already installed, Communications Manager determines the location of the product code required for installation by examining the CMLAN invocation. For example, if the product code is on diskette images on LAN drive X, you would type X:\CMLAN at the command prompt. After you are prompted to specify the target drive (the drive that will receive the product files), you can complete all the configuration and feature selections. If Communications Manager is already installed, you are asked for the location of the Communications Manager product files required for installation. The location of the target drive is assumed to be the same as the current installation. The Interactive Configuration Interface is an additional function which is installed by default. If you do not want to install this additional function, select Options from the menu bar on the CMLAN window and select Remove Additional Functions. You can select the functions you want to remove. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are some examples of CMLAN usage: o To install MY.CFG located on D:\CMLIB, type the following and press Enter: CMLAN /I D:\CMLIB\MY.CFG o To enter configuration services and open MY.CFG in D:\CMLIB, type the following and press Enter: CMLAN /C D:\CMLIB\MY.CFG o To remove all features not associated with the default configuration, type the following and press Enter: CMLAN /K o To remove Communications Manager from the D drive, type the following and press Enter: CMLAN /D D: Use the following statement to do all of the following: o Process a response file named JOE.RSP on the Z drive in the directory CMUSERS. o Use Z:\GENERAL as the general path for additional files. o Keep a record of the processing in Z:\CMOUTPUT\JOE.LOG. CMLAN /R Z:\CMUSERS\JOE.RSP /G Z:\GENERAL /L1 z:\CMOUTPUT\JOE.LOG ΓòÉΓòÉΓòÉ 1.3. CMSETUP ΓòÉΓòÉΓòÉ CMSETUP Purpose Allows you to configure and install Communications Manager. The configuration file is upgraded if it is from a previous version of Communications Manager. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMSETUPΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γö£ΓöÇ/CΓöÇΓöÇ configurationΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/IΓöÇΓöÇ configurationΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/DΓöÇΓöÇ [drive]ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇ/QΓöÇΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇ/KΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/RΓöÇΓöÇ response_fileΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γö£ΓöÇ/SΓöÇΓöÇ source_pathΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/GΓöÇΓöÇ general_pathΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/L1ΓöÇ log_file1ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/L2ΓöÇ log_file2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/CRΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/MGΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γöé ΓööΓöÇmigr_fileΓöÇΓöÿ Γöé Γö£ΓöÇ/KLΓöÇ passwordΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/QΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Specifies the drive for the command you want to process. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ Specifies the exact location of the command you want to process. ΓòÉΓòÉΓòÉ <hidden> /C configuration ΓòÉΓòÉΓòÉ Allows you to create or change a configuration file. CONFIGURATION is a mandatory subparameter that indicates the fully qualified name of a configuration file that must have an extension of .CFG. You must enter either a colon or a space after the parameter. You do not need to enter the file extension on the command line. The configuration file option is mutually exclusive with the other options. When you specify this option, the setup processor invokes configuration services directly for interactive modification of the specified configuration file. You are returned to the command line after you exit configuration services and complete any resulting installation activities. This request is rejected if the Interactive Configuration Interface is not installed. ΓòÉΓòÉΓòÉ <hidden> /I configuration ΓòÉΓòÉΓòÉ Allows you to install or update IBM Communications Manager/2 Version 1.1 based on the specified configuration file. CONFIGURATION is a mandatory subparameter and is a fully qualified configuration file name that must have an extension of .CFG. You must enter either a colon or a space after the parameter. You do not need to enter the file extension on the command line. The configuration file option is mutually exclusive of the other options. When you specify this option, the setup processor installs according to the specified configuration file without requiring that you enter configuration services. You are returned to the command line after you exit the installation program. The specified configuration file is then copied to the \CMLIB subdirectory and upgraded if necessary. ΓòÉΓòÉΓòÉ <hidden> /D drive ΓòÉΓòÉΓòÉ Allows you to remove an installed Communications Manager on your machine. This option removes the Communications Manager executable code, the Communications Manager/2 folder, and the CONFIG.SYS updates. The Communications Manager configuration files and audit trail file are not removed. You do not have to type the blank or specify the disk drive. The default disk drive is the current drive. This request is rejected if Communications Manager is running. This request is also rejected if the drive specified does not contain Communications Manager or if the drive is not specified and Communications Manager is not installed on any drive. Note: /d is optional, if /d is used with /q then it is required. ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Indicates that Communications Manager should be deleted from the specified drive on your machine. ΓòÉΓòÉΓòÉ <hidden> /Q ΓòÉΓòÉΓòÉ When specified with the /d parameter, indicates that the deletion of files is done in "quiet" mode (without windows). ΓòÉΓòÉΓòÉ <hidden> /K ΓòÉΓòÉΓòÉ Allows you to request that features not needed by the default configuration file be removed. The default configuration file and contents of the target drive are compared, and any unneeded features are removed. This parameter is not supported if CMSETUP was invoked from install diskettes/images. This request is rejected if Communications Manager is running with a configuration other than the default configuration. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Allows you to display the command line syntax on your screen. The command line syntax is displayed when any unrecognized parameters are entered. ΓòÉΓòÉΓòÉ <hidden> /R response_file ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Allows you to request the following installation actions based on the specified response file: o Install IBM Communications Manager. on a drive with no Communications Manager o Upgrade a previous Communications Manager release to IBM Communications Manager/2 Version 1.1 (including installation and configuration) o Configuration change with installation of additional features if necessary o Configuration change without installation o Re-install Communications Manager o Remove communication features (based on the default configuration) Response_file is a mandatory sub-parameter and is a fully qualified response file name that must have an extension of .RSP. This extension need not be entered on the command line. You must use a blank or colon after the /R parameter. The response file parameter is mutually exclusive of the previous parameters. Response files are processed when Communications Manager is installed and configured using the /R parameter. For more information on response files and remote installation, refer to the online IBM Communications Manager/2 Version 1.1 Response File Reference. ΓòÉΓòÉΓòÉ <hidden> /S ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the path to the product image files existing on the server. ΓòÉΓòÉΓòÉ <hidden> /G ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the path to a directory on the server that can contain a general response file or other data files. You may not specify a diskette drive. ΓòÉΓòÉΓòÉ <hidden> /L1 ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the fully qualified name of the file into which the log file for remote installation and configuration is to be copied. ΓòÉΓòÉΓòÉ <hidden> /L2 ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the fully qualified name of the file into which the installation log file is to be copied. ΓòÉΓòÉΓòÉ <hidden> /CR ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Indicates that the response file is a "current response file" and that no check should be made to determine if it contains Extended Services specific keywords that need to be converted. If this parameter is not specified, the entire response file is checked to determine the level of the keywords. If they are the current level, remote installation or configuration continues normally. ΓòÉΓòÉΓòÉ <hidden> /MG ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Indicates that the response file will be migrated and that the migrated response file should be saved as migr_file upon completion of the remote installation/configuration request. The path, if not specified, defaults to \CMLIB. This parameter is only used when you are migrating from an Extended Services response file and you want to save the output of the migration step. If you do not specify a migration file name, the default file name rspfile.mig is used (where rspfile is the name of your response file). ΓòÉΓòÉΓòÉ <hidden> /KL ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. Specifies the keylock password of the configuration file. ΓòÉΓòÉΓòÉ <hidden> /Q ΓòÉΓòÉΓòÉ This parameter applies only when you are performing a response_file installation or configuration of Communications Manager. When specified with the /R parameter, indicates that response file processing is done in "quiet" mode (without windows). ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Command line parameters for this command are not case sensitive. You must use a colon or a space after any of the key parameter letters. If Communications Manager is not already installed, Communications Manager determines the location of the product code required for installation by examining the CMSETUP invocation. For example, if the product code is on diskette images on LAN drive X, you would type X:\CMSETUP at the command prompt. After you are prompted to specify the target drive (the drive that will receive the product files), you can complete all the configuration and feature selections. If Communications Manager is already installed, you are asked for the location of the Communications Manager product files required for installation. The location of the target drive is assumed to be the same as the current installation. The Interactive Configuration Interface is an additional function which is installed by default. If you do not want to install this additional function, select Options from the menu bar on the CMSETUP window and select Remove Additional Functions. You can select the functions you want to remove. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are some examples of CMSETUP usage: o To install MY.CFG located on D:\CMLIB, type the following and press Enter: CMSETUP /I D:\CMLIB\MY.CFG o To enter configuration services and open MY.CFG in D:\CMLIB, type the following and press Enter: CMSETUP /C D:\CMLIB\MY.CFG o To remove all features not associated with the default configuration, type the following and press Enter: CMSETUP /K o To remove Communications Manager from the D drive, type the following and press Enter: CMSETUP /D D: Use the following statement to do all of the following: o Process a response file named JOE.RSP on the Z drive in the directory CMUSERS. o Use Z:\GENERAL as the general path for additional files. o Keep a record of the processing in Z:\CMOUTPUT\JOE.LOG. CMSETUP /R Z:\CMUSERS\JOE.RSP /G Z:\GENERAL /L1 z:\CMOUTPUT\JOE.LOG ΓòÉΓòÉΓòÉ 1.4. CMSERVER ΓòÉΓòÉΓòÉ CMSERVER Purpose Syntax >>ΓöÇΓöÇCMSERVERΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇ/?ΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/SΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/TΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/FWΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> /? ΓòÉΓòÉΓòÉ Help (or any other incorrect parameter). ΓòÉΓòÉΓòÉ <hidden> /S ΓòÉΓòÉΓòÉ Source drive of diskette or images (required for installation). ΓòÉΓòÉΓòÉ <hidden> /T ΓòÉΓòÉΓòÉ Target drive CMLIB (default to working directory) must be at the same CM level (e.g. CM 1.1). ΓòÉΓòÉΓòÉ <hidden> /F filename ΓòÉΓòÉΓòÉ Create report of available feature for redirected workstations (default to CMSERVER.LOG). ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ There is no remove option (removed with all CM). /F without any other parameters will generate a report file without performing any installation. Note: CMSERVER is an interactive command and is not supported to be run by a CID process. To install server capability remotely, put CMSERVER=1 in the CM response file and issue the CMSETUP /R filename.rsp command. ΓòÉΓòÉΓòÉ 1.5. CMUPGRAD ΓòÉΓòÉΓòÉ CMUPGRAD Purpose Allows you to upgrade Communications Manager configuration files from the previous version of Communications Manager. This upgrade can take place without installing or going through the configuration dialog. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMUPGRADΓöÇΓöÇfilenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ Your current working drive must be the drive where Communications Manager resides. Your current working directory must be \CMLIB. ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where Communications Manager resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator. Your current working directory must be \CMLIB. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ The name of the configuration file to be upgraded. This configuration file must reside in the \CMLIB directory. Warning: Your source configuration file will be overwritten. If you wish to retain a copy of your original configuration file, make a backup prior to using the CMUPGRAD command. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ The upgrade facility files are in the \CMLIB\DLL directory. Make sure this directory is defined in the LIBPATH statement before using the CMUPGRAD command. Usually, this directory is included automatically in LIBPATH when you install Communications Manager. The log file UPGRADE.LOG is created after each upgrade and is located in the \CMLIB directory. In addition to the common .CFG file, there are configuration-related files created for some specific features such as APPN and LAN Adapter and Protocol Support (LAPS). These new files are saved in predefined directories. For example, .NDF and .CF2 files are saved for APPN and stored in \CMLIB. Note: 1. If you are upgrading from Extended Edition 1.30.1, make sure you run LAPS configuration to upgrade the information before you run Communications Manager configuration. 2. LAN Adapter and Protocol Support (LAPS) is available as part of Network Transport Services/2 (a separately orderable product). Any autotrace selections you may have saved in your configuration are lost when you upgrade to IBM Communications Manager/2 Version 1.1. Trace selections in IBM Communications Manager/2 Version 1.1 are perpetual and there is no need for autotrace. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of CMUPGRAD usage: o To upgrade an Extended Edition 1.30.1 or Extended Services configuration file to an IBM Communications Manager/2 Version 1.1 format, follow these steps: 1. Duplicate and rename your original configuration file as an archive copy. 2. Set your working directory to \CMLIB. For example: CD C:\CMLIB Drive C, in this example, is a variable and changes depending on which drive Communications Manager resides. 3. Type the command followed by the name of the configuration file to be upgraded. For example: CMUPGRAD MY.CFG ΓòÉΓòÉΓòÉ 1.6. CMVERIFY ΓòÉΓòÉΓòÉ CMVERIFY Purpose Verifies a Communications Manager configuration. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMVERIFYΓöÇΓöÇfilenameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇ/cΓöÇΓöÇ filenameΓöÇΓöÿ ΓööΓöÇ/eΓöÇΓöÇΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇ/iΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ ΓööΓöÇ/kΓöÇΓöÇ keyΓöÇΓöÿ ΓööΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇnetiniΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMVERIFY.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMVERIFY.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Indicates the name of the configuration file to be verified. The specified name is also used when the .CF2 and .SEC files are created. ΓòÉΓòÉΓòÉ <hidden> /c filename ΓòÉΓòÉΓòÉ Specifies a control file other than APPNV.CTL. ΓòÉΓòÉΓòÉ <hidden> /e ΓòÉΓòÉΓòÉ Updates Communications Manager Systems Network Architecture (SNA) information if the configuration file is verified successfully. This update process is possible without stopping and restarting Communications Manager (dynamic updating). When using this option, an error message indicates if you have requested a dynamic update that is not possible. ΓòÉΓòÉΓòÉ <hidden> /i netini ΓòÉΓòÉΓòÉ Indicates that ISDN parameters should be verified. The optional filename "netini" can be given to specify an alternate NETWORK.INI file to be used during ISDN verification. "netini" may be fully qualified or have relative or no path information included. The default file is NETWORK.INI, which is located in the active \CMLIB directory. ΓòÉΓòÉΓòÉ <hidden> /k key ΓòÉΓòÉΓòÉ Specifies the key value (service or master) to unlock the configuration. If keylocked, you cannot update the .CF2 configuration file or dynamically update the active .CFG configuration file without supplying the correct service or master key. The key value must be between 1 and 8 alphanumeric characters. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Displays syntax and help for CMVERIFY. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ CMVERIFY verifies a Communications Manager configuration and creates a binary SNA data configuration file (.CF2) and security file (.SEC) if an ASCII SNA data configuration file (.NDF) exists for the configuration. CMVERIFY uses the .NDF file to create the binary .CF2 file, which is used by Communications Manager during execution. If you choose to manually alter the SNA data in an .NDF file, or if a .CF2 file does not exist, you must run CMVERIFY on that configuration in order for the changes to be effective. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of CMVERIFY usage: o To verify the configuration "NODES" and update Communications Manager SNA information with the new configuration, type the following and press Enter: CMVERIFY nodes /e o To verify the configuration "ISDN1" including all ISDN parameters, type the following and press Enter : CMVERIFY isdn1 /i Note: The default NETWORK.INI file is used in this case. ΓòÉΓòÉΓòÉ 1.7. KEYLOCK ΓòÉΓòÉΓòÉ KEYLOCK Purpose Allows you to protect a configuration against unauthorized or accidental changes. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇKEYLOCKΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ Γö£ΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöñ A Γö£ΓöÇΓöÿ Γö£ΓöÇΓöÇconfig_file_nameΓöÇΓöÇΓöñ B Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇcurrent_pswdΓöÇΓöÇΓö¼ΓöÇ/LΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇ/CMΓöÇΓöÇΓöÇnew_mstr_pswdΓöÇΓö¼ΓöÇΓöÇΓöñ C Γö£ΓöÇΓöÿ ΓööΓöÇ/UΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/EMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓö¼ΓöÇ/CSΓöÇΓöÇΓöÇnew_srvc_pswdΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/ESΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the KEYLOCK.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the KEYLOCK.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Causes help text to be sent to STDOUT (usually the screen). If ? appears on the command line, it must be the first command line parameter. Help is displayed when an unrecognized keyword is encoutered or when no parameters are specified. ΓòÉΓòÉΓòÉ <hidden> config_file_name ΓòÉΓòÉΓòÉ The name of the configuration file in \CMLIB to change the password. ΓòÉΓòÉΓòÉ <hidden> current_pswd ΓòÉΓòÉΓòÉ The existing master or service password, if one exists. ΓòÉΓòÉΓòÉ <hidden> /L ΓòÉΓòÉΓòÉ Locks the configuration file, protecting it from updates. This can only be specified if current_pswd supplied is either the master password or the service password. ΓòÉΓòÉΓòÉ <hidden> /U ΓòÉΓòÉΓòÉ Unlocks the configuration file, allowing updates to the configuration. This can only be specified if current_pswd supplied is either the master password or the service password. ΓòÉΓòÉΓòÉ <hidden> /CM new_master_pswd ΓòÉΓòÉΓòÉ The new master password. This can only be specified if the current_pswd supplied is the master password or if the configuration currently has no password. ΓòÉΓòÉΓòÉ <hidden> /CS new_service_pswd ΓòÉΓòÉΓòÉ The new service password. This can only be specified if the current_pswd supplied is either the master password or the service password, or if the configuration currently has no password. ΓòÉΓòÉΓòÉ <hidden> /EM ΓòÉΓòÉΓòÉ Erases the existing master password. This can only be specified if the current_pswd supplied is the master password. ΓòÉΓòÉΓòÉ <hidden> /ES ΓòÉΓòÉΓòÉ Erases the existing service password. This can only be specified if the current_pswd supplied is either the master password or the service password. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ KEYLOCK can be executed from the Communications Manager/2 folder or from the command line. To execute KEYLOCK from the Communications Manager/2 folder, select Keylock. When you execute KEYLOCK from the command line, you can issue the command with or without parameters. Executing KEYLOCK without parameters has the same result as selecting Keylock from the Communications Manager/2 folder (a Presentation Manager window appears). If you issue the command with parameters, no windows will be shown, and errors will be written to STDOUT. If you want errors to be written to a file, provide a file name as follows: KEYLOCK :[parameters:] >error.file where error.file is the name of the file the errors are written to. KEYLOCK can be executed from any directory. If you use KEYLOCK on a configuration from a prior release of Communications Manager, the Upgrade window appears. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of KEYLOCK usage: o To use the windowed interface with the default config file name type: KEYLOCK o To use the windowed interface with config file "mycfg" type: KEYLOCK mycfg o To write help text to STDOUT type: KEYLOCK ? o To use the command line interface with config file "mycfg" and erase the master password type: KEYLOCK mycfg mstrpwd /EM o To use the non-windowed interface with config file "mycfg" and change the master password type: KEYLOCK mycfg mstrpwd /CM newmstr o To use the non-windowed interface with config file "mycfg" and change the service password type: KEYLOCK mycfg mstrpwd /CS newsvc or KEYLOCK mycfg svcpwd /CS newsvc o To use the non-windowed interface with config file "mycfg", erase the service password, and have errors written to file USER57.ERR, type: KEYLOCK mycfg svcpwd /ES >user57.err o To use the non-windowed interface with config file "mycfg" and lock the configuration file type: KEYLOCK mycfg svcpwd /L o To use the non-windowed interface with config file "mycfg" and unlock the configuration file type: KEYLOCK mycfg svcpwd /U ΓòÉΓòÉΓòÉ 1.8. VHAPINST.EXE ΓòÉΓòÉΓòÉ VHAPINST.EXE Purpose Adds or deletes the EHLLAPI virtual device driver statement. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇVHAPINST.EXEΓöÇΓöÇ/DΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the VHAPINST.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the VHAPINST.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /D ΓòÉΓòÉΓòÉ Deletes the EHLLAPI virtual device driver statement from your CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ By default, VHAPINST.EXE adds the EHLLAPI virtual device driver statement to your CONFIG.SYS file. To delete the EHLLAPI virtual device driver statement from your CONFIG.SYS file, use the /D optional parameter. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ C:\CMLIB\VHAPINST.EXE C:\CMLIB\VHAPINST.EXE /D ΓòÉΓòÉΓòÉ 2. Communications Commands ΓòÉΓòÉΓòÉ This chapter describes Communications Manager communications commands. Each command description includes the purpose of the command, a syntax diagram, a list of parameters, a discussion of the options, remarks, and examples. In addition to using the Presentation Manager interface to perform Communications Manager functions, you can issue commands to start certain functions from the OS/2 command line. Unless otherwise specified, directions in this book assume you are invoking commands from the OS/2 command line. To view the list of communications commands, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 2.1. CM ΓòÉΓòÉΓòÉ CM Purpose Starts Communications Manager from the OS/2 command line. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇfilenameΓöÇΓöÿ ΓööΓöÇ/IΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ Specifies the drive for the command you want to process. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ Specifies the exact location of the command you want to process. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Name of the configuration that you want to use when you start Communications Manager. If you do not specify this parameter, Communications Manager uses the default startup configuration specified in the initialization file CM.INI. Do not include the file extension. Any file extension is ignored and assumed to be .CFG. ΓòÉΓòÉΓòÉ <hidden> I ΓòÉΓòÉΓòÉ Specifies that you want the Communications Manager icon displayed in the window list. The default is not to display the Communications Manager icon in the window list. Note: If you start Communications Manager using this parameter and then select Communications Manager in the window list, the Communications Manager window appears. This window contains statements about Communications Manager initialization and startup. Minimize this window to clear your screen. If you close this window, Communications Manager is stopped. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ To start Communications Manager from the Communications Manager/2 folder, select Start Communications. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CM usage: o To start Communications Manager using the default configuration specified in the initialization file, type the following and press Enter: CM o To start Communications Manager using a configuration other than the one specified in the initialization file, type CM and the name of the configuration you want to activate. In the following example, MYCONFIG is the name of the configuration to be activated. CM MYCONFIG ΓòÉΓòÉΓòÉ 2.2. CMSTOP ΓòÉΓòÉΓòÉ CMSTOP Purpose Starts the program used to stop Communications Manager either from the Communications Manager/2 folder or from the command line. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMSTOPΓöÇΓöÇΓö¼ΓöÇNORMALΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇABNORMALΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMSTOP.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMSTOP.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> NORMAL ΓòÉΓòÉΓòÉ This parameter allows a normal stop of Communications Manager and all services that are either started or starting at the time of the request. A normal stop allows for a completion of normal processing before termination. This is the default parameter. ΓòÉΓòÉΓòÉ <hidden> ABNORMAL ΓòÉΓòÉΓòÉ This parameter permits an abnormal stop of Communications Manager and all services that are either started, starting, or stopping at the time of the request. An abnormal stop terminates processing without regard to the state of completion. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This command can be issued from any directory. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of CMSTOP usage: o To stop Communications Manager abnormally from the command line, type the following and press Enter: CMSTOP ABNORMAL ΓòÉΓòÉΓòÉ 2.3. RECEIVE-for CICS Host ΓòÉΓòÉΓòÉ RECEIVE-for CICS Host Purpose Receives a file from an IBM CICS host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇRECEIVEΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename1ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇ.extΓöÇΓöÿ ΓööΓöÇid:ΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ(ΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇCRLFΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓööΓöÇNOCRLFΓöÇΓöÿ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇΓö¼ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöñ Γöé Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γöé Γöé ΓööΓöÇBINARYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the RECEIVE.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the RECEIVE.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where you want the file that you are receiving from the host computer to reside. Specify this drive only if it is not the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the file being received is to reside. Specify a path if the file is not to reside in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename1 ΓòÉΓòÉΓòÉ The name of the workstation file being received from the host computer. Use the FAT or HPFS naming conventions described in OS/2 Technical Library. In the examples for this command, report is the file name for the FAT file system; "long filename" is the file name for HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ The extension for the workstation FAT file being received from the host computer. In the examples for this command, .dat is the extension using the FAT file system. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 emulation session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. If no 3270 emulation sessions are configured and started, an error message is returned. You can view the identifiers in the configuration file and from the File Transfer Operations Menu. In the examples for this command, stat2 is the ID parameter. This parameter is separated from the file name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> filename2 ΓòÉΓòÉΓòÉ The CICS file name of the file that you want to transfer. The CICS file name must be the name in the first record of the file in CICS temporary storage. In the examples for this command, report is the file name. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to translate workstation files from EBCDIC to ASCII so that the file is readable to the workstation. When receiving text files from the host computer, specify the ASCII option. If the host computer file is already in ASCII form, do not supply this option. Do not use this option when you are transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the host file code page you are using for the host file being received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the emulation that is specified in the keyboard remap profile. The host code page also specifies the file transfer command program you are using. This option is valid only when the ASCII keyword is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the workstation file code page you are using for the workstation file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the active command line screen group. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Allows you to send or receive files that were transferred using Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that do not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> Binary ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes binary files to be sent to the workstation without being changed. When receiving binary files from the host computer, always specify the BINARY option. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to delete carriage-return and line-feed characters from the host data before sending it to the workstation. If you specified the ASCII option, EBCDIC blanks are removed. If you specified the BINARY option, ASCII blanks are removed. ΓòÉΓòÉΓòÉ <hidden> NOCRLF ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies that the host computer file being sent does not consist of logical records delimited by carriage-return or line-feed characters. The file transfer program does not split the records, and the file is written into the workstation file as one long string of data. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The part of the command which follows is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nn is not specified, 00 is the default, which means the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the RECEIVE command in a command file and run that file from the OS/2 command line. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started, and you must be logged on and ready to receive a command. The options you use are always those that you specify in the command or those implied by the command. The options in the file at the host computer, if any, are never used. The options CRLF and NOCRLF are mutually exclusive. The options CRLF and ASCII imply each other if only one is specified. The options BINARY and ASCII are mutually exclusive. Warning: Unpredictable ASCII to EBCDIC translation occurs if neither ASCII nor BINARY is specified. The options BINARY and NOCRLF imply each other if only one is specified. If no options are specified, CRLF and ASCII are assumed. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the RECEIVE command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for descriptions of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of RECEIVE usage: o To receive a file with an FAT file name from an IBM CICS host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:report.dat stat2:report (CRLF ASCII o To receive a file with an HPFS file name from an IBM CICS host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:\firstdir\seconddir\"long filename" stat2:report (CRLF ASCII Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 2.4. SEND-for CICS Host ΓòÉΓòÉΓòÉ SEND-for CICS Host Purpose Sends a file to an IBM CICS host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSENDΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename1ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ ΓööΓöÇ.extΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇid:ΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇ)commentsΓöÇΓöÿ Γöé Γöé Γöé ΓööΓöÇ(ΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇCRLFΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓööΓöÇNOCRLFΓöÇΓöÿ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇΓö¼ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöñ Γöé Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γöé Γöé ΓööΓöÇBINARYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the SEND.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the SEND.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where the workstation file that you want to send to the host computer resides. Specify this drive only if it is not the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the workstation file that you want to send resides. Use this path only if the file is not in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename1 ΓòÉΓòÉΓòÉ The name of the workstation file that you want to send. Use the FAT or HPFS naming conventions described in OS/2 Technical Library. In the examples for this command, report is the file name for the FAT file system; "long filename" is the file name for HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ The extension for the workstation FAT file that you want to send. In the examples for this command, .dat is the extension. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 emulation session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. If no 3270 emulation sessions are configured and started, an error message is returned. You can view the identifiers in the configuration file and from the File Transfer Main Menu. In the examples for this command, stat2 is the ID parameter. This parameter is separated from the file name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> filename2 ΓòÉΓòÉΓòÉ The CICS file name of the file that you want to transfer. The name can be up to 8 characters and must begin with a letter. The file name may be a program name, a transaction identifier, or any other identifier selected by the CICS application programmer. This name is written into the first record of the host computer file to allow host users, such as another transaction, to identify the data sent from the workstation. In the examples for this command, report is the file name. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Causes the host program to translate work station files from ASCII to EBCDIC so that the file is readable to the host computer. When sending text files to the host computer, specify the ASCII option. If the workstation file is already in EBCDIC form, do not supply this option. Do not use this option when you are transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Specifies the host file code page you are using for the host file being received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the emulation that is specified in the keyboard remap profile. The host code page also specifies the file transfer command program you are using. This option is only valid when the ASCII keyword is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Specifies the workstation file code page you are using for the workstation file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the active command-prompt screen group. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Allows you to send or receive files that were transferred using Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that do not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> BINARY ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Causes binary files to be sent to the host computer without being changed. When sending binary files to the host computer, always specify the BINARY option. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Causes the host program to delete carriage return and line feed characters from the workstation data before storing it at the host computer. When sending an ASCII or EBCDIC file to the computer, you should always supply the CRLF option so the file is readable when on the host computer. Note: The file is written into CICS temporary storage using one item on the queue to represent each logical record. Null records in workstation files, indicated by two carriage return or line feed characters in a row, are represented in the file in CICS temporary storage by an item with two blanks in it. If you specify the ASCII option, the blanks inserted into the file are EBCDIC blanks. The maximum length allowed for a logical record is 32767 bytes. If a logical record exceeds this size, you receive a warning message at the end of the file transfer. Data is not lost but may be incorrectly formatted on the host. ΓòÉΓòÉΓòÉ <hidden> NOCRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Specifies that the workstation file sent does not consist of logical records delimited by carriage-return or line-feed characters. The file transfer program does not split the records, and the file is written into CICS temporary storage using one item on the queue to represent each inbound data buffer. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nn is not specified, 00 is the default, which means the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> )comments ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a left parenthesis with one space between each option. In the examples for this command, ASCII is the option. Allows you to supply comments or control information to be associated with the host computer file. Indicate the end of your options and the beginning of your comments by typing a blank followed by a right parenthesis. Follow the parenthesis with your comments. The blank before the right parenthesis is required for proper recognition of the options specified. If you want to add comments without specifying any options, type the left and right parentheses immediately before the comments to indicate the absence of options. Comments are written into the first record of the host computer file, where they are available for another transaction to use. In the examples for this command, )enddata is the comment. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the SEND command in a command file and run that file from the OS/2 command line. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started, and you must be logged on and ready to receive a command. The options you use are always written into the first record of the host computer file, regardless of whether they were specified at the workstation. The options CRLF and NOCRLF are mutually exclusive. The options CRLF and ASCII imply each other if only one is specified. The options BINARY and ASCII are mutually exclusive. The options BINARY and NOCRLF imply each other if only one is specified. If no options are specified, CRLF and ASCII are assumed. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the SEND command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for descriptions of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of SEND usage: o To send a file with an FAT file name to an IBM CICS host computer, type the SEND command with the necessary parameters at an OS/2 command line and press Enter. For example: send a:report.dat stat2:report (ASCII )enddata o To send a file with an HPFS file name to an IBM CICS host computer, type the SEND command with the necessary parameters at an OS/2 command line and press Enter. For example: send a:\firstdir\seconddir\"long filename" stat2:report (ASCII )enddata Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 2.5. RECEIVE-for TSO Host ΓòÉΓòÉΓòÉ RECEIVE-for TSO Host Purpose Receives a file from an IBM TSO host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇRECEIVEΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇdatasetnameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇ.extΓöÇΓöÿ ΓööΓöÇid:ΓöÇΓöÿ ΓööΓöÇ(membername)ΓöÇΓöÿ ΓööΓöÇ/passwordΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓö¼ΓöÇAPPENDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöñ Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇCRLFΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the RECEIVE.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the RECEIVE.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where you want the data set that you are receiving from the host computer to reside. Specify a drive if the file is not to reside on the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the file being received is to reside. Specify a path if the file is not to reside in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ The name of the file being received from the host computer. Use the FAT or HPFS naming conventions described in OS/2 Technical Library. In the examples for this command, myfile is the file name for the FAT file system; "long filename" is the name for HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ The extension for the FAT file being received from the host computer. The file name will not have an extension if you do not supply one. In the examples for this command, .txt is the extension. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 emulation session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. For 3270 emulation sessions, this parameter can be either a long session ID or a short session ID. You can view the identifiers in the configuration file and from the File Transfer Operations Menu. In the examples for this command, stat2 is the ID parameter. This parameter is separated from the data set name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> datasetname ΓòÉΓòÉΓòÉ The name of the TSO data set to be received. To show that the user ID is not prefixed, you can Enter the data set name and member name together and enclose the information in quotation marks. In the examples for this command, boss is the data set name. ΓòÉΓòÉΓòÉ <hidden> (membername) ΓòÉΓòÉΓòÉ The name of a member of a partitioned data set. The data set must already exist. In the examples for this command, bossname is the member name. Note that the member name is enclosed in parentheses (). ΓòÉΓòÉΓòÉ <hidden> /password ΓòÉΓòÉΓòÉ The password that allows access to password-protected TSO data sets. This parameter is required only if the data set is password-protected. In the examples for this command, gky5hf is the password. Note that the password is preceded by a slash (/). ΓòÉΓòÉΓòÉ <hidden> APPEND ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Allows you to attach the host data set to the end of an existing workstation file. Warning: If APPEND is not specified and a workstation file already exists with the same name, the host data set replaces the existing workstation file. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Causes the host program to translate workstation files from EBCDIC to ASCII so that the file is readable to the workstation. When receiving text data sets from the host computer, always specify the ASCII option. If the host data set is already in ASCII form, do not supply this option. Do not use this option when you are transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the host computer file code page you are using for the host file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the terminal emulation session that is specified in the keyboard remap profile. The host code page also specifies the file transfer command program you are using. This option is only valid when the ASCII keyword is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the workstation file code page you are using for the workstation file being received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the active command-prompt screen group. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Allows you to send or receive files that were transferred using Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that did not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nn is not specified, 00 is the default, which means the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Causes the host program to insert carriage returns and line feed characters as the last 2 characters of each line before sending the data set to the workstation. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the RECEIVE command in a command file and run that file from the OS/2 command line. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started and you must be logged on and ready to receive a command. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the RECEIVE command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for descriptions of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of RECEIVE usage: o To receive a file with an FAT file name from an IBM TSO host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:myfile.txt stat2:boss(bossname)/gky5hf ASCII o To receive a file with an HPFS file name from an IBM TSO host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:\firstdir\seconddir\"long filename" stat2:boss(bossname)/gky5hf ASCII Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 2.6. SEND-for TSO Host ΓòÉΓòÉΓòÉ SEND-for TSO Host Purpose Sends a file to an IBM TSO host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSENDΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilenameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ ΓööΓöÇ.extΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇdatasetnameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇid:ΓöÇΓöÿ ΓööΓöÇ(membername)ΓöÇΓöÿ ΓööΓöÇ/passwordΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓö¼ΓöÇAPPENDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇCRLFΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇBLKSIZE (n)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇLRECL (n)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇRECFMΓöÇΓöÇΓö¼ΓöÇ(F)ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γö£ΓöÇ(U)ΓöÇΓöñ Γöé Γöé ΓööΓöÇ(V)ΓöÇΓöÿ Γöé Γö£ΓöÇSPACE(qΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇ)ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γöé ΓööΓöÇ,iΓöÇΓöÿ Γö£ΓöÇAVBLOCK (n)ΓöÇΓöñ Γöé Γöé Γö£ΓöÇCYLINDERSΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇTRACKSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the SEND.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the SEND.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where the workstation file that you want to send to the host computer resides. Specify this drive only if it is not the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the workstation file that you want to send resides. Use this path only if the file is not in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ The name of the workstation file that you want to send. Use the FAT or HPFS naming conventions described in OS/2 Technical Library. In the examples for this command, myfile is the file name for the FAT file system; "long filename" is the file name for the HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ The extension of the workstation FAT file that you want to send. You are allowed 4 characters for the extension, including the period. In the examples for this command, .txt is the extension. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 emulation session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. You can view the identifiers in the configuration file and from the File Transfer Main Menu. In the examples for this command, stat2 is the ID parameter. This parameter is separated from the data set name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> datasetname ΓòÉΓòÉΓòÉ The TSO data set name for the file that you are sending. To show that the user ID does not have a prefix, you can type the data set name and member name together and enclose the information in quotation marks. In the examples for this command, boss is the data set name. ΓòÉΓòÉΓòÉ <hidden> (membername) ΓòÉΓòÉΓòÉ The name of a member of a partitioned data set. The data set must already exist. In the examples for this command, bossname is the member name. Note that the member name is enclosed in parentheses (). ΓòÉΓòÉΓòÉ <hidden> /password ΓòÉΓòÉΓòÉ The password that allows access to password-protected TSO data sets. This parameter is required only if the data set is password-protected. In the examples for this command, gky5hf is the password. Note that the password is preceded by a slash (/). ΓòÉΓòÉΓòÉ <hidden> APPEND ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Allows you to attach the workstation file to the end of an existing host data set. The APPEND option overrides any other values specified for LRECL and RECFM. You may not specify APPEND for members of a partitioned data set. Warning: If APPEND is not specified and a host computer file already exists with the same name, the host computer file is replaced. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Causes the host program to translate workstation files from ASCII to EBCDIC so that the file is readable to the host computer. When sending text files to the host computer, always specify the ASCII option. If the workstation file is already in EBCDIC form, do not supply this option. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the host file code page you are using for the host file being received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the emulation that is specified in the keyboard remap profile. The host code page also specifies the file transfer command program you are using. This option is valid only when the ASCII keyword is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the workstation file code page you are using for the workstation file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the active command line screen group. This option is valid only when the ASCII keyword is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Allows you to send or receive files that were transferred using Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that do not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Causes the host program to delete carriage-return and line-feed characters from the workstation data before storing it in the host computer. When sending an ASCII or EBCDIC file to the host computer, you should always supply the CRLF option so the file is readable when on the host computer. ΓòÉΓòÉΓòÉ <hidden> BLKSIZE(n) ΓòÉΓòÉΓòÉ Specifies the size of the host data set, where n is the length in bytes of a data block. If you omit BLKSIZE, the host default is used. The host default is usually LRECL for new files. If you are replacing or appending to a file, BLKSIZE is ignored. ΓòÉΓòÉΓòÉ <hidden> LRECL(n) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Provides the logical record length of the host data set, where n is the number of characters in each record. If LRECL is omitted, the host defaults are used. The host default value for new files is usually 80 characters for new data sets. If you are replacing an existing data set, its record length is used as the record length of the new version. If you are appending a data set, the current record length of the data set is used and the LRECL value specified is ignored. When using variable-length records, set n to the maximum record size that the host computer can accept. The program automatically resets the logical record length equal to the longest record actually sent. ΓòÉΓòÉΓòÉ <hidden> RECFM F/V/U ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the record format and characteristics of the host computer file. RECFM is followed by one of the following characters: o F specifies that the file contains fixed-length records. o V specifies that the file contains variable-length records. o U specifies that the data set contains undefined-length records. For new files, the default is F, unless the CRLF option is specified, in which case V is the default. ΓòÉΓòÉΓòÉ <hidden> SPACE(q[,i]) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the amount of space allocated for a new data set, where q (mandatory) is the quantity of space allocated initially for a data set and i (optional) is the increment of space added to the data set each time the previously allocated space is filled. If you use SPACE, you can use one of these three options to specify the units used for quantity and increment: o AVBLOCK(n) specifies the average block length of the records to be written to the data set, where n is the desired average block length in bytes. o TRACKS specifies that the unit of space is a track. o CYLINDERS specifies that the unit of space is a cylinder. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter with one space and one additional space between each option. In the examples for this command, ASCII is the option. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nn is not specified, 00 is the default, which means the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the SEND command in a command file and run that file from the OS/2 command prompt. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started, and you must be logged on and ready to receive a command. The options AVBLOCK, CYLINDERS, TRACKS, BLKSIZE, RECFM, and SPACE are valid only for physical sequential data sets. The options AVBLOCK, CYLINDERS, and TRACKS are mutually exclusive. If neither AVBLOCK, CYLINDERS, nor TRACKS is specified, the value specified for BLKSIZE is used as the space allocation unit. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the SEND command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for descriptions of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of SEND usage: o To send a file with an FAT file name to an IBM TSO host computer, type the SEND command with the necessary parameters at an OS/2 command prompt and press Enter. For example: send a:myfile.txt stat2:boss(bossname)/gky5hf ASCII o To send a file with an HPFS file name to an IBM TSO host computer, type the SEND command with the necessary parameters at an OS/2 command prompt and press Enter. For example: send a:\firstdir\seconddir\"long filename" stat2:boss(bossname)/gky5hf ASCII Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 2.7. RECEIVE-for VM Host ΓòÉΓòÉΓòÉ RECEIVE-for VM Host Purpose Receives a file from an IBM VM host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇRECEIVEΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename1ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename2ΓöÇΓöÇfiletypeΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇ.extΓöÇΓöÿ ΓööΓöÇid:ΓöÇΓöÿ ΓööΓöÇfilemodeΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ(ΓöÇΓöÇΓöÇΓö¼ΓöÇAPPENDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöñ Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇCRLFΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the RECEIVE.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the RECEIVE.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where you want the file that you are receiving from the host computer to reside. Specify this drive only if it is not the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the file being received is to reside. Specify a path if the file is not to reside in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename1 ΓòÉΓòÉΓòÉ The name of the workstation file that is to receive the host computer data. Use the FAT or HPFS naming conventions described in OS/2 Technical Library. In the examples for this command, report is the file name for the FAT file system; "long filename" is the filename for HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ For an FAT file, the extension for the workstation file that receives the data. In the examples for this command, .dat is the extension. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 emulation session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. For 3270 emulation sessions, this parameter can be either a long session ID or a short session ID. You can view the identifiers in the configuration file and from the File Transfer Main Menu. In the examples for this command, stat2 is the ID. This parameter is separated from the file name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> filename2 ΓòÉΓòÉΓòÉ The VM file name of the file that you want to transfer. In the examples for this command, report is the file name on the VM system. ΓòÉΓòÉΓòÉ <hidden> filetype ΓòÉΓòÉΓòÉ The VM file type of the file that you want to transfer. In the examples for this command, script is the file type. Warning: APPEND, ASCII, CRLF, MIGR, SUB, H(nnnnn), and P(nnnnn) are reserved keywords for transferring files. They should not be used as a VM file type. If used as a VM file type, undesirable results can occur, including the possible destruction of host files. ΓòÉΓòÉΓòÉ <hidden> filemode ΓòÉΓòÉΓòÉ The VM file mode of the file that you want to transfer. This is an optional parameter. If this parameter is omitted, the default is A1. In the examples for this command, A is the file mode. ΓòÉΓòÉΓòÉ <hidden> APPEND ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Allows you to attach the information from the host computer file to the end of an existing workstation file. Warning: If APPEND is not specified and a workstation file already exists with the same name, the file is replaced with the received file. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to translate the host computer file from EBCDIC to ASCII so that the file is readable on the workstation. When receiving text files from the host computer, specify the ASCII option. If the host computer file is already in ASCII form, do not supply this option. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the host file code page you are using for the host file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the emulation that is specified in the keyboard remap profile. The host character set also specifies the file transfer command program you are using. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the workstation file code page you are using for the workstation file received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the active command line screen group. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Allows you to send or receive files that were transferred using Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that do not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to insert carriage-return and line-feed characters as the last 2 characters of each line before sending it to the workstation. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nnis not specified, 00 is the default, which means that the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the RECEIVE command in a command file and run that file from the OS/2 command line. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started, and you must be logged on and ready to receive a command. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the RECEIVE command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for a list and description of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer program name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of RECEIVE usage: o To receive a file with an FAT file name from an IBM VM host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:report.dat stat2:report script A (CRLF ASCII o To receive a file with an HPFS file name from an IBM VM host computer, type the RECEIVE command with the necessary parameters at an OS/2 command line and press Enter. For example: receive a:\firstdir\seconddir\"long filename" stat2:report script A (CRLF ASCII Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 2.8. SEND-for VM Host ΓòÉΓòÉΓòÉ SEND-for VM Host Purpose Sends a file to an IBM VM host computer. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSENDΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename1ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdrive1ΓöÇΓöÿ ΓööΓöÇpath1ΓöÇΓöÿ ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ ΓööΓöÇ.extΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilename2ΓöÇΓöÇfiletypeΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇid:ΓöÇΓöÿ ΓööΓöÇfilemodeΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ(ΓöÇΓöÇΓöÇΓö¼ΓöÇAPPENDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γö£ΓöÇASCIIΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöñ Γöé Γö£ΓöÇH(nnnnn)ΓöÇΓöñ Γö£ΓöÇMIGRΓöÇΓöñ Γöé Γöé ΓööΓöÇP(nnnnn)ΓöÇΓöÿ ΓööΓöÇSUBΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇCRLFΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇLRECL nΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇRECFMΓöÇΓöÇΓö¼ΓöÇFΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇVΓöÇΓöÿ Γöé ΓööΓöÇT(nn)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive1 ΓòÉΓòÉΓòÉ The drive where the SEND.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path1 ΓòÉΓòÉΓòÉ The path designator that specifies where the SEND.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> drive2 ΓòÉΓòÉΓòÉ The drive where the workstation file that you want to send to the host computer resides. Specify this drive only if it is not the default drive. In the examples for this command, a: is the drive. ΓòÉΓòÉΓòÉ <hidden> path2 ΓòÉΓòÉΓòÉ The path designator that specifies where the workstation file that you want to send resides. Use this path only if the file is not in the current directory. ΓòÉΓòÉΓòÉ <hidden> filename1 ΓòÉΓòÉΓòÉ The name of the file that you want to send. Use the File Allocation Table (FAT) or High Performance File System (HPFS) naming conventions described in OS/2 Technical Library. In the examples for this command, report is the file name for the FAT file system; "long filename" is the file name for the HPFS. ΓòÉΓòÉΓòÉ <hidden> .ext ΓòÉΓòÉΓòÉ The extension for the FAT file that you want to send. In the examples for this command, .dat is the extension. ΓòÉΓòÉΓòÉ <hidden> id: ΓòÉΓòÉΓòÉ The 1- to 8-character name that identifies the 3270 session used for the file transfer. If you do not supply this parameter, the first configured 3270 emulation session that you start is used for the file transfer. For 3270 emulation sessions, this parameter can be either a long session ID or a short session ID. You can view the identifiers in the configuration file and from the File Transfer Operations Menu. This parameter is separated from the file name by a colon (:). ΓòÉΓòÉΓòÉ <hidden> filename2 ΓòÉΓòÉΓòÉ The name of the file on VM into which you want to receive the data. In the examples for this command, report is the file name on the VM system. ΓòÉΓòÉΓòÉ <hidden> filetype ΓòÉΓòÉΓòÉ The VM file type of the file that you want to transfer. In the examples for this command, script is the file type. Warning: APPEND, ASCII, CRLF, MIGR, SUB, H(nnnnn), and P(nnnnn) are reserved keywords for transferring files. They should not be used as a VM file type. If used as a VM file type, undesirable results can occur, including the possible destruction of host files. ΓòÉΓòÉΓòÉ <hidden> filemode ΓòÉΓòÉΓòÉ The VM file mode of the file that you want to transfer. This is an optional parameter. If this parameter is omitted, the default is A1. In the examples for this command, A is the file mode. ΓòÉΓòÉΓòÉ <hidden> APPEND ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Allows you to attach the workstation file to the end of an existing host computer file. The APPEND option overrides any other values specified for LRECL and RECFM. Warning: If APPEND is not specified and a host computer file already exists with the same name, the host computer file is replaced. ΓòÉΓòÉΓòÉ <hidden> ASCII ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to translate workstation files from ASCII to EBCDIC so that the file is readable to the host computer. When sending text files to the host, specify the ASCII option. If the workstation file is already in EBCDIC form, do not supply this option. Do not use this option when you are transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> H(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the host file code page to be used for the host file being received, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the code page for the host character set of the emulation session that is specified in the keyboard remap profile. The host code page also specifies the file transfer command program to be used. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> P(nnnnn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the workstation file code page to be used for the workstation file being sent, where nnnnn is the code page number. Refer to OS/2 Keyboard and Code Pages for information on code pages. If you do not specify a code page, the system uses the active code page for the command line screen group. This option is valid only when the ASCII option is specified. ΓòÉΓòÉΓòÉ <hidden> MIGR ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Allows you to send or receive files that were transferred with Extended Edition 1.30.1 or Extended Services and Communications Manager/2 Version 1.0. This option applies only to files that were transferred in one direction using the ASCII option. Use this option to transfer the file back to the source location. This option is valid only if the ASCII option is also specified. If MIGR is specified but the ASCII option is not, MIGR is ignored. ΓòÉΓòÉΓòÉ <hidden> SUB ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies multiple-substitute mapping for the file transfer. All unmatched code points are mapped to a specific set of characters in the target code page to enhance comprehension. With multiple-substitute mapping, a file transferred to a host computer and transferred back to the workstation is not identical to the original file. Code points that do not have a match in the target code page are different. If SUB is not specified, the file transfer function uses one-to-one character mapping. One-to-one character mapping maps each unmatched code point to a unique character in the target code page. With one-to-one character mapping, a file transferred to a specific host computer and transferred back to the workstation is identical to the original file. This option is valid only when the ASCII option is specified. If SUB is specified but the ASCII option is not, SUB is ignored. ΓòÉΓòÉΓòÉ <hidden> CRLF ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Causes the host program to delete carriage-return and line-feed characters from the workstation data before storing it at the host computer. When sending an ASCII or EBCDIC file to the host computer, you should supply the CRLF option so the file is readable on the host computer. Do not use this option when transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> LRECL n ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Provides the logical record length of the host computer file, where n is the number of characters in each record. If LRECL is omitted, the host defaults are used. The host default value for new files is usually 80. If you are replacing an existing host computer file, its record length is used as the record length of the new version. If you are appending a file, the current record length of the file is used and the LRECL value specified is ignored. When using variable-length records, set n to the maximum record size that the host computer can accept. The program automatically resets the logical record length to the length of the longest record actually sent. Do not use this option when transferring a binary file. ΓòÉΓòÉΓòÉ <hidden> RECFM F/V ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the record format and characteristics of the host computer file. RECFM is followed by F or V: o F specifies that the file contains fixed-length records. o V specifies that the file contains variable-length records. For new files, the default is F, unless the CRLF option is specified, in which case V is the default. ΓòÉΓòÉΓòÉ <hidden> T(nn) ΓòÉΓòÉΓòÉ Note: The following part of the command is an option. Options are separated from the last parameter by a required left parenthesis with one space between each option. In the examples for this command, CRLF and ASCII are the options. Specifies the period of time that the file transfer program waits for the host computer to respond before canceling the file transfer request. nn is a 2-digit integer in a range from 00 through 99 that indicates the number of 30-second increments the file transfer program waits for the host computer to respond. If nn is not specified, 00 is the default, which means the file transfer program waits indefinitely for the host computer to respond. The file transfer program sends a message to the screen every 30 seconds until the host computer responds. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ You can type the SEND command in a command file (.CMD) and run that file from the OS/2 command prompt. You can transfer more than one file at a time, as long as each file transfer is on a different emulation session and is initiated from a different OS/2 session. The maximum number of concurrent file transfers is nine. To issue multiple file transfers, specify a different emulation session for each file transfer with the ID in the file transfer command. The emulation session that corresponds to the ID that you specify must be started, and you must be logged on and ready to receive a command. The MIGR and SUB options cannot be specified together. If both are specified, an error is displayed stating that the second option is not valid. If an error occurs during an attempted file transfer, the SEND command sets the system environment variable ERRORLEVEL to a value equal to the returned TRANS code minus three. Refer to Message Reference for descriptions of the TRANS codes. If your host file transfer program name is not IND$FILE, use the OS/2 SET command before issuing the file transfer command. To use the SET command, type the following and press Enter: SET IND_FILE=xxxxxxxx where xxxxxxxx is your host file transfer program name. You should use the OS/2 SET command in the CONFIG.SYS file to avoid typing the SET command each time. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of SEND usage: o To send an ASCII file with an FAT file name to an IBM VM host computer, type the SEND command with the necessary parameters at an OS/2 command prompt and press Enter. For example: send a:report.dat stat2:report script A (CRLF ASCII o To send an ASCII file with an HPFS file name to an IBM VM host computer, type the SEND command with the necessary parameters at an OS/2 command prompt and press Enter. For example: send a:\firstdir\seconddir\"long filename" stat2:report script A (CRLF ASCII Note the use of quotation marks when specifying a filename containing blanks. ΓòÉΓòÉΓòÉ 3. Utilities ΓòÉΓòÉΓòÉ This chapter describes Communications Manager utilities. Each command description includes the purpose of the command, a syntax diagram, a list of parameters, a discussion of options, remarks, and examples. In addition to using the Presentation Manager interface to perform Communications Manager functions, you can issue commands to start certain functions from the OS/2 command line. Unless otherwise specified, directions in this book assume you are invoking commands from the OS/2 command line. To view the list of utilities, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 3.1. APPNRST ΓòÉΓòÉΓòÉ APPNRST Purpose Generates a detailed report of the binary configuration file (.CF2) contents. This command is also used to restore damaged or deleted .NDF and .SEC files. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇAPPNRSTΓöÇΓöÇfilenameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇoutfileΓöÇΓöÿ ΓööΓöÇ/rΓöÇΓöÇΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇ/cΓöÇΓöÇ filenameΓöÇΓöÿ ΓööΓöÇ/wΓöÇΓöÇ(n)ΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the APPNRST.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the APPNRST.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Indicates the name of the binary configuration file (.CF2) to use for the report or restore operation. A .CF2 file must exist to use the APPNRST command. In the examples for this command, nodes is the file name. ΓòÉΓòÉΓòÉ <hidden> outfile ΓòÉΓòÉΓòÉ Indicates the name of the output file to be generated, for example, a report file. In the examples for this command, nodes.ndf is the output file name. ΓòÉΓòÉΓòÉ <hidden> /r ΓòÉΓòÉΓòÉ Generates a report of the binary configuration file (.CF2). If no output file is specified, creates a file with an .NDF extension. This is not a true node definitions file in that it cannot be verified. When generating a report using this option, no security file is created. ΓòÉΓòÉΓòÉ <hidden> /c filename ΓòÉΓòÉΓòÉ Specifies a control file other than APPNV.CTL. ΓòÉΓòÉΓòÉ <hidden> /w(n) ΓòÉΓòÉΓòÉ Specifies the message level. The value n can be in the range of 0 to 3, where: 0 Disables all messages 1 Displays error messages 2 Displays error and warning messages 3 Displays all messages (including informational messages). ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ After using APPNRST to restore a node definitions file, you can verify the restored .NDF file, create a new .CF2 file, and generate a new .SEC file using the CMVERIFY command. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of APPNRST usage: o To generate a report file with the name nodes.ndf, type the following and press Enter: APPNRST nodes.ndf /r o To restore the file nodes.NDF and create a security file nodes.SEC, type the following and press Enter: APPNRST nodes ΓòÉΓòÉΓòÉ 3.2. CMANSWER ΓòÉΓòÉΓòÉ CMANSWER Purpose Enables you to receive an incoming call over a switched network for the purpose of sending and receiving data. The protocols that are supported once the connection has been established are LAN and SDLC. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMANSWERΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ/CΓöÇΓöÇ[ALLNAME]:callnameΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γö£ΓöÇ/PΓöÇΓöÇ[ROTOCOL]:ΓöÇΓöÇΓö¼ΓöÇLANΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γöé Γö£ΓöÇSDLCΓöÇΓöñ Γöé Γöé ΓööΓöÇIDLCΓöÇΓöÿ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ/AΓöÇΓöÇ[DAPTER]:nΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓöÿ ΓööΓöÇnΓöÇΓöÿ All CMANSWER parameters are optional. All parameters may be specified using the first letter of the keyword. The CMANSWER window is displayed if no parameters are specified. ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMANSWER.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMANSWER.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /CALLNAME: callname ΓòÉΓòÉΓòÉ An existing incoming Directory Entry Name or permanent connection name which has been created during connection manager configuration. The maximum length of a Directory Entry Name is 16 characters. If a Directory Entry Name is supplied, the remainder of the optional parameters can be supplied by either: o A Directory Entry Name that has parameters defined and saved by connection manager configuration o Using the Connection Manager Answer Utility Presentation Manager window o Supplying the parameters at connection manager start-up time ΓòÉΓòÉΓòÉ <hidden> /PROTOCOL ΓòÉΓòÉΓòÉ A protocol that is used for the link. Use LAN for NETBIOS or IEEE 802.2 protocols. Valid values are LAN and SDLC. ΓòÉΓòÉΓòÉ <hidden> /ADAPTER: n ΓòÉΓòÉΓòÉ The adapter numbers that are used for the link. You must supply at least one adapter number. Maximum number of adapter numbers are: 2 for SDLC and 12 for LAN. Valid numbers are 0 through 11. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Parameters supplied at connection manager start-up override any preconfigured parameters. If connection manager is started with a valid Directory Entry Name and all of its associated parameters are defined, connection manager initiates the request without requiring any further action by the user. If you do not specify a protocol type and adapter number, the Connection Manager Answer Utility Presentation Manager window appears. You can specify more than one adapter number. If the first number is busy, the dialing utility tries the next number. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CMANSWER usage: o To start the dialing utility and supply all parameters interactively, type the following and press Enter: CMANSWER o To start the dialing utility and use the directory entry name of "RemoteRequesters", type the following and press Enter: CMANSWER /CALLNAME:RemoteRequesters Note: If you have already configured the protocol and adapter parameters for this directory entry name, this link is established immediately. Otherwise, use the dialing utility to define the protocol and adapter for this link. o To start the dialer and use the directory entry name of "RemoteRequesters" with a LAN protocol for adapter 0, type the following and press Enter: CMANSWER /CALLNAME:RemoteRequesters /PROTOCOL:LAN /ADAPTER:0 Note: If you have already configured the protocol and adapter parameters for this directory entry name, the parameters supplied here override the configured parameters. ΓòÉΓòÉΓòÉ 3.3. CMCALL ΓòÉΓòÉΓòÉ CMCALL Purpose Enables you to establish an outgoing call over a switched network for the purpose of sending and receiving data. The protocols that are supported once the connection has been established are LAN and SDLC. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMCALLΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ/CΓöÇΓöÇ[ALLNAME]:callnameΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÿ Γö£ΓöÇ/PΓöÇΓöÇ[ROTOCOL]:ΓöÇΓöÇΓö¼ΓöÇLANΓöÇΓöÇΓö¼ΓöÇΓöñ Γöé ΓööΓöÇSDLCΓöÇΓöÿ Γöé Γö£ΓöÇ/AΓöÇΓöÇ[DAPTER]:nΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/NΓöÇΓöÇ[UMBER]:phone numberΓöÇΓöÿ All CMCALL parameters are optional. All parameters may be specified using the first letter of the keyword. The CMCALL window is displayed if no parameters are specified. ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMCALL.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMCALL.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /CALLNAME:callname ΓòÉΓòÉΓòÉ An existing outgoing Directory Entry Name or permanent connection name which has been created during connection manager configuration. The maximum length of a Directory Entry Name is 16 characters. If a Directory Entry Name is supplied, the remainder of the optional parameters can be supplied by either: o A Directory Entry Name that has parameters defined and saved by connection manager configuration o Using the Connection Manager Call Utility Presentation Manager window o Supplying the parameters at connection manager start-up time ΓòÉΓòÉΓòÉ <hidden> /PROTOCOL ΓòÉΓòÉΓòÉ A protocol that is used for the link. Use LAN for NETBIOS or IEEE 802.2 protocols. Valid values are LAN and SDLC. ΓòÉΓòÉΓòÉ <hidden> /ADAPTER:n ΓòÉΓòÉΓòÉ The adapter numbers that are used for the link. You must supply at least one adapter number. Maximum number of adapter numbers are: 2 for SDLC and 12 for LAN. Valid numbers are 0 through 11. ΓòÉΓòÉΓòÉ <hidden> /NUMBER:phone number ΓòÉΓòÉΓòÉ A phone number in IA5 characters, according to the formats specified in the appropriate number/dialing plan in the connection manager configuration. If you specify this parameter, this phone number is used to establish the call instead of the first phone number specified in the Outgoing Directory Entry. The length of the phone number must be less than or equal to 40 characters. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ When making an outgoing call using CMCALL, you must specify the logical adapter number used by the application. Parameters supplied at connection manager start-up override any preconfigured parameters. If connection manager is started with a valid Directory Entry Name and all of its associated parameters are defined, connection manager initiates the request without requiring any further action by the user. If you do not specify a protocol type and adapter number, the Connection Manager Call Utility Presentation Manager window appears. You can specify more than one adapter number. If the first number is busy, the dialing utility tries the next number. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CMCALL usage: o To start the dialing utility and supply all parameters interactively, type the following and press Enter: CMCALL o To start the dialing utility and use the directory entry name of "DowJonesBBS", type the following and press Enter: CMCALL /CALLNAME:DowJonesBBS Note: If you have already configured the protocol and adapter parameters for this directory entry name, this link is established immediately. Otherwise, use the dialing utility to define the protocol and adapter for this link. o To start the dialing utility and use the directory entry name of "DowJonesBBS" with a LAN protocol for adapter 0 and dial the phone number 555-2222 instead of the phone number defined in the DowJonesBBS directory, type the following and press Enter: CMCALL /CALLNAME:DowJonesBBS /PROTOCOL:LAN /ADAPTER:0 /NUMBER:555-2222 Note: If you have already configured the protocol and adapter parameters for this directory entry name, the parameters supplied here override the configured parameters. ΓòÉΓòÉΓòÉ 3.4. CMGWSESS ΓòÉΓòÉΓòÉ CMGWSESS Purpose Displays session information about your workstation through a gateway. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMGWSESSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMGWSESS.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMGWSESS.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ The CMGWSESS command invokes CMGWSESS.EXE to display the sessions that are used on the gateway. The CMGWSESS command must work with the remote display server program (RDSPSRVR.EXE) to allow remote users to obtain significant information about a workstation. The "Communications Manager/2 API Support Diskette" contains the source code for this program . CMGWSESS.C is contained in the zip file-SNA.ZIP which can be unzipped using PKUNZIP2. Note: The "Communications Manager/2 API Support Diskette" is mentioned in this document. Please note that a CD-ROM that contains the complete Communications Manager product, including all information, is also available. Making RDSPSRVR.EXE operational: Since this program does not have security capability, you must take one of the following steps to make RDSPSRVR.EXE operational before it can be called by a remote program: o Copy RDSPSRVR.EXE to the directory specified by the DIRECTORY_FOR_INBOUND_ATTACHES statement in your .NDF file. o Add a DEFINE_TP statement for RDSPSRVR to your .NDF file. The following is an example: DEFINE_TP TP_NAME(RDSPSRVR) FILESPEC(C:\CMLIB\RDSPSRVR.EXE) CONV_SECURITY_RQD(NO) CONVERSATION_TYPE(MAPPED) PROGRAM_TYPE(BACKGROUND) RECEIVE_ALLOCATE_TIMEOUT(100) SYNC_LEVEL(EITHER) TP_OPERATION(NONQUEUED_AM_STARTED) DESCRIPTION(Server TP supporting remote display); After adding the DEFINE_TP statement to your .NDF file, activate RDSPSRVR by using the /E option of the CMVERIFY command. From the OS/2 command line, enter CMVERIFY fn /E, where fn is the filename of your .NDF file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of CMGWSESS usage: o To display the sessions between the gateway and the host related to your workstation, type the following and press Enter: CMGWSESS ΓòÉΓòÉΓòÉ 3.5. CMIMAGE ΓòÉΓòÉΓòÉ CMIMAGE Purpose Allows the network administrator to copy the Communications Manager diskette images onto a hard drive in a certain subdirectory. This subdirectory may then be used as the source location for the CMSETUP installation program. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMIMAGEΓöÇΓöÇ[/uΓöÇΓöÇ]ΓöÇΓöÇsource_drive:ΓöÇΓöÇtarget_drive:ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇ\path_nameΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMIMAGE.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMIMAGE.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /U ΓòÉΓòÉΓòÉ The /U option is used to create a code server for Workgroup Client Support. The /U option will unbundle the files and place them in a CMLIB subdirectory within the target path. If a target path is not given, CMIMAGE is the default target path. If the target directory already exists, a warning is issued and a confirmation is needed to continue. ΓòÉΓòÉΓòÉ <hidden> source_drive: ΓòÉΓòÉΓòÉ Drive where the files that are to be copied reside. ΓòÉΓòÉΓòÉ <hidden> target_drive: ΓòÉΓòÉΓòÉ Drive where the copied files will reside. ΓòÉΓòÉΓòÉ <hidden> /path_name ΓòÉΓòÉΓòÉ Directory where the copied files will reside. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ o CMIMAGE is located on Communications Manager diskette 1 in unpacked format. o The default path_name is \CMIMAGE. o To remove the files created by CMIMAGE, type DEL *.* in the directory that the files were copied to. If the /U option was specified, remove any subdirectories that were created. o For more information on CMIMAGE, refer to IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CMIMAGE usage: o To copy files from diskette drive A: to drive X: and place the files in the \IBMAPPS\CM10 directory, type the following and press Enter: CMIMAGE A: X:\IBMAPPS\CM10 o To copy files from diskette drive B: to drive V: and place the files in the default directory (\CMIMAGE), type the following and press Enter: CMIMAGE B: V: ΓòÉΓòÉΓòÉ 3.6. CMQUERY ΓòÉΓòÉΓòÉ CMQUERY Purpose Allows you to query information about Communications Manager. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMQUERYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMQUERY.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMQUERY.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of CMQUERY usage: o To get information including the status of Communications Manager, the default configuration, and the active configuration, type the following and press Enter: CMQUERY ΓòÉΓòÉΓòÉ 3.7. CMRECORD ΓòÉΓòÉΓòÉ CMRECORD Purpose The CMRECORD utility generates a Communications Manager response file from the default configuration and the installation parameters of the machine on which it is run, or from any existing Communications Manager configuration. CMRECORD ignores keylock, allowing you to create a response file from a keylocked configuration. The response file generated by CMRECORD is not complete to use with the CMSETUP /R command. You must edit the response file to add the appropriate update type (CMUpdateType) or additional control keyword entries. Note: The OS/2 command line limit of 255 characters applies to the CMRECORD command. Syntax >>ΓöÇΓöÇCMRECORDΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇcfg_nameΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/DΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ/O output.filΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γö£ΓöÇ/M model.filΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇ/K ΓöÇΓöÇΓöÇlistΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ ΓööΓöÇINSTALLΓöÇΓöÿ ΓööΓöÇCONFIGΓöÇΓöÿ Note: You must use a colon or a space to separate keywords from their parameters. For example, you might enter the following: CMRECORD MYFILE.CFG /O CONFIG1.RSP /M MYMODEL.FIL where MYFILE.CFG is the configuration you want to record, /O CONFIG1.RSP is the name of the output file, and /M MYMODEL.FIL is the name of the model response file. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Causes help text to be sent to STDOUT (usually the screen). If ? appears on the command line, it must be the first command line parameter. Help will also be displayed when an unrecognized keyword is encountered or when no parameters are specified. ΓòÉΓòÉΓòÉ <hidden> cfg_name ΓòÉΓòÉΓòÉ Specifies the Communications Manager configuration to record. An extension of .CFG is assumed. A file with the name of the configuration and the extension .CFG must exist on the path specified, and it must be a valid Communications Manager configuration file. The .CF2, .NDF, and .SEC files that may be part of the configuration are assumed to be in the same directory. ΓòÉΓòÉΓòÉ <hidden> /D ΓòÉΓòÉΓòÉ Records the workstation's default configuration, as specified in \CMLIB\CM.INI. If you specify this option, do not specify cfg_name. ΓòÉΓòÉΓòÉ <hidden> /O output.fil ΓòÉΓòÉΓòÉ Optionally specifies a file for the output. The default is a file with the configuration name and a .RSP extension. If the file already exists, it will be overwritten upon successful completion. The CMRECORD utility writes the keywords to the file in the following order: install keywords, followed by .CFG file configuration keywords, followed by .CF2 file configuration keywords. Note that passwords will not be recorded. For the X.25 route records, the ORDER keyword is not recorded. Lines can be output longer than 255, since the input line length max is 384 characters. If the output file has lines longer than 255, some editors will split the line into multiple lines. These lines will have to be corrected before the response file can be used to update a workstation. ΓòÉΓòÉΓòÉ <hidden> Mutually ΓòÉΓòÉΓòÉ exclusive parameters that limit the amount of information returned in the response file. /M model.fil Specifies the model response file, model.fil. The path to the model response file can be specified, but is optional. This model file has the same format and syntax as a normal response file, but values (the data right of the `=' sign) may be present or absent. The recording program will read the model file and fill in the current setting for each keyword, writing the result to output.fil. If a keyword cannot be recorded because it was not specified in the configuration, a comment will be placed in the output file. The order of the output in the model response file might be different from the order of input. If the /M flag is specified, the /K flag is ignored. There are several basic rules for model response files: o If the model file only specifies a record keyword, all instances of that record and all field keywords for the record are included in the response file. In this example, x25_route= ( ) the resulting response file includes all instances of X.25 route records and all field keywords within the record. o If the model file specifies a record keyword and a name keyword that identifies a record, all fields within the named record are included in the response file. In the following example, x25_route= ( name = xyz ) the resulting response file includes all field keywords and values within the xyz X.25 route record. o If the model file specifies a record keyword, a name keyword without a value and one or more field keywords, the specified fields are returned for all records. In the following example, x25_route= ( name = link_station_role = ) the resulting response file includes all the link_station_role fields for all instances of the X.25 route record. o If the model file specifies a record keyword, a name keyword with a value, and one or more field keywords, the specified fields are returned for named records. In this example, x25_route= ( name = xyz link_name = link_station_role = ) the resulting response file includes the link_name and link_station_role fields for the xyz X.25 route record. o Comments will not be copied from the model response file to the output response file. /K list Specifies that only the keywords in list are to be included in the response file. Each keyword entry must be separated by a space. The keywords in the list can be one of the following: list Specifies zero or more profile keywords that you want included in the response file. For example, a specification of /K WORKSTATION LAN_DLC generates only two outputs, showing the configuration data for the workstation and for the LAN DLC. The keywords may not be keywords that are list members; for example, you could specify the keyword SDLC_DLC, but not an SDLC_DLC's field keyword such as LINE_TYPE. ΓòÉΓòÉΓòÉ <hidden> INSTALL ΓòÉΓòÉΓòÉ Records all installation keywords in the response file. Individual installation keywords are not supported. For example, you cannot use /K ConfigWsSerial2, but you can use the INSTALL keyword. ΓòÉΓòÉΓòÉ <hidden> CONFIG ΓòÉΓòÉΓòÉ Records all the configuration keywords in the response file. The /K flag is ignored if the /M flag is specified. If neither the /M flag nor the /K flag is given, all keywords supported by response file installation are extracted from the configuration, except for the passwords, which are not recorded. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ CMRECORD ignores the keylock. A keylocked configuration file can be processed. CMRECORD can be used for problem determination. You can review the response file and the .NDF file (if applicable) to see a complete ASCII representation of your configuration. The output response file cannot be used to re-create or modify a configuration unless you first add some keywords to the response file. You must add CMUPDATETYPE = value to the response file before using it. You can optionally name the configuration that is created by adding the CMUSERCFG = value keyword. Refer to IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide for additional information. CMRECORD can partially record configuration files that have not been verified or have failed verification. Any records stored in the .CFG file will be recorded, but records from the .NDF file will not be recorded. These records may be viewed directly (in the .NDF format) in the .NDF file. There are several special cases for recording with model response files: o If the model file specifies only a record keyword, all instances of that record and all field keywords for the record are included in the response file. o If the model file specifies a record keyword and a name keyword that identifies a record, all fields within the named record are included in the response file. o If the model file specifies a record keyword, a name keyword without a value, and one or more field keywords, the specified fields are returned for all records. o If the model file specifies a record keyword, a name keyword with a value, and one or more field keywords, the specified fields are returned for named records. o If the keywords COPY or DELETE are encountered in the model file, they are copied to the output file. Using the DELETE keyword in a response file while using the CMSETUP command will cause the entry to be deleted from the configuration file. o For configuration keywords that support the .* syntax, the keyword can be specified in the model file with the .* and all occurrences of that field will be output. o Comments will not be copied from the model response file to the output response file. o The order of the keywords in the output response file may be different than the order of the keywords in the model response file. The CMRECORD utility writes errors to STDOUT. To write errors to a disk file, type the following and press Enter: CMRECORD [command line parms] >error.fil where error.fil is the name of the file where the errors are to be written. Refer to IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide for additional information on remote installation, response files, and CMRECORD. To build a response file using the CMRECORD utility, follow these steps: 1. Start from an OS/2 command prompt. 2. Type CMRECORD cfg_name, where cfg_name is the name of the configuration that you want to record. The CMRECORD utility creates a response file. Any messages or warnings concerning the response file are placed in the file as comments. Edit the response file and add the CMUpdateType keyword to indicate what you want the response file to do. Also add any other keywords like CMModelCFG, CMUserCFG, CMStopCommunications, and add or change any other keywords you want the response file to process. ΓòÉΓòÉΓòÉ <hidden> Example ΓòÉΓòÉΓòÉ The following are examples of CMRECORD usage: o To get help for CMRECORD, type the following and press Enter: CMRECORD ? o To record all keywords for the default configuration file to the default output file, type the following and press Enter: CMRECORD /D o To record all keywords for the default configuration file to the output response file temp.out, type the following and press Enter: CMRECORD /D /O temp.out o To record all keywords for the configuration myconfig. and use the output response file myconfig.rsp, type the following and press Enter: CMRECORD myconfig o To record all logical link records in the configuration myconfig, type the following and press Enter: CMRECORD myconfig /K LOGICAL_LINK o To record the installation keywords and workstation record for the configuration myconfig, type the following and press Enter: CMRECORD myconfig /K INSTALL WORKSTATION o To record all the keywords specified in the file model.rsp for the default configuration, type the following and press Enter: CMRECORD /D /M model.rsp ΓòÉΓòÉΓòÉ 3.8. CMTRACE ΓòÉΓòÉΓòÉ CMTRACE Purpose Provides command line control over the Communications Manager trace functions. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMTRACEΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇSTARTΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Γö£ΓöÇ/API xΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/DLC xΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/EVENT nΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/RESETΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/STORAGE nΓöÇΓöñ ΓööΓöÇ/TRUNC nΓöÇΓöÇΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇSTOPΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ ΓööΓöÇCOPY filenameΓöÇΓöÿ Γö£ΓöÇ/API xΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/DLC xΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/EVENT nΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMTRACE.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMTRACE.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Displays an online summary of CMTRACE. Note: The ? is the default value for CMTRACE. If you type CMTRACE and do not specify a parameter, the online CMTRACE summary is displayed. You can use | MORE or > filename to easily view this information. ΓòÉΓòÉΓòÉ <hidden> START ΓòÉΓòÉΓòÉ Starts one or more trace categories using the following options: /API, /DLC, /EVENT, /RESET, /STORAGE, and /TRUNC. If no trace category is specified, the START parameter enables any categories previously specified. ΓòÉΓòÉΓòÉ <hidden> STOP ΓòÉΓòÉΓòÉ Stops one or more trace categories using the following options: /API, /DLC, and /EVENT. If no trace category is specified, the STOP parameter stops the tracing of all categories. ΓòÉΓòÉΓòÉ <hidden> COPY ΓòÉΓòÉΓòÉ Copies a trace to a file. You must specify a file name with this parameter. ΓòÉΓòÉΓòÉ <hidden> /API x ΓòÉΓòÉΓòÉ Used to specify one or more of the following API traces: ACDI, APPC, EHLLAPI, LUARUI, LUASLI, ROPS, SERVICES, SRPI, SUBSYSM, and X25API. ΓòÉΓòÉΓòÉ <hidden> /API x ΓòÉΓòÉΓòÉ Used to specify one or more of the following API traces: ACDI, APPC, EHLLAPI, LUARUI, LUASLI, ROPS, SERVICES, SRPI, SUBSYSM, and X25API. ΓòÉΓòÉΓòÉ <hidden> /DLC x ΓòÉΓòÉΓòÉ Used to specify one or more of the following DLC traces: DFT, ETHERAND, IBMPCNET, IBMTRNET, ROPS, IDLC, SDLC, TWINAXIAL, X25DLC, and X25FRAME. ΓòÉΓòÉΓòÉ <hidden> /DLC x ΓòÉΓòÉΓòÉ Used to specify one or more of the following DLC traces: DFT, ETHERAND, IBMPCNET, IBMTRNET, ROPS, SDLC, TWINAXIAL, X25DLC, and X25FRAME. ΓòÉΓòÉΓòÉ <hidden> /EVENT n ΓòÉΓòÉΓòÉ Selects one or more system events to trace. This option is followed by one or more numbers between 1 and 32. Note: Refer to Problem Determination Guide for additional information on system events. ΓòÉΓòÉΓòÉ <hidden> /EVENT n ΓòÉΓòÉΓòÉ Selects one or more system events to trace. This option is followed by one or more numbers between 1 and 31. Note: Refer to Problem Determination Guide for additional information on system events. ΓòÉΓòÉΓòÉ <hidden> /RESET ΓòÉΓòÉΓòÉ Resets the trace buffer. Previous trace records are lost. ΓòÉΓòÉΓòÉ <hidden> /STDOUT ΓòÉΓòÉΓòÉ Writes the trace data to standard output. ΓòÉΓòÉΓòÉ <hidden> /STORAGE n ΓòÉΓòÉΓòÉ Sets the number of 64KB trace buffer segments. ΓòÉΓòÉΓòÉ <hidden> /trunc n ΓòÉΓòÉΓòÉ Sets the line length number at which trace records are truncated. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ CMTRACE provides command line control over the Communications Manager trace functions. With CMTRACE, you can start and stop tracing of particular trace categories and copy a trace to a file. If you are familiar with the Communications Manager trace windows, CMTRACE provides an alternative means for running a trace. In addition, the CMTRACE command can be used in a batch file. CMTRACE is installed by default as an additional function. If you do not want CMTRACE to be installed, deselect Install Additional Functions during Communications Manager installation. You can install or remove CMTRACE at any time by selecting Options from the Communications Manager Setup window menu bar and selecting your choice of operations (CMTRACE is associated with Problem Determination Aids). You can use CMTRACE before Communications Manager is running; therefore, the "autostart" function of CMTRACE is no longer needed. Any use of the autostart parameter invokes CMTRACE START. You can use CMTRACE to: o Monitor the events of a problem without swapping to and from the Communications Manager Trace Services windows. o Selectively stop a few active traces. o Selectively start additional trace categories without stopping active traces. o Run the same trace several times. You can create several one- or two-line command files (.CMD) that invoke CMTRACE with various trace parameters. Options can be entered in uppercase or lowercase letters. All options are separated by a single space. For more information on CMTRACE and for information on interpreting traces, refer to Problem Determination Guide. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of CMTRACE usage: o To view the syntax for CMTRACE, type the following and press Enter: CMTRACE ? | MORE o To start a trace on ACDI and APPC, type the following and press Enter: CMTRACE START /API ACDI APPC o To stop all currently running traces, type the following and press Enter: CMTRACE STOP o To copy the results of a trace to a file named TRACE1.TRC, type the following and press Enter: CMTRACE COPY TRACE1.TRC ΓòÉΓòÉΓòÉ 3.9. DISPLAY ΓòÉΓòÉΓòÉ DISPLAY Purpose Displays status and configuration information for an active SNA configuration. Output is sent to the standard output destination, which is normally the display screen. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇDISPLAYΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇpartner LU nameΓöÇΓöÿ ΓööΓöÇoptionsΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the DISPLAY.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the DISPLAY.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Partner LU name ΓòÉΓòÉΓòÉ Can be a partner LU alias or a fully qualified partner LU name. If you do not specify a partner LU name, the local workstation's sessions are displayed. ΓòÉΓòÉΓòÉ <hidden> options ΓòÉΓòÉΓòÉ The following parts of the command are options: Options are not case sensitive. If you specify more than one option, the options must be separated by blanks. If you do not specify any options, all of the workstation's sessions are displayed. ? Displays a help screen -ad Displays adapter information -am Displays attach manager information -cn Displays connection network information -co Displays APPN class of service information -d Displays APPN directory information -g Displays SNA gateway information -ic Displays ISDN incoming call directory entries -is Displays intermediate session routing information -ld Displays link definitions -li Displays active links information -lud Displays logical unit definitions -lu0 Displays logical unit 0-3 information -lu6 Displays logical unit 6.2 information -md Displays mode definitions -ms Displays management services information -n Displays APPN node information -pl Displays partner logical unit definitions -pu Displays ISDN physical units -se Displays session information -sn Displays SNA global information -sy Displays system defaults -to Displays APPN topology information -tp Displays active transaction programs information -x Displays X.25 physical links information -tpd Displays transaction program definitions ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ The DISPLAY command invokes DISPLAY.EXE to display the SNA information about an active configuration. The DISPLAY command can work with the remote display server program (RDSPSRVR.EXE) to allow remote users to obtain significant information about a workstation including LU definitions, TP definitions, and partner LU definitions. If RDSPSRVR.EXE is installed and operational at your local workstation, users at remote workstations can acquire active SNA information about your workstation. If RDSPSRVR.EXE is installed and operational at a remote workstation, you can specify a partner LU name to display the active SNA configuration of that workstation. You can use these two programs to develop an automated network management capability to acquire information about the configuration and status of Communications Manager SNA workstations. The "Communications Manager/2 API Support Diskette" contains the source code for both programs. DISPLAY.C and RDSPSRVR.C are contained in the zip file-SNA.ZIP which can be unzipped using PKUNZIP2. Note: The "Communications Manager/2 API Support Diskette" is mentioned in this document. Please note that a CD-ROM that contains the complete Communications Manager product, including all information, is also available. Making RDSPSRVR.EXE operational: Since this program does not have security capability, you must take one of the following steps to make RDSPSRVR.EXE operational before it can be called by a remote program: o Copy RDSPSRVR.EXE to the directory specified by the DIRECTORY_FOR_INBOUND_ATTACHES statement in your .NDF file. o Add a DEFINE_TP statement for RDSPSRVR to your .NDF file. The following is an example: DEFINE_TP TP_NAME(RDSPSRVR) FILESPEC(C:\CMLIB\RDSPSRVR.EXE) CONV_SECURITY_RQD(NO) CONVERSATION_TYPE(MAPPED) PROGRAM_TYPE(BACKGROUND) RECEIVE_ALLOCATE_TIMEOUT(100) SYNC_LEVEL(EITHER) TP_OPERATION(NONQUEUED_AM_STARTED) DESCRIPTION(Server TP supporting remote display); After adding the DEFINE_TP statement to your .NDF file, activate RDSPSRVR by using the /E option of the CMVERIFY command. From the OS/2 command line, enter CMVERIFY fn /E, where fn is the filename of your .NDF file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of DISPLAY usage: o To display the system defaults and the partner LU definitions for the local workstation, type the following and press Enter: DISPLAY -sy -p o To display all the information available (the default) for a remote workstation containing a partner LU with a local alias of Ray, type the following and press Enter: DISPLAY ray ΓòÉΓòÉΓòÉ 3.10. ESLANX ΓòÉΓòÉΓòÉ ESLANX Purpose Allows you to modify or create LAN Transport information when using the Extended Services level of LAN Transport. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇESLANXΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇfilenameΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ESLANX.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ESLANX.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ The name of the file to be modified. If you do not specify a file name, PROTOCOL.INI is used. Do not include the file extension; it is assumed to be .INI. filename is required to be in the \IBMCOM subdirectory. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ ESLANX should only be used when you have upgraded from Extended Services but have not upgraded your LAN Transport to LAPS. Do not use ESLANX if you have upgraded to LAPS. If you use ESLANX to update PROTOCOL.INI, your CONFIG.SYS file is also updated to reflect any changes. The CONFIG.SYS file is only read during system startup; therefore, any changes that are made to the CONFIG.SYS file will not take affect until you restart your system. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of ESLANX usage: o To modify or create a PROTOCOL.INI file in the \IBMCOM subdirectory, type the following and press Enter: ESLANX ΓòÉΓòÉΓòÉ 3.11. FMTTRACE ΓòÉΓòÉΓòÉ FMTTRACE Purpose Formats an SNA trace file into a form that is easier to use. Note: The options for FMTTRACE are case sensitive; therefore, the normal conventions for variable information does not apply. For FMTTRACE, xxxxxxxx is used to represent variable information. The FMTTRACE syntax is as follows: Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilenameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇhelpΓöÇΓöÿ Γö£ΓöÇ+dΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ+sΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ+aΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ+fΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ-dΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ-sΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ-aΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ-fΓöÇΓöÇΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> Γö£ΓöÇ+rΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ+txxxxxxxxΓöÇΓöñ Γö£ΓöÇ+cxxxxxxxxΓöÇΓöñ Γö£ΓöÇ+lxxxxxxxxΓöÇΓöñ Γö£ΓöÇ+hΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ-rΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ-txxxxxxxxΓöÇΓöÿ ΓööΓöÇ-cxxxxxxxxΓöÇΓöÿ ΓööΓöÇ-lxxxxxxxxΓöÇΓöÿ ΓööΓöÇ-hΓöÇΓöÇΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γö£ΓöÇ+nΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ-nΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Specifies the name of the trace file to be formatted. The file name extension .TRC is the default. ΓòÉΓòÉΓòÉ <hidden> ? ΓòÉΓòÉΓòÉ Displays an online summary of the FMTTRACE command. ΓòÉΓòÉΓòÉ <hidden> help ΓòÉΓòÉΓòÉ Displays an online summary of the FMTTRACE command. ΓòÉΓòÉΓòÉ <hidden> +d ΓòÉΓòÉΓòÉ Produces a detail output file (.DET). ΓòÉΓòÉΓòÉ <hidden> -d ΓòÉΓòÉΓòÉ Does not produce a detail output file. This is the default. ΓòÉΓòÉΓòÉ <hidden> +s ΓòÉΓòÉΓòÉ Produces a summary output file (.SUM). This is the default. ΓòÉΓòÉΓòÉ <hidden> -s ΓòÉΓòÉΓòÉ Does not produce a summary output file. ΓòÉΓòÉΓòÉ <hidden> +a ΓòÉΓòÉΓòÉ Formats the API trace. This is the default. This option may also specify one or more of the following protocols for the x parameter: ACDI, APPC, CPIC, EHLLAPI, LUARUI, LUASLI, SERVICES, and SRPI. If x is not specified, all protocols are the default. ΓòÉΓòÉΓòÉ <hidden> -a ΓòÉΓòÉΓòÉ Does not format the API trace. ΓòÉΓòÉΓòÉ <hidden> +f ΓòÉΓòÉΓòÉ Formats the line-flow trace. This is the default. This option may also specify one or more of the following interfaces for the x parameter: ETHERAND, IBMPCNET, IBMTRNET, IDLC, MPTNBTCP, SDLC, and X25DLC. If x is not specified, all interfaces are the default. ΓòÉΓòÉΓòÉ <hidden> -f ΓòÉΓòÉΓòÉ Does not format the line flow trace. ΓòÉΓòÉΓòÉ <hidden> +r ΓòÉΓòÉΓòÉ Formats TEST_RTS. This is the default. ΓòÉΓòÉΓòÉ <hidden> -r ΓòÉΓòÉΓòÉ Does not format TEST_RTS. ΓòÉΓòÉΓòÉ <hidden> +txxxxxxxx ΓòÉΓòÉΓòÉ Formats the APPC API trace records with a TP ID matching X'xxxxxxxx'. ΓòÉΓòÉΓòÉ <hidden> -txxxxxxxx ΓòÉΓòÉΓòÉ Does not format the APPC API trace records with a TP ID matching X'xxxxxxxx'. ΓòÉΓòÉΓòÉ <hidden> +cxxxxxxxx ΓòÉΓòÉΓòÉ Formats the APPC API trace records with a conversation ID matching X'xxxxxxxx'. ΓòÉΓòÉΓòÉ <hidden> -cxxxxxxxx ΓòÉΓòÉΓòÉ Does not format the APPC API trace records with a conversation ID matching X'xxxxxxxx'. ΓòÉΓòÉΓòÉ <hidden> +lxxxxx ΓòÉΓòÉΓòÉ Formats the DLC data trace records with an LFSID matching X'xxxxx' (LFSID is a session identifier). ΓòÉΓòÉΓòÉ <hidden> -lxxxxx ΓòÉΓòÉΓòÉ Does not format the DLC data trace records with an LFSID matching X'xxxxx' (LFSID is a session identifier). ΓòÉΓòÉΓòÉ <hidden> +h ΓòÉΓòÉΓòÉ Uses uppercase alphabetics in hexadecimal output, such as X'BC2F'. ΓòÉΓòÉΓòÉ <hidden> -h ΓòÉΓòÉΓòÉ Uses lowercase alphabetics in hexadecimal output such as X'bc2f'. This is the default. ΓòÉΓòÉΓòÉ <hidden> +n ΓòÉΓòÉΓòÉ Interleaves raw trace with formatted trace ΓòÉΓòÉΓòÉ <hidden> -n ΓòÉΓòÉΓòÉ Does not interleave raw trace with formatted trace ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ FMTTRACE is installed by default as an additional function. If you do not want FMTTRACE to be installed, deselect Install Additional Functions during Communications Manager installation. You can install or remove FMTTRACE at any time by selecting Options from the Communications Manager Setup window menu bar and selecting your choice of operations (FMTTRACE is associated with Problem Determination Aids). FMTTRACE allows you to format a Communications Manager trace file into a form that is easier to interpret. It formats trace records for the APPC API, APPC send events, and DLC data. You can produce two types of formatted output: a summary file (in sequence diagram form with one line per trace event) and a detail file (with one line per formatted field). The default flag values are -d, +s, +a, +p, +f, +r, and -h. For +t, -t, +c, and -c, the hexadecimal string which follows must be eight characters and must immediately follow the option flag (there are no spaces between the flag and the hexadecimal string). For +l and -l, the hexadecimal string which follows must be five characters and must immediately follow the option flag (there are no spaces between the flag and the hexadecimal string). For more information on FMTTRACE including examples of formatted traces, refer to Problem Determination Guide. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following is an example of FMTTRACE usage: o To format the TRACE1 trace file, produce a detailed output file and a summary file, type the following and press Enter: FMTTRACE +D TRACE1 Because +S is the default, a summary file is produced without using an option. ΓòÉΓòÉΓòÉ 3.12. PMDSPLAY ΓòÉΓòÉΓòÉ PMDSPLAY Purpose Displays status and configuration information for an active SNA configuration of Communications Manager. PMDSPLAY uses Presentation Manager to display the information. This performs the same function as a display using Presentation Manager Windows. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇPMDSPLAYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the PMDSPLAY.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the PMDSPLAY.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This command invokes PMDSPLAY.EXE (a Presentation Manager version of DISPLAY.EXE) to display the SNA information about an active configuration. See DISPLAY for additional information. PMDSPLAY.EXE is also invoked when "Display active SNA configuration" is selected from the Communications Manager Subsystem Management menu. Three operational modes can be selected from Options on the menu bar: 1. Display to the screen (the default). 2. Display to the screen and place the display results in a file. 3. Display the active SNA information of a remote workstation. When you select this mode, the active SNA configuration of a remote workstation can be displayed. You must provide a configured Partner LU name for the remote workstation, and the remote display server program RDSPSRVR.EXE must be installed and operational at the remote workstation. The PMDSPLAY command can work with the remote display server program (RDSPSRVR.EXE) to allow remote users to obtain significant information about a workstation including LU definitions, TP definitions, and partner LU definitions. o If RDSPSRVR.EXE is installed and operational at your local workstation, users at remote workstations can acquire active SNA information about your workstation. o If RDSPSRVR.EXE is installed and operational at a remote workstation, you can specify a partner LU name to display the active SNA configuration of that workstation. PMDSPLAY.EXE is installed in the \CMLIB directory. The "Communications Manager/2 API Support Diskette" contains the source code for both programs. PMDSPLAY.C and RDSPSRVR.C are contained in the zip file-SNA.ZIP which can be unzipped using PKUNZIP2. Note: The "Communications Manager/2 API Support Diskette" is mentioned in this document. Please note that a CD-ROM that contains the complete Communications Manager product, including all information, is also available. Making RDSPSRVR.EXE operational: Since this program does not have security capability, you must take one of the following steps to make RDSPSRVR.EXE operational before it can be called by a remote program: o Copy RDSPSRVR.EXE to the directory specified by the DIRECTORY_FOR_INBOUND_ATTACHES statement in your .NDF file. o Add a DEFINE_TP statement for RDSPSRVR to your .NDF file. The following is an example: DEFINE_TP TP_NAME(RDSPSRVR) FILESPEC(C:\CMLIB\RDSPSRVR.EXE) CONV_SECURITY_RQD(NO) CONVERSATION_TYPE(MAPPED) PROGRAM_TYPE(BACKGROUND) RECEIVE_ALLOCATE_TIMEOUT(100) SYNC_LEVEL(EITHER) TP_OPERATION(NONQUEUED_AM_STARTED) DESCRIPTION(Server TP supporting remote display); After adding the DEFINE_TP statement to your .NDF file, activate RDSPSRVR by using the /E option of the CMVERIFY command. From the OS/2 command line, enter CMVERIFY fn /E, where fn is the name of your Communications Manager configuration. ΓòÉΓòÉΓòÉ 3.13. REDIRECT ΓòÉΓòÉΓòÉ REDIRECT Purpose Redirects serial ports on an OS/2 workstation. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇREDIRECTΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓööΓöÇCOMx TOΓöÇΓöÇΓö¼ΓöÇCOMyΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé Γöé ΓööΓöÇserver_nameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé Γöé ΓööΓöÇON LANAnΓöÇΓöÿ Γöé Γö£ΓöÇSAVEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇRESTOREΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the REDIRECT.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the REDIRECT.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> COMx, COMy ΓòÉΓòÉΓòÉ COM1, COM2, or COM3 communication ports. ΓòÉΓòÉΓòÉ <hidden> COMx, COMy ΓòÉΓòÉΓòÉ COM1, COM2, or COM3 communication ports. ΓòÉΓòÉΓòÉ <hidden> server_name ΓòÉΓòÉΓòÉ The server NETBIOS name assigned to the asynchronous resource at the asynchronous machine. ΓòÉΓòÉΓòÉ <hidden> LANAn ΓòÉΓòÉΓòÉ Either LANA0 for LAN adapter 0 or LANA1 for LAN adapter 1. ΓòÉΓòÉΓòÉ <hidden> RESTORE ΓòÉΓòÉΓòÉ Allows you to reinitialize ACDI to the permanent redirection configuration after you have temporarily changed to a different redirection configuration. ΓòÉΓòÉΓòÉ <hidden> SAVE ΓòÉΓòÉΓòÉ Allows you to save the current redirection configuration as the permanent redirection configuration. Note: Since the current redirection configuration is lost when you stop ACDI, this parameter must be used before you stop ACDI. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Be aware that there are two different REDIRECT commands. o The REDIRECT command for ACDI Redirection is provided with IBM Communications Manager. for use on OS/2 workstations. o This command is not the same as the REDIRECT command provided with the LAN Asynchronous Connection Server Program for use on DOS workstations. Using ACDI Redirection requires: o Communications Manager o ACDI o LAN Adapter and Protocol Support (NETBIOS). You can configure ACDI Redirection to be temporary or permanent. ACDI is initialized to the permanent redirection configuration when Communications Manager is started. While ACDI is running, you can temporarily change the redirection for a port; however, you cannot redirect a serial port while it is in use. You can change the redirection configuration from the command line, or from an application written to the ACDI Redirection application programming interface (API). The ACDI feature of Communications Manager must be installed and configured prior to activating the ACDI subsystem. The OS/2 workstation does not need to have a physical serial port (an asynchronous communications adapter) to use ACDI Redirection. When a user redirects a serial port, ACDI creates a virtual serial port. For example, if a user issues the statement REDIRECT COM1 TO REMOTECOM, ACDI creates a virtual serial port named COM1 and associates COM1 with the server NETBIOS name REMOTECOM. The virtual COM1, which can be accessed only by ACDI, is separate and independent from any physical COM1. An application written to ACDI can use the virtual COM1 at the same time that another application or device, such as a mouse, is using the physical COM1. ACDI can create: o Two virtual serial ports (COM1 and COM2) on an OS/2 LAN workstation with an IBM AT-type bus o Three virtual serial ports (COM1, COM2, and COM3) on Once you configure ACDI Redirection and save the redirection configuration, you do not need to configure ACDI Redirection again unless you want to change the redirection configuration. When you start an OS/2 workstation and start ACDI Redirection, ACDI automatically uses the permanent ACDI Redirection configuration. Refer to rspfile. for more information on ACDI installation and configuration. Refer to User's Guide for more information on ACDI Redirection. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following are examples of REDIRECT usage: o To cancel redirection, redirect a serial port to itself by typing the following and pressing Enter: REDIRECT COMx TO COMx o To display the current configuration for each serial port, type REDIRECT with no parameters and press Enter: REDIRECT o To redirect a local serial port to the server, type the following and press Enter: REDIRECT COMx TO server_name In this statement, COMx is either COM1, COM2, or COM3, and server_name is the NETBIOS name of the resource at the asynchronous server machine. o To redirect a serial port to another serial port on the same OS/2 workstation, type the following and press Enter: REDIRECT COMx to COMy ΓòÉΓòÉΓòÉ 4. User Profile Management Commands ΓòÉΓòÉΓòÉ User Profile Management is a program packaged with Communications Manager that provides: o Authorization checking by means of a logon facility o Administration of user IDs and passwords. This chapter discusses the User Profile Management commands. Each command description includes the purpose of the command, a syntax diagram, a list of parameters, a discussion of options, remarks, and examples. In addition to using the Presentation Manager interface to perform User Profile Management functions, you can issue commands to perform certain functions from the OS/2 command line. Unless otherwise specified, directions in this book assume you are invoking commands from the OS/2 command line. Note: A hyphen (-) can be used in place of a slash (/) when specifying an option for each of the commands in this chapter. For a detailed discussion of User Profile Management, refer to User's Guide. To view the list of User Profile Management commands, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 4.1. LOGOFF ΓòÉΓòÉΓòÉ LOGOFF Purpose Logs off the local OS/2 program and all remote workstations. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇLOGOFFΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ Γö£ΓöÇ/LΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ/N=nodeΓöÇΓöñ Γö£ΓöÇ/DΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/SΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the LOGOFF.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the LOGOFF.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /L ΓòÉΓòÉΓòÉ Lists current logged-on sessions, allowing you to select a particular session from which to log off. ΓòÉΓòÉΓòÉ <hidden> /N = node ΓòÉΓòÉΓòÉ Logs off the specified node name. If node is not specified, all nodes in the session are logged off. ΓòÉΓòÉΓòÉ <hidden> /D ΓòÉΓòÉΓòÉ Logs you off the LAN server domain. ΓòÉΓòÉΓòÉ <hidden> /S ΓòÉΓòÉΓòÉ Logs you off the current session. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ No specific authorization is required to issue the LOGOFF command. If no options are specified, all user IDs that are logged on are logged off. If you are not logged on, issuing the LOGOFF command does not cause an error. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following examples show various options of the LOGOFF command: A list of currently logged-on sessions is displayed. logoff /l The entry for the node name node4 is logged off. logoff /n=node4 All node entries are logged off. logoff /n All logons are logged off. logoff ΓòÉΓòÉΓòÉ 4.2. LOGON ΓòÉΓòÉΓòÉ LOGON Purpose Identifies you to the local and remote workstations and allows access, if required, to Communications Manager. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇLOGONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< Γöé ΓööΓöÇuseridΓöÇΓöÿ ΓööΓöÇ/P=passwordΓöÇΓöÿ Γö£ΓöÇ/N=nodeΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇ/L=logonΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇ/D=domainΓöÇΓöÿ Γöé ΓööΓöÇ/O=optionΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the LOGON.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the LOGON.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> userid ΓòÉΓòÉΓòÉ The user ID of the person logging on. If the user ID is not specified, the Logon window is displayed for typing the user ID. ΓòÉΓòÉΓòÉ <hidden> /P=password ΓòÉΓòÉΓòÉ Allows you to specify a password. If a password is specified, an attempt is made to log on using that password. If the password option is not specified, an attempt is made to log on without a password. If a password is necessary, the Logon window is displayed for typing the password. The /P option is ignored if a user ID is not specified. Warning: If you use the /P option, the password is displayed on the screen. If you are using the Retrieve Commands option (by placing SET KEYS=ON in the CONFIG.SYS file or by issuing KEYS ON at the OS/2 command prompt), another person can retrieve the LOGON command and see your password, even if you have logged off. To prevent someone from retrieving your password, you must close the OS/2 session after logging off. ΓòÉΓòÉΓòÉ <hidden> /N=node ΓòÉΓòÉΓòÉ Specifies the node to be used the next time the system requires the node to be accessed. With the /N option, the user ID and password are not validated until the program attempts to connect to the node. If node is omitted, the Logon window for Remote Node Access is displayed for entering the node name. If only the /N option is specified, the Logon window for Remote Node access is displayed for entering the user ID, password, and node name. ΓòÉΓòÉΓòÉ <hidden> /L=logon ΓòÉΓòÉΓòÉ The /L option specifies a local logon. ΓòÉΓòÉΓòÉ <hidden> /D=domain ΓòÉΓòÉΓòÉ The /D option specifies the domain name on which to log on. If a domain name is entered, an attempt is made to log on to that domain. If the /D option is specified without a domain name, an attempt is made to log on to the default domain. If that logon is unsuccessful, the Logon window is displayed so that a domain name can be entered. If a user is already logged on to a domain, the /D option displays the domain logon window. Note: The /D option is ignored if LAN Requester (a separately sold product) could not be started or if domain switching is not allowed. If this option is ignored, a local logon is performed. If the domain specified cannot be found or is not available, the user is logged on as a stand-alone user. That is, the user ID and password are saved and used when the user attempts to access a remote server. ΓòÉΓòÉΓòÉ <hidden> /O=option ΓòÉΓòÉΓòÉ The /O option specifies the type of local logon. There are two valid options: o MULTI specifies multiple local logons so that you can later log on with multiple local user IDs, allowing multiple application programs to run concurrently under different user IDs. User Profile Management displays a logon window for each new application program initiated. Application programs that access multiple protected resources may not require additional logons. o SINGLE specifies single local logon. Only one local logged on user ID is allowed for each workstation. All application programs run under that user ID until a logoff or another local logon is issued. If you log on with a different user ID, the current user ID is automatically logged off. This command is ignored if there are currently multiple local logons. You cannot specify the userid, /P, or /N options when the /O option is specified. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ If the LOGON command does not include userid, the Logon window is displayed. A user ID and, if required, the password for that ID must be specified before logon processing continues. Options can be indicated by a forward slash (/) and can be specified in any order. Each option can be used once. Logons are active until you log off or initialize your workstation again. For example, even if you had to log on to use the 5250 Work Station Feature, exiting does not automatically log you off. If you plan to leave your workstation unattended, you should log off to prevent unauthorized use of your user ID. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following examples show the various options of the LOGON command. o The user jsmith logs on to the system. If a password is required for jsmith, the Logon window is displayed and prompts the user for a password. logon jsmith o The user cjones logs on to the node nodeb: logon cjones /n=nodeb o The user rmiller issues the logon command without specifying a node. The Logon window for Remote Node Access is displayed and prompts the user for a node name. logon rmiller /n o Multiple local logon is specified. This allows multiple local user IDs to be able to log on. logon /o=multi o Local logon is specified. The Logon window for Local Access is displayed. logon /l o Logon to domain aus003 is specified. The Logon window for Domain Access to domain AUS003 is displayed. logon /d=aus003 ΓòÉΓòÉΓòÉ 4.3. UPMACCTS ΓòÉΓòÉΓòÉ UPMACCTS Purpose Displays the User Profile Management User Profile primary menu. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇUPMACCTSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the UPMACCTS.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the UPMACCTS.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ No specific authorization is required to issue this command. If the user is not logged on, the Logon window is displayed. If logon is successful, the User Profile primary menu is displayed. If the user has administrator authority, the User Management primary menu and the Group Management primary menu can be accessed from the User Profile primary menu. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following example displays the User Profile primary menu: upmaccts ΓòÉΓòÉΓòÉ 4.4. UPMCSET ΓòÉΓòÉΓòÉ UPMCSET Purpose Specifies the character set used to define user IDs, group IDs, and passwords. Syntax >>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇUPMCSETΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ Γö£ΓöÇ/MΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ/EΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the UPMCSET.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the UPMCSET.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /M ΓòÉΓòÉΓòÉ Indicates that user IDs, group IDs, and passwords must be defined in the minimal character set. ΓòÉΓòÉΓòÉ <hidden> /E ΓòÉΓòÉΓòÉ Indicates that user IDs, group IDs, and passwords can be defined in the expanded character set. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ The default for UPMCSET is /M. The minimal character set includes the following: o A through Z o 0 through 9 o Number sign (#) o At sign (@) o Dollar sign ($) The following rules apply when you use the minimal character set: o User IDs and group IDs cannot begin with a number or end with the dollar sign ($) character. o User IDs and group IDs can be from 1 to 8 characters long. Passwords can be from 4 to 8 characters long. o User IDs and group IDs cannot begin with IBM or SYS. o User IDs and group IDs cannot have the following values: - USERS - GUESTS - ADMINS - PUBLIC - LOCAL If you choose to use the expanded character set, you can use the minimal character set plus other printable characters except for the following: . ' / \ [ ] ; : | < > + = , ? * Also, you cannot use characters whose values are less than hexadecimal 20. If you use the expanded character set, user IDs and group IDs can be from 1 to 10 characters long and passwords can be from 4 to 10 characters long. Note: 1. Communications Manager identifiers are restricted to the minimal character set. However, if you have chosen to use the expanded character set, Communications Manager identifiers can be from 1 to 10 characters long. 2. User Profile Management does not guarantee correct processing of identifiers using the expanded character set if the code page or country code of the system differs from that specified when the identifier was created. It is your responsibility to make sure that the expanded character set is used only when the code page and country code of the system will not be changed. 3. You should not create network names (user IDs, group IDs, aliases, and so on) that begin with a number or end with the dollar sign ($) character even when using the expanded character set. Unpredictable results may occur. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ The following example specifies the expanded character set: upmcset /E ΓòÉΓòÉΓòÉ 5. Obsolete Commands ΓòÉΓòÉΓòÉ This appendix identifies obsolete commands and suggests the corresponding IBM Communications Manager/2 Version 1.0 replacement. To view the list of obsolete commands, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 5.1. APPNC ΓòÉΓòÉΓòÉ You can access Communications Manager Configuration Services by using CMSETUP. ΓòÉΓòÉΓòÉ 5.2. APPNLINK ΓòÉΓòÉΓòÉ No IBM Communications Manager/2 Version 1.0 command is equivalent to this command. Use the following steps to perform the function previously performed by APPNLINK. 1. From the Communications Manager/2 window, select Subsystem Management. The Subsytem Management window appears. Note: You can activate the Subsystem Management window from the command line by typing ACSSBMGT and pressing Enter. 2. Make sure that the SNA subsytem is started. If the SNA subsytem is not started, select SNA subsystem and select Start from the Services option on the menu bar. 3. Select SNA subsystem and select Details... from the Services option on the menu bar. The SNA Subsytem window appears. 4. From the SNA Subsytem window, select Logical Links. The Logical Links window appears which displays the link names, link status, and other details. For more information on subsystem management, refer to IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide. ΓòÉΓòÉΓòÉ 5.3. APPNLOG ΓòÉΓòÉΓòÉ No IBM Communications Manager/2 Version 1.0 command is equivalent to this command. You can use FFST/2 to view the message log. Use one of the following methods to view the FFST/2 message log: o Select FFST/2 from the desktop and select Message Log Formatter. o Type MSGLOGF from the command line and press Enter. Refer to Problem Determination Guide for more information on FFST/2. ΓòÉΓòÉΓòÉ 5.4. APPNMIG ΓòÉΓòÉΓòÉ Use CMUPGRAD to upgrade Communications Manager configuration files from Extended Edition 1.30.1 and Extended Services formats to IBM Communications Manager/2 Version 1.0 format. ΓòÉΓòÉΓòÉ 5.5. APPNV ΓòÉΓòÉΓòÉ You can verify Communications Manager configurations by using CMVERIFY. ΓòÉΓòÉΓòÉ 5.6. COPYCFG ΓòÉΓòÉΓòÉ You can use the OS/2 COPY command to copy the configuration files. These files have extensions .CFG, .NDF, .SEC, and .CF2. For LAN and ISDN configurations, other files must also be copied; refer to Configuration Guide for details. ΓòÉΓòÉΓòÉ 5.7. CUSTBLD ΓòÉΓòÉΓòÉ No IBM Communications Manager/2 Version 1.0 command is equivalent to this command. You can use the following procedure to perform a new but similar IBM Communications Manager/2 Version 1.0 function: 1. Create a response file and optionally create a model configuration file. 2. Place both the response file and optional model configuration file on a diskette. 3. Use CMSETUP /R response_file. See CMSETUP for more information. ΓòÉΓòÉΓòÉ 5.8. EECFG ΓòÉΓòÉΓòÉ You can access Communications Manager Configuration Services by using CMSETUP. ΓòÉΓòÉΓòÉ 5.9. ESCFG ΓòÉΓòÉΓòÉ You can access Communications Manager Configuration Services by using CMSETUP. ΓòÉΓòÉΓòÉ 5.10. ESINST ΓòÉΓòÉΓòÉ You can access Communications Manager Installation Services and Configuration Services by using CMSETUP. ΓòÉΓòÉΓòÉ 5.11. REINST ΓòÉΓòÉΓòÉ You can access Communications Manager Installation Services and Configuration Services by using CMSETUP. ΓòÉΓòÉΓòÉ 5.12. VIEWBLOG ΓòÉΓòÉΓòÉ No IBM Communications Manager/2 Version 1.0 command is equivalent to this command. You can use an ASCII editor to view the \CMLIB\CM.LOG file or use the following procedure to view the audit trail: 1. Select Communications Manager/2 from the desktop. The Communications Manager/2 window appears. 2. Select Communications Manager Setup from the Communications Manager/2 window. The Communications Manager Setup window appears. 3. Select Options from the menu bar of the Communications Manager Setup window and select View audit trail.... The View Audit Trail window appears. ΓòÉΓòÉΓòÉ 5.13. VIEWLOG ΓòÉΓòÉΓòÉ There is no IBM Communications Manager/2 Version 1.0 command line equivalent for this command. You can use an ASCII editor to view the \CMLIB\CM.LOG file or use the following procedure to view the audit trail: 1. Select Communications Manager/2 from the desktop. The Communications Manager/2 window appears. 2. Select Communications Manager Setup from the Communications Manager/2 window. The Communications Manager Setup window appears. 3. Select Options from the menu bar of the Communications Manager Setup window and select View audit trail.... The View Audit Trail window appears. ΓòÉΓòÉΓòÉ 6. CONFIG.SYS Usage ΓòÉΓòÉΓòÉ This appendix describes the Communications Manager device drivers. Each description includes the purpose of the device driver, a syntax diagram, a list of parameters, a discussion of the options, remarks, and examples. A device driver is a file that contains code which enables the operating system to recognize a device and correctly process information received from or sent to that device. The operating system loads default device drivers; however, you can replace these or add other devices by adding DEVICE statements in your CONFIG.SYS file. The CONFIG.SYS file is read only during system startup; therefore, any changes you make to the CONFIG.SYS file will not take affect until you restart your system. DEVICE statements are processed in the order in which they occur in the CONFIG.SYS file. Some device drivers have prerequisite device drivers. Read the "Remarks" section for each device driver for important information regarding placement of the DEVICE statement. For more information on installation, refer to Workstation Installation and Configuration Guide and IBM Communications Manager/2 Version 1.0 Network Administration and Subsystem Management Guide. For more information on configuration, refer to Configuration Guide. For more information on device drivers, refer to OS/2 Command Reference. To view the list of device drivers, press Ctrl+C to return to the Contents. Next, select the plus sign (+) or press the + key. ΓòÉΓòÉΓòÉ 6.1. ACSLANDD.SYS ΓòÉΓòÉΓòÉ ACSLANDD.SYS Purpose Allows access to the 802.2 link level control (LLC) API for Communications Manager SNA support. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇACSLANDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ACSLANDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ACSLANDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This device driver statement is necessary to use any 802.2 supported LAN type. This device driver statement can be placed anywhere in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load this device driver. DEVICE=C:\CMLIB\ACSLANDD.SYS ΓòÉΓòÉΓòÉ 6.2. ASYNCDDA.SYS ΓòÉΓòÉΓòÉ ASYNCDDA.SYS Purpose Loads the Asynchronous Communications Device Interface (ACDI) on an IBM Personal Computer AT. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇASYNCDDA.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ASYNCDDA.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ASYNCDDA.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ ASYNCDDA.SYS allows OS/2 application programs to use serial COM ports through ACDI. If a device driver that supports any one of the serial ports (COM1, COM2, or COM3) is installed by a DEVICE statement that precedes a DEVICE=ASYNCDDA.SYS statement, the port is unavailable to ASYNCDDA.SYS. If the DEVICE=ASYNCDDA.SYS statement comes prior to a DEVICE statement supporting a mouse, the DEVICE=ASYNCDDA.SYS statement is overridden without any warning or message. For an IBM Personal Computer AT equipped with an INS-8250 or INS-8250B serial device, the DEVICE=ASYNCDDA.SYS statement must precede the DEVICE=COMx.SYS statement in the CONFIG.SYS file or the COM port is unavailable for use by the device driver. For an IBM Personal Computer AT, you cannot use the ASYNCDDA.SYS and SDLCDD.SYS device drivers at the same time. ASYNCDDA.SYS supports COM1 and COM2 only. This device driver uses storage that can also be used for DOS mode. Do not use this device driver unless you require its function since it reduces the amount of storage available to run OS/2 application programs. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load ACDI support on an IBM Personal Computer AT: DEVICE=C:\CMLIB\ASYNCDDA.SYS ΓòÉΓòÉΓòÉ 6.3. ASYNCDDB.SYS ΓòÉΓòÉΓòÉ ASYNCDDB.SYS Purpose To load the Asynchronous Communications Device Interface (ACDI) on an IBM Personal System/2. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇASYNCDDB.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ASYNCDDB.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ASYNCDDB.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Allows OS/2 application programs to use serial COM ports through the Asynchronous Communications Device Interface (ACDI). ASYNCDDB.SYS supports COM1, COM2, and COM3. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load ACDI support on an IBM Personal System/2. ASYNCDDB.SYS allows OS/2 application programs to use serial COM ports through ACDI. If a device driver that supports any one of the serial ports (COM1, COM2, or COM3) is installed by a DEVICE statement that precedes a DEVICE=ASYNCDDB.SYS statement, the port is unavailable to ASYNCDDB.SYS. If the DEVICE=ASYNCDDB.SYS statement comes prior to a DEVICE statement supporting a mouse, the DEVICE=ASYNCDDB.SYS statement is overridden without any warning or message. This device driver works for any IBM Personal System/2 but it does not take advantage of Direct Memory Access (DMA) even if you have DMA hardware available and active. DEVICE=C:\CMLIB\ASYNCDDB.SYS ΓòÉΓòÉΓòÉ 6.4. ASYNCDDC.SYS ΓòÉΓòÉΓòÉ ASYNCDDC.SYS Purpose ASYNCDDC.SYS allows OS/2 application programs to use serial COM ports through ACDI. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇASYNCDDC.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ASYNCDDC.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ASYNCDDC.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ If a device driver that supports any one of the serial ports (COM1, COM2, or COM3) is installed by a DEVICE statement that precedes a DEVICE=ASYNCDDC.SYS statement, the port is unavailable to ASYNCDDC.SYS. If the DEVICE=ASYNCDDC.SYS statement comes prior to a DEVICE statement supporting a mouse, the DEVICE=ASYNCDDC.SYS statement is overridden without any warning or message. If you have an IBM Personal System/2 and have Direct Memory Access (DMA) hardware available and active, make sure that the ASYNCDDC.SYS device driver statement is located in your CONFIG.SYS file. DMA hardware must be enabled by using the IBM Personal System/2 Reference Diskette. If the DMA hardware is not available and active, you will not be able to use ACDI. Note: Switching to the ASYNCDDB.SYS device driver will allow you to use ACDI without utilizing DMA. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\ASYNCDDC.SYS ΓòÉΓòÉΓòÉ 6.5. ASYNCDDE.SYS ΓòÉΓòÉΓòÉ ASYNCDDE.SYS Purpose ASYNCDDE.SYS allows you to use ACDI Redirection. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇASYNCDDE.SYSΓöÇΓöÇserver_nameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ASYCDDE.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ASYCDDE.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> server_name ΓòÉΓòÉΓòÉ A required parameter that specifies a valid Local Area Network Asynchronous Communications Server (LANACS) server name. This 1- to 8-character name must be the same name as the LANACS server on your network. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ If you want to use ACDI Redirection, make sure that the ASYNCDDE.SYS device driver statement is located in your CONFIG.SYS file. ASYNCDDE.SYS will not load unless a valid LANACS server name is specified. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\ASYNCDDE.SYS server ΓòÉΓòÉΓòÉ 6.6. CMKFMDD.SYS ΓòÉΓòÉΓòÉ CMKFMDD.SYS Purpose Manages the locked storage that is used to contain control blocks used for communication between the SNA subsystem and DLCs on OS/2 1.0 and above. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMKFMDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMKFMDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMKFMDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This device driver locks and unlocks segments used to contain frames and Command Control Blocks (CCBs). It also provides a ring 0 interface for other device drivers to request and free frames and CCBs. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load this device driver. DEVICE=C:\CMLIB\CMKFMDD.SYS ΓòÉΓòÉΓòÉ 6.7. CMKFMDE.SYS ΓòÉΓòÉΓòÉ CMKFMDE.SYS Purpose Manages the locked storage that is used to contain control blocks used for communication between the SNA subsystem and DLCs on OS/2 2.0 and above. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇCMKFMDE.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMKFMDE.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMKFMDE.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This device driver locks and unlocks segments used to contain frames and Command Control Blocks (CCBs). It also provides a ring 0 interface for other device drivers to request and free frames and CCBs. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load this device driver. DEVICE=C:\CMLIB\CMKFMDE.SYS ΓòÉΓòÉΓòÉ 6.8. DFTDD.SYS ΓòÉΓòÉΓòÉ DFTDD.SYS Purpose Allows Communications Manager 3270 emulation (DFT) to access 3270 Emulation adapter cards or PCMCIA adapter card for use in communicating with 3274/3174 control units in DFT mode, as well as the System/9370. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇDFTDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the CMKFMDE.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the CMKFMDE.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ For the IBM Personal Computer AT, use the 3278/79 Emulation Adapter and the Advanced 3278/79 Emulation Adapter. For the supported IBM Personal System/2 models, use the IBM 3270 Connection Adapter or 3270 PCMCIA card. This device driver is used with coaxial connections. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement in the CONFIG.SYS file to load this device driver. DEVICE=C:\CMLIB\DFTDD.SYS ΓòÉΓòÉΓòÉ 6.9. GENMSGDD.OS2 ΓòÉΓòÉΓòÉ GENMSGDD.OS2 Purpose Allows the ISDN device drivers to interface with FFST/2. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇGENMSGDD.OS2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the GENMSGDD.OS2 file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the GENMSGDD.OS2 file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Placement of this device driver must be before the PROTMAN.OS2 statement. (DEVICE=x:\IBMCOM\PROTMAN.OS2) ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\GENMSGDD.OS2 ΓòÉΓòÉΓòÉ 6.10. GENMSGGEX.EXE ΓòÉΓòÉΓòÉ GENMSGGEX.EXE Purpose Provides a thread for the message device driver to interface with FFST/2. Syntax >>ΓöÇΓöÇRUN=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇGENMSGEX.EXEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the GENMSGGEX.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the GENMSGGEX.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Both GENMSGDD.OS2 and GENMSGEX.EXE must be present for device driver message support. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ RUN=C:\CMLIB\GENMSGEX.EXE ΓòÉΓòÉΓòÉ 6.11. ICARICIO.SYS ΓòÉΓòÉΓòÉ ICARICIO.SYS Purpose Allows Communications Manager X.25 support to access the IBM X.25 Interface Co-Processor/2 adapter for use in communicating with X.25 networks. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇICARICIO.SYSΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇIΓöÇΓöÇΓöÇ(card number)ΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the ICARICIO.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the ICARICIO.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> I (card number) ΓòÉΓòÉΓòÉ ICARICIO.SYS provides the capability to ignore certain Realtime Interface Co-Processor (ARTIC) cards. Using this parameter causes cards with the specified card numbers to be ignored. Note: The ARTIC card at Base I/O address 2A0 has a physical card number of 0. If you want to ignore more than one ARTIC card, separate the physical card numbers by either commas or spaces. The only valid entries for the ignore parameter are 0 through 9 and A through F. Note: An ARTIC card that appears in the ICAPARM.PRM (parameter) file is not ignored. If the card you want to ignore appears in the ICAPARM.PRM file, that card's entry must be removed. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Provides an application programming interface (API) Co-Processor Multiport/2 adapter. This device driver is for use with IBM Personal System/2 models 50Z, 55SX, 60, 70, P70, and 80. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\ICARICIO.SYS To ignore physical cards 0 and 2, but not 1, type the following line in your CONFIG.SYS file: DEVICE=C:\CMLIB\ICARICIO.SYS I(0,2) ΓòÉΓòÉΓòÉ 6.12. IDLCDD.SYS ΓòÉΓòÉΓòÉ IDLCDD.SYS Purpose Allows access to the IDLC protocol driver for Communications Manager SNA support. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇIDLCDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the IDLCDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the IDLCDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Use this device driver statement when using IDLC over IDSN. This statement must follow IDLCPD.SYS in your CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Exampes ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\IDLCDD.SYS ΓòÉΓòÉΓòÉ 6.13. IDLCPD.SYS ΓòÉΓòÉΓòÉ IDLCPD.SYS Purpose Provides CCITT Q.922 protocol support. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇIDLCPD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the IDLCPD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the IDLCPD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ IDLCPD.SYS must be placed after the PROTMAN.OS2 statement in your CONFIG.SYS file. Use this device driver statement when using IDLC over IDSN. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\IDLCPD.SYS ΓòÉΓòÉΓòÉ 6.14. IDLCVMAC.SYS ΓòÉΓòÉΓòÉ IDLCVMAC.SYS Purpose Links IDLC logical adapters to the data channels for ISDN when the call is connected. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇIDLCVMAC.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the IDLCVMAC.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the IDLCVMAC.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remars ΓòÉΓòÉΓòÉ Use this device driver statement when you are using IDLC over ISDN. This device driver statement must be after the IDLCDD.OS2 statement in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Exampes ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\IDLCVMAC.SYS ΓòÉΓòÉΓòÉ 6.15. LANVMAC.SYS ΓòÉΓòÉΓòÉ LANVMAC.SYS Purpose Links LAN logical adapters to the data channels for ISDN when the call is connected. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇLANVMAC.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the LANVMAC.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the LANVMAC.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Use this device driver statement when you are using LANs over ISDN. This device driver statement must be after the PROTMAN.OS2 statement in the CONFIG.SYS file. To install LANVMAC.SYS in the network information file (.NIF), type LAPS at the OS/2 prompt, select install, and insert Communications Manager diskette number 6. LAPS configuration places this statement in your CONFIG.SYS file after you configure Communications Manager. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\LANVMAC.SYS ΓòÉΓòÉΓòÉ 6.16. R0CSDD.SYS ΓòÉΓòÉΓòÉ R0CSDD.SYS Purpose Analyzes your workstation's processing capabilities and supplies that information to other device drivers for interaction between software and hardware. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇR0CSDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the R0CSDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the R0CSDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This device driver must be installed for all configurations and it must be before the SDLCDD.SYS device driver statement in your CONFIG.SYS file. Note: The second digit in R0csdd is a zero. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\R0CSDD.SYS ΓòÉΓòÉΓòÉ 6.17. RUNX25.EXE ΓòÉΓòÉΓòÉ RUNX25.EXE Purpose Provides an OS/2 thread of execution for X25DD.SYS. Syntax >>ΓöÇΓöÇRUN=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇRUNX25.EXEΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓööΓöÇ/NΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the RUNX25.EXE file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the RUNX25.EXE file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> /N ΓòÉΓòÉΓòÉ Instructs RUNX25.EXE to not issue a NETBIND to PROTMAN.OS2. This is an optional parameter. It is not needed even if another process (example: NETBIND.EXE) issues a NETBIND to PROTMAN.OS2. It is provided in case future releases of PROTMAN.OS2 do not handle multiple NETBIND instructions. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ RUNX25.EXE must appear after the X25DD.SYS statement in your CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ RUN=C:\CMLIB\RUNX25.EXE RUN=C:\CMLIB\RUNX25.EXE /N ΓòÉΓòÉΓòÉ 6.18. SDLCDD.SYS ΓòÉΓòÉΓòÉ SDLCDD.SYS Purpose Installs the Synchronous Data Link Control (SDLC) device driver. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSDLCDD.SYSΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ Γö£ΓöÇNΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ0ΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇSΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇ1ΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇBΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the SDLCDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the SDLCDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> N ΓòÉΓòÉΓòÉ Specifies that interrupts should not be shared. ΓòÉΓòÉΓòÉ <hidden> S ΓòÉΓòÉΓòÉ Specifies that interrupts should be shared. ΓòÉΓòÉΓòÉ <hidden> 0 ΓòÉΓòÉΓòÉ Specifies that adapter 0 should be enabled. ΓòÉΓòÉΓòÉ <hidden> 1 ΓòÉΓòÉΓòÉ Specifies that adapter 1 should be enabled. ΓòÉΓòÉΓòÉ <hidden> B ΓòÉΓòÉΓòÉ Specifies that both adapter 0 and adapter 1 should be enabled. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Allows OS/2 application programs or system programs (such as Communications Manager 3270 emulation) to use SDLC devices for communications. This device driver requires that the R0CSDD.SYS device driver also be loaded. The SDLCDD.SYS statement must come after the R0CSDD.SYS statement in your CONFIG.SYS file. For the IBM Personal Computer AT/ISA bus machines, you cannot use the SDLCDD.SYS device driver at the same time as any serial device that uses interrupt levels 3 or 4, because interrupts cannot be shared. The SDLC adapter card and MPA cards are restricted to use interrupt levels 3 and 4. If you need to use either of the preceding (for example, 3270 emulation (SDLC)), you must maintain separate copies of the CONFIG.SYS file; one for each device driver. The system must be restarted (press the Ctrl+Alt+Del keys) after the appropriate CONFIG.SYS file is placed in the root directory. If only one adapter is installed, it can be set to any of the valid values described in the following instructions. It does not have to be set to SDLC_1, Arb_1. If two adapters are installed, they must be set as follows: o To enable adapter 0, the reference diskette setting for the adapter must be SDLC_1, Arb_1. o To enable adapter 1, the reference diskette setting for the adapter must be SDLC_2 with an arbitration level of 4 or greater (for example, SDLC_2, Arb_7.). If no adapters with valid settings are found, the device driver will not be installed and "device not installed" will be displayed when you start your system. If at least one adapter with valid settings is found, the device driver will be installed and only the appropriate adapter will be enabled. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement to install the SDLC device driver on an IBM Personal Computer AT. DEVICE=C:\CMLIB\SDLCDD.SYS Use the following statement to install SDLC device driver for a primary adapter, on the supported IBM Personal System/2 models, with interrupt levels for SDLC specified so they can be shared. DEVICE=C:\CMLIB\SDLCDD.SYS S 0 ΓòÉΓòÉΓòÉ 6.19. SDLCSNET.OS2 ΓòÉΓòÉΓòÉ SDLCSNET.OS2 Purpose This device driver is used for the ISDN SDLC stack (NDIS network standard). Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSDLCSNET.OS2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the SDLCSNET.OS2 file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the SDLCSNET.OS2 file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ SDLCSNET.OS2 splits the protocol driver from the MAC level adapter code. This device driver is the SDLC NDIS-compliant protocol driver. This device driver statement must be placed after the PROTMAN.OS2 statement in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\SDLCSNET.OS2 ΓòÉΓòÉΓòÉ 6.20. SDLCVMAC.SYS ΓòÉΓòÉΓòÉ SDLCVMAC.SYS Purpose Links SDLC logical adapters to the data channels for ISDN when the call is connected. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇSDLCVMAC.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the SDLCVMAC.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the SDLCVMAC.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remar s ΓòÉΓòÉΓòÉ Use this device driver statement when you are using SDLC over ISDN. This device driver statement must be after the PROTMAN.OS2 statement in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examp es ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\SDLCVMAC.SYS ΓòÉΓòÉΓòÉ 6.21. T1P1SDD.SYS ΓòÉΓòÉΓòÉ T1P1SDD.SYS Purpose Allows you to use the Twinaxial adapter on a workstation using an AT bus. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇT1P1SDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇCFG=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the T1P1SDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the T1P1SDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Specifies the file name of your configuration. You can also optionally specify the drive and path of your configuration (drive2, path2). ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement to load the IBM Enhanced Emulator Adapter support on an IBM Personal Computer AT or an IBM Personal System/2 Model 30 286. DEVICE=C:\CMLIB\T1P1SDD.SYS CFG=:\CMLIB\ACSCFG.CFG ΓòÉΓòÉΓòÉ 6.22. T1P1NDD.SYS ΓòÉΓòÉΓòÉ T1P1NDD.SYS Purpose Allows you to use the Twinaxial adapter on a workstation using a Microchannel bus. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇT1P1NDD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ >ΓöÇΓöÇCFG=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfilenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdrive2ΓöÇΓöÿ ΓööΓöÇpath2ΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the T1P1NDD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the T1P1NDD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> filename ΓòÉΓòÉΓòÉ Specifies the file name of your configuration. You can also optionally specify the drive and path of your configuration (drive2, path2). ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ Use the following statement to load the IBM System 36/38 Workstation Emulation Adapter/A support on IBM PS/2 models 50, 55, 60, 70, and 80. DEVICE=C:\CMLIB\T1P1NDD.SYS CFG=C:\CMLIB\ACSCFG.CFG ΓòÉΓòÉΓòÉ 6.23. VHAPI.OS2 ΓòÉΓòÉΓòÉ VHAPI.OS2 Purpose VHAPI.OS2 is the EHLLAPI virtual device driver (VDD). It allows existing DOS EHLLAPI applications to run in the OS/2 virtual DOS machine (VDM) environment. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇVHAPI.OS2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the VHAPI.OS2 file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the VHAPI.OS2 file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ This device driver statement is not placed in the CONFIG.SYS file by default. To add this device driver statement, use VHAPINST.EXE. Refer to EHLLAPI Programming Reference for additional information. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\VHAPI.OS2 Purpose Provides frame layer (layer 2) and packet layer (layer 3) support for the ISDN X.25 stack using the NDIS network standard. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇX25DD.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the X25DD.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the X25DD.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ The X25DD.SYS device driver is required when using X.25 over ISDN. This device driver statement must appear after the PROTMAN.OS2 statement in your CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\X25DD.SYS ΓòÉΓòÉΓòÉ 6.24. X25VMAC.SYS ΓòÉΓòÉΓòÉ X25VMAC.SYS Purpose Links X25 logical adapters to the data channels for ISDN when the call is connected. Syntax >>ΓöÇΓöÇDEVICE=ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇX25VMAC.SYSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>< ΓööΓöÇdriveΓöÇΓöÿ ΓööΓöÇpathΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> drive ΓòÉΓòÉΓòÉ The drive where the X25VMAC.SYS file resides. Specify this drive only if it is not the default drive. ΓòÉΓòÉΓòÉ <hidden> path ΓòÉΓòÉΓòÉ The path designator that specifies where the X25VMAC.SYS file resides. Use this path only if the file is not in the default path. ΓòÉΓòÉΓòÉ <hidden> Remarks ΓòÉΓòÉΓòÉ Use this device driver statement when you are using X25 over ISDN. This device driver statement must be after the PROTMAN.OS2 statement in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Examples ΓòÉΓòÉΓòÉ DEVICE=C:\CMLIB\X25VMAC.SYS ΓòÉΓòÉΓòÉ 6.25. CONFIG.SYS Statements ΓòÉΓòÉΓòÉ Use Required CONFIG.SYS parameters as a guide to the CONFIG.SYS statements required for various protocol types. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Required CONFIG.SYS parameters Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé PROTOCOL TYPE Γöé PC TYPE Γöé STATEMENTS IN CONFIG.SYS Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ACDI Γöé All non-microchannel Γöé DEVICE=d:\CMLIB\ASYNCDDA.SYS Γöé Γöé Γöé types Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ACDI Γöé Microchannel types Γöé DEVICE=d:\CMLIB\ASYNCDDB.SYS Γöé Γöé Γöé including Model 90 or Γöé Γöé Γöé Γöé 95 with ASYNCH DMA Γöé Γöé Γöé Γöé disabled Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ACDI Γöé Mod 90 or 95 with Γöé DEVICE=d:\CMLIB\ASYNCDDC.SYS Γöé Γöé Γöé ASYNC DMA enabled Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ACDI redi- Γöé All types Γöé DEVICE=d:\CMLIB\ASYNCDDE.SYS Γöé Γöé rection Γöé Γöé server_name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Coaxial (DFT) Γöé All types Γöé DEVICE=d:\CMLIB\DFTDD.SYS Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé SDLC Γöé All non-microchannel Γöé DEVICE=d:\CMLIB\R0CSDD.SYS Γöé Γöé Γöé types Γöé DEVICE=d:\CMLIB\SDLCDD.SYS Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé SDLC Γöé All microchannel Γöé DEVICE=d:\CMLIB\R0CSDD.SYS Γöé Γöé Γöé types Γöé DEVICE=d:\CMLIB\SDLCDD.SYS x y Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé x can be S or N. y can be 0, 1, Γöé Γöé Γöé Γöé or B. The defaults are N and 0. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé X.25 Γöé All microchannel Γöé DEVICE=d:\CMLIB\ICARICIO.SYS x Γöé Γöé Γöé types Γöé Γöé Γöé Γöé Γöé x is I(card numbers). This is an Γöé Γöé Γöé Γöé optional parameter to ignore Γöé Γöé Γöé Γöé adapters. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Twinaxial Γöé All non-microchannel Γöé DEVICE=d:\CMLIB\T1P1SDD.SYS Γöé Γöé Γöé types; All micro- Γöé CFG=d:\CMLIB\filenam.CFG Γöé Γöé Γöé channel types for Γöé Γöé Γöé Γöé adapter #64G3494 Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Twinaxial Γöé All microchannel Γöé DEVICE=d:\CMLIB\T1P1NDD.SYS Γöé Γöé Γöé types for adapter Γöé CFG=d:\CMLIB\filenam.CFG Γöé Γöé Γöé #69X6279 Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LAN Γöé All types Γöé DEVICE=d:\IBMCOM\LANMSGDD.OS2 Γöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\PROTMAN.OS2 Γöé Γöé Γöé Γöé /I:d:\IMBCOM Γöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\PROTOCOL\LANDD.SYSΓöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\MAC\MACDRIVER.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ACSLANDD.SYS Γöé Γöé Γöé Γöé RUN=d:\IBMCOM\LANMSGEX.EXE Γöé Γöé Γöé Γöé RUN=d:\IBMCOM\PROTOCOL\NETBIND.EXE Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé (MACDRIVER.SYS is the appropriate Γöé Γöé Γöé Γöé network driver configured in LAPS) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé SDLC using ISDN Γöé All types Γöé DEVICE=d:\CMLIB\GENMSGDD.OS2 Γöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\PROTMAN.OS2 Γöé Γöé Γöé Γöé /I:d:\IMBCOM Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\SDLCSNET.OS2 Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\SDLCVMAC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBARIC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBADD.SYS Γöé Γöé Γöé Γöé RUN=d:\CMLIB\GENMSGEX.EXE Γöé Γöé Γöé Γöé RUN=d:\IBMCOM\PROTOCOL\NETBIND.EXE Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé IDLC using ISDN Γöé All types Γöé DEVICE=d:\CMLIB\GENMSGDD.OS2 Γöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\PROTMAN.OS2 Γöé Γöé Γöé Γöé /I:d:\IMBCOM Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\IDLCPD.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\IDLCDD.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\IDLCVMAC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBARIC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBADD.SYS Γöé Γöé Γöé Γöé RUN=d:\CMLIB\GENMSGEX.EXE Γöé Γöé Γöé Γöé RUN=d:\IBMCOM\PROTOCOL\NETBIND.EXE Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Required CONFIG.SYS parameters Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé PROTOCOL TYPE Γöé PC TYPE Γöé STATEMENTS IN CONFIG.SYS Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé X.25 using ISDN Γöé All types Γöé DEVICE=d:\CMLIB\GENMSGDD.OS2 Γöé Γöé Γöé Γöé DEVICE=d:\IBMCOM\PROTMAN.OS2 Γöé Γöé Γöé Γöé /I:d:\IMBCOM Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\X25DD.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\X25VMAC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBARIC.SYS Γöé Γöé Γöé Γöé DEVICE=d:\CMLIB\ISBADD.SYS Γöé Γöé Γöé Γöé RUN=d:\CMLIB\GENMSGEX.EXE Γöé Γöé Γöé Γöé RUN=d:\IBMCOM\PROTOCOL\NETBIND.EXE Γöé Γöé Γöé Γöé RUN=d:\CMLIB\RUNX25.EXE /N Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Note: 1. d is the target drive. 2. When multiple statements are listed, they must be loaded in the order listed. ΓòÉΓòÉΓòÉ 6.26. CONFIG.SYS Statements for APPN ΓòÉΓòÉΓòÉ Add one of the following DEVICE= statements to CONFIG.SYS when installing APPC/APPN support for SDLC, X.25, Twinaxial, LAN, SDLC using ISDN, IDLC using ISDN, and X.25 using ISDN. For optimum performance, it should be the last device driver statement in CONFIG.SYS: o DEVICE=d:\CMLIB\CMKFMDD.SYS o DEVICE=d:\CMLIB\CMKFMDE.SYS