IJ08876: SETAGENTCONNECTION DOES NOT UPDATE MULTIPLE INSTANCES
Closed as program error.
Setagentconnection does not update multiple instances Environment: 630 FP7 Windows OS Agent Do you think the latest patch applied is involved? No Problem Description: Executing the command setagentconnection against a Window's target where there are multiple Agent Instances and the Agent Owner field of an Agent Instance, as returned by the command Kincinfo -o is of the format DOMAIN\Owner will result in that Instance's configuration not updated. If the Agent's Instance Owner name is of the following format "NT AUTHORITY" the problem will not occur. Detailed Recreation Procedure: 1. Install TEMS 630.FP7 and Windows OS Agent 2. Install MS SQL Agent. 3. Change the ownership of the MS SQL Agent to be AETH\S049373 4. Execute the command tacmd setagentconnection -a -n <OS Agent MSN> -p SERVER=host1 PROTOCOL=IP.PIPE PORT=1918 BSERVER=host2 BPROTOCOL=IP.PIPE BPORT=1918 BACKUP=Y 5. Observe that only the Agents whose Ownership is of the format NT AUTHORITY\SYSTEM" are correctly configured by the the command. Related Files and Output: To determine if the problem exists on the target system, execute the command kincinfo -o on the target system and observe whether the format of the Owners of the Agents matches the format DOMAIN\OwnerName.
Setagentconnection does not update the connection settings for Agents with multiple instances. Executing the command setagentconnection against a Window's target where there are multiple Agent Instances and the Agent Owner field of an Agent Instance, as returned by the command Kincinfo -o is of the format DOMAIN\Owner will result in that Instance's configuration not being updated. If the Agent's Instance Owner name is of the format "NT AUTHORITY" which includes a space character between the words NT and AUTHORITY as displayed by the kincinfo -o output, the problem will not occur.
A code change has been made to reduce the minimum number of space character separated fields on the output line from kincinfo -o from nine to eight. The fix for this APAR is contained in the following maintenance packages: | service pack | 188.8.131.52-TIV-ITM-SP0002
Reported component name
Reported component ID
YesSpecatt / Installability / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID