AIPS does not readily safely quit, and so if a file is being written when the current process is suddenly killed, the file will remain open.
If you see this error of 'Could not Zap' and cannot resume the pipeline, then you will have to go into AIPS to clear the open file status first.
Run AIPS with aips notv
Enter the problematic user number. This can be found either as a -u flag of the python program causing the error, or as a random 4-digit string of numbers that will have been printed before running AIPS. Either way the Nextflow outputs of the process causing the error will tell you (check the log files in the work directory).
Type uc, a list of loaded files should be listed, with at least one of them having the status WRIT. This is the problem file.
Note the index of the problem file, and clear its status and zap:
getn X; clrstat; zap
AIPS does not readily safely quit, and so if a file is being written when the current process is suddenly killed, the file will remain open.
If you see this error of 'Could not Zap' and cannot resume the pipeline, then you will have to go into AIPS to clear the open file status first.
aips notvuc, a list of loaded files should be listed, with at least one of them having the status WRIT. This is the problem file.getn X; clrstat; zap