MPE/iX Error Messages Manual Vol 2 (32650-90879)

208 Chapter6
Volume II Chapter 5
SVIPC
(SVIPCERR 310)
CAUSE The semnum parameter on a semctl() call did not identify
a valid semaphore in the semaphore set. The value was
out of range.
ACTION Ensure that the semnum specified is valid for the
semaphore set specified.
311 MESSAGE semop() failed; invalid sem_op value
(SVIPCERR 311)
CAUSE The sem_op value specified in a sops array element
exceeds the maximum allowable sem_op value in the
SVIPC configuration settings.
ACTION Application dependent. If the sem_op value is valid, then
ensure that the SVIPC configuration will support the
application.
312 MESSAGE semop() failed; SEM_UNDO could not be
processed (SVIPCERR 312)
CAUSE SEM_UNDO was specified for one or more operations in
the semop() call and the sem_id_table in the KPO was full;
the SEM_UNDO could not be processed. Undo operations
for up to 64 semaphores can be tracked.
ACTION Application dependent. If an application must
simultaneously operate on more than 64 semaphores (with
SEM_UNDO), this cannot be supported by the current
SVIPC implementation on MPE/iX.
313 MESSAGE semop() failed; process would block on the
semaphore but IPC_NOWAIT was specified
(SVIPCERR 313)
CAUSE The operation(s) requested in the semop() call would result
in a process block on the related semaphore(s), but
IPC_NOWAIT was specified. An error is returned to the
caller.
ACTION Application dependent.
400 MESSAGE ipcrm failed; invalid type parameter
(SVIPCERR 400)
CAUSE The type parameter on the ipcrm interactive command
was invalid. Must be an upper or lowercase Q, M, or S.
ACTION Ensure that a valid type is specified on the command line.
401 MESSAGE ipcs or setconfig failed; internal error
(SVIPCERR 401)
CAUSE An error was encountered when processing an interactive
ipcs or setconfig command. Internal routine svipc_info
encountered an error.