|
I had recently just printed off a small tree using the iSeries search option within WDSC. Basically, I had done a lengthy search looking for a REFFLD value and found many, many source member matches. The problem is that as it displayed the results within RSE, it also printed them via PDM. The really strange part is that my user profile is defaulted to my own personal output queue. I usually have to manually change output queue's to print. How did WDSC find this printer? It seems that WDSC is using a PDM API to run an iSeries search and that it somewhat uses your user options that are set in Find String. My options that reflected this condition were... Option. . . . . . . *none Prompt . . . . N Print List . . . . N Print Records . . Y If WDSC is usng PDM to perform an iSeries search I can understand it creating a report. But how did it find an HP LaserJet that I manually have to do myself? Also, what is the proper procedure in using this function and not generate a spooled file? Best regards, Gregg Willow Programmer/Analyst Minnesota Counties Information Systems 413 SE 7th Avenue Grand Rapids, MN 55744 218-326-0381 ext: 17 gregg.willow@xxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.