|
Bonnie, Can you elaborate on what you need to accomplish? Does every individual spool file go to one (and only one) recipient? It strikes me that you will need to have some unique descriptor in each spool file, either the print file itself, the User Data field, or some character string embedded in the text itself. When a spool file is created you could then compare your descriptor value against a table you have created in order to determine the recipient(s), if any, for that report. Then process the spool file accordingly. Examine the use of a data queue associated with your output queue so that you can process on a fairly real-time basis. I'm not sure that a WRKDIRE API would shorten your workload because you would still need a table to determine the user profile. In this case, you might as well just put the email address in the table. You clearly said that purchased solutions are out, but as you examine the work necessary to implement this, you might find that some of the packaged solutions represent real value and are reasonably priced. Regards, Andy Nolen-Parkhouse > bounces@midrange.com] On Behalf Of Bonnie_Lokenvitz@epcmolding.com > Subject: Report Distribution Via Email - How to Determine Recipient > > Now that I can send to our internal email, I need to know how to handle > distribution. > I would rather not hard-code too much in CL programs. > > Are you setting up distribution matrices by printer file? Most of our > stuff does use unique printer files. > NOTE: we are at V4R5 and will not be spending real money - so purchased > solutions are out. > > Not all the recipients are AS/400 users but I could set up profiles. > Is there an API to retrieve the directory entry (WRKDIRE) email > address? > > Thanks, > Bonnie Lokenvitz > Engineered Polymers Corp
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.