Conference necsc::paw

963.0. "Augmenting PAW inventories" by CSC32::B_MACKENZIE (If it ain't fixed, don't break it!) Wed Mar 12 1997 17:16

Greetings,

I have a question regarding augmenting PAW inventories with MIF's.

I read in the SDK for SMS how one can add a Group to an existing Object.  
This seems pretty straightforward.  One merely copies the noid-Mif into 
the client's \MS\SMS\NOIDMIFS directory.  I'm sure this works fine for 
SMS/PC's.

Now with PAW, I believe one can copy the Mif or NHM file to the  
\PAW\MIF\PSC directory on the SMS server.  But how does PAW/SMS know to 
associate the Mif/Nhm file with a particular VAX?  I've tried using the 
SMSID as the filename  (eg.  CXO00005.NHM) and PAW promptly moves the file
to the Badmifs directory.  Mifcheck sees no errors with my noid-mif.

Any suggestions appreciated.  Here's a copy of my customized Mif.

Thanks, Bruce.

// collect version: T3.0-0826-1  Mon Sep  9 17:06:40 1996
Start Component
	Name = "SYSTEM SPECIFIC INFORMATION"
	Start Group
		Name = "System Specific"
		ID = 1
		Class = "ASSETWORKS|SYSTEMSPECIFIC|1.0"
		Start Attribute
			Name = "System Manager Name"
			ID = 1
			Access = READ-ONLY
			Storage = SPECIFIC
			Type = String(20)
			Value = "Bruce Mackenzie-Low"
		End Attribute
		Start Attribute
			Name = "Site"
			ID = 2
			Access = READ-ONLY
			Storage = SPECIFIC
			Type = String(3)
			Value = "CXO"
		End Attribute
		Start Attribute
			Name = "Environment"
			ID = 3
			Access = READ-ONLY
			Storage = SPECIFIC
			Type = String(15)
			Value = "PRODUCTION"
		End Attribute
	End Group
End Component

    There was a directory on the client side for both VMS and UNIX that
    would let you add groups via MIF's.   I think this was added in PAW 3.0
    though.  The MIF's are appended to the end of the next inventory MIF.

Thanks .1.

I'd like to tackle this problem from the server-side if possible to 
avoid visiting serveral hundred VAX clients.  And even if I copy the 
mif info to the client, how do I associate the mif with a particular 
cluster member (since they all share the same paw$root directory tree)?

    
> I'd like to tackle this problem from the server-side if possible...
    
    The only way I know to do it is to add the groups to the inventory
    before it is processed.  The inventory agent can do this and PAWEXEC
    could be modified to do it but I don't think that it does it now.
    
    You could produce an ID MIF with the ADD pragmas in the file.  Shutdown
    the data loaded and take a look at the files output from the inventory
    processor after history processing is done.