L.8 Changes in version 09-50

• Grouping monitoring on the business viewpoint (business group monitoring) is now available.

• The following contents have been added, relating to how to specify business groups:

  • Prerequisites when the path name is used to specify a business group

  • Applying business groups and monitoring groups also applies the names on the Central Console.

  • Deleting business groups or monitoring groups will disable the specified contents.

• Mapping statuses for the following cases have been added:

  • When conditions are not matched.

  • When the values have been already set.

• The description of IM host accounts has been changed.

• Actions to be taken in the following case have been added:

  • In the agent configuration, when the system hierarchy in the tree display area on the IM Configuration page is displayed in gray.

• The following descriptions have been added:

  • If an agent configuration is applied after the system hierarchies are synchronized, information on the base managers is cleared.

  • An agent configuration must be applied when a remote monitoring configuration is used.

• The operations related to exclusion control for virtualization configuration information have been changed as follows:

  • Virtualization configuration information on the same host cannot be edited concurrently from different IM configuration management viewers.

  • Virtualization configuration information for the different hosts can be edited concurrently from different IM configuration management viewers.

• Configuration files that can be collected for individual JP1/Base versions are now organized in one place.

• The statuses of applied configuration files and hosts have been added.

• Descriptions of predefined filters, which filter log files and event logs that are collected from remotely monitored hosts, have been added.

• The following contents have been added:

  • If a log file is output while other log files are being collected, the same log file might be trapped twice.

  • Conditions of log files

• A description that log information is not collected when JP1/IM - Manager is stopped has been added. Also, a description that the maximum number of retries for a remote-monitoring event log trap is three times has been added.

• The following description has been added regarding the JP1 events issued by remote monitoring: the event-source-host mapping function is required to display and define a monitored host name as the event source host.

• The number of files to be exported has been changed.

• An example of the total number of business groups and monitoring groups has been added to the examples of system scale for database size.

• IM Configuration Management of JP1/IM - Manager has been added to the descriptions about processes.

• Direction of communication through a firewall when information about remotely monitored hosts is collected has been added.

• The limits that apply to JP1/IM - Manager when using IM Configuration Management have been updated.

  • The limit of the number of remotely monitored hosts has been deleted.

  • The total number of business groups and monitoring groups has been added.

  • The maximum number of hosts that can be set for a business group or a monitoring group has been added.

  • The limits of the number of tiers for business groups and monitoring groups have been added.

  • For AIX or HP-UX, the maximum number of IM Configuration Management viewers that can be connected to one JP1/IM - Manager has been added.

• The required operating permissions are now separately described for when restrictions on viewing and operating business groups are enabled and for when they are disabled.

• Restrictions when JP1/IM - Manager 09-50 and JP1/IM - View 09-50 are connected to the previous versions of products have been added.

• The following types of monitoring and management are now available for the hosts in the remote monitoring configuration (with the remote communication settings):

  • Messages in log files and Windows event logs that are generated on a host on which JP1/Base has not been installed can now be remotely monitored.

  • Definition information (profiles) set on remotely monitored hosts can now be checked or edited.

  • The IM Configuration Management window has been divided into the Edit Agent Configuration window (for editing the agent configuration) and the Edit Remote Monitoring Configuration window (for editing the remote monitoring configuration).

• Multiple monitored hosts can now be grouped from the business viewpoint so that individual business groups can be monitored separately.

• The event source host for an event that caused a JP1 event can now be displayed and defined by using event-source-host mapping.

• Extended mode has been added to common exclusion-conditions, the number of definitions for condition groups and the number of specifiable attributes have been increased, and event conditions can now be compared by specifying date and time.

• The following method has been added to the methods for executing commands in JP1/IM - View: frequently used commands can be registered as command buttons and executed when the buttons are clicked.

• How to convert event inheritance information into JP1 event information has been added.

• Notes for the configuration file names for log file trap information have been added.

• JP1 events can now be manually registered as incidents in JP1/IM - Service Support.

• A description has been added for the connection method when JP1/IM - View is used for Remote Desktop Connection.

• When setting the event guide by using variables (placeholder strings), URL-encoded character strings or Base64-encoded UTF-8 character strings can now be output in event guide messages.

• The following files have been added to the files and folders that can be referenced or edited by the user:

  • Folder for the common-exclusion-conditions display item definition file

  • Common-exclusion-conditions display item definition file

  • Model file for the common-exclusion-conditions display item definition file

  • System color definition file

  • Model file for the system color definition file

  • Folder for remote command definitions

  • Command button definition file

  • Model file for the command button definition file

  • Event-source-host mapping definition file

  • Model file for the event-source-host mapping definition file

