topic Re: Debugging LSF file events in SAS Data Management

Debugging LSF file events

jtlbg — Tue, 19 Dec 2017 16:22:15 GMT

I have a job which I've scheduled to run via the Schedule Manager in SAS Management Console. I'm using Platform LSF as the scheduling server. The job is designed to start when some files arrive. I've used the "arrival" event rather than the "exists" event.

Unfortunately, despite all the files having arrived, the job is still in a waiting state.

How do I diagnose the cause here? SAS Management Console gives me no information about jobs which have already been submitted for scheduling. None of the LSF command line utilities, or the Flow Manager application, appear to give me information about file events (external events in LSF lingo). I've checked and double-checked that the files really do exist, in the right location, with the right names.

I've got other jobs which are successfully being triggered by file arrival so I don't think it's a general problem with my installation, which is SAS 9.4M4. Platform LSF is version 9.1.3.0.

Re: Debugging LSF file events

SASKiwi — Wed, 20 Dec 2017 00:28:29 GMT

Have you checked Platform Process Manager for the job? Is that where you see a status of "waiting"?

Re: Debugging LSF file events

jtlbg — Wed, 20 Dec 2017 09:05:56 GMT

Classification: Public

Yes, Platform Process Manager shows the job as waiting. It shows me (in the flow diagram) the list of file event dependencies, but doesn't tell me which of those (if any) it considers true.

Re: Debugging LSF file events

SASKiwi — Wed, 20 Dec 2017 19:19:07 GMT

I'd suggest opening a track with SAS Tech Support if you haven't done so already. I suspect you will need to dig into the LSF logs to make any progress.

Re: Debugging LSF file events

jtlbg — Tue, 02 Jan 2018 09:59:04 GMT

Classification: Public

We eventually resolved this ourselves. It seems the user that the LSF scheduling process runs as did not have access to the directory in which the trigger files were located. The vendor documentation is quite bare on this subject so this isn't a definitive root cause, but a permission change on the directory (chmod o+rx) worked.

Re: Debugging LSF file events

SASKiwi — Tue, 02 Jan 2018 19:35:34 GMT

Please update your post as solved then.