Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Tidal letters process

Hi Guys,

Appreciate your help with the following scenario:

We are using Tidal 5.3.x.x.

An external process from Tidal, drops randomly a group of letters with 3 different file extensions (1 letter consist of 1 set of three files) in a source folder location (Linux environment), then Tidal job moves the letters with a wildcard file name dependency and 1 min file stable for further processing and final printing.

The problem with the above is that after Tidal commit both dependencies, it starts moving the letters whilst at same time another letter can be dropped off and gets picked up by Tidal and partially printed at the end.

How can we avoid the above scenario?.


New Member

Tidal letters process

Try this. Create a queue with a job limit of 1. Create a variable in your move job. In the action fired by the file event set the value of this variable to be the name of the file picked up by the file event

This way you get a job called which only works on the specific filename and only one instance runs at a time so it won't affect newly inbound files.


New Member

Re: Tidal letters process

Hi Joe,

Thanks for your feedback. Have a couple of questions;

create a queue with a job limi of 1 --------> COULD YOU BE MORE EXPLICIT ON HOW DO I CREATE THE QUEUE

In regards of the filename element , how can I refer to an especific letter if its filename is a mask; asterisk (*), as per there are three diffferent extensions of letters dropped randomly.


New Member

Tidal letters process

Hi Miquel,

To add the queue, right click on queues, add the queue, set the priority to something higher (say 60) than the default systems queues, set the job limit =1  and apply a filter such as a job class so that only specfic jobs end up on this queue.

For the group doing the actual file handling define a group variable which will become the the name of the file picked up by the file event. So in the group we might define a local variable GROUP_FILENAME. Put this group in a job class which matches the filter on your queue.

In the action that calls the file handling job define an override such that GROUP_FILENAME is assigned a value drawn from the file event. In the Parameters section GROUP_FILENAME= which is a variable found under

Variables -> Event Variables -> File Events -> File Name.

Now when the event triggers the action sets the name of the file to be operated on to be that picked up by the event.

One file is processed at a time. No wildcards required. All nice and precise.