• The following items have been added to the table of regular expressions that can be used in JP1/IM functions:

  • Severity changing function

  • Common exclusion-conditions (extended mode)

  • Event-source-host mapping function

• A procedure has been added for monitoring remote-monitoring event traps for monitored hosts on which Windows 7, Windows Server 2008, Windows Server 2008 (x64), Windows Server 2008 R2 (x64), or Windows Vista is running even when the user is logged off.

• Procedures for setting local security are now separately described for JP1/IM - Manager hosts and monitored hosts.

• A procedure for editing the registry has been added.

• A procedure for setting the UseDNS or LookupClientHostnames item has been added to the procedures for setting up SSH servers.

• The user who logs in to the monitored hosts when the following operations are performed under the SHH setting has been changed to the user who can remotely monitor the target host:

  • Create keys (for Windows)

  • Place the secret keys on the JP1/IM - Manager hosts (for Windows)

  • Place the public keys on the remotely monitored hosts (for Windows)

• The following description has been added: to display Event source host name after JP1/IM - Manager is upgraded, E.JP1_SOURCEHOST must be added to the file that defines which items are displayed for event conditions.

• Notes when hosts are registered in IM Configuration Management have been added.

• The following description has been added: in the agent configuration, if on the IM Configuration page, the system hierarchy in the tree display area is displayed in gray due to the change of host names or mismatch of configuration definition information, the configuration must be applied again.

• The following description has been added: if the profiles have not been applied, all the profiles that have not been applied and saved on the server will be deleted.

• The following description has been added: the agent configuration must be applied when the remote monitoring configuration is used.

• Item name Assigned JP1 resource group name in the Create Business Group window and the Edit Business Group Basic Information window has been changed.

• The following description has been added: if business groups and monitoring groups are applied, the names of the business groups and monitoring groups specified in the definitions on the Central Console are also changed to the latest names.

• A procedure for deleting files and folders (directories) after deleting the IM Configuration Management database has been added.

• Prerequisites for the settings of individual databases have been added.

• Commands can now be registered to command buttons and executed. A procedure has been added for this.

• A function for monitoring logs on the remotely monitored hosts has been added. A description of the procedure for setting this function has been added.

• Remotely monitored hosts can now be monitored. Related descriptions have been added to the following functions:

  • Register hosts.

  • Change host information.

• IM configuration was divided into agent configuration and the remote monitoring configuration. Descriptions have been changed accordingly.

• A function restricting viewing and operating business groups has been added. A description of the procedure for setting business groups has been added accordingly.

• A procedure for acquiring exclusive edit rights has been added.

• A procedure for setting profiles on remotely monitored hosts has been added.

• Event source host name has been added to the items that can be set and displayed.

• Common exclusion-conditions are now divided into the basic mode and the extended mode. Descriptions have been changed accordingly.

• A procedure for setting the display colors of JP1 events has been added.

• An event-source-host mapping function has been added. A procedure for using this function has been added accordingly.

• A description that the font size can be changed in the Event Console window has been added.

• A function restricting viewing and operating business groups has been added. A procedure for setting this function has been added accordingly.

• A description of services has been added to the prerequisites for the physical host environment.

• Conditions for physical host names and logical host names have been added to the prerequisites for cluster operations.

• The following description has been added: if JP1/IM - MO is used, the JP1/IM - Message Optimizer service on the connection source host must be stopped.

• A procedure for suppressing error reports to Microsoft has been added.

• A procedure for deleting only logical hosts on a JP1/IM - Manager host has been added.

• Because the events managed by JP1/IM - Manager can be manually registered as incidents in JP1/IM - Service Support, a description of the procedures for setting up the linkage between JP1/IM - Manager and JP1/IM - Service Support has been added.

• The following files have been added to the files to be backed up:

  • Common-exclusion-conditions display item definition file

  • System color definition file

  • Command button definition file

  • Event-source-host mapping definition file

• The log file trap (remote) and event log trap (remote) have been added to the command that collects the service status.

• Log files and directory list has been updated.

• Causes and corrective actions have been added to the descriptions of problems when remote-monitoring log file traps are running.

• The cause and corrective actions have been added for when a dialog box remains displayed while the IM configuration management viewer is being processed.

• How to operate when JP1/IM - MO is used has been added.

• The Files to be backed up when the remote monitoring configuration is used have been added.

• A description of the tasks required when the passwords for the manager and the remotely monitored hosts are changed in the remote monitoring configuration has been added.

