Re: Dealing with CPE3029 in CPYFRMIMPF

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Sometimes the QSH copy command (see Patrik's response) doesn't care about
the locks.  I often use it to gather logs that are locked when I need to
send those to IBM (or HCL for Domino).  Actually the latter is more likely.

See also
https://www.ibm.com/docs/en/i/7.5.0?topic=services-ifs-object-lock-info-table-function

Yet another reason I'm developing a strong preference of stored procedures
over CL.

On Thu, Aug 28, 2025 at 4:14 PM mlazarus <mlazarus@xxxxxxxxxxxx> wrote:

>   Does anyone have a good way of dealing with an error thrown by the
> Copy From Import File (CPYFRMIMPF) command:
>
> Message ID . . . . . . :   CPFA0D4
> Message . . . . :   File system error occurred.  Error number 3029.
> Cause . . . . . :   File system experienced an unexpected error. Error
> number
>    3029 was received.
>
> Error 3029 points to:
>
> Message ID . . . . . . . . . :   CPE3029
> Message file . . . . . . . . :   QCPFMSG
>    Library  . . . . . . . . . :     QSYS
>
> Message . . . . :   Resource busy.
> Cause . . . . . :   An attempt was made to use a system resource that is
> not
>    available at this time.
>   This occurs when the file is open elsewhere.  The situation is that
> there are .csv files in the IFS that might be open in Excel.  All the
> program is attempting to do is copy the data into a PF.  It seems to
> want an exclusive lock.  Is there a way to tell it not to require that
> level of a lock?
>
>   This is extra strange to me because other commands such as MOV or REN
> seem to work fine, even if the file is open in Excel.  I think that
> those command *should* throw an error when the file is in use!
>
>   The original message is sent as a diagnostic message, so it can't be
> monitored.  Only the final message: "CPF2817 Copy command ended because
> of error" is an escape message.  This is a generic message for any error
> in this command.  I can of course monitor the escape and then receive
> the previous message, but I was hoping for a more elegant solution.  TIA.
>
>   -mark
> --
> 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.