IV81613: NCI_TRIGGER REPORTS SUCCESS WHEN INCORRECTLY RUN AGAINST A NON-EXISTENT POLICY

7.1.0-TIV-NCI-ZLINUX-FP0006
7.1.0-TIV-NCI-WINDOWS-FP0006
7.1.0-TIV-NCI-SOLARIS-FP0006
7.1.0-TIV-NCI-LINUX-FP0006
7.1.0-TIV-NCI-AIX-FP0006
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 5(7.1.0-TIV-NCI-FP0005)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 6(7.1.0-TIV-NCI-FP0006)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 7(7.1.0-TIV-NCI-FP0007)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 8(7.1.0-TIV-NCI-FP0008)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 9(7.1.0-TIV-NCI-FP0009)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 10(7.1.0-TIV-NCI-FP0010)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 11(7.1.0-TIV-NCI-FP0011)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 12 (7.1.0-TIV-NCI-FP0012)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 13 (7.1.0-TIV-NCI-FP0013)

APAR status

• Closed as program error.

Error description

• Introduced with Impact 7.1.0 Fix Pack 2:
  
  The use of nci_trigger against a none existent Policy does not
  report an error to the screen or the ImpactServer log.  There
  is an error recorded in the PolicyLogger and if the
  PolicyLogger is configured to append the Policy name a new
  PolicyLogger log file is created for the name of the none
  existent Policy containing the error (that the Policy can't be
  found).
  
  In testing in Impact 7.1.0 it was found that this is not the
  case and it does produce the error to the screen and in the
  ImpactServer log file.  So the behaviour is produced in Impact
  7.1.0 Fix Pack 2 onwards.
  
  The observed adverse behaviour
  
  $IMPACT_HOME/bin/nci_trigger NCI impactadmin/xxx
  some_undefined_policy
  some_undefined_policy Policy completed successfully
  
  The logs contain one successful and one error entry:
  
  impactserver.log:
  INFO [ImpactServerLibertyBean] Policy 'some_undefined_policy'
  executed successfully
  
  NCI_policylogger.log:
  [some_undefined_policy] [pool-3-thread-22]Unable to find policy:
  some_undefined_policy
  
  Expectation:
  nci_trigger should return an error, if the policy is not
  defined.
  
  Level 3 Support reports:
  
  "There was a change made in FP2 that logs that the policy does
  not exist but fails to send a failed result back to
  nci_trigger. Since the result nci_trigger gets back is 0, it
  shows success instead of failure."
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Impact 71x Users                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When nci_trigger is run against a non-existent policy, it    *
  * shows success instead of failure.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Since the result nci_trigger gets back is 0, it shows success
  instead of failure.
  

Problem conclusion

• The fix is to return a result = 1 so nci_trigger can show
  failure.
  The Fix for this APAR is contained in the following maintenance
  package:
  |Fix Pack | 7.1.0-TIV-NCI-FP0006
  

Temporary fix

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

  NETCOOL/IMPACT

• Fixed component ID

  5724O59IS

Applicable component levels