Re: trigger pgm doesn't know about Qprint

Another option is to open/close the file yourself - USROPN.   And add the
following keyword to your file:
extfile('qgpl/qprint')

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Prowak, Dave"
                    <DProwak@ci.syracus       To:     midrange-l@midrange.com
                    e.ny.us>                  cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     trigger pgm doesn't 
know about Qprint
                    drange.com


                    02/24/2002 03:37 PM
                    Please respond to
                    midrange-l






This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi,
I have a trigger program attached to FileA that gets called whenever a rec
is added to FileA (*AFTER).
The trigger program prints a report using the *PRTF QPrint.

When a rec is added to FileA from our AS/400 using DFU the trigger program
executes
as expected and prints the report.

Recs can also be added to FileA via a web page, in which case the recs are
sent over from
a SQL box.  When a rec is added via the internet, the trigger program blows
up.

I get a CPF4101 msg complaining about the *PRTF QPrint.

The connection between SQL & our AS/400 is using OLE and
a default userID that is defined to use the default job description.
Within
the default
job description, the library list includes QGpl where QPrint is defined.
So why doesn't the trigger program know about QPrint?

Thanks,
Dave


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.