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

Chapter 6 207
Volume II Chapter 5
SVIPC
invalid or could not be accessed.
ACTION Ensure that the sembuf structure was declared properly
and passed properly on the semop() call.
305 MESSAGE semget() failed; invalid nsems parameter
(SVIPCERR 305)
CAUSE The nsems parameter passed on a semget() call exceeded
configured SVIPC limits, or, if a semaphore set already
existed for the key, did not match the number of
semaphores in the existing set.
ACTION Ensure that the nsems parameter is within valid limits
and (if the semaphore set exists) matches the number of
semaphores in the existing semaphore set.
306 MESSAGE semop() failed; invalid sops array element
(SVIPCERR 306)
CAUSE The sem_num specified in a sops array element was
invalid (negative number or exceeded the largest index in
the semaphore set).
ACTION Ensure that the sem_num values in the sops array specify
valid elements in the semaphore set. The semaphore set
uses 0-based indexing.
307 MESSAGE semop() failed; invalid nsops parameter
(SVIPCERR 307)
CAUSE The nsops parameter passed to semop() was invalid
(negative number or exceeded configured maximums).
ACTION Ensure that the nsops parameter is within acceptable
limits.
308 MESSAGE Failed to create SVIPC semaphore set
(SVIPCERR 308)
CAUSE An error occurred while attempting to create a SVIPC
semaphore set in response to a semget() call.
ACTION Examine the process error stack to determine the cause of
the creation failure.
309 MESSAGE semop() failed; value out of range (SVIPCERR
309)
CAUSE The specified semop() values would cause the resulting
semaphore value (or the semadj value, if SEM_UNDO was
specified) to exceed configured limits.
ACTION Application dependent. If the semop() values are specified
correctly, then ensure that the current SVIPC
configuration will support the application.
310 MESSAGE semctl() failed; invalid semnum parameter