How easily to extract an IBDIR name from netconfig ?

Gaeten,

That would be nice if that information were avaiable during the Directory Parse UPoC.

What I use is a generic, reusable proc and it requires arguments giving the directory path for the inbound and where the copy should go.

If I could get the inbound directly, I could eliminate one argument (I would still need to know where the copy should go).

I refuse to use the unsupported mechanisms to interrogate the NetConfig and instead, continue to push Quovadx to publish a supported API to provide access into the various configuration files.

If you want to use them, there are some mechanisms which come with Cloverleaf(R) that allow you to navigate the NetConfig. That is all I know about them – others probably can give you more assitance there.

Thanks,

Jim Kosloskey

I agree with Jim but have found I do need to get that config data.

If you do a search on this form for “netcfgLoad” you should be able to find all kinds of related topics to those tcl procs.

In the latest version, the directory and file name are provided in the DRIVERCTL metdata field.  Sorry to say that the Directory Parse UPoC still provides only the file name itself.

I typically use a Directory Parse UPoC to check a file is stable prior to reading it and, as such, I need the full path to size it.  My Directory Parse UPoC has a subroutine which reads the NetConfig to get the directory name.

If you just need the path in a TPS proc then get it from the metadata.  If you need it in a Directory Parse UPoC, send me an e-mail and I’ll give you an example of how I do it.  Or, better yet, attend the User’s Conference and I will provide lots of example procs.

Hi,

does anyone know if the problem with the missing IB-dir information in directory parse TPS has been fixed in V5.8?

I’m currently thinking about writing a directory parse TPS to make Cloverleaf rename any file to .tmp before reading it to avoid concurrent access of the writing system while cloverleaf still reads.

However – same problem as above – I can’t rename unless I have the full path to the files.

I tried to sample some metadata from an directory parse message in V5.8 but I still can’t find any suitable information on the IB directory.

Is there still no alternative to parsing the NetConfig?

Thanks!

Simone

Yes, full path is there now

Although I don’t have time to test it in an dir proc I don’t see way it won’t work.  In the out bound I’ve used nfLoad to get the OBDIR value so I don’t have to hard code the directory where the file will be located.

Change OBDIR to IBDIR and that should get you the inbound directory name for the connection.  

Hope this works for you.

Yes, full path is there now

Hey Charlie,

that’s good news! Would you care to elaborate as to where I might find that piece of information?

Here’s a message dump of a V5.8.3 dir parse message:

I still get only a space separated list of filenames with no path information in either the message itself or the metadata.

Am I looking in the wrong places?

Thanks for any advice!

Simone

Hope this works for you.

Thanks John!

It works like a charm! (I tested it with IBDIR instead of OBDIR)

…but it still kinda feels like a hack…

I’d prefer having the engine handing over the information voluntarily rather than having to violently extract it from cloverleaf’s intestines .

😀

Geetings

Simone

set klst [msgmetaget $mh DRIVERCTL]

set filename “”; keylget klst FILENAME filename

The above will give you the full path.  If you want just the file name do a file tail command

set klst [msgmetaget $mh DRIVERCTL]

set filename “”; keylget klst FILENAME filename

Sorry Charlie,

the above code just gives me empty stings. As you can see in the message dump I posted, there’s no DRIVERCTL information in the metadata whatsoever.

Maybe you’re thinking about IB-TPS-messages? Those definitely have the fields you mentioned. But it seems to me, for directory parse messages the information is still missing…

Greetings

Simone

You are correct.  We cannot put in the DRIVERCTL until after the Directory Parse routine becuse, at that point, we don’t know which file to read.

Unfortunately the list provided to Directory Parse only has the names.

This might be a valid enhancment request to provide at least the directory name a t that point.

As someone else suggested, I simply read the NetConfig to get the directory

I don’t have my archived stuff with me right now but if you send me an e-mail I will be glad to send you a copy of the Directory Parse proc I use to verify a file is stable prior to fetching it