Directory Parse TPS

[Max Drown (Infor)]

There’s often some confusion for new users on the Directory Parse TPS for the fileset-local protocols. Here are some helpful notes on the topic.

In recent versions of Cloverleaf, the filename (including the full path) is included in the msg metadata.

Here are some examples.

proc xltp_get_filename {} {
[code]proc xltp_get_filename {} {

-- Max Drown (Infor)

Topic

[Max Drown (Infor)]

In CIS 6.1.1.0 there will be some changes to the way dirparse works.

The dirparse parameter format has been updated for parsing a list of filenames and attributes sent to a TPS, so that a keyed list is sent into the TPS.

keylset fileNames file1.LENGTH 4567 file1.MTIME 1416347174 file2.LENGTH 322 file2.MTIME 1716347174 file3.LENGTH 8888 file3.MTIME 1416347999

{file1 {{LENGTH 4567} {MTIME 1416347174}}} {file2 {{LENGTH 322} {MTIME 1716347174}}} {file3 {{LENGTH 8888} {MTIME 1416347999}}}

There is no change for return list (filename list).

Note: This update changes the format of the Tcllist. You must modify your TPS code to get the filename list data from the list.

-- Max Drown (Infor)

[Gregory Hunt]

How do you run this though the testing tool?

I see that you can change the Caller Context to ‘fileset_ibdirparse’ and I have my Proc Selected.  The Choose Data File field requires you to choose a files and not a directory, so I chose the first file in the directory.  What else do I need to do in order to be able to test a Directory Parse TPS?

[Elijah Park]

Any idea why I would be getting this in my message and not the {name size mtime} list or even a simple file list {file1 file2 file3} for that matter?

NLST

“DEBUG: fileList: File1

File2

File3

File4″

===============================================

LIST

“DEBUG: fileList: total 1880

-rw-r

---

   1 lawson   lawson        36115 Nov  9 09:46 File1

-rw-r

---

   1 lawson   lawson       886294 Nov  6 14:57 File2

-rw-r

---

   1 lawson   lawson        32241 Nov  6 14:57 File3

-rw-rw-rw-    1 lawson   lawson          237 Jan  9 2015  File4″

[Jim Kosloskey]

I think for some FTP servers you need to use a special command maybe it is NLST maybe it is LIST I don’t know.

Also be aware not every FTP seerver is capable of or may be configured to return an extended list. Check with the owner of the server to find out if it is possible and what to use.

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

[Elijah Park]

Jim, I used both NLST and LIST with no success. I’ll get with the server guys. Appreciate the response.

Max, thanks for the code hookup. Well documented too. Suggestion: you might want to initialize variable “fileNames” in tps_dirparse_list_files.

[Max Drown (Infor)]

*high five*

-- Max Drown (Infor)

[Peter Heggie]

With 6.2.0.2, we noticed a slight change in the content of the file list. This is for a Fileset-FTP protocol with the FTP Options / Dir List Command set to ‘list’, when connecting to a Windows server from an AIX server.

With version 6.1.2.0, we get this content:

[tcl :out :INFO/0:fr_soarian_extracts:08/11/2017 15:13:36] tpsDirParseFileCompleteWindows input file: 04-24-17  02:58PM               587308 ZTest_ch_20170811.txt

With version 6.2.0.2, we get this content:

[tcl :out :INFO/0:fr_soarian_extracts:08/11/2017 15:34:46] tpsDirParseFileCompleteWindows input file: {04-24-17  02:58PM               587308 ZTest_ch_20170811.txt}

I know some previous discussions show curly brackets surrounding the content or surrounding individual file data content,  but for the fileset-ftp we did not get brackets with 6.1.2.

Now we are. Still not seeing the keyed list. Is that only available with a local fileset? Or only available with a different Dir List Command?

Peter Heggie

[Author]

Replies