The issue regarding $stdlists having a priority set to 0 is done when $stdlists
are closed at a time
when JobPak is not running. This is an attempt to insure that the $stdlists will
remain in the spooler
until such time as JobPak is brought back up to analyze these $stdlists. In the
event you find that
there are many $stdlists in your spooler with a priority of 0, I would suggest
that you take a look at
your production schedule. If in the event that JobPak is brought down prior to
the beginning of a backup
and before lets say all of your production jobs have completed, the $stdlists's
priority would be set to
0 and a portion of your memory would be allocated to hold on to information
regarding these un-analyzed
$stdlists. Now, if you, after your backup completes, restart your system, you
will effectively wipe that portion
of memory out. This will leave the $stdlists at a priority of 0 with no record
for JobPak to analyze them.
This is when you would use REPROCS to process these 'orphaned' $stdlists.

The trick is to follow your normal schedule with one important alteration. After
the backup has completed
and before the system is re-started, bring JobPak back up to analyze the
unprocessed $stdlists.

Hope This Helps,

Reid E. Baxter
Applied Materials, Inc.