Conference azur::mcc

Two questions:

	1) The installation keeps bombing because it can't find logical
	   directory MCC_EXAMPLES.  I have no such logical defined on
           my SSB V1.2 system.  Where should it point?

	2) The only requirements listed indicate SSB V1.2.  Does this
	   also require the Developers Toolkit?  If so, it is unclear
	   from the description that this is a requirement.

	   I would assume from the reading of the accompanying material
	   that the Toolkit is not involved?

Thanks,
Al

RE: .0

>	1) The installation keeps bombing because it can't find logical
>	   directory MCC_EXAMPLES.  I have no such logical defined on
>           my SSB V1.2 system.  Where should it point?
>
>	2) The only requirements listed indicate SSB V1.2.  Does this
>	   also require the Developers Toolkit?  If so, it is unclear
>	   from the description that this is a requirement.
>
>	   I would assume from the reading of the accompanying material
>	   that the Toolkit is not involved?


                The painful itch of an installation procedure.

  >>> 1 <<<

  The MCC_EXAMPLES directory for VMS is located at:

	sys$common:[syshlp.examples.mcc]

  This directory *is* created by the Toolkit installation.  As a workaround,
  you can create this directory and a system logical pointing to it:

	$ def/sys/exe mcc_examples sys$common:[syshlp.examples.mcc]


  The next release of the Script AM will ask where you want the template
  MSL files and create the directory if you do not already have it.  The
  default will be sys$common:[syshlp.examples.mcc]

  >>> 2 <<<

  The DECmcc Developers Toolkit is not required ... just the mcc_examples
  directory.

  /keith

    +---------------------------+ TM
    |   |   |   |   |   |   |   |
    | d | i | g | i | t | a | l |           Interoffice memorandum
    |   |   |   |   |   |   |   |
    +---------------------------+

    To:  MCC Community                      From:   Keith Roberts
    CC:                                     Date:   11-Aug-1992
                                            Mail:   MK02-1/D09
                                            Enet:   MOLAR::ROBERTS
                                            DTN:    264-2236

    Subj:  New 'mcc_sysgen.com' release for the Script AM (VMS)


    The 'mcc_sysgen.com' Script supplied with the Script AM (VMS only)
    Internal Field Test Kit has been updated.

    The first release could not display sysgen data from remote nodes in
    your cluster.

    This second release automatically executes the script on remote cluster
    nodes via Transparent DECnet.  You can copy the script from the
    Script-AM kit directory:

           copy molar::script_am:mcc_sysgen.com mcc_scripts:*.*

    /keith



      ----------------------------------------------------------------

                                  N O T E

        This is the second release of this Script.  The first release
        did not return all the data from other nodes in your Cluster.
        This release can execute itself remotely on any system via
        Transparent DECnet.

        There is some setup for this to work properly:

        (1) You must define a system logical on each node which will
            be executing this script:

            def/sys/exe mcc_sysgen mcc_scripts:mcc_sysgen.com

        (2) You must either enable the Task Object (not recommended)
            or setup Network Proxy on each remote system (recommended)

        Due to the time it takes to start up a remote process,
        executing this script across all the nodes in your cluster
        may take a few minutes.  Be sure to set the Script Timeout
        to an appropriate value:

          create mcc 0 script sysgen clusterwide -
            command = "@mcc_scripts:mcc_sysgen *", -
            timeout = 00:05:00

          show mcc 0 script sysgen clusterwide all status

      ----------------------------------------------------------------

I'm having a lot of difficulty figuring out how to get the Ultrix
version of the example scripts to work as shown in the documentation.

The installation script loads the dictionary and creates instances of
each of the four sample scripts, each named "x", for example:

	MCC> show mcc 0 script mcc_vmstat *
	Using default ALL IDENTIFIERS

	MCC 0 SCRIPT mcc_vmstat x
	AT 1992-08-12-20:31:15.383Iinf Identifiers

	Examination of attributes show:
	                               Hostname = x

This instance will not execute, however:

	MCC> show mcc 0 script mcc_vmstat x all attr

	MCC 0 SCRIPT mcc_vmstat x
	AT 1992-08-12-20:33:14.207Iinf All Attributes

	                               Hostname = x
	sh: /tmp/mcc_script_am_15_33_14.error: bad file unit number
	The script has produced no output.
                                Command =