• The differences in the agent configuration and the remote monitoring configuration when the monitoring configuration is changed in the system configuration have been added. Also, related notes have been added.

• Event source host name has been added to the display items and display names in the event list.

• A description of the difference between event information mapping and event-source-host mapping has been added.

• Restrictions when restrictions are enabled on viewing and operating business groups have been added.

• A procedure for calling the Select the process work board as the registration target window of JP1/IM - Service Support has been added because JP1 events can be registered as incidents.

• Descriptions and examples of the following options of the jcochfilter command have been added to the description of activating or deactivating common exclusion-conditions:

  • -on

  • -off

  • -e

• How to execute commands by using the command buttons has been added.

• The versions of the functions displayed in the Tool Launcher window have been clarified.

• A description of the Edit Remote Monitoring Configuration window used for remote monitoring has been added.

• A description of the management of business groups has been added.

• A description of remote monitoring operations has been added.

• The following items have been added to the information to be exported or imported:

  • Remote authentication information

  • Business group information

  • Monitoring group information

• In troubleshooting, actions to be taken when a business group or monitoring group is specified for the target host have been added to the actions to be taken when commands cannot be executed.

• Actions to be taken for remote monitoring problems have been added.

• The following description has been added: In Search host in the Event Search Conditions window and Target host in the Execute Command window, the name of a host belonging to the business group that can be viewed by the logged-in JP1 user must be entered.

• The causes of some display items in the IM configuration management viewer becoming different or disabled have been added.

• System Common Settings has been added to the Edit menu in the IM Configuration Management window.

• Detailed information displayed for remote monitoring has been added.

• The following description has been added to the description of Host name in the Edit Host Properties window: if a host is registered in a business group, Host name cannot be changed.

• A description for when hosts are deleted from the agent configuration has been added to the description for the Edit Agent Configuration window.

• A description has been added explaining that, in the following windows, it is mandatory to fill in the User name and Password fields if characters are entered in any other fields.

  • Remote Monitoring Settings window

  • WMI/NetBIOS page in the System Common Settings window

  • IM Host Account page in the System Common Settings window

• Notes have been added about deleting hosts from the remote monitoring configuration and reapplying when in the Edit Remote Monitoring Configuration window.

• The following contents have been added to the Configuration File page of the Display/Edit Profiles window:

  • Details about the individual statuses have been added to the displayed Application status item.

  • The following description has been added: when log file trap information or remote-monitoring event log trap information is selected, predefined filters can be set.

  • The following descriptions have been added to the items displayed in Configuration File:

    - Restrictions on characters that can be used in Monitoring log file have been added to the description of start options.

    - A description for when Apply by Restarting must be executed has been added to the description of saving and applying settings.

  • A description has been added to explain the Startup Options to be displayed when remote-monitoring event log trap information is selected in the tree display area while WMI/NetBIOS (NetBIOS over TCP/IP) connection is used.

• The Common Exclusion-Condition Settings (Extended) window has been added. This window can be used to set JP1 event exclusion-conditions and their validity periods for an event acquisition filter.

• The IM Configuration Management window has renamed to the Edit Agent Configuration window.

  Also, the following contents in the Edit Agent Configuration window have been corrected:

  • The menu items have been renamed.

  • Remote communication type (which is used to display the communication method of remote monitoring) and Configuration type (which is used to display configuration type) have been added.

• The Remote Monitoring Settings window has been added to set information for remote monitoring.

• The Edit Remote Monitoring Configuration window has been added to enable editing of the remote monitoring configuration managed by IM Configuration Management.

• The Create Business Group window has been added to enable creation of business groups.

• The Edit Business Group Basic Information window has been added to enable editing of basic information about business groups.

• The Create Monitoring Group window has been added to enable creation of monitoring groups.

• The Edit Monitoring Group window has been added to enable editing of basic information about monitoring groups.

• The Add/Delete Monitoring Group Hosts window has been added to enable registering or release of registration of hosts for business groups or monitoring groups.

• The Change Monitoring Group Name window has been added to enable changing monitoring group names.

• The System Common Settings window has been added to enable saving and managing the values of setting items as common setting values.

• For the registration of incidents, the Select the process work board as the registration target window of JP1/IM - Service Support can now be called from JP1/IM - Manager by clicking the Register Incident button.

• The following contents have been added to the Event Details window and the Edit Event Details window:

  • The Execute Command button has been added. It displays the Execute Command window for command execution.

  • For the registration of incidents, a JP1/IM - Service Support window can now be called by clicking the Register Incident button.

