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

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

Hi Marc,

Hello Dan

The file currently has 1900000 records in it. I am waiting for the DSPFD
listing from the client. Regardless, the existing file's SIZE attributes
(Initial number of records, Increment number of records, and Maximum
increments) would have to accommodate the number of records already in the
file. I think, anyway.

- Dan

I ran a quick test and cannot reproduce the message. The file was created with 1 as initial number of records, 1 as increment number and 1 as maximum number of increments. Then, I inserted 3 records so that 2 increments were added.

Member size SIZE

  Initial number of records . . . . . . . :                     1
  Increment number of records . . . . . . :                1
  Maximum number of increments  . . . . . :                1
Current number of increments  . . . . . . : 2
Record capacity . . . . . . . . . . . . . : 3
Current number of records . . . . . . . . : 3

I changed the source definition (unique field size incremented from 10 to 11).

4 > CHGPF FILE(QTEMP/TEST) SRCFILE(DIMARCO1/QDDSSRC) SIZE(*SAME *SAME *SAME)
    3 records copied from member TEST.
    File TEST in library QTEMP changed.

However, I have noticed that when prompting CHGPF command for the file, it displays the initial size values not the current ones.

                         Change Physical File (CHGPF)

Type choices, press Enter.

Physical file  . . . . . . . . . FILE         > TEST
  Library  . . . . . . . . . . .              >   QTEMP
System . . . . . . . . . . . . . SYSTEM         *LCL
Source file  . . . . . . . . . . SRCFILE        *NONE
  Library  . . . . . . . . . . .
Expiration date for member . . . EXPDATE        *NONE
Maximum members  . . . . . . . . MAXMBRS        1
Access path size . . . . . . . . ACCPTHSIZ      *SAME
Access path maintenance  . . . . MAINT          *SAME
Access path recovery . . . . . . RECOVER        *SAME
Force keyed access path  . . . . FRCACCPTH      *SAME
Member size:                     SIZE
  Initial number of records  . .                1
  Increment number of records  .                1
  Maximum increments . . . . . .                1
Allocate storage . . . . . . . . ALLOCATE       *NO


Mystery is still here. Because running the command without specifying SIZE succeeds as well.

4 >    STRSEU SRCFILE(DIMARCO1/QDDSSRC) SRCMBR(TEST) OPTION( 2)
    Member TEST in file DIMARCO1/QDDSSRC changed with 2 records.
4 > CHGPF FILE(QTEMP/TEST) SRCFILE(DIMARCO1/QDDSSRC)
    3 records copied from member TEST.
    File TEST in library QTEMP changed.

On Thu, Jan 27, 2022 at 1:35 PM Marc Rauzier <marc.rauzier@xxxxxxxxx> wrote:

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

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com