The key will be capturing the original file name in the first place. Are you using fileset local to read the file? FTP? Did you write a file reader procedure of your own?
Once you have the file name then you will want to stash the file name in the driver control metadata field so that it travels along with the message until the end and the driver will then use that file name to write it out.
FYI, you can’t save the file name in a global variable because each thread has it’s own namespace and Cloverleaf doesn’t publish the namespace names anywhere.
Let me know how you’re reading the file and either me or someone else can tell you how to capture the file name.
I developed a tcl proc to process a file, so I chose the protocol: file, and I manually changed the file name each time I had a file to process. I didn’t think this procedure would be used extensively. Now, I find that I need to process quite a few files, and manually changing the file name each time was too tedious. I would like to use the protocol: fileset-local and process all files in a given folder.
Using fileset local you will have to write a directory parse TPS procedure that will save the file name in a global variable so that when the driver reads the file you can take the global variable and store it into metadata (IB data TPS). This also means that your directory parse procedure will have to restrict reads to one file at a time.
There has been a change request that has been around for a while for the engine to store the file name in metadata automatically but it hasn’t been implemented yet.
The alternative to all this would be to write a procedure that reads a file.
I haven’t had a project where I did what I was suggesting, that’s just how I would do it. Someone will have to jump in with examples of writing procedures for directory parse. I’m writing my self a not to include a dir parse procedure in class though 😉
To give you a place to start, create a fileset local thread and write a simple dir parse procedure that echo’s the message text. You’ll find that it’s actually the list of files that would be read by the file driver. You can manipulate that list using TCL. What ever list of files that you continue will be the list that the driver will read.
Make sure your metadata USER field has a keyed list with the key OBFILENAME. It is from that key (OBFILENAME) that the proc in question is setting the value of fileName variable.
If the OBFILENAME does not exist in the USERDATA metadata field, then the variable fileName will not get established thus the error you see.
Jim Kosloskey
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
I have not had chance to install 5.4 yet and it would be great if metadata will have ability to carry FILENAME with the message through the engine.
Jim is absolutely right. I have another set of procs that do set OBFILENAME key list value in message metadata. Let me know if you want me to send that to you via e-mail or whether I should post it on the board.
Essentially it takes file name from inbound Fileset-Local or Fileset-FTP and stuffs it into userdata in metadata.
Here is the TCL code (see attached). Please note that you need to have both TCL procs work in tandem with each other to capture file name into a global variable first and then populate USERDATA meta data field with the value of that global in the second proc. See attached screenshots for proc placement.
.
.