Examples

File Errors

Other than link error (MMO'LKE) and file full (MMO'FUL), all other errors reported by INMEMO in the POS variable will be standard AMOSL file service system errors. The relevant error codes are listed below. (These are defined in SYS.M68.)

Error

Description

Error

Description

2

insufficient free memory

16

file not open

3

file not found

18

bitmap kaput

5

device not ready

19

device not mounted

7

device error

20

invalid filename

8

device in use

24

insufficient queue blocks

9

illegal user code

27

remote is not responding

10

protection violation

28

file in use

11

write protected

29

record in use

12

file type mismatch

33

record not locked

13

device does not exist

34

record not locked for output

14

illegal block number

35

LOKSER queue is full

15

buffer not INITed

37

illegal record size

 

Most of these errors indicate some sort of system malfunction that may require a system reset or action by the system operator. Obviously, file full (MMO'FUL) requires that the memo file be expanded. You should first make sure that no other user is in the memo file and then expand it using the EXPMMO utility (described later). For illegal link errors (MMO'LKE), you will probably want to zero out LINK and write the primary data record back to the file to avoid having the error repeated over and over again. You may also want to run the FIXMMO, or better yet, the ANAMMO utility to determine the extent of the linkage damage and clean up the file.