"/usr/mcc/mcc_system/mcc_scripts/mcc_v
                                          mstat"

It appears that the instance identifier is always passed to the script
as the first argument.  I guess I don't understand how this is all
supposed to work - looking at the scripts, I should be able to pass a
null argument, but how do I set up the script instance attributes to do this?

	- Andy

  Andy,

  Could you try:

	MCC> show mcc 0 script mcc_vmstat x all char

  and post the output?

  The actual instance you enter (in this case "x") is not currently
  being passed to the script as an input argument.  The script that
  is executed is the one which will be displayed by the command above.

  Using the Script 'Command' Attribute, you can execute *any* script
  or O/S command and supply any arguements which that command may need.

  Let me know how it goes.

  /keith

  Andy,

  I just tried (on vms - suspect that ULTRIX will do the same thing)

	show mcc 0 script disk alldisks all attr

  I wasn't happy with the results.  I'm not even sure what was happening.
  It looked like the FCL was executing many show directives .. and putting
  the Out-Entity (in this case the names of the disks on the current system)
  into In-Entity on the next call.  This resulted in the Script AM  telling
  you that there wasn't any script by that name .. 8(

  I finally had to control/c out of it

  /keith

  --------------------------------------------------------------------------

MCC> show mcc 0 script disk alldisks all attr

MCC 0 SCRIPT disk alldisks
AT 13-AUG-1992 09:54:32 All Attributes

                                   Name = alldisks
                       Command Executed = "@mcc_scripts:mcc_disk"
                            Volume Name = "VolName"
                                 Errors = 0
                           Free Storage = 0 Blocks
                        Maximum Storage = 0 Blocks
                            Utilization = 0 Percent
                            Device Type = "Blocks"
Script not found in the MIR.

MCC 0 SCRIPT disk _DSA0:
AT 13-AUG-1992 09:54:36 All Attributes

                       Command Executed = "disk"
                            Volume Name = "VolName"
                                 Errors = 0
                           Free Storage = 0 Blocks
                        Maximum Storage = 0 Blocks
                            Utilization = 0 Percent
                            Device Type = "Blocks"
Script not found in the MIR.

MCC 0 SCRIPT disk _DAD0:
AT 13-AUG-1992 09:54:41 All Attributes

                       Command Executed = "disk"
                            Volume Name = "VolName"
                                 Errors = 0
                           Free Storage = 0 Blocks
                        Maximum Storage = 0 Blocks
                            Utilization = 0 Percent
                            Device Type = "Blocks"
Script not found in the MIR.

MCC 0 SCRIPT disk _DAD1:
AT 13-AUG-1992 09:54:46 All Attributes

