home *** CD-ROM | disk | FTP | other *** search
-
- +-------------------------------------------------------------+
- | II06915 |
- | COMMUNICATIONS MANAGER/2 1.0 562125400 |
- | |
- | Finding the cause of problems when |
- | using Communications Manager/2 |
- | |
- |LAST UPDATE: 05/26/93 BY: RHB |
- | |
- +-------------------------------------------------------------+
- |
- | 1. 04/22/93 Finding the cause of INSTALLATION problems.
- | 1.1. Check if CM.LOG in OS2 CMLIB exists. If it
- | does then edit or type this file to see the
- | error messages produced during installation.
- | You may need to also check "Communications Manager/2
- | Message Reference" SC316159.
- | 1.2. Check if CMRINST.LOG in OS2 CMLIB exists. If it
- | does then edit or type this file to see the
- | error messages produced during CID processing.
- | 1.3. Check if CM.LOG in CMLIB exists. If it
- | does then edit or type this file to see the
- | error messages, or view this file from the OPTION
- | pulldown of CMSETUP.
- | 1.4. Check the FFST/2 Message log for errors.
- | If FFST/2 was operational at the time of the
- | error. See 6. Checking the FFST/2 Message log.
- | 1.5. Consult the "Communications Manager/2 Workstation
- | Installation Guide" SC316169.
- | 1.6. Consult the README for Communications Manager/2
- | under "OPTIMAL ERROR REPORTING".
- |
- | 2. 04/22/93 Finding the cause of Configuration problems.
- | 2.1. If errors occurred during the verification of
- | the Communications Manager/2 configuration you
- | will be prompted to view the VERIFY.LOG
- | 2.2. Use the CMRECORD command to produce an ASCII
- | file showing the Communications Manager/2
- | Configuration. You can print this file or display
- | it in an OS/2 window while you review error messages
- | CMRECORD <configuration filename>
- | 2.3. Check the FFST/2 Message log for errors.
- | See 6. Checking the FFST/2 Message log.
- | 2.4. Use the Help available on the Configuration
- | panels. Help is available via PF1 in a
- | field or put focus on the field and click
- | on the help button. This will present help
- | for the field. PF2 from a HELP window
- | or HELP in a window will produce general
- | help for the window.
- | 2.5. Consult the IBM "Communications Manager/2
- | Configuration Guide" SC316171.
- |
- | 3. 04/22/93 Finding the cause of problems when
- | migrating a configuration from a
- | previous release to Communications Manager/2.
- | 3.1. Check UPGRADE.LOG using the FFST/2
- | Message Log Formatter to view this file.
- | See 6. Checking the FFST/2 Message log.
- | 3.2. Check the FFST/2 Message log for errors.
- | See 6. Checking the FFST/2 Message log.
- |
- | 4. 04/22/93 Finding the cause of CID problems.
- | 4.1. Check CMRINST.LOG in OS2 CMLIB or CMLIB.
- | Edit or type this file to see the
- | error messages produced.
- | 4.2. Check the FFST/2 Message log for errors.
- | See 6. Checking the FFST/2 Message log.
- |
- | 5. 04/22/93 Finding the cause of other Communications
- | Manager/2 problems.
- | 5.1. Use the CMRECORD command to produce an ASCII file
- | showing the Communications Manager/2 Configuration.
- | You can print this file or display it in an OS/2
- | window while you review error messages.
- | CMRECORD <configuration filename>
- | 5.2. Check the FFST/2 Message log for errors.
- | See 6. Checking the FFST/2 Message log.
- | 5.3. ONLINE help is available. See 9. Checking the
- | ONLINE MESSAGE REFERENCE.
- | 5.4. If you are receiving a OIA MACH___ or COMM
- | error message, press ALT-Q
- | while in an emulator window
- | or chose Emulator Help from the
- | Emulator window pull down in upper left hand
- | corner.
- |
- | 6. 05/26/93 Checking the FFST/2 message log.
- | 6.1. Locate the FFST/2 folder on the OS/2 desk top.
- | 6.2. In the FFST/2 folder, Chose the MESSAGE LOG
- | FORMATTER ICON.
- | If the FFST/2 folder is not on the desktop you may
- | enter MSGLOGF to invoke the Message Log Formatter
- | in an OS/2 window.
- | 6.3. On the OPEN panel,
- | Select the message log you are currently using.
- | The default message log is OS2 SYSTEM OS2MLOG.DAT
- | (on the boot drive). Errors which
- | occurred during Verify or Upgrade of your
- | configuration may be viewed by selecting either
- | VERIFY.LOG or UPGRADE.LOG in the CMLIB directory.
- | Select the desired directory and log, then
- | click on OPEN.
- | 6.4. On the MESSAGE LOG FORMATTER panel, the current
- | System and Communications Manager/2 messages are
- | displayed. Review the message details and
- | then message help for each message.
- | The message at the top is the most recent message.
- | Help can be selected as follows:
- | Place the cursor on the line of the message you
- | would like to see help for, from options pull down
- | select DETAIL ENTRY (or double click on the line).
- | Note the scroll bars, the next button and the
- | previous button, to move the displayed information
- | The message may direct you to other sources of
- | information, such as the System Error Log, FFST/2
- | DUMP formatter, or the Communications
- | Manager/2 Publications, make a note of the
- | PROBE ID, PROBLEM ID, DATE, and TIME.
- |
- | 7. 04/22/93 Checking the SYSTEM ERROR LOG.
- | 7.1 In the FFST/2 folder, chose the SYSTEM ERROR
- | LOG ICON or from the command prompt enter
- | "START SYSLOG".
- | 7.2 ON THE OS/2 ERROR LOG FORMATTER, the most recent
- | error log record is displayed. Chose the error
- | record that matches the PROBLEM ID, PROBE ID, DATE
- | and TIME. Follow the instructions for the message
- | that directed you here. All system error log
- | entries should have a corresponding
- | message entry.
- |
- | 8. 04/22/93 Checking the FFST/2 DUMP FORMATTER.
- | 8.1. In the FFST/2 folder, choose the DUMP
- | FORMATTER ICON or from a command prompt
- | enter "START EPWDF".
- | 8.2 On DUMP FORMATTER/OPEN panel, choose the
- | dump file to open as directed
- | by the message. EPWALERT.DMP is the
- | most common dump file, containing all the
- | alerts for Communications Manager/2.
- | Choose the dump record that matches the
- | PROBE ID, the PROBLEM ID, DATE and TIME.
- | Follow the instructions for the message that
- | directed you here.
- |
- | 9. 04/22/93 Checking the ONLINE MESSAGE REFERENCE.
- | 9.1. In the Communications Manager/2 ICON VIEW folder,
- | choose the MESSAGE REFERENCE ICON,
- | or from a command prompt enter "VIEW CMMSGREF".
- | 9.2. SELECT the message prefix for the message you are
- | interested in or chose SERVICES, SEARCH and enter
- | the message number. Press enter or double
- | click on the messages.
- | This is an ONLINE version of the
- | Communications Manager/2 Message
- | Reference SC316159.
- | 9.3. Or enter HELP <message number> (HELP ACS0619)
- | to have the message information displayed.
- | The Help command will not display messages
- | that end with an I. The I indicates Information
- | Messages. Messages ending with E, Error
- | and ending with W, Warning, are displayed.
- |
- |10. 04/22/93 Other References
- | Check the "Communications Manager/2 Problem
- | Determination Guide" SC316156, especially
- | Chapter 1 "Problem Determination Procedures".
- |
- +-------------------------------------------------------------+
- |KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
- | CMDOC CMPD CMPSI PD PSI PD PSI ERRORS PROBLEMS |
- | MESSAGE MESSAGES LOG LOGS ALERTS |
- | |
- | |
- +-------------------------------------------------------------+
-