(Subsystem 520)

Could not initialize SVIPC data structure (SVIPCERR 1)

A call to cb_init failed when attempting to initialize a semaphore associated with a SVIPC data structure.

Examine the process error stack for the cb_init error to determine cause.

SVIPC resource has been removed from the system (SVIPCERR 2)

A SVIPC resource on which a process was waiting (message queue or semaphore) was removed from the system before the wait condition was satisfied.

Application dependent.

SVIPC resource limits exceeded, cannot create (SVIPCERR 2)

A get() call failed because the configured or system-imposed maximums for this type of SVIPC resource have been exceeded; there are no available entries in the SVIPC Entry Table, a new resource cannot be created.

Remove SVIPC resources which are no longer used from the system. If configured limits do not exceed system-imposed maximums, they may be increased, but only if no resources of that type are currently allocated on the system.

Cannot create SVIPC resource IPC_EXCL; entry already exists (SVIPCERR 4)

A SVIPC get() call was made with the IPC_CREAT and IPC_EXCL flags specified, but an entry already existed for the specified key.

(Application dependent) Specify a different (unique) key on the get() call.

Invalid mode specified on SVIPC get() call; does not match existing entry's access mode (SVIPCERR 5)

A mode permissions mask was specified on a SVIPC get() call which is inconsistent (not a subset of and not equal to) with the mode mask with which the existing resource was created.

(Application dependent) Specify a mode mask which matches or is a subset of the mode mask for the existing SVIPC resource.

Nonexistent key specified on a SVIPC get() call (SVIPCERR 6)

A SVIPC get() call was made without IPC_CREAT specified, and no existing SVIPC resource entry was found with the specified key.

(Application dependent) Make sure the appropriate key was specified, or if a new resource should be created, make sure IPC_CREAT is specified in the flags.

An invalid id was specified on a SVIPC call (SVIPCERR 7)

The id specified on a SVIPC call was invalid. No entry exists with that id, or the resource associated with that id was removed from the system.

(Application dependent) Make sure that the appropriate id was specified on the SVIPC call. Verify that the associated resource still exists on the system.

A key value of IPC_PRIVATE cannot be specified on a ipcrm command (SVIPCERR 8)

An ipcrm command was issued with a key parameter, but the key was IPC_PRIVATE. Only global keys or a valid id may be specified with ipcrm.

If the resource was created with the IPC_PRIVATE key, then the id must be specified on the ipcrm command. Otherwise, the correct global key value (or id) must be specified.

The SVIPC resource associated with id is pending removal and cannot be accessed (SVIPCERR )

A SVIPC call was made with an id whose associated resource is in the process of being removed from the system (due to a previous remove command). The resource cannot be accessed.

Application dependent.

The SVIPC resource associated with key has been removed from the system (SVIPCERR 10)

During processing of a SVIPC get() request, a resource entry with a matching key was found, but another process removed the resource from the the system before the cb_lock semaphore for the entry could be obtained.

Application dependent.

The calling process for a SVIPC ctl() call does not have appropriate privilege or access to the associated resource (SVIPCERR 11)

A SVIPC ctl() was made with a command to alter an existing SVIPC resource, and the calling process was not the owner or the creator of the resource or does not have SM capability.

Application dependent. Make the ctl() call to alter or remove the existing resource from a process with a UID that matches the current owner or creator of the resource, or from a process that has SM capability.

Error accessing the SVIPC KPO pointer (SVIPCERR 12)

An error was encountered when attempting to access the SVIPC KPO pointer from a get_kpo_pointer call.

Examine the process error stack to determine the error encountered by get_kpo_pointer.

SVIPC KSO does not exist (SVIPCERR 13)

An attempt to access the SVIPC KSO failed; the pointer returned from get_kso_pointer was nil and the attempt to create the KSO failed.

Unexpected error. Examine the process error stack for possible cause.

SVIPC KPO does not exist (SVIPCERR 14)

An attempt to access the SVIPC KPO failed; the pointer returned from get_kpo_pointer was nil and the attempt to create the KPO failed.

Unexpected error. Examine the process error stack for possible cause.

Failed to create the SVIPC KPO (SVIPCERR 15)

