Download PDF of this I0.
When prompted, select to Save the file to your computer.

User Technologies

I0 Document for
Logical Partition Advisors

Product: RID3
DCR Numbers: 12161.1, 12164.1
AS/400 VRM: V5R1M0
Document Owner: Garrett Winn
winnga@us.ibm.com
Dept. 533
253-6918
Authors: Garrett Winn
Send all comments to: winnga@us.ibm.com
Document last changed: November 16, 1999 9:39am

This document is based on the I0 package template (Version I0TMPLD.1995.1) on PROCDOC.

APPROVAL: This document has been approved by Jerry Barry on xx/xx/1999.

THE ON-LINE VERSION IS THE MASTER VERSION

Preface

  1. Change History

Date Change Description

10/01/1999

Created by Garrett Winn
11/16/1999 Changes incorporated based on review
mm/dd/yyyy  
  1. Approval Procedure

Any revision or new versions must be approved prior to replacement of the old version. The approver is listed on the title page.
  1. How to access this document

This document is located in the following places: All previous versions of this document are to be destroyed.
  1. Reviewers, Invitees, Attendees

Reviewer Role Required Attend Review Time
Dennis Kappers 533 Manager      
Jackie Curry 533 Team Lead X comments  
Mike Kelly UT Test Team Lead X    
Tom Parry UT 2E    
Jerry Barry UT T-CEM X    
Joe DiCecco UI T-CEM      
Mark Manges SLIC LPAR Developer X X 1.5 HR
Dennis Schmidt UI Designer X    
Frank Bonner UT Information Developer X comments  
Susan Benysh UCD Team Lead X X  
Jeff Scheel LPAR Product Designer      
Samuel Choy UT LPAR Writer X X 2 HR
Georgia Toogood UT Product Designer: IC X X 1 HR
Beth Hettich UT Product Designer X    
Beth Taylor UT Product Designer X comments  
Doug O'Hara UT Product Designer X    
Doc Dockter UT Product Designer X X .5 HR
Elizabeth Crockett UT Product Designer X X 1 HR
Kirsten Schmidt UT Product Designer X    
Edith Lueke UT Product Designer X comments  
Paula Muth UT Product Designer X X 1 HR
Alyson-Kathleen Riley UT Product Designer X X .5 HR
Richard White Information Developer      
Mike Horsman NLS   comments  
Bergie Young NLS      
Cheryl Henning UT Editor   X 1 HR
Rita Roque UT Editor      
Joyce Lewis UT Unity Team Lead      
Selwyn Dickey TSC      
Mike Temple UT Tools, Tech Admin      
Tim Covalt End-to-End Testing      
Dan Cutshall Tech Support CEM      
Todd Gabriel Tech Support - Product Intro   X .5 HR
John Tillotson SME      
Dan Laun SME      
Karen McWaters Graphic Design Team Lead      
Dave Boutcher Ease of Use S-CEM      
Kathleen Bies Information Developer   X 1 HR
Jill Shepherd Test Team   X 1 HR
Chris Seyer Advisor Project Leader X X 1 HR

Contents
Preface 2
1.1.1Change History 2
1.1.2Approval Procedure 2
1.1.3How to access this document 2
1.1.4Obsolete copy handling 2
1.1.5Reviewers, Invitees, Attendees 3
1.0Introduction and Overview 7
1.1 Overview 9
1.1.1Associated Line Items 9
1.1.2Associated UT DCRs 10
1.1.3Associated Development DCRs 10
1.2 User Requirements 10
1.3 User Centered Design 11
1.3.1Personas, User Goals and Tasks 13
1.4Usage Scenarios 13
1.5 Usability Testing 13
2.0 External Interfaces 14
2.1Graphical User Interface Design 14
2.1.1Advisor: LPAR Planning Advisor 14
2.1.1.1Description 14
2.1.1.2Flow 14
2.1.1.3Panel: Welcome 16
2.1.1.4Panel: Select a server 18
2.1.1.5Panel: Select processors 20
2.1.1.6Panel: Number of partitions 22
2.1.1.7Panel: Divide processors 24
2.1.1.8Panel: Select interactive workload 26
2.1.1.9Panel: Divide interactive workload 29
2.1.1.10Panel: Divide memory 33
2.1.1.11Panel: Divide disk storage 37
2.1.1.12Panel: Select partition communications types 40
2.1.1.13Panel: Select IOP type for load source 43
2.1.1.14Panel: Select feature code for IOP for load source 45
2.1.1.15Panel: Select IOP type for alternate restart device 47
2.1.1.16Panel: Select feature code for IOP for alternate restart device 49
2.1.1.17Panel: Select switchable IOP for alternate restart device 51
2.1.1.18Panel: Select switching partitions for IOP for alternate restart device 53
2.1.1.19Panel: Select IOP type for console 55
2.1.1.20Panel: Select feature code for IOP for console 58
2.1.1.21Panel: Select switchable IOP for console 60
2.1.1.22Panel: Select switching partitions for IOP for console 62
2.1.1.23Panel: Use electronic customer support 64
2.1.1.24Panel: Select IOP type for electronic customer support 67
2.1.1.25Panel: Select feature code for IOP for electronic customer support 69
2.1.1.26Panel: Select switchable IOP for electronic customer support 71
2.1.1.27Panel: Select switching partitions for IOP for electronic customer support 73
2.1.1.28Panel: Add additional hardware 75
2.1.1.29Panel: Select hardware type for additional hardware 77
2.1.1.30Panel: Enter name for additional hardware 79
2.1.1.31Panel: Select feature code for IOP for -- - --- - (hardware name) 80
2.1.1.32Panel: Select quantity for -- --- ---- (hardware name) 82
2.1.1.33Panel: Select switchable IOP for -- --- ---- (hardware name) 85
2.1.1.34Panel: Select switching partitions for IOP for -- --- ---- (hardware name) 87
2.1.1.35Panel: Select type of disk protection 88
2.1.1.36Panel: Select disk unit type 90
2.1.1.37Panel: Assign disk unit types 92
2.1.1.38Panel: Partition summary 96
2.1.1.39Panel: Provide additional information 98
2.1.1.40Panel: Enter contact information 100
2.1.1.41Panel: Results 106
2.1.2Advisor: LPAR Troubleshooting Advisor 108
2.1.2.1Description 108
2.1.2.2Flow 108
2.1.2.3Panel: Welcome 109
2.1.2.4Panel: Select a search method 110
2.1.2.5Panel: Enter the SRC 112
2.1.2.6Panel: SRC question 114
2.1.2.7Panel: Select an SRC 116
2.1.2.8Panel: Results (SRC) 118
2.1.2.9Panel: Enter the error message 119
2.1.2.10Panel: Select error message 121
2.1.2.11Panel: Select an error message 123
2.1.2.12Panel: Results (Error Message) 125
2.2Help Objects 126
2.3 Book Objects 126
3.0 Considerations 127
3.1 NLS Considerations 127
3.2 Compatibility Considerations 127
3.3 Integration/Build Considerations 127
3.4 Distribution 127
3.5Design Alternatives 127
3.6Dependencies 127
3.7 Restrictions and Limitations 128
3.8Migration and Coexistence Considerations 128
3.9 UT Testing Considerations 128
3.9.1Equipment Needed 128
3.9.2Test Subjects Needed 128
3.10 New Terms and Concepts 128
3.11 Reference Materials 129
3.11.1UT Strategy 129
3.11.2Information Center CAI 129
3.11.3Other Topic CAI and I0 Documents 129
3.11.4Information Plan 129
3.11.5Programming SAI/CAI/I0 Documents 129
3.12 I0 Review Issues/Resolutions 130
4.0 Appendix A: LPAR Documentation Focus Group Summary 131

  1. Introduction and Overview

