home *** CD-ROM | disk | FTP | other *** search
- +-------------------------------------------------------------+
- | II06895 |
- | COMMUNICATIONS MANAGER/2 1.0 562125400 |
- | |
- | Management Services |
- | |
- | Tips, Techniques, Questions and Answers |
- | |
- |LAST UPDATE: 04/16/93 BY: RHB |
- | |
- +-------------------------------------------------------------+
- |
- | 1. 04/16/93 Information on Communications Manager/2
- | Management Services.
- |
- | Network Administration and Subsystem Management
- | Guide SC316168
- | Chapter 1 Communications Manager Features
- | Chapter 2 Communications Manager and SNA
- | Chapter 16 System Management Programming Capabilities
- | System Management Programming Reference SC316173
- | Chapter 1 Introduction, under Management Services Verbs
- | Chapter 2 The Display Verb
- | Chapter 5 Configuration Verbs
- | Chapter 6 Management Services Verbs
- | Appendix D Management Services (MS) Support
- | Appendix E MDS-MUs for Requesting and Reporting
- | System Data
- | Communications Manager/2 Version 1.0 New Features GG243958
- | Chapter 9 SNA Management Services
- |
- | 2. 04/16/93 CMSETUP Installation/Configuration panels and CID
- | do not support the following verbs:
- |
- | DEFINE_DEFAULT_SOC
- | DEFINE_EXPLICIT_SOC
- | DEFINE_REMOTE_FP
- | These verbs and associated parameters will need to be
- | added via editing the <your configuration name>.NDF file,
- | then verifying the changed .NDF file via CMVERIFY.
- | See Chapter 1 Communications Manager Features under
- | Communications Manager Configuration Methods
- | in the Network Administration and Subsystem Management
- | guide SC316168 and Chapter 5 Configuration Verbs
- | in the System Management Programming Reference, SC316173.
- | The APPNV.CTL file in the CMLIB sub-directory also shows
- | the syntax for these verbs.
- |
- | 3. 04/16/93 Why are my Alerts not getting to NetView?
- |
- | a. Verify in error log that Alert (type 0017-00000002) is
- | received correctly by Communications Manager/2.
- | Check for correct Alert formatting of subvectors.
- | Alert dump formatter (EPWALERT.DMP) may help.
- | b. Use PMDSPLAY to display FP status for Alert
- | if FP status = ACTIVE, check that
- | EPWROUT is started and set properly (EPWROUT 1).
- | Then start a Communications Manager/2 Trace
- | to insure Alert is sent.
- | Check for NetView filters that keep Alert from
- | being displayed, See NetView Operation book--DFILTER
- | to display, SRFILTER to set.
- |
- | c. If FP status is INACTIVE &
- | If using SSCP-PU session (NMVT Alerts),
- | DEFINE_LOCAL_CP host_fp_support must be (YES)
- | AND SSCP-PU session must be active
- |
- | d. If FP status is INACTIVE &
- | If using LU 6.2 session (MDS-MU Alerts) then
- | check one of the following 3 items:
- | 1. FOCALPT CHANGE FPCAT=ALERT TARGET=cpname must be
- | issued and accepted at NetView. If not accepted,
- | check that links are active and that NetView
- | LU or implicit inbound PLU
- | support is on at Communication Manager/2.
- | NetView will not reissue the command.
- | 2. DEFINE_REMOTE_FP must be issued at Communication
- | Manager/2.
- | 3. This may be due to delay in acquisition.
- | - 30 seconds after link comes active.
- | - 30 minute automatic retry in case of non-APPN links
- | or unknown time if Communications Manager/2
- | is not responsible for acquisition.
- |
- | 4. 04/16/93 Why am I not a focal point for entry
- | point xxxxxxxx?
- |
- | a. Use PMDSPLAY to display MS information for local
- | focal points.
- | b. Must use .NDF file verbs, SOC program, or entry
- | point definition to establish relationship.
- | d. Focal FP application must be currently registered.
- | e. Session may not be active (inactive links, no
- | LU definitions).
- | f. EP may have higher rank FP.
- | g. Check error log for revoke received (type 0055 ), then
- | EP may have been acquired by another FP
- | or FP loop may have been detected and broken.
- | h. Entry point product may not accept focal point
- | AS/400 pre V2R2 only accepts Alert category.
- | NetView does not accept higher Alert FP (and some
- | other categories).
- | i. May be due to delay in acquisition, as previously stated.
- |
- |
- | 5. 04/16/93 Why do I keep getting xxxxxxxx as my FP?
- |
- | a. Use PMDSPLAY to check retry responsibility and rank
- | for category.
- | b. If FP has retry responsibility,
- | Remove this node from FPs SOC.
- | (Does not have immediate effect) and
- | issue REVOKE_REMOTE_FP for this category
- | (no user interface supplied).
- | c. If EP (local Communications Manager/2 node)
- | has retry responsibility,
- | remove DEFINE_REMOTE_FP from the .NDF file,
- | if it is present. Stop Communications Manager/2 and
- | erase APPCMS.DAT (will remove all categories).
- | Issue REVOKE_REMOTE_FP for this category.
- | If host rank, set DEFINE_LOCAL_CP HOST_FP_SUPPORT (NO).
- |
- |
- +-------------------------------------------------------------+
- |KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
- | FOCAL POINT ENABLEMENT MS APPLICATION |
- | NMVT MS ALERTS ALERT DEFINEREMOTEFP |
- | DEFINEDEFAULTSOC DEFINELOCALCP HOSTFPSUPPORT |
- | DEFINEEXPLICITSOC REVOKEREMOTEFP |
- | DEFINEREMOTEFP |
- | |
- | |
- +-------------------------------------------------------------+
-