An attempt to create the process local SVIPC KPO failed.

Examine the process error stack for other relevant error information to determine the cause of the failure.

Failed to create the SVIPC KSO or other global data (SVIPCERR 16)

An attempt to create the SVIPC KSO or related global data structure failed.

Examine the process error stack for the process reporting the error to determine the cause of the failure.

Failed to create SVIPC virtual space domain (SVIPCERR 17)

A call to create_virtual_space_domain failed when setting up the SVIPC global data structures.

Examine the process error stack to determine the cause of the create_virtual_space_domain failure.

Creation of SVIPC Entry Table failed. (SVIPCERR 18)

A call to create_object failed when setting up the SVIPC entry table global data structure.

Examine the process error stack to determine the cause of the create_object failure.

Creation of SVIPC global message frame pool failed. (SVIPCERR 19)

A call to create_object failed when setting up the SVIPC message frame pool global data structure.

Examine the process error stack to determine the cause of the create_object failure.

Creation of an SVIPC semaphore set failed. (SVIPCERR 20)

A call to create_object failed when creating a SVIPC semaphore set after a semget() call.

Examine the process error stack to determine the cause of the create_object failure.

Failed to queue a process waiting on a SVIPC resource. (SVIPCERR 31)

A call to put_wait_queue failed when attempting to queue a process on a wait queue associated with a SVIPC resource.

Examine the process error stack to determine the cause of the failure in put_wait_queue.

A signal or soft interrupt was received by a process queued on a SVIPC resource (SVIPCERR 32)

A SVIPC process wait (message queue or semaphore wait) was terminated by receipt of a signal or other soft interrupt, before the wait condition was satisfied.

Application dependent.

Failure occurred when attempting to wake a process from a SVIPC process wait (SVIPCERR 33)

A call to reply_to_waiter failed when attempting to wake a process queued to a SVIPC process wait queue for a SVIPC resource.

Examine the process error stack to determine the cause of the failure in reply_to_waiter.

Failure occurred when attempting to queue a process waiting on a SVIPC resource (SVIPCERR 34)

A process could not be queued on a SVIPC process wait queue because the cb_lock semaphore associated with the wait queue had not been obtained.

Internal SVIPC error. Report error to HP.

Invalid size specified on shmget() call (SVIPCERR 100)

The size parameter on a shmget() call was either outside of the acceptable configured range or (if the shared memory area already exists) did not match the size of the existing shared memory area.

Make sure the size specified is within the configured range for the system (min_shm_size and max_shm_size) or, if a shared memory area already exists for the specified key, that the size matches the existing size.

Invalid buf parameter passed to shmctl() (SVIPCERR 101)

The buf parameter passed to shmctl() was invalid or could not be accessed to perform the specified cmd.

Check that the buf structure was declared properly and specified properly on the shmctl() call.

Caller does not have appropriate privilege or access rights to perform a shmctl() IPC_STAT command (SVIPCERR 102)

The caller does not have read access for the SVIPC shared memory resource, and is not privileged (SM capability).

Ensure that the caller has appropriate privilege to perform the requested IPC_STAT command.

An invalid cmd was specified on a shmctl() call (SVIPCERR 103)

The cmd parameter on a shmctl() call was not valid.

Verify that an appropriate value is assigned to the cmd parameter.

SVIPC shared memory could not be frozen (SVIPCERR 104)

An error was encountered when attempting to freeze a SVIPC shared memory region into MPE/iX main memory. This functionality is not available on initial releases of SVIPC/iX.

If SHM_LOCK is supported on this release of MPE/iX, then examine the process error stack to determine the cause of the error returned from the MPE/iX freeze routine.

SVIPC shared memory could not be unfrozen (SVIPCERR 105)

An error was encountered when attempting to unfreeze a SVIPC shared memory region from MPE/iX main memory. This functionality is not available on initial releases of SVIPC/iX.

If SHM_UNLOCK is supported on this release of MPE/iX, then examine the process error stack to determine the cause of the error returned from the MPE/iX unfreeze routine.

The SVIPC shared memory region was not found (SVIPCERR 106)

The shmaddr value specifying an attached shared memory region was invalid.

Verify that the shmaddr parameter was correct

