Dear Angel,

There is a mechanism built in ADF to protect files from writing from
more than one process at the same time, which may happen in parallel
environment. This mechanism is triggered by trying to write to file that
was not created by this process but existed before. This explains the
difference between creating a new file and adding data to an existing
TAPE41 file. This mechanism can be fooled by renaming the file to
TAPE41__0 and then running the command as:
udmpkf TAPE41__0 < nameASCIIfile

The __0 suffix tells ADF (and other programs that are using KF file
format) that the file is accessed exclusively by this process and,
hence, can be safely written to.

I hope this solves the problem for you.

Best regards,
Alexei Yakovlev
SCM

mañanes wrote:

> In a LINUX system, we are trying to include an ASCII file (a modified
> density) in a TAPE41.
>
> The answer of the command
>
> udmpkf TAPE41 < nameASCIIfile
>
> is
>
> kf error : write to shared file
>
>
>
> and the file is not included in the TAPE41.
>
>
>
> On the other side, we can create a NEW TAPE41 in which udmpf is
> able to put the ascii file, but when we append this new file to the
> old one the applications pkf , dmpkf are not able to see the new
> part of the file.
>
>
>
> Do you have any suggestion ?. Thank you.
>
>
>
> Dr Angel Mañanes Pérez
>
> Departamento de Física Moderna . Facultad de Ciencias
>
> Universidad de Cantabria
>
> Avda. Los Castros s/n . 39005 Santander. Spain
>
> Tlf: 942 201454 Fax: 942 201402 Email: mananesa_at_unican.es
>
>
>

Received on 2005-10-04 11:07:14