[AGENT++] Agent++ does not separate MIBs during code generation

[Sellinath, Juergen]

Hi Frank,
Thanks for the quick answer. I never deleted MIBs from our repository, I just added new modules from time to time and modified existing MIBs.

I tried to use AgenPro 2.7 to fix the repository as you explained - without success. A dialog opened that listed five MIB modules that could not get fixed and some explanation. I had problems to understand what is meant by "move from the repository", because there was no target given the files should be moved to. I had to guess whether the text meant "remove" (thus being a typo) or whether something like "backup" was meant. Anyway, I tried both, but neither worked.

Then I checked out the file MODULE.IDS from clearcase - thus it became writeable.  A retry of reselecting the repository suceeded - there was no problem announced any longer and the problems seemed to have been fixed by AgenPro. But if I try to open MIBs in AgenPro now nothing happens - AgenPro does not load the MIBs. I had this problem once before and had to recreate the repository, i.e. deleting all binary files and importing MIB module by MIB module - extremely annoying. 

I would be happy to have a mode of MIBDesigner and AgenPro that completely avoids the use of a repository and does parse the textual representations of the mibs on each load instead. Of course the tools would get slowed down, but the loss of time would probably be significantly smaller than periodically recreating the repository.

BTW (and a little bit of-topic): I had a look to the textual representations of one of the mibs AgenPro complained about. I found that the definition of leafs I added to tables are not at the end of the former definition of the table but at the beginning of the file like

---8<--------------------------------------
Definition MibModule
Definition Table X::leaf G
Definition Textual representations
...
Definition Table X
Definition Entry X
Definition Sequence X
Definition Table X::leaf A
Definition Table X::leaf B
Definition Table X::leaf C
Definition Table X::leaf D
Definition Table X::leaf E
Definition Table X::leaf F
...
---8<--------------------------------------

maybe it's worth a look in your code to fix it before the 2.7 release.

Regards,

Jürgen


*******************************************************
Jürgen Sellinath
SW-Engineer
 
Thales ATM GmbH
Air Systems Division
Lilienthalstrasse 2
70825 Korntal-Münchingen
Germany
Tel.: + 49 711 86032 - 222
Fax.: + 49 711 86032 - 9222
-------------------------------------------------------
Register of Trade HRB 207307, District Court Stuttgart
General Manager: Wolfgang Ernesti

-----Original Message-----
From: Frank Fock [mailto:fock at agentpp.com]
Sent: Tuesday, April 08, 2008 8:16 PM
To: Sellinath, Juergen
Cc: agentpp at agentpp.org
Subject: Re: [AGENT++] Agent++ does not separate MIBs during code
generation


Hi Jürgen,

Please upgrade to AgenPro 2.7 and then reselect
the MIB repository you are currently working
on. This will run a verification and auto-repair
process on the repository.

In (some) versions < 2.7 the MIB repository could
get compromised which could lead to problems with
MIB modules that import other MIB modules.

An update release for MIB Designer will be available
soon. Until then, you should avoid deleting MIB modules
in the repository using MIB Designer.

I am not sure if upgrading to 2.7 indeed fixes the
issue you described below, but it is very likely that
it does.

Best regards,
Frank

Sellinath, Juergen wrote:
> Hi together!
> 
> I have a MIB layout that uses a layout like this
> 
> Parent module: SNMPv2-SMI::enterprises.company.project.devicetype
> Subdevice A module: SNMPv2-SMI::enterprises.company.project.devicetype.subdeviceA
> Subdevice B module: SNMPv2-SMI::enterprises.company.project.devicetype.subdeviceB
> Subdevice C module: SNMPv2-SMI::enterprises.company.project.devicetype.subdeviceC
> 
> Since some years I generate code for Modules A, B and C based on the very same project file and everything was fine. Now, as I added some leafs to the MIB of modules A and B, AgenPro 2.6.2 produced a strange result: The code for modules A and C is generated correctly. Within the code for Module B, however, I find code for all the leafs defined within Module A. The very same velocimacros are to generate code for the sub-modules. MIBDesigner 2.5.2 declares the MIBs as being syntactically correct, thus I doubt that it is a problem with the inserted leafs.
> 
> Is somebody out there who has similar experiences and maybe a reason for that strange behaviour?
> 
> BTW: I sometimes had - for other devices of the same layout - a similar behaviour: Code for all leafs of modules A, B, and C was generated within the source file of the parent module.
> 
> Best regards,
> 
> Jürgen
> 
> *******************************************************
> Jürgen Sellinath
> SW-Engineer
> 
> Thales ATM GmbH
> Air Systems Division
> Lilienthalstrasse 2
> 70825 Korntal-Münchingen
> Germany
> Tel.: + 49 711 86032 - 222
> Fax.: + 49 711 86032 - 9222
> -------------------------------------------------------
> Register of Trade HRB 207307, District Court Stuttgart
> General Manager: Wolfgang Ernesti 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com