This I0 document outlines the information plan for all V5R1 Logical Partition advisors (the Ops Nav help and Information Center documentation is covered in a separate I0). This information plan focuses on work that is being done for AS/400 Information Center advisors.

Logical partitions are the distribution of resources (processors, memory, and I/O devices) within a single AS/400 system, making it operate as if it was two or more independent systems. Logical partitions will be supported on the following system models in V5R1:

Logical partitions will NOT be supported on any of the following models because of hardware restrictions: The following tables indicate the combination of releases that will run on different AS/400 systems. The tables are built on the model of allowing n-1 / n+1 (n = current release) SLIC release from the primary partition (To contain testing costs, this has been changed from the previous -2/+1 plan). So, for instance, a primary partition using V4R5 software (assuming compatible hardware), can generally have secondary partitions at V4R4 and V5R1. The tables show the allowed software releases within a secondary partition when the primary partition is using a certain software release.

V5R1 introduces the following new functions that need to be addressed in the LPAR advisors:

The following is not being offered in LPAR for V5R1.

This I0 covers the V5R1 plans for the LPAR advisors:

A separate I0 will cover the rest of the documentation being produced for LPAR.

A separate I0 was held for the GUI design of the LPAR interface and wizards. See Dennis Schmidt for more information.

Documentation Not Covered in This I0

There are many other deliverables that have or will have LPAR-related information. Because they are not exclusively related to logical partitions, and since they can be covered more effectively outside this I0, they will be covered in separate CAIs and Topic I0s. These include the following:

Specifically, this I0 addresses LPAR customer documentation delivered through the following method: Because of all the new functionality for LPAR to be included in this release of V5R1, we will need to add new content to the existing advisors. Unclear steps will also be fixed.

We will also continue to get customer feedback through additional UCD work to determine how internal and external customers use the current information so that we can identify areas for improvement.

We will continue to work with the TSC to get feedback from customers about the product and the documentation.

  1. Associated Line Items

Line Item Description Information Deliverable
7EU Information Development Articles/Web Pages
7LB LPAR - Stage 2 Articles/Wizards/Web Pages
7H2 Management Central Java Infrastructure Wizards/Operations Navigator Interface
7H5 Management Central and Clusters Wizards/Operations Navigator Interface

349

LAN Console Wizards/Operations Navigator Interface

  1. Associated UT DCRs

DCR Component Description Contact

12159

RID3 Printing and What's new topics Garrett Winn

12160

RID3 Learning about logical partitions Sam Choy

12161

RID3 Planning for logical partitions Garrett Winn

12162

RID3 Creating logical partitions Sam Choy

12163

RID3 Managing logical partitions Sam Choy

12164

RID3 Troubleshooting logical partitions Garrett Winn

98153

GUIX LPAR Help Frank Bonner
  1. Associated Development DCRs

DCR Component Description Contact

97885

GYLP LPAR GUI design Dennis Schmidt

97486

SLIC LPAR Development Mark Manges
  GUIX/UGLP LPAR GUI Management Jeff Scheel
  1. User Requirements

The LPAR Personas document goes into great detail about user requirements and what types of companies would use LPAR, and for what reasons.

Based on customer input, we have developed the following user scenario for logical partitions:

The scenario is Logical Partitions, which is why it is a main level (under System Admin) heading. Or more specifically, the scenario is "How do I create and use an LPAR system?"

Each topic discussed in this I0 is a part of that scenario. They are all steps to completing the scenario.

First, the customer needs to know what it is and what it can do (Learning about logical partitions); second, once they decide that this is for them, they need to know the "ingredients" for an LPAR system (Planning for logical partitions); third, they need to know how to create the partitions on their system (Creating logical partitions in Ops Nav help and the Create wizard).

This fulfills the basic scenario of creating.

To use an LPAR system, they need to know the various controls and how to use them (Managing logical partitions in Ops Nav help and the Delete wizard).

Finally, the customer may also experience problems with either creating the partitions or managing them, so they need to know how to find and fix these problems (Troubleshooting logical partitions).

So, every topic is part of the main scenario. They have been broken into the logical steps every customer must take to create and use an LPAR system.

The advisors are supplementary to these tasks, helping the user complete the task quicker and easier.

  1. User Centered Design

UCD held a focus group for LPAR on March 26, 1999. While the main point of this group was not necessarily to get feedback on the existing LPAR documentation, some customers did comment on it. A summary is available in Appendix A: LPAR Documentation Focus Group Summary. We will continue to ask for customer opinion. We will also hold similar focus groups to look at the new information deliverables (the advisors).

The following are some suggestions about the documentation that were made during the focus group:

  1. LPAR is not easy to understand, plan, setup. Anything that can make this easier, faster, more accurate would be optimal. Include sufficient overview/background material; many examples, case studies, and detailed configuration steps; adequate FAQs (frequently asked questions); and ample troubleshooting information.
  2. The online documentation needs to have better navigation. Have everything all in one place rather that having to go to 3 or 4 different manuals to figure out how to do things that pertain to LPAR.
  3. You need to improve the documents' clarity. Good documentation on how to plan, setup, and manage logical partitions needs to be made available so users are not going into this blind. It would help save time in figuring out exactly what needs to be done.
  4. Provide better online help in DST/SST. Provide help within LPAR configuration/management displays so that we wouldn't have to "hunt" to find an online document.
  5. There needs to be a document that will help us understand the hardware. It's confusing for testers and customers and support line test subjects who have never had to know hardware before. Too hard to teach old dogs new tricks. A person should be able to create a partition without any additional assistance.
  6. A configurator to play with would help in planning purchasing needs, as well as the actual partitioning procedure. This GUI tool could be available online.

The following is how we plan on addressing these concerns:

  1. The Troubleshooting advisor will help provide adequate troubleshooting information. The Planning advisor will help users complete the work sheets quicker, and with less confusion.
  2. We will use more words to help the user predict where a link will take them. The Hardware Planning Guide will still be included in the Information Center, with only very technical, often-changing information on the LPAR web site, so that almost all LPAR-specific information is in one place.
  3. The advisors will be edited by a member of the Editing team for clarity and correctness.
  4. Although we will not be focusing on DST help, Sam Choy will create detailed and informative online help for Operations Navigator that will give the users all the information they need, when they need it.
  5. The Planning advisor will help shield users from the complexities of the hardware by asking them simple questions that will be used by the advisor to fill in the complex Planning Work Sheet.
  6. The Planning advisor will let customers "try out" various configurations during planning, in the sense that they can try out various configurations of hardware to see what hardware they will need. The customer can do this as often as necessary without having to send the information to the Technology Solutions Center.
As we write our information for V5R1, we plan to base our task analysis (for usage scenarios and usability testing) on information gathered from specific User Centered Design (UCD) activities. These planned activities for UT include: Detailed personas for LPAR were created for the GUI design. These personas are available in the LPAR Persona Report document. See Garrett Winn for a copy or download the Smartmaster document. When prompted, select to Save the file to your computer.
  1. Usage Scenarios

We will work with the UT Test team to create scenarios for new and significantly changed information for V5R1. This is especially true of the advisors. We will create a list of potential inputs for each panel, as well as invalid inputs that should result in an error message. Current plans are in the UT Test Plan database (See Mike Kelly for more information).
  1. Usability Testing

Mike Kelly's Team will provide usability testing for the Logical partition planning advisor and all Ops Nav help, wizards, and usability. The writers will perform usability testing for all other articles.
  1. External Interfaces

An advisor is an application that provides a recommendation or suggestion based on input from the user. Advisors, unlike wizards, do not perform any functions or change any system values. Advisors are written in HTML, JavaScript, and Java.

In V4R5, UT is adding advisors to the Information Center. Advisors will be located (that is, linked to from) the sections of the Information Center to which they pertain. Also, an "Advisors" link from the main menu will be added to display a list of advisors.

No PDF files of advisors will be provided. Advisors are included in both the internet and CD versions of the Information Center. Translation instructions will be included to address JavaScript coding and the Java applet in the advisors.

  1. Graphical User Interface Design

LPAR has advisors in the Information Center for the following LPAR tasks: The Operations Navigator Software Design Guidelines can be found at:

http://w3.rchland.ibm.com/projects/AS400-Unity/GUIDesign/Guidelines/
  1. Advisor: LPAR Planning Advisor

    1. Description
Since customers indicated that they want to be shielded from the hardware of their systems, the Planning Advisor will ask simple questions about the customer's wants, which wants will be used to fill in the Planning Work Sheet. Customers will not need to know feature numbers, use complex tables, or memorize hardware requirements. In V5R1, this advisor will get smarter, and understand switching requirements better, feature code combinations, and provide the customer with placement information.

The Planning advisor helps the user to complete the LPAR Hardware Planning Work Sheet. The user should be able to complete the work sheet faster, and with fewer errors than just doing it by hand. Eventually, the advisor will be able to provide product assurance and hardware placement information that is currently being done by the TSC or business partners.

  1. Flow
This advisor flows from beginning to end with relatively no deviation. Many panels are set in a loop for the number of partitions requested, as follows:


Figure A: LPAR Planning Advisor Flow

  1. Panel: Welcome

Figure 1: LPAR Planning Advisor - Welcome Panel
  1. Push buttons
Push button Results
Start >> Displays the next advisor panel.
  1. Properties
N/A

  1. Behind the Panel
This panel is actually part of the Planning articles. Since content will be sourced in HTML for V5R1, a Start button can be included on the page instead of the text link at the bottom.

The design of the frames will be based on the V5R1 Information Center design (which may not look like figure 1). Because this design has not yet been created, the rest of the figures in this document will only focus on the content part of the panel--the rest of the web page has been erased.

  1. Panel: Select a server

Figure 2: LPAR Planning Advisor - Select a server Panel
  1. Push buttons
Push button Results
< Back Displays the welcome panel.
Next > Displays the next advisor panel.
  1. Properties

Select server drop-down box:

Description: User must select a server
Field type:
Drop-down box
Possible values: 620, 640, 650, 720, 730, 740, 820, 830, 840, S20,

S20 ISV, S30, S30 ISV, S40, S40 ISV
Default value: 620
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: The type of server selected determines what the next panel is.
DBCS considerations: N/A
Other unique characteristics: N/A

Radio Button Group 1:

Description: User must select a new or existing server to plan for
Field type: Radio Buttons
Possible values: New, Existing
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Depending on the choice, some words change on other pages. I.e., "How many processors do you want" versus "How many processors do you have"
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
When the panel first loads, it checks to see whether the applet has been loaded. If not, it loads it. If the applet is loaded, it checks for changes to the default values and selects the appropriate choices.

Some values are initialized to 0 or "" (blank) when the page is loaded.

The selected values are stored in the applet.

Back goes to Welcome panel.

If 620 is selected, Next is the Divide interactive workload panel. Otherwise, Next is the Number of partitions panel.

  1. Panel: Select processors

Figure 3: LPAR Planning Advisor - Select processors Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties

Radio Button Group 1:

Description: User must select the number of processors
Field type: Radio Buttons
Possible values: 2, 4, 8, 12, 24 (feature codes vary)
Default value: 2
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: The actual values depend on the system limits.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Number of partitions.

Next is as follows:
Server Number of Partitions Next
640, 650, Sxx, Sxx ISV = total processors Divide interactive workload
< total processors Divide processors
7xx, 8xx = total processors Select interactive feature
< total processors Divide processors

The number of total processors is stored in the applet. The feature number is stored in the applet.

If the number of processors is 2, the advisor sets up to have 2 partitions with 1 processor in each. If the system is not 7xx or 8xx, the interactive feature and interactive workload are stored in the applet.

  1. Panel: Number of partitions

Figure 4: LPAR Planning Advisor - Number of partitions Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
List box 1:

Description: User must select the number of partitions
Field type: List box
Possible values: 2 through
32
Default value: 2
Formatting and length restrictions: 3 vertical spaces long
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Actual displayed number depends on the number of processors selected.

DBCS considerations: N/A
Other unique characteristics: Only the correct choices show up in the list box.

  1. Behind the Panel
Back goes to Select server.

Next is as follows:
Server Number of Processors Next
640, 650, Sxx, Sxx ISV 2 Divide interactive workload
>2 Select processors
7xx, 8xx 2 Select interactive feature
>2 Select processors

If the number of partitions selected equals the total number of processors, the advisor sets up with the requested number of partitions each having only 1 processor.

The number of partitions is stored. Each partition is given 1 processor. The number of processors in each partition is stored.

  1. Panel: Divide processors

Figure 5: LPAR Planning Advisor - Divide processors Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Drop-down lists:

Description: User must select number of processors for each partition.
Field type: Drop-down list
Possible values: 1 through (total processors - 1
), or shared
Default value: 1
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: The sum of the drop-down lists is displayed in the Total text box.
DBCS considerations: N/A
Other unique characteristics: A drop-down list is created for every partition
, plus one for unassigned.


Total text box:

Description: Displays total number of selected processors
Field type: Text box
Possible values: Number of partitions, user-supplied.
Default value: Number of partitions
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Never.
Conditions when enabled/disabled: N/A
Relationship to other properties: Is the sum of the selected drop-down lists.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select processor.

If the system is not 7xx or 8xx, Next is Divide interactive workload. Else, Next is Select interactive feature.

If the Total does not equal the total processors, the following error message displays:

  1. Panel: Select interactive workload

Figure 6: LPAR Planning Advisor - Select interactive workload Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select an interactive feature

Field type: Radio Buttons
Possible values: Varies depending on server.
Default value: First radio button
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics:
The radio buttons are only displayed for the possible interactive features.

  1. Behind the Panel
Back is as follows:
Number of processors Back Panel
number partitions != total processors Divide processors
number partitions = total processors Select processors
number processors = 2 Number of partitions

Next is Divide interactive workload.

The advisor stores the selected total CPW and the interactive feature code.

  1. Panel: Divide interactive workload

Figure 5: LPAR Planning Advisor - Divide interactive workload Panel

  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
Update Total Calculates and displays the total percentage.
  1. Properties
Update Total button:
Description: Calculates the total based on user supplied values.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Displays the total in the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Partition text boxes:

Description: Percentage of total CPW.
Field type: Text boxes
Possible values: 0 through 99.
Default value: Based on number of processors selected for that partition.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: These text boxes automatically total into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A


Unassigned text box:

Description: Percentage of total CPW.
Field type: Text box
Possible values: 0 through 100.
Default value: Based on what is left over from other partitions. Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box automatically totals into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Total text box:

