|
midrange.com
Odds are slim that it's security.
How's about my earlier suggestion to use USROPN and EXTFILE as keywords on
the printer file? Bypasses having to have CL and an OVRPRTF.
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: RE: trigger pgm
doesn't know about Qprint
drange.com
02/25/2002 03:52 PM
Please respond to
midrange-l
Here you go:
Object -----Object------
------Data-------
User Group Authority O M E A R R A U D
E
*GROUP QPGMR *ALL X X X X X X X X X
X
*PUBLIC *CHANGE X X X X X
X
-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Monday, February 25, 2002 3:24 PM
To: midrange-l@midrange.com
Subject: RE: trigger pgm doesn't know about Qprint
Let's compare:
Object
User Group Authority
QPGMR *ALL
*PUBLIC *CHANGE
Object ----------Object-----------
User Group Authority Opr Mgt Exist Alter Ref
QPGMR *ALL X X X X X
*PUBLIC *CHANGE X
Object ---------------Data---------------
User Group Authority Read Add Update Delete Execute
QPGMR *ALL X X X X X
*PUBLIC *CHANGE X X X X X
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: RE: trigger pgm
doesn't know about Qprint
drange.com
02/25/2002 03:24 PM
Please respond to
midrange-l
*PUBLIC has access to the "data" portion of QPRINT.
-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Monday, February 25, 2002 3:04 PM
To: midrange-l@midrange.com
Subject: RE: trigger pgm doesn't know about Qprint
WRKOBJ QPRINT
5=Display authority
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: RE: trigger pgm
doesn't know about Qprint
drange.com
02/25/2002 02:43 PM
Please respond to
midrange-l
Evan,
Great questions. Thanks for your time.
> - is there another QPRINT higher in the library list ?
A *PRTF by the name of QPRINT only exists in QGPL.
> - are both users authorised to QPRINT or is public authorised
I think everyone is authorized to use QPRINT, aren't they?
How would I tell either way?
> - is the QPRINT object in QGPL definitely a print file
Both a *OUTQ and a *PRTF exist by the name QPRINT.
> - what is the last change date on the print file and the program ?
QPRINT was last changed 8/14/01. The program is being developed as we
speak.
> - is there another QPRINT file anywhere on the system that the program
> could have been compiled with ?
Yes, but those libraries with their own definition of QPRINT are not in the
library list of the job description (or the current library list) when the
compile takes place. Regardless, at runtime, the trigger program should be
able to find QPRINT
in QGPL. In fact it does when the event that causes the trigger program to
fire occurs on the AS/400.
It's just when the triggering event occurs from a rec coming over from our
SQL box that the trigger
program doesn't seem to know about QPRINT.
Dave
-----Original Message-----
From: Evan Harris [mailto:spanner@ihug.co.nz]
Sent: Monday, February 25, 2002 2:15 PM
To: midrange-l@midrange.com
Subject: RE: trigger pgm doesn't know about Qprint
Dave
try the following questions then:
- is there another QPRINT higher in the library list ?
- are both users authorised to QPRINT or is public authorised
- is the QPRINT object in QGPL definitely a print file
- what is the last change date on the print file and the program ?
- is there another QPRINT file anywhere on the system that the program
could have been compiled with ?
Hope this helps
Regards
Evan Harris
>Both QUSER and the userID that I think is running the job
>use QDFTJOBD. QFDTJOBD has QGPL in it.
>
>
>-----Original Message-----
>From: Evan Harris [mailto:spanner@ihug.co.nz]
>Sent: Monday, February 25, 2002 1:37 PM
>To: midrange-l@midrange.com
>Subject: Re: trigger pgm doesn't know about Qprint
>
>
>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.
>_______________________________________________
>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.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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 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.
