(c) Copyright IBM Corporation, 1994. All rights reserved. PRODUCTIVITY AIDS *************************************************************************** ***** TABLE OF CONTENTS ***** *************************************************************************** 1.0 INSTALLATION 2.0 ACM 2.1. Introduction 2.2. Selecting a Server 2.3. Scanning for Profiles 2.4. Editing a Profile 2.5. Finding a List of Profiles 2.6. Exiting the Access Control Manager 3.0 CONMAN 3.1. Introduction 3.2. Installation 3.3. Syntax 3.4. STARTUP.CMD Usage 3.5. Connection Manager Data File 3.6. Mouse Selections 3.7. Keys Help 4.0 DCDBEXIM 4.1. Introduction 4.2. IMPACC 4.3. IMPALIAS 4.4. IMGROUP 4.5. IMPGRPPM 4.6. IMPUSER 5.0 DIRSTAT 5.1. Description 5.2. Sample Output 6.0 DISCUSER 6.1. Description 6.2. Installation 7.0 EXPDCDB 8.0 EXTALIAS 8.1. Description 8.2. Installation 9.0 FINDNAME 10.0 FORCELOG 11.0 LOGOFF 11.1. Introduction 11.2. Requirements-Requesters 11.3. Requirements-Servers 11.4. How It Works 12.0 LSRXUTIL 12.1. Description 12.2. Installation 13.0 LSS 13.1. Description 13.2. Installation 13.3. More Information 14.0 MOVESTUF 15.0 NCBSTAT 15.1. Description 15.2. Syntax 16.0 NETSESS2 16.1. Introduction 16.2. Description 16.3. Syntax 16.4. Output Interpretation 16.5. Sample Output 17.0 NEWPW 18.0 PWMON 19.0 QMC 19.1. Introduction 19.2. Description 19.3. Syntax 20.0 RDRDEBUG 20.1. Description 20.2. Sample Output 21.0 REMOTEFS 21.1. Description 21.2. Installation 22.0 REMUSER 22.1. Description 22.2. Syntax 22.3. Installation 23.0 REPLINI 24.0 RPLADD 24.1. Introduction 24.2. Using RPLADD 24.3. Command Line Parameters 24.4. Input File Format 25.0 RPLDEL 25.1. Introduction 25.2. Using RPLDEL 25.3. Command Line Parameters 25.4. Input File Format 26.0 RPLENUM 26.1. Introduction 26.2. Using RPLENUM 26.2. Command Line Parameters 27.0 RPLFDISK 27.1. Introduction 27.2. Using RPLFDISK 27.3. Command Line Parameters 28.0 RPLSRID 28.1. Introduction 28.2. Using RPLSRID 28.3. Command Line Parameters 29.0 SMBTOOL 29.1. Introduction 30.0 SNAPDF 30.1. Introduction 30.2. Syntax 30.3. Dump Formatter Window 31.0 SNAPDUMP 31.1. Introduction 31.2. Data Collection 31.3. Operating Environment 31.4. The SnapDump/2 Package 31.5. Installing SnapDump/2 31.6. Syntax 31.7. SnapDump/2 Input File 31.8. Sample SnapDump/2 Input File 31.9. SnapDump/2 Output File 31.10. Displaying SnapDump/2 Output Files 31.11. Transporting SnapDump/2 Output Files 31.12. Support for SnapDump/2 31.12.1. Usage Support 31.12.2. Defect Support 31.13. SnapDump/2 Utility Programs 31.14. Example *************************************************************************** 1.0 INSTALLATION *************************************************************************** The LAN Services Productivity Aids Installation window has the following fields/controls: * Install After selecting the source drive, target drive, and LAN Services Productivity Aids program, select Install to begin installation of the program. NOTE: The following applications are not installed with this installation procedure; refer to the applicable sections of this file for installation instructions. - DISCUSER - EXTALIAS - LSRXUTIL - LSS - REMOTEFS - REMUSER * Exit After you have completed installing the selected LAN Services Productivity Aids programs, select Exit to end the program. * Source drive Use the up an down arrows on the Source drive spin button to select the drive that will contain the LAN Services Productivity Aids disks. The source drive can be either a physical diskette drive or CD-ROM drive. * Target drive The Target drive spin button is preset to the drive letter where the LAN Services files were found on your system. The LAN Services Productivity Aids programs must be installed on the same drive where the LAN Services files were installed. The target drive must be a physical hard disk drive installed in your system. * Productivity Aids programs This container lists the LAN Services Productivity Aids programs available for installation on your system. The container displays two fields: File name The source file that contains the Productivity Aids program. Description Describes the function of the Productivity Aids program. Select the program to be installed by highlighting a line item within the container. *************************************************************************** 2.0 ACM *************************************************************************** _________________ 2.1. Introduction The Access Control Manager provides both administrators and users the ability to manage access control rules on servers in the network. Users can use the Access Control Manager to: * Select a server to manage. * Scan drives and devices for profiles. * Edit profiles from a tree view. * Find lists of profiles to manage as a group. * Exit the application. _______________________ 2.2. Selecting a Server There are two ways to display the Select a Server window: * Select the Options menu bar item and then the Select server menu item. * Display the Context menu (mouse button 2) and then select the Select server menu item. You can also select a server to manage when you start the Access Control Manager from an OS/2 window. Simply type the name of the server after the command to start the Access Control Manager program. For example: ACM SERVER1 __________________________ 2.3. Scanning for Profiles To scan a drive, directory, or device for profiles: 1. Select the drive, directory, or device you want to scan. 2. Select the Scan menu item from the Menu Bar. 3. Select the Descendent menu item from the displayed Scan menu. The Scan menu item is also available on the Context menu. ______________________ 2.4. Editing a Profile To display a profile to edit: 1. Scan the drive or device that contains the profile. 2. Open the tree to display the profile. There are three ways to edit a profile once it is displayed: * Select (double-click) the profile icon. * Move the cursor to the profile icon, and select Edit from the Manage menu item. * Display the Context menu for the profile icon, and select the Edit menu item. In all three cases, the Add/Edit window is displayed, which will allow you to edit the permissions in the profile. _______________________________ 2.5. Finding a List of Profiles There are two ways to find a list of profiles to manage: * Select the Find menu bar item and then any of the choices in that menu. * Display the Context menu (mouse button 2) and then select the Find menu item. _______________________________________ 2.6. Exiting the Access Control Manager There are three ways to exit the Access Control Manager. * Select the Exit menu item from the Manage menu. * Select the Exit menu item from the Context menu. * Select the Close menu item from the System menu. *************************************************************************** 3.0 CONMAN *************************************************************************** Connection Manager Version 1.6 (C) Copyright IBM Corporation 1991, 1992. All rights reserved. _________________ 3.1. Introduction The purpose of the Connection Manager is to provide OS/2 LAN Requester users with an easy method of managing LAN resources. Connection Manager displays the current state of all LAN connections while allowing the user to connect to, release, and reassign LAN resources. The main window of Connection Manager displays the resources to which the local OS/2 LAN Requester is currently connected and the locations where they are connected. This display may be either graphics or text depending on the selection of the View pull-down menu. The user ID logged onto the machine is indicated in the upper left hand corner, or "Not Logged on" is displayed if OS/2 LAN Requester has not been started. In a column to the right is a list of all servers between which connections exist. To the right of the server list is a list of all resources in use at that server and the locations where they are connected. _________________ 3.2. Installation Three files constitute the Connection Manager utility. These files are CONMAN.EXE, CONMAN.INI, and CONMAN.HLP. CONMAN.EXE is an OS/2 Presentation Manager application that uses OS/2 LAN Requester. This file needs to be placed in your path or installed as an application in a group menu. The CONMAN.INI file should be located either in the same location as CONMAN.EXE or somewhere along the DPATH. Connection Manager searches for all occurrences of CONMAN.INI, looking first in the directory from which CONMAN.EXE was called and then in each location along the DPATH, adding the entries found in the CONMAN.INI files to its list of known resources. The CONMAN.HLP file is the online help for Connection Manager. It must be located in the current working directory or in a directory pointed to by the HELP environment variable. A LAN administrator can choose to have Connection Manager as one of the applications in the Public Applications group. This allows the main executable and main CONMAN.INI file to reside on a server where it can be centrally maintained. Users then have the option of keeping a CONMAN.INI file of their personal resources on their own workstations (located within the DPATH). ___________ 3.3. Syntax At the command prompt, the syntax for Connection Manager is: _________________________ | | ___________CONMAN___________v_________________________|_| |_path_| |_/MIN_| |__/N=nickname________| | | | | | |_/MAX_| |__/F=alias___________| | |_@ d:____| |__/P=alias___________| | |_@ LPTx:_| |__/S=alias___________| |_@ COMx:_| where: path Specifies either the drive and path location of where to find CONMAN.EXE, or the universal naming convention of where CONMAN.EXE is found on the network. This location is used to find the primary CONMAN.INI file. Additional CONMAN.INI files are pulled in if they are located along the DPATH. /MIN Specifies that Connection Manager is to be minimized when started. /MAX Specifies that Connection Manager is to be maximized when started. /N Specifies that a nickname is to be connected. The nickname must be defined in the CONMAN.INI file. The nickname may contain spaces. /F Specifies a file alias to attach. The alias is either the alias of a resource that exists in the current domain, or the universal naming convention of a resource that exists in another domain. /P Specifies a printer alias to attach. The alias is either the alias of a resource that exists in the current domain, or the universal naming convention of a resource that exists in another domain. /S Specifies a serial device alias to attach. The alias is either the alias of a resource that exists in the current domain, or the universal naming convention of a resource that exists in another domain. d: Specifies a drive to attach a file resource to. If not specified, the first available drive is used. LPTx: Specifies a printer port to attach a printer resource to. If not specified, the first available printer port is used. COMx: Specifies a serial port to attach a serial device to. If not specified, the first available serial port is used. ______________________ 3.4. STARTUP.CMD Usage A common use of Connection Manager is to have it activated by your STARTUP.CMD when you log on to OS/2 LAN Requester. For example, the STARTUP.CMD file might contain the following lines: Example STARTUP.CMD file. . . . LOGON userid /P:password \\server1\tools\CONMAN /MIN /N=Lotus Working Set /P=Q4019A @ LPT2: . . . In this example, the user first logs on to the network specifying his user ID and password. After the logon is complete, the STARTUP.CMD invokes Connection Manager from where it resides on a LAN server by specifying the universal naming convention of this alias in front of CONMAN. This causes Connection Manager to load any CONMAN.INI file found at that location. Further parameters on the command line inform Connection Manager that it is to minimize itself on startup, connect to all the aliases specified by the "Lotus Working Set" nickname, and connect the alias Q4019A at printer port LPT2:. Note that Q4019A is an alias, and therefore must exist in the current domain. If the printer exists in a different domain from the logon domain, the full universal naming convention (UNC) must be specified. _________________________________ 3.5. Connection Manager Data File Nickname entries for the Attach window are obtained from the Connection Manager data files. The data files are named CONMAN.INI and must exist in the DPATH or the same location as CONMAN.EXE. All CONMAN.INI files in these locations are used to fill the nickname list, filling first from the DPATH and then from the location of CONMAN.EXE. In this way, CONMAN can exist on a network drive with a master CONMAN.INI file, and the user can have a personal list of nicknames located along the DPATH. 3.5.1. Format of the Connection Manager Data File. The source file to the Connection Manager is a user-editable file, which defines the resources in the network and how they are accessed. Each file consists of two types of lines, comment lines, and resource lines. Columns Record field 1 - 40 Nickname User-defined name of the resource. If the nickname field is blank, the record is considered to be an additional resource to be linked along with the previous resource. 41-60 Alias Name The full universal naming convention of the resource. 61-70 Resource type Only the first character of the resource type is significant. The resource type can be either F for files, P for print devices, or S for serial devices. 71-76 Default location First choice location for linking the resource to. If this field is left blank, or contains an asterisk, the first available location is used. 77-84 Password If the remote resource requires a password, it can be specified in columns 77 - 84. Either an explicit password may be stored in the table, or a ? may be placed in column 77 to indicate Connection Manager should prompt the user for the password. A blank or an * in column 77 indicate that no password is used. The limit of aliases that may be defined to Connection Manager is 1000 for all CONMAN.INI files found. Any aliases above that number are discarded. This number may be further limited by system limitations. _____________________ 3.6. Mouse Selections While the display is in graphics mode, you can select or open items in the display with the mouse cursor. Move the mouse to the desired item and click (to select) or double-click (to open) with mouse button 1. ______________ 3.7. Keys Help The following is a list of all keys and their defined usage in Connection Manager: Key Function ALT-A Allows a user to attach to resources. ALT-F Sets current device type to files. ALT-G Changes main window display to graphics mode. ALT-L Depending on whether a user is currently logged on to the network, allows logging on or logging off. ALT-M Activates Move Resources window. ALT-P Sets current device type to print device. ALT-R Activates Release window. ALT-S Sets current device type to serial device. ALT-T Changes main window display to text mode. ALT-V Activates View Resources window. ALT-2 Changes main window display to half-sized graphics mode. F1 Displays context-sensitive help for Connection Manager. F3 Quits (exits) the Connection Manager. F10 Moves cursor to menu bar. *************************************************************************** 4.0 DCDBEXIM *************************************************************************** DCDBEXIM Version 4.0 (C) Copyright IBM Corporation 1994. All rights reserved. _________________ 4.1. Introduction DCDBEXIM is a PM program that imports DCDB information collected from EXPDCDB. ___________ 4.2. IMPACC Syntax: IMPACC OLD_SERVER_NAME NEW_SERVER_NAME INPUT_FILE_NAME [/CREATE] _____________ 4.3. IMPALIAS Syntax: IMPALIAS OLD_SERVER_NAME NEW_SERVER_NAME INPUT_FILE_NAME _____________ 4.4. IMPGROUP Syntax: IMPGROUP DC_NAME INPUT_FILE_NAME _____________ 4.5. IMPGRPPM IMPGRPPM Version 4.0 (C) Copyright IBM Corporation 1994. All rights reserved. IMPGRPPM is a PM program that imports a group from an ASCII file. ____________ 4.6. IMPUSER ImpUser Syntax: IMPAPPL DC_NAME INPUT_FILE_NAME *************************************************************************** 5.0 DIRSTAT *************************************************************************** NETWORK DIR.STATUS Version 0.01 (C) Copyright IBM Corporation 1991. All rights reserved. ________________ 5.1. Description DIRSTAT.EXE Adapter status information (SAPS, Link Stations, etc.) __________________ 5.2. Sample Output adapter #0 hard address :0x08005A49D377 soft address :0x08005A49D377 group address :0x00000000 functional addr :0x00000000 max SAPS :3 open SAPS :0 max link stations :8 open link stations :0 avail link stations:8 adapter config :0x0015' token release :Yes shared ram :16K data rate :16 mbps microcode level :0x000600C6D7F1C4C1F240 last ring status :0x0000 adapter type :0x0020 :Token-Ring Network PC 16/4 Adapter adapter #1 not installed *************************************************************************** 6.0 DISCUSER *************************************************************************** ________________ 6.1. Description DISCUSER forces a single user off the network domain by disabling the user's account. DISCUSER will also disconnect the user from all resources in the domain. DISCUSER has one input parameter which is the current user ID to be disconnected. _________________ 6.2. Installation 1. Create a subdirectory with an appropriate name. A suggested name would be DISCUSER. md dir_name 2. Change to the created subdirectory. cd dir_name NOTE: Be sure Productivity Aids diskette 2 is in the A: drive before performing step 3. 3. Run PKUNZIP2.EXE in order to unzip the DISCUSER.ZIP file on Productivity Aids diskette 2. pkunzip2 a:discuser.zip *************************************************************************** 7.0 EXPDCDB *************************************************************************** EXPDCDB Version 4.0 (C) Copyright IBM Corporation 1994. All rights reserved. EXPDCDB is a PM program that exports the DCDB information to an ASCII file. The file produced by EXPDCDB is a flat ASCII file containing all of the definitions (users, aliases, applications, and access control profiles) located on a domain. *************************************************************************** 8.0 EXTALIAS *************************************************************************** ________________ 8.1. Description EXTALIAS is a program that migrates external aliases to cross-domain aliases. _________________ 8.2. Installation 1. Create a subdirectory with an appropriate name. A suggested name would be EXTALIAS. md dir_name 2. Change to the created subdirectory. cd dir_name NOTE: Be sure Productivity Aids diskette 2 is in the A: drive before performing step 3. 3. Run PKUNZIP2.EXE in order to unzip the EXTALIAS.ZIP file on Productivity Aids diskette 2. pkunzip2 a:extalias.zip *************************************************************************** 9.0 FINDNAME *************************************************************************** FINDNAME.EXE is a simple OS/2 command line utility that searches for duplicate names in your local table and, if it does not find any, then prompts the user for a NetBIOS name to search for. The utility then searches the network for the adapter address of the machine or machines with that NetBIOS name. This may be useful if a network administrator is searching for a user who has caused a duplicate name conflict by misconfiguring a COMPUTERNAME parameter. This utility takes no parameters and requires that the OS/2 requester be started. *************************************************************************** 10.0 FORCELOG *************************************************************************** FORCELOG will pause all services and disconnect all users. *************************************************************************** 11.0 LOGOFF *************************************************************************** LOGOFF Utility Version 1.0 __________________ 11.1. Introduction The LOGOFF utility is a client-server application whose server piece enables: * Command line logoff of all users * A Presentation Manager interface where any or all users can be selected for a forced log off from the domain. The server piece can be run from any workstation in the network; however, it only logs users off the domain to which the workstation is currently logged on. The client piece of the code runs as a detached process on all OS/2 LAN Requesters. _____________________________ 11.2. Requirements-Requesters This program has the following requirements on requesters: * OS/2 Version 2.x * OS/2 LAN Requester or OS/2 LAN Server, versions 3.0 or 4.0 * CLNTLGFF.EXE program running as a detached process NetBIOS requirements: * 1 NetBIOS name in the PROTOCOL.INI file * 1 NCB in PROTOCOL.INI __________________________ 11.3. Requirements-Servers This program has the following requirements on servers * OS/2 Version 2.x * OS/2 LAN Requester or OS/2 LAN Server, versions 3.0 or 4.0 * LOGOFF.EXE program * 1 NetBIOS name in the PROTOCOL.INI file * 1 NCB in PROTOCOL.INI NetBIOS requirements: * 1 NetBIOS name in the PROTOCOL.INI file * 1 NCB in PROTOCOL.INI __________________ 11.4. How It Works The client version can be started in the STARTUP.CMD as follows: DETACH CLNTLGFF.EXE This program waits (without using any CPU resources) for the server program to initiate the logoff procedure. If the server sends the domain and user ID that is currently logged onto the workstation, then the user is logged off. If the server sends the correct domain and "ALL", CLNTLGFF checks to see whether the server piece LOGOFF is running on the workstation, and if so, does not log the user off. This is accomplished by turning off the ability to force the user off the workstation for three minutes (180 seconds). CLNTLGFF checks to see if someone is logged onto the workstation before trying to force the logoff. CLNTLGFF creates an output file called C:\LOGOFF.ERR to log any error messages and keep track of successful user logoffs. The server version has two options to start: * LOGOFF /ALL This is a non-Presentation Manager interface to log off all users except the user logged onto the workstation that issues this command. This is useful for tape backup operations where all users need to be forced off the domain. However, you do not want to place a dedicated logon statement in the batch file. This command is complete in a maximum of 10 seconds. * LOGOFF This is a Presentation Manager interface that allows a user to pick exactly what users to logoff. An option is also given to log all users off the network. Even though up to 1000 users can be listed, only 100 can be logged off at one time. After the selections have been made, the program is terminated. This can take up to 30 seconds. *************************************************************************** 12.0 LSRXUTIL *************************************************************************** ________________ 12.1. Description LSRXUTIL is an extensive set of REXX programming interfaces for LAN Server. LSRXUTIL provides administrators, application programmers, and end-users a simple means to develop LAN Server applications and to create command files and tools to automate repetitive tasks. The REXX programming interfaces are very similar to the application programming interfaces (APIs) provided by LAN Server. __________________ 12.2. Installation 1. Create a subdirectory with an appropriate name. A suggested name would be LSRXUTIL. md dir_name 2. Change to the created subdirectory. cd dir_name NOTE: Be sure Productivity Aids Diskette 2 is in the A: drive before performing step 3. 3. Run pkunzip2.exe in order to unzip the LSRXUTIL.ZIP file on Productivity Aids diskette 2. pkunzip2 a:lsrxutil.zip *************************************************************************** 13.0 LSS *************************************************************************** _________________ 13.1. Description LAN Server Specialist (LSS) is a problem determination tool for LAN Server 4.0. LSS consists of Agents and the Manager. The Agents are installed on each LAN Requester and Servers to be managed, and one LSS Manager is installed on a LAN Server (or Domain Controller) per LAN domain. LSS Agents report the errors, messages, and alerts issued by the LAN Requesters or Servers to the LSS Manager. The LSS Manager generates problem reports, which include: * The error messages correlated for the same problem cause * Possible cause(s) for the correlated error messages * Recommended action to fix the problem. LSS can also run on LAN Server 3.0. __________________ 13.2. Installation LSS is a CID-enabled (Configuration-Installation-Distribution) product. It is easy to install on workstations in LAN environments. 1. Install LSS from the LAN Server 4.0 Productivity Aid Diskettes 3 and 4: (NOTE: If you are installing from CD-ROM, the subdirectory to look for is LANEXP.) To install an LSS Manager (which includes a LSS agent), insert the LAN Server 4.0 Productivity Aid Diskette 3 in a drive and type: :\LSSINST /T:: For example, the following command will install LSS in D:\IBMLSS directory: A:\LSSINST /T:D: Similarly, to install a LSS Agent, insert the LAN Server 4.0 Productivity Aid Diskette 3 in a drive and type: :\LSSAINST /T:: This will install an Agent in the :\IBMLSS directory. 2. Create a code server: To create a code server from the LSS installation diskettes, LAN Server 4.0 Productivity Aid Diskettes 3 and 4, use the following command: LSSIMG /S: /T: For example, the following command will upload the LSS installation code to D:\LSSINST directory: A:\LSSIMG /S:A: /T:D:\LSSINST After that, you can install the LSS Agent and Manager from the code server remotely. ______________________ 13.3. More Information After a LSS Manager is installed, a LSS folder appears on the OS/2 desktop. From there you can read the on-line documentation for more information. *************************************************************************** 14.0 MOVESTUF *************************************************************************** Move Stuff Version 1.4 (C) Copyright IBM Corporation 1991, 1994. All rights reserved. This utility moves or copies aliases or home directories from one server to another server. *************************************************************************** 15.0 NCBSTAT *************************************************************************** NETWORK NCB.STATUS Version 0.02 (C) Copyright IBM Corporation 1991. All rights reserved. _________________ 15.1. Description NCBSTAT.EXE displays NetBIOS information. ____________ 15.2. Syntax The syntax of the NCBSTAT command follows: __NCBSTAT_________remotename___________| |_-An_| |_-hxx_| | where: -An Adapter number. Default is adapter 0. remotename Specifies the domain name. If the name contains blanks, you must enclose the entire string in double quotes; for example: "DOMAINNAME1 " Use '*' to represent the local system. Nulls are padded if the remotename length is not 16. -hxx Interpret the value as a hex value and append it to the remote name. For example: "DOMAINNAME1 " -h03 The entire name can be specified this way. For example: -H56414E43485552202020202020202003 *************************************************************************** 16.0 NETSESS2 *************************************************************************** NETSESS - Version 2.3 ee (C) Copyright IBM Corporation 1987. All rights reserved. __________________ 16.1. Introduction The NETSESS2 program obtains and prints session statistics kept by the LAN adapter card (or NetBEUI in the case of the token ring). The session statistics may be obtained for the local station only. __________________ 16.2. Description NETSESS2.EXE local LAN session information ____________ 16.3. Syntax The syntax of the NETSESS2 command follows: __NETSESS2___________session_name__| |_-lana_| | where: -lana Indicates use of the alternative LAN adapter specified instead of the default which is LAN adapter 0. Possible values include 1, 2, and 3. session_name Prints only the statistics for sessions with that local name. If this parameter is not specified, statistics for all sessions are printed. ___________________________ 16.4. Output Interpretation The session statistics printed appear as follows: Session statistics for local station Number of Sessions in progress = 03 LSN Status Local Name Remote Name Rcv Send --- ------- ---------------- ---------------- --- ---- 003 Session morbius YKTLAN1 001 000 004 Session jeffat robbi 001 001 005 Session morbius altair 001 000 Receive Datagram commands outstanding 000 Receive Any commands outstanding 004 The columns include the following information: LSN Contains the local session numbers that are assigned to each session by the LAN adapter. Status Contains keywords indicating the status of the session. See the "Technical Reference Manual" for explanations of these status conditions. Local Name Contains the LAN adapter name used at the local adapter in the CALL or LISTEN command that established the session. Remote Name Contains the LAN adapter name used at the remote adapter in the CALL or LISTEN command that established the session. Rcv Contains the number of outstanding RECEIVE commands for this session. Send Contains the number of outstanding SEND commands for this session. The two lines following the tabular information contain the number of outstanding RECEIVE DATAGRAM commands and the number of outstanding RECEIVE ANY commands, respectively. ___________________ 16.5. Sample Output NETSESS - Version 2.3 ee (C) Copyright IBM Corporation 1987. All rights reserved. Session statistics for local station Number of Sessions in progress = 02 LSN Status Local Name Remote Name Rcv Send --- ------- ---------------- ---------------- --- ---- 005 Listen FVT072394PLSERV * 000 000 027 Listen FVT072394PLSERV * 000 000 Receive Datagram commands outstanding 004 Receive Any commands outstanding 006 *************************************************************************** 17.0 NEWPW *************************************************************************** Change Password Version 1.0 (C) Copyright IBM Corporation 1990, 1992. All rights reserved. This program may be used to change your password on multiple OS/2 LAN domains. You may also use this program to determine your password age on multiple domains. The bottom of the Change Password window contains a message area. View this area for help and other messages. This window has the following fields: Domains Select one or more domains by highlighting them. User ID Enter user ID here (user ID must already exist on each domain). Old Password Enter the old password here. New Password Enter the new password here. New Password Enter the new password here again. (Confirmation) Check Password Age Select this push button to see the password age on each domain. Change Password Select this push button to change the password on each domain. *************************************************************************** 18.0 PWMON *************************************************************************** The Bad Password Monitor, PWMON, is a program to monitor attempted logons for invalid passwords and revoke the user's account if a limit is exceeded. This program MUST be run on the domain controller. Syntax: pwmon [limit] where: [limit] Number of password retries allowed before the user's account is disabled. Note that this must occur within the last two intervals defined by the value of alertsched. The default value is 3. The value you may specify must be in the range from 1 to 99. *************************************************************************** 19.0 QMC *************************************************************************** QSYSTEM V2.20 (C) Copyright IBM Corporation 1989, 1994. All rights reserved. __________________ 19.1. Introduction The QMC program returns a wealth of useful information about the hardware installed on the workstation where it is run. You must have the IOPL=YES statement in your CONFIG.SYS file for QMC to function. _________________ 19.2. Description QMC.EXE displays detailed technical information about your computer. ____________ 19.3. Syntax The syntax of the QSYSTEM command follows: QSYSTEM [/?][/A][/B][/C][/D][/E][/I][/M][/O[file]][/P][/Q] [key="text"] where: /? Displays this help information. /A Displays all Micro Channel adapters supported by QSYSTEM. /B Displays debug information. /C Displays additional detail on async ports. /D Displays a detailed listing of hardware. /E Displays current environment. /I Displays CONFIG.SYS, STARTUP.CMD & AUTOEXEC.BAT. /M Displays all machines supported by QSYSTEM. /O Redirects output to file QSYSTEM.OUT. /Ofile Redirects output to file (anyname). /P Pauses the output between screens. /Q Does not display redirect message. key="text" Defines key with text to appear in output (must be last option). For example: User="Norris Couch" "Site Location"=Boca There are a couple of methods to handle data scrolling off the screen: QMC | MORE Pipes information from QMC into the MORE command QMC /O Redirects the output to the QSYSTEM.OUT file The first technique is good if you just want to view the information one screen at a time. The second technique works best for keeping a permanent copy and being able to browse or edit the results. *************************************************************************** 20.0 RDRDEBUG *************************************************************************** _________________ 20.1. Description The RDRDEBUG utility dumps internal OS/2 requester data structures. It would primarily be used under the direction of IBM support personnel. This utility takes no parameters and requires that the OS/2 requester be started. ___________________ 20.2. Sample Output Active threads in redir: 0 Threads waiting to enter: 0 MPX Table (in decimal) ThreadId smb command TimeOut lsn BufChn pRetry MID pSrvList Complete 52 FindCls 65535 114 0 0 30466 VPP60 Complete 50 Trans2 65535 114 0 0 30531 VPP60 Complete 50 Trans2 65535 114 0 0 30596 VPP60 Complete 52 FindCls 65535 114 0 0 30661 VPP60 Complete 50 Trans2 65535 114 0 0 30726 VPP60 Complete 50 Trans2 65535 114 0 0 30791 VPP60 Complete 52 FindCls 65535 114 0 0 30856 VPP60 Complete 50 Trans2 65535 114 0 0 30921 VPP60 Complete 50 Trans2 65535 114 0 0 30986 VPP60 Complete 52 FindCls 65535 114 0 0 31051 VPP60 Complete 52 FindCls 65535 114 0 0 31116 VPP60 Complete 113 tdisc 65535 114 0 0 31181 VPP60 Complete 113 tdisc 65535 114 0 0 31246 VPP60 Complete 116 ulogoffx 65535 114 0 0 31311 VPP60 Complete 50 Trans2 65535 13 0 0 31376 MICKEY Complete 50 Trans2 65535 13 0 0 31441 MICKEY Complete 52 FindCls 65535 114 0 0 30226 VPP60 Complete 50 Trans2 65535 114 0 0 30291 VPP60 Complete 50 Trans2 65535 114 0 0 30356 VPP60 Complete 52 FindCls 65535 114 0 0 30421 VPP60 Server Information (srvlists) Server name: MICKEY Server is in Domain: MOUSE Server OS/2 version: OS/2 2.11 Server type: IBM LAN Server 3.0 SMB protocol: LAN Server 3.0 or MS LANMAN 2.1 Flags: 0 SRV_USER_LOGGEDON Security mode: SRV_USER_LEV SRV_ENCR_PWD Optional support: RAWREAD, RAWWRITE, SUBDIAL RefCnt: 1 SerialNm: 4 SBufLim: 64 MaxXmt: 1104 MaxWrt: 1104 MaxVCs: 1 SesKey: 13e9 WtCnt: 0 AsyPnd: 0 ActRq: 0 PndRq: 0 UID:1003 MchId: 0 Printing Redirector Per Thread Info. (RTCBs) SMB Segment (initial segment only) Free Command: 34 FindCls Error class: 0 Error: 0 Flags: 8 REQUEST UID: 4000 MID: 794b UID: 4000 PID: fa Data: 59 23 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Y#.............. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0 0 0 0 0 0 0 0 22 1d 42 43 22 1d 42 43 ........".BC".BC 0 0 0 0 0 0 0 0 10 0 1 2e 0 0 0 0 ................ 0 0 0 0 0 22 1d 6b 53 22 1d 6b 53 0 0 0 .....".kS".kS... Free Command: 34 FindCls Error class: 0 Error: 0 Flags: 88 RESPONSE UID: 4000 MID: 794b UID: 4000 PID: fa Data: 0 0 0 0 a 0 b3 10 0 0 0 0 0 0 0 0 ................ 0 0 17 0 44 0 0 0 0 0 1 0 1 0 1a 0 ....D........... 0 0 0 37 0 64 0 4 0 1 0 0 0 0 0 5c ...7.d.........\ 54 6f 6f 6c 73 5c 2a 0 0 0 0 0 0 0 0 0 Tools\*......... 0 0 0 0 0 1d 1d 29 5a 1d 1d 29 5a 0 0 0 .......)Z..)Z... Free Command: 71 tdisc Error class: 0 Error: 0 Flags: 8 REQUEST UID: 4000 MID: 79cd UID: 4000 PID: 10 Data: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0 0 0 0 0 0 0 0 14 1d 64 7f 14 1d 64 7f ..........d..d 0 0 0 0 0 0 0 0 10 0 1 2e 0 0 0 0 ................ 0 0 0 0 0 21 1d 58 90 21 1d 58 90 0 0 0 .....!.X!.X... >>>some sample output text deleted here No open files. Network Drive Information Drive K information follows: Serial Num: 5 Active Cnt: 1 Device uses: 1 Total uses: 1 Tree id: f804 UID: 1003 Time Dormant: 2e60baaf Remote name: \\MICKEY\D$ Server drive type: HPFS386 IBM LAN Redirector debug information returned successfully *************************************************************************** 21.0 REMOTEFS *************************************************************************** _________________ 21.1. Description REMOTEFS (Mobile File Synch) provides a caching front-end for distributed file systems that are designed to support mobile users. Users can disconnect from their file servers (unplug their laptops) and continue to work on files that are cached on their laptops. This application requires at least 4.6MB for installation. __________________ 21.2. Installation NOTE: To use Mobile File Synch, you must have the OS/2 LAN Requester GUI installed. The actual icon title is "LAN Server Administration." 1. If you don't already have a temporary directory on your hard disk, create one. This procedure assumes that it is C:\TMP. mkdir TMP 2. Change to the TMP subdirectory. cd TMP Be sure Productivity Aids Diskette 4 is in the A: drive before performing step 3. 3. Copy REMOTEFS.ZIP from Productivity Aids Diskette 4 to the temporary directory. copy a:remotefs.zip 4. Remove Productivity Aids Diskette 4 from the A: drive. 5. Put a blank, formatted, high-density ("2.0" MB) into the A: drive. 6. Run pkunzip2.exe to unzip the REMOTEFS.ZIP file from your temporary directory to create an installation diskette. pkunzip2 remotefs.zip a: 7. Label your installation diskette MARS1. If you do not do this, the installation program will not work. label a: 8. At the OS/2 command line, invoke the INSTALL command for MARS. a:install 9. Follow the instructions on your screen. Some tips: a. On the panel that asks whether you want the installation program to change CONFIG.SYS, make sure that the box has a check mark. b. On the panel that asks where you want your directories, be aware the list box actually contains five directory names, but you can see only three at once. c. At the end of install, just select (click on) the Exit button. 10. Before you run Mobile File Synch, you must reboot. For information on how to run Mobile File synch, see the README file in the MARS\DOC subdirectory (or whatever you chose to call it.) *************************************************************************** 22.0 REMUSER *************************************************************************** _________________ 22.1. Description REMUSER removes a user account, its logon profiles, and home directory. ____________ 22.2. Syntax The Syntax of REMUSER is: REMUSER [/Y] Don't include the '<' or '>' marks The optional /Y suppresses confirmation questions NOTE: If you execute this command remotely with the NET ADMIN command, then you must include the command in quotes so the command parser does not drop the /Y. __________________ 22.3. Installation 1. Create a subdirectory with an appropriate name. A suggested name would be REMUSER. md dir_name 2. Change to the created subdirectory. cd dir_name NOTE: Be sure Productivity Aids diskette 2 is in the A: drive before performing step 3. 3. Run pkunzip2.exe in order to unzip the REMUSER.ZIP file on Productivity Aids diskette 2. pkunzip2 a:remuser.zip *************************************************************************** 23.0 REPLINI *************************************************************************** The Replicator Configuration utility sets or clears the Replicator service or the DCDB Replicator service. *************************************************************************** 24.0 RPLADD *************************************************************************** __________________ 24.1. Introduction The RPLADD program can be used to create LAN Server Version 4.0 remote IPL client definitions from an OS/2 command line. The files included in this package are: * RPLADD.EXE - Executable program * RPLADD.FIL - Sample input file * RPLADD.DOC - This README document * RPLADD.ICO - Icon file __________________ 24.2. Using RPLADD RPLADD can be used to create remote IPL definitions from any OS/2 workstation within the same domain. The local workstation and the target remote IPL server must both be running LAN Server Version 4.0. The local workstation must be logged on with administrator level privilege. The target remote IPL server must have the Server service started, but does not require that the Remoteboot service be started. _____________________________ 24.3. Command Line Parameters Required Parameter: /F:input_filename Specifies the path and file name of the source input file containing the formatted records that will be used as input to the RPLADD.EXE program. See the INPUT FILE FORMAT section of this document for an explanation of the input file format. Optional Parameters: /O:output_log_filename Specifies the path and file name of an ouput log file that will be used to record all output from the RPLADD.EXE program. If this parameter is specified, all output that would normally be displayed on the display will be redirected to a file. /Debug Specifies to display additional debug information about the execution of the RPLADD.EXE program. This parameter can be useful for displaying information about the parameters that are parsed from the input file. _______________________ 24.4. Input File Format RPLADD.EXE requires an input file containing formatted records. A sample input file, RPLADD.FIL, is supplied with this program. Below is a brief description of the input file format. PARAMETER 1 = CREATE TYPE CREATE TYPE = 2 Is specified to create a new machine definition and will inherit the default machine configuration. CREATE TYPE = 12 Is specified to create a new machine from an existing model machine definition. The new machine will inherit all of the configuration files from the model machine definition. The new machine and the model machine must exist on the same server. PARAMETER 2 = NAME The name of the new remote IPL machine definition. The machine name must be a unique name within the Domain. DOS remote IPL machine names cannot exceed 8 bytes in length. Machine names defined on a server with a FAT file system cannot excced 8 bytes in length. PARAMETER 3 = ADAPTER ADDRESS The ADAPTER ADDRESS is the 12 character universal adapter address of the remote IPL machine. PARAMETER 4 = SERVER RECORD IDENTIFIER The SERVER RECORD IDENTIFIER specifies the operating system plus network adapter type configuration information. The SERVER RECORD IDENTIFIER specified must exist as an enabled server record identifier on the remote IPL server. OS/2 PARAMETER 5 = OS/2 DRIVE (OS/2 PARAMETER ONLY) The OS/2 DRIVE specifies the boot drive letter for the OS/2 remote IPL machine. NOTE: USE THIS PARAMETER FOR OS/2 MACHINE DEFINITIONS ONLY! OS/2 PARAMETER 6 = OS/2 CONFIG (OS/2 PARAMETER ONLY) The OS/2 CONFIG parameter is used to specify OS/2 configuration parameters for the OS/2 remote IPL machine. A combination of 3 flags are to be specified, one from each of the 3 catagories. SWAPPER.DAT LOCATION L = SWAPPER.DAT file located on remote IPL machine hard disk S = SWAPPER.DAT file located on server hard disk BUS ARCHITECTURE I = ISA bus architecture M = Microchannel bus architecture DISPLAY TYPE 3 = S-3 Super VGA display 8 = 8514 display E = EGA display U = Super VGA display(non S-3) V = VGA display X = XGA display NOTE: USE THIS PARAMETER FOR OS/2 MACHINE DEFINITIONS ONLY! DOS PARAMETER 5 = DOS IMAGE (DOS PARAMETER ONLY) The DOS IMAGE specifies the DOS image file for the remote IPL machine. The DOS image file must exist on the target server before the DOS remote IPL machine can be defined. Do not specify a file name extention for the DOS IMAGE parameter. NOTE: USE THIS PARAMETER FOR DOS MACHINE DEFINITIONS ONLY! FINAL PARAMETER = SERVERNAME (Optional) The SERVERNAME is the name of the target server where the remote IPL machine will be created. The server name specified must exist within the same domain as the machine where RPLADD is being run. The SERVERNAME parameter is optional if the remote IPL machines are to be created on the same machine where RPLADD is being run. Below are sample input lines... ;CREATE NAME ADAPTER SERVER RECORD OS/2 OS/2 DOS [SERVERNAME] ;TYPE ADDRESS IDENTIFIER DRIVE CONFIG IMAGE (Optional) ;------ -------- ------------ ------------- ----- ------ -------- ------------ 2 OS2_MACH 10005A111111 R_21_OTK Z LMV 2 DOS_MACH 10005A222222 R_DTK STD3HFUL ;CREATE NAME ADAPTER MODEL [SERVERNAME] ;TYPE ADDRESS NAME (Optional) ;------ ------------- ------------ ------------ ------------ 12 NEW_MACH 10005A333333 MODEL_MACH RIPL_SERV The results expected from each line above are... A remote IPL definition for OS2_MACH will be created on the local server. OS2_MACH will be defined as an OS/2 remote IPL machine and will be created from the R_21_OTK standard configuration files. OS2_MACH will boot from drive letter "Z:" and will be configured for a local SWAPPER.DAT file, microchannel bus architecture and VGA display. A remote IPL definition for DOS_MACH will be created on the local server. DOS_MACH will be defined as a DOS remote IPL machine and will be created from the R_DTK standard configuration files. DOS_MACH will boot using the STD3HFUL DOS image file. A remote IPL definition for NEW_MACH will be created on RIPL_SERV server. NEW_MACH will inherit all the configuration information of MODEL_MACH. NEW_MACH and MODEL_MACH will exist on the same remote IPL server. *************************************************************************** 25.0 RPLDEL *************************************************************************** __________________ 25.1. Introduction The RPLDEL program can be used to delete LAN Server Version 4.0 remote IPL client definitions from an OS/2 command line. The files included in this package are: * RPLDEL.EXE - Executable program * RPLDEL.FIL - Sample input file * RPLDEL.DOC - This README document * RPLDEL.ICO - Icon file __________________ 25.2. Using RPLDEL RPLDEL can be used to delete remote IPL definitions from any OS/2 workstation within the same domain. The local workstation and the target remote IPL server must both be running LAN Server Version 4.0. The local workstation must be logged on with administrator level privilege. The target remote IPL server must have the Server service started, but does not require that the Remoteboot service be started. _____________________________ 25.3. Command Line Parameters Required Parameters: /F:input_filename Specifies the path and file name of the source input file containing the formatted records that will be used as input to the RPLDEL.EXE program. See the INPUT FILE FORMAT section of this document for an explanation of the input file format. Optional Parameters: /O:output_log_filename Specifies the path and file name of an ouput log file that will be used to record all output from the RPLDEL.EXE program. If this parameter is specified, all output that would normally be displayed on the display, will be redirected to a file. /Debug Specifies to display additional debug information about the execution of the RPLDEL.EXE program. This parameter can be useful for displaying information about the parameters that are parsed from the input file. _______________________ 25.4. Input File Format RPLDEL.EXE requires an input file containing formatted records. A sample input file, RPLDEL.FIL, is supplied with this program. Below is a brief description of the input file format. PARAMETER 1 = NAME The name of the remote IPL machine definition to be deleted. PARAMETER 2 = SERVERNAME (Optional) The SERVERNAME is the name of the target server where the remote IPL machine will be deleted. The server name specified must exist within the same domain as the machine where RPLDEL is being executed. The SERVERNAME parameter is optional if the remote IPL machines are to be deleted on the same machine where RPLDEL is being run. Below are sample input lines... ;NAME [SERVERNAME] (Optional) ;----------- ------------ RPL_MACH1 RPL_MACH2 RIPL_SERV The results expected from each line above are... * A remote IPL definition for RPL_MACH1 will be deleted on the local server. * A remote IPL definition for RPL_MACH2 will be deleted on RIPL_SERV server. *************************************************************************** 26.0 RPLENUM *************************************************************************** __________________ 26.1. Introduction The RPLENUM program can be used to enumerate LAN Server Version 4.0 remote IPL client definitions from an OS/2 command line. The files included in this package are: * RPLENUM.EXE - Executable program. * RPLENUM.DOC - This README document. * RPLENUM.ICO - Icon file. ___________________ 26.2. Using RPLENUM RPLENUM can be used to enumerate remote IPL definitions from any OS/2 workstation within the same domain. The local workstation and the target remote IPL server must both be running LAN Server Version 4.0. The local workstation must be logged on with administrator level privilege. The target remote IPL server must have the Server service started, but does not require that the Remoteboot service be started. _____________________________ 26.2. Command Line Parameters Required Parameters: There are no required parameters for this program. Optional Parameters: /L:level The optional level parameter can be be used to specify the level of information that is to be returned about the remote IPL machine definitions on a remote IPL server. If no level is specified, the default level is 2, which returns all the information about the remote IPL machine definitions. /L:0 - returns names of remote IPL machine definitions /L:1 - returns names and remarks of remote IPL machine definitions /L:2 - (DEFAULT LEVEL) returns all information about remote IPL machine definitions /T:type The optional type parameter can be be used to specify the type of remote IPL machine definitions to be returned from a remote IPL server. If no type is specified, the default type is ALL, which returns all the information about the remote IPL machine definitions. /T:DOS - returns DOS remote IPL machine definitions only /T:OS2 - returns OS/2 remote IPL machine definitions only /T:ALL - (DEFAULT TYPE) returns ALL remote IPL machine definitions /O:output_log_filename This optional parameter specifies the path and file name of an ouput log file that will be used to record all output from the RPLENUM.EXE program. If this parameter is specified, all output that would normally be displayed on the display, will be redirected to a file. /S:server This optional parameter specifies the name of the remote IPL server from where the remote IPL machine definitions will be retrieved. If specified, the server name parameter must be entered as the server name only, (example: RIPL_SERV). Do not specify the UNC server name (example: \\RIPL_SERV). *************************************************************************** 27.0 RPLFDISK *************************************************************************** __________________ 27.1. Introduction The RPLFDISK program can be used to enable or disable the hard disk on an OS/2 remote IPL machine. The files included in this package are: * RPLFDISK.EXE - Executable program. * RPLFDISK.DOC - This README document. ____________________ 27.2. Using RPLFDISK RPLFDISK can be used to enable or disable the hard disk on an OS/2 remote IPL machine. The remote IPL machine does not require any network services to be running. The RPLFDISK program can be executed from any OS/2 command prompt. The RPLFDISK.EXE file should be copied into a directory that is in the \\rpl_server\RPLFILES share directory tree so that the OS/2 remote IPL machines will have access to the file. If you are not certain where the RPLFILES share is located on your remote IPL server, you can use the NET SHARE command on the remote IPL server to determine the location of the share. The recommended target directory is d:\IBMLAN\RPL\IBMLAN\NETPROG, where d: is the remote IPL server drive letter where the IBMLAN\RPL directory tree was installed. _____________________________ 27.3. Command Line Parameters Required Parameters: The RPLFDISK program requires ONE of the following parameters /D This parameter is specified to disable remote IPL boot from the network adapter. If the hard disk contains a bootable partition, the machine will now boot from the local hard disk. /E This parameter is specified to enable remote IPL boot from the network adapter. If the hard disk contained a bootable partition, the partition will be marked as non-bootable. /S This parameter is specified to display the current status of the fixed disk. *************************************************************************** 28.0 RPLSRID *************************************************************************** __________________ 28.1. Introduction The RPLSRID program can be used to enumerate LAN Server Version 4.0 remote IPL server record identifiers from an OS/2 command line. The files included in this package are: * RPLSRID.EXE - Executable program. * RPLSRID.DOC - This README document. * RPLSRID.ICO - Icon file. ___________________ 28.2. Using RPLSRID RPLSRID can be used to enumerate remote IPL server record identifiers from any OS/2 workstation within the same domain. The local workstation and the target remote IPL server must both be running LAN Server Version 4.0. The local workstation must be logged on with administrator level privilege. The target remote IPL server must have the Server service started, but does not require that the Remoteboot service be started. _____________________________ 28.3. Command Line Parameters Required Parameters: There are no required parameters for this program. Optional Parameters: /O:output_log_filename This optional parameter specifies the path and file name of an ouput log file that will be used to record all output from the RPLSRID.EXE program. If this parameter is specified, all output that would normally be displayed on the display, will be redirected to a file. /S:server This optional parameter specifies the name of the remote IPL server from where the remote IPL server record identifiers will be retrieved. If specified, the server name parameter must be entered as the server name only, (example: /S:RIPL_SERV). Do not specify the UNC server name, (example: /S:\\RIPL_SERV). *************************************************************************** 29.0 SMBTOOL *************************************************************************** IBM LAN Server SMB Tracing Tool, Version 1.1 (C) Copyright IBM Corporation 1994. All rights reserved. __________________ 29.1. Introduction The SMBTOOL utility can be used to capture various types of network traces. Especially important is its ability to capture IBM LAN Server server message block (SMB) information. It also includes extensive formatting and filtering features for SMB trace data. It can be used for advanced problem determination. The utility takes no parameters and requires OS/2 2.1 or higher. More information is available by selecting HELP from within the utility. This utility can also analyze various types of binary network trace data and translate SMB information if present. *************************************************************************** 30.0 SNAPDF *************************************************************************** __________________ 30.1. Introduction SnapDump/2 includes a program (SNAPDF.EXE) which provides a Presentation Manager interface useful for viewing and formatting the contents of a file that contains the data collected by SnapDump/2. The formatting program provides three views of the data: * Hexadecimal plus ASCII * Hexadecimal plus EBCDIC * ASCII only The SnapDump/2 formatter can also be used to extract data from the SnapDump/2 output file, returning it to its original binary format. This is particularly useful for binary files that require specialized tools or programs to view them in a meaningful way (for example, the Communications Manager configuration file). The binary file can be extracted from the dump file and stored as an individual file in its original binary format. Because each data item collected in the dump file is tagged with an entry title, it is very easy to select a specific data item for display. It is not necessary to display the entire dump file. ____________ 30.2. Syntax The syntax of the SNAPDF command follows: __SNAPDF__________________| |_dump-fname_| | where: dump-fname Specifies the name of the SnapDump/2 output file. If this parameter is not supplied the SNAPDF program looks for the default output file SNAPDUMP.DMP. ___________________________ 30.3. Dump Formatter Window The SNAPDF command displays the Dump Formatter window from which you can select data to be displayed. If no output file is found, the SNAPDF command displays a standard Open File window, from which you can select the output file name. NOTE: Maximize the window to display all the fields. The Dump Formatter window has the following fields: * Output File Name This is first field in the window. It displays the name of the SnapDump/2 output file specified in the SNAPDF command. * Dump Segment Identifier This is the second field in the window. It displays all the data entries (segments) in the output file. Scroll the list by selecting the down arrow to the right of the field. Select (highlight) the segment you want. NOTE: Segmentation only occurs after approximately 300 data entries are collected. * Date, Time, and Program This is the third field in the window. It displays the date and time at which the dump file was created and the program that created the dump file. * Data Item This is the fourth field in the window. It displays the currently selected data item for the selected segment. Scroll the list by selecting the down arrow to the right of the field. Select (highlight) the data item you want. When you have completed the fields, press Enter (or double-click on the selected data item) to display the data. By pressing F12, you can change the format of the data display to one of the following: * Hexadecimal plus ASCII * Hexadecimal plus EBCDIC * ASCII only Helpful menu bar selections in the Dump Formatter window include: File, Save as Enables you to save a data item in a file in the format you want. File, Open Enables you to open a new output file for display without having to start over at the command prompt. This is useful when multiple SnapDump/2 output files are to be viewed. *************************************************************************** 31.0 SNAPDUMP *************************************************************************** IBM Snapdump/2 Data Collector and Formatter (C) Copyright IBM Corporation 1994. All rights reserved. __________________ 31.1. Introduction SnapDump/2 is a set of tools that assists with problem determination in the OS/2 environment. SnapDump/2 provides the ability to capture a wide variety of system data into a single, easily transportable file. The collection of data is controlled by the contents of a tailorable flat ASCII file. Although a sample version of this file is shipped with SnapDump/2 (SNAPDUMP.DAT), this ASCII file can be easily modified by support personnel to customize the collection of data. In addition, SnapDump/2 provides an easy-to-use menu interface for displaying the contents of the output file that contains the system data collected by SnapDump/2. See 12.0 SNAPDF for more information about this interface. This tool is an IBM Reliability, Availability, and Serviceability (RAS) tool developed by IBM United States Software Services. _____________________ 31.2. Data Collection SnapDump/2 includes a program (SNAPDUMP.EXE) that provides the ability to collect many types of data. The data collected falls into the following categories: * Files (binary and ASCII) * Data areas contained in named shared segments * Standard output and standard error from programs invoked by SnapDump/2 * Environmental information automatically collected by the SnapDump/2 data collection program * The system trace buffer (if the system trace is active) When SnapDump/2 scans for files, it searches all accessible drives, including shared drives on servers and diskette drives. Multiple instances of a file are collected, if they exist. ___________________________ 31.3. Operating Environment There are no special requirements, other than OS/2. SnapDump/2 operates in the following environments: * Standard Edition 1.2 through Standard Edition 2.0 * Extended Edition 1.2 through Extended Edition 1.30.2 * Standard Edition 1.30.1 (including Extended Services) * Standard Edition 1.30.2 (including Extended Services and LAN Server 2.0) ____________________________ 31.4. The SnapDump/2 Package SnapDump/2 consists of the following files: SNAPDUMP.EXE The data collection program SNAPDF.EXE The data formatter program SNAPDUMP.DAT Sample ASCII input file for the collection program SNAPDUMP.INF Online documentation for SnapDump SNPNL001.HLP Help file for SnapDump QMC.EXE Qsystem program to display hardware information FINDSEG.EXE Program to display segment information NETSESS2.EXE Local LAN session statistical and status DIRSTAT.EXE 802.2 adapter level information NCBSTAT.EXE NetBIOS status information SNAPDUMP.DOC SnapDump/2 documentation ___________________________ 31.5. Installing SnapDump/2 These installation instructions assume that you are familiar with using the OS/2 command line and that you wish to create a separate directory on the C drive for SnapDump/2. You may substitute a different drive letter and directory name or omit steps where appropriate. 1. Download the SNAPDRIV EXEBIN file. 2. Install using one of the following methods: * Method 1: a. Create a directory for SNAPDUMP (for example: MKDIR SNAPDUMP). b. Enter the following command: SNAPDRIV -d -o C:\XXXXXXXX This command places the .EXE file in the XXXXXXXX directory. * Method 2: a. Place SNAPDUMP in the OS2\SYSTEM directory. b. Enter the following command: SNAPDRIV -d -o c:\OS2\SYSTEM This command places the .EXE file in the OS2\SYSTEM directory. ____________ 31.6. Syntax The syntax of the SNAPDUMP command follows: __SNAPDUMP____________________________________| |_input-fname_________________| | |_dump-fname__| where: input-fname Is the name of the flat ASCII file that contains the list of files, data, and programs to be processed by SnapDump/2. If this parameter is not specified, the input file name defaults to SNAPDUMP.DAT. dump-fname Is the name of the file into which SnapDump/2 writes all the captured data. In this document, it is also called the SnapDump/2 output file. If this parameter is not specified, the input file name defaults to SNAPDUMP.DMP. ___________________________ 31.7. SnapDump/2 Input File The SnapDump/2 input file controls the information to be captured in the SnapDump/2 output file. The SnapDump/2 input file can be edited with any ASCII editor, including the OS/2 system editor. The following describes the types of information that can be captured and how they are to be specified in the flat file. * A 'f/' in column 1 indicates that a file is to be captured. For example: f/config.sys When a file is captured, the contents of the file are appended to the SnapDump/2 output file. Wildcards may be specified, but be aware that the SnapDump/2 output file may become very large if the wildcard specification is too broad. Note that files that are in-use, such as the Communications Manager MESSAGE.DAT and ERROR.DAT files, are collected by SnapDump/2. * A 'p/' in column 1 indicates that the specified program is to be invoked. For example: p/c:\qmc.exe -d Any programs (including .CMD files) that can be run from the OS/2 command prompt and that write to standard output and/or standard error files may be specified. The standard output and/or standard error output of the program is appended to the SnapDump/2 output file. The output of programs that use other techniques of writing to the screen, such as Presentation Manager Win calls or VIO calls, cannot be captured by SnapDump/2. * A 'm/' in column 1 indicates that a named shared memory segment (\SHAREMEM\...) is to be captured. For example: m/\SHAREMEM\ACS\RAS_SEG The contents of the named shared segment are appended to the SnapDump/2 output file. Wildcards for named shared memory are not allowed. Certain named shared memory segments are protected and cannot be dumped. The names of the named shared memory files in the system may be obtained by issuing the following command at the command prompt: pstat /m * Any other value in column 1 causes the line to be treated as a comment. If the system trace is active, the system trace buffer is automatically captured by SnapDump/2 and appended to the SnapDump/2 output file. __________________________________ 31.8. Sample SnapDump/2 Input File The following SnapDump/2 input file is shipped with SnapDump/2 and can be modified as required: *This is a sample file to show SnapDump/2 Capability. Most *of the entries have been deactivated (* in first column) to *reduce size of the output file. *File names and paths will differ with OS/2 release level. *The user may customize as needed. * * OS/2 information * f/config.* f/syslevel.* f/startup.cmd f/*.ini *f/os20001.dat *f/log0001.dat * * FFST/2 files * *f/epw.ini *f/snapdump.dat *f/os2mlog.dat *p/dir c:\os2\system\*.dmp * * Communication Manager * *p/display.exe *f/*.cfg *f/*.ndf *f/*.sec *f/*.cf2 *f/error.dat *f/message.dat *f/esinst.hst *f/acs.pro f/acslan.log f/lantran.log *f/c2instal.log *f/install.log *f/message.log *f/custbld.hst *f/cmfeater.dat *m/\sharemem\acs\ras_seg * * Database Manager * *f/sqldbdir *f/sqlsystm *f/sqldbcon *f/sqluif.* *f/sqlnodir *f/sqlgwdir *f/sqlogctl.lfh *f/dbdrqlib.cfg * * LAN Server 2.0 * *f/net.err p/net error *f/net.acc *f/net.aud * * LAN status command * *p/net statistics requester *p/net statistics server *p/net config requester *p/net config server *p/net files *p/net sessions *p/net share *p/net status *p/net view *p/net who * * Workstation Status Programs * *p/netsess2.exe *p/ncbstat.exe * p/dirstat.exe *p/findseg -S C:\ p/qmc.exe -d p/pstat.exe * *Adapter Shared Ram Dump for OS/2 Extended Edition *Version 1.3 (device driver TRADUMP.SYS required) * *p/tradump /f * *Adapter Shared Ram and NetBIOS Dump for OS/2 version 2.0 *with LAPS (Lan Adapter and Protocol Support) * *p/lapsdump /f (will be provided by 5/1/92) * ____________________________ 31.9. SnapDump/2 Output File At the completion of a SNAPDUMP command, the output file name is displayed. SnapDump/2 output files should be directed to a drive with enough free disk space. The drive may be a network drive, a local hard disk drive, a floppy drive, or a virtual disk drive. _________________________________________ 31.10. Displaying SnapDump/2 Output Files Use the SnapDump/2 Formatter (SNAPDF) to display SnapDump/2 output files. ___________________________________________ 31.11. Transporting SnapDump/2 Output Files If the SnapDump/2 output file is too large to fit on a single diskette (even after packing it), the Backup function provided with OS/2 can be used to store a very large file on multiple diskettes. Conversely, the Restore function provided with OS/2 can be used to restore the diskette-spanning information into a single file. The SnapDump/2 output file can be sent to a central support location for diagnostic assistance. When using the file transfer capabilities of OS/2 Communications Manager to send the output file to a host, ensure that the record format and characteristics of the host computer file are set to 'variable'. * If you are using the OS/2 command line to enter the SEND command for file transfer, use the RECFM V option. For example: SEND C:OUTPUT.DMP A:OUTPUT DUMP A (RECFM V * If you are using OS/2 Communications Manager File Transfer Profiles to send the output file; (1) under 'Modify host file characteristics options', select - Yes; (2) under 'Record format of host file', select - Variable. _____________________________ 31.12. Support for SnapDump/2 31.12.1. Usage Support. Usage support, for Customers and SEs, is provided through EQUAL/ASKQ. Keyword for entries should be "SNAPDUMP". 31.12.2. Defect Support. Defect support for SnapDump/2 is handled through SNAPDUMP FORUM on IBMPC, which is monitored. Defect will be answered within 2 weeks. __________________________________ 31.13. SnapDump/2 Utility Programs Any programs that provide useful problem determination information, or status, are candidates for use with SnapDump/2. The following programs may be of use to you, and are installed with SnapDump/2: QMC.EXE Displays hardware information FINDSEG.EXE Displays segments NETSESS2.EXE Displays session statistical and status DIRSTAT.EXE Exhibits adapter information NCBSTAT.EXE Displays NetBIOS information The following program is provided with Extended Services for OS/2. To install this program, you must install the Communications Manager Utilities found on the Additional Features panel during initial installation (ESINST) or reinstallation (REINST). See the 'Extended Services Communications Manager Command Reference' for more information about using this program. DISPLAY.EXE Displays the active SNA configuration The following program is provided with the OS/2 operating system. PSTAT.EXE Displays system information ______________ 31.14. Example An end user with a software problem needs to be able to easily capture all the problem related information requested by support personnel. This information is dispersed throughout the end user's system and, without SnapDump/2, requires a lot of work by the end user to locate and gather it all up to send to the support personnel. SnapDump/2 can capture the files needed by the support team. Example: A customer who is running IBM OS/2 ES Communications Manager changes the STARTUP.CMD to use a different configuration file. The next day the customer starts the PS/2 and finds Communications Manager is not running the same as the day before. The customer, forgetting he had changed configuration files, calls the Level 2 support team. The Level 2 support team requests a list of 8 files in different directories that the customer must find, copy, and send. The customer runs SnapDump/2, which collects all the files plus the configuration file from the day before. The Level 2 support team is able to find the changes in the two configuration files and then inform the customer. This is one of the ways SnapDump may help perform problem determination. ************************************************************************* **** END OF FILE **** *************************************************************************