Description: Total assigned percentage
Field type: Text box
Possible values: 0 through 100.
Default value: 100
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box is the total of the Partition text boxes
and the Unassigned text box.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back is as follows:
Server Number of processors Back Panel
7xx, 8xx N/A Select interactive workload
620 N/A Select server
All others number partitions != total processors Divide processors
number partitions = total processors Select processors
number processors = 2 Number of partitions

Next is Divide memory.

The advisor calculates the percentage for each partition based on the server and the number of processors in the partition. The advisor will use the median value, but the user can enter any value within the allowed range.

The advisor will not let the user go to the next panel unless the Total equals 100%. If the Total is less than 100%, the following message displays:


If the Total is greater than 100%, the following message displays:


The advisor will only accept valid numbers between 1 and 99. It will only allow whole numbers between this range (no decimal places).

  1. Panel: Divide memory

Figure 86: LPAR Planning Advisor - Divide memory Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Update Total button:
Description: Calculates the total based on user supplied values.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Displays the total in the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Partition text boxes:

Description: Total memory for the partition in MB.
Field type: Text boxes
Possible values: 0 through system maximum.
Default value: 256 for the primary (partition 0), 64 for all other partitions.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: These text boxes automatically total into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Unassigned text box:

Description: Potential unassigned memory.
Field type: Text box
Possible values: 0 through system maximum minus partitions.
Default value: Based on what is left over from other partitions. Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box automatically totals into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Total text box:

Description: Total assigned memory in MB.
Field type: Text box
Possible values: 0 through system maximum.
Default value: based on minimums (from 320 to 2240)
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box is the total of the Partition text boxes
and Unassigned text box.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Divide interactive workload.

Next goes to Divide disk storage.

The advisor will not let the user enter a value less than 256 for partition 0. If they try, the following message appears. The advisor reenters the minimum value at this point and the user can try again.


The advisor will not let the user enter a value less than 64 for all other partitions. If they try, the following message appears. The advisor reenters the minimum value at this point and the user can try Again.


If the combined Total is greater than the system maximum, the following error message appears:

The advisor stores memory information for each partition, as well as the total memory selected and system maximum.

  1. Panel: Divide disk storage

Figure 7: LPAR Planning Advisor - Divide disk storage Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Update Total button:
Description: Calculates the total based on user supplied values.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Displays the total in the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Partition text boxes:

Description: Total disk storage for the partition in GB.
Field type: Text boxes
Possible values: 4 through system maximum.
Default value: 4.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: These text boxes automatically total into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A


Unassigned text box:

Description: Left over disk storage.
Field type: Text box
Possible values: 0 through system maximum minus partitions.
Default value: Based on what is left over from other partitions. Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box automatically totals into the Total text box.
DBCS considerations: N/A
Other unique characteristics: N/A

Total text box:

Description: Total assigned disk storage in GB.
Field type: Text box
Possible values: 8 through system maximum.
Default value: based on minimums (from 8 to 128)
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: This text box is the total of the Partition text boxes
and Unassigned text box.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Divide memory.

Next goes to Select partition communications types.

If the user enters a value for a partition that is less than 4, the following message appears:

If the user enters a combined total that is greater than the system maximum, the following message appears:


The advisor stores disk storage information for each partition, as well as the total disk capacity selected and system maximum.

  1. Panel: Select partition communications types

Figure 8: LPAR Planning Advisor - Select partition communication types Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Virtual OptiConnect check boxes:

Description: User may select whether they plan to enable this.
Field type: Check Box
es
Possible values: N/A
Default value: Not selected
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Only one check box
for each partition appears.
DBCS considerations: N/A
Other unique characteristics: N/A


Select all partitions check boxes:

Description: One for virtual OptiConnect and one for HSL.
Field type: Check Boxes
Possible values: N/A
Default value: Not selected
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: When selected, all check boxes below it (within the comm type) are selected. When deselected, all check boxes below it are unchecked.
Relationship to other properties: Only one check box appears for each type.
DBCS considerations: N/A
Other unique characteristics: N/A



High-speed link check box
es:

Description: User may select whether they plan to enable this.
Field type: Check Box
es
Possible values: N/A
Default value: Not selected
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Only one check box
for each partition appears.
DBCS considerations: N/A
Other unique characteristics: This check box (and associated text) only appears for the 8xx servers.

  1. Behind the Panel
Back goes to Divide disk storage.

Next goes to Select IOP type for load source (partition 0).

Advisor stores virtual OptiConnect and HSL information for each partition.

  1. Panel: Select IOP type for load source

Figure 9: LPAR Planning Advisor - Select IOP type for load source Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether this is new or existing hardware.
Field type: Radio Buttons
Possible values: N/A
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select partition communications types if this is for partition 0, or Partition summary if any other partition.

Next goes to Select feature code for IOP for load source.

This panel starts a large loop that happens for each partition. The advisor must remember what partition this hardware is for and store the selection in the appropriate place.

  1. Panel: Select feature code for IOP for load source

Figure 10: LPAR Planning Advisor - Select feature code for IOP for load source Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Feature code drop-down list:

Description: User must select a feature code for the hardware
Field type: Drop-Down List
Possible values: N/A
Default value: The first one in the list.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only allowed feature codes will be displayed.

  1. Behind the Panel
Back goes to Select IOP type for load source.

Next goes to Select IOP type for alternate restart device, Select IOP type for console, Use electronic customer support, or Add additional hardware. Which one depends on whether the device was set to be switched for this partition from a previous partition. Partition 0 will always go to Select IOP type for alternate restart device.

The advisor stores the feature code selected.

  1. Panel: Select IOP type for alternate restart device

Figure 11: LPAR Planning Advisor - Select IOP type for alternate restart device Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether this is new or existing hardware.
Field type: Radio Buttons
Possible values: N/A
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select feature code for IOP for load source.

Next goes to Select feature code for IOP for alternate restart device.

The advisor stores the selection for this hardware in this partition.

  1. Panel: Select feature code for IOP for alternate restart device

Figure 12: LPAR Planning Advisor - Select feature code for IOP for alternate restart device Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Feature code drop-down list:

Description: User must select a feature code for the hardware
Field type: Drop-Down List
Possible values: N/A
Default value: The first one in the list.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only allowed feature codes will be displayed.

  1. Behind the Panel
Back goes to Select IOP type for alternate restart device.

Next goes to Select switchable IOP for alternate restart device.

The advisor stores the feature code selected.

  1. Panel: Select switchable IOP for alternate restart device

Figure 13: LPAR Planning Advisor - Select switchable IOP for alternate restart device Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether to allow switching or not.
Field type: Radio Buttons
Possible values: N/A
Default value: Do not allow switching
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select feature code for IOP for alternate restart device.

Next is as follows:
Switching? Previous Next Panel
Yes N/A Select switching partitions for IOP for alternate restart device
No Console no switch Select IOP type for console
Console switch, ECS no switch or still available Use electronic customer support
Console and ECS switch Add additional hardware

  1. Panel: Select switching partitions for IOP for alternate restart device

Figure 14: LPAR Planning Advisor - Select switching partitions for IOP for alternate restart device Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Partition check boxes:

Description: User can select which partitions will be using this.
Field type: Check Boxes
Possible values: N/A
Default value: None checked
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: All partitions except the current one show up.
DBCS considerations: N/A
Other unique characteristics: If the user does not select any partitions, the Advisor assumes that the device will not be switched.

  1. Behind the Panel
Back goes to Select switchable IOP for alternate restart device.

Next is as follows:
Previous Next Panel
Console no switch Select IOP type for console
Console switch, ECS no switch or still available Use electronic customer support
Console and ECS switch Add additional hardware

The advisor stores which partitions are selected to switch for this hardware. The user will not be asked about this hardware in the relevant switched partitions.

  1. Panel: Select IOP type for console

Figure 15: LPAR Planning Advisor - Select IOP type for console Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether this is new or existing hardware.
Field type: Radio Buttons
Possible values: N/A
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back is as follows:
Switching alternate restart device? Previous Next Panel
Yes Alternate restart device no switch Select switching partitions for IOP for alternate restart device
No Alternate restart device no switch Select switchable IOP for alternate restart device
Alternate restart device switch Select feature code for IOP for load source

Next goes to Select feature code for IOP for console.

The advisor stores the selection for this hardware in this partition.

  1. Panel: Select feature code for IOP for console

Figure 16: LPAR Planning Advisor - Select feature code for IOP for console Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Feature code drop-down list:

Description: User must select a feature code for the hardware
Field type: Drop-Down List
Possible values: N/A
Default value: The first one in the list.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only allowed feature codes will be displayed.

  1. Behind the Panel
Back goes to Select IOP type for console.

The advisor stores the feature code selected.

Next is as follows:
Previous Next Panel
ECS no switch, still available Use electronic customer support
ECS switch Add additional hardware

  1. Panel: Use electronic customer support

Figure 17: LPAR Planning Advisor - Use electronic customer support Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio button group 1:

Description: User must select how to implement ECS on the server if this is partition 0. Other partitions either will not have radio buttons or will select whether to have or not.
Field type: Radio Buttons
Possible values: N/A
Default value: Partition 0 only, or Yes.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: Enabled if partition 0, or selected to have more than 2.
Relationship to other properties: If the user only has two partitions, only 2 radio buttons appear.
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select feature code for IOP for console.

Next is as follows:
Partition Selection Next Panel
0 Any radio button Select IOP type for electronic customer support
1 Only 2 ECS lines Select IOP type for electronic customer support
>2 lines and part 0 not sharing Select IOP type for electronic customer support
>2 lines and part 0 sharing Add additional hardware
Others If >2 lines and 1 is available Select IOP type for electronic customer support
Others Add additional hardware


If the user only has two partitions, the following radio buttons display:

If the user selected to have more than 2 ECS, the following panel displays on subsequent partitions:


If the user selected to have 2 communication lines, the following displays for partition 1:

  1. Panel: Select IOP type for electronic customer support

Figure 20: LPAR Planning Advisor - Select IOP type for electronic customer support Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio button group 1:

Description: User must select whether this is new or existing.
Field type: Radio Buttons
Possible values: N/A
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Use electronic customer support.

Next goes to Select feature code for IOP for electronic customer support.

The advisor stores the selection for this hardware in this partition.

  1. Panel: Select feature code for IOP for electronic customer support

Figure 21: LPAR Planning Advisor - Select feature code for IOP for electronic customer support Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Feature code drop-down list:

Description: User must select a feature code for the hardware
Field type: Drop-Down List
Possible values: N/A
Default value: The first one in the list.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only allowed feature codes will be displayed.

  1. Behind the Panel
Back goes to Select IOP type for electronic customer support.

Next goes to Select switchable IOP for electronic customer support if not partition 0. If partition 0, Next goes to Add additional hardware.

The advisor stores the feature code selected.

  1. Panel: Select switchable IOP for electronic customer support

Figure 18: LPAR Planning Advisor - Select switchable IOP for electronic customer support Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether to allow switching or not.
Field type: Radio Buttons
Possible values: N/A
Default value: Do not allow switching
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A


  1. Behind the Panel
Back goes to Select feature code for IOP for electronic customer support.

Next is as follows:
Switching? Next Panel
Yes Select switching partitions for IOP for electronic customer support
No Add additional hardware
  1. Panel: Select switching partitions for IOP for electronic customer support

Figure 19: LPAR Planning Advisor - Select switching partitions for IOP for electronic customer support Panel
  1. Push buttons
Push button Results
< Back Displays the previous advisor panel.
Next > Displays the next advisor panel.
  1. Properties
Partition check boxes:

Description: User can select which partitions will be using this.
Field type: Check Boxes
Possible values: N/A
Default value: None checked
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: If the user does not select any partitions, the Advisor assumes that the device will not be switched.

  1. Behind the Panel
Back goes to Select switchable IOP for electronic customer support.

Next goes to Add additional hardware.

The advisor stores which partitions are selected to switch for this hardware. The user will not be asked about this hardware in the relevant switched partitions.

  1. Panel: Add additional hardware

Figure 20: LPAR Planning Advisor - Add additional hardware Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.

  1. Properties
Radio Button Group 1:

Description: User must select whether to add more hardware.
Field type: Radio button
Possible values: N/A
Default value: No
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Changes to default to Yes if add before in this partition.

  1. Behind the Panel
Back is as follows:
Switching? Previous Next Panel
Add hardware N/A Select switching partitions for IOP for ------- (additional hardware name)
Add hardware no N/A Select switchable IOP for ------- (additional hardware name)
ECS ECS no switch Select switching partitions for IOP for electronic customer support
ECS no Select switchable IOP for electronic customer support
Console no ECS switch
Console no switch
Select feature code for IOP for console

If Yes is selected, Next is Select hardware type for additional hardware. Otherwise, Next is Select type of disk protection.

The advisor stores the number of times hardware is added. This starts another small loop within the big loop for each partition. This loops infinitely depending on the user.

  1. Panel: Select hardware type for additional hardware

Figure 21: LPAR Planning Advisor - Select hardware type for additional hardware Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Additional hardware drop-down list:

Description: User must select the type of additional hardware.
Field type: Drop-down List
Possible values: Netfinity Server (
INS), IPCS/100 Mbps Ethernet, 100 Mbps Ethernet, 10 Mbps Ethernet, 16 Mbps Token Ring, 155 Mbps ATM, Frame Relay, Communications (Controller), Communications (V.24), Communications (X.21), Communications (ATM), Communications (FDDI), Disk Controller, Storage (tape device), Storage (optical device), Workstation (twinaxial), SPD OptiConnect, Other
Default value: Netfinity Server (IPCS)
Formatting and length restrictions: N/A
Required or optional: Required.
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: The selected hardware name shows up on the subsequent add hardware pages.
DBCS considerations: N/A
Other unique characteristics: N/A

Radio Button Group 1:

Description: User must select whether this is new or existing hardware.
Field type: Radio Buttons
Possible values: N/A
Default value: New
Formatting and length restrictions: N/A
Required or optional: Required.
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Add additional hardware. The number of added hardware is decreased by one.

If Other is selected, Next is Enter name for additional hardware. Otherwise, Next is Select feature code for IOP for --- --- -- (hardware name).

The advisor stores the selections.

  1. Panel: Enter name for additional hardware

Figure 22: LPAR Planning Advisor - Enter name for additional hardware Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Name text box:

Description: User must supply a name for this "Other" hardware.
Field type: Text Box
Possible values: User supplied.
Default value: Other
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: Always
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select hardware type for additional hardware.

Next goes to Select feature code for IOP for -- - --- - (hardware name).

The advisor will not let the user go on until a name of at least one character is entered.

