Re: Problem with qshell cp command

No the lock message is different.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Scott Klement
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 01/12/2011 03:17PM
Subject: Re: Problem with qshell cp command

Hi Mark,

Is it possible that the destination file or directory is already in use
by another process/job?

I would've expected that to generate the message 'Resource busy' (rather
than 'Device Busy') but perhaps they use different error messages in
QShell vs. ILE...?


On 1/12/2011 9:24 AM, Mark Murphy/STAR BASE Consulting Inc. wrote:

Anyone know why the cp command would give a "Device Busy" result.  Source and target are in the IFS, no symbolic links or NFS.  Here is an example:

$ cp -R Prod BC
cp: BC/dispatcher.log.3: Device busy
cp: BC/dispatcher.log.2: Device busy
cp: BC/dispatcher.log.1: Device busy
cp: BC/dispatcher.log: Device busy
cp: BC/20091006/lib/pal-service-14.4.1-standalone.jar: Device busy
cp: BC/20091006/lib/plan-services-client-14.4.1.jar: Device busy
cp: BC/20091006/lib/poi-2.5.1.jar: Device busy
cp: BC/20091006/lib/rules-tools-14.4.1.jar: Device busy
cp: BC/20091006/lib/service-objects-14.4.1.jar: Device busy



Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx