| 2520-001 | The HA_GS interface has already been initialized. |
Explanation: This process has already successfully executed ha_gs_init().
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-002 | A responsiveness callback function must be specified. |
Explanation: Specify a responsiveness callback function on the ha_gs_init() call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-003 | A delayed error callback function must be specified. |
Explanation: Specify a delayed callback function on the ha_gs_init() call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-004 | A responsiveness counter of non-zero length must be specified. |
Explanation: A counter length which is not valid was specified on the ha_gs_init() call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-005 | The HA_GS interface has not been initialized. |
Explanation: The program attempted to execute a group services interface before it has successfully executed ha_gs_init().
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-006 | Unable to allocate memory for group information. |
Explanation: A malloc call was not successful while running within the group services library.
User Response: Restart the application. If this continues to happen, increase the amount of memory available to the application.
| 2520-007 | A merge callback function must be specified. |
Explanation: Specify a merge callback function on the ha_gs_init() call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-008 | Batch Control specified is not valid. |
Explanation: A batch control flag which is not valid was specified on an ha_gs_init() call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-009 | Number of Phases specified is not valid. |
Explanation: A batch control flag which is not valid was specified on a Group Services interface call.
User Response: Refer to the interface description in the Group Services Programming Guide and Reference manual that the application attempted when it received this error.
| 2520-010 | Source Reflection Number of Phases specified is not valid. |
Explanation: A number of phases flag which is not valid was specified on an ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-011 | Group Default Vote specified is not valid. |
Explanation: A group default value which is not valid was specified on an ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-012 | Group name group name can be no longer than maximum length characters. |
Explanation: The group name specified for an ha_gs_join() call is too long.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference.
| 2520-013 | Unknown Notification Message, type=notification type, length=notification length. |
Explanation: A notification which was not valid was received by a Group Services application.
User Response: Contact the IBM Support Center.
| 2520-014 | Provider token provider token does not exist. |
Explanation: A Group Services interface was called and the given provider token does not represent any current providers.
User Response: Refer to the Group Services Programming Guide and Reference manual.
| 2520-015 | Vote submitted, but this group is not in a voting protocol. |
Explanation: The ha_gs_vote() interface was called for a group that is not currently in a voting protocol.
User Response: Refer to ha_gs_vote() in the Group Services Programming Guide and Reference manual.
| 2520-016 | Invalid socket control flag given. |
Explanation: A socket control flag which is not valid was specified on a Group Services interface call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-017 | Invalid dispatch control flag given. |
Explanation: A dispatch control flag which is not valid was specified on a Group Services interface call.
User Response: Refer to ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-018 | Invalid vote value given. |
Explanation: A vote value which is not valid was given on a call to ha_gs_vote().
User Response: Refer to ha_gs_vote() in the Group Services Programming Guide and Reference manual.
| 2520-019 | Invalid default vote value given. |
Explanation: A default vote value which is not valid was given on a call to ha_gs_vote().
User Response: Refer to ha_gs_vote() in the Group Services Programming Guide and Reference manual.
| 2520-020 | Invalid subscription control flag value given. |
Explanation: A subscription control flag which is not valid was given on a call to ha_gs_subscribe().
User Response: Refer to ha_gs_subscribe() in the Group Services Programming Guide and Reference manual.
| 2520-021 | unsupported interface name is not currently supported. |
Explanation: The specified interface name is not supported.
User Response: Modify the application to not call this interface.
| 2520-022 | Client joins to group named group name are not allowed. |
Explanation: The group name specified for an ha_gs_join() call is the name of a reserved group to which joins are not allowed.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-023 | Group named group name may not be specified as a source group name. |
Explanation: The group name specified for an ha_gs_join() call is the name of a reserved group which may not be used a source group name.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-024 | Source group name, source group name, can be no longer than maximum length characters. |
Explanation: The source group name specified for an ha_gs_join() call is too long.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-025 | Invalid Deactivation Phase Specified. |
Explanation: A deactive phase which is not valid was specified on a Group Services ha_gs_expel() call.
User Response: Refer to the ha_gs_expel() description in the Group Services Programming Guide and Reference manual that the application attempted when it received this error.
| 2520-026 | Cannot determine current client working directory. |
Explanation: While processing ha_gs_init(), the Group Services library could not determine the current client process working directory.
User Response: Refer to the interface description in the Group Services Programming Guide and Reference manual that the application attempted when it received this error.
| 2520-027 | Must specify at least one provider for an expel. |
Explanation: You did not specify any providers to expel on an ha_gs_expel() call.
User Response: Refer to the ha_gs_expel() description in the Group Services Programming Guide and Reference manual that the application attempted when it received this error.
| 2520-028 | Provider provider instance number, provider node number appears twice in expel list. |
Explanation: A provider was listed twice to be expelled on an ha_gs_expel() call.
User Response: Refer to the ha_gs_expel() description in the Group Services Programming Guide and Reference manual that the application attempted when it received this error.
| 2520-040 | Client compiled against later release library. |
Explanation: The client program was compiled and linked against a later version of the Group Services library, and cannot be run on this node.
User Response: Install the latest Group Services release on this node, or recompile the client program against the level of the Group Services library on this node.
| 2520-041 | Client cannot issue ha_gs_goodbye(). |
Explanation: Client was compiled against an earlier level of the Group Services library.
User Response: Install the latest Group Services release on this node and recompile the client program against the level of the Group Services library on this node.
| 2520-042 | Group contains back-level providers thus ha_gs_goodbye() cannot be called. |
Explanation: Other clients in the group were compiled against an earlier level of the Group Services library.
User Response: Install the latest Group Services release on all nodes, and recompile the client program against the level of the Group Services library on all nodes.
| 2520-043 | A subscription callback function must be specified. |
Explanation: Specify a subscription callback function on the ha_gs_subscribe() call.
User Response: Refer to ha_gs_subscribe() in the Group Services Programming Guide and Reference manual.
| 2520-044 | A protocol n_phase callback function must be specified. |
Explanation: Specify a protocol n_phase callback function on the ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-045 | A protocol approved callback function must be specified. |
Explanation: Specify a protocol approved callback function on the ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-046 | A protocol rejected callback function must be specified. |
Explanation: Specify a protocol rejected callback function on the ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-047 | An announcement callback function must be specified. |
Explanation: Specify an announcement callback function on the ha_gs_join() call.
User Response: Refer to ha_gs_join() in the Group Services Programming Guide and Reference manual.
| 2520-048 | The cu_get_cluster_info() returns an error error number. |
Explanation: Although the program attempted to get the cluster name and ID to connect the group services daemon, the cluster utility API returns an error.
User Response: Refer to cu_get_cluster_info() and ha_gs_init() in the Group Services Programming Guide and Reference manual.
| 2520-201 | Cannot remove service entry service_name from services_file. |
Explanation: Either the service name service_name was not found in the services-file, or the service_name could not be removed from the services file. The /tmp directory or the file system containing service_file could be full.
User Response: Add the service name before deleting it, or ensure that the file systems are not full.
| 2520-202 | Cannot determine node number. |
Explanation: On the SP, every node has it's node number stored in the ODM at install time. This node number could not be retrieved.
User Response: Install the node again.
| 2520-203 | Cannot determine syspar name. |
Explanation: The system partition for this node could not be determined. The most likely cause is that the SDR could not be reached.
User Response: Validate that the SDR is running and is operating correctly.
| 2520-204 | Cannot determine the IP address or code version for system partition syspar_name. |
Explanation: On the SP, every node should be in one system partition. The node on which you ran the command, is in the system partition syspar_name, but vital information, such as the IP address or code version, cannot be determined. The SDRGetObjects -x -G Syspar syspar_name==syspar-name ip_address code_ve command was not successful.
User Response: Validate that the SDR is running and is reachable. Properly configure the system partition, and try the command again.
| 2520-205 | Port number not found for subsystem subsystem_name. |
Explanation: The SDRGetObjects Syspar_ports subsystem==subsystem name port command was not successful.
User Response: Run this command on the control workstation in the partition to which this node belongs, and try the command again on the node.
| 2520-206 | Cannot register service service_name, protocol protocol, port port_number. |
Explanation: The subsystem being installed by the command was not able to install the specified service name service_name protocol protocol port number port_number in the /etc/services directory, which is required for the subsystem to operate.
User Response: If there is a port number specified in the error message, verify that this port number is not being used by another subsystem. If a port number is not specified in the error message, all of the port numbers that this command selected were already in use.
| 2520-207 | daemon_file_name is not executable. |
Explanation: The daemon file name daemon_file_name must be an executable file to allow the subsystem being installed by the command to operate. The the daemon file name daemon_file_name may not exist.
User Response: As root, run chmod +x daemon_file_name and try the command again, or run installp again to install the subsystem.
| 2520-208 | The subsystem_name subsystem must be stopped. |
Explanation: Stop the subsystem subsystem_name to allow the specified command to operate on it.
User Response: As root, run stopsrc -s subsystem_name and try the command again.
| 2520-209 | Could not add subsystem_name to resource_controller. |
Explanation: The specified command was not successful defining the subsystem name subsystem_name to the resource controller resource_controller. If the resource controller is inittab, mkitab subsystem name was not successful. If resource controller is SRC, mkssys -s subsystem name was not successful.
User Response: Fix what caused the resource controller command listed above to not succeed and try the command again.
| 2520-210 | Cannot create object in SDR_object_class_name for object_attributes. |
Explanation: The specified command was not successful creating an object in the SDR class SDR_object_class_name with the attributes specified by object_attributes.
User Response: The command generates an error message, which appears prior to this message. Correct the problem indicated by the prior message and run this command again.
| 2520-211 | Internal error. |
Explanation: The specified command encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2520-212 | Cannot verify registration of service name service name, protocol protocol , port port number. |
Explanation: The subsystem being installed by command-name was unable to verify the installation of the specified service-name protocol port number in /etc/services, which is required for the subsystem to operate. If the machine is an NIS client, you may have to update the NIS master server's services map to reflect this change.
User Response: If the machine is an NIS client, copy the entry with the specified service name, protocol, and port number from the local /etc/services file into the same file on the NIS master server and do a NIS make on the NIS master server.
| 2520-213 | Cannot get DCE credentials for SDR access. |
Explanation: command-name was not successful in getting DCE credentials for SDR access.
User Response: DCE subsystem may not work correctly. Check /usr/lpp/ssp/bin/dsrvtgt.
| 2520-214 | Startup parameter line is HACMP/ES 4.2.x style. Assuming HAES domain. |
Explanation: Startup parameter line is HAES 4.2.x style.
User Response: Group Services daemon will assume its environment as HACMP/ES.
| 2520-215 | cldomain is not found, assuming HAES 4.2, use SP partition name. |
Explanation: cldomain cmd is not found. Assume HAES 4.2.x style.
User Response: Group Services daemon will assume its environment as HACMP/ES.
| 2520-216 | Domain name domain name on parameter line will be used. |
Explanation: Domain name on command line will be used.
User Response: Group Services daemon will assume its environment as HACMP/ES.
| 2520-217 | Cannot initialize FFDC environment, return code = return code. |
Explanation: FFDC initialization error.
User Response: Check if the FFDC environment is working correctly.
| 2520-218 | Cannot get system partition name with spget_syspar --n. |
Explanation: Unable to obtain the syspar name from spget_syspar --n.
User Response: Check the syntax of the spget_syspar command.
| 2520-219 | Aggregate IP group on /dev/ml0 under domain domain_type is not supported. |
Explanation: Aggregate IP group is not supported for the given domain.
User Response: Only the PSSP domain is supported for Aggregate IP group.
| 2520-220 | SW_GROUPIE_AGGIP_CFG is not defined by hagsglsmd. |
Explanation: The environment variable SW_GROUPIE_AGGIP_CFG is not defined
User Response: Check the version of script hagsglsm and the daemon hagsglsmd.
| 2520-221 | command-name Cannot retrieve Aggregate_IP from SDR. |
Explanation: The command-name failed to retrieve an object Aggregate_IP in the SDR class.
User Response: An error message is displayed prior to this message by the failing SDR command. Correct the problem indicated by the error message and rerun this command.