We have persistence defined for JobID, JobState and JobAccounting tables.
Suppose the printer has been idle for longer than the largest persistence
value... what do we expect the tables to look like? Will they be empty? Or
should some minimum number of jobs always be in the tables? Or is it up to the
implementation? I suggest that there is really no problem with "empty" tables -
and indeed, we can't prevent them on initialization. I just want to bring this
out for anyone who may be considering applications target
at the Job MIB.
Harry Lewis - IBM Printing Systems