Patch Name: PHSS_30854

Patch Description: s700_800 11.X OV ITO7.1X Msg/Act Agt Windows A.07.25

Creation Date: 04/06/17

Post Date: 04/06/21

Hardware Platforms - OS Releases:
	s700: 11.00 11.11
	s800: 11.00 11.11

Products:
	OpenView Operations 7.1

Filesets:
	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP

Automatic Reboot?: No

Status: General Release

Critical:
	Yes
	PHSS_30854: HANG ABORT CORRUPTION MEMORY_LEAK
	PHSS_30202: HANG ABORT CORRUPTION MEMORY_LEAK
	PHSS_29356: HANG ABORT CORRUPTION MEMORY_LEAK
	PHSS_28943: HANG ABORT CORRUPTION MEMORY_LEAK
	PHSS_28501: HANG ABORT CORRUPTION MEMORY_LEAK
	PHSS_27388: HANG ABORT CORRUPTION MEMORY_LEAK

Category Tags:
	defect_repair general_release critical halts_system
	corruption memory_leak

Path Name: /hp-ux_patches/s700_800/11.X/PHSS_30854

Symptoms:
	PHSS_30854:
	Change Request: 8606353730
	  opcmsga may log OpC20-184 warning in opcerror while
	  starting the agent at anytime (even if there was no
	  message removed):

	  03/03/04 17:36:47 WARNING opcmsga   (Message Agent)(2592)

	  [genmsga.c:789]: Removing messages with lower severity
	  from buffer file
	  successful. (OpC20-184)
	Change Request: B555025826
	  Enhance opcagt for coexistence with future versions of
	  components.
	Change Request: B555028156
	  Event Log may fill up with Events (ID 1008).
	Change Request: B555027932
	  If traps contain special characters (e.g. german vowel
	  mutation) there is no way to convert them.
	Change Request: B555021291
	  The itoprocs.exe utility fails to monitor the
	  'System' process: it always returns 'not running'.
	Change Request: B555015566
	  It should be possible to use variables for the policy
	  name when specifying program sources.
	Change Request: B555025830
	  Enhance installation for coexistence with future
	  versions of components.
	Change Request: 8606347268
	  OVO does not offer Java APIs for opcmsg and opcmon
	  similiar to the ones that are available for C.
	Change Request: R555026293
	  In case the agent is running in cluster aware mode, the
	  distributed ServiceDiscovery policies do not get updated
	  during runtime, but it is necessary to restart the agent
	  to activate the policies.
	Change Request: B555026065
	  When forwarding message from OVO Windows to OVO UNIX, the
	  message attribute "Time created on mgd node" might be one
	  hour behind on OVO UNIX.
	Change Request: B555029097, B555034081
	  The agent should not write the inst.log file to c:\temp.
	  This directory may not exist and furthermore placing
	  the logfile to this location prevents Windows
	  certification for the OVO Windows manual agent
	  installation.
	Change Request: B555028360
	  opcapm reports error opc30-3287 with an empty cluster
	  name.
	Change Request: B555026161
	  opcapm stops right after startup.
	  It may send the message Opc30-3220.
	Change Request: B555019473
	  A measurement threshold policy with a single external
	  source that is deployed from an OVO Windows Management
	  Server may miss the first value sent by an opcmon call
	  directly after the policy was deployed.
	Change Request: B555029983
	  There is a typo within error message OpC30-1139
	  (operaition instead operation).
	Change Request: B555028454
	  When starting itoprocs with enabled tracing, this trace
	  removes old trace files. During long time tests, most
	  traces get lost.
	Change Request: B555027720
	  In a NAT environment, the opcle may show a memory leak
	  while monitoring the Windows Event Logs.
	Change Request: B555032615, 8606360189, 8606359013
	  The agent installation removes all "<drive>:\bin"
	  entries within PATH environment variable.
	Change Request: B555030236, , 8606284425
	  You may receive error messages:
	  "Illegal index (numvalue) (function csm_pb_proc_get_pid)
	  (OpC10-12)
	  Performance Agent of subagent 12 aborted or exited.
	  Restart failed.
	  (Opc30-1197)"
	  During system reboot/shutdown.
	Change Request: 8606338462
	  After time change to Standard Time from day time saving,
	  only messages generated by "open message interface" type
	  policies are sent correctly with the same created and
	  received time:
	  Received  11/3  3:47:33 PM -08:00 UTC
	  Created     11/3  3:39:44 PM -0800 UTC
	  Messages from monitoring measurement threshold are sent
	  with one hour difference:

	  Received  11/3  8:23:08 AM -07:00 UTC
	  Created     11/3  7:15:19 AM -0800 UTC

	  This behavior is seen on Windows and will be corrected
	  only after stop and restart the agents. Customer has 600+
	  nodes and has requested a fix for this defect.
	Change Request: 8606351529
	  Problem with message forwarding between OVO/W 7.x and
	  OVO/U 6.x.
	Change Request: B555027075
	  Request to restrict the reading of Windows Events written
	  to the Event Logs to the Events that occur during the
	  agent runtime.
	Change Request: B555030238
	  The Monitor Agent may report an error while it tries to
	  monitor the performance object Memory on French systems.
	  This usually works on the second retry.
	Change Request: B555027595, 8606340667
	  opcle does complete reprocess of a logfile as the switch
	  between daylight saving and standard time occured or vica
	  versa.
	Change Request: B555028060
	  opcmona places the OVO paths at end of $PATH instead of
	  in front which causes a delay in application starts if
	  the PATH contains NFS mounted directories.
	Change Request: B555028709
	  Due to an internal bug, advanced monitoring policies can
	  get wrong time to wait for the next check after the
	  policy was running for more than 24 days.
	Change Request: B555018316
	  If files cannot be deployed there is no reason shown.
	Change Request: 8606348130
	  opcqchk -dump may hang on Windows 2000 after successfully
	  dumping the queue content.
	Change Request: H555012137
	  OVO processes may leak file descriptors while writing
	  logfile entries which might lead to strange behaviour
	  as soon as the system limit is reached.
	Change Request: B555026700
	  Installing an OVO A.07.xx agent on top
	  of an installed HPOvLcore version 2 will
	  break the HPOvLcore installation.
	  The OVO agent comes with an BBC Local
	  Location Broker (LLB)
	  '<AgentInstallDir>\bin\llbserver.exe'
	  which does not coexist with the new
	  version 2 location broker ovbbccb.

	PHSS_30202:
	Change Request: R555026193
	  An Advanced Monitor only sends one message per threshold
	  the first time the threshold is reached in a monitor
	  template with multiple conditions.
	Change Request: B555016583, B555018000
	  As soon as the agent is configured with an apminfo.xml
	  file so as to become cluster aware the deployment of a
	  "Service Discovery" policy together with other policy
	  types may cause only the "Service Discovery" policy to
	  be installed.
	Change Request: 8606321177
	  The size of the buffer file msgagtdf is not set to zero,
	  nor is msgagtdf deleted, after connection to the
	  management server is re-established and agents are
	  stopped and restarted.
	Change Request: 8606310908
	  If a logfile size is increasing rapidly, faster than
	  opcle can process it, duplicate messages may not be
	  suppressed.
	Change Request: B555026668
	  <$MSG_OBJECT> is never replaced with the Object set in
	  the template condition that is producing the message.
	Change Request: B555021669, B555024574
	  opctrapi/opcevti may fall behind during storms of traps,
	  and as a result it is disconnected from pmd.
	Change Request: B555019543
	  The Action Agent might report 'cannot set environment
	  variable DISPLAY (OpC30-505)'.
	Change Request: B555022224
	  State-Based Advanced Monitoring of CODA values does not
	  send Msgs to reflect the current state.
	Change Request: 8606322495
	  opctemplate returns always exit code zero, even if it
	  fails or a template does not exist.
	Change Request: B555017581
	  The monitor agent may produce very large error messages
	  each time policies are redeployed.
	Change Request: B555025485, R555027071
	  opcwbemi.exe may abort with a pop up when stopping the
	  agent on Windows 2003.
	Change Request: B555020101
	  opcle.exe logs "Error (87)" messages to the trace file if
	  the end of the eventlog is reached.
	Change Request: B555016164
	  Sometimes the action agent stops working after it gets a
	  large list of actions to execute.
	Change Request: B555023264
	  <$MSG_OBJECT> is never replaced with the Object set in
	  the template condition that is producing the message.
	Change Request: 8606327029, 8606339952, R555026242,
	                B555022834
	  After upgrading from a previous version of OpenView
	  Operations for Windows to OVOW 7.20, tools or scheduled
	  commands that are set to run using a domain user fail to
	  execute. When using a tool on the OVOW Console the tool
	  does not produce any output that might help indicate
	  what the problem is.
	Change Request: 8606331230, 8606337212, 8606358486
	  The OVO Windows Agent should support MS Windows Server
	  2003 64 Bit.
	Change Request: B555018953
	  In trap conditions, $MSG_NODE_NAME is replaced by the
	  trap sender's name, not the trap's agent address name.
	  These names can differ in a proxied environment.
	Change Request: B555018506
	  Want a command to return the communication type of agent.
	Change Request: B555024181
	  API function 'LookupAccountName' failed during
	  installation of BBC settings.
	Change Request: B555026529
	  The problem occurs in case the Windows Event Log that
	  should be monitored is configured to be overwritten
	  either immediately or after a couple of days.
	  As soon as the number of events that are dropped from
	  the Event Log is higher than the number of events that
	  are still in the Event Log, the policies do not generate
	  any message for new events.
	  In case the Event Log is manually reset, the Event Log
	  monitoring starts functioning again.
	Change Request: B555015673
	  The Windows agent installation may abort with the error E
	  -> Error from opc_pb_nt_get_sid_DomainAdminsGroupName
	  when the Agent is installed on a system where the
	  Domainname is a "well known" name like "local".
	Change Request: B555024748
	  opcwbemi leaks memory when using WMI queries and polling
	  intervals.
	Change Request: B555006064
	  Enhancement to opc(r)agt to allow a removal of all
	  agent's temporary files before a restart.
	Change Request: H555010571
	  The Message agent could die when sending messages in a
	  NAT environment.
	Change Request: B555017910, 8606340349, 8606340351
	  The opcle may start consuming a lot of CPU when starting
	  up and will never return to normal behavior.
	  During this it will send a huge number of messages
	  reporting "NT API RegCreateKeyEx: WIN32API_ERROR; Thread
	  ID . System Error Number: 87 (57) - (OpC30-2000)"
	Change Request: B555022243
	  With Service Pack 4 of Windows 2000 and in Windows 2003
	  there is a new privilege "Impersonate a client after
	  authentication". The HP-ITO-Account should have this
	  privilege.
	Change Request: B555017327
	  The agent process opcmona.exe leaks memory when a new
	  source is created via scripting and data is stored.
	  A new source object can be created when using the
	  "Policy.CreateObject" method for VBScript or when using
	  the "Include" and "Exclude" methods of the source object.
	  The monitor agent leaks memory when "Add" is used to add
	  new metrics to the source object.
	  With VBScript the monitor agent also leaks when using the
	  method "Policy.StoreCollection".
	Change Request: B555021144
	  When doing a local reinstall to a Windows agent you may
	  receive the following errors: OpC130-306, OpC30-2170 and
	  OpC30-2171.
	  Those errors complain that there are certain registry
	  keys that can't be found.
	Change Request: R555026123
	  The monitor agent may not do threshold checking on
	  multiple source policies in case there are no instance
	  names that match and the policy is configured to process
	  all instances separately.
	Change Request: B555017861
	  The control agent may not be able to trigger the
	  reconfiguration of the event interceptor after the new
	  policies have been deployed.
	Change Request: 8606315885
	  If a resource group on an active cluster node is taken
	  offline then the policies configured in the XML file do
	  not get disabled.
	Change Request: B555015548
	  The built-in ECS annotation server (opcecaas/opcecmas)
	  may start looping or even abort.
	Change Request: B555022044
	  In an OVIS and OVOW integration, If OVIS and OVOW are
	  installed on a
	  drive rather than C, OVIS alarms may give -10 error code.
	Change Request: B555020612
	  Duplicate suppressing is inconsistent, when using a mix
	  of counter/timer or when default settings are set and
	  more settings are added in the conditions.
	Change Request: 8606323200
	  OpenView Operations for Windows 7.10 with all patches
	  installed receives the following message from Windows
	  agents when the windows system shuts down:
	  Performance Agent of subagent 12 aborted; process did an
	  exit 0. Restarting the subagent after 10 seconds for the
	  '1' time in the last '0 d 00:02:33'. (OpC30-1195).
	  Illegal index (numvalue) (function csm_pb_proc_get_pid)
	  (OpC10-12) Performance  Agent of subagent 12 aborted or
	  exited.  Restart failed. (Opc30-1197)
	Change Request: B555022945
	  Distribution of monitors fails with OpC20-65/66 if
	  system resources are low and memory allocation fails for
	  the monitor file.
	Change Request: B555026998
	  opcmona may abort during startup when monitor
	  Windows Perfmon Sources.
	Change Request: B555018732
	  You may receive the error "Illegal value( function )
	  (OpC10-13)" in the opcerror file reported by the process
	  opcecaas or opcecmas.
	Change Request: B555022373, B555023339
	  The opcwbemi process may consume a large amount of memory
	  when the deployed policies have a certain configuration
	  of contained conditions.
	Change Request: B555023880
	  Some Coda Policies generate an operator initiated action
	  to show the Fileystem graph. This action sometimes fails,
	  and displays:
	  Error in generating report
	  No data found in the selected date range
	Change Request: B555018987
	  opcagt -status and opctemplate may erroneously report:
	  Error opctemplate(24470) : opcctla not running on node
	  <node>. (OpC30-3002) Cannot connect to RPC service at
	  system 'ncacn_ip_tcp:<ip>[<port>]'. Local port
	  configuration has been consulted - rpcd/llbd on remote
	  system not queried. (OpC20-186)
	Change Request: 8606325445, B555021772
	  opctemplate help information is incorrect. opctemplate -
	  enable is shown in the help, but the correct command is
	  opctemplate -e.
	Change Request: B555023337, B555023525
	  The agent may report the errors:
	  An Error occurred in the processing of the policy ''....
	  (OpC30-797)
	  Lost the connection to Coda on host 'localhost'
	  (OpC30-768)
	  AND/OR
	  Policy '': The 'ExecQueryAsync' call to Windows
	  Management failed (NO_KNOWN_WBEM_RESULT).... (OPC30-326)
	  Policy '': The connection to Windows Management was
	  lost.... (OPC30-318)
	Change Request: 8606333207, 8606355920
	  The Logfile Encapsulator may lose messages when
	  monitoring files that periodically get renamed.
	Change Request: B555018498, R555026201, B555019473
	  A measurement threshold policy with a single external
	  source that is deployed from an OVO Windows Management
	  Server may miss the first value sent by an opcmon call.
	Change Request: B553010627
	  Between 7.0 and 7.20, the behavior of the
	  $MSG_GEN_NODE_NAME variable has changed. In 7.0, this
	  variable contained the fully-qualified-domain-name of
	  the node which generated the event. This is no longer
	  the case in 7.20. This happens on Windows nodes when the
	  'System Properties/ Network Identification/ Properties/
	  Computer Name' is given in capital letters and in '.../
	  More/ Primary DNS suffix of this computer' no domain
	  name is given.
	Change Request: H555010468
	  opc(r)agt does not have an option to remove queue and
	  temporary files.
	Change Request: H555010925
	  The following error message appears in opcerror file:
	  >> Cannot retrieve value of type 'MDT_UINT32' in
	  column '4' of interval '0'(OpC30-762) <<
	Change Request: B555023808, B555027712
	  opcmona does not replace <$MSG_OBJECT> properly.
	Change Request: R555025398
	  The logfile encapsulator loses one file handle per
	  configured interval, if all of the following conditions
	  are met:
	  - the logfile name is dynamically evaluated via a script
	  - the script returns file names that cannot be opened
	  - the logfile template defines a 'file to be read'
	  Under these conditions the 'file to be read' will be
	  opened over and over.
	Change Request: 8606320346
	  Messages coming from NT event logs policies shows
	  usernames as SID.
	Change Request: B555017862
	  Monitor agent might leak memory.

	PHSS_29356:
	Change Request: B555017892
	  If tracing is used on cluster systems that have the
	  opcapm running, the trace file is not unlocked after
	  disabling trace with 'opcagt -trace'.
	Change Request: 8606281001
	  Set up a threshold policy that calls a program to get a
	  value at certain intervals. now execute the opcmon
	  command manually, sending a value to this threshold
	  policy. The execution of this policy might get stopped
	  now.
	Change Request: 8606221991
	  SNMP Policy variable <$A> doesn't work correctly
	  (contains the reverse IP address) if the IP address of
	  node sending a trap can't be resolved.
	Change Request: H555009399
	  opcmona cores if an invalid string tries to be converted.
	Change Request: B555015967
	  The control agent may restart the service discovery or
	  llbserver sub-agent endless in case they abort.
	Change Request: B555014691
	  In case the node attribute in automatic and operator
	  initiated actions in msgi templates are empty, the value
	  of <$MSG_NODE_NAME> is used, which is misleading.
	  <$MSG_GEN_NODE_NAME> is used instead.
	Change Request: B555016044
	  If processes which habe been started as an automatic
	  action by the action agent are hanging, the process table
	  can grow. If the limit of 10 processes is reached no more
	  processes will be started.
	Change Request: B555017560
	  opcsetup.exe may abort when installing or updating a node
	  when the opcinfo file has several customized setting
	  (e.g. Firewall environment settings).
	Change Request: 8606318934
	  Typo in message:
	  MESSAGE OpC30-154: The NT Event Log '...' could not be
	  red, because it is corrupt. Please clean the corrupted NT
	  Event Log so that further monitoring is possible.
	  Suppressing further error messages.
	Change Request: 8606298307
	  If large amounts of messages that have a long original
	  message text are forwarded to OVOW (for example messages
	  from WMI: WINOSSPI-ADS_DomainChange), then the OVOW
	  Console memory usage grows.
	Change Request: R555018044
	  The monitor scheduled command policy will be executed
	  only once.
	Change Request: B555016259, 8606354936
	  The length of the PATH environment variable within
	  Windows NT has a set length. Since the agent has a long
	  path and several entries, it takes a lot of space and so
	  the PATH environment variable is sometimes overloaded.
	Change Request: B555017582
	  The Monitor Agent may report that it can't find an
	  instance for a NTPerfMon source irregularly.
	Change Request: B555015766
	  Running multiple instances of itodiag.exe/ovntdiag.exe
	  with tracing creates one log-file with all the tracing
	  information. Afterwards you cannot see, from which
	  instance the output comes from.
	Change Request: H555010496
	  The control agent may abort when doing changing agent
	  registration files and loading them with opcagtreg -add.
	Change Request: R555022806, R555021214
	  The Monitor Agent may abort when using Visual Basic or
	  Perl scripts to write data into CODA.
	Change Request: B555017846, B555020271
	  Perl.exe is not installed with the manual agent
	  installation, if installation is started from any drive
	  other than OS installation drive.
	Change Request: B555016398
	  opcle may abort on Windows 2000 ADS systems while
	  monitoring the security event log.
	Change Request: 8606306951
	  opctemplate may not enable/disable all of the specified
	  policies when used on a Windows agent. This happens most
	  often when disabling each policy separately instead of
	  giving a list of policies to opctemplate.
	Change Request: B555017068
	  A.07.12 changed the behavior of opcle: Newly created
	  logfiles that are discovered by the dynamic logfile
	  discovery functionality are now read from the beginning.
	  But often this is not what is desired, for example if
	  using DBSPI with new instances that need to be monitored.
	Change Request: B555017804
	  The Wbem Interceptor (opcwbemi) may abort while
	  processing a policy.
	Change Request: B555017860
	  opcle might have a high CPU usage when there are
	  policies/templates deployed monitoring the Windows
	  EventLog.
	Change Request: 8606284810, 8606292311, 8606283592
	  The agent may report duplicate events in case of a system
	  abort.
	Change Request: B555017407
	  The process opcmona has a memory leaks in different
	  areas:
	  1. When using WMI sources in the Measurement Threshold
	  Policies;
	  2. When monitoring of CODA sources fails and needs a
	  reinitialization;
	  3. When either using the Policy.SourceEx method of
	  scripting or upgrading policies very often.
	Change Request: H555010422
	  opcmsga binds to the NAT translated IP address causing
	  long delays before messages are sent.
	Change Request: B555016446, 8606296412
	  When running the OVO agent you may experience that
	  console applications may just hang and never finish.
	Change Request: B555018699
	  The opcle may not use the configured OPC_IP_ADDRESS when
	  monitoring the Windows EventLog.
	Change Request: 8606301574
	  Text defined for the default message is not expanded for
	  logfile, opcmsg and monitor policies.
	Change Request: 8606290676, 8606280832
	  Processes started as scheduled actions by the Windows
	  agent create might hang
	  and stay as orphaned processes forever.
	Change Request: 8606312047
	  The virtual memory usage by the process WinMgmt.exe
	  increases constantly while OVO/Win agents on domain
	  controllers monitor WMI via WMI policies.
	Change Request: 8606313801, B555017924
	  If all the server entries in mgrconf are not resolvable
	  then the agent restart will fail during initialization.
	Change Request: B555017631
	  OVO/Unix should support ECS 3.2.
	Change Request: R555022489
	  opcle may generate garbled messages in Japanese
	  environments.
	Change Request: B555017530
	  Message that are sent by the installation server can not
	  be filtered through the internal message filtering on the
	  management server.
	Change Request: B555016407
	  Policies registering for WMI Instance Modification Events
	  send a message filled with the entire PreviousInstance
	  and TargetInstance data. To decrease the size of the
	  message text and make the message more useful, the
	  message should be changed to only report the parts of
	  PreviousInstance and TargetInstance data that has
	  actually changed.
	Change Request: B555015872
	  The file transfer through opctranm may fail when the
	  target node is installed through an OVO Windows 7.x
	  management server.
	Change Request: H555010231
	  When the Application Package Monitor (opcapm) is
	  configured and running on the node, the deployment of
	  some policies may cause opcctla to abort.

	PHSS_28943:
	Change Request: 8606294668
	  The trap interceptor does not use new/changed
	  templates/policies when doing SNMP trap interception on a
	  Windows system that has NNM installed.
	Change Request: B555015785
	  opcecaas may report that it runs out of free process
	  slots and therefore can't start anymore process.
	Change Request: B555015674
	  The Windows agent installation may abort with the error
	  that the node is already managed by a different
	  management server.
	  The inst.log and the command line output on the node you
	  are installing to may contain:
	  E-> NOTE: VPO software, version A.0X.X installed on
	  system <node name>, belongs to Management Server
	  <management server name>.
	Change Request: 8606282084
	  The change between multiple managements doesn't work,
	  because the configuration file primmgr - that has higher
	  priority for agent, is not updated by the
	  'SwitchMgmtServer.cmd' tool that uses 'mgmt_sv.vbs'
	  script.
	Change Request: B555016133
	  opcwbemi.exe may abort while stopping the agent on
	  Microsoft Windows XP.
	Change Request: B555015741
	  During the shutdown of a system, the agent processes
	  still try to start new processes, causing pop up windows.
	Change Request: B555015449
	  Monitor agent may abort while receiving
	  templates/policies.
	Change Request: 8606290346
	  After installing a new version the registry key
	  HKLM\SOFTWARE\Hewlett-Packard\OpenView\ITO\Agent Version
	  remains at A.07.10.
	Change Request: B555015557
	  The current implementation of the control agent does not
	  allow to restart aborted sub agent processes
	  automatically.
	Change Request: B555015199
	  If OPC_IP_ADDRESS (nodeinfo) and OPC_NAMESRV_LOCAL_NAME
	  (opcinfo) were used in combination the entry in
	  OPC_IP_ADDRESS was not used in the right way.
	Change Request: 8606300991
	  opcdcode of Logfile Encapsulator policy shows version
	  number is not updated after a new policy has been
	  deployed, even though the policy is working using the
	  latest version.
	Change Request: 8606303962
	  After time change (beginning of daylight saving time),
	  all logfiles are read from the beginning.
	Change Request: B555015700, B555016671
	  Agent often fails to shut down from the services control
	  panel in time. It also fails to stop in time during the
	  uninstall/redeployment of the agent software.
	Change Request: 8606299704, 8606300881, B555016113
	  You may get the error
	  "Cannot open file <$...>. System Error Number: ... -
	  (OPC20-63)"
	  when using environment variables in the "File to be Read"
	  field of a logfile policy/template.
	Change Request: B555015758
	  opcmsgi aborts if one of the set attributes has an
	  unmatched '<'.
	Change Request: B555015170
	  During distribution of templates, the agent might report
	  that 'The codeset "-1" is incompatible to the codeset
	  "acp1252"'.
	Change Request: 8606290908, R555019859, B555015124,
	                8606290897, R555020110, B555015208
	  The OVO Windows agent may loos it's AgentID when
	  doing a "Redeploy All" or installing an agent package
	  with a higher version. In case this happens, Service
	  Discovery may stop working correctly.
	Change Request: B555015770
	  Agent should report the current internal status of
	  policies. The Flag OPC_TEMPL_STATUS TRUE can be set now,
	  reporting the status for monitors and logfile policies in
	  the two files 'monitor.status' and 'le.status' in
	  '%OvAgentDir%\tmp\OpC'.
	Change Request: B555015771
	  opcmona.exe may sometimes fail to start and show up a
	  message box that a certain ordinal can not be found.
	Change Request: B555015325
	  opcmsga wrongly generates a message OpC30-3002 'opcctla
	  not running on node localhost.' when receiving a
	  reconfigure signal, or at exit time.
	Change Request: H555008529, H555008546
	  If a process dies immediately after being started by the
	  Control Agent, it is possible that OpC30-1094 messages
	  start appearing in the error logfile.
	Change Request: 8606297998
	  The ECS engine (opcecm & opceca) might have problems
	  when a circuit is using global dictionaries.
	  (This is the case for the MessageStorm detection ECS
	  circuit).
	Change Request: B555008674
	  The opcagt and the opcragt commands have a new option
	  '-version'. In both man pages, this was not documented.
	  The new option was not part of the usage strings of
	  opcagt and opcragt.
	Change Request: B555014942
	  The opcle process loops if a logfile is removed while
	  it is read.
	Change Request: B555015378, B555014944, 8606299437
	  The agent might not be able to monitor instances of the
	  LogicalDisk object and returns no data for it at all.
	Change Request: B555014851
	  opcmsga sends the same message operation (e.g. an
	  acknowledge request created by opcmack(1) )
	  again and again if the related message is not in the
	  cache and one of the target managers can not be reached.
	Change Request: B555016032
	  The process opcapm.exe may show a memory leak during
	  runtime.
	Change Request: B555015912
	  Agent installation fails when ntmsgm.dll is in use by
	  other process
	Change Request: B555015484
	  You might not be able to install the agent either through
	  server based deployment or manual agent installation. In
	  case Dr. Watson is configured you will see there, that
	  the opcsetup.exe aborted.
	  The problem can also show up during agent runtime. In
	  this case you may not be able to execute any commands
	  through the agent.
	Change Request: B555015485
	  In this case the cause was a mapped network drive listed
	  in the system environment variable PATH.
	  Every time the agent tries to execute an external
	  command, the PATH might be scanned by the used Windows
	  APIs.
	  This is causing a login error on the PC providing the
	  network share and in case this PC also has the "HP ITO
	  account" it will lock this account.
	Change Request: B555015496
	  Queue file handling was inefficient for larger queue
	  files.
	Change Request: 8606293840, 8606293839
	  Monitor agent and Event interceptor grow in memory.
	Change Request: 8606290675, B555015230
	  Agent should report 'agent start' into the opcerror file.
	Change Request: B555015441, B552002692
	  Action agent aborts when process table is full. This
	  happens when more than 52 tools/actions are called from
	  the console in parallel.
	Change Request: R555018185
	  If the agent is started in Simplified Chinese codeset,
	  monitor agent, logfile encapsulator and message
	  interceptor processes will fail.
	Change Request: B555015155
	  Errors in the opcerror file are not written to the trace
	  file. This makes it difficult to find the place in the
	  trace file where the error occurred.
	Change Request: 8606280846, 8606308495, 8606300125
	  Monitor Agent often reports 'Evaluation of policy
	  stopped'.
	Change Request: B555015277
	  The NT monitor agent aborts in process-monitoring policy
	  when the 'ID Process' performance counter exists twice in
	  the performance registry.
	Change Request: B555015331
	  The monitor agent, opcmona, may report wrong results of
	  executed monitor scripts or programs when using many
	  'advanced monitors' such as OVPERF. In some of these
	  cases opcmona might even abort.
	Change Request: B555015712
	  The trap/event interceptor forwards traps with the source
	  address 127.0.0.1 unchanged, therefore they are discarded
	  by the management server due to the unknown source
	  address.
	Change Request: 8606232431
	  VPO tries to resolve node names that only contain blanks
	  because of typo in template definition or variable
	  assignment. This leads to a lot of unnecessary DNS
	  traffic.
	Change Request: B555014781
	  opcwbemi doesn't react on opcagt -trace
	Change Request: 8606300119
	  The logfile encapsulator does not return the last line of
	  a logfile immediately, if there is no carriage return
	  in this line.

	PHSS_28501:
	Change Request: 8606290723, R555020192
	  You may get errors about commands or DLLs that can not be
	  found while executing a command or batch file using the
	  OVO Windows agent. This behavior has been seen with the
	  DBSPI very often.
	Change Request: B555015308
	  When configuring the agent with apminfo.xml
	  to be cluster aware, the agent may not install newly
	  deployed policies correctly.
	Change Request: B555015349
	  The monitor agent might abort while using
	  templates/policies that have an external source
	  specified.

	PHSS_27388:
	Change Request: B555013936
	  agent installation may fail with a high number of the
	  following messages in the inst.log:
	  T-> Tracing information: Can't get status for service:
	  ...
	  It can even happen that the install script reports
	  successfull but nothing gets installed.
	  This may happen when you have installed HP OpenView
	  Internet Services and not all MS Internet Information
	  Services.
	Change Request: B553003927, 8606290146
	  opcmsgi and message APIs (agent + server) leak memory
	  when handling messages with custom message attributes.
	Change Request: B555014999
	  The start of batch files (.bat|.cmd) with Tools/Automatic
	  or Operator initiated actions by using the OVO Agent on
	  Windows NT may fail with a an error saying, the command
	  is not found.
	Change Request: B555014328
	  opcevti.exe may abort when using <$x>.
	Change Request: B555015077
	  Installation server always receives version A.07.10
	  to be installed on the target node.
	  This causes problems in case the installation server just
	  knows A.07.12 but not A.07.10.
	Change Request: B555014961
	  The OVO agent should be able to execute tools and
	  scheduled commands for either the "HP ITO account" or the
	  SYSTEM account user. Or any other user currently running
	  the agent. In any case this should work without a switch
	  user.
	Change Request: B555014634, 8606289806, 8606289053
	  The OVO Windows agent may not pickup the SYSTEM event log
	  entries with ID 6008 or 6009 during the system is
	  rebooted.
	  Or in other cases the opcle may go to 100 % CPU time for
	  several minutes during startup.
	Change Request: B555013965
	  The pdh.dll delivered with the agent
	  has a memory leak as it is described
	  in Microsoft article: Q263221.
	Change Request: B555013978, B555013977
	  In case the agent buffering and you execute the command
	  opcagt or "opcagt -status" you may get an output like:
	  "Message Agent opcmsga buffering for
	  testmgmtsrv.bbn.hp.com (2376) is running"
	Change Request: B555014558
	  itodiag.exe/OvNtDiag.exe may start looping/hanging
	  forever.
	Change Request: B555014093
	  opcmona may crash (UNIX) or doesn't process all SCHEDULE
	  templates (Windows) when using SCHEDULE templates.
	Change Request: B555014513
	  opcle.exe may generate a message storm with messages
	  saying that one of the Windows event logs is corrupt.
	Change Request: B555014714
	  You may receive a message storm with messages:
	  OPC INTERNAL ERROR, CANNOT GENERATE MESSAGE
	  1500 OF SET ZERO
	  Or the opcle may start taking a lot of CPU over a long
	  period of time.
	Change Request: B555014523
	  nt_inst.exe may abort with Dr. Watson while trying to
	  install the Windows agent to a node.
	Change Request: B555013510, 8606278103
	  Autoactions are not executed on systems in a NAT
	  environment.
	Change Request: R555017956
	  The monitor agent is terminated if you use a session
	  variable within the message text of a template followed
	  by any other variable (for example $INSTANCE).
	Change Request: B555014715
	  The Control Agent slowly grows in memory usage.
	Change Request: R555018043, R555018267, R555018227
	  Japanese characters in Perl scripts within templates
	  don't get converted correctly into the server code set.
	  If the Japanese characters are used as message text for
	  example these characters are corrupted.
	Change Request: B555012869
	  Instead of using the trap's UUID, the trap interceptor
	  created a new message id for all but the first trap
	  template. The original message id was not set correctly
	  in these cases.
	Change Request: B555014212
	  opcle may report:
	  ntle.c:3670: OpC internal error: Cannot generate message
	  1500 of set 0
	  System Error Number: 1966234 (1e009a) -  (OpC0-1500)
	Change Request: B555014728
	  Currently OvNtKill.exe / itokill.exe requires the
	  libopc.dll as well as some other DLLs required by
	  libopc.dll.
	Change Request: 8606282247, 8606284806, 8606310913,
	                8606286654
	  Logfile Encapsulator does not perform variable
	  replacement for all Message Defaults fields.
	Change Request: 8606267798
	  In SNMP trap policies when using the <$r> or <$R>
	  variables, on Windows systems the IP address is used in
	  reverse order and therefore there are incorrect results.
	Change Request: B555014667
	  The first lines of a logfile are not forwarded to the
	  message browser when using a command to discover
	  logfiles and the logfile was created after the first
	  polling interval.
	Change Request: B555014708
	  Memory leaks in agent process. Especially monitor and
	  action agent leak when executing processes.
	Change Request: B555014378
	  opcctla may crash when doing a distribution on a Windows
	  XP node in a NAT environment.
	Change Request: B555014799
	  NT agent reinstall might cause cmd.exe startup issues.
	  This can happen when scheduled actions or tools have been
	  executed as user opc_op without specifying a password.
	Change Request: B555009284
	  The authorization verification for remote start and stop
	  requests of the agent was sometimes unreliable. Possibly
	  this allowed more OVO servers to start or stop the agent,
	  than specified in the MoM configuration.
	Change Request: B555013796
	  When using itomserv.exe/opcntmserv.exe to list services
	  or devices where the Service Name or Description contains
	  Japanese Multibyte characters it may happen
	  that the text is truncated wrongly. The leads to a wrong
	  last character and maybe even to problem when displaying
	  this text in the Java or Motif UI.
	Change Request: 8606242614, 8606277183
	  Messages are incorrectly suppressed by the logfile
	  encapsulator if "suppress identical output messages" is
	  specified and the messages differ only in the values of
	  <$LOGFILE> and/or <$LOGPATH>.
	Change Request: B555014882
	  When monitoring Windows performance values by using the
	  NTPerfMon (OVO UX) / Real Time Performance (OVO Windows)
	  sources, there might be an error that not all instances
	  can be found.
	Change Request: B555014759
	  When enabling/disabling policies you might discover a
	  memory leak in the agent processes.
	Change Request: 8606286316
	  When retrieving a list of logfiles by using <`...`>
	  the logfile encapsulator may not retrieve any filename.
	  This has been seen when using perl scripts, that
	  internally call other system commands through the perl
	  function 'system' or 'open' or just use the backticks to
	  execute the command.
	  e.g.: $output = `more c:\loglist.txt`;
	Change Request: B555013872
	  Agent installation sets full access rights for "HP ITO
	  account" on files in %SYSTEMROOT%\system32
	  (opcauth.dll and psapi.dll).
	Change Request: B555014319
	  When reading Windows Event logs the opcle.exe and
	  services.exe may start taking a lot of CPU time for a
	  longer period of time.
	Change Request: B555015004
	  After uninstalling an OV Agent in Local Security Policy
	  there were still some SIDs left over.
	Change Request: 8606285428, 8606285429, 8606279910,
	                8606273263
	  SNMP V2 Traps cannot be received via Windows Agent, when
	  NNM is not installed on the Node.
	Change Request: R555019153
	  When deploying policies from a Windows management server
	  and using the "StoreCollection" method within the Perl
	  or VBScript, the monitor agent might show the Policy name
	  instead of the given metric name or may abort.
	Change Request: B555014591
	  When the OPC_INT_MSG_FLT is set to TRUE then the filtered
	  message is received corrupted on the server in
	  a Japanese environment.
	Change Request: B555013891
	  In MoM environments, opcmsga does not return action
	  responses to SECONDARY managers, if their name is not
	  resolvable.
	Change Request: B555015072
	  'opcagt -id 12 -stop' may not work when starting as
	  'Administrator' as long as the OVO agent runs with
	  'SYSTEM' (LocalSystem) account.
	Change Request: H555008631
	  Customer receives a lot of OpC20-61 and OpC20-63 messages
	  in the error logfile when using NCS agents.
	Change Request: B555014442
	  opcle may report system error 32 and OPC20-63 while
	  processing a logfile on MS Windows systems and after this
	  stopping the processing of this logfile at all.
	Change Request: B555014570
	  The logfile encaspulator might start consuming CPU when
	  doing Windows Event Log monitoring.
	Change Request: B555012827, B555012829
	  Support Windows XP with the VPO Windows agent.
	  Please see the "Defect Description" section below for
	  further details.
	Change Request: 8606244582, B555013444, B553001962,
	                R555014598
	  The distribution/deployment of action/command/monitor
	  binaries might fail due to some of them being used.
	Change Request: B555014101
	  Monitor agent may report error OPC30-783 and the
	  initialisation of the first template/policy using Windows
	  Performance data fails.
	Change Request: B555015047
	  opcecaas (Annotation Server) might log error
	  "Illegal NULL parameter (function ) (OpC10-11)"
	  with many similar lines.
	Change Request: B555014281
	  When using the Windows agent SDK (opcapi.h and
	  opcapi.lib) you may get linker unresolved symbol errors
	  when using one of the following API calls:
	  opcdata_type, opcdata_ldel, opcdata_ladd,
	  opcdata_lget_len, opcdata_lget_str,  opcdata_lset_str,
	  opcdata_generate_id, opcdata_get_error_msg,
	  opcdata_lget_long, opcdata_lset_long, opccdata_clear,
	  opc_version
	Change Request: B555014700
	  The monitor agent and action agent on NT leak handles.
	Change Request: B555013540
	  opcsetup may report:
	   E-> Error from opc_ipinterf_getaddrs.
	   E-> Error from InitSetup.
	   E-> Setup program aborted.
	Change Request: B555015050, 8606302001, 8606322283
	  The environment PATH set by the agent during executing
	  external commands may contain several duplicate entries
	  and get very large therefore. This may cause problems
	  when an executed program tries to add it's own
	  directories as well.
	Change Request: B555013719
	  Message agent doesn't stop message buffering when the
	  management server is available again after a network
	  outage, fixed DNS problem or similar.
	  This can happen when the agent restarts/the machine
	  reboots during the network problem occurred.
	Change Request: 8606187183
	  After deploy/undeploy of opcmsg policies/templates the
	  suppressing times are lost. Messages that should be
	  suppressed after a deploy/undeploy of policies/templates
	  are shown.
	Change Request: 8606282754
	  When calling the perl interpreter without fully qualified
	  pathname within a automatic/operator initiated action or
	  a tool, you may run in problems, since the wrong perl
	  interpreter is used.
	Change Request: B555014873
	  The exit code of commands executed through an ECS
	  annotate node and the OVO annotation server is always 0.
	Change Request: B555013534
	  When the "HP ITO Installtion Server" service
	  gets started you may find the following event in your
	  Application event log:

	  EventID: 0xC0001B68 (7016) - The HP ITO Installation
	  Server service has
	  reported an invalid current state 0.
	Change Request: B555012562
	  The control agent might crash while processing a
	  distribution. This only happens in very special
	  situations. So far it has been seen in environments
	  which are using firewalls.
	Change Request: B555014132
	  During a distribution the agent may report an error like:
	  ITO responsible manager configuration. (OpC30-1203)
	  Cannot open file \usr\OV\tmp\OpC\cfgchg.
	  System Error Number: 13 (d) - The data is invalid.
	   (OpC20-63)
	Change Request: B555013096
	  several itoprocs.exe might hang instead of finishing.
	Change Request: 8606228146
	  opcntmserv.exe/itomserv.exe uses fixed width to display
	  the service names.
	  The defined values are 18 characters for the service
	  name and 25 for the description.

