Page History

The most common causes of a "make new or amended file definition operational" job failure are described in detail below:

The Renamed "$$" File Has Not Been Deleted

When LANSA re-creates a file it renames the existing version of the file by appending the prefix "$$" to the name. Thus existing file CUSMST would be renamed $$CUSMST before the new version of CUSMST is created.

...

1.  Check that the new file has been re-loaded correctly (i.e. it actually contains the correct data).
2.  Delete the "$$" version. Note that "$$" versions are only created when it is necessary to delete and re-create the physical file. Thus not all file re-creation jobs will actually produce a "$$" version of the file.

The File Cannot Be Allocated for Exclusive Use

The file re-creation job attempts to place an exclusive lock on the file being re-created. If any other user or job in the system has the file open then the re-creation job will not be able to gain an exclusive lock and will fail. This situation is indicated clearly by messages on the job log.

...