The advisor stores the name associated with this additional hardware.

  1. Panel: Select feature code for IOP for -- - --- - (hardware name)

Figure 23: LPAR Planning Advisor - Select feature code for IOP for -- - --- - (hardware name) Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Feature code drop-down list:

Description: User must select a feature code for the hardware
Field type: Drop-Down List
Possible values: N/A
Default value: The first one in the list.
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only allowed feature codes will be displayed.

  1. Behind the Panel
If the user supplied a name, Back goes to Enter name for additional hardware. Otherwise, Back goes to Select hardware type for additional hardware.

Next goes to Select quantity for -- --- ---- (hardware name).

The advisor stores the selected feature code for this hardware.

  1. Panel: Select quantity for -- --- ---- (hardware name)

Figure 24: LPAR Planning Advisor - Select quantity for -- --- ---- (hardware name) Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Quantity text box:

Description: User must supply a whole number quantity.
Field type: Text Box
Possible values: N/A
Default value: 1
Formatting and length restrictions: Only allow up to 9999. Not less than 1.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select feature code for IOP for -- --- ---- (hardware name).

Next goes to Select switchable IOP for -- --- ---- (hardware name).

If an invalid quantity is entered, the following displays:

  1. Panel: Select switchable IOP for -- --- ---- (hardware name)

Figure 29: LPAR Planning Advisor - Select switchable IOP for -- --- ---- (hardware name) Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether to allow switching or not.
Field type: Radio Buttons
Possible values: N/A
Default value: Do not allow switching
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select quantity for -- --- ---- (hardware name).

If Yes is selected, Next goes to Select switching partitions for -- --- ---- (hardware name). Otherwise, Next goes to Add additional hardware.

  1. Panel: Select switching partitions for IOP for -- --- ---- (hardware name)

Figure 30: LPAR Planning Advisor - Select switching partitions for IOP for -- --- ---- (hardware name) Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Partition check boxes:

Description: User can select which partitions will be using this.
Field type: Check Boxes
Possible values: N/A
Default value: None checked
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: If the user does not select any partitions, the Advisor assumes that the device will not be switched.

  1. Behind the Panel
Back goes to Select switchable IOP for -- --- ---- (hardware name).

Next goes to Add additional hardware.

The advisor stores which partitions are selected to switch for this hardware. The user will not be asked about this hardware in the relevant switched partitions.

  1. Panel: Select type of disk protection

Figure 25: LPAR Planning Advisor - Select type of disk protection Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select one of the types of protection.
Field type: Radio Buttons
Possible values: N/A
Default value: Parity Protection
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Add additional hardware.

Next goes to Select disk unit type.

The advisor stores the selected radio button and the selected type of disk protection for this partition.

  1. Panel: Select disk unit type

Figure 32: LPAR Planning Advisor - Select disk unit type Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select whether to assign specific disk unit types to this partition.
Field type: Radio Buttons
Possible values: N/A
Default value: Yes
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select type of disk protection

If Yes is selected, Next goes to Assign disk unit types. Otherwise, Next goes to Partition summary.

The advisor stores the selected value.

  1. Panel: Assign disk unit types

Figure 26: LPAR Planning Advisor - Assign disk unit types Panel

  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Update Totals button:
Description: Calculates the total based on the subtotals.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: Updates the Total text box with the combined total.
DBCS considerations: N/A
Other unique characteristics: N/A

Quantity text boxes:

Description: User may enter a quantity for each type of disk unit.
Field type: Text Boxes
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: Always

Conditions when enabled/disabled: N/A
Relationship to other properties: The quantity times the disk type equal the Subtotal.
DBCS considerations: N/A
Other unique characteristics: Only whole numbers allowed.
Automatically updates subtotal value.

Disk Unit Subtotal text boxes:

Description: Provides the subtotal based on the quantity entered.
Field type: Text Boxes
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: Contains the subtotal for the disk unit type.
DBCS considerations: N/A
Other unique characteristics: If user tries to enter anything, it is ignored and recalculated. Automatically updates Total value.

Total text box:

Description: Provides the total based on the sum of the subtotals.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: Contains the total of the subtotals.
DBCS considerations: N/A
Other unique characteristics: If user tries to enter anything, it is ignored and recalculated.

  1. Behind the Panel
Back goes to Select disk unit type.

Next goes to Partition summary.

If the total is different than what the user supplied in Divide disk storage, the following appears:

If the user clicks OK, the total is adjusted as indicated. Otherwise, the user can try again.

If the total is greater than the system maximum, the following appears:


If the total in this partition plus the total in other partitions exceeds the system maximum, the following displays:


The advisor stores the total and the quantity and subtotal for each disk unit that has at least 1 quantity.

If the user does not enter any quantities, or they are all 0, the Advisor assumes that they want the TSC to decide.

  1. Panel: Partition summary

Figure 27: LPAR Planning Advisor - Partition summary Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Save button:

Description: Saves the user's progress so far in a cookie.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: Stores the values from the applet into a cookie on the user's system.
DBCS considerations: N/A
Other unique characteristics: The cookie can be read by the advisor to restore information.

  1. Behind the Panel
If the user specified quantities of disk units, Back goes to Assign disk unit types. Otherwise, Back goes to Select disk unit type.

This is the last panel in the large loop for each partition. If the user must enter information for the next partition, Next goes to Select IOP type for load source. Otherwise, Next goes to Provide additional information.

The advisor retrieves all stored values for this partition and displays them in the tables.

  1. Panel: Provide additional information

Figure 28: LPAR Planning Advisor - Provide additional information Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Additional information text box:

Description: User may supply additional information.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: 8 rows and 50 characters wide showing. But, user may enter more. Wraps at end of 50 characters.
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Partition summary.

Next goes to Enter contact information.

The advisor stores any entered information.

  1. Panel: Enter contact information

Figure 29: LPAR Planning Advisor - Enter contact information Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
First name text box:

Description: User's first name.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: Must be at least 1 character.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Last name text box:

Description: User's last name.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: Must be at least 1 character.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Company text box:

Description: User's company name.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Customer number text box:

Description: User's customer number.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Phone number text box:

Description: User's phone number.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: Must be at least 10 characters long.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Business street address text box:

Description: User's address.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Business city text box:

Description: User's city of business.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Business state/province text box:

Description: User's state or province of business.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Business zip code text box:

Description: User's zip code for business.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

Business country text box:

Description: User's country of business.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Optional
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

E-mail address text box:

Description: User's e-mail address.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: Must be at least 5 characters long. Must include the "@" sign.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Provide additional information.

Next goes to Results.

The advisor stores all entered values.

If the user does not enter their first name, the following appears:


If the user does not enter their last name, the following appears:


If the user does not enter their phone number, the following appears:


If the user does not enter their e-mail address, the following appears:


If the user does not enter a valid phone number of at least 10 characters, the following appears:


If the user does not enter a valid e-mail address of at least 5 characters and an "@" sign, the following appears:

  1. Panel: Results

Figure 30: LPAR Planning Advisor - Results Panel
  1. Push buttons
Push button Results
Start Over Returns to beginning of advisor. Confirmation prompt pops up to confirm this action.
<< Back Displays the previous advisor panel.
Print Prints the page of information for the user.
  1. Properties
Save button:

Description: Saves the user's progress so far in a cookie.
Field type: Button
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: N/A
Conditions when editable/not editable: Never
Conditions when enabled/disabled: N/A
Relationship to other properties: Stores the values from the applet into a cookie on the user's system. User will have option to save the file under a different name for later retrieval by the Create Partition Wizard.
DBCS considerations: N/A
Other unique characteristics: The cookie can be read by the advisor to restore information.

  1. Behind the Panel
