Re: Getting CPD3216 "SIZE less than current size for file XTRA9" when SIZE parm isn't specified on CHGPF -- MIDRANGE-L

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

Subject: Re: Getting CPD3216 "SIZE less than current size for file XTRA9" when SIZE parm isn't specified on CHGPF
From: Marc Rauzier <marc.rauzier@xxxxxxxxx>
Date: Thu, 27 Jan 2022 19:35:20 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Le 27/01/2022 à 19:24, Dan a écrit :

Does this make any sense? Command is:
QSYS/CHGPF FILE(OI9LIB/XTRA9) SRCFILE( OI9LIBS/QDDSSRC) SRCMBR( XTRA9)

When I prompt the CHGPF command, the default for SIZE is *SAME.

In that case, *SAME might refer to initial size, and your file got some increments?

What is the initial size versus the current one?

Not sure at all, just thinking.

- Dan

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Getting CPD3216 "SIZE less than current size for file XTRA9" when SIZE parm isn't specified on CHGPF , Dan

This mailing list archive is Copyright 1997-2025 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.