IZ63822: CUSTOM AGENT FAILS TO START WHEN DEPLOYED VIA THE COMMAND LINE

APAR status

• Closed as program error.

Error description

• TEMS 6.2.1 environment.  Agent Builder 6.2.1.1.
  Custom agent is deployed to windows servers via the 'tacmd
  addsystem' command.  Agent gets deployed, but is not started.
  .
  Agents deployed via the TEP GUI are deployed and started
  successfully.
  .
  When an Add Managed System is made from the TEP, the TEP
  generates a pseudo Instance name for the Agent, whereas the
  command generated by the CLI program does not.  To Deploy,
  the inputs should be the same wehter from the TEP or CLI when
  the Agent has no parameters.
  

Local fix

• Problem has been fixed in version 6.2.2 of the code.
  

Problem summary

• TEMS 6.2.1 environment. Agent Builder 6.2.1.1. Custom agent is
  deployed to windows servers via the 'tacmd addsystem' command.
  Agent gets deployed, but is not started.
  
  Agents deployed via the portal client are deployed and started
  successfully.
  
  When an Add Managed System is made from the portal client, the
  portal client generates a pseudo Instance name for the Agent,
  whereas the command generated by the CLI program does not. To
  Deploy, the inputs should be the same whether from the portal
  client or CLI when the Agent has no parameters.
  

Problem conclusion

• The CLI logic has been aligned with the GUI logic.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | fix pack | 6.2.1-TIV-ITM-FP0002
      | fix pack | 6.2.2-TIV-ITM-FP0002
  

Temporary fix

• Deploy the agent via portal client.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R621 PSY

     UP