ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahg_5.4.0.1/rzahgexprpts.htm

150 lines
8.0 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2005 by IBM Corporation">
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights - -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<title>Experience reports</title>
<link rel="stylesheet" type="text/css" href="ic.css">
</head>
<script language="Javascript" src="synch.js" type="text/javascript">
</script>
<body>
<h1>Experience reports</h1>
<p>The following experience reports are available.</p>
<p><strong>Note</strong>: PDF versions of the Experience Reports are only available on the Web version of the iSeries Information Center. The Experience Report abstracts are available on both the Web and CD versions of the iSeries Information Center.</p>
<table width="100%" border="0" cellpadding="5">
<!-- Description for Printable PDFs came from rzatc_rzatcprintable.txt -->
<tr>
<td class="hilightbarlink"><a href="../experience/ifs_saveabstract.htm"><strong>Backing
up the integrated file system</strong></a></td>
<!-- Description for Database overview came from rzatc.txt -->
<!-- Description for Database information finder came from rzatd.txt -->
<!-- Description for Administration came from rzahf.txt -->
<!-- Description for Commitment control came from rzakj.txt -->
<!-- Description for Performance and optimization came from rzajq.txt -->
<!-- Description for Programming came from rzahgdbp.txt-->
<!-- Description for Reference came from rzahgdref.txt-->
<!-- Description for Related information came from rzatd_rzatdadd.txt -->
<tr>
<td> <p>For many customers the amount of data stored in the integrated file
system is small enough that it is not a concern. However, for an increasing
number of iSeries<sup>(TM)</sup> customers the backup of their integrated file
system data has created additional considerations for their backup. This
experience report documents information about integrated file system backup.
It is intended to help those customers who are experiencing concerns.
</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/mcfirewallabstract.htm">Configuring
Management Central connections for firewall environments</a></strong></td>
<tr>
<td> <p>This report details Management Central connections and the configurations
required to enable Management Central to operate within a variety of firewall
environments. As a distributed management application, Management Central
requires numerous incoming and outgoing TCP/IP socket connections. In
contrast, the basic premise of a firewall is to restrict or modify incoming
and outgoing connections.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/consolidationabstract.htm">Consolidating i5/OS, AIX, and Linux partitions on your IBM eServer i5 system</a></strong></td>
<tr>
<td> <p>Consolidating i5/OS<sup>(TM)</sup>, AIX<sup>(R)</sup>, Linux<sup>(R)</sup>, and Windows<sup>(R)</sup> servers onto an eServer i5 system allows for maximum resource utilization. This report details the benefits of consolidation as well as outlining the general process for moving to the new system.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/idrinkabstract.htm">iDrink SMB scenario</a></strong></td>
<tr>
<td>
<p>This report documents the IBM eServer<sup>(TM)</sup> i5 Customer Solution Test team's
experience of implementing a small-to-medium business (SMB) scenario using
WebSphere<sup>(R)</sup> Application Server - Express and Lotus<sup>(R)</sup>
Domino<sup>(R)</sup>. In this scenario, WebSphere Application Server - Express
for iSeries is used to establish an initial Web presence through
dynamic Web pages, database access, and directory server access. A Lotus Domino application
meanwhile provides internal dynamic Web pages for iDrink employees.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/jobacctabstract53.htm">Job
accounting</a></strong></td>
<tr>
<td> <p>Job accounting is a function available on every iSeries
Server that can be used to track usage of system resources.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/oraclemigabstract.htm">Oracle
migration </a></strong></td>
<tr>
<td> <p>This document describes the process of migrating an Oracle<sup>(TM)</sup>
database to DB2<sup>(R)</sup> Universal Database<sup>(TM)</sup> for iSeries
using the Oracle Migration Toolkit (MTK).</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/work3abstract.htm">The
performance adjuster (QPFRADJ)</a></strong></td>
<tr>
<td> <p>The iSeries server has the ability to automatically
manage the shared memory pools without any user interaction. This function
is controlled by the performance adjustment system value, QPFRADJ. </p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/ipla-3-exprabstract.htm">Reducing
iSeries IPL time</a></strong></td>
<tr>
<td> <p>This report describes ways you can control how long it takes to start
your iSeries server. The initial program load (IPL) for an iSeries server
is made up of three major stages. First the hardware is powered up, second
the Licensed Internal Code is initialized, and third operating system
is started. This report focuses on performance aspects of the IPL that
change based on how you configure and use your system. </p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/wmrstateabstract53.htm">Restricted
state </a></strong></td>
<tr>
<td> <p>At times you might need to perform work on your iSeries server without
interference from other users. Performing that work while the system is
in the restricted state allows you to do just that.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/spool_expreport.htm">Spool
performance considerations</a></strong></td>
<tr>
<td> <p>As hardware capacity and workloads on the iSeries increase, considerations
should be made to ensure that performance of spool operations is efficient.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/work1abstract.htm">Subsystem
configuration</a></strong></td>
<tr>
<td> <p>The default subsystem configuration included with the operatng system is a basic
subsystem configuration that works well for small systems. However, as
the number of users increase on the system, it is desirable to split
the work into multiple subsystems to better manage the work on the system.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><strong><a href="../experience/work2abstract.htm">Tuning
prestart job entries</a></strong></td>
<tr>
<td> <p>This document shows how to manage prestart jobs to improve overall
system performance.</p></td>
</tr>
<tr>
<td class="hilightbarlink"><a href="../experience/jobattabstract53.htm"><strong>Work
management job attributes</strong></a></td>
<tr>
<td> <p>There are several work management interfaces that can be used to retrieve
information about jobs. The same job attribute may be available on several
different user interfaces. Determining the best interface to use for a
particular piece of information can be difficult. This experience report
provides a summary of information to make it easier to determine which
interfaces to use when dealing with job attributes.</p></td>
</tr>
</table>
</body>
</html>