Posted by Robert G laurin on May 06, 2013 at 07:34:52:
Found a problem with the way DES works.
I have a program that writes to two (2) different Document Archives (Spoolers). The first print job is a short summary that executes with the standard text viewer 'EXTPTR', then proceeds to create a series of jobs on a different spool which has no DES program.
Each spool job is closed before the next one starts.
What I see as a result of EXTPTR is a text view in the of next job in the spool that has no DES program. It displays only the beginning since the job has just started and is still queuing.
I know that the DES program is getting the job info from the # buffer in DES.Data. Obviously the print handler (COSP ?) is really confused.
I know it had to wait for the copy from %%UserProfile%%\Local Settings\Temp to $(SPL) folder to complete before the launch. But that does not explain the confusion.
Can this be fixed?
While you are at it, I've asked a couple of times, can we get either the final filename or at least the job number in the Document Archives when the DES is called? That would be so helpful so we can complete the full automation of some processes. You know, the good old "Press ONE button and the WHOLE job gets done!"
Yes! We can fix it!
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.