Object ownership during CRTDUPOBJ

Hi,

Situation:
Create duplicate objects of a physical file and its logicals, using CRTDUPOBJ OBJ(FILE*) FROMLIB(LIB1) OBJTYPE(*FILE) TOLIB(LIB2) DATA
(*YES).

File information:
Physical file size: 1.8 GB
Logical file 1 size: 500MB
Logical file 2 size: 100MB

Userprofile issuing the command (XXXXXXXX) has:
MAXSTG = 250000
GRPPRF = SOMEGRP
OWNER = *GRPPRF

Group profile SOMEGRP has:
MAXSTG = *NOMAX

Result:
Physical file is created just fine, including the data.
Logical file 2 is created just fine.
Logical file 1 is created, but contains no members because of:
- MCH4601: Storage limit overflow for user profile XXXXXXXX.
- CPF3217: Not enough storage to create file LOGICAL1 or add member to file.

Since the new objects being created will get the groupprofile as owner, which has *NOMAX as storage limit, I expect no problems with storage limit on the user profile. This is true for the physical file. Why is it that the logical that is larger than the max storage limit of the user, but smaller than the physical that copied just fine, gives an error while adding the member?

The only logical explanation I can think of, is that both the physical and logical files are first created with user profile XXXXXXXX as owner, but with the physical file the owner is changed to the groupprofile before adding the data, and the access path is being build BEFORE changing the object owner.

I could not find any information on this in the documentation. Does anyone know if my explanation is correct? Or know why this is happening? We are on version 7.1.

Regards,
Erwin Donker