Kees wrote : ----------------------- Do you have a MAS where both jobs can be converted and run? How many convertors do you have available? JES2 can't keep jobs waiting for a resource. If they "wait for a resource" they must have "started" already. How do they wait for the resource and how do they determine the resource is available? -------------------------
Hi Kees, Waiting a resource, say, a dataset currently used by another user, is no matter here. That was just what is actually happening. So this is not an issue or matter here. So let's forget about resource case. Anyway let's start from the point where everything is okay for them to run rather than there is only one initiator for them. Plus as a natural expectation the system gave the two distinct job IDs. First submitted jobs has lower job number and same input queue priority with second submitted job, and they both went through JES2 input queue. As I looked at input queue (this time that initiator is allocated another job) for a while first job seem to be run first.. When the initiator is ready to select a job between these two second job is selected for execution at first. Regards. Nasuh. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
