You can access files of bs2fs file systems using the same program interfaces as for when you access files of ufs file systems. However, in the event of an error the errno variable can contain additional values or values with a different meaning. The meaning of the various error numbers when you access bs2fs file systems is provided in the table below:
Error number | Meaning |
EAGAIN | A BS2000 file can temporarily not be accessed, e.g. because the file was opened by another process or because the connection to the pubset has been interrupted. |
EDOM | Internal interface error |
EFAULT | Internal processing error or invalid address (e.g. buffer address) |
EIO | DMS or LMSUP or PLAM reported I/O error |
EMACRO | DMS or LMSUP or PLAM reported processing error |
ENAME | Part of the path name is not a valid BS2000 file name, PLAM type name or element name (the latter possibly including a valid version identifier) |
ENODEV | The volume or the device cannot be accessed |
ENOEXEC | An LLM element which is to be edited does not have an LLM structure. |
ENONET | Pubset is not available, possibly because of a problem in the MSCF network |
ENOSTR | An attempt is being made to access a BS2000 file which does not have a file type |
ENOSUBSYS | No connection could be established to LMSUP or PLAM |
ENOSYS | Operation not supported by the bs2fs file system |
ENXIO | File was displaced (migrated) |
EOPR | Operation is not supported for the specified file |
ESRCH | No bs2fs daemon exists which could perform the accesses to the BS2000 object. Response: notify the system administrator |
Error values such as EIO, ENOEXEC or ENOSPC can also be set for close if the file was opened in write mode and could not be written back properly to the BS2000 file or the library element. In these cases the copy is retained in the bs2fs container.