Process does not have access required for shmat() (SVIPCERR 107)

A process wishes to attach to a shared memory region, but does not have read access to the SVIPC resource.

Ensure that the calling process has appropriate privilege and access to the SVIPC resource.

Process does not have access required for shmat() (SVIPCERR 108)

A process wishes to attach to a shared memory region, but does not have write access to the SVIPC resource and SHM_RDONLY was not specified.

Make sure SHM_RDONLY is specified in the flags, if appropriate; otherwise, make sure the calling process has appropriate privilege and access to the SVIPC resource.

SHM_RND is not supported (SVIPCERR 109)

A process specified SHM_RND in the flags parameter of a shmat() call, but SHM_RND is not supported on MPE/iX.

Remove the SHM_RND specification from the flags parameter.

Invalid shmaddr specified on shmat() call (SVIPCERR 110)

A process specified a nonzero shmaddr value on a shmat() call, but shmaddr does not match the address of the existing shared memory area. MPE/iX does not allow the caller to specify an arbitrary attach address.

Make sure the shmaddr parameter is either zero or matches the address of the shared memory area exactly.

Failure occurred in shmat() call (SVIPCERR 111)

An error was encountered in MPE/iX procedure add_protectid_entry when attempting to process a shmat() request.

Examine the process error stack to determine the cause of the error in add_protectid_entry.

Failure occurred in a shmdt() call (SVIPCERR 112)

An error was encountered in MPE/iX procedure delete_protectid_entry when attempting to process a shmdt() request.

Examine the process error stack to determine the cause of the error in delete_protectid_entry.

Failure occurred in shmget () call (SVIPCERR 113)

An error was encountered in MPE/iX procedure allocate_pid when attempting to associate an MPE/iX pid with a shared memory region.

Examine the process error stack to determine the cause of the error in allocate_pid.

Could not allocate SVIPC shared memory (SVIPCERR 114)

An error was encountered in create_object when attempting to create a SVIPC shared memory region.

Examine the process error stack to determine the cause of the error in create_object.

Could not remove a SVIPC shared memory region (SVIPCERR 115)

An error was encountered in release_object when attempting to remove a SVIPC shared memory region.

Examine the process error stack to determine the cause of the error in release_object.

shmat() failed; process already attached (SVIPCERR 116)

A process attempted to attached to a shared memory region to which it was already attached. This is not allowed on MPE/iX.

Application dependent.

shmat() failed; process limit exceeded (SVIPCERR 117)

A process attempted to attach to a shared memory region but was already attached to the maximum allowable regions (256). There were no available entries in the associated KPO table.

Application dependent. Detach from another shared memory region in order to attach to a new shared memory region.

Invalid shmaddr specified on shmdt() call (SVIPCERR 118)

The shmaddr value specified on the shmdt() call did not correspond to a currently attached shared memory region for the process. No matching entry was found in the KPO shm_id_table.

Ensure that the shmaddr value passed on the shmdt() call is correct (same value returned from the previous shmat() call).

Invalid buf parameter on msgctl() call (SVIPCERR 200)

The buf parameter passed to msgctl() was invalid or could not be accessed to perform the specified cmd.

Check that the buf structure was declared properly and specified properly on the msgctl() call.

Caller does not have appropriate privilege or access rights to perform a msgctl() IPC_STAT command (SVIPCERR 201)

The caller does not have read access for the SVIPC message queue resource, and is not privileged (SM capability).

Ensure that the caller has appropriate privilege or access rights to perform the requested IPC_STAT command.

msgctl() failed; invalid cmd specified (SVIPCERR 202)

The cmd parameter on a msgctl() call is invalid or unrecognized.

Ensure that the cmd parameter is assigned a valid value.

Invalid msgsz parameter specified (SVIPCERR 203)

A msgsz value was specified that was negative or that exceeded the largest allowable message size configured for the system.

Make sure the msgsz parameter is positive and is within an acceptable range for the current SVIPC configuration.

msgrcv() failed; message is too large (SVIPCERR 204)

The message to be received from a msgrcv() call is larger than the user-specified buffer size (msgsz), and MSG_NOERROR was not specified in the msgflg parameter.

