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



ITSCHEDP is a printer file (permanent).

I was signed on as QSECOFR when I started the save. WRKACTJOB, though, showed QPGMR as the "person" running the startup job when I noticed the error.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

I found a delivery in my flaw. -Don Quisenberry


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Thursday, May 20, 2010 3:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: QSTRUP Issue

Is ITSCHEDP a perm file or temp file?? What id are you signed on with when
you do the option 21.

On Thu, May 20, 2010 at 1:01 PM, Jerry Adams <Jerry@xxxxxxxxxxxxxxx> wrote:

I just finished doing a SAVE 21 on our backup system (prior to installing a
new Cume and some Groups). QSTRUP is run whenever the system returns from a
restricted state. Part of my QSTRUP program has a call to a program that I
wrote a year or two ago. In the program there is a printer file when is
defined as USROPN.

There is a message waiting (the text of which is not very helpful - a call
to a procedure ended in error). Under debug I found that the program is
stopped at the statement which opens the printer file. The joblog prior to
that has CPF4104 - User not authorized to operation on file ITSCHEDP.
Running DSPOBJAUT over the printer file shows *PUBLIC with *All; there are
no exclusions. The job (QSTRUPJD) is running under QPGMR (which has no
password on our system).

I've had this program running in QSTRUP for a year or so without any
mishaps. Any ideas?

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx<mailto:jerry@xxxxxxxxxxxxxxx>

I've seen the future and it's much like the present, only longer. -Don
Quisenberry

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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 ...

Replies:

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.