• When a correlation event on a host other than the one to which the user logged in from JP1/IM - View is displayed under Display Items in the Related Events (Correlation) window, incident registration in JP1/IM - Service Support is disabled.

• The following contents have been added to the Severe Event Definitions window, the Event Search Conditions window, the Settings for View Filter window, and the Detailed Settings for Event Receiver Filter window:

  • Event source host name can now be specified in event conditions.

  • When the -ignorecasehost option of the jcoimdef command is specified as ON, if an option other than Regular expression is selected for Source host and Event source host name, now the character string is not case sensitive.

  • The path name for a business group name can now be specified for Source host and Event source host name.

• The mode of common exclusion-conditions can now be selected from basic mode and extended mode. Accordingly, descriptions for individual modes have been added to the General page of the System Environment Settings window and to the Common exclusion-conditions groups in the Event Acquisition Conditions List window.

• The Preferences window has been changed to a tabbed view and the display size of fonts can be specified.

• The following contents have been added to the Action Condition page of the Action Parameter Detailed Definitions window:

  • Event source host name can now be specified in event conditions.

  • When the -ignorecasehost option of the jcoimdef command is specified as ON, if an option other than Regular expression is selected for Source host and Event source host name, now the character string is not case sensitive.

  • A business group name can now be specified as the path name when Source host and Event source host name are specified for the character string to be edited.

  • A business group name and monitoring group name can now be specified as the path name in Target host.

• In the Conditions for Updating List of Action Results window, a business group name and monitoring group name can now be specified as the path name in Host.

• The following contents have been added to the Execute Command window:

  • Commands can now be executed by clicking the command buttons.

  • A business group name or monitoring group name can now be specified as the path name in Target host.

• Agent configurations, remote monitoring configurations, and business groups can now be monitored. Accordingly, the menu items in the IM Configuration Management window have been changed.

• A Business Group page (Business Group tab) has been added to the IM Configuration Management window. It displays the configuration of business groups and monitoring groups.

• On the Host List page of the IM Configuration Management window, the following items have been added to the items displayed in low-level host information:

  • Collection status

  • Remote communication type

  • Business Group

  • Monitoring Group

• The remote monitoring configuration can now be monitored. Accordingly, Remote monitoring settings has been added to the items displayed in Basic Information on the Host List page of the IM Configuration Management window.

  Also, a display item in Detailed Information has been changed as follows:

  • Collection status -> Information collection result

• The following contents have been added on the IM Configuration page of the IM Configuration Management window:

  • Icons that indicate agent monitoring and remote monitoring have been added.

  • Remote (Base manager) and Remote (Integrated manager) have been added to the relationship between the host type and display information.

• Remote communication settings can now be specified in the Register Host window and the Edit Host Properties window.

• Profiles for remote-monitoring log file traps can now be added in the Add Profile window.

• Editing business group has been added to the items displayed in the Login User List window.

• Descriptions of the number of commands that can be executed at the same time have been added to the functional overview of the following commands:

  • jcfaleltdef command (for Windows only)

  • jcfaleltreload command (for Windows only)

  • jcfaleltstart command (for Windows only)

  • jcfaleltstat command (for Windows only)

  • jcfaleltstop command (for Windows only)

  • jcfallogdef command

  • jcfallogreload command

  • jcfallogstart command

  • jcfallogstat command

  • jcfallogstop command

  • jcfexport command

  • jcfimport command

  • jcfvirtualchstat command

• The -filter option has been added to the following commands:

  • jcfaleltdef command (for Windows only)

  • jcfaleltstart command (for Windows only)

  • jcfallogdef command

  • jcfallogstart command

• Descriptions of the return values for the following commands have been changed:

  • jcfaleltdef command (for Windows only) (Return value: 21)

  • jcfaleltreload command (for Windows only) (Return value: 12, 21)

  • jcfaleltstart command (for Windows only) (Return value: 21)

  • jcfaleltstat command (for Windows only) (Return value: 1, 21)

  • jcfaleltstop command (for Windows only) (Return value: 12, 21)

  • jcfallogdef command (Return value: 8, 21)

  • jcfallogreload command (Return value: 21)

  • jcfallogstart command (Return value: 8, 21)

  • jcfallogstat command (Return value: 1, 21)

  • jcfallogstop command (Return value: 12, 15, 21)

  • jcfexport command (Return value: 21)

  • jcfimport command (Return value: 21)

  • jcfview command (for Windows only) (Return value: 5)

  • jcfvirtualchstat command (Return value: 21)

