Writing an empty second "flag" file after data file to FTP

[Former Member]

Before I start, yes I'm well aware this is not a good way to handle file locking! Unfortunatly we have a legacy system we cannot change and rename is not an option. We are using PI7.0/SPS12.

We write a file to FTP location, and subsequently need to write a file of similar name (appended with "OK"). Ideally an empty file.

I dont really want to go down the path of writing an adapter module just for this (I'm not even sure if you can generate multiple outputs with different filenames from 1 call to an adapter module!).

Any ideas?

Thanks,

James.

Points where appropriate.

[bhavesh_kantilal · Accepted solution]

I still did not get the entire flow of your interface here, and what you actually want, but why not usre multiple inbound interfaces in the interface determination?

One will wruite the actual file and the other the empty file that you want...

Does it make sense? If no, can you explain a bit further on what the entire requirement is?

Thanks,

Bhavesh

[Former Member · Accepted solution]

As much as I hate to add to your massive points total, you were right

Testing seems to show that the stub file is written after the mainfile when the process in order flag is checked.

Thanks

James.

[bhavesh_kantilal · Accepted solution]

A wild guess helped 😛

Glad to know that!

[Former Member]

James

I used BPM to create four files with different names from the same input...

I used the filename variable to generate the different filenames, but had four separate communication channels....

One of my files purely has the word READY in it so the legacy application know the job has finished!

[Former Member]

We did think about that and it's perfectly valid but it's a lot of testing, same as writing an adapter module! Ideally the solution needs to be config based

Only other way I can think of is to run a post command which runs an ftp script, but that's so horrific I didnt want to mention it