N.3 Changes in 10-00

• Support for the following OSs was added:

  • Microsoft(R) Windows(R) 7 Enterprise

  • Microsoft(R) Windows(R) 7 Professional

  • Microsoft(R) Windows(R) 7 Ultimate

  • Microsoft(R) Windows Server(R) 2003, Datacenter Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Datacenter Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Standard Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Datacenter x64 Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

  • Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition

  • Microsoft(R) Windows Server(R) 2008 Datacenter

  • Microsoft(R) Windows Server(R) 2008 R2 Datacenter

  • Microsoft(R) Windows Server(R) 2008 R2 Enterprise

  • Microsoft(R) Windows Server(R) 2008 R2 Standard

  • AIX V7.1

  • Linux 6 (AMD/Intel 64)

  • Linux 6 (x86)

• The following OSs are no longer supported:

  • AIX 5L V5.3

  • HP-UX 11i V2 (IPF)

  • Solaris 9 (SPARC)

• A description of language type settings was added.

• jp1hosts2 information can now be used as JP1-specific hosts information

• JP1/Base can now use IPv6 addresses to communicate.

• Users with JP1/Base administrator privileges can now use JP1/Base.

• The event log trapping function now supports event types added in Windows Vista and Windows Server 2008.

• Log file traps can now monitor log files in SEQ3 and UPD format.

• Log file traps can now be started using a log-file trap startup definition file.

• The description of log files that cannot be monitored by a log file trap now includes files in which log information is always recorded at the beginning.

• Log file traps in HP-UX, Solaris, and AIX can now monitor log information output in UTF-8 encoding.

• The definitions in the log-file trap startup definition file can now be collected and distributed by the event service.

• Users can now select whether to monitor the starting and stopping of monitored hosts when using the health check function to monitor a remote host. Accordingly, the following changes were made:

  • The STOP_CHECK parameter was added to the health check definition file.

  • The auto-forward-off flag was added to the options parameter of the event server settings file.

  The occurrence conditions for JP1 event 0000474A were also added.

• Descriptions of the IP address used in an environment with multiple LAN connections were added and changed.

• A cautionary note was added regarding setting the installation folder when installing JP1/Base in an x64 environment.

• A description of the default location and permission settings of the JP1/Base installation folder was added.

• JP1_ITSLM_Admin and Cosminexus_vMNG_Admin were added as default permissions for JP1users in the description of the user management function.

• To enhance password security, a way to change the password save method was added.

• A description of how to update the common definition information was added.

• A cautionary note about registering JP1/Base services with cluster software was added.

• Descriptions of situations where communication settings need to be changed, and the definition files to use to make those changes have been added and changed.

• Changes were made to the communication protocol settings file specified when executing the jbssetcnf command.

• A cautionary note about stopping the event service was added.

• A procedure for temporarily changing the linked directory server was added.

• The tasks required when changing the IP of a computer running JP1/Base were changed.

• A command for checking the status of the log-file trap management service (daemon) was added.

• A procedure for suppressing the messages output when you execute the jbs_start.cluster command was added.

• The return values of the following commands were amended:

  jbsadduser, jbschgpasswd, jbslistuser, jevexport, jevlogreload

• The -s option was added to the jevdef_distrib command, allowing for distribution of the definition information in the log-file trap startup definition file.

• The -s option was added to the jevdef_get command, allowing definition information to be collected from the log-file trap startup definition file. The -r option was also added to allow definition information to be collected for specific hosts.

• The -x option was added to the jevlogstart command, allowing the output source host name for log data to be set in the JP1_SOURCEHOST extended attribute when converting log entries to JP1 events. Also, the specification of the -s option was made case sensitive.

• Errors in the format of the jbs_setup_cluster (Windows only) command were corrected.

• Cautionary notes were added for the following commands:

  jbsrt_distrib command, jevexport command

• The description of the -r option of the jevlogstart command was changed.

• A cautionary note about specifying batch file names that contain spaces in parameters of the start sequence definition file was added.

• The instruction not to insert a space or any other characters in front of a parameter name at the start of a line now mentions hash marks (#) (code 0x23).

• A cautionary note was added regarding the client-bind parameter of the event server settings file, about situations where multiple addresses are specified.

• A cautionary note has been added about log types in Windows Vista and Windows Server 2008.

• The log-file trap startup definition file has been added as a distribution definition file.

• The description of the @action-definition-file-name parameter in the section about distribution definition files was changed.

• The format of the directory server linkage definition file (Windows only) was amended.

• The following JP1 events were added:

  00003A25, 00003A26, 00003A27, 00003A28, 00003A29, 00003A2A, 00003A30, 00003A31, 00003A32, 00004724, 00004725, 0000474C, 0000474D

• The PP name of JP1 event 00003A71 is now different depending on whether a remote monitoring event log trap or a JP1/Base event log trap generated the event.

• The PP name of JP1 events whose ID is the value specified in the ACTDEF parameter of the action definition file is now different depending on whether a remote monitoring log file trap or a JP1/Base log file trap generated the event.

• The format of the ACTDEF parameter in the action definition file for log file trapping was amended.

• There is now more information to be collected when troubleshooting errors.

• The jbs_setup_cluster (Windows only) can now not be executed while JP1/Base is running.

• Data is now output to additional log files during installation.

• Remote monitoring logs were added to log file traps and event log traps.

• The file name of the trace log for the jbs_killall.cluster command was changed.

• The number of jbscomd_api.exe processes was amended.

• jelallog was added to the list of UNIX processes.

• The direction in which jp1bscom data passes through the firewall was added.

• A note about V5 compatibility in Windows Server 2008 was added to the cautionary notes regarding JP1/SES events.

• The procedure for outputting data to operations logs was changed.

• Messages were added, changed, and deleted.

• Compatible compilers were added, changed, and deleted.

To Page Top