no class 4 initiators were open.

[alpna]

Hi,

Recently we had an issue in production. In that, a file was not sent across to a business location because a Job did not run. Later it was told that "no class 4 initiators were open and so job could not run".

Can someone please advise why such a thing would happen? Will not a WLM policy make sure that an initiator be available, if for some class all initiator are busy?

[Robert Sample]

First, be aware that there are WLM initiators and JES initiators. The site support group has to make an explicit determination to use WLM initiators and make changes to system parameters to make them available.

Second, if there are no WLM initiators on the system, then WLM plays absolutely no role in initiator allocation / selection / deallocation / etc. So your statement

Will not a WLM policy make sure that an initiator be available, if for some class all initiator are busy?

may not even apply to your site.

Third, from the V2.1 JES2 Commands manual:

WLM can adjust the number of initiators on each system based on:

The queue of jobs awaiting execution in WLM-managed classes.
The performance goals and relative importance of this work.
The success of meeting these goals.
The capacity of each system to do more work.

So if your system was running at 100%, or the job is not running in an important service class, or various other reasons, WLM would not start another initiator for that job even if your site is using WLM initiators.

The usual site solution for your problem is to have a dedicated job class with its own initiator for the job(s) that meet particular criteria.