Defect Description:
	PHSS_30854:
	Change Request: 8606353730
	  The agent may report OpC20-184 during startup or after a
	  management server reboot.
	  This message can be safely ignored.
	  This message indicates, that the opcmsga performed a
	  cleanup of the msgagtdf file to remove empty entries, but
	  it doesn't remove any messages.
	Change Request: B555025826
	  Enhance opcagt for coexistence with future versions of
	  components.
	Change Request: B555028156
	  Event Log may fill up with Events (ID 1008).
	  Those errors are usually created by incorrectly working
	  performance counters. Since the agent is using Microsoft
	  APIs, there is no direct influence to the way how and
	  when the performance counter get loaded. But Microsoft
	  did a change to the PDH APIs the agent is using to
	  prevent loading all available performance counter. With
	  this change in place, the PDH only loads the DLL where
	  the values are queried for.
	  Since this DLL is not redistributable, the agent can only
	  check whether the DLL shipped with the agent is newer or
	  older than the one available on the system. As long as
	  the DLL on the system is newer, this one will be used.
	Change Request: B555027932
	  Added nodeinfo configuration variable OPC_TRAP_CHARSET to
	  set the charset of incoming snmp traps. If variable is
	  not defined, no convertion is done.
	Change Request: B555021291
	  The itoprocs.exe utility fails to monitor the
	  'System' process: it always returns 'not running'.
	Change Request: B555015566
	  The execute command made by the monitor agent does allow
	  additional processing now, this allows special opc
	  defined variables for the policy/monitor/source name to
	  be resolved.

	  Variables:
	  <$NAME>      name of the template or policy
	  <$SRCNAME>   name of the source
		       for a template this would return nothing,
		       i.e. empty string
	  <$FULLNAME>  name of the policy and the source
		       (concatenated with -)
		       as defined for policies for templates this
		       would return the same as <$NAME>

	  The <$ character combination can be suppressed  with
	  the \ escape character.
	  If  the <$ character combination is found, but the
	  variable is unknown or no closing bracket (>) is found,
	  then no substitution is preformed.
	  Parsing for escape characters would be limited to the
	  characters directly before a known variable. (i.e. see
	  examples 3,4

	  It would be possible to disable this for a node via the
	  OPCINFO/NODEINFO key;
	  OPC_MON_DISABLE_PROG_VARS TRUE

	  Examples:
	  Policy: SNMP-service-Win2k with source name service
	  Example:     1
	  Definition:  ovntprocs  SNMP <$NAME>-<$SRCNAME>
	  Resolved:    ovntprocs  SNMP SNMP-service-Win2k-service
	  Notes:       Create required name for opcmon from both
	  the policy name and source name variables

	  Example:     2
	  Definition:  ovntprocs  SNMP <$FULLNAME>
	  Resolved:    ovntprocs  SNMP SNMP-service-Win2k-service
	  Notes:       Resolves to the combined policy and source
	  name.

	  Example:     3
	  Definition:  ovntprocs  SNMP \<$FULLNAME>
	  Resolved:    ovntprocs  SNMP	<$FULLNAME>
	  Notes:       Single escape character therefore variable
	  is ignored

	  Example:     4
	  Definition:  ovntprocs  SNMP \\<$FULLNAME>
	  Resolved:    ovntprocs  SNMP	\SNMP-service-Win2k-service
	  Notes:       Double escape character, resolved to single
	  and variables resolved.
	Change Request: B555025830
	  Enhance installation for coexistence with future
	  versions of components.
	Change Request: 8606347268
	  The OVO agent now includes Java OVO API wrapper classes.
	  To use the Java OVO API wrapper classes, your classpath
	  variable must include the jopcagtbase.jar and
	  jopcagtmsg.jar files and your java.library.path system
	  variable must include the directory where the shared
	  library files reside.

	  See /opt/OV/www/htdocs/jdoc_agent/index.html for a
	  javadoc style class documentation.
	Change Request: R555026293
	  The control agent doesn't inform the ServiceDiscovery
	  subagent about newly installed/updated policies in case
	  the agent is configured in cluster aware mode.
	  This is caused by an invalid handling of those policies
	  by the control agent. At the time those policies should
	  be updated, the control agent lost track which of the
	  existing policies have been changed and treats them all
	  as unchanged.
	Change Request: B555026065
	  When forwarding message from OVO Windows to OVO UNIX, the
	  message attribute "Time created on mgd node" might be one
	  hour behind on OVO UNIX.
	  This happens when a timezone is in standard time, but
	  doesn't happen when it is in daylight saving time. This
	  is caused by a wrong conversation of the time and the
	  time offset to GMT when forwarding the message to OVO
	  UNIX.
	Change Request: B555029097, B555034081
	  The agent logfile - inst.log - should not be placed to
	  c:\temp. In order to prevent writting to c:\temp a
	  different common available directory is used.
	  The logfile is written to
	  %SYSTEMROOT%\temp\inst.log now.
	  When installing in the OVO Windows context - from the
	  management server or through the manual installer - the
	  logfile is also placed into %OvAgentDir%\inst.log.

	  For OVO/UX please be aware that you need to change the
	  Application "NT Tools\VPO Install log".
	  Please change this from "cmd /c type c:\temp\inst.log"
	  to "cmd /c type %SYSTEMROOT%\temp\inst.log".
	Change Request: B555028360
	  opcapm reports error OpC30-3287.
	  This error message is missleading, because
	  actually it means, that this is either no cluster node
	  or the cluster service is not running.
	  opcapm reports a new error message OpC30-3288, which
	  should is more meaningful, telling that it is not
	  possible to connect to the cluster node.
	Change Request: B555026161
	  opcapm stops right after startup while sending the
	  message Opc30-3220. The cause is a wrong handling of the
	  specified start/stop commands for a cluster package.
	  In case such a command fails, the opcapm just stop
	  processing. This has been changed to handle this error
	  without stopping the whole opcapm.
	Change Request: B555019473
	  A measurement threshold policy with a single external
	  source that is deployed from an OVO Windows Management
	  Server may miss the first value sent by an opcmon call
	  directly after the policy was deployed.
	Change Request: B555029983
	  Typo was removed.
	Change Request: B555028454
	  Added option -i to get a logfile name including date and
	  PID of the process. Since every process has different
	  date and PID, with option -i no logfile gets lost any
	  more.
	Change Request: B555027720
	  In a NAT environment, the opcle may show a memory leak
	  while monitoring the Windows Event Logs.
	Change Request: B555032615, 8606360189, 8606359013
	  Now <drive>:\bin is only removed, if it was inserted by
	  OpenView before.
	Change Request: B555030236, , 8606284425
	  The Performance Agent did the exit earlier than the
	  control agent expected it and therefore treats this like
	  an abort of the sub agent.
	  In order to avoid this, the control agent listens to the
	  system shutdown signal on it's own as well now and does
	  not only rely on the stop signal from the service control
	  manager.
	Change Request: 8606338462
	  The monitor agent as well as other message interceptors
	  on Windows may sent message with the wrong "Time Created"
	  after there was a time change to Standard Time from Day
	  Time Saving.
	  This is caused by the interceptors reading the time zone
	  offset only during there startup instead of adjusting it
	  for each message they generate.
	Change Request: 8606351529
	  Certain attributes of the message are modified by the 7.x
	  opcmsga and therefore, can not be read on a ITO 6.x
	  server.

	  Now, when OPC_MSGA_ITO6_COMPAT_MODE TRUE is set in
	  opcinfo, opcmsga does not modify these attributes.
	  Therefore, they can be read by an ITO6 message reciever.
	Change Request: B555027075
	  In order to configure the agent to read only Windows
	  Events that occur during agent runtime, a new opcinfo
	  variable has been introduced.
	  Keyword     : OPC_EVENT_RUNTIME_ONLY
	  Description : configure the Windows Event Log
			monitoring to read only events that come
			in during the agent runtime. All events
			that come in during reboot or the time
			the agent is stopped are ignored.
	  Type/Unit   : bool
	  Default     : FALSE
	  Used In     : opcinfo
	Change Request: B555030238
	  The Monitor Agent may report an error while it tries to
	  monitor the performance object Memory on French systems.
	  This usually works on the second retry.
	Change Request: B555027595, 8606340667
	  opcle is using the C API _stat to retrieve modified and
	  created time for a file. Unfortunately this command is
	  using the current daylight settings to transform the UTC
	  time to local time.

	  Now the opcle is using the UTC directly while using
	  different Windows APIs to retrieve those times.
	Change Request: B555028060
	  opcmona places the OVO paths at end of $PATH instead of
	  in front which causes a delay in application starts if
	  the PATH contains NFS mounted directories.
	Change Request: B555028709
	  Now opcmona gets right interval, even if the agent was
	  running for more than 24 days.
	Change Request: B555018316
	  Now the file/folder that is producing the problem is send
	  to opcerror and console.
	Change Request: 8606348130
	  opcqchk -dump may hang on Windows 2000.
	  The root cause for this problem is the way how process
	  opcqchk.exe is ended. The process exited while using a
	  thread exit API, that seems to work on most Windows
	  versions. But it is causing problems on Windows 2000.
	  opcqchk uses a different API to exit now.
	Change Request: H555012137
	  The function used to log messages to a logfile has been
	  fixed by adding error checking for each system call and
	  closing file descriptors where necessary.
	Change Request: B555026700
	  Only one instance of BBC Local Location Broker
	  can run on the system.
	  Future technology location/communication broker would
	  take over tasks of BBC LLB. In case the new
	  location/communication broker is installed on the system,
	  'llbserver.exe' will be saved to 'llbserver.bak' and not
	  started by the control agent. 'opcagt -status' will  not
	  report the status of 'llbserver'.

	PHSS_30202:
	Change Request: R555026193
	  An Advanced Monitor only sent a message the first time
	  a threshold is reached. For example, if a template has
	  three thresholds of 75, 50, and 25 and the values of
	  33, 55, 88, 60, 30, and 10 were given, messages were
	  only sent for 33, 55, and 88. A reset msg is sent for 10
	  which attempts to acknowledge the 25 threshold which is
	  no longer in the browser.
	  Now, messages are sent for 33, 55, 88, 60, and 30. The
	  reset message then acknowledges the correct message.
	  The opcinfo variable OPC_MONA_MSG_PER_STATE has been
	  added to reflect this behaviour:
	  TRUE (default) reflects the new and correct behavior.
	  FALSE has opcmona return to it's previous behaviour of
	  only sending one message per state.
	Change Request: B555016583, B555018000
	  As soon as the agent is configured with an apminfo.xml
	  file so as to become cluster aware the deployment of a
	  "Service Discovery" policy together with other policy
	  types may cause only the "Service Discovery" policy to
	  be installed.
	Change Request: 8606321177
	  The message agent does remove the free entries from the
	  double buffer file (msgagtdf) regularly.
	Change Request: 8606310908
	  Added OPC_LE_MAX_LINES_READ <int> variable for opcinfo.
	  If it is not set, then the default of 50 lines are read
	  with each interval. If it is set, then the number of
	  lines that is specified will be read. If it is set to 0,
	  then an unlimited number of lines will be read.
	Change Request: B555026668
	  <$MSG_OBJECT> is now replaced with the Object set in the
	  template condition if it is set and
	  OPC_MON_MSGOBJ_COND_FIRST is set to TRUE in opcinfo.
	Change Request: B555021669, B555024574
	  1. The original message text is now evaluated once per
	  trap (no longer once per trap and template). This change
	  can speed up opctrapi up to 50% when many trap templates
	  are used.
	  2. opctrapi will now evaluate an opcinfo variable
	  OPC_SEND_MAX_ONE_MSG_PER_TRAP. If set to TRUE, opctrapi
	  will skip processing further templates for a trap after
	  one template generated a message out of this trap.
	  NOTE: Disconnection from pmd is still possible but will
	  happen less frequently.
	Change Request: B555019543
	  The Action Agent might report 'cannot set environment
	  variable DISPLAY (OpC30-505)'.
	Change Request: B555022224
	  Advanced Monitoring only sends a msg the first time a
	  state is entered.  Currently if a template has three
	  thresholds of 75,50, and 25 and the values of 33, 55, 88,
	  60, 30, and 10 are given, msgs are only sent for 33, 55,
	  and 88.  A reset msg is sent for 10 which attempts to
	  acknowledge the 25 threshold which is no longer in the
	  browser.
	  Now, messages are sent for 33, 55, 88, 60, and 30.  The
	  reset message then acknowledges the correct message.
	  OPC_MONA_MSG_PER_STATE has been added to reflect this
	  behaviour.
	  TRUE (default) reflects the correct behaviour.
	  FALSE has opcmona return to it's previous behaviour of
	  only sending one message per state.
	Change Request: 8606322495
	  opctemplate returns always exit code zero, even if it
	  fails or a template does not exist.
	Change Request: B555017581
	  The monitor agent may produce very large error messages
	  each time policies are redeployed.
	Change Request: B555025485, R555027071
	  opcwbemi.exe may abort with a pop up when stopping the
	  agent on Windows 2003.
	Change Request: B555020101
	  "Error (87)" is only logged during a trace, if there is a
	  real problem (e.g. event log to large).
	Change Request: B555016164
	  Sometimes the action agent stops working after it gets a
	  large list of actions to execute.
	Change Request: B555023264
	  <$MSG_OBJECT> is now replaced with the Object set in the
	  template condition for threshold monitors if it is set
	  and the opcinfo variable OPC_MON_MSGOBJ_COND_FIRST is
	  set to TRUE.
	Change Request: 8606327029, 8606339952, R555026242,
	                B555022834
	  The tool/application execution for a different user may
	  fail with no output. This is caused by a conflict in the
	  internal handling done by the OS managing the different
	  desktops for services and the interactive user.
	  In order to prevent this, all tools/applications will be
	  started with access to the interactive desktop.
	  Due to a problem in Windows 2000 this may cause certain
	  applications to hang. When you discover this behavior you
	  should apply the following Microsoft Windows HotFix:
	  http://support.microsoft.com/?id=821107
	  This HotFix is also part of the security bulletin:
	  http://www.microsoft.com/technet/security/bulletin/ \
	  MS03-045.asp
	  You can control the behavior of the agent by using an
	  opcinfo variable.
	  OPC_PROC_ALWAYS_INTERACTIVE
	  This switch tells the agent how to start processes
	  on Windows. This is helpful due to a problem in Windows
	  2000. Here some processes may hang when they are started
	  with access to the default desktop as long as there is
	  no user logged on. This is documented in:
	  http://support.microsoft.com/?id=821107
	  To avoid this problem without installing the mentioned
	  HotFix, you can set this variable to FALSE. But this may
	  result in problems executing tools that require a switch
	  user. Those tools may just fail without any output. In
	  case you don't run tools that require a switch user, you
	  can safely set this option to FALSE. Otherwise, please
	  install the HotFix provided by Microsoft.
	  Type/Unit   : bool
	  Default     : TRUE
	Change Request: 8606331230, 8606337212, 8606358486
	  The OVOW Windows Agent does support MS Windows Server
	  2003 64 Bit version. The agent itself is running in 32
	  bit emulation mode. There are certain limitations that
	  apply during the runtime of the agent.
	  Limitations:
	  Files:
	    The agent is not able to process files that are bigger
	    than 2 GB. This mainly affects the
	    Logfile Encapsulator, which is not able to read
	    those files. In case a logfile goes beyond this limit,
	    you will get the error:
	    "Cannot seek file <...> System Error Number: 131(83) -
	     (OpC20-70)"
	  Registry:
	    The registry entries for the agent are located under:
	    HKLM\SOFTWARE\Wow6432Node\Hewlett-Packard\....
	    In order to access the registry while using the
	    original path: HKLM\SOFTWARE\Hewlett-Packard\...
	    The application that is accessing the registry
	    needs to run in 32 bit emulation mode as well.
	    This applies for instance to the VB Script mgmt_sv.vbs.
	    The script should be executed by using the
	    script engine located under: %SYSTEMROOT%\SysWOW\64.
	    You may use wscript.exe or cscript.exe.
	    The script will fail when using the standard script
	    engine that is located in the PATH!
	    Please see MS KB Article Q305097 for further
	    information.
	    (http://support.microsoft.com/default.aspx \
	      ?scid=kb;[LN];305097)
	  MS Windows 2003 64 bit Problems that affect the agent:
	    The agent processes may show a memory increase
	    while starting external processes.
	    This problem is documented and fixed with the
	    Microsoft KB article:
	    32-Bit Process Calls the CreateProcess Function but
	    Does  Not Successfully Start Another 32-Bit Process
	     (822961)
	    (http://support.microsoft.com/default.aspx \
	      ?scid=kb;[LN];822961)
	    HP strongly recommends to install this HotFix prior
	    to install the agent on Windows 2003 64 Bit editions.
	Change Request: B555018953
	  <$MSG_NODE_NAME> is now set correctly to the trap
	  override node name.
	Change Request: B555018506
	  opcagt -type will now return the communication type.
	Change Request: B555024181
	  API function 'LookupAccountName' failed during
	  installation of BBC settings.
	Change Request: B555026529
	  The problem occurs in case the Windows Event Log that
	  should be monitored is configured to be overwritten
	  either immediately or after a couple of days.
	  As soon as the number of events that are dropped from
	  the Event Log is higher than the number of events that
	  are still in the Event Log, the policies do not generate
	  any message for new events.
	  In case the Event Log is manually reset, the Event Log
	  monitoring starts functioning again.
	Change Request: B555015673
	  The Agent installation use the MS API functions
	  LsaLookupNames and LsaLookupSids that behave differently
	  when a "well known" domain name is used. In this case and
	  when SYSTEM Account is used for installation, the call to
	  the result of these MS API functions is necessary and
	  will be dismissed.
	Change Request: B555024748
	  opcwbemi leaks memory when using WMI queries and polling
	  intervals.
	Change Request: B555006064
	  A new option (-cleanstart) has been added to the
	  opc(r)agt commands. It stops the agent, removes all files
	  in the agent's temporary directory and restarts the
	  agent. The trace and pids files are not removed.
	Change Request: H555010571
	  When a message is sent and the agent is configured for
	  a NAT environment, a NULL pointer could be used in
	  strlen() causing a crash of the message agent. An extra
	  check has been added to the code to prevent this.
	Change Request: B555017910, 8606340349, 8606340351
	  The opcle may start consuming a lot of CPU when starting
	  up and will never return to normal behavior.
	  During this it will send a huge number of messages
	  reporting "NT API RegCreateKeyEx: WIN32API_ERROR; Thread
	  ID . System Error Number: 87 (57) - (OpC30-2000)"
	Change Request: B555022243
	  HP-ITO-Account gets the new privilege "Impersonate a
	  client after authentication" at the agent installation
	  (if agent is installed before Service Pack 4 of Windows
	  2000, the HP-ITO-Account doesn't have this privilege).
	Change Request: B555017327
	  The agent process opcmona.exe leaks memory when a new
	  source is created via scripting and data is stored.
	  A new source object can be created when using the
	  "Policy.CreateObject" method for VBScript or when using
	  the "Include" and "Exclude" methods of the source object.
	  The monitor agent leaks memory when "Add" is used to add
	  new metrics to the source object.
	  With VBScript the monitor agent also leaks when using the
	  method "Policy.StoreCollection".
	Change Request: B555021144
	  The local reinstall may fail with several different error
	  messages (OpC130-306, OpC30-2170 and OpC30-2171).
	  Those errors are sent when the IIS FTP server is not
	  using it's default root directory (C:\inetpub\ftproot).
	  In this case the agent tries to find the root directory
	  in the registry and this fails due a typo in the
	  specified registry path.
	  The used registry path has been correct now.
	Change Request: R555026123
	  The monitor agent had a problem that it does thresholding
	  against multiple source policies even when they are
	  configured to process each instance separately. This
	  threshold checking was done for the first set of
	  instances found, but not for all. This behavior has been
	  corrected, but the result is that policies that rely on
	  this behavior will no longer work.
	  In order to prevent this, the old behavior has been
	  reintroduced. Two opcinfo variables exist to configure
	  the monitor agent behavior. If no instance is available
	  in all sources the script is called once. By setting the
	  nodeinfo variable POLICY_NO_INST_CALL_SCRIPT to FALSE it
	  is possible to define that the script is not called if no
	  matching instances are available. If the nodeinfo
	  variable POLICY_NO_INST_SEND_MSG is set to TRUE a warning
	  message is created if no matching instances are
	  available. The message contains also the available
	  instances for all sources. The default is that no message
	  is created.
	Change Request: B555017861
	  The control agent may not be able to trigger the
	  reconfiguration of the event interceptor after the new
	  policies have been deployed.
	Change Request: 8606315885
	  If a resource group on an active cluster node is taken
	  offline then the policies configured in the XML file do
	  not get disabled.
	Change Request: B555015548
	  opcecaas can abort or exit in situations when there are
	  several parallel annotate nodes running.
	Change Request: B555022044
	  In an OVIS and OVOW integration, If OVIS and OVOW are
	  installed on a
	  drive rather than C, OVIS alarms may give -10 error code.
	Change Request: B555020612
	  Default suppressing setting is now used, if the setting
	  is not made in the condition itself.
	  The mix of counter/timer works like it was described
	  before: First the timer is checked - all messages that go
	  through this go into the counter check afterwards.
	Change Request: 8606323200
	  OpenView Operations for Windows 7.10 with all patches
	  installed receives the following message from Windows
	  agents when the windows system shuts down:
	  Performance Agent of subagent 12 aborted; process did an
	  exit 0. Restarting the subagent after 10 seconds for the
	  '1' time in the last '0 d 00:02:33'. (OpC30-1195).
	  Illegal index (numvalue) (function csm_pb_proc_get_pid)
	  (OpC10-12) Performance  Agent of subagent 12 aborted or
	  exited.  Restart failed. (Opc30-1197)
	Change Request: B555022945
	  Distribution of monitors fails with OpC20-65/66 if
	  system resources are low and memory allocation fails for
	  the monitor file.
	Change Request: B555026998
	  opcmona may abort during startup when monitor
	  Windows Perfmon Sources where the string length
	  of the Perfmon Source Path can be divided by four.
	  The reason is that there is not enough memory allocated
	  to cover this path. The monitor agent allocates enough
	  memory now.
	Change Request: B555018732
	  The error "Illegal value (function ) (OpC10-13)" is
	  accidentally reported by opcecaas/opcecmas when using
	  the built in ECS annotate server as well as a custom
	  annotate server. The built in annotate server
	  misinterprets the annotate requests for the custom
	  annotate server and logs an error instead of ignoring
	  those requests.
	  Now it ignores those requests and only logs a note to
	  tracing about the rejected request.
	Change Request: B555022373, B555023339
	  The opcwbemi process may consume a large amount of memory
	  when the deployed policies have a certain configuration
	  of contained conditions.
	Change Request: B555023880
	  Some unsigned integers are printed as signed.
	Change Request: B555018987
	  When a port range is specified for the control agent, and
	  the first port of that range is occupied during startup,
	  opcctla registers on a different port within the range.
	  Clients connecting to opcctla however, expected opcctla
	  to always be on the first port of the range, and failed
	  to connect in this case.
	Change Request: 8606325445, B555021772
	  The help text for opctemplate has been corrected.
	Change Request: B555023337, B555023525
	  The order that processes are informed of the system
	  shutdown is indeterminate. This causes problems with the
	  OVO subagents during a system shutdown, e.g. the subagent
	  making a call to the WBEMI service gets a error returned
	  that the service is not available, in this case the agent
	  does not know if this is an error or if the system is
	  shutting down and therefore normal.
	  This could lead to the following problems in the OVO
	  agent during shutdown:
	  - The opcmona would attempt to connect to the CODA agent
	    to collect data, but this agent had already shutdown.
	  - The opcwbemi would attempt to connect to the WBEM
	    service, but this would refuse the connection as it
	    was already shutdown.
	  These errors could occur and were reported to the OVO
	  Management server as the following errors:
	  An Error occurred in the processing of the policy ''....
	  (OpC30-797)
	  Lost the connection to Coda on host 'localhost'
	  (OpC30-768)
	  AND/OR
	  Policy '': The 'ExecQueryAsync' call to Windows
	  Management failed (NO_KNOWN_WBEM_RESULT).... (OPC30-326)
	  Policy '': The connection to Windows Management was
	  lost.... (OPC30-318)
	  Now the sub-agents register an additional Windows Message
	  Handler that receives the shutdown message before it is
	  passed to the Service Control Manager (this later sends
	  the signal to the control agent). Therefore the
	  sub-agents now get the message before the other Windows
	  Services (e.g. WBEM). Once they have received this
	  message they do not report errors related to connection
	  problems or attempt to restart services or reconnect.
	Change Request: 8606333207, 8606355920
	  opcle has been modified to check to see if the file name
	  is still the same, if the file was not modified for a few
	  intervals. If the file name has changed, opcle attempts
	  to reopen the logfile, reading it from begin. This only
	  works reliably if the 'close after read' option is
	  switched off.
	Change Request: B555018498, R555026201, B555019473
	  A measurement threshold policy with a single external
	  source that is deployed from an OVO Windows Management
	  Server may miss the first value sent by an opcmon call.
	Change Request: B553010627
	  Between 7.0 and 7.20, the behavior of the
	  $MSG_GEN_NODE_NAME variable has changed. In 7.0, this
	  variable contained the fully-qualified-domain-name of
	  the node which generated the event. This is no longer
	  the case in 7.20. This happens on Windows nodes when the
	  'System Properties/ Network Identification/ Properties/
	  Computer Name' is given in capital letters and in '.../
	  More/ Primary DNS suffix of this computer' no domain
	  name is given.
	Change Request: H555010468
	  A new option (-cleanstart) has been added to the
	  opc(r)agt command. It stops the agent, removes all files
	  in the agent's temporary directory and restarts the
	  agent. Trace and pids files are not removed.
	Change Request: H555010925
	  FS metrics were retrieved from coda for some filesystems,
	  for which coda values were not yet valid.
	  Solution: Check whether the data for a specific instance
	  is valid, before further processing the instance.
	Change Request: B555023808, B555027712
	  <$MSG_OBJECT> in threshold monitor templates is now
	  replaced consistently according to this priority:
	  1. Set Condition, if OPC_MON_MSGOBJ_COND_FIRST is TRUE
	  2. object from opcmon
	  3. Template Default
	  4. Empty String
	Change Request: R555025398
	  opcle now checks if the file was already opened, and
	  closes it if necessary before reopening it.
	Change Request: 8606320346
	  SIDs are replaced with the usernames, if it is possible
	  to get the username. If the user does not exist any more
	  the username is shown as SID (this is similar to the
	  event log viewer).
	Change Request: B555017862
	  Monitor agent might leak memory.

	PHSS_29356:
	Change Request: B555017892
	  If tracing is used on cluster systems that have the
	  opcapm running, the trace file is not unlocked after
	  disabling trace with 'opcagt -trace'.
	Change Request: 8606281001
	  Set up a threshold policy that calls a program to get a
	  value at certain intervals. now execute the opcmon
	  command manually, sending a value to this threshold
	  policy. The execution of this policy might get stopped
	  now.
	Change Request: 8606221991
	  Wrong usage of function converting IP address (network
	  byte order vs. host byte order).
	  Changed usage of function converting IP address.
	Change Request: H555009399
	  opcmona cores if an invalid string tries to be converted.
	Change Request: B555015967
	  The control agent may restart the service discovery or
	  llbserver sub-agent endless in case they abort very
	  quickly after being started.
	Change Request: B555014691
	  In case the node attribute in automatic and operator
	  initiated actions in msgi templates are empty, the value
	  of <$MSG_NODE_NAME> is used, which is misleading.
	  <$MSG_GEN_NODE_NAME> is used instead.
	Change Request: B555016044
	  A new function checks if there are processes which are
	  running longer than the defined timeout. If so, a process
	  will be killed by the action agent and and action
	  response will be generated. This function is called
	  regularly. In addition it is called if the process table
	  is full.
	  The timeout can be defined in the opcinfo file using:
	  OPC_KILL_AUTO_ACTION TRUE
	  OPC_KILL_AUTO_ACTION_TIMEOUT <secs>	(default 590 sec)
	Change Request: B555017560
	  opcsetup.exe may abort when installing or updating a node
	  when the opcinfo file has several customized setting
	  (e.g. Firewall environment settings).
	Change Request: 8606318934
	  Fixed in the A.07.12 Windows agent patches.
	Change Request: 8606298307
	  An opcinfo variable was introduced to truncate the
	  original message text to a maximum length:
	  OPC_TRUNCATE_ORIG_TEXT <int>
	  -1:  no truncation done (Default)
	  0: no original message sent at all
	  <n>: truncation done after the n'th character.
	  This can be configured per managed node.
	Change Request: R555018044
	  Internal flag is restored after monitor schedule policy
	  execution.
	Change Request: B555016259, 8606354936
	  Insert the possibility to use subst drive. The subst
	  drive links to the OvAgentDir. To install the settings
	  for subst drive run
	  %OvAgentDir%\bin\OpC\install\mk_subst.vbs.
	  With Windows XP and Windows 2003 subst cannot be set
	  globally, so this tool does not run properly with these
	  systems.
	Change Request: B555017582
	  This can occur when monitoring "\Cache\Copy Read Hits %"
	  on a box having a PCI bus like described in the MS
	  Article
	  "Q274323 - Performance Counter Value May Unexpectedly
	  Leap Forward"
	  The result of this hardware problem is that the Monitor
	  Agent receives negative values when it shouldn't.
	Change Request: B555015766
	  Now the trace logfile name contains the pid of the
	  process.
	Change Request: H555010496
	  When changing subagent registration data, opcagtreg
	  informs the Control Agent of the change (if it is
	  running). The Control Agent then reads the new
	  registration file and stops/starts the processes based on
	  the new data. During comparison of old and new data, a
	  NULL pointer could be used in a strcmp() call which
	  caused crashes.
	Change Request: R555022806, R555021214
	  The Monitor Agent abort is caused by the usage of a
	  static buffer to split the CODA data path into the
	  pieces. When two or more threads split path names at the
	  same time, one could overwrite the other's data.
	Change Request: B555017846, B555020271
	  The drive letter was missing in the installation routines
	  for Perl.
	Change Request: B555016398
	  opcle may abort on Windows 2000 ADS systems while
	  monitoring the security event log.
	Change Request: 8606306951
	  opctemplate may not enable/disable all specified
	  templates, since the Control Agent that is doing the
	  enable/disable is not able to replace the policy config
	  files under %OvAgentDir%\conf\OpC[\vpwin]. Those files
	  can still be in use by the subagents updating their
	  configuration.
	  This problem has been solved by retrying to remove those
	  files once they are no longer locked.
	Change Request: B555017068
	  The default behavior is now again the behavior of
	  A.07.10:
	  If a new logfile is returned by the logfile discovery
	  program, only new lines of the new logfile are processed.
	  If it is required that all lines of newly added logfiles
	  are processed, add following line to the opcinfo file:
	  OPC_NEW_LOGFILE_FROM_BEGIN TRUE
	Change Request: B555017804
	  The Wbem Interceptor (opcwbemi) may abort while
	  processing a policy.
	Change Request: B555017860
	  opcle receives the EOF too early and runs at 100% CPU
	  usage when reading the last event log.
	Change Request: 8606284810, 8606292311, 8606283592
	  In order to prevent reporting duplicate events, the
	  logfile encapsulator writes the current time to the
	  registry. This is done each time after an event log is
	  processed. When starting up the agent, this time is read
	  and the agent starts reading all events after this time
	  from the event log.
	Change Request: B555017407
	  The process opcmona has a memory leaks in different
	  areas:
	  1. When using WMI sources in the Measurement Threshold
	  Policies;
	  2. When monitoring of CODA sources fails and needs a
	  reinitialization;
	  3. When either using the Policy.SourceEx method of
	  scripting or upgrading policies very often.
	Change Request: H555010422
	  opcmsga used the address specified via the
	  OPC_IP_ADDRESS option instead of a local IP address.
	  Only local RPC calls were affected.
	Change Request: B555016446, 8606296412
	  The startup of the OVO agent may trigger some problems
	  that prevent the correct startup of console applications
	  in Microsoft Windows. This behavior has been seen most
	  often under Microsoft Windows 2000.
	  The new agent prevents this problem by implementing a
	  workaround to no longer cause this problem in the
	  operating system.
	Change Request: B555018699
	  The opcle may not use the configured OPC_IP_ADDRESS when
	  monitoring the Windows EventLog.
	Change Request: 8606301574
	  Text defined for the default message is not expanded for
	  logfile, opcmsg and monitor policies.
	Change Request: 8606290676, 8606280832
	  Processes started as scheduled actions by the Windows
	  agent create might hang
	  and stay as orphaned processes forever.
	Change Request: 8606312047
	  The virtual memory usage by the process WinMgmt.exe
	  increases constantly while OVO/Win agents on domain
	  controllers monitor WMI via WMI policies.
	Change Request: 8606313801, B555017924
	  If all the server entries in mgrconf are not resolvable
	  then the agent restart will fail during initialization.
	Change Request: B555017631
	  OVO/Unix includes the ECS 3.2 runtime now.
	  The ECS 3.1 circuits can still be used with the new ECS
	  runtime.
	Change Request: R555022489
	  This defect was caused by freeing memory twice.
	Change Request: B555017530
	  The installation server sets the internal message flag
	  for all messages now.
	Change Request: B555016407
	  Policies registering for WMI Instance Modification Events
	  send a message filled with the entire PreviousInstance
	  and TargetInstance data. To decrease the size of the
	  message text and make the message more useful, the
	  message should be changed to only report the parts of
	  PreviousInstance and TargetInstance data that has
	  actually changed.
	Change Request: B555015872
	  The file transfer through opctranm may fail when the
	  target node is installed through an OVO Windows 7.x
	  management server.
	Change Request: H555010231
	  When the Application Package Monitor (opcapm) is
	  configured and running on the node, the deployment of
	  some policies may cause opcctla to abort.

	PHSS_28943:
	Change Request: 8606294668
	  The trap interceptor does not use new/changed
	  templates/policies when doing SNMP trap interception on a
	  Windows system that has NNM installed.
	Change Request: B555015785
	  One possible cause for opcecaas to report that there are
	  no more free process slots is, that all slots are in use
	  by applications that are running very long or might even
	  hang. In order to have control on this, the opcecaas
	  retrieves the timeout set for the "Annotate Node" in the
	  ECS circuit and kills the process in case it is beyond
	  this timeout.
	Change Request: B555015674
	  The setup may report an error in case your management
	  server name did change from short hostname to a long
	  hostname. e.g.: test123 changed to test123.test.com
	  or even test123.test.com is different to
	  test123.TEST.COM.
	  This caused the old setup to fail, since the management
	  server names are different while doing a string compare.
	  The new version of setup does a case insensitive compare
	  of the names and in case they do not match. It checks
	  whether at least the short hostname of the new and old
	  server matches.
	Change Request: 8606282084
	  Add the specific code to update also the primmgr file,
	  not only the opcinfo file.
	Change Request: B555016133
	  opcwbemi.exe may abort while stopping the agent on
	  Microsoft Windows XP.
	Change Request: B555015741
	  During the shutdown of a system, the agent processes
	  still try to start new processes, causing pop up windows.
	Change Request: B555015449
	  Monitor agent may abort while receiving
	  templates/policies.
	Change Request: 8606290346
	  The version in the registry key
	  HKLM\SOFTWARE\Hewlett-Packard\OpenView\ITO\Agent Version
	  is not updated in the right way during an installation
	  of a new version.
	Change Request: B555015557
	  The control agent has been changed in order to make the
	  restart of an aborted sub agent process configurable.

	  The control agent can be configured to restart aborted
	  sub agent processes. Furthermore it can be defined how
	  often a process should be restarted in a certain time
	  interval.

	  To configure this, you can use the following variables
	  in the opcinfo file:

	  OPC_RESTART_SUBAGENT
	      If set to TRUE, the control agent tries
	      to restart aborted sub agent processes.
	      The restart is done a defined number of
	      times (OPC_RESTART_COUNT) in a specified
	      period of time (OPC_RESTART_MINIMUM_RUN_TIME).
	      In case the process aborts more often,
	      it wont be restarted again.
	    Type/Unit	: TRUE|FALSE
	    Default	: TRUE

	  OPC_RESTART_COUNT
	      Defines how often an aborted sub agent process
	      should be restarted within the specified
	      minimum runtime. In case a process stops more often
	      it wont be restarted.
	      (See OPC_RESTART_SUBAGENT)
	    Type/Unit	: integer
	    Default	: 5

	  OPC_RESTART_DELAY
	      Defines the time the control agent waits
	      before it restarts an aborted sub agent
	      process. The time is specified in seconds.
	    Type/Unit	: integer
	    Default	: 10

	  OPC_RESTART_MINIMUM_RUN_TIME
	      Defines the time frame a sub agent process
	      should run without being restarted more
	      than specified by OPC_RESTART_COUNT.
	      The time is specified in minutes.
	    Type/Unit	: integer (minutes)
	    Default	: 60
	Change Request: B555015199
	  If OPC_IP_ADDRESS (nodeinfo) and OPC_NAMESRV_LOCAL_NAME
	  (opcinfo) were used in combination the entry in
	  OPC_IP_ADDRESS was not used in the right way.
	Change Request: 8606300991
	  opcdcode of Logfile Encapsulator policy shows version
	  number is not updated after a new policy has been
	  deployed, even though the policy is working using the
	  latest version.
	Change Request: 8606303962
	  After time change (beginning of daylight saving time),
	  all logfiles are read from the beginning.
	Change Request: B555015700, B555016671
	  To deploy the new agent version to a system holding an
	  older version of the agent (7.00, 7.10, 7.12, 7.14),
	  execute the following steps:
	  - Call a tool that executes 'opcagt -stop' as 'HP ITO
	  account'. this tool execution will not come back with
	  either 'Successful' or 'Failed' but stay in state
	  'Starting'.
	  This is to stop the subagents. This will speed up the
	  later redeployment, causing this not to fail. Due to the
	  stopped agents, this action will never be completed in
	  the console.
	  - Wait for 2 minutes to make sure the stopping of the
	  agents is finished.
	  - 'Stop' and 'Rerun' this tool execution. The status
	  should switch to 'Failed', reporting that the 'Action
	  could not be executed because action agent is not
	  running'.
	  This is just to verify that the agents are actually
	  stopped.
	  - Now either 'Redeploy All' or deploy the new version of
	  the 'OpenView Operations Agent' package to the node. This
	  will now work without failing and during this process all
	  agents are restarted.
	Change Request: 8606299704, 8606300881, B555016113
	  The error OPC20-63 comes when using environment variables
	  in the "File to be read" field, because the logfile
	  encapsulator does not correctly resolve those environment
	  variables.
	  This has been changed to resolve those variables.
	  The logfile encapsulator also resolves the environment
	  variables in the "File to be executed" field now.
	Change Request: B555015758
	  opcmsgi aborts if one of the set attributes has an
	  unmatched '<'.
	Change Request: B555015170
	  During distribution of templates, the agent might report
	  that 'The codeset "-1" is incompatible to the codeset
	  "acp1252"'.
	Change Request: 8606290908, R555019859, B555015124,
	                8606290897, R555020110, B555015208
	  The OVO Windows agent may loos it's AgentID when
	  doing a "Redeploy All" or installing an agent package
	  with a higher version.
	  Root cause for this problem is the agent setup. It
	  overwrites the currently existing nodeinfo file without
	  merging the values in there.
	Change Request: B555015770
	  Agent should report the current internal status of
	  policies. The Flag OPC_TEMPL_STATUS TRUE can be set now,
	  reporting the status for monitors and logfile policies in
	  the two files 'monitor.status' and 'le.status' in
	  '%OvAgentDir%\tmp\OpC'.
	Change Request: B555015771
	  In order to ensure, that the opcmona.exe always uses the
	  most recent libopc.dll, the dll is copied to
	  %OvAgentDir%\bin. Since the opcmona.exe is located in the
	  same place, this is the first location it will search for
	  the dll.
	Change Request: B555015325
	  During startup a timing issue prevented a connection from
	  opcmsga to opcctla, which generated the message. This
	  message was not immediately reported, but only after
	  receiving a signal. Retries will now prevent the
	  connection failure. If it still fails because opcctla is
	  really not running, the error will be reported
	  immediately.
	Change Request: H555008529, H555008546
	  This is a timing issue, where internal structures are not
	  updated by the signal handler in time for proper values
	  to be written in the PIDS file.

	  An additional check for process presence has been
	  implemented before writing the PIDS file.
	Change Request: 8606297998
	  The ECS engine (opcecm & opceca) might have problems
	  when a circuit is using global dictionaries.
	  (This is the case for the MessageStorm detection ECS
	  circuit).
	Change Request: B555008674
	  The man pages for opcagt and opcragt now document the new
	  option '-version'. The message catalog was updated to
	  show the '-version' option in the usage string of the
	  opcagt and opcragt commands.
	Change Request: B555014942
	  The opcle process loops if a logfile is removed while
	  it is read.
	Change Request: B555015378, B555014944, 8606299437
	  The agent might not be able to monitor instances of the
	  LogicalDisk object and returns no data for it at all.
	  The root cause for this problem is a problem in the used
	  Microsoft API's, it is documented that wildcard patterns
	  can be used to retrieve performance data anywhere. But
	  the implementation only allows either wildcards or names.
	  A workaround for this issue has been implemented. The
	  monitor agent retrieves all data now and filters on the
	  searched values afterwards.
	Change Request: B555014851
	  opcmsga maintains an internal cache to find out the
	  target managers per message ID. The cache expires
	  after 1 hour (can be changed with the opcsvinfo variable
	  OPC_STORE_TIME_FOR_MGR_INFO) and then it runs into a
	  problem in its algorithm so that a message operation on
	  a non-cached message is sent again and again until the
	  last target manager in an internal list can be reached.
	Change Request: B555016032
	  The memory leak that shows up in opcapm.exe has several
	  causes.
	  1. The application opens a connection to the Cluster
	     several times, but does not close it.
	  2. The application reconnects to the Control Agent
	     several times without disconnecting and
	     overwrites the internal connection structure.
	  3. The application leaks while reading the XML
	     configuration file due to a memory leak
	     in the used BBC XML parser.
	Change Request: B555015912
	  Agent installation fails when ntmsgm.dll is in use by
	  other process
	Change Request: B555015484
	  The agent might not be able to execute any external
	  commands. This can be caused by disabling the 8.3
	  filename creation in the registry as it is described in
	  the Microsoft article Q174456.
	  The agent internally tries to convert all path names of
	  executed commands to 8.3, because otherwise you get
	  problems while executing programs with quoted parameters.
	  With this new version the error while converting the path
	  is ignored and the long path name is used instead.
	Change Request: B555015485
	  To avoid that the "HP ITO account" gets locked out
	  on a machine providing network shares a new opcinfo
	  variable has been introduced.

	  Keyword     :
	    OPC_WIN_DONT_USE_PATH_NWDRIVE
	  Description :
	    Force the Windows agent to scan the currently used
	    environment PATH to remove all mapped network
	    paths referenced in the PATH to avoid login
	    errors on the machines providing the network share.
	    Please note, this also removes relative PATH entries
	    like "." or ".." .
	  Type/Unit   :
	    BOOLEAN (TRUE|FALSE)
	  Default     :
	    FALSE
	  Used In     :
	    opcinfo

	  In case you want to use these new features, please edit
	  the %OvAgentDir%\bin\OpC\install\opcinfo file.
	  Add the following entry and restart the agent:
	  OPC_WIN_DONT_USE_PATH_NWDRIVE TRUE
	Change Request: B555015496
	  So far a queue file garbage collection was done, if more
	  than 256 Kbyte were unused. Now the unused space has to
	  be more than 256 Kbyte and more than a quarter of the
	  queue file size. This drastically reduces file I/O when
	  handling large queue files.
	Change Request: 8606293840, 8606293839
	  Monitor agent and Event interceptor grow in memory.
	Change Request: 8606290675, B555015230
	  Agent should report 'agent start' into the opcerror file.
	Change Request: B555015441, B552002692
	  Action agent aborts when process table is full. This
	  happens when more than 52 tools/actions are called from
	  the console in parallel.
	Change Request: R555018185
	  Simplified Chinese codeset is now mapped as a valid
	  codeset.
	Change Request: B555015155
	  Whenever an error is added to the internal error list,
	  a trace line with the DEBUG area ERRLIST is written to
	  the trace file.
	  When the error list is written to opcerror, another
	  trace line with the DEBUG area ERROR is written.
	  ERROR and ERRLIST are distinguished, since some errors
	  are added to the error list, but then later ignored
	  and therefore never appear in the opcerror file.
	Change Request: 8606280846, 8606308495, 8606300125
	  Monitor Agent often reports 'Evaluation of policy
	  stopped'.
	Change Request: B555015277
	  The NT monitor agent aborts in process-monitoring policy
	  when the 'ID Process' performance counter exists twice in
	  the performance registry.
	Change Request: B555015331
	  opcmona holds a central table for all subprocess related
	  information. Advanced monitors are executed in separate
	  threads and could access this table in parallel, thus
	  overwriting each other's data. The table accesses are now
	  serialized by a mutex.
	Change Request: B555015712
	  In order to be able to correctly handle traps that have a
	  source address 127.0.0.1 the trap/event interceptor is
	  now able to replace the localhost address (127.0.0.1)
	  with the IP address of the node processing the trap.
	  In order to enable this, you need to add the following
	  line to the opcinfo file on your managed node:
	  OPC_RESOLVE_TRAP_LOCALHOST TRUE
	Change Request: 8606232431
	  VPO now ignores node names that contain only white space
	  characters without contacting the name service.
	Change Request: B555014781
	  The signal for tracing init was not send from the opcctla
	  and the start of tracing inside of opcwbemi
	  was not done in the right way.
	Change Request: 8606300119
	  The logfile encapsulator does not return the last line of
	  a logfile immediately, if there is no carriage return
	  in this line.

	PHSS_28501:
	Change Request: 8606290723, R555020192
	  The agent may report errors about commands or DLLs that
	  can not be found while executing commands using the OVO
	  Windows agent.
	  The cause is a modification of the system environment
	  variable PATH during the agent runtime. The agent
	  modifies the PATH in order to add certain agent specific
	  directories and to remove duplicate entries in order to
	  limit the size of the PATH. The size has to be reduced
	  because the length of PATH is limited to 2 kByte within
	  command prompts.
	Change Request: B555015308
	  When configuring the agent with apminfo.xml
	  to be cluster aware, the agent may not install newly
	  deployed policies correctly. The root cause
	  for this problem is the wrong status the policy has
	  internally once the Application Package Monitor(APM)
	  wants to inform all other sub agents. All policies are
	  set to status UNCHANGED and therefore no information of
	  the sub agents is done at all. A new status has been
	  introduced to
	  allow the APM to remember that there were modified
	  policies.
	Change Request: B555015349
	  The monitor agent aborts when using templates/policies
	  with external sources as soon as it receives a value
	  from the external source during checking for the
	  threshold with a previously received value. In this case
	  the received value is stored temporary and as soon as
	  the monitor agent tries to process this value it aborts.
	  The root cause is that the monitor agent tries to free
	  up already freed memory.

	PHSS_27388:
	Change Request: B555013936
	  agent installation may fail with many of such messages:
	  T-> Tracing information: Can't get status for service: ..
	  in the inst.log file.
	  The install script may even report that the installation
	  was successfull but it wasn't.
	  The cause for this problem is that the installation tries
	  to stop MS Internet Information Services and OpenView
	  Internet Services in case OVIS has been installed and
	  fails when not all MS Internet Information Services are
	  installed. It then tries to stop the missing services in
	  a loop and in the end just dies or even brings a Dr.
	  Watson error message.
	  This fix just ignores the missing service and goes to the
	  next one.
	Change Request: B553003927, 8606290146
	  opcmsgi and message APIs (agent + server) leak memory
	  when handling messages with custom message attributes.
	Change Request: B555014999
	  The problem while starting batch files on Windows NT is a
	  result of a problem in a Windows API.
	  This seems to have problems handling commands that have a
	  space in there path in case there are also quoted
	  parameters used.
	  The behavior have been modified in the way that the path
	  is converted to the 8.3 filename format.
	  Please note, the command itself is not converted.
	  This is not done, because the command name might be
	  used by the program itself for identification or
	  something similar.
	  The consequence is that you will still see this problem
	  when using commands containing a space under Windows NT.
	  The following will work:
	  c:\temp\test test1\dummy.bat test "test test",
	  but:
	  c:\temp\test test1\dummy 1.bat test "test test"
	  doesn't work on Windows NT.
	Change Request: B555014328
	  opcevti.exe may abort when using <$x>.
	  This issue is caused by traps having a timestamp
	  not in the range between 0 and 2147483647.
	  In case such a trap is received, the timestamp will be
	  reset to 0 now.
	Change Request: B555015077
	  Installation server always receives version A.07.10
	  to be installed on the target node.
	  Therefore it never tries to install the latest agent
	  package, but just A.07.10.
	  Since the version is no longer used to distinguish
	  between the different agent packages on the Management
	  Server it has been completely removed in
	  \usr\OV\databases directory on the Installation Server.
	  on the Installation
	Change Request: B555014961
	  The OVO agent should be able to execute tools and
	  scheduled commands for either the "HP ITO account" or
	  the SYSTEM account user. Or any other user currently
	  running the agent.
	  In any case this should work without a switch user.
	  To allow this, a design change has been made.
	  As soon as the agent executes some action now, it allows
	  actions to be executed as "HP ITO account" even in case
	  the agent is running as SYSTEM and vica versa.
	  Both user accounts are also mapped the way, that
	  no 'Switch User' is performed in case an action
	  contains those user names.

	  For OVO Windows 7.x users there is an updated
	  version (3.0) of the
	  'Using the SYSTEM account for Windows agents' white paper
	  available. This white paper is also part of this patch
	  and can be found unter
	  <InstallDir>\NLS\1033\Manuals\SystemAccount.pdf
	  after installing the patch.
	Change Request: B555014634, 8606289806, 8606289053
	  The OVO Windows agent may not pickup the SYSTEM event log
	  entries with ID 6008 or 6009 during the system is
	  rebooted.
	  The logfile encapsulator that is used to monitor
	  the SYSTEM event log uses entries in the event log
	  itself to find the time the agent has been stopped.
	  In order to achieve this, the agent writes a
	  "agent stop" event to the event log as soon as the
	  opcle.exe process goes down. This fails
	  during system shutdown, since the event log is already
	  stopped.
	  Now the agent is using a registry value instead of the
	  event log to get the correct time and this can be written
	  even late in the shutdown process.
	  This fix also prevents reading the SYSTEM event log in
	  order to find the "Agent Stop" event and therefore makes
	  the agent startup less expensive.
	Change Request: B555013965
	  The memory leak which can occur as described in Microsoft
	  article Q263221. Has been fixed by Microsoft
	  by providing a new pdh.dll, which is included in the
	  patch.
	Change Request: B555013978, B555013977
	  In case the agent buffering and you execute the command
	  opcagt or "opcagt -status" you may get an output like:
	  "Message Agent opcmsga buffering for
	  testmgmtsrv.bbn.hp.com (2376) is running"
	  The output has been correct to look like on the UNIX
	  agents, where the information about the management
	  servers the agent is buffering to comes on the bottom.
	Change Request: B555014558
	  itodiag.exe/OvNtDiag.exe may start looping/hanging
	  forever.
	  This problem occurs in case of an error returned by
	  PdhGetFormattedCounterArray. This brings the program in
	  an endless loop trying to get the correct data. Has been
	  fixed by breaking the loop in error case immediately.
	Change Request: B555014093
	  opcmona may crash (UNIX) or doesn't process all SCHEDULE
	  templates (Windows) when using SCHEDULE templates.
	  This can occur when there are only spaces in
	  one of the schedule fields (Minute, Hour, Day of the
	  Month, Month, Year, Day of the Week).
	  You can verify this by going to the conf/OpC directory on
	  the node and doing an opcdcode monitor. When
	  there are entries like WEEKDAY " " the problem can occur.
	  Now the monitor agent treats sequences of spaces like
	  an empty string that is a wildcard and uses all valid
	  values in the possible range.
	  For WEEKDAY this is 0-6.
	Change Request: B555014513
	  opcle.exe may generate a message storm with messages
	  saying that one of the Windows event logs is corrupt.
	Change Request: B555014714
	  You may receive a message storm with messages:
	  OPC INTERNAL ERROR, CANNOT GENERATE MESSAGE
	  1500 OF SET ZERO
	  Or the opcle may start taking a lot of CPU over a long
	  period of time.
	  This problem is caused by a corrupt Windows event log the
	  Logfile Encapsulator tries to read. With the last version
	  the opcle tried to read on with the next event instead of
	  exiting, but this doesn't work since the Windows API used
	  to read events reports very strange error codes once the
	  event log is corrupt.
	  The behavior of the opcle has been changed.
	  Now it stops monitoring the particular event log that is
	  corrupt and sends a message (OPC30-154) that this event
	  log has to be cleared and the agent must be restarted.
	Change Request: B555014523
	  nt_inst.exe may abort with Dr. Watson while trying to
	  install the Windows agent to a node.
	  This can happen when the command 'nslookup <target node>'
	  doesn't produce valid output on your installation server.
	  The installation server tries to get the WINS name of the
	  target node and therefore tries to get the IP address
	  first via GetHostByName.
	  Internally this failure results in an invalid pointer and
	  accessing this causes the crash.
	  To fix this, the invalid pointer is catched and goes to
	  the next possible case that can be tried to get the WINS
	  name.
	Change Request: B555013510, 8606278103
	  Autoactions are not executed on systems in a NAT
	  environment.
	Change Request: R555017956
	  The monitor agent is terminated if you use a session
	  variable within the message text of a template followed
	  by any other variable (for example $INSTANCE).
	Change Request: B555014715
	  The Control Agent slowly grows in memory usage.
	Change Request: R555018043, R555018267, R555018227
	  Japanese characters in Perl scripts within templates
	  don't get converted correctly into the server code set.
	  If the Japanese characters are used as message text for
	  example these characters are corrupted.
	Change Request: B555012869
	  Instead of using the trap's UUID, the trap interceptor
	  created a new message id for all but the first trap
	  template. The original message id was not set correctly
	  in these cases.
	Change Request: B555014212
	  opcle may report:
	  ntle.c:3670: OpC internal error: Cannot generate message
	  1500 of set 0
	  System Error Number: 1966234 (1e009a) -  (OpC0-1500)

	  The cause is the a wrong error number in the logfile
	  encapsulator itself.
	Change Request: B555014728
	  Currently OvNtKill.exe / itokill.exe requires the
	  libopc.dll as well as some other DLLs required by
	  libopc.dll.
	  This new version is indepented from the other agent
	  libraries.
	Change Request: 8606282247, 8606284806, 8606310913,
	                8606286654
	  Variable replacement is now performed for all Message
	  Defaults fields.
	Change Request: 8606267798
	  In SNMP trap policies when using the <$r> or <$R>
	  variables, on Windows systems the IP address is used in
	  reverse order and therefore there are incorrect results.
	Change Request: B555014667
	  The first lines of a logfile are not forwarded to the
	  message browser when using a command to discover
	  logfiles and the logfile was created after the first
	  polling interval.
	Change Request: B555014708
	  Documented Microsoft API memeory leak in putenv():
	  Q235601. Replaced putenv() by SetEnvironmentVariable()
	Change Request: B555014378
	  opcctla may crash when doing a distribution on a Windows
	  XP node in a NAT environment.
	Change Request: B555014799
	  NT agent reinstall might cause cmd.exe startup issues.
	  This can happen when scheduled actions or tools have been
	  executed as user opc_op without specifying a password.
	Change Request: B555009284
	  There were two different authorization algorithms which
	  interfered with each other. This has been consolidated
	  and is now checked more strictly.
	Change Request: B555013796
	  itomserv.exe / opcntmserv.exe do truncate display and
	  service names and with Japanese multibyte characters it
	  can happen that the text is truncated exactly in the
	  middle of such a character.
	  This wrong character or better first part of a multibyte
	  character confuses the Java and the Motif UI and leads to
	  problems when calling this application.
	  With this version the truncation is done by using a
	  function which is aware of multibyte characters and
	  truncates them correctly.
	Change Request: 8606242614, 8606277183
	  The variables <$LOGFILE> and <$LOGPATH> were replaced
	  after the suppression rules were evaluated. Therefore the
	  comparison did not use the actual logfile name or path,
	  but compared the string "<$LOGFILE>" or "<$LOGPATH>".
	Change Request: B555014882
	  When monitoring Windows performance values by using the
	  NTPerfMon (OVO UX) / Real Time Performance (OVO Windows)
	  sources, there might be an error that not all instances
	  can be found. This is caused by an incorrect parsing of
	  the given instance name. This splitted one instance name
	  into parent instance and instance name even in case there
	  is no parent. This has been corrected now.
	Change Request: B555014759
	  When enabling/disabling policies you might discover a
	  memory leak in the agent processes.
	Change Request: 8606286316
	  When retrieving a list of logfiles by using <`...`>
	  the logfile encapsulator may not retrieve any filename.
	  This has been seen when using perl scripts.
	  The cause for this problem is the StdInput file handle
	  provided to the executed program. This handle is invalid,
	  this doesn't matter as long as the called program doesn't
	  use internal redirection or piping.
	  Now the agent provides a valid file handle and so the
	  internal handling of the executed program should work
	  correctly.
	Change Request: B555013872
	  Agent installation sets unrequired file permissions
	  on files in %SYSTEMROOT%\system32 for "HP ITO account".
	  These unrequired file permissions have been removed
	  and should disappear when installing this patch.
	Change Request: B555014319
	  When reading Windows Event logs the opcle.exe and
	  services.exe may start taking a lot of CPU time for a
	  longer period of time.
	  The cause was a misleading return code from a Windows API
	  which says the event log is on it's end, but it wasn't so
	  the logfile encapsulator permanently looped on the same
	  event instead of proceeding with the next one.
	  This behavior has been fixed by doing some additional
	  checks whether the end of the event log has been really
	  reached. If not, the current event will be skipped.
	Change Request: B555015004
	  Some privileges of the OV-accounts were not deleted
	  after uninstalling the OV Agent.
	Change Request: 8606285428, 8606285429, 8606279910,
	                8606273263
	  SNMP V2 Traps can be received by the windows agent with
	  the following settings now:

	  - disable the Windows
	    SNMP Service / SNMP Trap Service on the Node
	  - add the following line to opcinfo:

	    SNMP_SESSION_MODE NNM_LIBS

	  - restart the agent (opcagt -start)
	Change Request: R555019153
	  When deploying policies from a Windows management server
	  and using the "StoreCollection" method within the Perl
	  or VBScript, the monitor agent might show the Policy name
	  instead of the given metric name or may abort.
	Change Request: B555014591
	  The defect was caused by the double conversion from the
	  server code set to the internal code set, once on the
	  agents side when it sent the internal message to opcmsga
	  and once by opcmsgi when it forwarded the message again.
	  Now, the message is converted back from the internal code
	  set to the server code set in opcmsga before sending the
	  message to the opcmsgi queue. The management server will
	  get the message through opcmsga in the internal code set,
	  and it will convert it into the server code set.
	  The conversion is made only if the internal code set is
	  different from the server code set.
	Change Request: B555013891
	  Even if the IP address of the management server was
	  specified in the mgrconf file, it was not used except for
	  the primary manager. This behavior was changed to give
	  the mgrconf file precedence over name resolution.
	Change Request: B555015072
	  'opcagt -id 12 -stop' may not work when starting as
	  'Administrator' as long as the OVO agent runs with
	  'SYSTEM' (LocalSystem) account.
	  The root cause for this is an 'Access Denied' error,
	  since the 'Administrator' by default is not allowed to
	  send events for processes running as 'SYSTEM'.
	Change Request: H555008631
	  NCS agent open() and stat() calls did not handle EINTR,
	  so a check/loop was implemented to handle it.
	Change Request: B555014442
	  opcle may report system error 32 (Sharing violation) and
	  OPC20-63 when trying to access a file and after such an
	  error the monitoring of this file is stopped.
	  With this fix the opcle tries to read the file
	  at each interval even, when there was an error 32.
	Change Request: B555014570
	  The logfile encaspulator might start consuming CPU when
	  doing Windows Event Log monitoring.
	Change Request: B555012827, B555012829
	  Together with the "Windows XP" support for the VPO
	  Windows agent, there are some changes that are results of
	  changes in the way "Windows XP" works, these
	  changes/issues are documented below.

	  As default templates for "Windows XP" you can
	  use the same than for "Windows 2000".

	  List of all known changes/issues:
	  - Users created by the agent setup (HP ITO account &
	    opc_op) appear on the XP Welcome Screen

	  - Dr. Watson shows internal program name instead of
	    binary name.
	    This may affect you when troubleshooting processes
	    should be necessary.

	  - "itouser /local" doesn't work correctly, but
	    returns errors.
	    The tool can't be used with this switch under
	    Windows XP.

	  - Mapped network drives no longer visible to all users
	    - Windows XP is capable to really separate several
	      user environments
	      and therefore also the network drives mapped by one
	      user can't be seen by the other one
	    - This is a new functionality of Windows XP and
	      may effect user who have shared tools
	      placed on network drives and using them in scripts
	      executed by the agent.
	    - To avoid this don't use mapped network drives
	      but the complete network path to access such tools.

	  - Bug in snmptrap.exe (Microsoft Article Q319680, see
	    http://support.microsoft.com)
	    Microsoft confirmed this to be bug in Windows XP and
	    will be fixed with the first service pack.
	    Microsoft may also provide a HotFix for users
	    needing this functionality.
	    The result is that you can't do trap interception
	    or MIB monitoring.
	Change Request: 8606244582, B555013444, B553001962,
	                R555014598
	  The distribution/deployment of action/command/monitor
	  binaries might fail due to some of them being used.
	Change Request: B555014101
	  Monitor agent may report error OPC30-783 and the
	  initialisation of the first template/policy using Windows
	  Performance data fails.
	  This can be caused by a none critical problem in the
	  Windows registry. The monitor agent queries for the
	  languages, for which there are counter and object names.
	  When accessing some languages the system returns "NOT
	  FOUND" and the monitor agent internally reports this
	  errors and this causes the first template using this
	  source type to fail. All subsequent call will pass, since
	  the query of the registry is done only once to get all
	  performance counter and object names.
	  The opcmona ignores this error completely now.
	Change Request: B555015047
	  opcecaas (Annotation Server) might log error
	  "Illegal NULL parameter (function ) (OpC10-11)"
	  with many similar lines.
	Change Request: B555014281
	  When using the Windows agent SDK (opcapi.h and
	  opcapi.lib) you may get linker unresolved symbol errors.
	  Some of the APIs were not exported in the DLL and LIB and
	  therefore you get linker errors.
	  The missing exports have been added now.
	Change Request: B555014700
	  The monitor agent and action agent on NT leak handles.
	Change Request: B555013540
	  Cause is a problem in the registry
	  That a TcpIP Device is there but
	  doesn't contain any entry for it's IPAddress.
	  Devices with such behavior are skipped now.
	Change Request: B555015050, 8606302001, 8606322283
	  The environment PATH set by the agent during executing
	  external commands may contain several duplicate entries
	  and get very large therefore.
	  To avoid this duplicates and to make the used PATH
	  shorter, the PATH is parsed and all duplicates are
	  removed.
	Change Request: B555013719
	  Message agent remains in buffering mode even when
	  the management server is available again.
	  The reason is that the agent wasn't able to resolve
	  the management server name to an IP address at startup
	  and the agent doesn't try again during runtime.
	  This has been fixed by checking for a resolvable name
	  every time a message should be buffered till the name can
	  be resolved, after this the normal checkalive mechanism
	  which handles buffered message takes place.
	Change Request: 8606187183
	  The opcmsg interceptor restarts after a deploy/undeploy
	  of policies/templates. During this process all the
	  policy/template information is cleaned and read again
	  from a temporary file. Because suppressing times are not
	  stored in this temporary file, this times are lost.
	  Now the suppressing times are taken over to the new data.
	Change Request: 8606282754
	  When calling the perl interpreter without fully qualified
	  pathname within a automatic/operator initiated action or
	  a tool, you may run in problems, since the wrong perl
	  interpreter is used.
	  This is caused by the OVO agent, that contains a perl
	  interpreter. This perl interpreter can be found through
	  the PATH and when executing any command with the OVO
	  agent, the OVO agent directories are always added to the
	  beginning of the PATH. Therefore it is more likely that
	  the perl.exe shipped with OVO will be used.
	  In order to avoid this, you can install the agent with a
	  new option. While setting this option, the perl.exe will
	  be renamed to ovperl.exe.
	  In case you want to use the perl interpreter coming with
	  the OVO Windows agent, please use the environment
	  variable OVPERLBIN to call the perl interpreter in
	  future. This will ensure, that you are independent
	  whether you selected to rename the perl interpreter or
	  not. This variable is always set according to the setting
	  you made.
	  The option is configured differently for agent
	  installations with OVO Unix server and an OVO Windows
	  server.
	  OVO Unix server:
	  - do a manual or ftp installation
	  - before calling opc_inst.bat or opc_pre.bat
	  - edit opcsetup.inf, add
	  [Rename Perl]
	  TRUE
	  - start the installation
	  OVO Windows server:
	  - the tool setmgmtserver.exe has been extended with
	    a new switch /renperl
	  - in order to use ovperl.exe instead of perl.exe, please
	    call "setmgmtserver.exe /renperl /on"
	  - redeploy the agents that the changes are made
	    on the agents
	  The setting you made will be stored to the registry. This
	  ensures that a patch installation will not overwrite your
	  settings.
	Change Request: B555014873
	  The exit code of commands executed through an ECS
	  annotate node and the OVO annotation server is always 0.
	  The reason is an hardcoded return value in the OVO
	  annotation server. With this patch the annotation server
	  passes the received exit code to ECS.
	Change Request: B555013534
	  The "HP ITO Installation Server" service doesn't
	  set the status correctly at startup and therefore
	  it reports an invalid status when the operating
	  system asks for it.
	Change Request: B555012562
	  The control agent might abort with Dr. Watson message
	  while it processes a distribution request.
	  The problem might only occur from time to time because
	  it depends on the system, the data transfer rate
	  between agent and server and other factors.
	  In the end it's a timing issue between two threads which
	  should end in a specific order and especially in
	  environments with firewalls it seems that the threads
	  often end in the wrong order which leaded to the
	  crash because of pointers used in both threads.
	  The issue has been fixed by defining the pointer
	  differently so that they are not lost in case
	  a thread closes.
	Change Request: B555014132
	  During a distribution the agent may report error number
	  OPC30-1203/OPC20-63 when trying to access the cfgchg
	  file.
	  The cause for this problem is that there are several
	  processes trying to get exclusive access to this file
	  at the same time. The problem has been fixed by doing a
	  retry for 10 times in case the error should occur with a
	  delay of one second.
	Change Request: B555013096
	  itoprocs.exe might hang when several itoprocs.exe
	  are running at the same time.
	  The reason is a dead lock between all of them.
	  This is fixed by using a central mutex to protect
	  critical areas.
	Change Request: 8606228146
	  opcntmserv.exe/itomserv.exe is only able to display
	  service names with a specific length of less than
	  18 characters.
	  This patch introduces a new option for the program
	  which allows to set the length via command line switch.
	  The new switch is called /width and takes as parameters
	  the width of the service name and the width of the
	  description.
	  Following example list the service name with a width
	  of 30 characters and completely hides the description.
	  > itomserv.exe /list s /width 30 0
	  The width switch is useful together with the /list and
	  /status option.

Enhancement:
	No

SR:
	R555027071 R555026293 R555026242 R555026201 R555026193
	R555026123 R555025398 R555022806 R555022489 R555021214
	R555020192 R555020110 R555019859 R555019153 R555018267
	R555018227 R555018185 R555018044 R555018043 R555017956
	R555014598 H555012137 H555010925 H555010571 H555010496
	H555010468 H555010422 H555010231 H555010124 H555009399
	H555008631 H555008546 H555008529 B555034081 B555032615
	B555030238 B555030236 B555029983 B555029097 B555028709
	B555028454 B555028360 B555028156 B555028060 B555027932
	B555027720 B555027712 B555027595 B555027075 B555026998
	B555026700 B555026668 B555026529 B555026161 B555026065
	B555025830 B555025826 B555025485 B555025117 B555024892
	B555024748 B555024574 B555024181 B555023880 B555023808
	B555023525 B555023339 B555023337 B555023264 B555022945
	B555022834 B555022373 B555022243 B555022237 B555022224
	B555022044 B555021772 B555021669 B555021291 B555021144
	B555020612 B555020271 B555020101 B555019543 B555019473
	B555018987 B555018953 B555018732 B555018699 B555018506
	B555018498 B555018316 B555018000 B555017924 B555017910
	B555017892 B555017862 B555017861 B555017860 B555017846
	B555017804 B555017631 B555017582 B555017581 B555017560
	B555017530 B555017407 B555017327 B555017068 B555016671
	B555016583 B555016446 B555016407 B555016398 B555016326
	B555016315 B555016259 B555016164 B555016133 B555016113
	B555016044 B555016032 B555015967 B555015912 B555015872
	B555015785 B555015771 B555015770 B555015766 B555015764
	B555015763 B555015758 B555015754 B555015743 B555015741
	B555015712 B555015700 B555015674 B555015673 B555015566
	B555015557 B555015548 B555015538 B555015496 B555015485
	B555015484 B555015449 B555015441 B555015378 B555015349
	B555015331 B555015325 B555015308 B555015277 B555015230
	B555015208 B555015199 B555015170 B555015155 B555015124
	B555015088 B555015077 B555015072 B555015050 B555015047
	B555015004 B555014999 B555014961 B555014944 B555014942
	B555014897 B555014882 B555014873 B555014851 B555014799
	B555014781 B555014759 B555014728 B555014715 B555014714
	B555014708 B555014700 B555014691 B555014667 B555014634
	B555014591 B555014570 B555014558 B555014523 B555014513
	B555014442 B555014378 B555014328 B555014319 B555014281
	B555014212 B555014132 B555014101 B555014093 B555013978
	B555013977 B555013965 B555013936 B555013891 B555013872
	B555013796 B555013719 B555013540 B555013534 B555013510
	B555013444 B555013096 B555012869 B555012829 B555012827
	B555012562 B555009284 B555008674 B555006064 B553010627
	B553003927 B553001962 B552002692 8606360189 8606359013
	8606358486 8606355920 8606354936 8606353730 8606351529
	8606348130 8606347268 8606340667 8606340351 8606340349
	8606339952 8606338462 8606337212 8606333207 8606331230
	8606327029 8606325445 8606323200 8606322495 8606322283
	8606321177 8606320346 8606318934 8606315885 8606313801
	8606312047 8606310913 8606310908 8606308495 8606308208
	8606306951 8606303962 8606302269 8606302001 8606301574
	8606300991 8606300881 8606300125 8606300119 8606299704
	8606299437 8606298307 8606297998 8606296412 8606294668
	8606293840 8606293839 8606292311 8606290908 8606290897
	8606290723 8606290676 8606290675 8606290346 8606290146
	8606289806 8606289053 8606286654 8606286316 8606285429
	8606285428 8606284810 8606284806 8606284425 8606283592
	8606282754 8606282247 8606282084 8606281001 8606280846
	8606280832 8606279910 8606278103 8606277183 8606273263
	8606267798 8606244582 8606242614 8606232431 8606228146
	8606221991 8606187183 8606176226

Patch Files:
	
	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
		v=HP:

	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
		v=HP:
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opc_pkg.Z
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opcsetup.inf
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/monitor/itoprocs.exe
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itomserv.exe
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itodiag.exe
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itokill.exe
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opc_version
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		AgentPlatform

what(1) Output:
	
	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opc_pkg.Z:
		None
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opcsetup.inf:
		None
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/monitor/itoprocs.exe:
		OVO_A.7.25.00.9
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itomserv.exe:
		None
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itodiag.exe:
		OVO_A.7.25.00.9
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/cmds/itokill.exe:
		OVO_A.7.25.00.9
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		A.07.10/RPC_DCE_TCP/opc_version:
		None
	/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
		AgentPlatform:
		None

cksum(1) Output:
	
	OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	3258874557 5094850 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/opc_pkg.Z
	2991632397 415 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/opcsetup.inf
	272834677 24621 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/monitor/
		itoprocs.exe
	3583806128 36909 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/cmds/
		itomserv.exe
	805350726 61484 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/cmds/
		itodiag.exe
	2219491262 28716 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/cmds/
		itokill.exe
	4136466889 8 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/opc_version
	3251105360 6528 /var/opt/OV/share/databases/OpC/mgd_node/
		vendor/ms/intel/nt/AgentPlatform

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_30202 PHSS_29356 PHSS_28943 PHSS_28501 PHSS_27388

Equivalent Patches:
	ITOSOL_00314:
	sparcSOL: 2.7 2.8 2.9

Patch Package Size: 5170 KBytes

Installation Instructions:
	Please review all instructions and the Hewlett-Packard
	SupportLine User Guide or your Hewlett-Packard support terms
	and conditions for precautions, scope of license,
	restrictions, and, limitation of liability and warranties,
	before installing this patch.
	------------------------------------------------------------
	1. Back up your system before installing a patch.

	2. Login as root.

	3. Copy the patch to the /tmp directory.

	4. Move to the /tmp directory and unshar the patch:

		cd /tmp
		sh PHSS_30854

	5. Run swinstall to install the patch:

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -s /tmp/PHSS_30854.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHSS_30854.  If you do not wish to retain a
	copy of the original software, include the patch_save_files
	option in the swinstall command above:

		-x patch_save_files=false

	WARNING: If patch_save_files is false when a patch is installed,
		 the patch cannot be deinstalled.  Please be careful
		 when using this feature.

	For future reference, the contents of the PHSS_30854.text file is 
	available in the product readme:

		swlist -l product -a readme -d @ /tmp/PHSS_30854.depot

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHSS_30854.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	General Information:
	--------------------

	This patch introduces the support for
	Windows 2003 64 Bit version running on Itanium.

	Important Information for IA64 Nodes:
	-------------------------------------

	Virtual Term (PC) application has to run as user
	"HP ITO account" when started on an IA64 system,
	or you use a fully qualified user login
	(username and password).
	In general, the IA64 system doesn't allow a
	passwordless switch user!

	The HP Installation Server method for installing
	agents is not supported on IA64 systems
	(for the Installation Server as well as for the
	node).

	Information for Nodes running Windows XP/2003:
	-----------------------------------------------

	In order to have an automatical recognition of
	the node type when adding a node to the VPO Node
	Bank, there is a manual step neccessary:

	A new Agentplatform file comes with this patch,
	it includes the updated version structure.
	Import that file into the VPO server database
	using the following command:

	a) enter the following directory

	/opt/OV/bin/OpC

	b) execute the following command

	./opcagtdbcfg -p ms/intel/nt -d -force

	Windows XP/2003 Nodes will now be recognized
	automatically by VPO.

	
	BEFORE LOADING THIS PATCH...

	(A) Patch Installation Instructions
	    -------------------------------

	(A1)  Install the patch, following the standard
	      installation instructions.

	      For backing up the system before installing
	      a patch, you may use opc_backup(1m)

	NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
	      ADDRESSED BY THIS PATCH IS DISTRIBUTED
	      (either from the VPO Administrator's GUI
	      or from command line using inst.sh) WHILE
	      RUNNING SWINSTALL.

	NOTE: This patch must be installed on the VPO Management
	      Server system, NOT on an VPO Managed Node directly.
	      Changes will take effect on managed nodes by means of
	      VPO Software Distribution. See chapter 2 of the VPO
	      Administrator's Reference manual for more information.

	
	(B) Patch Deinstallation Instructions
	    ---------------------------------

	(B1)  To deinstall the patch PHSS_30854 run swremove:

	      NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
	            ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
	            from the ITO Administrator's GUI or from
	            command line using inst.sh) WHILE RUNNING
	            SWREMOVE.

	      # swremove PHSS_30854