Job Number Oddity

All,

I reset our F986111 to 1 and noticed an odd thing I hadn't seen before. When a job is submitted by the scheduler, it uses the next number. When a job is submitted by a fat client, it skips a number and uses the next number.

Example: F986111 = 1000, scheduler would submit using 1001 while fat client would submit using 1002.

Looking back through our history, it looks like it has always been that way.

Any ideas? It is not a problem for us, just a curiousity.

Thanks,

Jer

Probably a bug in the code.

I've checked my history table (documented elsewhere) and it hasn't missed any job numbers on mine.

I seem to recall that somehow the in-between number is used for spec updates for selection and sequencing, but in a hidden fashion. Since the scheduler (and runube executable) don't do spec updates, the in-between number isn't used.

I may be remembering wrong, it has been a long time.