autoping -S doesn't work on i5/OS, z/OS, HP/Linux, Itanium, or Windows x64 agents

Document ID : KB000049746
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

In R11.3 I cannot get a successful result when I am autoping my agent with the -S option on any of these OS: is i5/OS, z/OS, HP/Linux, Itanium, Windows x64.

autoping -m  -S                                                       
                                                                             
                                                                             
CAUAJM_I_50023 AutoPinging Machine [AUTOTMP]                                 
CAUAJM_I_50031 Checking the Agent's connectivity to the Application Server.  
CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.   
CAUAJM_E_50041 ERROR: Agent returned <Error loading support library - "Unable
to find library 'libas_c_bind.sl'.">.                                        
CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.               
                                                                             
CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.   
CAUAJM_E_50041 ERROR: Agent returned <Error loading support library - "Unable
to find library 'libas_c_bind.sl'.">.                                        
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL.

Solution:

The autoping -S switch is not supported on the following agents:

i5/OS
z/OS
HP/Linux Itanium
Windows x64

This is because the -S switch is testing connectivity from the agent to the application server. That requires the AutoSys SDK which is not yet supported on these platforms.

Note: SSA must also be installed as well.

In the case of i5os, the machine definition in AutoSys can specify:

type: i5os

Then the autoping -S will be rejected upon issuing.

Please note that the -S option is only used to test functionality from the agent back to the application server on 11.3 agents. The agents only require this connectivity when using a blob or glob. Command jobs that do not use these features are not affected by this limitation.