Classification:
Prologue:
Epilogue: Harry Lewis - IBM Printing Systems
Tom, I'm confused a bit by your question:
>Convincing that we need to keep jmGeneralMaxNumberOfJobs as it is
>independent of the wrap point.
>So do we also need to add an object, say, jmGeneralMaxJobIndex,
>for the wrap point as my second question in the issue asks?
>For example, BSD LPR/LPD wraps at 999 back to 0.
What does the fact that BSD LPR/LPD wraps at 999 have to do with
the wrap point of jmJobIndex (that *is* what we're talking about,
isn't it?). I'm missing your point.
little value, especially if we also have another object representing
how long a job entry will remain in the table (in seconds). I assume
some applications will use jmGeneralMaxNumberOfJobs for storage
allocation, but this assumes a rather static approach by this
application.
Can someone shed more light on who will use this object, how and
why?
Tom, maybe you can help me out with the BSD slant.
Harry Lewis