Reply To: fileset-local in run mode at process start

[Greg Eriksen]

Thank you both for the responses.

Michael,

I had thought about making the code in the ‘run’ mode conditional on being around the time of the advanced scheduling, but in times past I have run into problems with using a time window like that.  What happens when you have scheduled/unscheduled down time which precludes the normal processing, and now you can’t force a run outside the time window without modifying the code.  But this will probably be my plan “B” if there’s some unresolvable problem with the current solution.

And, “nice emails”?, I’m not sure I understand the concept.

Richard,

Unless I’m misunderstanding you, I think we are talking about the same thing.  The proc I’ve been coding is used in the Inbound / TPS / Directory Parse (fileset_ibdirparse) to replace the default action.   And yes, if the file exists and I don’t have to send out any nasty emails, then I modify the content of the proc’s continued message to only contain the name of the file I want to be processed.  Otherwise, I’d have problems with the names of some hidden files (start with a dot “.”) and a subdirectory that are also in that inbound directory.

All,

The main problem I can see with my solution is that it is really just a fix for what I consider to be a bug with the ‘run’ mode getting executed at startup even though advanced scheduling is enabled.  If Cloverleaf ever comes to agree with this viewpoint and changes the startup behavior, then my code will stop working until I remove the fix.