• Descriptions of the return values for the following commands have been deleted:

  • jcfaleltdef command (for Windows only) (Return value: 13)

  • jcfaleltstat command (for Windows only) (Return value: 10, 13)

  • jcfaleltstop command (for Windows only) (Return value: 16)

  • jcfallogdef command (Return value: 13)

  • jcfallogreload command (Return value: 8)

  • jcfallogstat command (Return value: 10, 13)

  • jcfallogstop command (Return value: 16)

• The following description has been added to the description for the jcfaleltreload command: if the start options are changed by the jcfaleltdef command or in the Display/Edit Profiles window, they are not applied even after reloading.

• Descriptions of the -o option for the following commands have been changed:

  • jcfaleltstart command (for Windows only)

  • jcfallogdef command

  • jcfallogstart command

• A description for deleting profiles has been added to the functional overview of the jcfallogdef command.

• Descriptions of the -r option for the following commands have been changed:

  • jcfallogdef command

  • jcfallogstart command

• The following description has been added to the description for the jcfallogreload command: if a value of any parameter other than the MARKSTR and ACTDEF parameters is changed by the jcfaleltdef command or in the Display/Edit Profiles window, it is not applied even after reloading.

• A description of the files to be deleted after the jcfdbunsetup command is executed has been added.

• A description about "while remote monitoring is performed" has been added to the functional overview of the jcfimport command.

• The apply-IM-configuration-method definition file (jp1cf_applyconfig.conf), which is automatically generated when JP1/IM - Manager is installed, has been added.

• A description about the maximum character string size has been added to HEADLINE in the remote-monitoring log file trap action-definition file.

  Also, definition examples have been added.

• An example of definitions in the remote-monitoring event log trap action-definition file has been added.

• IMDBHOSTNAME has been added to the setup information file (jimdbsetupinfo.conf).

• JP1 events have been added.

• Event occurrence of JP1 events and messages have been changed.

  00003FD3

• Log type has been deleted from the details of event ID 00003FD0.

• The following items have been added to the details about event ID 00003FD2:

  • API where error occurred

  • Monitored host name

• The following item has been added to the details about event ID 00003FD3:

  • Monitored host name

• The jimdbupdate command has been added so that the IM database can be updated.

• The following description has been added to the functional description of the jcfmkcsdata command: generating import files for the Central Scope for which the monitoring tree information of a business group has been added.

• The following commands have been added so that remotely monitored hosts can be managed:

  • jcfaleltdef command (for Windows only)

  • jcfaleltreload command (for Windows only)

  • jcfaleltstart command (for Windows only)

  • jcfaleltstat command (for Windows only)

  • jcfaleltstop command (for Windows only)

  • jcfallogdef command

  • jcfallogreload command

  • jcfallogstart command

  • jcfallogstat command

  • jcfallogstop command

• The jcochcefmode command has been added so that the operation mode of common exclusion-conditions can be changed.

• The description of the -d option of the jcashowa command has been changed. Also, the description of how to specify the option by seconds has been added.

• Notes for the following commands have been added:

  • jcfdbsetup

  • jcfdbunsetup

  • jcodbsetup

  • jcodbunsetup

• The -r and -g options have been added to the following commands:

  • jcfexport

  • jcfimport

• The -g option has been added to the jcfmkcsdata command. Also, return value 11 has been added.

• The following files have been added to the definition files that are enabled when the jco_spmd_reload command is executed:

  • A file that defines which items are displayed for event conditions (attr_list.conf)

  • Common-exclusion-conditions display item definition file (common_exclude_filter_attr_list.conf)

• Notes at system startup and when JP1/IM - Manager is manually started have been added to the functional description of the jco_start command (UNIX only).

• Notes when JP1/IM - Manager is manually stopped have been added to the functional description of the jco_stop command (UNIX only).

• The following options have been added to the jcochfilter command:

  • -on

  • -off

  • -ef

  • -check

• A cross reference for CSV output format has been added to the functional description of the jcoevtreport command and the operand name of the -f option has been changed.

• The following options have been added to the jcoimdef command:

  • -cmdbtn

  • -hostmap

  • -bizmonmode

  • -ignorecasehost

• Notes about when JP1/IM - MO is used have been added to the descriptions for the following commands:

  • jimdbbackup

  • jimdbrecovery

  • jimdbrorg

  • jimdbstop

• The remote-monitoring log file trap action-definition file has been added to define actions of the remote-monitoring log file trap function.

• The remote-monitoring event log trap action-definition file has been added to define actions of the remote-monitoring event log trap function.

