I know we can change the command defaults but it is just short of requiring
stone tablets if you get my drift. This was done in the past and when they
did an OS upgrade, they didn't change them again.
My thought is why go through the command default hassle if I can just change
the types to remove the 38 and make them like the other 99% of the system?
I am in control of my source and can easily change its types but I have no
ability to change the commands myself.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Tuesday, September 3, 2019 11:27 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: PF/LF vs PF38/LF38
Why not change the system defaults for CRTPF.
We do this for several commands.
First we copy the original command to a library we created in front of QSYS.
CHGCMDDFT CMD(SYSCHG/crtpf) NEWDFT('size(*nomax *n *n)') CHGCMDDFT
CMD(SYSCHG/CRTPF) NEWDFT('REUSEDLT(*yes)')
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Tuesday, September 03, 2019 10:54 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: PF/LF vs PF38/LF38
The default compile options is the main reason that I want to change these.
The company changed the default for MAXMBRS on the PF and LF commands to
*NOMAX (this is an IP shop) but not the PF38 and LF38 commands (it is still
1) and it has bit me a few times.
The document you included is counting the PF38 files but no idea why. Maybe
it was just an example value to show that you could pull.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Tuesday, September 3, 2019 10:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: PF/LF vs PF38/LF38
IDK about any "weirdness". Some cursory searching shows a few things.
Pf-src vs pf38-src generally works better in RDi searches but there are work
arounds.
Default compile options change between pf38-src and pf-src.
Now, when you are talking about non source files...
There is a performance document which seems to single out pf-38 but doesn't
say why. (Search the document for 38.) I wonder if it has anything to do
with its later recommendation to change to bigger page size on index?
https://www.tug.ca/MoMHandouts/2014-03-19/DB2%20for%20i%20Utilizing%20more%2
0efficiently.pdf
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
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Tuesday, September 3, 2019 10:23 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: PF/LF vs PF38/LF38
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
We have some files defined as PF38 and LF38. Is there anything I need to
know about or beware of if I change them to PFs and LFs? I know there is
weirdness about a CLP38 but not sure about the PF38 and LF38.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.