I have a conflict with the time scheduled and will not be able to
participate in the call.
A quick comment for the discussion: My goal in drafting the Mapping
document was to provide guidance in creating jmJobSubmissionId without any
changes to current job submission protocols. I now propose that this is
incorrect. I believe that this corresponds to what you have been stating
for quite some time.
jmJobSubmissionIds should only be generated when there is a coupled Job
Monitoring application that requires its use. Therefore, a Job Monitoring
agent for the printer should only generate jmJobSubmissionId when
explicitly required by the Job Monitoring Ap. This requires the agent to
only develop jmJobSubmissionIds when properly formatted within the job.
This reduces the problem I originally formulated, but there still is the
issue of multiple submission ids. Unless an alternate solution can be
developed, I am in favor of allowing multiple jmJobSubmissionIds to be
created for the same job.
Ron Bergman
Dataproducts Corp.
On Wed, 19 Nov 1997, Harry Lewis wrote:
> I'm setting up a call tomorrow (Firday) Noon-2 MST (2-4 wayEast; 11-1 wayWest).
>
> Number is 1-888-687-2860
> pass code is 404724
>
> Topics: 1. nested JmJobSubId
> 2. collatted / uncollated
>
> I have 8 lines (we had 6 participants today). Hope you can be there!!!
>
> Harry Lewis - IBM Printing Systems
>