• The event-source-host mapping definition file (user_hostmap.conf) has been added. This file is used to define the conditions and the mapping source for a JP1 event to which the event source host is mapped by using the event source host mapping function.

• The values that can be specified for "ACTIONLIMIT"=dword:hexadecimal-value in the automated action environment definition file (action.conf.update) have been added.

• The system color definition file (systemColor.conf) has been added to define the settings of the colors used in the event list.

• The common-exclusion-conditions extended definition file has been added to define event conditions and applicable periods of common exclusion-conditions in extended mode.

• The common-exclusion-conditions display item definition file (common_exclude_filter_attr_list.conf) has been added to define items displayed in the Attribute name display area in the Common Exclusion-Condition Settings (Extended) window.

• The command button definition file (cmdbtn.conf) has been added to define the command buttons displayed in the Execute Command window.

• Event source host name, which is used for event-source-host mapping, has been added to the attribute names that can be specified for event conditions for the following files:

  • Automated action definition file (actdef.conf)

  • User profiles (defaultUser | profile_user-name)

  • Event guide information file (jco_guide.txt)

  • Correlation event generation definition file

  • severity changing definition file (jcochsev.conf)

  • Definition file for opening monitor windows

• The business group name and monitoring group name have been added to the items that can be specified for the host name in the automated action definition file (actdef.conf).

• The comments in the table of variables that can be used for action definitions in the automated action definition file (actdef.conf) have been changed.

• Event source host name, which is used for event-source-host mapping, has been added to the display items that can be specified in the file that defines which items are displayed for event conditions (attr_list.conf).

• A description for the configuration file for converting information (event_info_replace.conf) has been added.

• A description for when an error is detected by the health check function has been added to the description of FAILOVER in the health check definition file (jcohc.conf).

• The description of DESC_VERSION and EV_FILE in the event guide information file (jco_guide.txt) has been changed.

• EV_USER has been added in the event guide information file (jco_guide.txt).

  Also, descriptions of replacing characters for event guide messages have been added.

• The maximum sizes of the attribute values for the correlation event generation definition file have been added.

• The description of extended attributes that cannot be specified as attribute names in the correlation event generation definition file has been changed.

• The description of the correlation approval events for the correlation event generation definition file has been added.

• A description of linking with JP1/IM - Service Support has been added in the incident manual-registration definition file (incident.conf).

• The versions of the products that can link with JP1/IM - Manager and the supported OSs have been added to the list in the Web page call definition file (hitachi_jp1_product-name.html).

• In the description of the operation definition file of the IM configuration management viewer (jcfview.conf), the Edit IM Configuration window has been changed to the Edit Agent Configuration window.

  Also, descriptions of the Edit Remote Monitoring Configuration window have been added.

• Descriptions about the active host name have been added to the description of ONLINEHOSTNAME in the cluster setup information file (jimdbclustersetupinfo.conf).

• The description of item names in the item file has been changed.

• The description of attribute names, operators, and operands that can be specified for event conditions in the filter file has been added.

