parsing destination from NetConfig with tcl

[Yves Guerin]

Dear,

I try to get information about a destination:

Code:

NetConfig code:
destination inter_site {
   { BITMAP {} }
   { GROUPS mygrp }
   { HOST  }
   { PORT 29405 }
   { SITE adt }
   { SYMNAME inter_site }
   { THREAD intersite }
}

from a tcl proc, I am able to get everything with the “netconfig” command but with the destination I got the following errror

Code:

puts “[netconfig get destination data inter_site]”

illegal netconfig command destination data inter_site
   while executing
“error “illegal netconfig command $originalArgs””
   (”get” arm line 25)
   invoked from within
“switch $action {
       ingroup                 {eval netcfgIsConnInGroup $args}
       inprocess               {eval netcfgIsConnInProcess $args}
       load                    {eval netcfgLoad $args}
       modifi…”
   (procedure “netconfig” line 9)

But from the nci.tlib file I got this:

Quote:

#    get destination data    netcfgGetDestData

So I need your help

We run cloverleaf 5.8 on AIX

Regards,

Yves

Topic

[Yves Guerin]

Dear,

I finally find the bug in the file nci.tlib:

[Max Drown (Infor)]

The switch command for $which in the netconfig proc in nci.tlib is missing the destination entry.  It should be:


               switch $which {
                       connection        {set which “Conn”}
                       destination        {set which [code]
               switch $which {
                       connection        {set which “Conn”}
                       destination        {set which

-- Max Drown (Infor)

[Yves Guerin]

Dear,

Great, I was not very ready to change the code for this tcl (cloverleaf made).

Regards,

Yves

[Jim Kosloskey]

Is the use of these modules now supported?

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Yves Guerin]

Dear,

They are not supported by cloverleaf ?

Regards,

Yves

[Jim Kosloskey]

It was my understanding to use at your own risk.

Meaning the way you interact with the scripts could change without notice and functionality could potentially disapppear or alter without notice.

I don’t believe at this time there is a supported API for doing this – I could be wrong though I don’t find one.

For example I see no mention of any of this functionality in the documentation  (Cloverleaf 6.0.0) nor have I ever seen any from Cloverleaf 3.1 on.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[James Cobane]

I believe the nci.tlib is used internally by the engine, so is technically supported but not in terms of creating custom scripts and or being modified by a customer.  I have created many custom scripts referencing the procs within nci.tlib, but if something changes within nci.tlib that breaks your custom scripts, you are on your own.

Jim Cobane

Henry Ford Health

[Yves Guerin]

Dear,

Ooops, not supported 😯 , ok I will stick with my tcl + tclX or shell script to parse the NetConfig.  

Regards,

Yves

[Rob Abbott]

Actually, starting with Cloverleaf 6.1, these commands are documented.  There is one caveat:

Quote:

Note: These commands and the data they return are primarily intended for internal use. The interfaces or data may change at any time.

If the commands change we’ll update the documentation.  They haven’t changed in several years, so you are reasonably safe using them.

Rob Abbott
Cloverleaf Emeritus

[Jim Kosloskey]

Good deal – glad to see they are documented.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies