× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You'd be danged hard pressed to find a user with a job description which
doesn't include QGPL in it's library list.

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



                    Evan Harris
                    <spanner@ihug.co.nz       To:     midrange-l@midrange.com
                    >                         cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     Re: trigger pgm 
doesn't know about Qprint
                    drange.com


                    02/26/2002 02:36 AM
                    Please respond to
                    midrange-l






Dave

my suggestion would be to try and establish what user is actually running
the job that the message originates from - maybe even by taking a dump when
you get the program message.

It would seem to me that the likely cause of the error is that the job is
running under a user profile that is something different to what you expect
it to be, hence a different job description is in use and the printer file
can't be located. Identifying which profile is running the job that is
issuing the message should fix this for you. If I had to guess I'd say it
is probably QUSER :)

Hope this helps

Regards
Evan Harris


>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?


_______________________________________________
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.







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.