This can be implementation detail specific, so consider a safer design to handle the starting of the import only after successful completion of export, possibly by smarter scheduling or different scripting.
If you start a Db2 import from IXF, and then start a Db2 export to the same IXF, then currently supported versions of Db2-LUW clients should fail the export with SQL3001c (i/O error opening the output file) for local file systems.
If you start an export to IXF, and then start an import from that same IXF before the export has completed, then currently supported versions of Db2-LUW clients should fail the import again with SQL3030C (i/o error opening the input file) at least for local file systems.
However, behaviour can vary with operating-system, the file-system hosting the input/output files, file-system mount options etc, and of course bugs are unavoidable. For those reasons, consider a more robust design.