mmsdemo.txt

ICCP Toolkit 是在 Tru64下开发Tase.2通信协议的开发包

                                    MMS-EASE

                      Demonstration Software Documentation







             (C) Copyright 1986 - 2002.  All Rights Reserved By:



                              S I S C O   I N C. 

                 Systems Integration Specialists Company, Inc.
              6605 19 1/2 Mile Road Sterling Heights, MI  48314-1408
                     Tel: [phone], Fax: [phone]
	     E-mail: [e-mail], URL:http://www.sisconet.com














                        
                           
                           
                           
                           
                           



                                                       
TABLE OF CONTENTS

  1.  WHAT SYSTEM FILES ARE NEEDED
  2.  MAIN MENU
  3.  HINTS ON MENU NAVIGATION
  4.  CONTEXT MANAGEMENT MENU (F1 FROM MAIN MENU)
  5.  VMD SUPPORT MENU (F2 FROM MAIN MENU)
  6.  VMD MANAGEMENT MENU (F7 FROM VMD SUPPORT MENU)
  7.  DOMAIN MANAGEMENT OPERATIONS (F3 FROM MAIN MENU)
  8.  DOMAIN UPLOAD/DOWNLOAD (F1 FROM DOMAIN MANAGEMENT MENU)
  9.  PROGRAM INVOCATION MANAGEMENT MENU (F4 FROM MAIN MENU)
 10.  VARIABLE ACCESS (F5 FROM THE MAIN MENU)
 11.  TYPE/NAME DEFINITION MENU (F4 FROM VARIABLE ACCESS MENU)
 12.  LOCAL NAMED TYPE MENU (F6 FROM VARIABLE ACCESS MENU)
 13.  LOCAL NAMED VARIABLE MENU (F7 FROM VARIABLE ACCESS MENU)
 14.  FILE OPERATIONS MENU (F6 FROM MAIN MENU)
 15.  FILE MANAGEMENT MENU (F9 from the FILE OPERATIONS MENU)
 16.  OPERATOR COMMUNICATION OPERATORS MENU(F9 FROM MAIN MENU THEN F2)
 17.  EVENT MANAGEMENT OPERATIONS MENU (F9 FROM MAIN MENU THEN F3)
 18.  JOURNAL MANAGEMENT OPERATIONS MENU (F9 THEN F4 FROM MAIN MENU)
 19.  MISCELLANEOUS MENU (F9 then F5 FROM THE MAIN MENU)
 20.  SETTING THE MMS DEBUG LEVELS (F3 FROM THE MISCELLANEOUS MENU)
 21.  MODULE NAMES AND DESCRIPTIONS
                                                      
                             
                               
                               
                            N O T I C E




THIS DEMONSTRATION SOFTWARE IS NOT FOR RESALE.  THE CONTENTS OF THIS
FILE AS WELL AS THE DEMONSTRATION SOFTWARE ITSELF ARE COPYRIGHTED AND
WHOLLY OWNED BY SISCO.  NO SALE OR TRANSFER OF THIS SOFTWARE OR THIS 
DOCUMENTATION IS CONSIDERED TO BE A TRANSFER OF OWNERSHIP OF THIS 
SOFTWARE.  THIS DEMONSTRATION SOFTWARE IS LICENSED TO YOU AT NO COST
AND THE LICENSE CAN NOT BE TRANSFERRED WITHOUT THE EXPRESS WRITTEN
CONSENT OF SISCO.





     PLEASE OBSERVE THE FOLLOWING PRIOR TO ATTEMPTING TO RUN THE
     DEMONSTRATION SOFTWARE:


    a.  UNIX: THE TERMINAL YOU RUN THIS SOFTWARE FROM MUST BE ANSI COMPATIBLE.

    b.  YOU MUST HAVE AT LEAST SOME KNOWLEDGE OF MMS AND MMS-EASE IN
        ORDER TO EFFECTIVELY USE THIS SOFTWARE.
        IT IS HELPFUL TO READ AND UNDERSTAND THE MMS-EASE REFERENCE MANUAL.

    c.  PLEASE READ AND UNDERSTAND THIS DOCUMENTATION FULLY BEFORE
        ATTEMPTING TO RUN THIS SOFTWARE.

    See the MMS-EASE Installation Guide and Release Notes for more information
    on the MMS-EASE configurations.

             