Back goes to Enter contact information.

Start Over displays the following prompt:

If the user clicks OK, the Select server panel displays and all entered information is deleted from the advisor.. Otherwise, the user is returned to the Results panel.

The advisor retrieves all stored values for all partitions and displays them in the tables.

  1. Advisor: LPAR Troubleshooting Advisor

    1. Description
Many customers expressed a need for better troubleshooting information. The Troubleshooting Advisor will help users to quickly and accurately find the source of their problem and the steps that are necessary to correct the problem. This will also help customers so that they do not have to scan through six or seven pages of SRCs and error messages (as was the case in V4R4), but instead allow them to enter their error or SRC and receive a "customized" solution that is only one to two pages long.
  1. Flow
Figure B: LPAR Troubleshooting Advisor Flow
  1. Panel: Welcome

Figure 38: LPAR Troubleshooting Advisor - Welcome Panel
  1. Push buttons
Push button Results
Start Displays the next advisor panel.
  1. Properties
N/A

  1. Behind the Panel
This panel is actually part of the Troubleshooting articles. Since content will be sourced in HTML for V5R1, a Start button can be included on the page instead of the text link at the bottom.

The design of the frames around this content will be based on the V5R1 Information Center design.

Next goes to Select a search method.

  1. Panel: Select a search method

Figure 31: LPAR Troubleshooting Advisor - Select a search method Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio Button Group 1:

Description: User must select a type of search.
Field type: Radio Buttons
Possible values: N/A
Default value: Enter SRC
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Welcome.

Next is as follows:
Selected Radio Button Next Panel
Enter SRC Enter the SRC
Browse SRCs Select an SRC
Enter error message Enter the error message
Browse error messages Select an error message

The advisor stores the selected radio button.

  1. Panel: Enter the SRC

Figure 40: LPAR Troubleshooting Advisor - Enter the SRC Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
SRC text box:

Description: User must supply an SRC.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: Must be between 8 and 12 characters long.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select a search method.

If the SRC has a solution, Next goes to Results (SRC). If there is another question, Next goes to SRC question.

The advisor stores the SRC entered.

If the user does not enter an SRC, the following appears:


If no matching SRC exists, the following displays:

If the value entered is not the correct length or format, the following displays:

  1. Panel: SRC question

Figure 41: LPAR Troubleshooting Advisor - SRC question Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Radio Button Group 1:

Description: The user must answer the question.
Field type: Radio Buttons
Possible values: N/A
Default value: Yes
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Enter the SRC.

Next goes to Results (SRC).

The advisor decides which SRC question to display based on the SRC entered. The advisor stores the selected answer and determines the result.

  1. Panel: Select an SRC

Figure 32: LPAR Troubleshooting Advisor - Select an SRC Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
SRC list box:

Description: User must select an SRC from the list.
Field type: List Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics:
"Not Listed" option takes usre to results page with link to other documentation.

  1. Behind the Panel
Back goes to Select a search method.

Next goes to Results (SRC) or SRC question.

If the user does not select an SRC, the following appears:


The advisor stores the selected index and the SRC. The advisor determines whether another question or a Result is needed.

  1. Panel: Results (SRC)

Figure 43: LPAR Troubleshooting Advisor - Results (SRC) Panel
  1. Push buttons
Push button Results
Start Over Displays the first advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
N/A

  1. Behind the Panel
Back takes user to either SRC question, Select an SRC, or Enter an SRC (depending on what the last page was).

Start Over takes the user to Select a search method. All values stored in the advisor are deleted.

  1. Panel: Enter the error message

Figure 33: LPAR Troubleshooting Advisor - Enter the error message Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Error message text box:

Description: User must supply at least the first word of the error message.
Field type: Text Box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: 4 rows long and 40 characters wide. Wraps at the 40th character.
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select a search method.

Next goes to Select error message if more than one possibility. Otherwise, Next goes to Results (Error Message).

The advisor stores the entered error message.

If the user does not enter anything, the following appears:


If the user enters something that has no match, the following appears:

  1. Panel: Select error message

Figure 34: LPAR Troubleshooting Advisor - Select error message Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Error Message list box:

Description: User must select the desired error message.
Field type: List Box
Possible values: N/A
Default value: First in list (alphabetically)
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: Only valid selections for the entered error message are shown.

  1. Behind the Panel
Back goes to Enter the error message.

Next goes to Results (Error Message).

The advisor stores the selected error message and the selected index.

  1. Panel: Select an error message

Figure 35: LPAR Troubleshooting Advisor - Select an error message Panel
  1. Push buttons
Push button Results
Next >> Displays the next advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
Error message List box:

Description: User must select an error message from the list.
Field type: List box
Possible values: N/A
Default value: N/A
Formatting and length restrictions: N/A
Required or optional: Required
Conditions when editable/not editable: N/A
Conditions when enabled/disabled: N/A
Relationship to other properties: N/A
DBCS considerations: N/A
Other unique characteristics: N/A

  1. Behind the Panel
Back goes to Select a search method.

Next goes to Results (Error Message).

The advisor stores the selected index and error message.

If the user does not select an error message, the following appears:

  1. Panel: Results (Error Message)

Figure 47: LPAR Troubleshooting Advisor - Results (Error Message) Panel
  1. Push buttons
Push button Results
Start Over Displays the first advisor panel.
<< Back Displays the previous advisor panel.
  1. Properties
N/A
  1. Behind the Panel
Back goes to Select an error message, Select error message, or Enter the error message, depending on where the user was previously.

Start Over takes the user to Select a search method. All stored information is erased.

The advisor determines what solution to display based on the error message.

  1. Help Objects

N/A
  1. Book Objects

N/A
  1. Considerations

    1. NLS Considerations

All information may have EEA (Easy English Analyzer) run against it if EEA is available for HTML-authored information. All HTML-authored information must be run against CHKPII to ensure the quality of the HTML being sent to the Translation Centers.

Only the answers for the SRC Troubleshooting advisor need to be translated since the SRCs are the same across all languages. However, the OS/400 error messages need to be translated exactly as they appear for the user. The readme file will contain instructions to this effect.

Special non-translating tags will be used in the advisors to bring the word count down to normal levels.

  1. Compatibility Considerations

The logical partition advisors will follow the same format designated for all advisors, as detailed by Kris Henke and Chris Seyer.

The Appendix information must conform to the AS/400 web site look and feel (called Bullseye). Because of this, the information must be maintained in HTML and use the Bullseye template.

Because we will not be documenting new or changed DST/SST function, the articles that describe them must contain a disclaimer at the beginning.

  1. Integration/Build Considerations

Since the advisors are dynamic, they are not part of the PDF built from the topic's articles. The information that comes out of the Advisors must be maintained as articles so that users who do not use the advisors or who print out the PDF document can find the information.

Only the first page (the welcome page) of the advisors needs to be indexed for the search function. No other advisor pages should be included in the search, since the user must progress from the start of the advisor to the end.

  1. Distribution

N/A
  1. Design Alternatives

N/A
  1. Dependencies

None at this time.
  1. Restrictions and Limitations

N/A
  1. Migration and Coexistence Considerations

V5R1 Information supersedes V4R5 information, except for DST/SST functions.
  1. UT Testing Considerations

Defined by Mike Kelly in Lotus Notes Database UT_Testing on d27dbl02.
  1. Equipment Needed

