Hi John,
I wrote these two Scripts that are included as Inbound Data TPS on two timer threads that run once a night. They create CSV files once a day that contain details for all threads defined in the SITES argument. One is for Protocol details, the second for Route details.
Here is how the TPS Args are configured:
{SITES {site1 site2 site3}}
{DEBUG 0}
The threads are configured as fileset-local that function both as an inbound (the file from the previous run is the “trigger”) and an outbound. Warning! – the thread will “consume” all files in the target directory, so you will need a dedicated directory for each thread. I use a filename filter “Directory Parse” TPS, so both files can co-exist in one directory.
The scripts are running on both Unix and Windows platforms.
Regards from Germany, Jim Vilbrandt
Attachments:
You must be
logged in to view attached files.