1. WHAT SYSTEM FILES ARE NEEDED

     The specific setup needed by MMS-EASE demo program is different from
     computer system to computer system.  However, all systems generally
     need the following information to be resident somewhere on the system,
     be it a file on the local computer, information in a network manager,
     etc.:
     
               a.    The Directory Information Base (DIB).
               b.    The Demo Configuration File.
               c.    The Logging Configuration File.
              
     
     a. THE DIRECTORY INFORMATION BASE (DIB).
     
     On UNIX systems the DIB file (osill2.cfg) is located in the following
     directory:
       on Tru64 UNIX:	/usr/osill2/cfg
       on AIX:		/usr/lpp/osill2/cfg
       on Sun:		/usr/osill2/cfg
       on HP-UX:	/opt/osill2/cfg
     On Windows a GUI configuration utilities is used to configure the communication
     parameters:
       Start\Programs\SISCO\SISCO OSI Stack\STack Configuration or 
       Start\Programs\SISCO\AX-S4 MMS\AX-S4 MMS Configuration Utility.

     See the MMS-EASE Installation Guide for more configuration information.

     b. THE DEMO CONFIGURATION FILE (mmsdemo.cfg)

     NOTE:     THE DEMO CONFIGURATION FILE (MMSDEMO.CFG) IS ONLY NECESSARY FOR
               THE DEMONSTRATION PROGRAMS SUPPLIED WITH MMS-EASE.  YOUR
               PROGRAMS MAY DECIDE TO IMPLEMENT THE CONFIGURATION IN A
               DIFFERENT MANNER.  THE DEMO CONFIGURATION FILE DESCRIBED
               HERE IS NOT ACCESSED IN ANY WAY BY THE MMS-EASE SPECIFIC
               LIBRARIES, ONLY BY THE DEMONSTRATION APPLICATION
               ITSELF.  CONSULT THE SOURCE CODE FOR THE DEMONSTRATION
               APPLICATION THAT WAS INCLUDED WITH YOUR MMS-EASE FOR MORE
               DETAILS ON HOW THIS FILE IS READ IN AND USED.
     
     When using the demo program you must create a file named mmsdemo.cfg
     which tells the demo program what AR Names to activate, what AR Names
     to register to which channels and which channels should be listening.
     The mmsdemo.cfg is a text file that you can create using most any text
     or word processor.  
     The mmsdemo.cfg file contains the following information:

               1.    Channel parameters:
               		Number of channels
               		Maximum MMS message size.

               2.    AR Names to be activated.

               3.    AR Names to be registered on which channels.

               4.    Which channels are to be listening.

     NOTE:  In the MMSDEMO.CFG file further described below, a blank line
            or any line beginning with a pound sign ("#") denotes the
            beginning of an entry.  All data following the "#" sign on that
            line is ignored and can be used to enter comments.


     If 2 local AR Names need to be activated and registered on consecutive
     channels, and only channel 0 should be listening, then the following
     mmsdemo.cfg file would result:


                    #1 CHANNEL CONFIGURATION
                    TOTAL_CHAN=2
                    MAX_MSG_SIZE=3000
                    #2 NAMES TO BE ACTIVATED
                    Local1
                    Local2
                    #3 NAMES TO BE REGISTERED ON CHANNELS
                    Local1
                    Local2
                    #4 CHANNELS TO BE LISTENING (CALLED)
                    0
                    #5 END OF FILE

     See the supplied mmsdemo.cfg for example using more channels. The local AR Names
     used in the mmsdemo.cfg file must be configured in the DIB.
     
     c. THE LOGGING CONFIGURATION FILE (mms_log.cfg).

     The provided mmsdemo.cfg allows to configure the logging parameters for
     the demonstration program. See the file for descriptions of parameters.



2. MAIN MENU

     Before the demo program brings up the main menu, few prompts
     appear. Just hit the <RETURN> key to continue program initialization.

     After initialization, the following menu appears:


          +----------------------------------------------+