Rich P
Member
We're using Acom EZeDocs on World 7.3 and are having our share of pains with the way it integrates with JDE DREAM Writers and iSeries out queues.
First:
ACOM monitors a defined output queue which needs to be set up in their software. If the JDE DW version does not have an output queue override, the output will go to the users default output queue. This would force us to define each output queue on our iSeries in Acom software.
Next:
Acom's software does not check the status of the spool file in the output queue, and it will automatically print it regardless if the spool file status is on "hold" or not. After it prints, Acom moves the spool file to another output queue (so it doesn't print again).
If anybody is using Acom with JDE, this will probably make more sense than to others not using it.
Thoughts? Solutions??
First:
ACOM monitors a defined output queue which needs to be set up in their software. If the JDE DW version does not have an output queue override, the output will go to the users default output queue. This would force us to define each output queue on our iSeries in Acom software.
Next:
Acom's software does not check the status of the spool file in the output queue, and it will automatically print it regardless if the spool file status is on "hold" or not. After it prints, Acom moves the spool file to another output queue (so it doesn't print again).
If anybody is using Acom with JDE, this will probably make more sense than to others not using it.
Thoughts? Solutions??