Application dependent. Specifying MSG_NOERROR in the msgflg allows the message to be truncated without an error indication.

msgsnd() failed; insufficient privilege or access rights (SVIPCERR 205)

A msgsnd() failed because the calling process does not have write access to the message queue, and is not privileged (SM capability).

Ensure that the calling process has appropriate access to the message queue.

msgrcv() failed; insufficient privilege or access rights (SVIPCERR 206)

A msgrcv() failed because the calling process does not have read access to the message queue, and is not privileged (SM capability).

Ensure that the calling process has appropriate access to the message queue.

msgsnd() failed; invalid msgp parameter (SVIPCERR 207)

The msgp buffer passed on a msgsnd() call is invalid or cannot be accessed for reading.

Ensure that the msgp structure is defined correctly and is passed correctly on the msnd() call.

msgsnd() failed; negative mtype specified (SVIPCERR 208)

The mtype value in the msgp structure was negative. This is invalid on a msgsnd() call (the mtype must be >=0).

Ensure that a nonnegative mtype value is specified in the msgp structure on a msgsnd() call.

msgrcv() failed; no message of appropriate type was found and IPC_NOWAIT was specified (SVIPCERR 209)

There were no messages of the type requested on the msgrcv() call queued to the message queue. The IPC_NOWAIT option was specified, so instead of queueing the process, an error is returned.

Application dependent.

msgsnd() failed; not enough room on the message queue for the message and IPC_NOWAIT was specified (SVIPCERR 210)

The message could not be sent because the configured maximum for bytes queued to a message queue would be exceeded.IPC_NOWAIT was specified so instead of queueing the process, an error is returned.

Application dependent.

msgsnd() failed; message frame allocation error (SVIPCERR 211)

An error occurred when attempting to allocate frames from the global SVIPC message frame pool.

Examine the process error stack to determine the cause of the frame allocation error.

Error occurred in SVIPC message frame deallocation (SVIPCERR 212)

An error occurred when attempting to deallocate message frames from a message queue and return them to the global SVIPC message frame pool.

Examine the process error stack to determine the cause of the frame allocation error.

Insufficient privilege to increase message queue size (SVIPCERR 213)

The calling process attempted to increase the message queue size in a msgctl() call, but does not have SM capability.

Ensure that the calling process has appropriate capability to reconfigure (increase) the global SVIPC message queue size configuration value.

msgrcv() failed; error processing message frame list (SVIPCERR 214)

An error was encountered while traversing the linked list of message frames associated with a large (>1K) message; the link was broken.

Report the error condition to HP, along with any other error information from the process error stack (and related process error stacks).

Invalid buf parameter on semctl() call (SVIPCERR 300)

The buf parameter passed to semctl() was invalid or could not be accessed to perform the specified cmd.

Check that the buf structure was declared properly and specified properly on the semctl() call.

Insufficient access rights or privilege to perform requested operation on SVIPC semaphore. (SVIPCERR 301)

A call to semctl() or semop() failed because the calling process does not have appropriate privilege or access to the SVIPC semaphore set.

Ensure that the calling process has appropriate access and privilege to perform the requested function.

semctl() failed; invalid cmd parameter (SVIPCERR 302)

The cmd parameter specified on a semctl() call was invalid.

Check that a valid value is being assigned to the cmd parameter for the semctl() call.

The arg parameter passed on a semctl() call is invalid or cannot be accessed (SVIPCERR 303)

An error was encountered when attempting to access the arg parameter passed on a semctl() call for a GETALL, SETVAL, or SETALL cmd.

Ensure that the arg structure was declared properly and was passed properly on the semctl() call.

semop() failed; invalid sembuf parameter (SVIPCERR 304)

The sembuf parameter passed on a semop() call was invalid or could not be accessed.

Ensure that the sembuf structure was declared properly and passed properly on the semop() call.

semget() failed; invalid nsems parameter (SVIPCERR 305)

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.

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.

semop() failed; invalid sops array element (SVIPCERR 306)

The sem_num specified in a sops array element was invalid (negative number or exceeded the largest index in the semaphore set).

Ensure that the sem_num values in the sops array specify valid elements in the semaphore set. The semaphore set uses 0-based indexing.