%MCC-S-CANCELED, serviced cancel request calls
%MCC-E-ALERT_TERMREQ, thread termination requested

    Try the sample commands as presented in mcc_script_install.csh:
    
    manage << \%%
     show mcc 0 script mcc_df x all status
     show mcc 0 script mcc_ls x all status
     show mcc 0 script mcc_ps x all status
     show mcc 0 script mcc_vmstat x all status
     exit
     \%%
    
    These should work fine.
    
    I'm curious why you got the sh error when attempting to execute
    mcc_vmstat:
    
    	sh: /tmp/mcc_script_am_15_33_14.error: bad file unit number
    
    Use df outside of mcc to make certain you have enough space for
    temporary files in the /tmp directory.  Make certain the partition is 
    healthy.  Let me know what you find so that we can document any system 
    requirements (gotchas') for others.
    
    Thanks,
    
    Darryl
    
    

    
    On a new install, I took the option to use a private dictionary
    and it tried to copy mcc_examples:mcc_dev_fdictionary.dat to my local
    directory. This file didn't exist. can I use the one in mcc_common
    instead ?
    
    Dave McCallum

    Yes, using the dictionary in mcc_common should work just fine.
    
    Let us know how you make out with the Script AM.
    
    Darryl

    
    I have got it going from the FCL, can it run from the iconic map?
    
    Dave

    How dare you suggest the MCC development group would break the
    sacred architecture and build an AM or FM that had a dependency on a
    PM?   :-)
    
    Yes it will work with the IMPM.
    

    
    Sorry - I have GREAT faith in the architecture. It's more the
    practicalities which I was intending to ask - i.e. how do I start a
    script from the IMPM.
    
    Rgds,
    
    Dave

  Dave,

  The first IFT of the Script AM puts the Script entity under MCC, that is:

	MCC 0 Script { Command | your-entity | ...}

  So .. you have to add an MCC entity (from the IMPM toolbox) to your
  map first.  Then double click on the MCC, look for the Script, and
  double click on that ... yuck ...

  I have since changed the entity model to:

	Script <some-name> { Command | your-entity | ... }

  This allows you to register the Script AM as a global entity and have
  it appear on the map along with all your other nodes, bridges, etc...

  I'll try to make a kit available today with the entity model change, but

	Any private MS files you make for use with the Script AM will
	have to be changed a bit and the Script AM and your MS data
	reloaded into the dictionary.  The Scripts themselves will remain
	the same however.

  /keith

  A new release of the Script AM is now available ... IFT-1A

  This release fixes a few bugs and changes the entity model; making
  the Script a global entity and more easily accessible from the Iconic
  Map.  A Script Icon has been provided with this kit.

  The kits are in the same location as IFT-1.  A draft Use manual (.PS)
  file is located in:

	molar::script_am:mcc_script_use.ps

  A new version of this manual is expected in another week or so.
  

  Copy the kit to an empty directory and install the kit:

     VMS:  molar::script_am:mcc_script_pift01.bck

           backup/log mcc_script_pift01.bck/save *.*

  ULTRIX:  tlsrus::/usr/users/toolkit/public/mcc_script_pift01.tar.Z

           uncompress mcc_script_pift01.tar.Z
           tar -xvf mcc_script_pift01.tar

  Then run the Script AM install script mcc_script_install.{csh,com} with
  privileges to write to system directories.  The Script AM runs
  completely unchanged in the installed V1.2 DECmcc BMS environment

  The kits now include the Toolkit Developers Dictionary - so you don't
  have to install the DECmcc/toolkit first.

  /keith

    I have looked for this kit, but MOLAR::SCRIPT_AM: returns an error and
    tlsrus seems not to be available anymore.
    
    Are these kits still available, or do I have to go for DECmcc V1.3 ?
    
    Thanks,
    
    S�ren

    
    The kit is still available but tlsrus was moved into a DECnet hidden
    area.  To fix this try substituting hamma:: for tlsrus:: in the dcp 
    command.
    
    Note that this kit is not the lastest--we have added some mail
    scripts on the official V1.3 kit.  If you just want to try it out on
    top of V1.2 this kit will work fine--I would encourage you to copy the
    V1.3 documentation for the script, and, if you like what you see, to 
    install the V1.3 kit.  Note that we will not be rereleasing this kit 
    since V1.3 is now available.
    
    
    Regards,
    
    Darryl

    
    Is there a valid pointer to the Script AM User's Guide ?
    
    molar::script_am: does not seem to work.
    
    Thank.
    
    fg/

    Thanks I got it.
    fg/

    
    		Could the SCRIPT AM be of use to my need?
    
    I've added a note later on in this conference inquirying about the
    COLLECTION AM, but perhaps I'll pose it here as well...
    
    I have a customer that has asked if they can manage a PDP11 (actually,
    they've got several) that is NOT running DECnet.  They have used VCS
    and are not happy with the alarming capabilities...
    
    The only access they have to the PDP, (I'm not at the site yet, so
    don't quote me), is via a terminal server (I believe it a DECserver
    200), and they have a hardcopy console setup.
    
    Now here's what I'm thinking of doing, writing a command procedure that
    will fire an ALARM when the PDP is unavailable, or even more
    specifically, if a process on the PDP goes away...
    
    I'm in the process of seeing if I can get the SCRIPT AM doc printed,
    and hopefully when I get to the customer site next week they'll let me
    install V1.3.  BTW, this is on a VMS platform.
    
    Has anyone written anything like this?  Thanks in advance.  I'll be
    here until Friday and then I'm scheduled for the other site for 2
    weeks.  Mail gets to me at OTOOA::KAOU15::M_GALVIN or IOOSRV::GALVIN.
    
    /Mic