Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How to make job QPRTJOB go away?
683 views
Skip to first unread message
Mr. K.V.B.L.
Aug 7, 2012, 11:03:33 AM8/7/12
to
I'm working on a 'thing' where QSQSRVR is complaining about me adding libraries to it's library list. It's doing so by adding job logs entries into a job called QPRTJOB. I delete these things but they never go away completely. Deleted entries have a status of FIN.
This stuff is coming from a Java program. I'm setting the library list for the server job. Anyway, any details on getting rid of the FIN deleted logs?
This stuff is coming from a Java program. I'm setting the library list for the server job. Anyway, any details on getting rid of the FIN deleted logs?
CRPence
Aug 7, 2012, 1:07:40 PM8/7/12
to
On 07 Aug 2012 08:03, Mr. K.V.B.L. wrote:
> <<SNIP>> adding job logs entries into a job called QPRTJOB. I delete
> deleted logs?
The *N/UsrPrf/QPRTJOB jobs are the owning job [see SPLFOWN parameter
of OVRPRTF, CRTPRTF, CHGPRTF] of a spool file when the owner should not
be the current job in which the spool file was created. A new job
number by that naming [&N/UsrPrf/QPRTJOB] will be created to become an
owner when yet another SPLF must be assigned a job to the current user
instead of the current job; i.e. removing the job would be somewhat
futile if that or other spooling will effect new entries assigned to the
current user vs the job. Typically only ever one job by that name
[unless spooled files are not being deleted], that the one job exists
for any one user is not an issue once the purpose of the job is
understood and since recognized. Nonetheless, the job can be removed by
issuing an ENDJOB, having specified the option(s) to delete spool data
for the job; i.e. minimally IIRC, to request to "Delete spooled files"
SPLFILE(*YES).
Preventing the creation of the spool files or ensuring they are owned
to another job other than to the QPRTJOB of the current user [i.e. the
SPLFOWN adjusted] would eliminate the creation of the user's QPRTJOB for
the given scenario; albeit such a job possibly generated by another origin.
Regards, Chuck
> <<SNIP>> adding job logs entries into a job called QPRTJOB. I delete
> these things but they never go away completely. Deleted entries have
> a status of FIN.
>
> <<SNIP>> server job. Anyway, any details on getting rid of the FIN
> a status of FIN.
>
> deleted logs?
The *N/UsrPrf/QPRTJOB jobs are the owning job [see SPLFOWN parameter
of OVRPRTF, CRTPRTF, CHGPRTF] of a spool file when the owner should not
be the current job in which the spool file was created. A new job
number by that naming [&N/UsrPrf/QPRTJOB] will be created to become an
owner when yet another SPLF must be assigned a job to the current user
instead of the current job; i.e. removing the job would be somewhat
futile if that or other spooling will effect new entries assigned to the
current user vs the job. Typically only ever one job by that name
[unless spooled files are not being deleted], that the one job exists
for any one user is not an issue once the purpose of the job is
understood and since recognized. Nonetheless, the job can be removed by
issuing an ENDJOB, having specified the option(s) to delete spool data
for the job; i.e. minimally IIRC, to request to "Delete spooled files"
SPLFILE(*YES).
Preventing the creation of the spool files or ensuring they are owned
to another job other than to the QPRTJOB of the current user [i.e. the
SPLFOWN adjusted] would eliminate the creation of the user's QPRTJOB for
the given scenario; albeit such a job possibly generated by another origin.
Regards, Chuck
rodj...@gmail.com
Oct 1, 2012, 9:11:45 PM10/1/12
to
On Tuesday, August 7, 2012 10:03:33 AM UTC-5, Mr. K.V.B.L. wrote:
> I'm working on a 'thing' where QSQSRVR is complaining about me adding libraries to it's library list. It's doing so by adding job logs entries into a job called QPRTJOB. I delete these things but they never go away completely. Deleted entries have a status of FIN.
>
>
>
> This stuff is coming from a Java program. I'm setting the library list for the server job. Anyway, any details on getting rid of the FIN deleted logs?
FIN status spooled files essentially are non-existant, they do not take up any space except an index entry. I do not recommend doing anything with these other then deleting the spooled files as you're already going. I do not recommend messing with the SPLFOWN unless you REALLY REALLY understand the full consequences of the changes. The best approach is to stop the creation of the joblogs. I don't have the access to all the System i doc and code like I use to, but got to believe someone can help you address the creation of the qpjoblogs such as possibly some settings on the qsqsrvr job description to not be so "chatty".
> I'm working on a 'thing' where QSQSRVR is complaining about me adding libraries to it's library list. It's doing so by adding job logs entries into a job called QPRTJOB. I delete these things but they never go away completely. Deleted entries have a status of FIN.
>
>
>
> This stuff is coming from a Java program. I'm setting the library list for the server job. Anyway, any details on getting rid of the FIN deleted logs?
0 new messages