semop() failed; invalid nsops parameter (SVIPCERR 307)

The nsops parameter passed to semop() was invalid (negative number or exceeded configured maximums).

Ensure that the nsops parameter is within acceptable limits.

Failed to create SVIPC semaphore set (SVIPCERR 308)

An error occurred while attempting to create a SVIPC semaphore set in response to a semget() call.

Examine the process error stack to determine the cause of the creation failure.

semop() failed; value out of range (SVIPCERR 309)

The specified semop() values would cause the resulting semaphore value (or the semadj value, if SEM_UNDO was specified) to exceed configured limits.

Application dependent. If the semop() values are specified correctly, then ensure that the current SVIPC configuration will support the application.

semctl() failed; invalid semnum parameter (SVIPCERR 310)

The semnum parameter on a semctl() call did not identify a valid semaphore in the semaphore set. The value was out of range.

Ensure that the semnum specified is valid for the semaphore set specified.

semop() failed; invalid sem_op value (SVIPCERR 311)

The sem_op value specified in a sops array element exceeds the maximum allowable sem_op value in the SVIPC configuration settings.

Application dependent. If the sem_op value is valid, then ensure that the SVIPC configuration will support the application.

semop() failed; SEM_UNDO could not be processed (SVIPCERR 312)

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.

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.

semop() failed; process would block on the semaphore but IPC_NOWAIT was specified (SVIPCERR 313)

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.

Application dependent.

ipcrm failed; invalid type parameter (SVIPCERR 400)

The type parameter on the ipcrm interactive command was invalid. Must be an upper or lowercase Q, M, or S.

Ensure that a valid type is specified on the command line.

ipcs or setconfig failed; internal error (SVIPCERR 401)

An error was encountered when processing an interactive ipcs or setconfig command. Internal routine svipc_info encountered an error.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

ipcs or setconfig failed; internal error (SVIPCERR 402)

The info_arg1 parameter passed to internal routine svipc_info is invalid or cannot be accessed.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

ipcs or setconfig failed; internal error (SVIPCERR 403)

The info_key parameter passed to internal routine svipc_info is invalid or cannot be accessed.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

setconfig command failed; internal error (SVIPCERR 404)

An error was encountered by internal routine svipc_control when processing a setconfig command.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

setconfig command failed; internal error (SVIPCERR 405)

The ctrl_arg1 parameter passed to internal routine svipc_control on a setconfig command was invalid or inaccessible.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

setconfig command failed; internal error (SVIPCERR 406)

The ctrl_key parameter passed to internal routine svipc_control was invalid.

Unexpected error. Make sure the SVIPCUTL.PUB.SYS program file is valid and compatible with the SVIPC version on this MPE/iX release.

ftok() failed; invalid path parameter (SVIPCERR 407)

The path name string passed to ftok was invalid or inaccessible.

Ensure that the path name string variable is properly declared and is being passed properly in the ftok() call.

ftok() failed; file system error (SVIPCERR 408)

The ftok() failed because the flabelinfo intrinsic returned an error.

Examine the process error stack to determine the cause of the failure in flabelinfo.

Configuration of SVIPC shared memory failed (SVIPCERR 409)

A setconfig command to alter shared memory configuration failed because shared memory is currently in use on the system or the configuration value(s) specified is invalid or inconsistent.

Ensure that no SVIPC shared memory regions are currently allocated on the system before reconfiguring. Ensure that the configuration value(s) specified is within acceptable limits and does not conflict with other values.

Configuration of SVIPC message queues failed (SVIPCERR 410)

A setconfig command to alter message queue configuration failed because message queues are currently in use on the system or the configuration value(s) specified is invalid or inconsistent.

Ensure that no SVIPC message queues are currently allocated on the system before reconfiguring. Ensure that the configuration value(s) specified is within acceptable limits and does not conflict with other values.

Configuration of SVIPC semaphores failed (SVIPCERR 411)

A setconfig command to alter semaphore configuration failed because semaphores are currently in use on the system or the configuration value(s) specified is invalid or inconsistent.

Ensure that no SVIPC semaphore sets are currently allocated on the system before reconfiguring. Ensure that the configuration value(s) specified is within acceptable limits and does not conflict with other values.