Data Exchange Services "0B100xxx"

Table 1 lists the condition codes that are returned if there is an error with the following INGHWCMD functions:

  • ACTIVATE
  • APROF
  • CCNTL
  • CBU
  • CTRLCONS
  • DEACTIVATE
  • EXTERNAL
  • GETISTAT
  • GETSINFO
  • GETSSTAT
  • ICNTL
  • INITCOM
  • LOAD
  • OOCOD
  • RESERVE
  • RESTART
  • START
  • STOP
  • SYSRESET
  • TERMCOM

The condition code data "xxx" prefixed by 0B100 is returned as part of the following response messages, with a status value of REJECTED or FAILED:

  • AOFA0001
  • AOFA0002
  • AOFA0004
  • AOFA0006
  • AOFA0007
  • AOFA0017
  • AOFA0018
  • AOFA0020

For additional return code information see the section Data Exchange API Call Return Codes, in the appendix API Return Codes of the most current release of IBM Z® SNMP Application Programming Interfaces.

Table 1. Data Exchange Services Condition Codes
Condition Code Error String
001 HWMCA_DE_NO_SUCH_OBJECT This condition indicates that an object (CPC, Image, Profile) or an associate attribute cannot be found for this request in the SNMP MIB data base of the SE or HMC. A possible cause can be that an object has been requested that is not available on this CPC's type or CPC's micro code level.

Additional information for INITCOM requests:

  • If this condition code is returned from an INITCOM request, a Set request for the console object itself did not work. A possible cause is an API configuration problem on the target SE or HMC.
    1. The community name settings in the SE or HMC may not allow access from your location due to an invalid netmask specification.
    2. (BCPii only) Make sure that the community name that is specified in the Enable API window is also defined in the SNMP Settings window and has the IP address of the first LAN adapter of the SE defined with it. This information is valid only for SE Workplace versions 1.6.2–1.8.2.
002 HWMCA_DE_INVALID_DATA_TYPE
003 HWMCA_DE_INVALID_DATA_LENGTH
004 HWMCA_DE_INVALID_DATA_PTR
005 HWMCA_DE_INVALID_DATA_VALUE If this condition code is returned from an ICNTL request, the variable value is not accepted by the HW. This means either the value is below or above a range of accepted values (such as a negative value, where only 0 or positive values are allowed), or a certain variable value conflicts with the setting of a related variable. If, for example, the value of the initial processing weight, PWI, is set below the value of the minimum processing weight, PWMN this request fails with a condition code of 005.
006 HWMCA_DE_INVALID_INIT_PTR
007 HWMCA_DE_INVALID_ID_PTR
008 HWMCA_DE_INVALID_BUF_PTR
009 HWMCA_DE_INVALID_BUF_SIZE
010 HWMCA_DE_INVALID_DATATYPE_PTR
011 HWMCA_DE_INVALID_TARGET
012 HWMCA_DE_INVALID_EVENT_MASK
013 HWMCA_DE_INVALID_PARAMETER
014 HWMCA_DE_READ_ONLY_OBJECT
015 HWMCA_DE_SNMP_INIT_ERROR This is a condition code that can be retried.
016 HWMCA_DE_INVALID_OBJECT_ID
017 HWMCA_DE_REQUEST_ALLOC_ERROR
018 HWMCA_DE_REQUEST_SEND_ERROR For SNMP sessions only: If possible, enable the INGHWCOM trace and repeat the request. Additional TCP/IP error information will be in an error message (EDC) from the LE runtime environment. Have the z/OS LE Run-Time Messages manual available for reference.
019 HWMCA_DE_TIMEOUT For SNMP sessions only: If possible, enable the INGHWCOM trace and repeat the request. Additional TCP/IP error information will be in an error message (EDC) from the LE runtime environment. Have the z/OS LE Run-Time Messages manual available for reference. Verify if the network address and the network mask specified in the SE/HMC for the community name are valid. Address field and mask field are logically ANDed. If the result is 0, the request may fail with a TIMEOUT. Note that address and mask fields positions that are both 0 are not ANDed.
020 HWMCA_DE_REQUEST_RECV_ERROR
021 HWMCA_DE_SNMP_ERROR Check that the SNMP API is enabled on the SE/HMC. Check if the SNMP community name access is set to READ & WRITE.