• The following messages have been added:

  KAVB0012-W to KAVB0015-W, KAVB0110-E, KAVB0267-E, KAVB0354-I, KAVB0415-E to KAVB0419-E, KAVB0422-E to KAVB0424-E, KAVB0682-I, KAVB0683-E, KAVB0760-W, KAVB0761-W, KAVB0888-E to KAVB0891-E, KAVB0893-E to KAVB0900-E, KAVB0902-W, KAVB0903-E, KAVB0961-E, KAVB0962-W, KAVB1012-E to KAVB1021-W, KAVB1104-W, KAVB1105-W, KAVB1136-W to KAVB1141-E, KAVB1533-E, KAVB1534-E, KAVB1593-W to KAVB1688-W, KAVB1692-W, KAVB1694-E, KAVB1851-I to KAVB1872-W, KAVB4016-W, KAVB4440-W to KAVB4445-E, KAVB4507-W, KAVB4508-W, KAVB4650-I to KAVB4664-E, KAVB4666-W to KAVB4669-E, KAVB4706-W to KAVB4708-W, KAVB4710-I to KAVB4713-E, KAVB4790-W, KAVB8450-I to KAVB8457-E, KAJV0016-W, KAJV0017-W, KAJV0500-I to KAJV0503-E, KAJV0600-I to KAJV0614-E, KAJV0616-W to KAJV0619-E, KAJV2016-W, KAJV2017-W, KAJV2500-I to KAJV2503-E, KNAN11197-I to KNAN11202-I, KNAN20009-I, KNAN20045-Q, KNAN20046-E, KNAN20048-W, KNAN20057-I, KNAN20238-Q, KNAN20240-Q, KNAN20303-Q, KNAN20364-I, KNAN20365-I, KNAN20418-Q to KNAN20433-E, KNAN20437-Q, KNAN20438-Q, KNAN20440-Q, KNAN21185-E, KNAN21186-E, KNAN21300-E to KNAN21311-E, KNAN21400-W to KNAN21404-E, KNAN22032-E, KNAN22033-E, KNAN22265-E to KNAN22267-E, KNAN22270-E to KNAN22273-I, KNAN22307-I to KNAN22321-E, KNAN22413-E to KNAN22415-E, KNAN22451-E, KNAN22452-E, KNAN22454-E, KNAN22462-E, KNAN22529-E, KNAN22700-E to KNAN22702-E, KNAN22861-W, KNAN22862-E, KNAN22870-I to KNAN22874-E, KNAN22890-E, KNAN26000-I to KNAN26003-E, KNAN26006-I, KNAN26008-E, KNAN26010-E, KNAN26025-W to KNAN26028-E, KNAN26039-E, KNAN26050-I, KNAN26055-I to KNAN26059-E, KNAN26063-E to KNAN26065-E, KNAN26069-E, KNAN26072-W, KNAN26073-W, KNAN26078-I, KNAN26081-E, KNAN26091-I to KNAN26095-E, KNAN26097-E to KNAN26110-W, KNAN26117-E, KNAN26119-E, KNAN26121-I, KNAN26123-E, KNAN26131-I, KNAN26132-E, KNAN26138-E, KNAN26140-W, KNAN26142-W, KNAN26153-E, KNAN26155-E, KNAN26163-E, KNAN26181-E, KNAN26182-E, KNAN26187-E, KNAN26189-E, KNAN26196-E, KNAN26206-E, KNAN26208-E to KNAN26212-E, KNAN26214-I, KNAN26216-I, KNAN26217-I, KNAN26223-Q to KNAN26226-I, KNAN26230-I, KNAN26239-I, KNAN26243-E, KNAN26247-E, KNAN26249-I, KNAN26251-I, KNAN26252-I, KNAN26256-I, KNAN26258-E, KNAN26261-I, KNAN26265-E to KNAN26267-E, KNAN26269-I, KNAN26271-I, KNAN26274-I, KNAN26276-I, KNAN26278-I, KNAN26279-I, KNAN26281-I, KNAN26283-I, KNAN26285-I, KNAN26287-I, KNAN26292-E to KNAN26298-E, KNAN26317-I to KNAN26323-E, KNAN26325-E to KNAN26332-E, KNAN26334-E, KNAN26336-E, KNAN29087-E, KNAN29088-E, KNAN11203-I

• The output destinations of the following messages have been changed:

  KAVB8430-E, KNAN20354-Q, KNAN20362-Q, KNAN20520-I, KNAN20810-I, KNAN20816-E, KNAN20821-I, KNAN21180-E, KNAN21181-E, KNAN22267-E, KNAN22270-E to KNAN22272-I, KNAN22529-E, KNAN22819-E, KNAN22832-E, KNAN22846-E, KNAN22861-W, KNAN26003-E, KNAN26039-E, KNAN26050-I, KNAN26058-E, KNAN26063-E, KNAN26069-E, KNAN26072-W, KNAN26073-W, KNAN26078-I, KNAN26092-E, KNAN26097-E, KNAN26138-E, KNAN26153-E, KNAN26163-E, KNAN26187-E, KNAN26196-E, KNAN26208-E, KNAN26209-E, KNAN26211-E, KNAN26317-I, KNAN26318-I to KNAN26320-E

• Dialog boxes were added to the table of output destinations for messages related to IM Configuration Management (part 3).

• The following messages have been deleted:

  KNAN22870-I to KNAN22874-E, KNAN24100-I to KNAN24107-I, KNAN26008-E, KNAN26010-E, KNAN26059-E, KNAN26064-E, KNAN26065-E, KNAN26117-E, KNAN26121-I, KNAN26123-E, KNAN26131-I, KNAN26132-E, KNAN26180-E, KNAN26265-E, KNAN26292-E, KNAN26295-E, KNAN26298-E, KNAN26325-E

