If the jobs using a print file routinely apply the attributes with OVRPRTF, the attributes become part of the CL source. I worked 12 years at a site where all the printer files were compiled with standard source, but the CL's set them to whatever was needed. I've missed that at other shops.
You can need accurate printer file attributes with design tools, but the CL will document what they are at least.
Sent from Outlook<
http://aka.ms/weboutlook>
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Rob Berendt <rob@xxxxxxxxx>
Sent: Tuesday, March 13, 2018 4:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Comparing prtf atributes from Production LPAR to R&D LPAR - flagging the differences
We too had a big problem in which people were modifying printer files on
our production machine. Keep in mind that we do not even keep source on
our production machines. They were executing things like CHGPRTF to
change overlays, etc.
And when we did change something on source and brought it over to
production their change got clobbered.
This hasn't been so much an issue with good change management software.
They do a fairly good job of checking the attributes during audits and
flagging stuff changed outside of the system.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/13/2018 04:09 PM
Subject: Comparing prtf atributes from Production LPAR to R&D LPAR
- flagging the differences
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Whenever we do an application upgrade, we have issues with prtf attributes
being updated incorrectly, not matching previous values.
Over time, prtf attributes on production get changed to meet new
production requirements.
These changes are not always mirrored back to the R&D LPAR, where the
source is.
My goal is to compare the prtf attributes from production LPAR to thos on
R&D LPAR, flag the differences.
One method
dump the production attributes to an outfile.
Slight issue here is that not all attributes are presented with one dspfd.
Need to do two.
DSPFD FILE(*ALLUSR/*ALL) TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PRTF)
OUTFILE (QGPL/ BRCPRTATR) OUTMBR (*FIRST *ADD)
DSPFD FILE(*ALLUSR/*ALL) TYPE(*SPOOL) OUTPUT(*OUTFILE) FILEATR(*PRTF)
OUTFILE (QGPL/ BRCPRTSPL) OUTMBR (*FIRST *ADD)
I then combine these two files into one file, BRCPRTOUT.
Send this file to R&D LPAR.
Repeat the above process on R&D LPAR.
Compare the two combined outfiles, flag the differences.
Anyone from the group do something similar, possibly with an simpler
process.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