Not yet determined. See Mike Kelly's test plan.
  1. Test Subjects Needed

Not yet determined. See Mike Kelly's test plan.
  1. New Terms and Concepts

Term Definition
advisor

An interactive program within electronic documentation that provides recommendations to the user. Advisors are similar to wizards except they do not actually perform the task. For example, the Security advisor determines the security value settings that best suit the user needs based on user-provided input.
article A small, self-contained piece of information that describes a particular information type such as a procedure, concept, example, or reference information. (Use only internally; use page externally.)
category The title of a group of topics that fit within a functional area in the Information Center.
concept An information type that describes an idea; for example, what it is or how it works.
context An information type that is available as Help directly within the interface. For example, Operations Navigator provides contextual help for most fields in a dialog.
dummy book A one-page, online book in the Online Library that points to the Information Center for information about a topic. This is generally used when the hardcopy documentation has moved to the Information Center.
example An information type that illustrates a procedure, concept, program, snippet, or user scenario.
information type A category of information that matches the users' needs: procedure, concept, reference, context. AS/400 information also includes information types of example, details, and tips.
keyword A word that is representative of the content in articles.
package A grouping of articles for administrative purposes such as DCRs, PTRs, translation, tracking, and so forth.
page Synonymous with article. Use page externally, not article.
predefined path Information designed to step the user through a series of tasks that, when completed successfully, will accomplish a user's goal.
procedure An information type that describes how to perform a task. It is generally written as a set of steps.
reference An information type that documents programming constructs or facts about a product; for example, what programming constructs do or values that can be specified.
subtopic A functional group of articles that are a subset of a topic. This term is only meaningful when mentioned within the context of the parent topic. The use of subtopic is preferred to section.
topic A functional group of articles. It can be used to describe a grouping at any level within the hierarchy. The use of topic is preferred to section.
user goal The user's ultimate reason for using AS/400, that is, a specific high-level objective.
wizard An interactive program that performs a task for the user. Wizards are similar to advisors except wizards actually perform the task. For example, the TCP/IP Interface Wizard configures TCP/IP on AS/400 for the first time.
  1. Reference Materials

    1. UT Strategy

Available on the Intranet at:

http://w3.rchland.ibm.com/projects/ID/strategy/strat.htm

  1. Information Center CAI

Available from Georgia Toogood in Rochester.
  1. Other Topic CAI and I0 Documents

Documents for other topic areas can be found in the UT Design Documents Lotus Notes database in the 'u_dir' on the d27dbl02/27/A/IBM server.

LPAR SAI/CAI for development can be found off the LPAR web page at http://w3.rchland.ibm.com/~lpar

  1. Information Plan

Available from Tom Parry in Rochester.
  1. Programming SAI/CAI/I0 Documents

Document Product/Component Owner Available From
GUI LPAR Management SAI/CAI GUIX Jeff Scheel Jeff Scheel
Logical Partitioning (LPAR) I0 Document GUIX Dennis Schmidt Dennis Schmidt
The AS/400 V5R1 Logical Partitioning Stage II Version 1.0 Combined SAI/CAI SLIC Mark Manges Mark Manges

  1. I0 Review Issues/Resolutions

Type

(Issue/Comment)

Originator Owner Due
Date
Resolution
Issue--Need shared processor pool article M Manges G Winn
S Choy
  One will be added to the Learning and one to the Planning topics, as well as support in the advisor (Note: the graphic in the I0 does not show this. We are trying to determine how it will work best)
Issue--EEA optional for HTML source C Seyer G Winn   Changed wording to indicate that EEA may be optional for all HTML-sourced info for V5R1
Issue--Reword section 3.3 of the Doc I0 for clarity (to make it clearer that advisor panels are not included in the PDF) J Curry G Winn   Reworded as indicated
Issue--No more focus group needed for LPAR. Use iterative design instead E Lueke
S Benysh
G Winn   Changed point to indicate that we will continue to meet with customers to verify information design and structure, as well as advisor flow and ease of use
Issue--Include info about how the Planning advisor fits into the whole process ?? G Winn   This section has been updated and made clearer. The advisor helps the user complete the work sheets. It fits in at the same place as the planning articles. Eventually, it will take the place of these articles when it becomes "smart" enough to do validation
Issue--Switch Number of processors and Number of partitions panels S Benysh G Winn   Switched
Issue--Do not allow switching for console and load source M Manges G Winn   Functionality removed from advisor
Issue--Redesign welcome page Many C Seyer
G Winn
  Some rework done. Chris Seyer will continue to work on this for all advisors. For the Planning advisor, sentences have been made clearer and most of the steps in the original have been removed because they are no longer required steps
Issue--Being able to save progress (also part of "this advisor is too long") Many G Winn
C Seyer
  We can save progress with cookies. We will have prototypes within the next couple of months. Will include graphics that let the user see visually where they are in the process. Also, will include buttons on each page for "Progress so far" (Note: this button has not been added to the graphics in the I0). We will continue to work with customers to see how we can make the advisor more usable
Issue--No more TSC for LPAR T Gabriel G Winn   The TSC is training Tech Line, and will give it all to them by (hopefully) V5R1. The TSC still wants their name in the documentation, they just want it behind Tech Line and business partners
Issue--Assign disk unit types seems out of place S Benysh G Winn   We are working with customers to see how this should be changed, if at all. So far, it looks like we will move this panel after the divide disk storage panel, and have it do a short loop for each partition (Note: This has not been changed in the I0 because it is still under investigation)
Comment--Grammatical stuff Many G Winn   Changes have been made where appropriate
Comment--New definitions to include ?? G Winn   Included
Comment--Explain new and existing better S Benysh G Winn   Changed to include "to be ordered" information for new
Comment--Make fig 3 and 6 look the same (using columns) ?? G Winn   Done
Comment--Stores where? F Bonner G Winn   Added wording in first couple instances to indicate that it stores everything in the advisor
Comment--Allow "not here" item for troubleshooting browse ?? G Winn   Added item to list. Will take user to results page and link to other documentation
Comment--Use list box on Select error message ?? G Winn   Changed to list box
Comment--Be more specific about time to complete advisor K Bies G Winn   Made wording clearer
Comment--Allow select individual partitions for virtual OptiConnect. Use "select all" check box Many G Winn   Did as suggested
  1. Appendix A: LPAR Documentation Focus Group Summary

The following items were derived by analyzing specific requests from the LPAR Focus Group Collation of Customer Wants and Needs as gathered by the UCD Team. Only items relating to user documentation were used. These items are ranked from most requested to least requested with the number of responses noted for each item.

Rank Request Responses
1 Include an overview/background, examples, case studies, FAQs, and troubleshooting

Recommendations:

  • Help a new user create partitions using the documentation
  • Create FAQs, Troubleshooting, case studies, sample configs, etc.

10
2 Documentation on understanding hardware

Recommendations:

  • Shouldn't have to use support line

2
3 Clarity of documentation

Recommendations:

  • All steps and possibilities are covered in detail
  • Make it easier to understand so it cuts down on the amount of time required

4
4 Easy to navigate

Recommendations:

  • Links need to say where they go
  • When F1 help is available

3
5 Configurator local to the box

Recommendations:

  • GUI tool that is marketed by IBM
  • Downloadable from IBM web site

2
6 Multiple access to documentation

Recommendations:

  • Make planning guide part of InfoCenter
  • Either a hardcopy book, PDF, or on soft copy CD

2