For BCPii connections check if the loopback address 127.0.0.1 is defined to SNMP and to TCP/IP. On the SE use the Network Diagnostic Information to determine this.

For GET*, ICNTL, or APROF(Profile) requests this error may also indicate one of the following:
  • (1) - Same as 005 HWCA_DE_INVALID_DATA_VALUE
  • (2) - Same as 001 HWCA_DE_NO_SUCH_OBJECT
  • (3) - Error in SE/HMC microcode for an object attribute used in the request
022 HWMCA_DE_INVALID_TIMEOUT
028 HWMCA_DE_INVALID_HOST
029 HWMCA_DE_INVALID_COMMUNITY There are two possible reasons for this:
  1. SNMP community on the HMC/SE does not match the SA Policy coding. Compare the coding in the SA Policy Processor entry and the one on the HMC/SE. Please note that the Community name is case-sensitive, on the HMC/SE. Community names must be entered in uppercase.
  2. RACF profiles (HSA.ET32TGT.xxxx) are missing. Check if required HSA.ET32TGT.xxxx profiles exist. For details about required RACF Profiles, please refer to the appendix "Security and Authorization" of IBM Z System Automation Planning and Installation.
For INTERNAL (BCPii) connections, this condition code report may also provide the following sense information: 080F0001 End-user not authorized: The requesting end-user does not have access to the requested resource.
  1. Make sure, the Auth Token/Community Name specifications of the Processor Information policy are in upper case and are identical to the upper case definitions made in the addressed SE/HMC. Use the ACSADMIN task "API Settings" to validate the definitions on the SE/HMC side.

    Besides, check if all other parameters of the "API Settings" entry (Address, Network Mask, Access Type) are defined as documented in Step 7: Preparing the Hardware of IBM Z System Automation Planning and Installation.

  2. Make sure, the Cross Partition Authority Flag of the requesting system's LPAR is enabled. Perform the SYSPROG task "Change LPAR Security" on the Support Element of the requesting system's CPC to validate this. This is applicable for INTERNAL connections only.
  3. Make sure, the 'LIC Change enabled' flag is set on all HMCs in your processor LAN, in case the request fails only if it targets another than the local CPC. Perform the SYSPROG task "Customize Console Services" to validate and change the flag. This is applicable for INTERNAL connections only.
  4. Make sure, the UNICODE libraries SYS1.SCUNLOCL and SYS1.SCUNTBL are both available, accessible and cataloged on the system that issues the request.
  5. If steps 1-4 could not resolve this condition code, look for any SAF messages, like RACF's ICH408I which may indicate the user not being authorized to access the HW resource.
030 HWMCA_DE_INVALID_QUALIFIER
074 HWMCA_DE_AUTHORIZATION_ERROR

A data exchange API request was issued targeting a CPC or CPC image over BCPii. The targeted CPC has BCPii permission settings that do not allow this from the requesting CPC image.

BCPii permission settings are controlled using the Image Activation Profile of the targeted CPC partition.

095 HWMCA_DE_UNKNOWN_USERNAME

SNMPv3 User on the HMC/SA does not match the System Automation policy definitions.
096 HWMCA_DE_INCORRECT_PASSWORD

SNMPv3 Password on the HMC/SA does not match the System Automation policy definitions for SNMPv3 user. If keyword SAFPW is used in the System Automation Policy, then incorrect password is stored in the System Automation Password store (INGPW).
097 HWMCA_DE_INVALID_STACKNAME (SNMP connections only)

During INITCOM request, the IP stackname supplied caused the internal setibmopt() call in the HwmcaInitialize() request to fail. The setibmopt call sets which IP stack is to be used for all subsequent TCP/IP calls over a socket connection.

The IP stackname must be stored in the NetView Cglobal variable 'ISQHW.netid.nau.OTCP' prior to the INITCOM call. Note that the CS TCP/IP configuration must have the usage of multiple IP stacks enabled correctly, otherwise any setibmopt call will fail, even if the default stackname is specified. If multiple IP stack environment is not configured on the system, do not specify a stackname for SNMP connections. This definition is done in the SA Customization dialog, Option 10 'Processors', Processor Info, entry field 'IP stack'.
098 HWMCA_DE_REQUIRES_QUALIFIER
099 HWMCA_DE_TRANSPORT_ERROR Check that the BCP Internal Interface modules are correctly installed. Module or module version error detected in LPA lib or LNKLST.