Problem: A trace shows the following:

  <description>Driver exception.</description>
<exception class-name="com.Omnibond.system.Command.CommandSessionException">        
<message>Error occured during writeLine(): 
com.Omnibond.system.Command.ScriptException: linenum=4 cursor=0 : Invalid password supplied
</message>

Possible Cause: The password for the administrative user ID is not specified correctly in the driver parameters.

Action: Specify the correct Application Password in the driver parameters. For details, see Configuring Driver Parameters after Setup Has Been Completed.

Problem: A trace shows the following:

  <description>Driver exception.</description>
<exception class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error occured during writeLine(): com.Omnibond.system.Command.ScriptException: linenum=3 cursor=0 : User is not authorized
  </message>
</exception>

Possible Cause: The administrative user ID is not specified correctly in the driver parameters.

Action: Specify the correct Authentication ID in the driver parameters. For details, see Configuring Driver Parameters after Setup Has Been Completed.

Problem: A trace shows the following:

  <description>Driver exception.</description>
<exception class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error connecting: java.net.NoRouteToHostException: No route to host
</message>
</exception>

Possible Cause: The RACF host address or Telnet port is not specified correctly in the driver parameters.

Action: Specify the correct RACF host address and Telnet port in the driver parameters. For details, see Configuring Driver Parameters after Setup Has Been Completed.

Problem: A trace shows the following:

  <description>Driver exception.</description>
<exception class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error occured during writeLine(): com.Omnibond.system.Command.ScriptException: linenum=6 cursor=0 : Account Number has not been defined for use
</message>
</exception>

Possible Cause: The RACF TSO account number is not specified correctly in the driver parameters.

Action: Specify the correct RACF TSO account number in the driver parameters. For details, see Configuring Driver Parameters after Setup Has Been Completed.

Problem: A trace shows the following:

Code(-8016) Operation vetoed by object matching policy.

Possible Cause: Your Matching policy rejected the operation.

Action: Verify that your Matching policy is working as intended.

Possible Cause: No Matching Policy is in use.

Action: Ensure that a Matching policy that properly implements your installation management policies is provided. Upon installation, Use Default Matching Rules is not enabled by default. For details, see Setting Global Configuration Values.

Problem: A trace shows the following:

  <description>Driver exception.</description>
<exception class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error occured during writeLine(): 
com.Omnibond.system.Command.ScriptException: linenum=3 cursor=0 : User already logged on
</message>
</exception>

Possible Cause: The administrative user ID is specified in the driver parameters could not be logged on by the driver because it is already in use. z/OS does not allow multiple concurrent logons for the same user ID.

Action: Ensure that only the driver uses the administrative user ID.