• The corrective actions to be taken for the following messages have been changed:

  KAVB0422-E, KAVB0423-E, KAVB1586-W, KAVB1587-E, KNAN11122-E, KNAN11123-E, KNAN11144-W, KNAN20000-E, KNAN20105-E, KNAN20230-Q, KNAN21400-W, KNAN21402-E, KNAN21403-E, KNAN22012-E, KNAN22058-E, KNAN22201-E, KNAN22205-E, KNAN22249-E, KNAN22253-E, KNAN22265-E, KNAN22403-E, KNAN22406-E, KNAN22407-E, KNAN22422-E, KNAN22424-E, KNAN22426-E, KNAN22466-E, KNAN22468-E, KNAN22500-E, KNAN22526-W, KNAN22701-E, KNAN22702-E, KNAN22806-E, KNAN22823-E, KNAN22824-E, KNAN24005-E, KNAN26002-E, KNAN26027-I, KNAN26039-E, KNAN26057-E, KNAN26063-E, KNAN26081-E, KNAN26095-E, KNAN26097-E, KNAN26099-E, KNAN26119-E, KNAN26163-E, KNAN26187-E, KNAN26208-E, KNAN26209-E, KNAN26296-E, KNAN26328-E, KNAN29041-E, KNAN11141-E

• The following messages have been changed:

  KAVB0682-I, KAVB0683-E, KNAN20040-E to KNAN20042-E, KNAN20222-Q, KNAN20226-Q, KNAN20227-Q, KNAN20230-Q, KNAN20326-Q, KNAN20354-Q, KNAN20362-Q, KNAN20437-Q, KNAN20438-Q, KNAN20440-Q, KNAN22012-E, KNAN22015-E, KNAN22200-I to KNAN22206-E, KNAN22208-E, KNAN22209-I, KNAN22249-E, KNAN22263-E, KNAN22271-I, KNAN22272-I, KNAN22407-E, KNAN22500-E, KNAN22823-E, KNAN22824-E, KNAN24005-E, KNAN26097-E, KNAN26099-E, KNAN26187-E, KNAN26196-E, KNAN26281-I, KNAN26328-E, KNAN29922-E

• The explanations of the following messages have been changed:

  KAVB0246-E, KAVB1513-W, KNAN20048-W, KNAN20222-Q, KNAN20230-Q, KNAN20238-Q, KNAN20303-E, KNAN20354-Q, KNAN20362-Q, KNAN20364-I, KNAN20365-I, KNAN21300-E to KNAN21310-E, KNAN22033-E, KNAN22200-I to KNAN22206-E, KNAN22208-E, KNAN22209-I, KNAN22263-E, KNAN22266-E, KNAN22267-E, KNAN22270-E to KNAN22272-I, KNAN22406-E, KNAN22407-E, KNAN22498-E, KNAN22500-E, KNAN22701-E, KNAN22861-W, KNAN24005-E, KNAN26000-I, KNAN26027-I, KNAN26039-E, KNAN26050-I, KNAN26063-E, KNAN26092-E, KNAN26093-I, KNAN26095-E, KNAN26098-E, KNAN26100-E, KNAN26103-I to KNAN26105-W, KNAN26108-I to KNAN26110-W, KNAN26119-E, KNAN26138-E, KNAN26187-E, KNAN26211-E, KNAN26212-E, KNAN26214-I, KNAN26216-I, KNAN26217-I, KNAN26226-I, KNAN26230-I, KNAN26249-I, KNAN26251-I, KNAN26252-I, KNAN26256-I, KNAN26261-I, KNAN26269-I, KNAN26271-I, KNAN26274-I, KNAN26276-I, KNAN26278-I, KNAN26279-I, KNAN26281-I, KNAN26283-I, KNAN26285-I, KNAN26287-I, KNAN26293-E, KNAN26294-E, KNAN26322-E, KNAN26323-E, KNAN26326-I to KNAN26330-E

• The operations of the system for the following messages have been changed:

  KNAN20048-W, KNAN20303-E, KNAN20330-E, KNAN20530-W, KNAN21307-E, KNAN21310-E, KNAN22266-E, KNAN22267-E, KNAN22270-E to KNAN22272-I, KNAN22506-W, KNAN22514-W, KNAN22515-W, KNAN22517-W, KNAN22528-W, KNAN22861-W, KNAN26000-I, KNAN26039-E, KNAN26081-E, KNAN26095-E, KNAN26163-E, KNAN26208-E, KNAN26294-E

• The following message IDs have been changed:

  KNAN20303-Q to KNAN20303-E

  KNAN21308-E to KNAN21308-Q

  KNAN22518-W to KNAN22518-E

  KNAN26025-W to KNAN26025-E

  KNAN26098-W to KNAN26098-E

To Page Top