iseries Getting started with iseries

iseries Getting started with iseries

iseries Getting started with iseries

Copyright International Business Machines Corporation 1998, 2001. All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents Chapter 1. Getting started with iseries 400...................... 1 Completing EZ-Setup: do these tasks first........................ 1 Chapter 2. Configuring your LAN console....................... 3 Chapter 3. Backing up your system......................... 5 Chapter 4. Microsoft s Data Access Components (MDAC)................. 7 How MDAC works on your system.......................... 7 How to get MDAC................................. 7 Saing changes after installing software........................ 7 Adding electronic customer support to your system.................... 7 Chapter 5. Making your system operational...................... 9 Before you start................................. 9 Turning on the system............................... 9 Powering on the system............................. 9 Performing an Initial Program Load (IPL)....................... 10 Configuring your LAN console............................ 10 System interfaces................................ 10 Operations Naigator.............................. 10 Command line interface............................. 11 Installing Management Central........................... 12 Backing up your system.............................. 12 Initializing the tape for a system backup....................... 12 Performing a system backup........................... 13 Installing software................................ 14 Saing changes after installing software........................ 15 Adding electronic customer support to your system.................... 15 Configuring Uniersal Connection......................... 16 Configure serice proider information........................ 18 Testing your connection to electronic customer support................. 18 Configuring SNA connection to electronic customer support................ 18 Chapter 6. System configuration concepts...................... 21 Chapter 7. System operations concepts....................... 23 Messages................................... 23 Jobs..................................... 24 Objects.................................... 24 Logs and journals................................ 24 Logs.................................... 24 Journals................................... 25 System authorities................................ 25 Files and file systems............................... 26 Control language commands............................ 26 Command syntax............................... 26 Entering commands.............................. 27 User profiles.................................. 28 Printing on iseries................................ 28 Fixes..................................... 29 Installed and permanently installed fixes....................... 29 Aailable and delayed fixes............................ 29 Copyright IBM Corp. 1998, 2001 iii

Chapter 8. Managing system operations....................... 31 Controlling jobs................................. 31 To get information about a job on your system:.................... 31 Handling messages................................ 32 To send a message............................... 32 To delete a message.............................. 32 To get more information about a message...................... 32 To reply to a message.............................. 32 Your system status................................ 33 User profile tasks................................ 33 Perform common user profile tasks......................... 34 Managing user profiles............................. 35 Adding and remoing users from groups....................... 36 Entering personal information into a user profile.................... 37 Setting security parameters for users........................ 37 Job-related information for users.......................... 38 Setting system security.............................. 38 System security classes............................. 39 Setting security policies............................. 39 Setting up auditing............................... 40 Defining authorization lists............................ 41 Using the security wizard............................ 42 Starting and stopping the iseries........................... 42 Setting up an automatic power on and off schedule................... 43 Starting the System............................... 44 Starting the iseries: signing on.......................... 46 Starting a remote system............................ 46 Changing your system IPL from the system control panel................. 47 System Values That Control IPL.......................... 47 Changing the system during IPL (attended IPL).................... 50 Tips for Improing IPL Performance......................... 53 Cleaning up your system to improe performance................... 57 Changing the system password.......................... 61 Working with subsystems............................ 62 Stopping the system.............................. 63 Powering off the system immediately........................ 64 Using the power pushbutton........................... 64 System reference codes and primary partitions.................... 65 System reference codes and secondary partitions................... 67 What causes an abnormal IPL?.......................... 69 Managing fixes................................. 69 Common fix management tasks.......................... 69 Adanced fix management tasks.......................... 70 Ordering indiidual fixes and coer letters...................... 70 Sample coer letter and description of fields..................... 73 Ordering fixes................................. 76 Using the SNDPTFORD command to order fixes.................... 78 Preparing to install fixes............................. 79 Choosing a storage area before applying a fix..................... 79 Installing a cumulatie fix pack.......................... 80 Installing licensed internal code fixes........................ 82 Installing licensed program (LP) fixes........................ 83 Verifying the fix installation............................ 84 Displaying fix status.............................. 85 Displaying fix information............................. 85 Distributing fixes to remote systems......................... 86 i iseries: Getting started with iseries

Remoing fixes................................ 92 Loading fixes................................. 94 Applying fixes: adanced procedure......................... 95 Working with deices............................... 98 System requirements for deice configurations..................... 98 Working with printer output............................. 99 ASCII LAN printing............................... 99 IPDS LAN printing............................... 100 Twinax printing................................ 100 Using Line Printer Requester/Line Printer Daemon (LPR/LPD) printing............ 100 Setting up a remote printer........................... 101 Setting up a remote printer from the command line.................. 101 Preparing to print............................... 102 Starting printer output............................. 104 Changing a format to ASCII before printing..................... 104 How spooled files are named.......................... 105 Ownership of spooled files............................ 106 Deleting printers that are no longer needed on the system................ 106 Setting up Telnet printer pass-through....................... 106 Setting the number of irtual deices........................ 107 Virtual controllers and deices created by the system.................. 108 Actiating the QSYSWRK subsystem........................ 108 Printer security considerations.......................... 109 Using remoeable media............................. 109 Using tapes and tape units........................... 110 General Tape Usage Information......................... 111 Storage Deice Ready Conditions......................... 114 Using CD-ROM Storage............................ 116 Using Optical Media Libraries.......................... 118 Tape Drie Enironment and Use......................... 118 Using 1/2-Inch and Magstar MP Tape Cartridges................... 119 Using 1/4-Inch Cartridges............................ 120 Using 8-Millimeter Tape Cartridges......................... 133 Using 1/2-Inch tape reels............................ 135 Chapter 9. Handling system problems and getting help through electronic customer support 141 Troubleshooting printer problems.......................... 141 Soling problems with sending jobs......................... 141 LPR command considerations.......................... 141 Common error messages............................ 142 Materials required for reporting LPR problems.................... 142 Soling problems with receiing jobs......................... 142 Materials Required for Reporting LPD Problems.................... 143 Finding a job that did not print........................... 144 On the serer................................ 144 On the client................................. 144 Resoling problems with the Uniersal Connection wizard................. 144 AT&T customers:................................ 146 Contacting electronic customer support........................ 146 Wait! Before You Access the Internet.......................... 146 Viewing system configuration lists.......................... 146 Hardware.................................. 147 Software.................................. 147 Troubleshooting your system............................ 147 Before you call................................ 147 How to use this flowchart............................ 148 Contents

Begin troubleshooting now............................ 148 Troubleshooting your system: Step 2........................ 148 Troubleshooting your system: Step 3........................ 148 Troubleshooting your system: Step 4........................ 148 Troubleshooting your system: Step 5........................ 148 Troubleshooting your system: Step 6........................ 148 Troubleshooting your system: Step 7........................ 149 Troubleshooting your system: Step 8........................ 149 Troubleshooting your system: Step 9........................ 149 Troubleshooting your system: Step 10....................... 149 Troubleshooting your system: Step 11....................... 149 Troubleshooting your system: Step 12....................... 149 Troubleshooting your system: Step 13....................... 149 Troubleshooting your system: Step 14....................... 150 Troubleshooting your system: Step 15....................... 150 Troubleshooting your system: Step 16....................... 150 Troubleshooting your system: Step 17....................... 150 Troubleshooting your system: Step 18....................... 151 Troubleshooting your system: Step 19....................... 151 Analyzing problems with a symptom......................... 152 Procedure 1: Recoering from system power problem................. 153 Procedure 2: Recoering when attention light is on or the System Reference Code (SRC) is displayed................................. 153 Procedure 2A: Recoering when Operations Console Remote Control Panel feature is not working properly.................................. 156 Procedure 3: Recoering when control panel pushbuttons or lights are not working properly... 156 Procedure 4: Recoering from IPL or system failure.................. 156 Procedure 5: Recoering from workstation failure................... 157 Procedure 6: Recoering from tape or optical deice problem............... 158 Procedure 7: Recoering from disk or diskette drie problem............... 158 Procedure 8: Recoering from communication problem................. 158 Procedure 9: Recoering from system hang or loop condition............... 158 Procedure 10: Recoering from intermittent problem.................. 159 Procedure 11: Recoering when system console did not ary on............. 159 Problem summary forms............................. 160 Problem summary form for systems with a single partition (except Model 270 and 8xx)..... 160 Problem summary form for systems with multiple partitions (except Model 8xx)........ 161 Problem summary form for Model 270 and 8xx systems with a single partition........ 162 Problem summary form for Model 8xx systems with multiple partitions........... 163 Accessing panel functions on a secondary partition.................. 164 Analyzing a new problem............................ 165 Reporting hardware and software problems..................... 165 Replacing Battery Power Unit on Models 5xx, and Tower FC507x and FC508X........ 170 Performing a main storage dump......................... 171 Determining the primary or alternate consoles.................... 174 Getting help with system operation problems..................... 175 i iseries: Getting started with iseries

Chapter 1. Getting started with iseries 400 Whether you are new to the iseries or an experienced professional, this topic is a useful starting point for all kinds of information for handling simple and complex tasks on your system. Use this information to get to know your system how it works, how the pieces interact, and how you can customize it to better meet your needs. Learn the terminology, and see how this platform is different from others you may hae worked on. Explore system concepts and learn to manage the day-to-day business of your system. Identify some of your common administratie tasks, and how you can accomplish them. If you run into problems, use the troubleshooting guide to get back on track. Making your system operational System configuration concepts System operations concepts Managing system operations Handling system problems and getting help Complete these tasks when you are ready to start your system for the first time. Your system configuration includes the hardware (system and any deices) and the software (operating system). Discoer what is under the hood of your new system. Focus on some of the most important concepts you need to know to operate your system. See how your new system compares to the competition. Perform a system performance check or set up user profiles. Understand the security features incorporated into your system and how you can take full adantage of them. If you e lost a print job, or want to know what those cryptic error messages mean, and why your system is acting weird, you need troubleshooting. When a problem arises, you can either sole it yourself or get assistance, depending on the nature of the problem. Print this topic for future reference. Completing EZ-Setup: do these tasks first Now that you hae successfully completed EZ-Setup, you need to complete the following tasks to bring your system online for the first time. Once completed, your system will be configured, backed up, and connected to IBM support serices. 1. Configure your LAN console If you did not configure your local area network when prompted in EZ-Setup, do so now. 2. Back up your system Perform an immediate system backup to sae your new configuration and create a regular backup schedule. 3. Install MDAC Add this component to enhance your database functionality. 4. Sae changes to your system Sae the changes you hae just made to your system. 5. Add electronic customer support Run the wizard to set up a support connection to IBM. Additional information on this topic can be found in these sources: Getting started with iseries 400: Introductory reference material for users new to the iseries. Copyright IBM Corp. 1998, 2001 1

2 iseries: Getting started with iseries

Chapter 2. Configuring your LAN console Operations Console allows you to use your PC as the system console, perform control panel functions, or both. With Operations Console, you can administer iseries serers that are on your local area network (LAN). You can also remotely administer seeral iseries serers at different locations, including other LANs. Follow the instructions in Client Access Express -> Operations Console. Copyright IBM Corp. 1998, 2001 3

4 iseries: Getting started with iseries

Chapter 3. Backing up your system When you create a system backup, you create a snapshot of your system information at a particular point in time. The system backup preseres all of the system configuration information that you hae made so far. You can expect to spend between 30 minutes and seeral hours performing this backup, but it is time well spent. Backing up a system is not a difficult process, but it is one that can easily be forgotten as you attend to more pressing tasks. Scheduling backups can not only ease your system maintenance workload by automating a commonly performed function, but help you address problems with data corruption, power outages, and other unforseen situations that may damage your system data. The backup schedule you create plays an important part of that strategy. Backup, Recoery and Media Serices (BRMS) will help you structure your backup tasks, and manage your backup media. You can use BRMS to restore data, recoer an entire system, and perform maintenance tasks. BRMS is not intended to replace your backup and recoery strategy, but it can be a useful tool for implementing that strategy. Backing up your system initially inoles these steps: 1. Initializing the tape 2. Performing the backup Additional information on this topic can be found in these sources: Backing up your system Planning a backup and recoery strategy Backup, Recoery, and Media Serices Copyright IBM Corp. 1998, 2001 5

6 iseries: Getting started with iseries

Chapter 4. Microsoft s Data Access Components (MDAC) One of your system s key roles is as a database serer. The DB2 database that is integrated into your system plays a ital role in managing client information, key business data, and historical archies. How MDAC works on your system MDAC adds important functionality to clients on your system. MDAC enables the uniersal data access required in client/serer enironments, and includes a number of Microsoft data components. Some database components, such as OLE DB which proides a connection between relational and non-relational information sources, including traditional databases, require MDAC to be installed on clients on the system. The minimum leel required for this release is MDAC ersion 2.5. How to get MDAC Download and install the most recent ersion of MDAC on your clients to ensure that all database components function effectiely. You can obtain the most current ersion of MDAC at no additional charge from the Microsoft site. Additional information on this topic can be found in these sources: DB2 Database information Saing changes after installing software After finishing the Checklist for completing installation in the Software Installation manual, you must sae the changes you hae made to your system to make them permanent. Follow these steps: 1. On the command line, type: PWRDWNSYS *IMMED. 2. Once the machine is powered off and 01 BN is on the remote control display on the system, press the white button on the front of the system to power on the machine. The system takes approximately 5 to 10 minutes to power on and completely restart. 3. Once the Function/Data display reads A900 2000 or 01 BN, the system has completed the restart and you are finished installing additional software. 4. Back up your system to sae the installed programs. Adding electronic customer support to your system From time to time, your system may experience problems that need attention from IBM s support serices. Electronic customer support is aailable to help you keep your system operating efficiently. If there is a system hardware or software problem, IBM Customer Engineers can access your system directly to rapidly diagnose and sole the problem.á Electronic customer support lets you: Order and install fixes Access the question-and-answer (Q & A) database Access local serice and IBM product information Access technology forums Copyright IBM Corp. 1998, 2001 7

Access problem analysis reporting and management You can access electronic customer support in one of these ways: 1. Using Uniersal Connection. Uniersal Connection is TCP/IP-based, and is configured using a graphical interface that allows you to choose how you connect to IBM: direct dial-up ia the AT&T Global Network Serice, through an existing Internet serice proider (ISP), or ia a irtual priate network (VPN). This flexibility lets you choose the most conenient solution for your organization, while still proiding a secure connection. For the majority of users, this option is the fastest, most conenient method of accessing electronic customer support. 2. Using the traditional connection. This route is aailable to users who use Systems Network Architecture (SNA) and a Synchronous Data Link Control (SDLC) capable modem. Additional information on this topic can be found in these sources: Installing Fixes Extreme Support 8 iseries: Getting started with iseries

Chapter 5. Making your system operational Your system is ready to go or is it? You re ready to bring your system online. Once you hae completed these tasks, your system will be configured, backed up, and connected to IBM support serices. Depending on the state of your system (is it powered on, are you upgrading from a preious release), you may need to complete some or all or of the tasks below to make your system operational. Before you start Do you want to start and configure the system yourself? If you prefer to use a wizard, obtain Client Access Express. Client Access Express s EZ-Setup simplifies the process of setting up a new serer. Working from Operations Console? Get information on setting it up now. Turn on the system Configure your LAN console Install the interfaces Install Management Central Back up your system Install software Add electronic customer support Your system is more complicated to start and stop than a PC. Get the information you need to power it on safely. Configure your local area network to allow a PC to act as a console. You need a way to communicate with your system. IBM gies you two. Plan now to simplify future administratie tasks. Perform an immediate system backup to sae your new configuration and create a regular backup schedule. Add new licensed programs to your new system. Run the wizard to set up a support connection to IBM Turning on the system If you hae just completed the cabling process, you are ready to turn the system on for the first time. These are the primary tasks to complete: turning the power on and performing an Initial Program Load. Powering on the system These are the steps you need to complete to power on your system for the first time. 1. Locate andáidentify some of the primary components on your control panel. The key components are: Power on light:áindicates when power has become aailable to the unit. Character display: displays the SPCN address, power status, or an SPCN reference code. Power switch:ácontrols the power for eerything installed in the unit. Mode button: allows you to scroll through different operating modes. 2. Turn on the power of any display stations, tape deices, and controllers you will need to operate. 3. Set the mode to Normal. 4. Turn the unit on using the Power Switch.áConfirm that the unit has power by noting theáblinking of the Power on light. If the unit is functioning properly, the Character display will display its normal running message: *rru where rr is the rack address (an integer from 01 to 63) and u indicates the SPCN port the unit is connected, and ranges from 1 to A (1 through 10). If the Power on light does not blink to indicate that power is being receied by the unit, and there is no data displayed in the Character display, erify that your system power cables are properly connected to electrical outlet and that all cables are properly connected to the system before trying again. Copyright IBM Corp. 1998, 2001 9

If the Character display contains a message that does not conform to the standard, go to the Getting Help section immediately. Do not attempt to rebootáthe systemáuntil you hae determined the cause of the problem! Now that the iseries is powered on correctly, you are ready to begin your Initial Program Load Performing an Initial Program Load (IPL) Once your iseries has powered on successfully, you are ready to perform an Initial Program Load (IPL). During an IPL, the system programs load from the system auxiliary storage and the system hardware is checked. If you hae not correctly cabled your system, it will not recognize some of the installed hardware, and you will need to re-ipl in order for that hardware to be recognized on the system. Your system is now ready to perform a normal, unattended IPL. In other words, the system will complete this IPL automatically because you set the mode to Normal. Once it is complete, a signon display will appear on your station. 1. Enter your user ID and press Enter. You should now be taken to the main menu display. 2. Install the interfaces necessary to interact with the system. Additional information on this topic can be found in these sources: Starting and stopping the system Changing operating modes and IPL types Configuring your LAN console Operations Console allows you to use your PC as the system console, perform control panel functions, or both. With Operations Console, you can administer iseries serers that are on your local area network (LAN). You can also remotely administer seeral iseries serers at different locations, including other LANs. Follow the instructions in Client Access Express -> Operations Console. System interfaces You hae a system made up of hardware and software. But how do you interact with that system? How do you get things to work? How do you monitor what is happening across the system? How do you check job performance? The answer is simple: you need an interface. Een better, hae two interfaces. Operations Naigator Operations Naigator is a graphical user interface that proides a connection to your system that looks and feels familiar to those experienced with Microsoft Windows platforms. You get point and click functionality without sacrificing speed and power. If you are comfortable in Windows, you will feel right at home with Operations Naigator. 10 iseries: Getting started with iseries

This example demonstrates the ease with which you can isualize and manage files, jobs, and security, among other components. Operations Naigator will soon become a familiar part of your PC desktop. Command line interface The command line interface (also known as a character-based display or emulation), offers another connection to your system. This interface takes longer to fully master, but may be preferred by those who are more comfortable typing commands rather than pointing and clicking. +--------------------------------------------------------------------------------+ Sign On System..... : SYSTEM01 Subsystem.... : QBASE Display..... : DSP01 User.............. Password............ Program/procedure........ Menu.............. Current library......... +--------------------------------------------------------------------------------+ Like Operations Naigator, the command line interface emulation is installed as a part of Client Access Express. Chapter 5. Making your system operational 11

Both Operations Naigator and the command line interface can operate together on the same desktop, the same way that Windows and the DOS command prompt do. For many functions, Operations Naigator is all you need to accomplish tasks; for some others, the command line interface will be required. Experience will help you decide which to use in eery situation. Additional information on this topic can be found in these sources: Operations Naigator home page Operations Console Installing Management Central Some functions of Management Central are optionally installable components of Operations Naigator, the graphical user interface (GUI) for iseries 400. When you install Operations Naigator, be sure to choose to install Operations Naigator Base Support (which includes most of the Management Central functions), plus Commands, Packages and Products, and Monitors. Follow the instructions in Operations Naigator -> Management Central. Backing up your system When you create a system backup, you create a snapshot of your system information at a particular point in time. The system backup preseres all of the system configuration information that you hae made so far. You can expect to spend between 30 minutes and seeral hours performing this backup, but it is time well spent. Backing up a system is not a difficult process, but it is one that can easily be forgotten as you attend to more pressing tasks. Scheduling backups can not only ease your system maintenance workload by automating a commonly performed function, but help you address problems with data corruption, power outages, and other unforseen situations that may damage your system data. The backup schedule you create plays an important part of that strategy. Backup, Recoery and Media Serices (BRMS) will help you structure your backup tasks, and manage your backup media. You can use BRMS to restore data, recoer an entire system, and perform maintenance tasks. BRMS is not intended to replace your backup and recoery strategy, but it can be a useful tool for implementing that strategy. Backing up your system initially inoles these steps: 1. Initializing the tape 2. Performing the backup Additional information on this topic can be found in these sources: Backing up your system Planning a backup and recoery strategy Backup, Recoery, and Media Serices Initializing the tape for a system backup Before beginning the backup, hae your backup media ready. You will need blank tape cartridges to perform the backup. You may need seeral tapes, depending on the type of tape deice you hae and the size of your system. 12 iseries: Getting started with iseries

Prepare the tape for backup 1. Label the blank tape cartridges that you use for saing the system information (for example: SAVT01, SAVT02). 2. Insert the tape into the iseries and closeáthe tape unit door. The tape unit may wind and rewind the tape to set the tension. This takes approximately three minutes. You do not need to wait for the tape unit to stop to proceed to the next step. Locate the initialize tape display 1. Open the command line interface. 2. On the command line Main Menu, type 3. Press Enter. The General System Tasks display appears. 3. On the command line, type 8. Press Enter. The Deice Operations display appears. 4. On the command line, type 4. Press Enter. The Tape display appears. 5. On the command line, type 2. Press Enter. The Initialize Tape display appears. Set the tape initialization parameters 1. Type the recommended alue for the following parameters: Tape deice: TAP01 (the name of the deice you are using) New olume identifier: sat01 (the same as the label on the tape) Check for actie files: *no 2. Leae all other alues as they appear in the display. Complete the tape initialization 1. Press Enter. The tape unit rewinds the tape which takes approximately one minute. The light on the tape unit goes off. 2. The Tape menu appears with the following message: Volume SAVT01 prepared for operation with owner ID*BLANK 3. Repeat these steps to initialize additional tapes, then perform the backup. Performing a system backup Periodically, and always after installing software, you should back up your system to presere important data and configuration information. Consider the impact to your business operations if you lose all of the information contained on your system through fire, flood, or andalism. A backup of ital information might sae your business from ruin with only relatiely minor disruption in serice. Backups should play a key role in any business s disaster recoery plan. Beginning the backup 1. From the main command line, type GO TAPE. 2. At the Tape display, type 4. 3. Press Enter. 4. At the Sae display, type 2. 5. Press Enter. The Sae the Entire System display explains what happens during the sae process. Read it carefully before proceeding. 6. Press Enter Chapter 5. Making your system operational 13

Configuring the backup From the Specify Command Defaults display, complete the following tasks: 1. Type the recommended alue for the following parameters: Parameter Tape deices Prompt for commands Check for actie files Message queue deliery Start time Recommended Value TAP01 N N *BREAK *CURRENT 2. Press Enter two times. If any display appears, follow the instruction on that display. The Sae display appears with the following message: Sae or restore option completed successfully 3. Remoe the tape when the light on the tape unit goes off. 4. Press F3 to return to the Main Menu. You hae now created a system backup. Ensure that all of your tapes are marked and stored in a safe, accessible place. Create a duplicate set of tapes and store them at a secure location off-site. To streamline the backup procedure, establish a backup schedule. This schedule should be part of a larger backup and recoery strategy. Consider your backup and recoery strategy What would happen to your business if a security breach allowed a malicious user to corrupt client files? Would you be able to recoer that information or would your business collapse in chaos? What would happen if a power failure or flood damaged your system? How would you respond? An effectie backup and recoery strategy takes all kinds of scenarios into account, and plans a response to each. This strategy should be tailored to your business s needs and particular circumstances. A good strategy can t be thrown together in a few minutes. It might require input from a ariety of people at all leels of your organization, and be a time-consuming enture. Howeer, the alternatie is een more time-consuming: responding to a major catastrophe without any planning or strategy to guide you! Create your own backup and recoery strategy now. Additional information can be found in these sources: Planning a backup and recoery strategy Backup and Recoery Guide Backing up your system Installing software From time to time, you may choose to install a licensed program that did not come pre-loaded onto your system. Software installation takes careful planning to minimize downtime and maximize efficiency.á The steps required for planning and installing software are the same for your first installation as they are for your hundredth. 1. Preparing for the installation Careful planning ensures that your software installation process is successful. 14 iseries: Getting started with iseries

2. Performing the installation Once you hae completely planned the installation, you are ready to actually install the software. 3. Saing changes after the installation Sae the changes you hae just made to your system. Additional information on this topic can be found in these sources: Managing software and licensed programs Saing changes after installing software After finishing the Checklist for completing installation in the Software Installation manual, you must sae the changes you hae made to your system to make them permanent. Follow these steps: 1. On the command line, type: PWRDWNSYS *IMMED. 2. Once the machine is powered off and 01 BN is on the remote control display on the system, press the white button on the front of the system to power on the machine. The system takes approximately 5 to 10 minutes to power on and completely restart. 3. Once the Function/Data display reads A900 2000 or 01 BN, the system has completed the restart and you are finished installing additional software. 4. Back up your system to sae the installed programs. Adding electronic customer support to your system From time to time, your system may experience problems that need attention from IBM s support serices. Electronic customer support is aailable to help you keep your system operating efficiently. If there is a system hardware or software problem, IBM Customer Engineers can access your system directly to rapidly diagnose and sole the problem.á Electronic customer support lets you: Order and install fixes Access the question-and-answer (Q & A) database Access local serice and IBM product information Access technology forums Access problem analysis reporting and management You can access electronic customer support in one of these ways: 1. Using Uniersal Connection. Uniersal Connection is TCP/IP-based, and is configured using a graphical interface that allows you to choose how you connect to IBM: direct dial-up ia the AT&T Global Network Serice, through an existing Internet serice proider (ISP), or ia a irtual priate network (VPN). This flexibility lets you choose the most conenient solution for your organization, while still proiding a secure connection. For the majority of users, this option is the fastest, most conenient method of accessing electronic customer support. 2. Using the traditional connection. This route is aailable to users who use Systems Network Architecture (SNA) and a Synchronous Data Link Control (SDLC) capable modem. Additional information on this topic can be found in these sources: Chapter 5. Making your system operational 15

Installing Fixes Extreme Support Configuring Uniersal Connection Unlike the traditional method, Uniersal Connectionáallows you to control how your business will connect to IBM s support serices. Once connected, you can access a ariety of customer support options as you need them. You can also run the Extreme Support wizard to configure Uniersal Connection. Extreme support also allows you to use the Electronic Serice Agent, and it will collect and send data to IBM when problems are encountered. Before you start There are some decisions you need to make prior to running the Uniersal Connection wizard. During the configuration process, you will be asked to choose the type of connection you want to use for electronic customer support. That decision will depend upon your network and accessibility to the Internet from your iseries. If your iseries currently has direct (broadband with a fixed IP address or LAN with a globally routable IP address) access to the Internet (without an interening firewall), you may want to select the Direct connection to the Internet option. This option will allow for the fastest secure access to IBM serices and support. If you already hae an Internet Serice Proider (ISP) which your iseries dials into, you may want to select the Dial up connection using an Internet Serice Proider option. This option will support a secure connection to IBM serices and support at the same time and oer the same dial-up connection currently used by your iseries to access the Internet. If your iseries is not on a network, or is only on a priate network, you may want to select the Dial-up connection using the AT&T Global Network Serices option. This option will proide you with a secure dial-up connection to IBM serices and support only, with no access to the Internet. Note: In order to run the wizard, you must hae installed both Client Access Express and the optional Network component. You must also hae *ALLOBJ and *IOSYSCFG authorities to run the wizard. If you would like to configure your serice proider information, do so now. Prepare to configure Uniersal Connection The tasks below will prepare you to begin configuring your connection. 1. From Operations Naigator, select the system you want to work with. 2. Expand Network. 3. Click Remote Access Serices. 4. Right-click Originator Connection Profiles. 5. Select Uniersal Connection Wizard and begin the configuration process. Note: If you encounter any problems while running the wizard, go to the problem resolution section for adice, and then re-run the wizard. Start the configuration process The tasks below will configure your connection to Electronic Customer Support. 1. At the welcome window, click Next to start configuring. 2. Enter your serice contact information in the spaces proided and click Next to continue. 3. Enter your company s address information in the spaces proided and click Next to continue. 16 iseries: Getting started with iseries

4. Identify the country where your system is located and click Next to continue. 5. Select the Electronic Customer Support connection and click Next to continue. Note: If you want to configure a connection for Serice Agent, the steps below remain the same. 6. Select the type of connection that you want to use for Electronic Customer Support. If you hae chosen to use a dial-up connection to AT&T Global Network Serices, select it now and click Next to continue. a. Select your hardware resource and click Next to continue. b. Identify the line description to use (this may take you through seeral wizard panels). After completing eery panel, click Next to continue. If multiple PPP lines already exist for that resource, you will be asked to select an existing one or to create a new one. If only one already exists, it will be used. c. Select the appropriate AT&T location to dial. Modify the telephone number as appropriate (remember to add any required prefixes to the phone number once it has been selected) and click Next to continue. d. Choose a backup phone number from the aailable list and click Next to continue. e. (optional) Select the modem you would like to use from the aailable list. If you selected an internal modem as your hardware resource, the wizard will not display this screen. Click Next to continue. If you hae chosen to use a Dial up connection using an Internet Serice Proider, select that option now and click Next to continue. a. Select new or existing dialup connection and click Next to continue. If you select an existing connection, the wizard will take you to the steps described below in Complete the configuration. If you select a new connection, the wizard takes you to step b. b. Enter a name for the new Profile and click Next to continue. c. Select your hardware resource and click Next to continue. d. Identify the line description to use (this may take you through seeral wizard panels). After completing each panel, click Next to continue. If multiple PPP lines already exist for that resource, you will be asked to select an existing one or to create a new one. If only one already exists, it will be used. e. Enter the telephone number used to connect to your ISP (remember to add any required prefixes to the phone number) and click Next to continue. f. Enter the account information proided by your ISP and click Next to continue. g. (optional) Select the modem you would like to use from the aailable list. If you selected an internal modem as your hardware resource, the wizard will not display this screen. Click Next to continue. If you hae chosen to use a Direct connection to the Internet, select that option now and click Next to continue. a. Select the TCP/IP interface (address) that you will use. b. Click Next to continue. Complete the configuration The tasks below allow you to confirm the choices you hae made during the configuration process, and then test the resulting connection. Chapter 5. Making your system operational 17

1. The next dialog summarizes the choices you hae made during the configuration process. Verify that the information is correct. If it is not, click Back to make the necessary corrections. 2. Click Finish when you are satisfied that the information is accurate. 3. Test your connection now to erify that the configuration has been successfully completed. 4. Test your electronic customer support connection. Configure serice proider information Occasionally, you may need to contact a serice proider directly, oer the telephone, for assistance. Complete the steps below to configure oice contacts for serice and support: 1. On the command line of the main menu, type: WRKCNTINF and press Enter. The Work with Support Contact Information display appears. 2. On the command line, type 6 (Work with serice proiders), and press Enter. 3. Select option 2 to change the *IBMSRV Control Point Entry, and press Enter. 4. The Change Serice Proider display appears. If you are installing this system in the United States, type the following on the Change Serice Proider display: Hardware serice: 1-800-426-7378 Software serice: 1-800-237-5511 If you are not installing this system in the United States, call your serice representatie for the serice telephone numbers. 5. Press Enter. 6. Press F3 (Exit) to return to the Work with Support Contact Information display. Testing your connection to electronic customer support To ensure your connection to Electronic Customer Support is functioning properly, complete the test described below. Upon receiing your request, an IBM serice representatie will telephone you. Connection/Registration Test 1. The Send Test Request display should be before you. If this screen does not appear, or you hae preiously set up Electronic Customer Support, follow this procedure: a. Go to the main menu. b. On the command line, type SNDSVRQS *TEST. c. Press Enter. 2. Press Enter to submit the test. 3. Test request complete appears at the bottom of the screen. If your test does not work, then note the error message and contact your serice representatie. Congratulations! You hae added and tested your electronic customer support connection. Configuring SNA connection to electronic customer support If you intend to access electronic customer support using SNA and a synchronous (SDLC) capable modem, then complete these tasks to establish your connection to IBM s support serices. Warning: Temporary Leel 5 Header Gather configuration information: 18 iseries: Getting started with iseries

1. Obtain primary and alternate numbers and connection information. If you do not know your serice numbers and are not in the United States, contact IBM s Serice and Support Center information. 2. Power on the modem that is connected to the electronic customer support cable. 3. (optional) You may choose to configure your serice proider information now. for more Get ready to begin configuration: 1. On your PC desktop, open Client Access. 2. Expand Operations Console. Note: If you hae not worked with Operations Console, you need to configure a new connection to your system. A wizard takes you through the configuration process. If no wizard appears, select Connection on the tool bar and select New Connection. If you do not hae Client Access Express installed, you can use telnet or a 5250 emulation session. 3. In Operations Console window, select your system. 4. From the file menu, select Connection. 5. If prompted for the DST user ID and password, type in QSECOFR for both alues. 6. Select Console. The system signon screen appears. 7. Enter your QSECOFR user ID and password. 8. On the command line of the main menu, type: Call QESPHONE and press Enter.á Configure primary telephone information: If you are installing this system in the United States, the Change Data Area (CHGDTAARA) display may hae one of these IBM serice support numbers in the New Value field. If you are not in the United States, call your IBM serice support telephone number. East of the Mississippi Rier: SST:18002378804 West of the Mississippi Rier: SST:18005252834 The SST alue is a modem command. If you receie an error after entering these alues, delete SST, or add the required prefix (for example, SST9 ), and try again. 1. Type in the primary telephone number in the New Value field. 2. Fill in the telephone/connection information outlined below and press Enter. Ensure that the telephone number you enter follows this format: '1234567890 ' Do not add or delete any spaces after the last digit of the telephone number. Adding or deleting characters or spaces will cause an error. Configure alternate telephone information: The Change Data Area (CHGDTAARA) display appears again to allow you to enter the alternate support number (if it is aailable in your area). To determine whether you are on the display for the primary support number or the alternate support number (if it is aailable in your area), check the alue of the substring starting position. For the primary support number, the alue is 001. For the alternate support number, the alue is 051. 1. Type the alternate support telephone number (the support number you did not use as primary) in the New Value field and press Enter. 2. Press F3 (Exit) to return to the main menu. Configure contact information: 1. On the command line of the main menu, type: WRKCNTINF and press Enter. Chapter 5. Making your system operational 19

2. Type 2 (Work with local serice information) and press Enter. 3. The Work with Local Serice Information display appears. Type 2 (Change serice contact information), and press Enter. 4. The Change Serice Contact Information display appears. Type the customer information. 5. Page down to the next display. 6. Enter the correct information in the National language ersion and Media for mailing fixes fields. Press F4 for a list of national language ersions. Press the Help key for more information about the Media for mailing fixes field. 7. Press Enter. 8. The Work with Local Serice Information display appears with the following message: Data area QSSF created in library QUSRSYS. If the contact information has been created and you change it, the following message appears: Support contact information updated. 9. Press F3 (Exit). Test your electronic customer support connection. Additional information on this topic can be found in these sources: Uniersal Connection 20 iseries: Getting started with iseries

Chapter 6. System configuration concepts Your system is up and running, but what is in the box? What kind of software was pre-installed on the system? These are the questions that new users often hae about their system configuration. If someone else purchased the system, you might not een know what they ordered, or how to tell if you receied eerything. You need to know more about your system s hardware and software fast! Hardware Software The hardware side of your system can be as straightforward as a single iseries and workstation in a single room, or as complex as an iseries in one location linked together with others across cities, countries, and continents, spanning numerous workstations and connected to local area networks and wide area networks that support a ariety of platforms. Your system, regardless of its size, is comprised of many components that work seamlessly together to meet the needs of your business. You can iew your hardware configuration Hardware on page 147 here. Your system is shipped with the operating system pre-installed. Additionally, it may contain optional programs that were selected prior to purchasing. You also hae the choice of installing programs contained within the media distribution set. You may also hae additional software packages, such as Facsimile Support for iseries 400, iseries 400 Toolbox for Jaa, NetFinity, HTTP Serer for iseries 400 MQ Series, or any of a list of programs that can be found on the IBM site. To determine which programs are currently installed on your system, follow these instructions Software on page 147. Additional information on this topic can be found in these sources: Software Installation book IBM s product listing (ShopIBM) Copyright IBM Corp. 1998, 2001 21

22 iseries: Getting started with iseries

Chapter 7. System operations concepts IFS? CL? APAR? Eer feel like you are learning an entirely new language in addition to a new operating system? Relax. The terminology used by the iseries 400 will soon become second nature, and you will be using acronyms with the best of them! The iseries uses some of the same operating system concepts and terminology as other platforms. Others are unique. These topics introduce you to some of the most commonly used terminology: Go here... For information like this... Messages Users communicate with each other, and your system communicates with you, using messages. Jobs Eery unit of work performed by your system is called a job. Objects If it takes up memory and can be used to perform a task, it is an object. Logs and journals A log is a iewable history of backup, archie, recoery, and media management operations. A journal is an object that contains a record of system actiity. Authorities (security) You control access to objects, and what users can do with them. Files and file systems Files can be easily organized and managed with Operations Naigator. OS/400 commands Familiarize yourself with the ways commands can be entered, and in what form. User profiles Manage user actiity with profiles. Printing See how printing works on your system. Fixes Discoer fixes and the role they play on your system. Additional reference information can be found in the IBM glossary. Messages Messages are communications that are sent from one person or program to another. Your system sends informational messages that allow you to track system actiity, jobs, users, and errors, and inquiry messages that require you to respond to system actiity. Messages that are immediate or impromptu are sent between users, and are not permanently stored on the system. Predefined messages, on the other hand, are created by the system and are stored. Predefined messages hae these components: a message ID, which seres as a storage identifier the text of the message a message key, which contains a queue identifier indicating the queue to which it belongs You can use these componentsáto track messages. Additional information on this topic can be found in these sources: Handling messages Working with messages Create a message monitor Copyright IBM Corp. 1998, 2001 23

Jobs A job is a unit of work on your system, and may be either interactie or batch. Users who enter commands are creating interactie jobs, while batch jobs run in the background without user interaction. The system initially places a new job in a job queue. The queue defines how many jobs that it contains may be actie and running at the same time. Subsystems manage the queues and determine the queue that each job is assigned to. The subsystem also decides when each job runs. Once the job begins to run, the subsystem selectsáthe area of memory (pool) that the job will use. The oerall performance of the job depends on the amount of resources aailable in that pool. Jobs may be filtered in Operations Naigator by name, user, type, and so on, at the user s conenience. Users may also choose the information that is displayed about a job. For instance, a user may choose to iew the job name, type, queue, priority, and subsystem.á Or, the user may only want to iew job name and status.á This flexibility enables users to iew the information that is important to them as they perform jobs on the system. Additional information on this topic can be found in these sources: Create a job monitor Objects The OS/400 is an object-based operating system. An object is anything that has a name and takes up space on the system. An object can be a data file, a directory, a user, or a printer. Each has an identifying name and holds space on your system. Objects are not limited to indiidual entities on your system. They can also be categorized by type. An object s type defines its purpose and how it is used on the system. Some examples of object types: *USRPRF *LIB User Profile Library Objects on this system are encapsulated. Encapsulation means that they are protected by an interface that defines the operations that can be done to that specific object. Additional information on this topic can be found in these sources: Commands operating on OS/400 objects Management Central and commands OS/400 objects Logs and journals Record keeping is an important management function. Accurate records can proide clues in the case of system failure or attempted security breach. Two key types of records on your system are logs and journals. Logs A log is a database file that contains the history of backup, archie, recoery, and media management operations that may be displayed online or printed for future reference.á Logs are usedáin backup and recoery situations.á Logs can also contain information about jobs and problems 24 iseries: Getting started with iseries

Journals A journal is a system object that contains information about changes made to another system object, such as a database or a security-related object.á The journal can be used to recoer a database.á Regular journaling speeds up database management tasks such as saes. Additional information on this topic can be found in these sources: Logs Job logs History logs Problem logs Eent logs Journals Database journals Backup, Recoery, and Aailability á á System authorities Protecting confidential information is the most important function of security on any system. Your system integrates security features into eery component, from the hardware to the interface that users see. The authorities that you grant to users on the system determine what they can and cannot access, change, and delete. The system does not recognize an absence of authority. Instead, users must be specifically excluded from accessing objects. Example: Granting Miranda the special authority All Object gies her access to the entire system. Miranda can now access to eery object on the system, and you hae no way to deny her access to specific objects, such as payroll. Similarly, granting Job Control to Dennis gies him the ability the control, change, or cancel any job on the system his and eeryone else s. You need to carefully consider who is gien these kinds of global special authorities to minimize who has superuser access to your system. Generally speaking, users only need to be granted the priileges necessary to perform their tasks. Authority can be granted at the object leel (the container that holds objects) or at the object data leel (the actual data within a container). Object leel authority gies a specific user specific access to specific objects. Example: Ophelia needs authorization to delete data in a database, but does not need to delete tables or the database itself. She would be granted object leel authority, rather than object data leel authority. Users can be granted public authority, granting them default access to objects. Users can also be added to an authorization list which gies them access to objects defined within that list. They can also receie adopted authority when the object they hae access to calls another object to complete its tasks. Users with similar kinds of access needs can be assigned indiidual profiles; these profiles can then be grouped to simplify security management. See creating and managing user profiles for more details. Additional information on this topic can be found in Setting system security. Chapter 7. System operations concepts 25

Files and file systems A fileáis another kind of object on your system. Each file has a description that describes its characteristics and how the data associated with the file is organized into records, and, in many cases, the fields in the records. Wheneer a file is processed, the operating system uses this description. Operations Naigator proides access to the integrated file system. In the integrated file system, files are sorted in a familiar, Microsoft Windows-like hierarchical structure. Viewed with Operations Naigator, files are instantly accessible, whether they are stored locally or remotely. This transparency eases management of files across a large network, because users can iew the file system, select files or folders to work with, and send them instantly to multiple systems if they choose. Files can be renamed or relocated with only a few clicks of the mouse. The integrated file system combines a Windows-like hierarchical structure with a Unix-like ability to handle file pointers, effectiely merging the strengths of these two operating systems. The integrated file system has real security adantages, too. In a Unix enironment, a directory is the smallest object that can be owned by a user. In the integrated file system, howeer, users hae object-leel ownership, which allows for a more granular leel of security. Users can hae access rights to indiidual files, rather than to entire directories, which eliminates some security risks, while at the same time, increasing flexibility for the administrator. Additional information on this topic can be found in these sources: File systems and management Integrated file system tasks Integrated file system concepts Control language commands By now, you hae probably run across the first signs of iseries Command language, also known as CL. Those unfamiliar with typing commands may be a bit intimidated by the seemingly-incomprehensible string of characters that you need to know in order to complete tasks on the system. Relax working with CL syntax Command syntax is not as difficult as it appears at first glance. Once you learn the trick to decoding CL, you may find yourself using it as shorthand in other situations. Commands may be entered into source files and compiled into programs. They can be entered from the command line Entering commands on page 27 or run from Management Central. Command syntax Control language syntax follows this structure:á <command name> <parameter> <parameter>... CL is used to interact with and get work done on your system. Commands usually take the form of erb/noun combinations (that is, what the action is followed by what is being acted on). Examples of commands include: Command Verb Noun DSPMSG Display Message CPYF Copy File SBMJOB Submit Job Some commands require a modifier. Examples of this kind of command include: Command Verb Modifier Noun WRKMSGQ Work Message Queue 26 iseries: Getting started with iseries

Command Verb Modifier Noun CRTCLPGM Create CL Program EDTLIBL Edit Library List Entering commands As you can imagine, the possible permutations that you might need to know to be fully fluent on your system is mind-boggling! Fortunately, you do not need to memorize commands that you seldom use to complete daily tasks. The system is designed to help you find just the information you are looking for. To enter a command, use one of these methods: Command prompt from Operations Naigator 1. Select Run command. 2. Enter a command and click Prompt. Press F10 to show additional parameters. Press F9 to show all parameters. Press F1 on a parameter to get specific information. Drag the? into the field to see possible alues. You may also be prompted to enter commands in Operations Naigator. Create and sae common commands as definitions that can be used oer again without retyping. Command prompt from a command line 1. Enter a command and press F4. A short description is gien for each parameter. 2. Press F10 to show additional parameters. 3. Press F9 to show all parameters. 4. Press F1 on a parameter to get specific information. 5. Drag the? into the field to see possible alues. Keyword notation Each parameter has a name. This is a keyword. From the command prompt screen, press F24 (more keys), then F11 (show keywords). You can enter a command from the command line using keyword notation. For example, <command> <keyword>(alue)<keyword>(alue)... The order of <keyword>(alue) combinations does not matter. Positional Notation Syntax:á <command> alue alue... The order of alues is important.á They must be entered in the order they are listed on the command prompt screen. Each command has a limit as to how many positional parameters it can accept. For example, CRTLIB payroll *PROD Production Library produces an error.á DSPCMD <command name> displays (among other information) how many parameters it can accept. You do not need to use all of the parameters aailable for a command. The system has many predefined default alues, and not all of them need to be entered for eery command. Additional information on this topic can be found in these sources: Commands operating on OS/400 objects How commands are named Running commands with Management Central Chapter 7. System operations concepts 27

User profiles When someone asks you to proe your identity, you hae the tools to do that. You can show them a birth certificate, a driing license, and other forms of identification that erify that you are indeed the person you claim to be. Similarly, you need proper identification on your system to proe that you hae access to the confidential information you need to do your job. One way this is handled is through a system of user profiles. A user profile defines a user to your system. It includes: A system user profile name The user s priileges and limitations A list of objects the user owns or is authorized to use A message queue An output queue Information about which groups the user is a member of (up to 16) Information on the user s last signon Job attributes, such as description and priority, the initial program to call, and the initial library list National language settings UNIX-like attributes, such as the userid (UID), group ID (GID), and home directory, similar to those found in UNIX systems User profiles may be linked to group profiles. In this way, all group members share common attributes, common access to specific objects, and common ownership of objects. Group profiles simplify user administration tasks. Administrators can also use Operations Naigator s Management Central functions to create large users and groups that allow them to create, edit, and delete both users and groups across systems. Additional information on this topic can be found in these sources: User profile tasks Printing on iseries If you are used to printing in a Microsoft Windows enironment, you will notice differences when you print on your iseries. Rather than just initiating a print job and picking up the output, printing on your system takes an extra step and gies you increased flexibility. The two-step printing process means that files you want to print are first spooled. During the spooling process, formatting occurs,áchanging what appears on your screen by adding line and page breaks, fonts, and so on, to create a more isually appealing end product. The spooled file then waits in an output queue until you hae decided to moe it to a printer. This allows you to manage printing jobs and resources more effectiely. Spooled files may be printed locally or remotely, immediately or at a later time, putting control oer print jobs entirely in your hands.áthat control is enhanced by Operations Naigator s print functioning.áyou can easilyáiew spooled information, sortáthe output queue, as well as work with those spooled files (open, hold, release, print, and send).á Once your spooled file has been moed from the output queue to a printer, printing begins. Your formatted data is collected and printed on the printer you hae specified. 28 iseries: Getting started with iseries

Operations Naigator also streamlines the printing process by combining print writers, printer deices, and output queues intoáa logical printer.á This is equialent toáthe WRKWTR (Work with all printers) command.á Through either interface, printers can be started, held, taken offline, and brought online. For more information on printing, see Working with printers. Additional information on this topic can be found in these sources: Fixes IBM AS/400 Printing V IBM AS/400 Printing IV IBM AS/400 Printing III Physical security for printers and printer output Periodically, bugs are discoered in iseries programs. IBM issues a fix (formerly called a PTF, or program temporary fix) once corrections are made and the affected programs are recompiled. Multiple fixes are bundled together to form a cumulatie pack, which contains certain recommended fixes. Cumulatie fix packs should be installed quarterly in dynamic enironments, and less frequently in stable ones. Cumulatie fix packs should also be considered prior to making major hardware or software changes to your enironment. Fixes play an important part in your system s maintenance strategy. They gie you a chance to fine-tune your system s operation, add additional functionality, or improe performance. Management Central wizards simplify fix management: they allow you to make a fix aailable on the system immediately or delay the installation if you choose. You can also use the compare and update wizard to compare a model system to multiple target systems to find missing or extra fixes throughout the system. Installed and permanently installed fixes When a fix is installed to a system, both the original and new objects are kept on the system. Logically, two copies of the code are in residence on the machine. This allows you to restart the system using either the original objects or the new objects. Installing a fix to your system gies you a secure backup while you test the new code. If the system functions incorrectly using the new code, you simply restart your system using the original code and remoe the defectie code. When a fix is permanently installed on your system, only the new objects exist on the system. A fix can be permanently installed when it has been in use for a period of time and you feel confident that the chances of it being defectie are small. Aailable and delayed fixes Once a fix is loaded on your system, you can choose to apply it right away or wait for a period of time before applying it. A fix can be made aailable if the system cannot run the old and new code at the same time. Alternatiely, you can choose to delay applying a fix. The fix is then applied the next time the system is restarted. Additional information on this topic can be found in these sources: Chapter 7. System operations concepts 29

Manage fixes with Management Central Fix maintenance strategy Fixes and logical partitions Managing fixes 30 iseries: Getting started with iseries

Chapter 8. Managing system operations Okay, your system is up and running. But how do you make stuff happen? How do you transform the box from a paperweight to an effectie, useful aspect of your business? There are a number of system operations that you need to perform on a daily basis. The topics below are a great starting point to get your system working the way it needs to work. If you want to... Go here... Monitor your system Control jobs to enhance system performance, send, track and handle messages, and monitor your system s performance. Manage users on the system Create and manage user profiles, and set security and authorities. Perform system tasks Discoer how to start and stop your system safely. Order, install and manage fixes to keep your system running at peak leels. Manage hardware-related actiities Work with deices, set up and manage printing tasks, and use remoeable media (tapes, CDs, reels, and cartridges) effectiely. Controlling jobs Controlling how jobs are handled is one of the most common tasks you perform on your system. You can control a job s attributes, change its priority, determine its status, and iew its output using Operations Naigator s work management functions. Why would you need to control a job on the system? Good question. If one of your users has just initiated an enormous job (printing War and Peace, for instance) that is really slowing down the system, you need to be able to change that job s priority, or cancel it altogether. Otherwise, eery other user needing to print business-related material on that printer would hae to wait. To get information about a job on your system: 1. Select the system you want to work with. 2. Expand Work Management. 3. Expand Job Queues. 4. Expand Actie Job Queues. When the information appears in the right window, you can iew the job queue, library, status, jobs on queue, subsystem, and description.á 5. Right-click a job queue and select Properties.á Use the information displayed on the tabs to determine the number of jobs waiting in a job queue.á Select Adanced on the Actiity tab to iew the priority of jobs contained within a queue. Operations Naigator s Management Central allows you to manipulate jobs on your system in numerous ways. Create a monitor, manage job queues Management Central gies you the flexibility you need to work with jobs Additional information on this topic can be found in these sources: Jobs and job queues Managing jobs Create a job monitor Copyright IBM Corp. 1998, 2001 31

Handling messages Oer the course of an aerage work day, you might receie dozens of messages. Your co-workers will send you messages about going for coffee or lunch, about problems they are haing with the system, or about system function in general. In addition, your iseries will send you messages keeping you informed about the state of the system, or about messages you hae sent or receied. Handling these messages, by responding or getting rid of them entirely, keeps you in touch with what is going on around you. Management Central offers you an effectie way to monitor messages. Message monitors allow you to keep a queue clear of unwanted messages, to be notified if a message or set of messages appear, and to delete or get more information about a message. Use Operations Naigator to do the following tasks: Send a message To send a message Delete a message To delete a message Get more information about a message To get more information about a message Reply to a message To reply to a message To send a message 1. Select the system you want to work with. 2. Expand Basic Operations. 3. Right-click Messages and select Send message. In the Send Message dialog, choose the users or workstations that you want to send a message to. You can choose to hae the message interrupt the recipients. You can also choose to request a reply from the users. 4. Type the text of the message and click Send. To delete a message 1. Select the system you want to work with. 2. Expand Basic Operations. 3. Right-click the message and select Delete. 4. In the Confirm Delete dialog, select Delete. To get more information about a message 1. Select the system you want to work with. 2. Expand Basic Operations. 3. Right-click the message you want more information about and select Details. This dialog proides you with the date and time the message was sent, as well as its text and help. 4. Right-click the message and select Properties. This dialog proides more complete information about the message, including the message s type, its queue, job number, and seerity. Alternately, you can also select the message and then click on Properties in the task bar. To reply to a message 1. Select the system you want to work with. 2. Expand Basic Operations. 3. Right-click the message you want to reply to and select Reply. Additional information on this topic can be found in these sources: 32 iseries: Getting started with iseries

Monitor messages Message queues Your system status Quick is your system operating at peak efficiency, or is it slowing down because of high demand? How can you tell? Operations Naigator allows you to monitor your system s performance, and gather data about your system oer a period of time. Use this data to track peak periods of demand on your system, and to plan how to resole that demand. Management Central performance monitors allow you to capture real-time data about your system 24 hours a day, and turn that data into useful information. You can een monitor system status using an internet phone, personal digital assistant (PDA), or browser by using Management Central - Perasie. Additional information on this topic can be found in these sources: Collecting performance data Performance Tools for iseries User profile tasks Managing large numbers of users is simplified by organizing them into groups. These groups can then be assigned shared attributes, access to selected objects, and ownership of objects. If you hae a single iseries, Operations Naigator lets you easily manage user profiles and groups. When you click one of the user or group icons, the operating system performs a security check. Users must hae at least read access to iew a group or user profile. Imagine being able to change authority on six different profiles across 20 systems at once! If you hae a large system and need to administer authority this way, use Management Central s user administration functions to create and edit multiple profiles. Management Central also allows you to delete profiles, scan for owned objects, send profiles between systems, and create user definitions. You can also search across systems for users that match a ariety of criteria, and export user and group information to a PC file. If this sounds like something you need for your system, check out Management Central s user administration function now. You can perform the following user and group administration tasks: Perform common user profile tasks Create a profile Creating a user profile on page 34 Change a profile Changing a user profile on page 34 Copy a profile Copying a profile on page 34 Delete a profile Deleting a profile on page 35 Manage user profiles Create a new group profile To create a new group profile on page 35 Add users to a group To add users to a group on page 35 Remoe users from a group To remoe users from a group on page 35 Chapter 8. Managing system operations 33

Additional information on this topic can be found in these sources: Management Central s user administration function Planning user groups Perform common user profile tasks Operations Naigator simplifies the performance of the following common user profile tasks: Creating a profile Creating a user profile Changing a profile Changing a user profile Copying a profile Copying a profile Deleting a profile To delete a message on page 32 Check out Management Central s user administration function if you need to administer profiles across multiple systems. Creating a user profile Create user profiles as often as you acquire new users who need access to your system. 1. Right-click the Users and Groups icon. 2. Select New User from the context menu. 3. Assign a password by typing one in, or change the password field to no password (logon not allowed). 4. Enter an eight-character user name and description. The password field defaults to use user name. 5. The user must change password at next logon option is now actie.á By default, new users are prompted for a new password the first time they attempt to logon to the system. 6. Change other system alues, which are grouped into dialog buttons: Groups: Add or remoe users from groups. Personal: Identify users by their real name, location, and mail address. The operating system creates a directory for a user once you enter personal information. Capabilities:á Set security parameters for the user. Jobs:á Enter the user s job-related information. Networks:á Add or remoe the user from remote serer sessions. Groups, personal, capabilities, jobs, and network parameters hae default alues that you can use; accept the defaults if you do not need to change any of these settings. 7. Click Add to accept the new user profile. Changing a user profile 1. Right-click the user profile that you want to change. 2. This brings up a window identical to the New User window that you saw when you added a new user profile, with the single exception that you cannot change the user name. 3. When you are done making changes, click OK. Copying a profile To copy a profile: 1. Expand Users and Groups icon. 2. Expand All Users. 3. Select a user whose profile you want to copy. 4. Right-click the selected user to get a context menu. 5. Select New Based On from the context menu. 6. Change all [user profile information]. 7. Click Add when finished. 34 iseries: Getting started with iseries

Deleting a profile To delete a user profile: 1. Highlight the user profile that you want to delete. 2. Click Delete, or select Delete from the Context menu. On the Delete User dialog, select the appropriate options: Do not delete if the user owns object Delete objects that the user owns Transfer objects to another user Additional information on this topic can be found in these sources: Management Central s user administration function Planning user groups Managing user profiles You can combine profiles into groups to further streamline the administration process. The tasks below describe how to create a new Creating a user profile on page 34 group profile and how to add To add users to a group, and how to delete To delete a message on page 32 users from group profiles. Remember, if you are managing user profiles across multiple systems, Management Central has features that can make the task much easier. Check out Management Central s user administration function for more details. To create a new group profile 1. In Operations Naigator, select the system you want to work with. 2. Expand User and Groups. 3. Select the Groups icon. 4. Right-click Groups. 5. Select the context menu item New Group. 6. Select the group name, write an optional description, and add users to the new group profile. The All Users box displays all the user profiles to which you hae at least *USE authority. 7. Click Add and create the group profile. To add users to a group 1. In Operations Naigator, select the system you want to work with. 2. Expand User and Groups. 3. Expand the All Users icon. 4. Select an existing user. 5. Expand the user to get the Properties window. 6. Click Groups. 7. Select the group and click Add after or Add before. 8. Click OK to accept the information in the Groups window. 9. Click OK to close the Properties window. Users can be a member of as many as 16 group profiles. Be sure to assign users to groups in order of most frequent use. To remoe users from a group 1. In Operations Naigator, select the system you want to work with. 2. Expand User and Groups. Chapter 8. Managing system operations 35

3. Expand Groups. 4. In the Group Properties window, highlight the users in the Selected Users list. 5. Click Remoe. 6. Click OK to close the window. Additional information on this topic can be found in these sources: Management Central s user administration function Planning user groups Adding and remoing users from groups Complete these tasks when adding or remoing users from groups: 1. In Operations Naigator, select your system. 2. Expand Users and Groups. 3. Expand All Users. 4. Expand a user to display Properties dialog. 5. Click the Groups button to open the Groups window. A list of the groups on your system is shown in the left pane of the Groups window under the All groups heading. To add a user to a group or groups when that group exists on all of your systems, follow this procedure: 1. Expand the system group you want to add the user to. 2. Expand Users and Groups. 3. Select Edit Groups. 4. Type in the name of the group. 5. Select the user to add to that group. The group or groups will automatically be updated on all systems at the same time to reflect this addition. To add a user profile to a group 1. Select a group from the list and click Add before or Add after. 2. Drag and drop to reorder the groups in the Selected Groups list. To remoe a user from selected groups 1. Highlight one or more groups in the Selected Groups list. 2. Click Remoe. To remoe a user from all groups 1. Close the Properties dialog and go back to the main Operations Naigator window. 2. Select a user. 3. Drag and drop the selected user onto the Users not in a Group icon. Other considerations Define the default authority that is gien to a user s first group of objects by selecting a alue from the Access Rights to Objects Created by User list. Define whether the first group has priate or primary group authority to objects created by a particular user by enabling the Source of Access Rights options. Additional information on this topic can be found in these sources: Planning user groups 36 iseries: Getting started with iseries

Entering personal information into a user profile The system creates a directory for this user once you enter personal information. 1. Expand the user. 2. In the user s Properties dialog, click the Personal button. 3. Enter in the user s name, location, and mail address. Remember, if you are managing user profiles across multiple systems, Management Central has features that can make the task much easier. Check out Management Central s user administration function for more details. Additional information on this topic can be found in these sources: Management Central s user administration function Setting security parameters for users From the Capabilities dialog you can change: User priileges Setting user priileges : Set the priilege class and system priileges. Applications: Set the user s access for specific applications. User passwords Setting user passwords : Set the user s password expiration parameters. Auditing Control user profile auditing : Set the user s action and object auditing parameters. Certificates: Get information about certificates and use the Digital Certificate Manager. Other settings Other user settings on page 38: Set the user s UID number for system reference. Setting user priileges Define the priilege class priileges screen using the following alues: User Programmer System operator System administrator Security officer Default system priileges are automatically selected based on a user s priilege class and the security leel. Additional system priileges can be granted or taken away by simply checking the appropriate box. Use Management Central s Edit Users to change the priileges for many users all at once. Setting user passwords Specify when a user s password expires from the Password dialog in the User Security window. Set the password to expire by clicking one of these options: 1. As specified by system alue 2. A certain number of days after last change (you need to type the number of days in the right-hand field). The number cannot exceed 366 days if you select this option. 3. Neer Control user profile auditing User profile object auditing is a combination of settings for the object itself and for those users who hae access to that object. On the auditing settings page, you can define which actions to log. Selecting the appropriate options lets you define none, change, or all. Your selection under Audit these actions specifies the leel of actiity that is audited for a user profile. Chapter 8. Managing system operations 37

The audit policy function lets you define a system-wide audit. Other user settings The user ID (UID number) is displayed in the other window. Because eery user on the system must hae an unique UID number, use the default setting of system generated alue for a new user. This irtually eliminates the possibility of duplicating a UID number. Additional information on this topic can be found in these sources: Management Central Job-related information for users This information includes the current library, job description, initial program and menu, and attention program. From the jobs window you can further define: General settings: Set the library, maximum storage, schedule priority, accounting codes, job descriptions, and home directory for the jobs. Session startup:á Set initial programs and menus and their libraries, display sign-on information, and limit deice sessions. Display session settings:á Set attention programs, limit program/menu capabilities, set the assistance leel, enable a keyboard buffer, and set user preferences (options) for display. Output settings:á Designate the printer deice, printer output queue, and message queue for the jobs. International settings:á Change the sort sequence, language, country, coded character set ID, and locale to make your system fit the way you do business. Additional information on this topic can be found in these sources: What can I do with Management Central Setting system security Nearly eery day, the newspapers contain headlines about companies who hae had their information inaded by malicious hackers. Only occasionally do they report the een more common occurrence of companies whose information security is breached internally. To help safeguard priileged information from curious eyes, you need to establish security protocols to control access to your data. You can organize user authorities to accomplish your goals. As you plan your system s security, keep in minds the ariety of security leels aailable to you. The leel you choose will depend upon the nature of your business and any security plans already in place. Then, complete these tasks to establish the security of your system: 1. Set system security alues Set security policies: Set the security-related system alues. Set up auditing: Control auditing of actions and new objects. Set up authorization lists: Create, maintain, delete, and display authorization lists. 2. Run security wizard Additional information on this topic can be found in these sources: Tips and Tools 38 iseries: Getting started with iseries

System security classes Security on your system is arranged in a series of leels or classes, each offering a greater degree of security and protection of your data than the preious. Select the leel that best meets the needs of your organization. You can use Operations Naigator to change these settings on a single system, and Management Central to alter them across multiple systems. Leel 20: This leel is referred to as password security. That is, users must hae a password and userid that is recognized by your system in order to gain access to the system. Both the userid and initial password are created for users by the System Administrator. This leel of security offers all users on the system total authority to do anything they want. That means they can access all data, files, objects, and so on, on your system. This may be appropriate for small businesses where internal security is a low priority, but would likely be inappropriate for larger businesses who do not want eery employee to be able to access confidential payroll files, for example. Leel 30: This leel is referred to as resource security. That is, users must hae a alid user ID and password defined for them by the system administrator, and no longer hae automatic access to eerything on the system. User access is limited by the security policies of the business. Leel 40: This leel is referred to as system integrity security. That is, at this leel, the system itself is protected against users. User-written programs cannot directly access the internal control blocks through pointer manipulation. Leel 40 is the default security leel for eery new installation. Leel 50: This leel is referred to as enhanced system integrity security. Leel 50 is the recommended leel of security for most businesses, because it offers the highest leel of security currently possible. Not only is the system protected against user-written programs, but it ensures that users only eer hae access to data on the system, rather than information about the system itself. This offers greater security against anyone attempting to learn about your system. Additional information on this topic can be found in these sources: Tips and Tools Security Reference Management Central s user administration function Setting security policies An important safety precaution you need to take is to set limitations and restrictions to make it more difficult for unauthorized users to get access to your system through workstations. Keep in mind that you must balance security with usability. If you allow users only one attempt to successfully sign onto the system, will you hae users calling you for help eery day because they incorrectly entered their passwords? At the other extreme, hae you set the limit of signons so high that a malicious user has enough time to crack a password? Now, in addition to setting security on one iseries, Management Central allows you to compare system alues to a model system, and then update alues across multiple systems. For instance, you could set the security leel on the model system to 50, then compare and update system alues to set that leel across 25 other systems. This allows you to easily standardize your security leels without haing to set each system indiidually a real time-saings. Chapter 8. Managing system operations 39

To set security for your system, complete these tasks: 1. In Operations Naigator, expand your system. 2. Expand Security. 3. Expand Policies. 4. Expand Security Policy.á The Security Policies Properties dialog appears. 5. Refer to the table below to select the appropriate tabs. 6. After you hae filled in the desired information, click OK. If you want to... Set and change time-out interals for jobs or job message queues Allow security officers to sign on to any display station Control remote sign-on Limit deice sessions Then click this tab... The Time-Out tab The Remote Sign-On tab The Remote Sign-On tab The System Sign-On tab Go to the heading Allow Auto-configuration of or enable Limit each user to one deice session Set action to take for failed sign-on attempts The System Sign-On tab Go to the heading Action when sign-on attempts reached Set maximum sign-on attempts allowed for users The System Sign-On tab Go to the heading Incorrect sign-on attempts Set password parameters, maximum and minimum length, different passwords required Set password expiration parameters Set security leels Allow restore of:á remote serice of the system, programs that adopt their owner, serer security information to be retained Allow objects that are not auditable to go into specific libraries Specify what action needs to happen when a deice error occurs at the workstation The Password tab The Password Expiration tab The Security Controls tab The Security Controls tab The Objects Not Auditable tab The Deice Error Action tab Additional information on this topic can be found in these sources: Security Reference Security system alues Setting up auditing Auditing is a ital tool in tracking what happened on your system at what time. Audit records can help you reconstruct system failure or intrusion. To actiate actie system auditing, the journal QAUDJRN must exist in library QSYS. Each time an eent is selected, the system writes a journal entry in the current receier for this journal. The journal receier can grow significantly in size so do not actiate system auditing if you do not need it. If you hae all object auditing special authority, you can control: 40 iseries: Getting started with iseries

Action Auditing Set action auditing New Object Auditing Creating a user profile on page 34 Set action auditing To open the Action Auditing dialog: 1. In Operations Naigator, select the system you want to work with. 2. Expand Security Policies. 3. Expand Security. 4. Expand Audit Policy. Start auditing new objects This tab can only be accessed object auditing is actiated. You can select the default auditing alue for new objects to be none, user settings, change to objects, orall access of objects. 1. In Operations Naigator, select the system you want to work with. 2. Expand Security. 3. Expand Policies. 4. Expand Audit Policy. 5. Click the New Objects tab in the Properties dialog. Additional information on this topic can be found in these sources: Security Reference Defining authorization lists Running out of time to set up and monitor authority for eery indiidual user on the system? Simplify management of authorities by creating authorization lists. Once you hae determined the kind of authorization lists you need, use Operations Naigator to perform the following tasks: Create a new authorization list Creating a user profile on page 34 Add users and groups To add users to a group on page 35 Change user permissions Changing a user profile on page 34 Display secured objects To display secured objects on page 42 To create a new authorization list 1. Select the system you want to work with. 2. Expand Security. 3. Right-click Authorization Lists. 4. Select New Authorization List from the Context menu. This opens a dialog where you enter a name, description, and select a public authority leel. To add users and groups 1. Select the system you want to work with. 2. Expand Security. 3. Click Add and expand the list of users or groups. 4. Select one or more users and groups. 5. Click OK. Chapter 8. Managing system operations 41

To change user permissions 1. Select the system you want to work with. 2. Expand Security. 3. Expand the authorization list that you want to change. This opens the basic authorization list dialog where you can change permissions for the displayed users or groups by checking the use, change, all, and exclude radio buttons. 4. Click Details to grant and reoke indiidual permissions. 5. Click Customize to assign customized permissions. This opens a dialog that contains a list of the indiidual rights that a user can hae. To display secured objects 1. Select the system you want to work with. 2. Expand Security. 3. Expand an authorization list. This opens the basic authorization list dialog. 4. Click Secured Objects. A window opens that displays all the objects that the authorization list secures. Additional information on this topic can be found in these sources: What can I do with Management Central? Using the security wizard The security wizard can adise you on security planning. You also need to run the security wizard when you moe to new ersions and releases of the iseries.á As new functionality is added to your system, you need to make sure that your security policy remains in force, and that users hae consistent access to new components on the system. The security wizard asks you questions and assess your security needs based on your answers.á It then offers up a selection of recommended security settings.á Youáchoose which recommendations to implement. The security wizard only makes suggestions:á no changes are made on your system until you hae approed of them. The security wizard also creates detailed reports based on your answers which explain in detail the recommendations it makes.á Once you hae selected the settings you want to implement on your system, the security wizard applies them to the system, and saes them for future reference. Note: You must hae a user ID with *ALLOBJ, *SECADMN, *AUDIT, and *IOSYSCFG authority to use the wizard. If you do not hae the correct authority, you will not be able to access the wizard. To run the security wizard in Operations Naigator: 1. Right click Security. 2. Select Configure. Additional information on this topic can be found in these sources: Tips and Tools for Securing your iseries Starting and stopping the iseries To start the system, turn the system power on and do an initial program load (IPL). During an IPL, system programs load from the system auxiliary storage and the system hardware is checked. When the IPL is finished, the Sign On display is shown on the console. 42 iseries: Getting started with iseries

You can stop the system (turn the power off) using the Power On and Off Tasks (POWER) menu. To get to the Power On and Off Tasks (POWER) menu, type go power on any command line and press Enter. You can also stop the system by using the Power pushbutton. Howeer, using the Power pushbutton may cause errors with your data files and other objects on the system. You can set up a schedule that automatically powers your system on and off. You can determine the time of day you want the system powered on and off. You can also specify special circumstances that change that normal daily schedule, such as a holiday or special closing. Refer to the following table when starting or stopping your system: Starting your system Stopping your system Starting the system (Unattended IPL) Stopping the system Signing on to the system Powering off the system immediately Starting a remote system Using the power pushbutton Changing your system IPL from your system control panel Changing your system during IPL (Attended IPL) Changing your system password Working with subsystems Additional information on this topic can be found in these sources: System reference codes and primary partitions System reference codes and secondary partitions What causes an abnormal IPL? Controlled shutdown concepts Setting up an automatic power on and off schedule You can plan when you want to power on and off the system by setting the power on and off schedule. To work with the power on and off schedule, go to the Power On and Off Tasks (POWER) menu. Tip: You can also display this menu from the Customize your system, users, and deices (SETUP) menu by selecting option 3 (Power on and off tasks). Displaying the power on and off schedule The power on and off schedule ensures that the system is powered on and off at specific times during the day or night. To iew this schedule: 1. On any command line, type go power and press Enter. 2. Select option 1 (Display power on and off schedule) on the Power On and Off Tasks menu. The power on and off schedule shows the date, day, and time (using the 24-hour clock) that the system will be powered on and off. The Description column includes comments about those days that hae been changed from the system s regular schedule. Any user can display this schedule. Changing power on and off schedule defaults To set up your own power on and off schedule, select option 2 (Change power on and off schedule) on the Power On and Off Tasks (POWER) menu. On the Change Power On/Off Schedule display, press F10 (Change power on/off defaults). On this display, you can change the first day of the week by typing a number in the First day of week field. Also, the system automatically sends users a message telling them when the system will be powered off. You can indicate how many minutes before power off you want the system to send this message in the Minutes before power off to send field. Chapter 8. Managing system operations 43

When the system sends the power off message, you can delay the scheduled time for powering off from 30 minutes to 3 hours when you reply to the message. Then the system will wait the time specified before powering off. You do not hae another chance to delay the time. For example, if you want the system powered on Mondays at 5:30 a.m. and off on Fridays at 11:00 p.m, and on Saturdays and Sundays you want the system powered on at 7:30 a.m. and off at 8:00 p.m., type the new times in the Default Power On and Default Power Off columns next to Saturday and Sunday. When you press Enter, your changes are shown on the Display Power On/Off Schedule and the Change Power On/Off Schedule displays. Changing a Day in the Power On and Off Schedule The Change Power On/Off Schedule display allows you to change the power on and off schedule for a single day. For example, to change the power on and off time for the plant s company picnic on Wednesday, May 3: 1. Type 14:30 in the Power Off column to power the system off at 2:30 p.m. so the employees can attend the picnic. 2. Type the reason for the change, Closing - Company picnic, in the Description column across from the date and time and press Enter. 3. Type the start time 5:30 in the Power On column to power the system back on Thursday, May 4. To display the schedule starting on a different date, type the date you want to start with in the Start list at field and press Enter. The information that is displayed begins with the date you specify. Soling Problems with the Automatic Power Schedule: If the power schedule is not working: Make sure that the Start Cleanup (STRCLNUP) command is part of your startup program. The automatic power scheduler uses a job called QSYSSCD to process the requests for schedule changes. The Start Cleanup (STRCLNUP) command must be run to start the QSYSSCD job. The IBM-supplied startup program includes the Start Cleanup (STRCLNUP) command. If you hae your own startup program from a preious release, it may not contain the Start Cleanup (STRCLNUP) command. Make sure that you specify Yes on the Change Cleanup (CHGCLNUP) command to allow automatic cleanup. The QSYSSCD job will not start if you do not allow automatic cleanup. Make sure that the Start Cleanup (STRCLNUP) command submits the QSYSSCD job to the job queue specified in the Change Cleanup (CHGCLNUP) command. Check to see if the QSYSSCD job is running; it could be on a held job queue. Make sure that the job queue that the Start Cleanup (STRCLNUP) command is submitted to has the maximum jobs parameter set to *NOMAX or a number greater than 1. Because the QSYSSCD job always runs, the other jobs that perform automatic cleanup and power off functions are not able to start if the maximum jobs parameter is set to 1. To change the maximum jobs parameter, use the Change Subsystem Description (CHGSBSD) command. Make sure the mode is set to Normal or Auto. Starting the System When you start your system by turning the power on, an IPL (initial program load) is done for the system to reset storage and recognize changes to certain system characteristics. If you are working on a system that has logical partitions, please refer to the documentation on starting and stopping logically partitioned systems. 44 iseries: Getting started with iseries

Note: A license authorization code (also referred to as a licensed key) must be installed for OS/400 and certain licensed programs. Each locked program has a unique license authorization code that must be installed within 70 days of installing the program. Starting with Version 4 Release 2, OS/400 will not IPL after the 70 day grace period without a alid key. Without a alid key, a message is sent to you (and possibly other users depending on how your system is set up) eery four hours during the 70 day grace period. Messages stop when you enter a alid key. After the 70 day grace period, a message is sent eery hour to you and to the QSYSMSG message queue. All high priority messages in the system are sent to the QSYSMSG message queue. Messages stop when you enter a alid key. A alid key must be entered, or the system will not complete the IPL process after the end of the 70 day grace period. You can enter the key by using the Add License Key Information (ADDLICKEY) command from any OS/400 command line before the grace period expires. If the grace period has expired or if you need a new OS/400 software license key, contact your IBM marketing representatie or IBM business partner. When to perform an IPL There are four different situations that typically require an initial program load: starting normal operations, starting a remote system, changing configuration options, and recoering after a power failure. When your system is sent to you, it is set to do a normal or unattended IPL. An unattended IPL is done automatically by the system after the power is turned on; then the Sign On display is shown on all aailable display stations. An attended IPL shows displays on the display station you are using for a console. This allows you to change the configuration options such as how the system does an IPL and how the system runs. IPL Summary System State Unattended IPL Attended IPL Running 1. Set the mode to Normal. 2. Type ENDSYS or ENDSBS *ALL on any command line and press Enter. 3. Type PWRDWNSYS *IMMED RESTART(*YES) on any command line and press Enter. 1. Set the mode to Manual. 2. Type ENDSYS or ENDSBS *ALL on any command line and press Enter. 3. Type PWRDWNSYS *IMMED RESTART(*YES) on any command line and press Enter. 4. Follow the displays on the console to complete the IPL. 5. Set the mode to Normal. Not Running 1. Set the mode to Normal. 1. Set the mode to Manual. 2. Power on all deices. 2. Power on all deices. 3. Press the Power pushbutton to Power On. 3. Press the Power pushbutton to Power On. 4. Follow the displays on the console to complete the IPL. 5. Set the mode to Normal. Note: While not required, setting the mode to Normal after the IPL is finished is a good practice. Normal operations (unattended IPL) Before you start The mode must be set to Normal (unattended IPL). The QIPLTYPE system alue must be set to 0 (unattended IPL). See system alues that control IPL for information on how to set this system alue. If this is the first time you are doing an IPL, the QIPLTYPE system alue is already set to 0. Chapter 8. Managing system operations 45

Note: The system must be powered on, and the IPL complete before you can display or change the QIPLTYPE system alue. To do an unattended IPL: 1. Turn on the power of any display stations, printers, tape deices, and controllers you or others may want to use. 2. Make sure that the mode is set to Normal. Use the Power pushbutton to turn on the system. 3. When the unattended IPL is done, the Sign On display appears on the display station. Starting the iseries: signing on To sign on the system: 1. Type your user ID, your password (if security is actie), and fill in any of the optional entry fields you want to use. Use the Tab key to moe the cursor from field to field on the display. Note: The Password field is displayed only if password security is actie on the system. In the top right corner of the Sign On display, the name of the system you are using, the subsystem the system is using, and the display station identifier (ID) are shown. 2. Press Enter. If this is an unattended IPL (initial program load), one or more of the following occurs, depending on what options you select on this display or what is defined in your user profile: The Main Menu is displayed. Another menu is displayed. A program or procedure is run. A current library is inserted into your library list. If you specify a program or procedure to run and a menu to be displayed, the program or procedure is run first and then the menu is shown. Now that your system is up and running be aware that: The Operational Assistant displays are now the default. The system cleanup functions are automatically started with default alues. The Attention key program defaults to display the Operational Assistant (ASSIST) menu. Starting a remote system To start the remote system automatically using a telephone and modem, you need to set system alue QRMTIPL to 1. Before you start: 1. Set the mode on the control panel to Normal or Auto and turn the system off. 2. After the system is turned off and is made ready for remote initial program load (IPL), do not turn the modem on or off. Otherwise, the system may start unexpectedly, although it will turn itself off in a few minutes. To start the remote system: 1. Dial the telephone number that is assigned to the electronic customer support modem and line of the remote system. Note: If you hang up before the silence, the IPL may not complete. 2. Wait about 20 to 40 seconds while the telephone rings. You will hear a modem tone and then silence. At this time, the communication is being established from the modem to the control panel to start the IPL sequence. 46 iseries: Getting started with iseries

3. Hang up the telephone. The system does an IPL and the Sign On display is shown. 4. Sign on to the system. Changing your system IPL from the system control panel The Increment/Decrement buttons are used to change the initial program load (IPL) type and mode on systems without a mode button. Use Function 02 to select the IPL type (A, B, or D) and Mode (Normal, Manual). To select IPLátype and mode, do the following: 1. Use the Increment/Decrement buttons to select Function 02, and press the Enter pushbutton. 2. Use the Increment/Decrement buttons to select the IPL type and mode you want, and then press the Enter pushbutton to sae. 3. You can also specify a fast or slow IPL that can only be set one time at the console panel when the system is powered off. Select Function 02 and press Enter twice. Then, use the Increment/Decrement buttons to select F(Fast), S(Slow), or V(Value from IPL attributes). The IPL attribute determines subsequent IPLs. *MIN is the recommended setting, howeer, if you anticipate any hardware problems, specify *ALL on the Hardware diagnostics parameter. Use the Change IPL Attributes (CHGIPLA) command to change the IPL attribute. System Values That Control IPL The system alues listed below let you control the type of IPL (initial program load) and the way the system does an IPL. Change these system alues using option 2 (Change) on the Work with System Values (WRKSYSVAL) display. QIPLDATTIM The IPL date and time system alue lets you specify the IPL date and time for starting the system automatically. The default alue *NONE indicates that no timed automatic IPL is desired. You can set this system alue independently in each partition. If the primary partition is powered down at the time an automatic IPL should occur in a secondary partition, the IPL will not occur. When the primary partition does IPL, the secondary partition is IPLed if its IPL date and time is past due. The secondary partition will not IPL if it is configured with an IPL action of hold. The date format used by your system for date and time is defined in the system alue QDATFMT. You need to know your system date format for step 1. Use option 5 (Display) to determine the format. To specify the IPL date and time: 1. Type the new date oer the current date as follows: MM/DD/YY where MM is the month, DD is the day, and YY is the year. For example, to start the system on June 26, 1997, type 06/26/97. YY/MM/DD where YY is the year, MM is the month, and DD is the day. For example, to start the system on June 26, 1997, type 97/06/26. DD/MM/YY where DD is the day, MM is the month, and YY is the year. For example, to start the system on June 26, 1997, type 26/06/97. YY/DDD where YY is the year and DDD is the Julian date. For example, to start the system on June 26, 1997, type 97/178. June 26 is the 178th day of the year. Note: The format is set with the system alue QDATFMT. The separator is set with the system alue QDATSEP. The separator is optional. 2. Type the time in the format HH:MM:SS where HH is the hour, MM is the minute, and SS is the second. Use the 24-hour clock. For example, if you want to start the system at 8:16 a.m., type 08:16:00, or if you want to start the system at 8:16 p.m., type 20:16:00. Chapter 8. Managing system operations 47

Note: 1. The time separator format is set with the system alue QTIMSEP. The separator is optional. 2. If you are using the automatic power schedule, you can force the power schedule to update the QIPLDATTIM system alue by entering the following command on any command line. CHGPWRSCDE DAY(*TODAY) PWRONTIME(*SAME) PWROFFTIME(*SAME) QIPLSTS The IPL status system alue displays the way the system did the last IPL. You cannot change this system alue. Use option 5 (Display) on the Work with System Values display to display it. 0 An IPL from the control panel of the system unit or from dedicated serice tool (DST) for a secondary partition. 1 An unattended IPL automatically after a power failure (QPWRRSTIPL set to 1). 2 An unattended IPL after using the Power Down System (PWRDWNSYS) command with the Restart after power down (RESTART) parameter set to *YES. 3 A unattended scheduled IPL (QIPLDATTIM set to the date and time for the IPL to occur). 4 An unattended remote IPL from another location (QRMTIPL set to 1). QIPLTYPE The IPL type system alue defines the type of IPL the system does from the control panel. 0 An unattended IPL. Start the system without an operator (see Normal Operations (Unattended IPL)). If the mode is set to Manual, an attended IPL is performed instead. 1 An attended IPL with Dedicated Serice Tools (DST) Start the system with an operator (see Changing Your System During IPL (Attended IPL).) An unattended IPL is done if it is done remotely, by date and time, or after power failure. 2 An attended IPL in debug mode. Start the system with an operator. The console description, QCONSOLE, is left aried on. You should only use this for problem analysis because it preents other deices on the work station controller from being used. QPWRRSTIPL The automatic IPL system alue allows the system to start automatically when power is restored after a power failure. On a partitioned system, change this system alue from the primary partition only. The QPWRRSTIPL system alue controls only the primary partition. The IPL action configuration alue for the secondary partition determines whether a secondary partition will IPL at the same time as the primary partition. For details on configuring logical partitions on your AS/400 48 iseries: Getting started with iseries

system, go to Planning and Setting Up under the Logical Partitions topic in the iseries Information Center. 0 Does not do an automatic IPL after a power failure. 1 Does an automatic IPL after a power failure. QRMTIPL The remote IPL system alue allows you to start the remote system by using your telephone and a modem or the SPCN signal. 0 Does not allow a remote IPL. 1 Allows a remote IPL. Note:If you are using a modem eliminator, your system will power up eery time PWRDWNSYS RESTART(*NO) is issued. QUPSDLYTIM The uninterruptible power supply delay time system alue controls the length of time the system will wait, before saing main storage and power down the system. If utility power is restored before the time ends, the system ends the timer. If the timer ends first, the system begins to sae main storage or goes into CPM. On a partitioned system, change this system alue from the primary partition only. There are three choices for the QUPSDLYTIM alue. *BASIC or *CALC The default alue for QUPSDLYTIM is *CALC. Leaing QUPSDLYTIM set to *CALC may defeat the purpose of haing a UPS. *BASIC or *CALC proide the same function in systems using PowerPC (R) technology. After a fixed interal delay (typically 45 seconds), high end systems enter CPM, while entry systems equipped with a UPS perform a controlled shutdown. Users with a UPS who prefer a shorter IPL may wish to use a numeric alue. *NOMAX *NOMAX is used when a user supplied program is controlling the power down of the system or a generator is proiding unlimited UPS power. 0 Automatic system power down when the system utility power fails. 1 99999 Specifies delay time in seconds before the system powers down. See the Uninterruptible power supply delay time system alue (QUPSDLYTIM) for more detailed information about QUPSDLYTIM. Chapter 8. Managing system operations 49

QUPSMSGQ The uninterruptible power supply message queue system alue allows you to specify where you want your messages sent when the power to the system is interrupted. Note: The SCPF job clears the message queue specified for the system alue QUPSMSGQ. QSYS/QSYSOPR Sends the messages to the system operator s message queue when power to the system is interrupted. message queue library Specifies another message queue (in addition to the system operator s message queue) where messages are sent when power to the system is interrupted. Specifies the library where the other message queue is located. Changing the system during IPL (attended IPL) If you want to change initial program load (IPL) options, install the operating system, use dedicated serice tools, work with logical partitions, or recoer from a system failure, you need to perform an attended IPL. Before you start: Set the mode to Manual, or Set the QIPLTYPE system alue to 1. For information on how to set this system alue, see System Values That Control IPL. Note: The system must be on and the IPL complete before you can display or change the QIPLTYPE system alue. Perform the attended IPL Performing an attended IPL when the power is off: 1. Make sure that the power for the display station you are using as the console is turned on. The power should be turned on for display stations, printers, tape deices, and controllers you or others may want to use. 2. Use the control panel to do the following: a. Make sure that Manual mode is selected on the control panel. b. Use the Power pushbutton to turn on the power. When you hae completed the attended IPL, you may want to set the mode to Normal. Performing an attended IPL when the power is on: If the system is running and you are able to enter commands: 1. Set the mode to Manual. 2. On any command line, type PWRDWNSYS OPTION(*IMMED) RESTART(*YES) 3. Press Enter. If you cannot enter commands, start the IPL from the operator panel, as follows: 1. Use the Power pushbutton to turn off the system. 2. Press the Power pushbutton to start an IPL. During the attended IPL, the IPL or Install the System display is shown on the console. 50 iseries: Getting started with iseries

3. On the IPL or Install the System display, select option 1 (Perform an IPL) and press Enter. The IPL Sign On display is shown. You may hae to wait 30 or more minutes for this display to appear. 4. Sign on to the system using the Sign On display. The Select Products to Work with PTFs display is shown. - On the Select Products to Work with PTFs display, select the product for which you want to apply the fix and continue with the attended IPL. - If you do not want to apply a fix, press F3 (Exit) on the Select Products to Work with PTFs display and continue with the IPL. 5. The IPL Options display is shown next. See Changing IPL Options below to select options to change system attributes. Change IPL options To change IPL options, you need to do an attended IPL. Use one of the procedures described aboe to begin the IPL. When you select option 1 (Perform an IPL) on the IPL or Install the System display, the IPL Options display is shown. To change an IPL option, type the new option oer the existing information, and press Enter. Depending on what you selected, one of the following displays is shown next: If you typed Y (Yes) in the Set major system options field, the Set Major System Options display is shown. Note: If you also typed Y (Yes) in the Define or change system at IPL field, the Define or Change the System at IPL menu is shown after the Set Major Options display. If you typed Y (Yes) in the Define or change system at IPL field and N (No) in the Set major system options field, the Define or Change System at IPL menu is shown. If you typed N (No) for both the Set major system options field and the Define or change system at IPL field, the menu, program, or procedure you defined on the Sign On display or in your user profile is shown. Set Major System Options The Set Major System Options display allows you to select automatic configuration, the type of deice configuration naming, and the special enironment in which you want to run. 1. Using the following information, type the new alues oer the existing alues in the following fields: Enable automatic configuration Y (Yes) automatically configures local deices. N (No) indicates no automatic configuration. Deice configuration naming *NORMAL uses a naming conention unique to the iseries, for example, DSP01 and PRT01 for displays and printers, TAP01 and DKT01 for tape and diskette deices. *S36 uses a naming conention similar to System/36(TM), for example, W1 for workstations, P1 for printers, and T1 and I1 for tape and diskette deices. *DEVADR uses a naming conention which is obtained from the deice resource name, for example, DSP010203 for a display station, PRT010203 for a printer, TAP01 and DKT01 for tape and diskette deices. Default special enironment *NONE indicates there is no special enironment. *S36 sets up the System/36 enironment. 2. Press Enter. Depending on what you selected on the IPL Options display, the following is shown next: Chapter 8. Managing system operations 51

If you typed an N (No) in the Define or change the system at IPL field, the menu, program, or procedure you defined on the Sign On display is shown next. If you typed a Y (Yes) in the Define or change system at IPL field, the Define or Change System at IPL menu is displayed. Define or change the system at IPL On the Define or Change the System at IPL display, you can change the system configuration, system alues, network attributes, user profiles, and object or file attributes. This display is shown when you type Y (Yes) in the Define or change the system at IPL field on the IPL Options display. 1. Do one of the following: To change the way the system starts, select option 3 (System alue commands) and go to Changing System Values During IPL. If you selected option 1, 2, 4, 5, 6, or 7, continue to select options and use the displays until you are finished. 2. When you are finished using the options on this display, press F3 (Exit and continue IPL) to continue the IPL. Change system alues during IPL System alues control information that affects the operation of certain parts of the system. Some system alues that you change do not take effect until the next IPL; other system alues take effect immediately. On the System Value Commands display, you can change system alues that affect IPL or other areas of the system. This display is shown when you type a Y (Yes) in the Define or change the system at IPL field on the IPL Options display (see step 6). To change system alues during an IPL: 1. Select option 3 (System alue commands) on the Define or Change System at IPL display (see Defining or Changing the System at IPL). 2. Select option 3 (Work with system alues). 3. Select option 2 (Change) on the Work with System Values display. 4. Type the new system alue oer the current alue and press Enter. 5. Press F3 (Exit) to return to the System Value Commands display. 6. Press F3 (Exit) to return to the Define or Change the System at IPL display, and press F3 again to continue the IPL. Security considerations:to change system alues, you must be signed on as QPGMR, QSYSOPR, or QSRV, or hae all object (*ALLOBJ) authority. Certain system alues can be changed only by a security officer (someone with all object (*ALLOBJ) and security administrator (*SECADM) special authorities). For information about system alues that control the way the system does an IPL, see System Values That Control IPL. Edit access paths during attended IPL Access paths define the order that records in a database file are organized for processing by a program. If there are access paths to rebuild, the Edit Rebuild of Access Paths display is shown after the IPL Options display. Tip: use the online help information on this display to get more about each column and field. A message notifies you that a journal should perform an access path recoery. A journal is a system object. It is used to record entries in a journal receier when a change is made to the database files associated with the journal. Any access path that is recoerable because it was recorded is not shown on this display. The IPL threshold indicates that access paths with a sequence less than or equal to the 52 iseries: Getting started with iseries

number specified will be rebuilt at IPL time. It is a alue from 1 through 99 that you can set (default is 50). If the IPL threshold changes, all access paths with a status of IPL and AFTIPL will change to reflect the new status of the IPL threshold. To change the sequence of access paths that will be rebuilt: Make any changes to the Seq column. Press Enter. If you do not want to change the sequence, press Enter and the Display Access Path Status display is shown if there are access paths left to be rebuilt. Tip: Press Enter to continue with the IPL from the Edit Rebuild of Access Paths display. If no access paths need to be rebuilt, the IPL continues. If you press F3 (Exit and continue IPL) the access paths will be rebuilt while the IPL continues. If you press F12 (Cancel), you return to the Edit Rebuild of Access Paths display. Eery 5 seconds, the display is updated with the current run time. After all the access paths hae been rebuilt (access paths with a sequence less than or equal to the IPL threshold), the IPL continues. Edit check pending constraints during attended IPL: During an attended IPL, the Edit Check Pending Constraints display is shown if there are constraints to be erified. A constraint is an attribute that places restriction or limitation on a physical file. Tip: use the online help information on this display to get more about each column and field. On the Edit Check Pending Constraints display, you can change the sequence (1 through 99) of the constraints to be erified. If the constraint has a sequence less than or equal to the IPL threshold, it is erified during the IPL. If a constraint has a sequence greater than the IPL threshold, it is erified after IPL. The sequence *HLD indicates that the constraint is not erified until it is changed to a number from 1 through 99. When the IPL threshold changes, all constraints with a status of IPL or AFTIPL are changed to reflect the new status of the IPL threshold. To change the sequence of check pending constraints: 1. Make any changes to the Seq column 2. Press Enter. If you do not want to change the sequence, press Enter. The Display Constraint Status display is shown if there are constraints left to be erified. If you press F3 (Exit and continue IPL) the constraints are erified while the IPL continues. Eery fie seconds, the display is updated with the current run time. After all constraints with IPL status hae been erified, the IPL continues. If you press F12 (Cancel), you return to the Edit Check Pending Constraints display. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Tips for Improing IPL Performance The topics that follow describe actions that you can take to reduce the amount of time that it takes your system to perform an IPL (initial program load). Note: A normal IPL means that your preious system shutdown was under normal conditions rather than being an abrupt shutdown caused, for example, by a power failure. Chapter 8. Managing system operations 53

Cleanup Actiities That Affect IPL Performance Cleaning Up Your System suggests many tasks that you can perform to reduce the clutter on your system and improe oerall system performance. Following are specific cleanup actiities that can hae the most impact on the time that it takes your system to perform an IPL. Reducing the Number of Jobs on the System: In simple terms, a new iseries job starts wheneer a user signs on the system or submits a batch job. When a job starts, the system creates an internal entry in a job table. It uses this table to keep track of all the jobs on the system and to organize information about those jobs. From a user perspectie, an interactie job ends when the user signs off. A batch job ends when all the programs hae run to completion. Howeer, from a system perspectie, a job ends when all the objects that are associated with that job hae been remoed from the system. Often, jobs create spooled files that remain on the system for days or weeks. As long as those spooled files remain, the entry for the job remains in the job table. When you perform an IPL, the system processes all the entries in the job table. A ery large job entry table can significantly increase your IPL time. The best way to clean up jobs is to remoe unnecessary spooled files. Setting Up Automatic Cleanup Setting Up Automatic Cleanup on page 57 describes how you can set up your system to automatically remoe old spooled files. Cleaning Up Obsolete Objects Cleaning Up Obsolete Objects on page 58 describes steps you can take to encourage users to remoe spooled files that they no longer need. You can use the Display Job Tables (DSPJOBTBL) command to monitor the size of the job table on your system. Use this as a signal for when you need to encourage your users to perform housekeeping. The image below illustrates this concept. +--------------------------------------------------------------------------------+ Display Job Tables SYSTEMX 02/20/97 14:05:32 Permanent job structures: Temporary job structures: Initial.... : 30 Initial.... : 20 Additional... : 10 Additional... : 10 Aailable... : 3 ---------------------Entries---------------------- Table Size Total Aailable In-use Other 1 164608 160 8 152 0 +--------------------------------------------------------------------------------+ Reducing the Number of Deice Descriptions: Wheneer you perform an IPL, the system processes eery deice description on the system seeral times (to make performance calculations and to prepare for arying on the deice). You can reduce this processing time by remoing obsolete deice descriptions from your system. Cleaning Up Your Hardware Configuration describes a method for finding and remoing unnecessary deice descriptions. System Settings That Affect IPL Performance You can use the Change IPL Attributes (CHGIPLA) command to control some of the processing that the system does during an IPL. The example below shows the prompt display for the command. The topics that follow describe seeral of the parameters and how they affect IPL performance. For a complete description of the parameters, refer to online information or the Programming topic in the iseries Information Center. +--------------------------------------------------------------------------------+ Change IPL Attributes (CHGIPLA) Type choices, press Enter. 54 iseries: Getting started with iseries

Restart type.......... *SYS *SAME, *SYS, *FULL Keylock position........ *SAME *SAME, *NORMAL, *AUTO... Hardware diagnostics...... *MIN *SAME, *MIN, *ALL Compress job tables...... *NONE *SAME, *NONE, *NORMAL... Check job tables........ *ABNORMAL *SAME, *ABNORMAL, *ALL Rebuild product directory... *NONE *SAME, *NONE, *NORMAL... Mail serer framework recoery. *NONE *SAME, *NONE, *ABNORMAL Display status......... *ALL *SAME, *SYS, *NONE... Clear job queues........ *NO *SAME, *YES, *NO Clear output queues...... *NO *SAME, *YES, *NO Clear incomplete joblogs.... *NO *SAME, *YES, *NO Start print writers...... *YES *SAME, *YES, *NO Start to restricted state... *NO *SAME, *YES, *NO +--------------------------------------------------------------------------------+ Specifying IPL Restart Type: When you specify RESTART(*SYS), the system restarts the System Licensed Internal Code and the operating system. Howeer, the system does not completely stop and then restart all the hardware functions. Usually, the IPL time for RESTART(*SYS) is less than the IPL time for RESTART(*FULL). Note: You can also specify the restart type on the Power Down System (PWRDWNSYS) command. Controlling the Leel of Hardware Diagnostics: When you specify HDWDIAG(*MIN), the system performs only a minimum, critical set of hardware diagnostics. The system runs a quick processor diagnostic check that coers approximately 90% of the hardware in approximately 10% of the time that is required for full diagnostics. The system does not perform extended main storage diagnostic or chip-to-chip circuitry tests. When you specify HDWDIAG(*ALL), the system performs complete hardware diagnostics. If you are not experiencing any hardware problems, you can reduce your IPL time by specifying HDWDIAG(*MIN). Howeer, you should periodically perform an IPL with HDWDIAG(*ALL) to ensure that the system checks the status of all components. You should always specify HDWDIAG(*ALL) for the first IPL after any of the following: Installation of new processor cards or modules, because of either hardware serice or a system upgrade. Replacement of the main processor card. Replacement or addition of main storage. You can oerride the HDWDIAG parameter from the control panel on the system unit by doing the following: 1. Select function 02 (Select IPL type/mode). 2. Press Enter. The system panel displays the current setting for the IPL type and mode. 3. Press Enter again to display the IPL speed. (The Enter button toggles between IPL type and IPL speed.) Following are the alues for the IPL speed: F S V Fast (*MIN) IPL (oerrides IPL attribute setting) Slow (*ALL) IPL (oerrides IPL attribute setting) Cancel oerride of current IPL attribute setting 4. Use the increment and decrement function to scroll through and select your desired IPL speed. 5. Press Enter to store the selected alue. 6. Continue the IPL. Compressing the Job Tables: When a job ends on your system, the system deletes its entry from the job table and makes that entry space aailable for another job. If the number of jobs on your system continues to grow, the system must expand the size of the job tables to accommodate new jobs. After you Chapter 8. Managing system operations 55

perform cleanup actiities on your system, you might find that you hae a large number of aailable job entries. (See the Aailable column in the Display Jobs Table example aboe.) If you hae a large number of aailable job table entries, you should set the Compress job tables parameter to *YES for your next IPL. Although the next IPL will be longer because of the compression, subsequent IPLs will be shorter because the system will hae a smaller job table to process. Note: Remember to set the Compress job tables parameter to *NO after the next IPL. Checking the Job Tables: When you specify *ABNORMAL for the Check job tables parameter, the system checks for damage to internal job tables and their associated objects only when your last system shutdown was abnormal. For most installations, this leel of checking is sufficient and will reduce your oerall IPL time. Rebuilding the Product Directory: The system maintains an internal product directory of all installed licensed programs. The system rebuilds this product directory automatically when you install the operating system. For most systems, this directory should be stable when you upgrade to a new release or install new licensed programs. You can reduce your IPL time by instructing the system neer to rebuild the product directory (RBDPRDDIR(*NONE)). Displaying Status: The display status attribute specifies whether the console displays status of OS/400 IPL steps during IPL. The status is not displayed during install IPLs or when the console is not powered on. Automatic Performance Tuning: The performance adjustment (QPFRADJ) system alue controls when the system does automatic performance tuning. You can set up your system to dynamically tune performance, to calculate performance alues during an IPL, or both. When you set up your system to tune performance during an IPL, it calculates performance settings based on information that includes the number of deices and network interfaces and the total amount of main storage. If your system configuration is stable, you can reduce your IPL time by eliminating these calculations (because they will hae the same result each time). For a stable configuration, set the QPFRADJ system alue to 3 (automatic adjustment) or 0 (no adjustment). How Access Paths and Journaling Affect IPL Performance Access paths and journaling can affect your IPL performance in the following ways: When you restart your system after it ends abnormally, the system must rebuild any access paths that were open when the system stopped. This rebuild time can be lengthy. You can reduce this time by journaling access paths, either explicitly by using the Start Journal Access Path (STRJRNAP) command or implicitly by using the System-Managed Access-Path Protection support. The Backup and Recoery Whenbook you perform describes a manual both methods IPL, you forsee protecting the Edit access Rebuild paths of Access from long Paths recoery display. times. You can use this display to specify which access paths the system rebuilds during the IPL ersus after the IPL. Except for critical files, you probably want to delay rebuilding access paths until after your system has completed the IPL. Note: The system rebuilds an access path if the access path was open for update when the system stopped or if the file description specifies MAINT(*DLY) Management of journal receiers can also affect IPL performance. You can set up a journal so that the system manages when to detach the current receier and attach a new one. This simplifies your job of monitoring the size of your journal receiers. Howeer, for each journal that specifies MNGRCV(*SYSTEM), the system performs processing during the IPL. If IPL performance is critical to you, you should consider switching to MNGRCV(*USER) for most of your journals. Similarly, you can set up the system to automatically delete journal receiers that it no longer needs for recoery by specifying DLTRCV(*YES) for the journal. This aoids excessie disk usage for journal 56 iseries: Getting started with iseries

receiers but it also increases your IPL time. Again, if IPL performance is critical, consider switching to DLTRCV(*NO). Howeer, you will need to monitor your system and remoe the journal receiers manually to aoid disk usage problems. Cleaning up your system to improe performance Think of your system like a house or office. It can fill up with clutter and unnecessary objects. This clutter can fill up the disk storage on your system and affect your system performance. The topics that follow proide suggestions for cleaning up your system on a regular basis. Setting Up Automatic Cleanup You can set up your system to run some cleanup functions regularly. Do the following to set up automatic cleanup: 1. Type GO CLEANUP to display the CLEANUP menu. 2. Select option 1 (Change cleanup options). You see the Change Cleanup Options display: +--------------------------------------------------------------------------------+ Change Cleanup Options XXXXXX Type choices below, then press Enter. Allow automatic cleanup............. Y Y=Yes, N=No Time cleanup starts each day.......... 22:00:00 00:00:00-23:59:59, *SCDPWROFF, *NONE Number of days to keep: User messages................. 7 1-366, *KEEP System and workstation messages........ 4 1-366, *KEEP Job logs and other system output....... 7 1-366, *KEEP System journals and system logs........ 30 1-366, *KEEP OfficeVision/400 calendar items........ 30 1-366, *KEEP +--------------------------------------------------------------------------------+ 3. Type Y for the Allow automatic cleanup field. 4. Type alues in the fields on the bottom half of the display (Number of days to keep). The online help information proides more information about what these options do. 5. Set up your system to run automatic cleanup regularly by typing a alue in the Time cleanup starts each day field. Then press Enter. Notes: a. If you want to run the automatic cleanup function immediately, you can select option 3 (Start cleanup immediately) from the CLEANUP menu. If you receie the message Cleanup has already been started, select option 4 (End cleanup). This ends either the scheduled cleanup job or the cleanup job that is already started. Then select option 3 again to run cleanup immediately. b. You can use the Work with Actie Jobs (WRKACTJOB) command to determine when the cleanup jobs hae finished. Their names begin with QCLN. Or you can check the QSYSOPR message queue for the message CPC1E1D (Cleanup has completed). Cleaning Up Obsolete User Profiles Obsolete user profiles take space on your system. In addition, obsolete user profiles probably own objects that you no longer need. To identify obsolete user profiles, do the following: 1. Type GO SECTOOLS and press Enter. You see the Security Tools menu. 2. Select option 4 (Analyze profile actiity). You see the Analyze Profile Actiity (ANZPRFACT) display. 3. For the Number of inactie days, type the number of days that a user can go without signing on before you consider the user profile to be inactie. Chapter 8. Managing system operations 57

4. Press Enter. The system schedules a job to run once a month (at 1 a.m. on the day after you selected this menu option). The job sets the status to *DISABLED for any user profile that has been inactie longer than the number of days that you specified. You receie a listing of the user profiles that the system set to *DISABLED. Notes: a. You can use option 3 (Change actie profile list) from the Security Tools menu to make a user profile exempt from ANZPRFACT processing. b. The Tips and Tools for Securing Your iseries book proides more information about using security tools. When you receie the report of user profiles that the system disabled, do the following: 1. Type WRKUSRPRF *ALL and press Enter. You see the Work with User Enrollment display. Note: If you see the Work with User Profile display, use F21 to change to basic assistance leel. 2. On the display, type 4 (Remoe) in the option column for the user profile that you want to remoe. You see the Remoe User display. 3. Select 2 (Delete or change owner of specific objects owned by this user) and press Enter. You see a list of objects owned by the user. 4. For eery object that you no longer need on the system, type 4 (Delete) in the option column in front of the object. Notes: a. You can select more than one object for deletion at a time. b. To see the type of object, press F11. 5. Press Enter. You see the Confirm Delete of Objects display. 6. If your selections are correct, press Enter. Otherwise, press F12 (Cancel) to return to the selection display. 7. For objects that you want to keep, you need to assign them to a new owner. Type the name of the user profile for the new owner at the top of the display. 8. Type 2 (Change to new owner) in the option column next to the objects and press Enter key. You see the Confirm Change of Owner display. 9. If your selections are correct, press Enter. Otherwise, press F12 (Cancel) to return to the selection display. 10. When you hae handled all the objects that the user profile owned, you see the message (User does not own any objects, press Enter to remoe) 11. Press Enter to remoe the user profile from the system. You see seeral messages while the system remoes the user s records. Then you see the Work with User Enrollment display again with a confirmation message at the bottom of the display. 12. To remoe any spooled files that the user created, do the following: a. Press F9 to display a command line. b. Type WRKSPLF SELECT(user-profile-name)and press Enter. c. On the Work with Spooled Files display, use option 4 (Delete) to delete any spooled files that you no longer need. d. When you hae deleted all the spooled files that are no longer necessary, press F12 (Cancel). Note: Spooled files can remain on the system een when the user profile that created them is no longer on the system. 13. If you hae additional user profiles to remoe, return to step 2. Cleaning Up Obsolete Objects As part of your cleanup effort, you need to encourage users to clean up objects that they no longer need. The example below shows a sample set of instructions that you can distribute to users. Notice that the 58 iseries: Getting started with iseries

example refers to an archies library. You might want to create a library for users to store things that they seldom use. Your operators can periodically sae the library to tape and delete it from your system. Cleanup Instructions - Sample To delete objects that you no longer need, do the following: 1. At a command line, type the following and press Enter: WRKOBJOWN You see the Work with Objects by Owner display. It lists all of the objects that you own. 2. If you are not sure about whether to delete an object, you can use the MOVOBJ (Moe Object) command to moe the object to the following archies library: á áááá. System operators will sae this library to an archies tape before deleting the library from the system. 3. If you are sure that you no longer need an object, use option 4 (Delete) on the Work with Objects by Owner display to remoe the object from the system. (You can delete more than one object at a time.) You will see a confirmation display with the objects that you selected to be deleted. 4. Verify that the correct objects are listed. Then press Enter. 5. To see a list of spooled files that you created, type the following and press Enter: WRKSPLF You see the Work Spooled Files display or the Work with Printer Output display, depending on your assistance leel. 6. From the display, use option 4 to delete spooled files that you no longer need. Cleaning Up Licensed Programs Your system might hae licensed programs that you no longer need. (Perhaps you installed them as a test and decided not to use them.) To remoe licensed programs that you do not plan to use, do the following: 1. To create a list of all the software resources on your system, type the following and press Enter: DSPSFWRSC OUTPUT(*PRINT) 2. Retriee the printout from the printing and mark any licensed programs that you want to delete. Be sure that you do not need a licensed program before you delete it. 3. Type GO LICPGM and press Enter. You see the Work with Licensed Programs menu. 4. To sae a licensed program before you delete it, type 1 (Sae) in the option column in front of the licensed program. Follow the instructions on the prompt displays. Note: If a licensed program does not appear in the list, use the Sae Licensed Program (SAVLICPGM) command to sae it. 5. Press F12 (Cancel) to return to the Work with Licensed Program menu. 6. After you hae saed the licensed programs, select option 12 (Delete licensed programs) from the menu. You see the Delete Licensed Programs display. 7. Type 4 (Delete) in the option column in front of each licensed program that you want to delete. Note:If a licensed program does not appear in the list, use the Delete Licensed Program (DLTLICPGM) command to delete it. 8. Follow the instructions on any prompt displays that you see. Cleaning Up Your Hardware Configuration Your system might hae configuration descriptions for deices that no longer exist on your system. You should remoe these unnecessary descriptions to sae space and improe your IPL performance. Note: On most systems with Logical Partitions, it is common to hae one or more system bus resources that are reported as missing or non-reporting under Hardware Serice Manager. For more information about managing logical partitions, see the Logical partitions topic in the iseries Information Center. Chapter 8. Managing system operations 59

The following list contains actions you should take when cleaning up your hardware configuration: 1. Use the GO SAVE command, menu option 21, to make a complete backup of your system. If you hae logical partitions, make a full backup of each partition. 2. Print a list of your hardware deices Hardware on page 147. 3. Type DSPHDWRSC TYPE(*CMN) and press Enter. You see the Display Communications Resources display. Press F6 to print this information. You may wish to make a hard copy printout of the list. 4. Make a note of any resource that has a status of Not detected. Check to see if the hardware is physically on the system. You might need to check with your hardware serice representatie to determine this. 5. Repeat steps 3 through 4 for the following resource types: *LWS. You see the Display Local Work Station Resources display. *CSA. You see the Display Coupled Resources display. *STG. You see the Display Storage Resources display. *PRC. For resource type *PRC, do not delete the resource CEC01, een if its status is Not detected. 6. Use the Work with Configuration Status (WRKCFGSTS) command to display and delete resources that you do not need. 7. Use the Start System Serice Tools (STRSST) command to start a serice tool. Select the Hardware Serice Manager option to remoe unwanted descriptions. Additional Cleanup Tasks Following are suggested tasks that you can perform regularly (such as monthly) to clean up the disk usage on your system. You may perform these tasks in any sequence. Some of them might require information from your system users. 1. To identify and delete obsolete libraries, do the following: a. Type DSPBCKUPL OUTPUT(*PRINT) and press Enter. b. Retriee the printout from the printer. The printout shows all the libraries on your system. Mark any libraries that you no longer need. c. Before you delete a library, use the Sae Library (SAVLIB) command to sae it to tape. d. To delete the library, use the Delete Library (DLTLIB) command. Note: If a library contains objects that hae dependent objects in another library (such as physical and logical files), you will need to resole the dependency problems before you can delete the library. On option might be to change the sequence in which you delete unneeded libraries. (Delete the library with the logical files first.) 2. To free up unused space in document library objects (DLOs), use the Reorganize Document Library Objects (RGZDLO) command. This command compresses documents and remoes unused space caused by editing changes. If your users frequently edit documents on the system, this command might free up a significant amount of space. 3. If you hae sae files that contain information that you no longer need (for example, because you hae saed it to tape), you can clear the sae files and free up most of the space that they use. Use the Clear Sae File (CLRSAVF) command. 4. If you hae database files with large numbers of deleted records, you can use the Reorganize Physical File Member (RGZPFM) command to free up space that is used for deleted records. Notes: a. You can use the Display File Description (DSPFD) command to determine how many deleted records are in a file. b. If you reorganize a file that is journaled, you must sae the file immediately after you reorganize it. 5. To free up space that is used by deleted spooled files, use the Reclaim Spool Storage (RCLSPLSTG) command. (Your system might do this automatically if you hae set the QRCLSPLSTG system alue.) 60 iseries: Getting started with iseries

6. If you hae message queues that sometimes hae many messages, you can reset the message queues to their original sizes. Use the Clear Message Queue (CLRMSGQ) command to remoe all the messages from the message queue. This resets the size. 7. Sae and delete any journal receiers that you no longer need for recoery. Use the Sae Object (SAVOBJ) command and the Delete Journal Receier (DLTJRNRCV) command. The Journal management for backup and recoeryfor more information about managing journal receiers. 8. If disk usage on your system is high, consider permanently applying fixes to clean up temporary objects and the fix index. Use the Apply PTF (APYPTF) command. Note: You should permanently apply fixes only after you hae alidated the affect of the fixes on your system. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Changing the system password When you install the OS/400 licensed program, the licensed program runs a check to detect system model changes, certain serice conditions, and ownership changes. If the licensed program detects these changes or conditions, you are prompted to enter the system password before the IPL (initial program load) can continue. If no changes or conditions are recognized, the IPL continues without a request for the system password. You must enter the correct system password to complete the IPL on the primary partition. If the system password is not aailable, you or your serice representatie may temporarily bypass entering the system password for a limited time. When the bypass period starts, immediately contact your marketing representatie, who will hae IBM send you the correct system password. To order the system password, ask your marketing representatie to order nonstandard RPQ S40345 if you are in the United States, Asia Pacific, Canada, Latin America, or Japan. If you are in Europe, Middle East, or Asia, request nonstandard RPQ S40346. Changing the system password If you hae just installed new hardware, you may need to change the system password during the first IPL. To do this: 1. Select option 1 (Change the system password) on the Verification of System Password Failed display. 2. The following system information on the Change the System Password display is shown: System serial number System type number System model number System password ersion Processor card serial number If you do not know the system password, use F12 (Cancel) and select option 2 (Bypass the system password) on the Verification of System Password Failed display. 3. Type the password in the blank field and press Enter. To change the system password when your system is operational: 1. Perform an attended IPL. 2. Select option 1 (Change the system password) on the Verification of System Password Failed display. 3. Type the password in the blank field and press Enter. Chapter 8. Managing system operations 61

Bypassing the system password Use the Verification of System Password Failed display to bypass the system password when: You do not know or cannot find the system password. You guess the system password and get a message telling you the password you entered is incorrect. Note: If you type the password incorrectly fie times, you must do the IPL again. To bypass the system password during the first IPL: 1. Select option 2 (Bypass the system password) on the Verification of System Password Failed display. 2. Read the information on the Bypass the System Password display. Remember to contact your marketing representatie immediately to obtain the system password before the bypass period runs out. 3. Press F9 (Bypass) to continue the IPL. When the IPL has finished, you will receie hourly messages that tell how much time is left in the bypass period. When you receie the password, you can enter it by: Doing an attended IPL and selecting option 1 (Change the system password) on the Verification of System Password Failed display. Doing an attended IPL and selecting option 1 (Change the system password) on the Bypass Period has Ended display. Working with subsystems A subsystem is an operating enironment where the system coordinates processing of jobs and resources for the jobs. If you use one of the default subsystem configurations supplied by IBM, all of your subsystems are automatically started when you do an IPL (initial program load). Once your system is successfully powered on, you may need to start additional subsystems to make your system ready to use if: You created a subsystem which is not automatically started, such as a subsystem which runs only at night. You ended all but the controlling subsystem to bring your system to a restricted state to back it up. To start or end subsystems or display subsystem descriptions, use the Work with Subsystem Descriptions (WRKSBSD) command. Starting Subsystems: To start a subsystem on the Work with Subsystem Descriptions display, use option 9 (Start subsystem). A message is displayed telling you the subsystem has started. Ending Subsystems: To end a subsystem, on the Work with Subsystem Descriptions display, use option 10 (End subsystem). On the End Subsystem (ENDSBS) display, in the How to end field, type one of the following: *CNTRLD Jobs are ended in a controlled manner. This allows programs that are running to perform cleanup and finish completely, which may take 600 seconds or more. *IMMED Jobs are ended immediately. This can cause problems if data has been partially updated. Use this option only if you hae attempted a controlled end unsuccessfully. Press Enter. A message is displayed indicating that the system has started to end the subsystem. Another message is sent when the subsystem has ended. 62 iseries: Getting started with iseries

Displaying Subsystem Descriptions: To display a subsystem description, on the Work with Subsystem Descriptions display, use option 5 (Display). The Display Subsystem Description menu is shown on which you can select options that gie you more information about that subsystem. Stopping the system Turning off your system takes careful attention. If you turn off the system without completing the tasks below, you may cause damage to data or cause the system to behae in unpredictable ways. Before you stop the system: Make sure all batch jobs are finished and users are signed off the system 1. Send a message that interrupts all users signed on the system telling them to sign off. a. Type go managesys and press Enter. b. Select option 12 (Work with signed-on users) on the Manage Your System, Users, and Deices (MANAGESYS) menu. Note: if the Work with User Jobs display is shown, you need to switch to basic assistance leel using F21. c. Press F10 (Send message to all) on the Work with Signed-On Users display. d. Type the message in the Message text field on the Send a Message display and press F10 (Send). 2. Wait for the users to sign off. 3. Check to make sure all users hae signed off by pressing F5 (Refresh) on the Work with Signed-On Users display. When eeryone is signed off the system, the display will show only your job. To sign someone off the system, use option 4 (Sign off). Note: if you hae separate interactie subsystems, other than the controlling subsystem, you may want to stop the interactie subsystems once the users hae signed off. This preents them from signing on again before you hae stopped the system. See Working with Subsystems for information on how to end a subsystem. Check the status of any batch jobs that might be affected if the system is powered down 1. On any command line, type go managesys and press Enter. 2. Select option 11 (Work with jobs) on the Manage Your System, Users, and Deices (MANAGESYS) menu. Note: if the Work with User Jobs display is shown, you need to switch to basic assistance leel using F21. 3. Press F14 (Select other jobs) on the Work with Jobs display. 4. Type *all in the User field. 5. Type an N in eery field except the Message waiting, Running, and Running job held fields. The Work with Jobs display is shown again with the batch jobs listed. 6. If any job queues hae jobs waiting to run, press F22 (Work with job queues) to see the Work with Job Queues display. 7. Hold any job queues that hae jobs waiting to run on the Work with Job Queues display. Don t forget to release these job queues when you start the system again. 8. Press F12 (Cancel) to return to the Work with Jobs display. 9. Press F5 (Refresh) eery few minutes until all batch jobs hae completed processing. Check for remoeable media 1. Check to see if there are any tapes in any of the tape units or diskettes in any of the diskette units. 2. Remoe any tapes or diskettes currently in the unit. Chapter 8. Managing system operations 63

Powering off the system immediately You can stop the system by using the Power Down System (PWRDWNSYS) command on any command line when the system is in any mode. Type PWRDWNSYS and press F4 to iew the power down options. You must hae QSYSOPR authority to use the Power Down System (PWRDWNSYS) command. If this command does not work on your system, use the following methods. To power off the system immediately: 1. Type go power on any command line to display the Power on and Off Tasks (POWER) menu. 2. Select option 3 (Power off the system immediately) if you want to keep the power off until the next time the system is scheduled to power on. 3. Press F16 (Confirm) to confirm your choice to power off the system immediately. An immediate power down occurs that causes the subsystems to end all actie jobs. To power off the system and restart immediately: 1. Select option 4 (Power off the system immediately and then power on) on the Power On and Off Tasks (POWER) menu. 2. Press F16 (Confirm) to confirm your choice. The system stops running and then starts again automatically. Note: Don t turn the modem on or off when the system is turned off and is made ready for remote IPL (initial program load). Otherwise, the system may start unexpectedly, although it turns itself off in a few minutes. Important: If you stop the system using the automatic power schedule or one of the options on the Power On and Off Tasks (POWER) menu, the IPL date and time system alue (QIPLDATTIM) is checked and, if necessary, reset to the next scheduled power-on time. This checking does not occur if you power off in another way, so the system may not power on automatically. To force the power schedule to update the QIPLDATTIM system alue, enter the following command on any command line: CHGPWRSCDE DAY(*TODAY) PWRONTIME(*SAME) PWROFFTIME(*SAME) Using the power pushbutton If you cannot use option 3 (Power off the system immediately) or option 4 (Power off the system immediately and then power on) on the Power On and Off Tasks (POWER) menu to stop the system, you can turn the power off using the Power pushbutton to turn off the system when the mode is set to Manual. Attention: Using the power pushbutton to turn off the system may cause results that cannot be predicted in your data files, and the next IPL (initial program load) will take longer to complete. Using the Power pushbutton to turn off the system will power down all partitions. Make sure that there are no tapes in the tape units or diskettes in the diskette units, and that the mode is set to Manual. Do not turn the modem on or off when the system is turned off and is made ready for remote IPL. Otherwise, the system may start unexpectedly, although it turns itself off in a few minutes. To turn the power off using the Power Pushbutton, do the following: 1. Press the Power pushbutton. The Function/Data display blinks with 0? (the international power off symbol). 2. Press the Power pushbutton again. The Power On light blinks as the system is being powered off. When power off is complete, the light goes off. 64 iseries: Getting started with iseries

If the system does not turn the power off within 30 minutes, wait for the System Attention light to come on. When the System Attention light comes on, go to Handling system problems and getting help and follow the steps necessary to sole the problem. System reference codes and primary partitions The figure below shows the system reference codes that are displayed on the control panel, and approximately how long they remain displayed while the IPL (initial program load) is progressing on the primary partition. If you notice a code displayed longer than it should or a code not listed, see handling system problems and getting help. Note: in the diagram, X can be any number 0 through 9 or letter A through F. Chapter 8. Managing system operations 65

After the Sign-on display or command entry display apears, the IPL may still be completing some processing in the background. The IPL is considered complete, but the system may be performing asynchronous clean up. Some functions, such as accessing folders and document library objects (DLOs) may not be aailable until this clean up is complete. 66 iseries: Getting started with iseries

You should allow sufficient time for an IPL to complete before attempting such functions. The time of completion for an IPL depends on such factors as your system model and configuration. System reference codes and secondary partitions The figure below shows the system reference codes that are displayed on the Work with Partition Satus display while the IPL (initial program load) is progressing on secondary partitions. The figure also shows approximately how long the codes remain displayed. If you notice a code displayied longer than it should or a code not listed see handling system problems and getting help. Note: in the diagram, X can be any number 0 through 9 or letter A through F. Chapter 8. Managing system operations 67

After the Sign-on display or command entry display apears, the IPL may still be completing some processing in the background. The IPL is considered complete, but the system may be performing asynchronous clean up. Some functions, such as accessing folders and document library objects (DLOs) may not be aailable until this clean up is complete. 68 iseries: Getting started with iseries

You should allow sufficient time for an IPL to complete before attempting such functions. The time of completion for an IPL depends on such factors as your system model and configuration. What causes an abnormal IPL? An abnormal IPL (initial program load) can be caused by any of the following: Using the End Job Abnormal (ENDJOBABN) command. To see if this command has been used, look for message CPC1124 in the job log. Using option 7 (Start a serice tool), then option 7 (Operator panel function) on the Dedicated Serice Tool (DST) menu. Using the Power pushbutton instead of the PWRDWNSYS command. A power failure occurring before all data is written from main storage to disk. Any B900 xxxx system reference code (where xxxx is any number or letter) during the start of the operating system phase of the IPL. A Power Down System (PWRDWNSYS) command that did not complete, ending with a system reference code of B900 3F10. Any function check in the controlling subsystem causing the system to end. For all actie secondary partitions, any failure of the primary partition. Issuing a PWRDWNSYS command in the primary partition without first powering down secondary partitions. The system going down when database recoery has not completed during the IPL. Note: if the End Job Abnormal (ENDJOBABN) command was issued, message CPI0990 will be in QHST. For all other reasons, message CPI091D will be in QHST stating why the IPL was abnormal. Managing fixes As a system administrator, one of your responsibilities is maintaining your iseries. Part of the maintenance procedure inoles getting, installing, and managing fixes. The topics described below will assist you with these tasks. Note: Before applying fixes to the primary partition on a system with logical partitions, be sure to power down secondary partitions. If you hae a logically partitioned iseries, go to Installing program temporary fixes on a system with logical partitions for more information. Common fix management tasks 1. Ordering fixes Plan to regularly isit IBM s fix page in order to find the fixes are aailable to you, those which affect most users, those which you need before installing new hardware or licensed programs, and those that come bundled together. Then, get the status of the fixes you e ordered. To order fixes electronically, configure electronic customer support. Coer letters Authorized program analysis reports (APARs) Authorized program analysis reports (APARs) on page 76 Cumulatie fix packs Cumulatie fix packs on page 76 Cross-referenced summary lists Cross-referenced summary lists on page 77 Preentatie serice packs (PSPs) Preentatie serice packs (PSPs) on page 77 Fix summary lists Fix summary lists on page 78 Status of fix orders Status of fix orders on page 78 Refer the SNDPTFORD command reference table when ordering fixes. Chapter 8. Managing system operations 69

2. Installing fixes Once you hae selected and ordered the fixes that your system needs, prepare to install them on your system. Be sure to select the appropriate storage area before beginning the installation. Then, once the fixes are installed, erify that the installation was successful, and iew information about the fix. a. Prepare to install fixes b. Choose the appropriate storage area c. Choose the appropriate type of fix Cumulatie fix packs Licensed internal code fixes Licensed program (LP) fixes d. Verify installation e. Display fix status Displaying fix status on page 85 You can also use Management Central to display the status of all fixes on your system. f. Display fix information Displaying fix information on page 85 3. Managing installed fixes After fixes hae been installed on the system, distribute them across multiple systems using Management Central. You can also remoe fixes that are no longer needed on the system. Distributing fixes across multiple systems You can also use Management Central to distribute fixes across multiple systems. Remoing fixes Adanced fix management tasks Fix installation is generally a two-step process: load and apply. The easiest way to install fixes is to follow the steps aboe. If you follow these instructions, the fixes are loaded and applied for you automatically. Occasionally, you may need to install fixes by loading them first and applying them later. The following procedures gie you information on how to load and apply fixes under special circumstances. If you do not need to use the load and apply steps separately, follow the steps aboe to install your fixes. Note: The methods described in this section are not recommended ways to install fixes. Using these methods may cause the following error conditions: Fix is not applied during an IPL (initial program load) due to missing prerequisites. Required distribution requirements are missing after the fix apply. Therefore, it is recommended that you use the steps aboe to install all your fixes. Adanced fix management tasks include: Loading fixes Applying fixes Additional information on this topic can be found in these sources: IBM technical support Administering Client Access Express serice packs Ordering indiidual fixes and coer letters Coer letters are used to explain the contents of a fix, what problem the fix resoles, what special instructions are associated with the fix, and what prerequisites or corequisites must also be installed on your system in order for the fix to function properly. See a sample of a coer letter, and learn more about the information it contains. 70 iseries: Getting started with iseries

This topic explains how to order Ordering coer letters, copy Copying a profile on page 34, display and print Displaying and printing fix coer letters on page 72 coer letters. Ordering coer letters You can order up to 20 fixes at a time. To order indiidual fixes and coer letters electronically, complete the following steps: 1. On any command line, type SNDPTFORD nnnnnnn where nnnnnnn is the number of the indiidual fix you want to order. 2. Press Enter. When you receie fixes electronically on your serice support communications line, they are placed in a sae file in library QGPL. In most cases, the sae file name is the fix identifier prefixed with a Q. For example, the sae file for fix identifier SFnnnnn is QSFnnnnn. Keep the following points in mind: If the fix files are too large to be deliered electronically, they are deliered on CD-ROM or tape. When you order a fix that has been replaced (superseded) with another fix, you receie the ordered fix, not the replacement fix. To identify fixes that hae been replaced (superseded), consult the fix summary list. When you order a fix for a product that is installed on your system, you will receie a fix package that contains the ordered fix and its requisites. If you order a fix for a product that is not installed on your system, you will receie only the fix that you ordered. If you use the Display Program Temprorary fix (DSPPTF) command on the fix you just ordered, you will receie the following message: PTF 5769xxx-SFxxxxx is not found. This message means that the fix is for a release of the product that is not installed on your system. Contact your serice proider for the correct fix number. Ordering a fix coer letter only: To order a fix coer letter without ordering the fix, complete these steps: 1. On any command line, type: SNDPTFORD nnnnnnn PTFPART(*CVRLTR) 2. Press Enter. Specifying media for shipping a fix: You can specify the media for shipping fixes by doing the following: 1. On any command line, type WRKCNTINF. 2. Press Enter. The Work with Support Contact Information display appears. 3. Select Option 2. 4. Press Enter. The Work with Local Serice Information display appears. 5. Select Option 2. 6. Press Enter. The Change serice contact information display appears. 7. Page down to the next display. 8. Specify the fix medium type by entering the corresponding number. 9. Press Enter. Copying fix coer letters from CD-ROM or Tape Fixes on CD-ROM or tape are sent by mail. A shipping information letter is included with the CD-ROM or tape. Each fix on the CD-ROM or tape may also hae a coer letter. Copy the coer letter into file QAPZCOVER in library QGPL. Make sure that the product that you are copying the coer letter for is installed. Copying coer letters from CD-ROM: To copy a coer letter from CD-ROM, do the following: 1. On any command line, type LODPTF LICPGM(XXXXXXX) SELECT(zzzzzzz) DEV(YYYYY) COVER(*ONLY) PATHID(*FIRST) Chapter 8. Managing system operations 71

where XXXXXXX is the licensed program number found in the shipping information letter, YYYYY is the CD-ROM unit ID (typically named OPT01 or OPT02), and zzzzzzz is the fix ID for the coer letter you want. 2. Repeat step 1 for each licensed program fix coer letter on the CD-ROM. If you are using this function to simultaneously load fixes and copy fix coer letters, change COVER(*ONLY) to COVER(*YES). This loads the fix and copies the coer letter onto the system. Copying coer letters from tape If the tape contains multiple fixes, perform these steps: 1. On any command line, type LODPTF LICPGM(XXXXXXX) DEV(YYYYY) COVER(*ONLY) ENDOPT(*LEAVE) where XXXXXXX is the licensed program number found in the shipping information letter, and YYYYY is the tape unit ID (typically named TAP01 or TAP02). 2. Repeat step 1 for each licensed program fix coer letter on the tape except the last licensed program fix coer letter. 3. For the last fix coer letter on the tape, change ENDOPT(*LEAVE) to ENDOPT(*REWIND). If you are using this function to simulatneously load fixes and copy fix coer letters, change COVER(*ONLY) to COVER(*YES). This loads the fix and copies the coer letter onto the system. If there are multiple fix files on the tape and the *LEAVE option is not specified, you must then specify the fix sequence number for the Sequence number (SEQNBR) parameter. Your fix sequence number is in the coer letter that comes with your tape. For each fix package, you need to specify the correct sequence number. If the tape contains only one fix: On any command line, type LODPTF LICPGM(XXXXXXX) DEV(TAPYY) COVER(*ONLY), where XXXXXXX is the licensed program number, and YY is the tape deice ID. Displaying and printing fix coer letters There are two ways to display or print fix coer letters. You should use the first method in most cases. If you are unable to display or print a coer letter using the first method, use the second method. This may be necessary, for example, when you want to print or display a coer letter for a product that has not been installed or supported on your system. Method 1 1. Enter the Display Program Temporary Fix (DSPPTF) command and press F4 (Prompt). This command only works for products that are installed or supported. 2. Specify the product, fix identifier, and release for the appropriate parameters on the Display Program Temporary Fix (DSPPTF) display. 3. Specify *YES for the Coer letter only (COVERONLY) parameter and press Enter to display the coer letter. You can also print a fix coer letter using the following command: DSPPTF LICPGM(xxxxxxx) SELECT(yyyyyyy) COVERONLY(*YES) OUTPUT(*PRINT), where xxxxxxx is the licensed program number, and yyyyyyy is the fix identification number. For example, if you wanted to print the Fix Summary List, type the following command on any command line: DSPPTF LICPGM(5769SS1) SELECT(SF97072) COVERONLY(*YES) OUTPUT(*PRINT). Your output will be placed in the output queue that is associated with your job. The output is stored under the file name QSYSPRT. Method 2 Printing the coer letter: 72 iseries: Getting started with iseries

1. On any command line, type cpyf fromfile(qgpl/qapzcover) tofile(qgpl/qprint) frommbr(qnnnnnnnxx), where Qnnnnnnnxx is the name of the file member in which the fix coer letter is stored. Remember, the member containing the coer letter is usually named Qnnnnnnnxx. The Q begins the member name. The nnnnnnn is either the associated fix number or a time stamp. The xx, if present, is the last two digits of the language code for the coer letter. For coer letters in English, the last two digits of the language code do not appear and the member name is the same as the corresponding fix number preceded by a Q. For example, if the related fix is SF12345 for English, the member name is QSF12345 (there is no xx. If the related fix is SF12345 for Dutch, the member name is QSF1234523 (the Dutch language code is 2923, so xx is 23 in this case). This is also the case when you are displaying a coer letter. 2. Press Enter. The file member is copied to the QPRINT print file. 3. On the Operational Assistant menu, select option 1 (Work with printer output). The Work with Printer Output display is shown. 4. Look in the Printer/Output column for the file name QPRINT. This is the file that contains the coer letter. 5. If the file is held, you can print the coer letter by selecting option 6 (Release). Displaying the coer letter: 1. On any command line, type dsppfm (the Display Physical File Member command). 2. Press F4 (Prompt). The Display Physical File Member display is shown. 3. Specify the member name in file QAPZCOVER in library QGPL. Remember, the member containing the coer letter is usually named Qnnnnnnnxx. The Q begins the member name. The nnnnnnn is either the associated fix number or a time stamp. The xx, if present, is the last two digits of the language code for the coer letter. For coer letters in English, the last two digits of the language code do not appear and the member name is the same as the corresponding fix number preceded by a Q. For example, if the related fix is SF12345 for English, the member name is QSF12345 (there is no xx. If the related fix is SF12345 for Dutch, the member name is QSF1234523 (the Dutch language code is 2923, so xx is 23 in this case). This is also the case when you are displaying a coer letter. 4. Press Enter to see the coer letter. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Sample coer letter and description of fields The figure below shows the contents of a typical fix coer letter. A description (See 75) of each field follows. 5769SS1 5050 0000 SI04400 2924 R02M00 XPF-DSPOBJD-CPF9999-DSPOBJD FUNCTION CHECKS WITH LIN(*) PARM PTF/FIX # SIxxxxx - OS/400 - BASE SYSTEM LICENSEDPROGRAM: 5769SS1 SYSTEM LEVEL RELEASE RECOMPILE LIBRARY MRI APAR MIN/MAX FEATURE FIXED AS/400 NONE VxRxMx N QSYS 2937 SExxxxx - Chapter 8. Managing system operations 73

PRE/COREQUISITE PTF/FIX LIST - REQ LICENSEDPTF/FIX LEVEL TYPE PROGRAM REL NUMBER MIN/MAX OPTION PRE 5769SS1 xxx SIxxxxx NONE 0000 PRE 5769999 xxx MFxxxxx NONE 0000 CO 5769SS1 xxx SIxxxxx NONE 0000 DIST 5769SS1 xxx SIxxxxx NONE 0000 DIST 5769SS1 xxx SExxxxx NONE 0000 (SEE MRI PTF/FIX LIST BELOW) MRI PTF/FIX LIST APAR SExxxxx AFFECTS THESE LANGUAGES. IF YOU HAVE ANY OF THESE LANGUAGES INSTALLED, INSTALL THE CO-REQUISITE MRI PTF THAT CORRESPONDS TO THE LANGUAGE(S) INSTALLEDON YOUR SYSTEM. - FEATURE LICENSEDPTF/FIX CODE LANGUAGE PROGRAM NUMBER - - - 2924 ENGLISH UPPER/LOWER CASE 5769SS1 SIxxxxx 2938 ENGLISH UPPERCASE (DBCS) 5769SS1 SIxxxxx 2950 ENGLISH UPPERCASE 5769SS1 SIxxxxx 2984 ENGLISH U/L (DBCS) 5769SS1 SIxxxxx DESCRIPTION OF PROBLEM FIXED FOR APAR SExxxxx: USERS CANNOT RECEIVE PTFS FOR PRODUCTS NOT INSTALLED ON THEIR SYSTEMS. CORRECTION FOR APAR SExxxxx: ELECTRONIC CUSTOMER SUPPORT PROGRAM CODE WILL BE CHANGED SO THAT PTFS WILL BE REQUESTED EVEN IF THE CORRESPONDING PRODUCTS ARE NOT INSTALLED ON THE REQUESTING SYSTEM. CIRCUMVENTION FOR APAR SExxxxx: - NONE. ACTIVATION INSTRUCTIONS: NONE. SPECIAL INSTRUCTIONS: NONE. 74 iseries: Getting started with iseries

DEFAULT INSTRUCTIONS: THIS PTF MUST BE APPLIEDAT IPL TIME. SUPERSEDES PTF/FIX NO(S).áá APAR TITLE LINE áá SIxxxxxááááááááá OSP-RSTS36F-MSGCPA2C6C RESTORING ALL FILES FROM SYSTEM/34 Description of fields: Field name PTF/Fix # Licensed Program System Leel Min/Max Release Recompile Library MRI Feature APAR Fixed Prerequisite PTF/Fix List Corequisite PTF/Fix List Distribution Requisite PTF/Fix List MRI Requisite PTF/Fix List Description of Problem Fixed Correction Circumention Actiation Instructions Special Instructions Description The alphanumeric identifier for the fix or Licensed Internal Code fix. The alphanumeric identifier for the licensed program. The IBM system for which this fix is alid. The lowest and highest leel of the product that this fix can be installed on. The ersion, release, and modification number of the system for which this fix is alid. The format for ersion, release, and modification number is VxRxMx where x is a number between 0 and 9. Y (Yes) means a recompile of affected objects is necessary after this fix is applied. N (No) means a recompile is not necessary after this fix is applied. The library the fix is intended for. The numeric identifier for the language feature of the language sensitie object affected by the fix. None means language sensitie object is not affected. The number of the authorized program analysis report (APAR) for which this fix was created. The information about the fixes that must be applied on the system before this fix can be applied. The information about other fixes that must be installed along with this fix. The system will check to ensure all corequisite fixes are applied together. The information about other fixes that must be installed at the same time as this fix. The system will not erify distribution requisites are applied together. The information about other fixes that must be installed at the same time as this fixes. Select the fixes that correspond to the languages that you hae installed on your system. A brief description of the problem this fix fixes. A brief description of what has been done to correct the problem. A description, if applicable, of how to work around the problem and continue your operation without applying the fix. Actions you must perform in order to actiate fixes without an IPL (initial program load) of the system. Actiation instructions are limited to actions that would normally be accomplished by an IPL of the system, such as stopping and restarting a subsystem, arying deices offline and back online, etc. Any special information pertaining to this fix. Chapter 8. Managing system operations 75

Field name Default Instructions Supersedes PTF/Fix No(s) APAR Title Line Description Tells when the fix can be applied; either at the next IPL (delayed) or immediately. The numbers of the fixes that this fix replaces or supersedes. The title of the authorized program analysis report (APAR) for the superseded fix. Ordering fixes There are many different kinds of fixes that can be ordered: Authorized program analysis reports (APARs) Authorized program analysis reports (APARs) Cumulatie fix packs Cumulatie fix packs Cross-referenced summary lists Cross-referenced summary lists on page 77 Preentatie serice packs (PSPs) Preentatie serice packs (PSPs) on page 77 Fix summary lists Fix summary lists on page 78 Status of fix orders Status of fix orders on page 78 Authorized program analysis reports (APARs) Information APARs are created when there is a need to proide worldwide access to information. Typically, information APARs are created to describe perasie user errors, proide recoery actions for non-defect situations, or explain system operation. To print an Information APAR, do the following: 1. On any command line type DSPPTF LICPGM(INFOAS4) SELECT(xxxxxxx) OUTPUT(*PRINT), where xxxxxx is the name of the information APAR you are printing. 2. Press Enter. Your printer output will be placed in the output queue that is associated with your job. 3. On the Operational Assistant menu, select option 1 (Work with Printer Output). The Work with Printer Output display is shown. 4. Look in the Printer/Output column for the name of your spooled file or printer output. This file contains the information APAR. 5. If the file is held, you can print the information APAR by selecting option 6 (Release). Cumulatie fix packs To order a cumulatie fix package electronically: 1. Identify your licensed program release leel: a. On any command line, type GO LICPGM. b. Press Enter. c. Select option 10 (Display installed licensed programs) on the Work with Licensed Programs display. d. Press F11. The current ersion, release, and modification leel is shown in the Installed Release column where V is the ersion, R is the release, and M is the modification leel. 2. Type SNDPTFORD SF99VRM, where VRM is the ersion, release, and modification leel you found in step 1. For example, for Version 5 Release 1 Modification 0, type SNDPTFORD SF99510. 3. Verify the shipping information on the Verify Contact Information display. If any of the information is incorrect, change it and press Enter. 4. Select option 1 (Send serice request now) on the Select Reporting Option display. This places the fix order. 76 iseries: Getting started with iseries

Cross-referenced summary lists The fix cross-reference summary list itemizes fixes from an earlier release that are included in the current release. Use this list to make sure you order any fixes for the new release that you had at the preious release, but are not included in the list. These fixes will not hae the same number, but they correct the same problem. To order this list electronically, select the ersion and release you are moing from and use the corresponding command. See SNDPTFORD command table for the fix cross-reference summary. Preentatie serice packs (PSPs) Preentie serice planning (PSP) information is a collection of information that is used when installing a licensed program, cumulatie fix package, or hardware. PSP information should be reiewed before installing a licensed program, a cumulatie fix package, or hardware. You should order preentie serice planning information and reiew the recommended High Impact Perasie (HIPER) fixes periodically. HIPER fixes fix seere problems such as: your system may crash or hang and requires an IPL (initial program load) to recoer, your system may be stuck in a looping condition, your system s data integrity may be threatened, your system may experience a seere performance degradation, or the problem inoles usability of a product s major function. If any of the fixes are needed for your system, you should order and install them. To order PSP information, use the following commands: For Licensed programs: SNDPTFORD SF98rm For Licensed Internal Code: SNDPTFORD MF98rm where rm is ersion, release, and modification leel. For Version 5 Release 1 Modification 0, use 510. To print preentie serice planning (PSP) information, use the instructions for printing and displaying fix coer letters Displaying and printing fix coer letters on page 72. The PSP information is placed in QAPZCOVER when it is sent to you. Preentie serice planning information is aailable for: Licensed programs installation Licensed Internal Code System equipment Cumulatie fix packages PTFs (fixes) in error (PE) High impact or perasie (HIPER) problems These PSPs can be ordered through your software serice proider or by using electronic customer support. Preentie serice planning information includes the following: Installation information: Information concerning upgrade and new installation, including information about cumulatie fix package installation. General information: Hints or tips for working with fix packages or products. Fixes in error:information about all fixes found to hae a problem, the users that will be affected by the problem, and recommendations on how to aoid the problem. Serice recommendations: Detailed information about critical fixes you need to install. You should get this information before you install or upgrade system equipment and licensed programs. This ensures that you hae all the latest information that is applicable for the new program or cumulatie package. Chapter 8. Managing system operations 77

Carefully reiew the following sections of the PSP before installing the cumulatie package: Serice Recommendations: This section lists those High Impact PERasie (HIPER) problems that hae been discoered in the base code since shipment and not included in this cumulatie package. As before, these recommendations should be reiewed based on your system s setup and configuration. PTFs (fixes) in Error (PE): This section contains a list of fixes that are included on this cumulatie package that, since shipment, hae been found to be defectie. You hae two options: install the cumulatie package without applying the fixes in error, or you can install the correctie fixes for the fixes in error, if aailable. This section lists the defectie fix, the users affected, the reason the fix is defectie, and the recommended action to take. The PSP information also contains a list of fix identifiers to order PSP information for Licensed Internal Code and system equipment, licensed programs installation, and PSPs for older cumulatie packages. Fix summary lists A fix summary list is a coer letter that contains a list of fixes that affect most system users. Use the fix summary list to identify fixes you may want to order. The fix summary list also identifies the current fix package and what package each fix was included in. To order the fix summary list, use the following command: SNDPTFORD SF97rm, where rm is ersion, release, and modification leel. For Version 5 Release 1 Modification 0, use 510. Status of fix orders To find the status of fix orders: 1. On any command line, type WRKPRB. Press Enter. 2. All fixes that you requested and hae been sent (either electronically or through the mail) are identified in the Problem Description column as Fix Request on the Work with Problems display. 3. Use option 5 (Display details) for the problem with the problem description Fix Request. 4. Press F9 (Display PTFs) on the Display Problem Details display. All fixes related to the problem you selected are shown on the Display PTF information display. This includes the fixes you ordered, in addition to any others requested that are not already on your system. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Using the SNDPTFORD command to order fixes The table below shows how to use the Send Fix Order (SNDPTFORD) command to order fixes and fix information. You may want to print and use this table as a reference when you order fixes. To process your PTF order in batch, use the Submit Job (SBMJOB) command. Getting fixes and fix information Fix Information Specific fixes and coer letters Fix coer letter only Command SNDPTFORD nnnnnnn(1) SNDPTFORD nnnnnnn(1) PTFPART(*CVRLTR) 78 iseries: Getting started with iseries

Fix cross-reference summary list VRM320 to VRM450 VRM420 to VRM450 VRM430 to VRM450 VRM440 to VRM450 SNDPTFORD SF97025 SNDPTFORD SF97097 SNDPTFORD SF97066 SNDPTFORD SF97035 Cumulatie fix packages SNDPTFORD SF99rm(2) PSP information for licensed programs SF98rm(2) PSP information for Licensed Internal Code MF98rm(2) PTF summary list SF97rm(2) Notes: (1) nnnnnnn is the fix identifier. You can order up to 20 fixes at a time. (2) is the ersion, r is the release, and m is the modification leel of the system. For Version 5 Release 1 Modification 0, type 510. Preparing to install fixes Before you begin to install fixes, complete these tasks: Hae a current backup of your user data, operating system and licensed programs. If you hae backed up the operating system and licensed programs since the last time you applied fixes, that backup is acceptable. Hae all users sign off the system. If you fail to hae all users sign off the system and someone else is doing a fix operation, the cumulatie fix package will not load. Before applying a fix to the primary partition of a system with logical partitions, power down the secondary partitions. Be sure you hae security officer (*SECOFR) user class. You need it to do the following steps. Note: get more information before you install fixes on a logically partitioned iseries. Choosing a storage area before applying a fix The system maintains two copies of all Licensed Internal Code on the system. One copy is considered the permanent copy and is stored on system storage area A. The other copy is considered the temporary copy and is stored on system storage area B. When the system is running, it uses the copy that was selected before the last IPL (initial program load). System storage areas A and B A B in the Data display on the front panel of the system unit indicates that the next system IPL will be made from the B or temporary storage area. The B storage area contains any Licensed Internal Code fixes that hae been temporarily or permanently applied. Temporarily applied Licensed Internal Code fixes can be applied permanently (copied to the A storage area) or be permanently remoed. For the system to use the latest Licensed Internal Code fixes that are temporarily applied, you must be using the B storage area. The B storage area is what you normally use. Select the A storage area if the IPL to the B storage area fails because of a temporarily applied Licensed Internal Code fix. Selecting the A or B storage area: You can change the storage area on the command line or the control panel: On the command line, type PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(X), where X is the storage area you want to select. On the control panel: 1. For systems with a mode button, set the system to the Manual mode. For systems without a mode button, start at step 2. Chapter 8. Managing system operations 79

2. Press the Increment/Decrement buttons until 02 is displayed in the Function/Data display on the control panel. 3. Press the Enter pushbutton on the control panel. 4. For systems with a mode button, press the Increment/Decrement buttons until the character that represents the storage area you want to use for your IPL source (A or B) appears in the Function/Data display. For systems without a mode button, press the Increment/Decrement buttons until you see Normal (N) and the character (A or B) for the IPL storage area you want to appear in the Function/Data display. 5. Press the Enter pushbutton on the control panel to sae the IPL settings. 6. For systems with a mode button, set the mode to Normal. 7. Power off the system using option 4 (Power off the system and immediately power on) on the Power On and Off Tasks (POWER) menu. Wait for the system to power down and automatically start an IPL. You see the Sign On display when the IPL is complete. The storage area is now changed. Installing a cumulatie fix pack If your system changes to a new release, order and install the current cumulatie fix package to keep your system at the most current fix leel. To install cumulatie fix packages: 1. Read the fix shipping information letter thoroughly and follow the instructions contained in it. You should be running on the B storage area (B side) when installing the cumulatie fix packages. 2. Select the storage area if you hae not already done so. Displaying or printing the cumulatie fix package summary To print or display the summary of fixes contained in a cumulatie fix package on CD-ROM: 1. Load the cumulatie fix package CD-ROM in the CD-ROM drie. 2. On any command line, type LODPTF LICPGM(5769999) DEV(OPTYY) SELECT(*ALL) PATHID(*FIRST) COVER(*ONLY), where YY is the unit ID for the CD-ROM drie in which you loaded the fix CD-ROM. For information about printing the cumulatie fix package summary, see Displaying and printing fix coer letters Displaying and printing fix coer letters on page 72. A copy of the fix summary is put into file QAPZCOVER in Library QGPL. To print or display the summary of fixes contained in a cumulatie fix package on tape: 1. Load the cumulatie fix package tape in the tape unit. 2. On any command line, type CPYFRMTAP FROMFILE(QTAPE) TOFILE(QPRINT) FROMSEQNBR(3) FROMDEV(TAPYY) FROMREELS(*SL), where YY is the tape unit ID (for example, TAP01) in which you loaded the fix tape. A copy of the fix summary is put into a system output queue from which you can print or display the fix summary information. Installing High-Impact Perasie (HIPER) fixes from a cumulatie fix package: To install both high-impact perasie (HIPER) fixes and HIPER Licensed Internal Code fixes, follow the fix installation instructions in the shipping information letter. When you are on the Install Options for Program Temporary Fix display, specify 2 for the PTF type field. To install only HIPER Licensed Internal Code fixes, specify 3 for the PTF type field. Verifying installation of the cumulatie fix package: 80 iseries: Getting started with iseries

After completing the last IPL (initial program load) in the installation instructions, to erify that the fix package was properly installed: 1. On any command line, type go licpgm. 2. Press Enter. 3. Select option 50 (Display log for messages) on the Work with Licensed Programs display. 4. Fill in the start date and start time on the Display Install History display. 5. Press Enter. 6. On the Display History Log Contents display, if the cumulatie fix package was installed successfully, you see messages like the following: Licensed program or PTF installation process started. Loading of PTFs completed successfully. Marking of PTFs for delayed application started. Marking of PTFs for delayed application completed successfully. Apply PTF started. Applying of PTFs for product 5769xxx completed successfully. Applying of PTFs for product 5769xxx completed successfully. Applying of PTFs for product 5769xxx completed successfully.... Applying of PTFs completed. If the cumulatie fix package was not installed successfully, you see error messages like the following: Licensed program or PTF installation process started. Loading of PTFs failed. Marking of PTFs for delayed application started. Marking of PTFs for delayed application failed. Apply PTF started.... Applying of PTFs failed for product 5769xxx.... Applying PTFs failed. Displaying the cumulatie fix package leel of your system: The cumulatie fix package leel of your system refers to the latest cumulatie fix package installed on your system. To determine the cumulatie fix package leel of your system: 1. On any command line, type DSPPTF LICPGM(5769SS1) 2. The PTF ID column on the Display PTF Status display lists the identifiers for all of the cumulatie fix packages installed on your system. Cumulatie fix package identifiers start with the letter T. If you are using Version 4 Release 3 Modification 0, and you hae PTF TC94178 installed on your system, your cumulatie fix package leel is C4178430 (430 is added to the end of the package ID to indicate Version 4 Release 3 Modification Leel 0). The last four digits of the cumulatie package ID indicate the release date of the package, using the Julian calendar. The latest cumulatie fix package is the one where the last four digits are the highest. Note: Fix IDs that start with the letters TC indicate that the entire CD-ROM or tape has been applied. Fix IDs that start with the letters TA indicate that the HIPER fixes and HIPER Licensed Internal Code Chapter 8. Managing system operations 81

fixes hae been applied. Fix IDs that start with the letters TL indicate that the HIPER Licensed Internal Code fixes hae been applied. To find the leel of Licensed Internal Code fixes on your system, enter DSPPTF 5769999. Omitting indiidual fixes from a cumulatie package: The omit function allows you to specify indiidual fixes that you do not want to install from the cumulatie package. To use the omit function, do the following: 1. On the Install Options for Program Temporary Fixes display, specify Y for the Other options field, and press Enter. The Other Install Options display is shown. 2. Specify Y for the Omit PTFs field, and a alue for the Apply Type field, and then press Enter. The Omit Program Temporary Fixes display is shown. 3. In the Opt Column, type a 1 next to each product and release for which you want to omit specific fixes from being installed, and press Enter. The PTFs to Omit display is shown for each product that was selected on the preious display. This display shows the list of fixes that are to be omitted from being loaded for the specified product and release. 4. To add fixes to the list on the PTFs to Omit display, type a 1 on the first line of the Opt column and specify the fix ID in the PTF ID column. Press Enter. 5. Repeat step 4 until you hae specified all of the fixes you want to omit from being installed for the product and release. Press Enter again and repeat the procedure for the next product and release you selected on the Omit Program Temporary Fixes display. When you are done with the last product and release you hae selected, the Omit Program Temporary Fixes display is shown again. The > symbol next to the product and release indicates that you hae specified fixes to be omitted. Press Enter. The Confirm to Omit PTFs panel is shown. 6. The Confirm to Omit PTFs panel lists each of the fixes that hae been specified to be omitted from being installed. If the list is correct, press Enter. Normal fix installation process continues from this point. Remember, you can install fixes using the power on and power off schedules. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Installing licensed internal code fixes There are two types of Licensed Internal Code fixes: Delayed and immediate. Delayed Licensed Internal Code fixes can only be applied immediately while running on the A side, or can be applied delayed while running on the B side. Immediate Licensed Internal Code fixes can be applied immediately while running on the A or B storage area. No IPL (initial program load) is required for applying immediate fixes. You must be running on the B storage area to use any temporarily applied Licensed Internal Code fixes. Temporarily applied Licensed Internal Code fixes can be applied permanently (copied to the A storage area). To permanently apply delayed or immediate Licensed Internal Code fixes, you must be running from the B storage area. These fixes can be permanently applied without an IPL. Licensed Internal Code fixes to be applied on the next IPL while running on the A side must be applied immediately. More information can be found in Applying fixes (in adanced fix management tasks). 82 iseries: Getting started with iseries

Installing Licensed Internal Code Fixes: For immediate Licensed Internal Code fixes that will be applied immediately without an IPL, see the instructions in Applying Licensed Internal Code fixes without an IPL Temporarily or permanently installing immediate licensed program or OS/400 fixes without an IPL on page 97. For delayed Licensed Internal Code fixes and immediate Licensed Internal Code fixes that will be applied during an IPL, use the following instructions: 1. Print and read each coer letter Displaying and printing fix coer letters on page 72. 2. If there are any pre-installation special instructions in any of the coer letters, follow those instructions first. NOTE: Do not cancel any of the following steps once they are started. Allow each step to complete normally. If shipping information letters are included with the fix CD-ROM or tape you receied, follow the instructions in the letters to install the fixs. If the shipping information letters are not included with the CD-ROM or tape, continue with the following instructions. 3. Determine the storage area you are currently using: a. On any command line, type dspptf 5769999 and press Enter. b. On the Display PTF Status display, the storage area is identified in the IPL source field. ##MACH#A is the A storage area and ##MACH#B is the B storage area. c. If you are not running on the B storage area, type the following command on any command line and press Enter: PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B) 4. On any command line, type go ptf and press Enter. 5. Select option 8 (Install program temporary fix package) on the Program Temporary Fix (PTF) display. The Install Options for Program Temporary Fixes display is shown. 6. Enter the appropriate alue in the Deice field from the list below: If the fix was deliered electronically, type *serice. If the PTF was deliered on a tape, type tapyy, where yy is the name of the tape unit (for example, tap01) where you loaded the fix tape. If the fix was deliered on CD-ROM, type optyy, where yy is the name of the CD-ROM drie unit (for example, opt01) where you loaded the fix CD-ROM. If you do not want to install certain fixes, you can omit those fixess by using the procedure called Omitting indiidual fixes from a cumulatie package (See 82). If you hae additional fixes to install at this time, type an N (No) in the Automatic IPL field and install the additional fixes. If you do not hae additional fixes to install at this time, type a Y (Yes) in the Automatic IPL field. Although it will take longer than preious releases to set Licensed Internal Code fixes for apply on the next IPL, the next IPL will take much less time. 7. Press Enter. After the IPL has finished, erify that the fixes are installed. If there are any post-installation special instructions in the coer letter, follow those instructions at this time. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Installing licensed program (LP) fixes For immediate OS/400 fixes that will be applied immediately without an IPL (initial program load), see the instructions in Applying Immediate Licensed Program or OS/400 PTFs Temporarily or Permanently Without an IPL. Chapter 8. Managing system operations 83

For licensed program fixes, delayed OS/400 fixes, or Immediate OS/400 fixes that will be applied during an IPL, use the following instructions: 1. Print and read each coer letter Displaying and printing fix coer letters on page 72. 2. If there are any pre-installation special instructions in any of the coer letters, follow those instructions first. Note: Do not cancel any of the following steps once they are started. Allow each step to complete normally. 3. On any command line, type go ptf and press Enter. If you do not want to install certain fixes, you can omit them by using the procedure called Omitting indiidual fixes from a cumulatie package (See 82). If you hae additional fixes to install at this time, type an N (No) in the Automatic IPL field and install the additional fixes. If you do not hae additional fixes to install at this time, type a Y (Yes) in the Automatic IPL field. 4. Select option 8 (Install program temporary fix package) on the Program Temporary Fix (PTF) display. 5. If the fix was deliered electronically, type *serice in the Deice field. If the fix was deliered on a tape, type tapyy, where yy is the name of the tape unit (for example, tap01) where you loaded the fix tape. If the fix was deliered on CD-ROM, type optyy, where yy is the name of the CD-ROM drie unit (for example, opt01) where you loaded the fix CD-ROM. Note: Fixes may not be applied successfully during an IPL if the IPL is abnormal. 6. Press Enter. After the IPL has finished, erify that the fixes are installed. If there are any post-installation special instructions in the coer letter, follow those instructions at this time. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Verifying the fix installation To erify that your Licensed Internal Code and licensed program PTFs hae been installed correctly, do the following: 1. On any command line, type GO LICPGM and press Enter. The Work with Licensed Programs display appears. 2. Select Option 50 (Display log for messages). The Display Install History display appears. 3. Fill in the start date and start time on the Display Install History display and press Enter. The messages about fix installation are shown. When fixes do not install To determine the cause of the failure, do the following: 1. Place the cursor on the preious message and press F10 (Display all). If F10 (Display all) is not aailable, switch to intermediate assistance leel using F21 (Select assistance leel) and try again. 2. A new message is shown that helps you find out what errors occurred. Use the Help key to display additional message information. You can also look at the SCPF job log for errors. To check this job log, do the following: 1. On any command line, type WRKSPLF SELECT(QSYS *ALL *ALL SCPF) ASTLVL(*INTERMED) 2. The Work with All Spooled file display appears. Find the last spooled file named QPJOBLOG. Use Option 5 (Display) to see if any errors are listed. OS/400 fix and licensed program actiity does not occur during an unattended IPL (initial program load) that immediately follows an abnormal system end. 84 iseries: Getting started with iseries

If an abnormal IPL occurs, and Licensed Internal Code fixes were ready to be applied, the Licensed Internal Code fixes will now be applied. To apply the fixes after an abnormal IPL to storage area B, type: PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B). Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Displaying fix status To determine the status of the fixes for products that are installed and supported on your system: 1. Enter the Display PTF (DSPPTF) command and press F4 (Prompt). 2. Specify the licensed program number and fix identifier for the product (LICPGM) parameter and for the fix numbers to select (SELECT) parameter. If you want to see the status for all the products on the system, specify *ALL for both parameters and press Enter until all the licensed programs are displayed. 3. The Display Program Temporary Fix display shows the action that will be taken for a fix at the next unattended IPL (initial program load). The status of a fix can be: Status On order Coer letter only Sae file only Not applied Temporarily applied Temporarily applied - PND Temporarily applied - ACN Permanently applied Permanently applied - PND Permanently applied - ACN Temporarily remoed Temporarily remoed - PND Temporarily remoed - ACN Permanently remoed - PND Permanently remoed - ACN Superseded Damaged Description Ordered but not receied by the system. They may reside on a tape, CD-ROM, be sent electronically, or copied from a tape. A coer letter exists for the fix. PTF exists in a sae file in library QGPL. Loaded but not applied. Applied temporarily Applied temporarily - Pending Applied temporarily - Action Applied permanently Applied permanently - Pending Applied permanently - Action Remoed temporarily Remoed temporarily - Pending Remoed temporarily - Action Remoed permanently - Pending Remoed permanently - Action PTF is replaced by another. A PTF object cannot be found (perhaps accidentally remoed). The PTF must be loaded again before you can apply it or remoe it. The pending and action status indicate that additional actions need to be taken to make the PTF actie or inactie. PND means the PTF status will be updated after the actions are taken. ACN means the PTF status will not be updated until the next IPL as no exit program was proided to erify that the actions were actually performed. Temporarily applied - ACN does not mean that the fix is not in effect. It means that the system cannot erify that it is in effect. Displaying fix information You can find out general information about a fix by doing the following: 1. On any command line, type DSPPTF. The display PTF Status display appears. Chapter 8. Managing system operations 85

2. Select the specific fix that you want to display, and then Option 5 (Display PTF details). The Display PTF menu appears. 3. Select Option 1 (General information). The General information display appears. The following describes each parameter on the General information display: Parameter On order PTF sae file PTF status Type Unattended IPL action Option part PTF library Coer letter Mandatory instructions Action pending Action required Target OS/400 Release Minimum-maximum leel Description Specifies whether the fix is on order. Yes indicates that the fix is on order, but may or may not be on the system. No indicates that the fix is not ordered. Specifies whether a sae file exists for the fix. Specifies the current status of the fix. The fix status field on the Display information display may differ from the Status field on the Display PTF status panel for seeral reasons: If there has been a change in status since the Display PTF Status display is shown, the General information display shows the updated status. The Status field on the Display PTF Status display is a combination of the fix status field, and the Action pending and Action required fields on the General information display. If the system encountered an error while building the fix information file, the fix status is updated when the General information display is shown. Specifies whether the fix is immediate or delayed Specifies the action that will occur on the next unattended IPL (initial program load). Specifies the option that this fix is for. Specifies the library this fix is installed into. Specifies whether there is a coer letter for this fix. Specifies whether there are instructions that need to be performed before this fix is applied. Specifies whether there is an action that needs to be performed. If YES is specified for this field, an action needs to be taken to make the fix actie or inactie. If NO is specified, it means the fix is actie. Specifies whether an action is required to make this fix actie after it has been applied. Specifies the release of the operating system this fix can be copied to or loaded on. Specifies the lowest and highest leel of the product that this fix can be installed on. fixes are able to span multiple leels of a system. Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Distributing fixes to remote systems You can distribute some or all the fixes you receie to a remote system. Fixes that are in a sae file can be sent to remote systems electronically. You can also use Management Central to distribute fixes across multiple systems. 86 iseries: Getting started with iseries

Note: When preparing a fix package to send to a remote system, make sure that the model of the remote system unit is compatible with the model of system unit required for the fixes (shown on the coer letter as Models). Combine some or all the fixes you receied electronically into a single fix sae file so you can send it electronically to a remote system. Note:You cannot combine fixes from different languages, releases, or superseded fixes into one sae file. Copy one or more fix files from CD-ROM or tape to a fix sae file so you can send it electronically to a remote system. If the fixes are already in a sae file, use object distribution to send the sae files electronically to the remote system. See the SNA Distribution Serices distribution. book for more information about using object If you ordered and receied a fix electronically for another system that has a newer release than the one on your system, you cannot load, copy, or display that fix on your system, but you can send that fix to the remote system using object distribution. Loading, Applying, and Remoing PTFs Automatically at Remote Systems To load fixes on remote systems follow the instructions in Installing Licensed Program or OS/400 fixes. To load fixes receied through the distribution serices network: 1. On any command line, type LODPTF LICPGM(xxxxxxx) DEV(*SAVF) SELECT(nnnnnnn), where xxxxxxx is the licensed program number and nnnnnnn is the fix identifier. 2. Type APYPTF (the Apply Fix command) to apply the fixes. To load PTFs from deice *SERVICE, do the following: Note: Loading fixes from deice *SERVICE is only alid if one fix exists in the saefile. 1. Use the QPZGENNM application program interface (API) to generate a name for the fix sae file. 2. Store the fix sae file in the library returned from the API. 3. Once the fix exists in the sae file, use the QPZLOGFX API to store the information about the fix in the fix database. 4. On any command line, type: LODPTF LICPGM(xxxxxxx) SELECT(nnnnnnn) FROMDEV(*SERVICE), where xxxxxxx is the licensed program number and nnnnnnn is the PTF identifier. For more detailed information about the QPZGENNM and QPZLOGFX APIs, see the Programming topic in the Information Center. To hae fixes applied automatically at the next unattended IPL (initial program load) on a remote system, specify the delayed parameter alue as *YES. If the next IPL at the remote system is attended, the Select Products to Work with PTFs (fixes) display is shown and the operator can choose to apply or not to apply the fixes. If the operator chooses not to apply the fixes, they are applied automatically during the next unattended IPL. To remoe delayed fixes from remote systems (see Remoing fixes), specify *YES for the Delayed PTFs field to remoe fixes during the next unattended IPL. If the next IPL on the remote system is attended, the Work with PTFs display is shown and the operator can choose to remoe or not to remoe the fixes. If the operator chooses not to remoe the fixes, they are remoed automatically during the next unattended IPL. Building a tailored fix package The following example shows you how to build your own fix package that can be used the same way as a fix package supplied by IBM serice support. This example combines a fix package with indiidual fixes into a tailored fix package for distribution to other iseries systems in your network. Chapter 8. Managing system operations 87

You can also use Management Central to complete these tasks. The order of a cumulatie PTF package is: 1. High-impact perasie (HIPER) Licensed Internal Code Fixes (5769999) 2. HIPER OS/400 fixes (5769SS1) 3. HIPER licensed program fixes 4. A delimiter which diides the HIPER fixes from the non-hiper fixes (5769111) 5. Non-HIPER Licensed Internal Code fixes 6. Non-HIPER OS/400 fixes 7. OS/400 online information fixes (if any) 8. Non-HIPER licensed program fixes For this example, assume that you want a tape that contains all but one (SF00600) of the fixes from the most recent fix package on CD-ROM or tape receied from IBM serice support, including the high-impact perasie (HIPER) fixes. In addition, you want to include four indiidual fixes receied electronically from serice support. These four fixes are MF00050, SF00480, SF00500, and SF00800. Because the four indiidual fixes were receied from IBM serice support, they already exist in sae files in library QGPL. They exist in the library as object type *file, as shown below: File Name QMF00050 QSF00480 QSF00500 QSF00800 Object Type *FILE *FILE *FILE *FILE The following shows the procedures for building a tailored fix package from CD-ROM or tape. Tailoring a PTF Package From Tape: 1. Find out the sequence number of the fix file you want to copy from the fix cumulatie package by using the Display tape (DSPTAP) command: DSPTAP DEV(TAP01) DATA(*LABELS) OUTPUT(*PRINT) The Display Spooled File display is shown. The product identifier is listed in the Data File Label column, and the fix file sequence number is listed in the File Seq column. For example, to copy fix for product RPG/400 (R), first find the data file label that identifies the product with an extension of A00, then find the corresponding sequence number. According to the figure below, the product identifier is P5769RG1.A00 and the file sequence number is 7. Display Spooled File display +--------------------------------------------------------------------------------+ Display Spooled File File..... : QPTAPDSP Page/Line 1/1 Control..... á Columns 1-78 Find...... á 5769SS1 V4R1M0 TAPE VOLUME INFORMATION C4123410 Deice..... : TAP01 Volume..... : C4123410 Owner ID.... : Density.... : *QIC120 Type...... : *SL Code...... : *EBCDIC Record File Block Recg Record Block File Mol Mol Data File Label Seq Format Tech Length Length Length Ind Seq P5769999.A00 0001 *U 00000 32760 000002 0001 P5769999.A01 0002 *U 00000 32760 000016 0001 P5769999.A02 0003 *U 00080 32760 000066 0001 P5769SS1.A00 0004 *U 00000 32760 000002 0001 P5769SS1.A01 0005 *U 00000 32760 000013 0001 P5769SS1.A02 0006 *U 00080 32760 000066 0001 88 iseries: Getting started with iseries

P5769RG1.A00 0007 *U 00000 32760 000002 0001 P5769RG1.A01 0008 *U 00000 32760 000013 0001 P5769RG1.A02 0009 *U 00080 32760 000066 0001 More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys +--------------------------------------------------------------------------------+ Display Spooled File display - screen 2 +--------------------------------------------------------------------------------+ Display Spooled File File..... : QPTAPDSP Page/Line 1/23 Control..... á Columns 1-78 Find...... á P5769111.A00 0010 *U 00000 32760 000002 0001 P5769111.A01 0011 *U 00000 32760 000016 0001 P5769111.A02 0012 *U 00080 32760 000066 0001 P5769999.A00 0013 *U 00000 32760 000002 0001 P5769999.A01 0014 *U 00000 32760 000013 0001 P5769999.A02 0015 *U 00080 32760 000066 0001 P5769SS1.A00 0016 *U 00000 32760 000002 0001 P5769SS1.A01 0017 *U 00000 32760 000016 0001 P5769SS1.A02 0018 *U 00080 32760 000066 0001 Bottom F3=Exit F12=Cancel F19=Left F20=Right F24=More keys +--------------------------------------------------------------------------------+ 2. Use the Copy Program Temporary Fix (CPYPTF) command to bring the HIPER fixes from the cumulatie fix package into library QGPL. Two licensed programs are being used in this example (MF and SF PTFs). CPYPTF LICPGM(5769999) FROMDEV(TAP01) TODEV(*SAVF) FROMSEQNBR(1) FROMENDOPT(*LEAVE) TOSAVF(QGPL/PCUMH999) CPYPTF LICPGM(5769SS1) FROMDEV(TAP01) TODEV(*SAVF) FROMSEQNBR(4) FROMENDOPT(*LEAVE) TOSAVF(QGPL/PCUMHSS1) 3. Copy the product delimiter into a sae file. CPYPTF LICPGM(5769111) FROMDEV(TAP01) TODEV(*SAVF) SELECT(*ALL) FROMSEQNBR(10) FROMENDOPT(*LEAVE) TOSAVF(QGPL/PCUMH111) 4. Copy the non-hiper fixes from the cumulatie package into a sae file omitting the unwanted fixes. CPYPTF LICPGM(5769999) FROMDEV(TAP01) TODEV(*SAVF) FROMSEQNBR(13) Chapter 8. Managing system operations 89

FROMENDOPT(*LEAVE) TOSAVF(QGPL/PCUMP999) CPYPTF LICPGM(5769SS1) FROMDEV(TAP01) TODEV(*SAVF) OMIT(SF00600) FROMSEQNBR(16) FROMENDOPT(*LEAVE) TOSAVF(QGPL/PCUMPSS1) Tailoring a fix Package From CD-ROM: 1. Find out the path identifier for the fix file you want to copy from the fix cumulatie package: Note: A path identifier is a1to6-digit number that identifies each fix file on the CD-ROM. Each release of a licensed product on the CD-ROM has its own unique set of identifiers. Each set of path identifiers for the product begins with the number 1 indicating the first fix file for the product and release. This first fix file may or may not contain HIPER fixes for the product. To get the path identifier for each fix file you want to copy from the cumulatie fix package for your product, use the Copy Program Temporary Fix (CPYPTF) command, and specify PATHID(*SELECT). The Select PTF CD-ROM File display is shown. Select PTF CD-ROM File display +--------------------------------------------------------------------------------+ Select PTF CD-ROM File System: SYSNAMXX Product........ : 5769SS1 Type option, press Enter. 1=Select National Feature Language Path Hiper Opt Release Type Version Identifier PTFs á V4R4M0 *CODE 1 Yes á V4R4M0 *CODE 2 No á V4R4M0 *LNG 2924 2 No +--------------------------------------------------------------------------------+ 2. Use the Copy Program Temporary Fix (CPYPTF) command to bring the HIPER fixes from the cumulatie fix package into library QGPL. Two licensed programs are being used in this example (MF and SF PTFs). You can identify the HIPER fix files on the Select PTF CD-ROM File panel by a Yes in the Hiper PTFs column. CPYPTF LICPGM(5769999) FROMDEV(OPT01) TODEV(*SAVF) FROMPATHID(1) TOSAVF(QGPL/PCUMH999) CPYPTF LICPGM(5769SS1) FROMDEV(OPT01) TODEV(*SAVF) FROMPATHID(1) TOSAVF(QGPL/PCUMHSS1) 3. Copy the product delimiter into a sae file. CPYPTF LICPGM(5769111) FROMDEV(OPT01) TODEV(*SAVF) SELECT(*ALL) FROMPATHID(1) TOSAVF(QGPL/PCUMH111) 4. Copy the non-hiper fixes from the cumulatie package into a sae file omitting the unwanted fixes. 90 iseries: Getting started with iseries

CPYPTF LICPGM(5769999) FROMDEV(OPT01) TODEV(*SAVF) FROMPATHID(2) TOSAVF(QGPL/PCUMP999) CPYPTF LICPGM(5769SS1) FROMDEV(OPT01) TODEV(*SAVF) OMIT(SF00600) FROMPATHID(2) TOSAVF(QGPL/PCUMPSS1) Creating the tailored fix cumulatie tape: Repeat the command for each licensed program with non-hiper fixes. The OMIT parameter was used to identify the fix not included in the tailored package. The TOSAVF name must be 8 characters in length and must start with the letter P. You can choose the remaining seen characters. The library on the TOSAVF parameter must be QGPL. Library QGPL now contains: File Name Object Type QMF00050 *FILE QSF00480 *FILE QSF00500 *FILE QSF00800 *FILE PCUMH999 *FILE PCUMHSS1 *FILE (plus more for HIPERs of licensed programs) PCUMH111 *FILE PCUMH999 *FILE PCUMPSS1 *FILE (plus more for non-hipers of licensed programs) 1. Initialize the tape for the tailored cumulatie package. INZTAP DEV(TAP01) NEWVOL(CUMPKG) 2. Copy the Licensed Internal Code HIPER fixes into one file and place it first on the tape. CPYPTF LICPGM(5769999) FROMDEV(*SERVICE) TODEV(TAP01) SELECT(CUMH999) TOENDOPT(*LEAVE) The TOENDOPT(*LEAVE) parameter is used to maintain tape position. 3. Copy the OS/400 HIPER fixes onto the tape. CPYPTF LICPGM(5769SS1) FROMDEV(*SERVICE) TODEV(TAP01) SELECT(CUMHSS1) TOENDOPT(*LEAVE) Repeat for each licensed program with HIPER fixes. 4. Copy the delimiter to the tape. CPYPTF LICPGM(5769111) FROMDEV(*SERVICE) TODEV(TAP01) SELECT(CUMH111) TOENDOPT(*LEAVE) 5. Copy the non-hiper Licensed Internal Code fixes into one file and place on the tape. Chapter 8. Managing system operations 91

CPYPTF LICPGM(5769999) FROMDEV(*SERVICE) TODEV(TAP01) SELECT(CUMP999 MF00050) TOENDOPT(*LEAVE) 6. Copy the non-hiper OS/400 fixes into one file and place on the tape. CPYPTF LICPGM(5769SS1) FROMDEV(*SERVICE) TODEV(TAP01) SELECT(CUMPSS1 SF00480 SF00500 SF00800) TOENDOPT(*LEAVE) Repeat for each licensed program with non-hiper fixes. The tape now contains the tailored fix package. It can be used in the same way that your serice support fix packages are used. Fixes can now be loaded on, applied to, or remoed from a system. Remoing fixes You can remoe fixes that are temporarily installed. Delayed fixes temporarily installed can be remoed temporarily when you do an IPL (initial program load) and then remoed permanently without doing an IPL. Immediate fixes temporarily installed can be remoed either temporarily or permanently without doing an IPL. You can also remoe immediate fixes that hae been loaded but not applied. Fixes permanently installed cannot be remoed. When fixes are remoed temporarily, the original objects that were replaced by the fix are restored to the program library. The system again erifies that the fix being remoed is not required for any other currently applied fix. If the fix being remoed is found to be required, the other fix (that it is required for) must be remoed first or at the same time. Note: Before you remoe a fix, be sure that the object affected by the immediate fix is not in use. Licensed Internal Code fixes can only be remoed permanently. Remoing licensed program fixes To remoe one or more licensed program fixes: 1. Enter the Remoe Program Temporary Fix (RMVPTF) command and press F4 (Prompt). 2. On the Remoe Program Temporary Fix (RMVPTF) display, type the character alue of the licensed program (shown on the coer letter) for the Product (LICPGM) parameter. 3. Select the fixes you want remoed by doing one of the following: Specify the numbers of the fixes you want to remoe for the PTF numbers to select (SELECT) parameter or *ALL to remoe all of them. Note: Specify RMVDEP(*YES) when specific fix numbers are entered on the SELECT parameter to ensure that dependents in the same product are also remoed. Specify *ALL for the PTF numbers to select (SELECT) field and the numbers of specific fixes you do not want to remoe for the PTF numbers to omit (OMIT) parameter. 4. Specify *TEMP for the Extent of change (APY) parameter to remoe the fixes temporarily or *PERM to remoe the fixes permanently. 5. If you are remoing immediate fixes, specify *NO for the Delayed PTFs (DELAYED) parameter. 6. If you are identifying delayed or immediate fixes that are to be automatically remoed during the next unattended IPL, specify *YES for the Delayed PTFs (DELAYED) parameter and *YES for the Remoe on unattended IPL (IPLRMV) parameter. 7. Press Enter. 92 iseries: Getting started with iseries

Remoing OS/400 fixes To remoe an immediate OS/400 fix temporarily: Type RMVPTF LICPGM(5769SS1) SELECT(SFxxxxx) RMV(*TEMP) RMVDEP(*YES), where xxxxx is the fix identifier. Note: if the fix is only temporarily remoed, it will be applied again with the next cumulatie fix package. To remoe an immediate OS/400 fix permanently: Type RMVPTF LICPGM(5769SS1) SELECT(SFxxxxx) RMV(*PERM) RMVDEP(*YES), where xxxxx is the fix identifier. To remoe a delayed OS/400 fix temporarily: 1. Type RMVPTF LICPGM(5769SS1) SELECT(SFxxxxx) RMV(*TEMP) DELAYED(*YES) RMVDEP(*YES), where xxxxx is the fix identifier. 2. Type the following command and press Enter to do an IPL to the B side: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B) To remoe a delayed OS/400 fix permanently: 1. Temporarily remoe the delayed fix first. 2. Type RMVPTF LICPGM(5769SS1) SELECT(SFxxxxx) RMV(*PERM) RMVDEP(*YES), where xxxxx is the fix identifier. Remoing licensed internal code fixes To remoe an immediate fix for the Licensed Internal Code temporarily, use the following command: RMVPTF LICPGM(5769SS1) SELECT(SFxxxxx) RMV(*PERM) RMVDEP(*YES), where xxxxx is the fix identifier. To remoe a delayed licensed internal code fix temporarily, do the following: 1. Type the following command and press Enter: RMVPTF LICPGM(5769999) SELECT(MFxxxxx) RMV(*PERM) DELAYED(*YES) RMVDEP(*YES), where xxxxx is the Licensed Internal Code identifier. 2. Type the following command and press Enter to do an IPL to the B side: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B) Remoing indiidual fixes in a cumulatie package before the next IPL To remoe a fix from a fix cumulatie package after you hae already selected option 8 (Install program temporary fix package) on the Program Temporary Fix (PTF) menu, but before the IPL has been done, enter the following command: APYPTF LICPGM(XXXXXXX) SELECT(YYYYYYY) DELAYED(*YES) APY(*TEMP) IPLAPY(*NO), where XXXXXXX is the licensed program and YYYYYYY is the number of the fix you want to omit. This resets the IPL apply indicator to IPL Action NONE. If you receie an error message, check the job log. If you receie message CPF3608, this fix has fixes that depend on it. You must omit these dependent fixes before omitting the original fix. The status of the omitted fixes will remain Not applied during subsequent IPLs. When you are finished omitting fixes, enter the following command to complete the cumulatie package installation: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B) Deleting fix sae files and coer letters After you hae permanently installed a fix, you may want to delete the fix sae file and coer letter if you do not need to distribute it to another system. Once a fix has been permanently installed and the sae file is deleted, all information about the fix except the status information is also deleted. By deleting the sae file, you can make more room on your system for other files. To delete a fix sae file, use the Delete Program Temporary Fix (DLTPTF) command. Do not use the Delete File (DLTF) command to delete fix sae files. Note: fix sae files and coer letters for a preious release are remoed during automatic cleanup if system logs are specified. Chapter 8. Managing system operations 93

Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Loading fixes The fix packages on CD-ROM, tape, or in a sae file can contain many fixes. You can load one, some, or all of them using the Load Program Temporary Fix (LODPTF) command. As fixes are loaded, the system erifies that the release of the product is correct. Fix status is not applied after the fix has been loaded on the system. Use the Apply Program Temporary Fix (APYPTF) command to apply the fix. For some of the applied fixes, the status is Temporarily applied - ACN. There are also some temporarily applied fixes that show a status of Temporarily applied - PND. For these fixes, you need additional actions to make them actie. Loading indiidual fixes from a cumulatie fix package To load one fix from a cumulatie package 1. Enter the Load PTF (LODPTF) command and press F4 (Prompt). 2. Specify the parameter alues according to the fix you are loading. 3. Specify the fix identifier you want to load in the fix numbers to select (SELECT) parameter and press Enter. 4. Repeat the Load PTF (LODPTF) command for each fix you want loaded from the cumulatie CD-ROM or tape. For fixes on a CD-ROM, the system will automatically find the fix file in the cumulatie package that contains the selected indiidual fixes when you specify PATHID(*FIRST). All fixes to be loaded must exist in the same path identifier. Otherwise, you need to load the fixes separately. For fixes on a tape, you can also use the Load PTF (LODPTF) command to specify the fixes by the sequence number found in the coer letter that comes with the tape. In the fix numbers to select (SELECT) parameter, specify the fix you want. Specify the sequence number for the sequence number (SEQNBR) parameter. You need to specify the correct sequence number for each fix in the cumulatie package. When loading indiidual fixes from the package on tape, you can also specify ENDOPT(*LEAVE) on the Load Program Temporary Fix (LODPTF) command and repeat the command until the desired fix is found. Loading fixes that supersede other fixes If the fix being loaded replaces (supersedes) existing fixes (identified in the fix coer letter) the following considerations apply: If the fix to be replaced is not applied to the system, the new fix can be loaded successfully. A record is kept indicating that the replaced fix has been superseded. If the fix to be replaced is permanently applied, it is considered to be a part of the operating system or licensed program to which it was applied. The new fix can be loaded successfully. If the fix to be replaced is temporarily applied, the load operation will automatically permanently apply any replaced (superseded) fixes. If you do not want the fix function to permanently apply any replaced (superseded) temporarily applied fixes automatically, specify *NOAPY for the Superseded PTFs (SPRPTF) parameter on the Load Program Temporary Fix (LODPTF) command. The fixes to be replaced must either be permanently applied or permanently remoed before fixes that are replacing them can be loaded. Note: When you order a fix, IBM serice does not search through the fixes to determine which one is the latest leel. For example, if you order a fix that is superseded by another fix, IBM serice will only send you the fix ordered by you instead of the superseding fix. You need to use the summary list to identify a fix you need to order. Scan the summary list for fixes that replace the fix in question and then order the fix. 94 iseries: Getting started with iseries

Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Applying fixes: adanced procedure Some fixes cannot be applied immediately because the operating system or licensed programs they affect are actie. These fixes are called delayed fixes and can be applied at the next system initial program load (IPL). Immediate fixes can be applied without doing an IPL if the licensed program they affect is not in use, or may be applied like delayed fixes when you do the next IPL. Fixes can be applied (made actie) on either a temporary or permanent basis. If the fix is applied temporarily (also known as installed), a copy of the object being changed is saed. If the fix is applied permanently (also known as permanently installed), the old object is remoed. Permanently applied fixes cannot be remoed. Fixes generally should be installed when receied. Installing fixes allows you to test them in your operational enironment. You should ensure that the new fixes operate properly on your system before permanently installing them. As long as the fixes are installed temporarily, they can be remoed. Once they hae been installed permanently, they cannot be remoed. When you are sure that the Licensed Internal Code fixes work properly, it is recommended that you install them permanently to reduce the time required to install the next cumulatie fix package, and to make aailable the storage for future fixes. If this storage is not made aailable, you will need to permanently install some of your Licensed Internal Code fixes before you can temporarily install any additional fixes. Temporarily installed Licensed Internal Code fixes are only in effect when you use the B storage area to perform an IPL. Notes: 1. You cannot apply or remoe fixes with mandatory special instructions when *ALL is specified on the PTF numbers to select (SELECT) parameter of Apply Program Temporary Fix (APYPTF) or Remoe Program Temporary Fix (RMVPTF)commands. These PTFs are only applied or remoed when they are specified by a number on the SELECT parameter. This protects against applying or remoing fixes without reading the mandatory special instructions. 2. The term fix, in this context, refers to Licensed Internal Code fixes and licensed program fixes, including OS/400 program fixes. Temporarily or permanently installing licensed program or OS/400 fixes during an unattended IPL You can install both delayed and immediate fixes temporarily or permanently. To install delayed fixes temporarily: 1. On any command line, type: APYPTF LICPGM(*ALL) SELECT(*ALL) APY(*TEMP) DELAYED(*YES) IPLAPY(*YES) 2. Press Enter. To permanently install all fixes that are temporarily installed (status of Temporarily applied) during the next unattended IPL, or to permanently install all immediate fixes that hae a status of Not applied during the next IPL 1. On any command line, type: APYPTF LICPGM(*ALL) SELECT(*ALL) APY(*PERM) DELAYED(*YES) IPLAPY(*YES) 2. Press Enter. To perform an IPL on the system: Chapter 8. Managing system operations 95

1. On any command line, type: PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B) 2. Press Enter. Remember: You must specify LICPGM(*ALL) and SELECT(*ALL) to ensure that fix dependency checking takes place for prerequisite Licensed Internal Code fixes. Attention: If your system has logical paripartitionsing the Power pushbutton, DST option 7, or the Power Down System (PWRDWNSYS) command can affect multiple partitions. For details on using logical partitions on your iseries serer, go to Managing logical partitions. Checking requisite fixes When installing fixes, other fixes can be specified as requisites for the fix. These different types include prerequisites and corequisites. Each type has a different relationship with the fix you are trying to apply. Some of the relationships hae additional considerations. Prerequisite fixes: You must specify LICPGM(*ALL) and SELECT(*ALL) on the Apply Program Temporary Fix (APYPTF) command to ensure that fix dependency checking takes place for prerequisite Licensed Internal Code fixes. The fix with prerequisites knows about its prerequisites, but a prerequisite fix does not hae any information about the fix that is dependent on it. Therefore, prerequisite checking must be done when the fix with the prerequisites is set for apply. When you use the GO PTF command and Option 8 to apply a fix with prerequisites, any Licensed Internal Code fixes that are called out as prerequisites are set for permanent apply. This is ery important to remember. It is the action of setting the dependent for apply that sets the Licensed Internal Code fixes prerequisite for permanent apply. Corequisite fixes: The system will not apply corequisite fixes unless it is also applying the other. The corequisite relationship is two-way, meaning each fix must specify the other as a corequisite. Corequisites must be within the same product, option, ersion and release. The system will check that the corequisite fixes are applied at the same time, but it cannot ensure that one will not end up actie without the other. The system now recognizes under certain conditions, whether a fix specified as a prerequisite or corequisite is really needed. This decision is based on whether the function it will fix is actually installed on your system. These prerequisites and corequisites are displayed as conditional requisites. Temporarily or permanently installing licensed program or OS/400 fixes during an attended IPL You can temporarily or permanently install both delayed and immediate fixes that hae a status of Not applied during an attended IPL. To temporarily install a delayed fix, you only need to do one IPL. To permanently install a delayed fix after it has been applied temporarily and tested, you need to do another IPL. Before you start: Send a message to users notifying them to sign off the system. To temporarily or permanently install a fix during an attended IPL: 1. Switch the system unit to the Manual mode. If you are temporarily installing delayed Licensed Internal Code fixes, select storage area A. Immediate Licensed Internal Code fixes can be installed when IPL d to storage area B. If you are permanently installing Licensed Internal Code fixes, select storage area B. 2. Type PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(x), where x is your storage area, on any command line and press Enter. 3. Select option 1 (Perform an IPL) on the IPL or Install the System display. 4. Type your user ID and password on the Sign On display. 5. On the Select Products to Work with PTFs display, select the licensed program for which you want to install the fix 96 iseries: Getting started with iseries

If fixes are not applied or are temporarily applied, the Work with PTFs display is shown. This display is used to install and remoe fixes and shows the current status of each fix that you can work with. If you want to keep the same status for any of the fixes displayed, leae the Opt column empty. Fixes that are not installed can be either temporarily installed using option 1 or permanently remoed using option 4. Fixes that are temporarily installed can be either permanently installed using option 2 or temporarily remoed using option 3. Note: For an explanation of permanently remoed and temporarily remoed PTFs, see Remoing fixes. 6. After typing the option number you want for each of the fixes displayed, press Enter. 7. Repeat step 5 and step 6 for each licensed program for which you want to apply fixes. 8. Press F3 (Exit) to continue with system operations. Temporarily or permanently installing immediate licensed program or OS/400 fixes without an IPL To temporarily or permanently install immediate fixes without doing an IPL: 1. Make sure the licensed programs to which the fixes are being applied are not in use. Note: If you are applying fixes to the Licensed Internal Code or to the OS/400, be sure to follow any special instructions, including actiation instructions, in the coer letter to ensure that the system is in the correct state. 2. Enter the Apply Program Temporary Fix (APYPTF) command and press F4 (Prompt). Press F9 (All parameters) to display all of the fields on the Apply Program Temporary Fix (APYPTF) display. 3. Specify the number that corresponds to the licensed program you are applying fixes for the Product (LICPGM) parameter. 4. Specify the release leel for the Release (RLS) parameter. Note: The release parameter is only required if more than one release of the product is installed. 5. Select the fixes you want applied by doing one of the following: Specify the identifiers of the fix you want to apply in the PTF numbers to select (SELECT) parameter. To apply all fixes, specify *ALL in the PTF numbers to select (SELECT) parameter. Specify *ALL for the fix numbers to select (SELECT) parameter, and the numbers of specific fixes you do not want to apply for the fix numbers to omit (OMIT) parameter. Note: Specify APYREQ(*YES) to ensure all requisites within the same product are also applied if indiidual fix identifiers are specified in the SELECT parameter. 6. To temporarily install the fixes, specify *TEMP for the Extent of change (APY) parameter. To permanently install the fixes, specify *PERM. Note: fixes temporarily installed can be remoed; fixes permanently installed cannot be remoed (see Remoing fixes). 7. Specify *NO for the Delayed PTFs (DELAYED) parameter. Note: To apply all immediate fixes right now and all delayed fixes on the next IPL, specify *ALL for the Product (LICPGM) parameter, *ALL for the Select (SELECT) parameter, and *IMMDLY for the Apply Type (APPLY) parameter. 8. Press Enter. The system applies the fixes to the specific licensed program. 9. Repeat steps 2 through 8 until the fixes are applied for all the selected licensed programs. Applying licensed internal code fixes at the next unattended IPL To apply Licensed Internal Code currently operating on the A storage area, the Licensed Internal Code fixes can be applied immediately. 1. Make sure the system is in the Normal mode. 2. If you are not running on the correct storage area, type the following on any command line and press Enter: PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B) Chapter 8. Managing system operations 97

3. Type the following commands on any command line and press Enter after each one: APYPTF LICPGM(5769999) APY(*TEMP) DELAYED(*YES) PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B) Note: While applying Licensed Internal Code fixes, it may be necessary for the system to reorganize a portion of the Licensed Internal Code storage. This reorganization can take up to 1 hour. While this reorganization is taking place, system reference codes (SRCs) C600 434B and C600 435B are displayed. Applying licensed internal code fixes without an IPL You may be operating from either storage area to temporarily install an immediate Licensed Internal Code fix without doing an IPL. You must be operating from the B storage area to permanently install a temporarily installed Licensed Internal Code fix without doing an IPL. To determine the storage area you are currently operating from: 1. On any command line, type DSPPTF 5769999. 2. Press Enter. On the Display PTF Status display, the storage area is identified in the IPL source field. ##MACH#A is the A storage area and ##MACH#B is the B storage area. If you are not running on the correct storage area: 1. On any command line, type PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(X), where IPLSRC(X) is A if you want to apply them temporarily or B if you want to apply them permanently. 2. Press Enter. To apply Licensed Internal Code fixes immediately: 1. On any command line, type APYPTF 5769999 APY(xxxxx) DELAY(*NO), where where xxxxx is *TEMP or *PERM. 2. Press Enter. Resetting IPL action: If you decide not to apply the fix on the next IPL, you can reset IPL action by using the following command: APYPTF LICPGM(5769999) APY(*TEMP) DELAYED(*YES) IPLAPY(*NO). Additional information on this topic can be found in these sources: Manage fixes with Management Central Fixes and logical partitions Working with deices A deice is a piece of equipment that is connected to, but does not directly interact with, your system. Instead, a deice (such as a workstation, printer, diskette or tape unit, or remote system) is controlled by a controller. Depending on your organization, you may frequently attach and configure new deices, or these actiities may happen rarely once your system is operational. System requirements for deice configurations Your system automatically configures any new deices that you attach. Howeer, if you changed the automatic configuration set parameter when you initially set up your system, you will not be able to change it until you perform an attended IPL, as the Set Major System Options display is only aailable at that time. If you hae automatic configuration set to Yes (Y), your system automatically configures any local controllers or deices, including local workstation and tape controllers, display stations, printers, tape, diskette or optical units, and media library deices. 98 iseries: Getting started with iseries

Your system must be powered off to physically attach new local controllers. Howeer, it does not hae to powered off, and you do not hae to perform an IPL for automatic configuration to take place when you add new external deices. Additional information on this topic can be found in these sources: Creating a deice inentory Working with printer output One of the most basic system functions is printing. Depending on the type of printing you choose, you can print to a local or remote printer, across a LAN (local area network) or to a directly-attached printer. The iseries supports many different kinds of printing. The three most commonly used methods are: ASCII LAN printing Intelligent Printer Data Stream (IPDS) LAN printing Twinax printing Choosing the printing method that is right for you depends on the particular circumstances of your business. For instance, if you hae a ery complex printing enironment and you want to share your printer between systems, you might want to consider IPDS LAN printing. If your print needs are less complex, or your printer will only be used on one system, the traditional Twinax printing method might be the best fit for your needs. Keep these considerations in mind as you choose a printing protocol from one of the ones listed below. ASCII LAN printing Printing across your local area network (LAN) can take many forms. Some of the most common are described below: Simple Network Management Protocol (SNMP) There are arious methods of ASCII LAN printing. One method of ASCII LAN printing is through the use of the SNMP printer drier support. To use the SNMP printing support, your printer and network printer serer must support the Host Resource MIB (Management Information Base) or the Printer MIB. Your network printer serer is the network interface used to connect the printer to the LAN. Sometimes it is an internal card in the printer itself, and sometimes it is an external box. This configuration method tracks printer status on a TCP/IP port separate from the TCP/IP port used to send the print data. This proides better error handling than other ASCII LAN attachment methods. This method also proides better sharing of the printer with other systems. Get the latest SNMP configuration and troubleshooting information from the IBM Knowledge Base, or check out the Printer Deice Programming manual. Print Job Language (PJL) A second method of ASCII LAN printing is through the use of the HP PJL printer drier support. To use the HP PJL printer support, your printer must support PCL5e and the network printer serer must support bi-directional PJL on some TCP/IP port. This configuration method proides some error handling through the same TCP/IP port used to send the print data. Unlike the LPR/LPD method, the PJL printer drier waits until the printer has finished printing the current spooled file before printing the next one. Get the latest PJL configuration and troubleshooting information from the IBM Knowledge Base,or check out the Printer Deice Programming manual. Chapter 8. Managing system operations 99

Line Printer Requester/Line Printer Daemon (LPR/LPD) A third method of ASCII LAN printing is through the use of the LPR/LPD (Remote Writer) support. To use the LPR/LPD support, your network printer serer must support LPD. This configuration method proides ery minimal error handling. Once the file has been sent to the printer, it is no longer monitored. This method does not proide page range or job accounting support. Telnet A fourth method of ASCII LAN printing is through the use of the telnet printer pass-through support. Get information on setting up and managing Telnet printing now. IPDS LAN printing PSF/400 (Print Serices Facility/400) is required to print to LAN attached IPDS printers. PSF/400 requires the network printer serer to support IPDS. This configuration method proides the best leel of printer error handling and printer data stream support. It also has performs better in complex printing enironments. Get the latest IPDS configuration and troubleshooting information from the IBM Knowledge Base. For more information on when to use PSF/400, check out the Printer Deice Programming manual. Twinax printing You can also print to printers attached to workstation controllers, InfoWindow displays, or PCs through the use of the twinax printing support. One adantage of twinax printing support is the automatic configuration of printers. See the Local Deice Configuration guide or the Printer Deice Programming manual manual for more information. Additional information on the printing topic can be found in these sources: IBM AS/400 Printing V Troubleshooting printers Printing and deice programming Printers and deices Using Line Printer Requester/Line Printer Daemon (LPR/LPD) printing Setting up a remote printer Setting up printers on your system can be accomplished quickly. The topics below describe the steps you need to follow to set up LPR/LPD printing on your system. Preparing to print Printing files using LPR/LPD is accomplished by sending spooled files. Determine if you hae the authorization necessary to send and receie spooled files, and to start an LPR print job. Starting printer output The printers are set up, and you hae all the authorization you need. Time to start printing. Managing printer output Spooled files are sent from the system to the printer queue or to another system. The topics below assist you as you manage the smooth flow of information from user to printer. Changing format to ASCII Naming printer output Determining ownership of printer output 100 iseries: Getting started with iseries

Deleting printers As a part of regular system maintenance, delete printers that you no longer want on your system. This eliminates the problem of users attempting to send spooled files to printers that no longer exist on the system. Setting up a remote printer Not eery printer attached to your system has to be in close physical proximity to your system. You hae the option of printing to a printer at another site. Follow the tasks below to set up a remote printer. To set up an LPD from Operations Naigator: 1. Expand the system that you want to configure. 2. Expand the Network icon. 3. Expand the Serers icon. 4. Expand the TCP/IP icon. 5. Right-click the LPD serer and select Properties. You can now select the number of listener jobs to be started and whether the LPD serer starts wheneer TCP/IP is started on the system. You can also specify that one or more LPD serers can be started automatically by using the Change LPD Attributes (CHGLPDA) command. Other properties can be configured from the command line. To set up an LPR from the command line (to a printer on the network), following the instructions in the IBM Knowledge Base, under Configuring a Remote Output Queue (RMTOUTQ). Additional information on this topic can be found in these sources: Starting printer output Printing and deice programming IBM Knowledge Base Setting up a remote printer from the command line Occasionally, you need to customize the remote printer configuration more than is possible through Operations Naigator. The steps below outline how to complete this task: 1. From the command line, enter the CRTOUTQ command to create an output queue to hold your spooled files. 2. When the command is displayed, press F4 to display optional parameters in stages. 3. Specify the following alues: Output queue: Enter the name of the output queue (up to 10 characters). The library the output queue is created in may also be specified. Remote system: Enter the name assigned to that IP address. Remote printer queue: PASS The supported alues for this parameter are determined by the remote system. This may be the name of the queue on a print serer or hae a specified alue, such as PASS, for some printers. This alue may be case sensitie; to presere lower case characters, enclose the parameter in single quotes. Consult your printer or serer manual for problem resolution. Connection type: *IP Destination type: *OTHER If destination is a network station printer, enter *OS400 for V4R4 and later systems. Host print transform: *YES Chapter 8. Managing system operations 101

Manufacturer type and model: Press F4 on this field to see the list of printer types and models and enter the alue that corresponds to your printer. Image configuration: *NONE Internet address: Enter the printer s IP address. Only an IP address is anticipated here (for example, address.address.address.address). No alidation is done to confirm that an appropriate alue has been entered. Do not use a host table entry in place of the address in this field. Text description : Enter the printer s description. Destination options: XAIX. Use this setting for printers but not for serers to ensure maximum compatibility. This option is needed for printers to print more than one copy of a spooled file that has more than one copy in its spooled file attributes. XAIX is not a default alue because it may cause problems with some print serers. 4. Enter WRKOUTQ [character string] on the command line. Use a portion of the name you gae the output queue in the character string. Entering the command without the character string returns a list of all output queues, which may be ery long. You will receie a message that the output queue was created in the library. 5. Confirm that the output queue was created. Look in the resulting list for the output queue name that you created. 6. Enter STRRMTWTR on a command line. 7. Enter the name of the output queue you created. You will receie a message that the writer was submitted to the job queue. 8. Enter WRKWTR [output queue name] on any command line to erify that the writer was started. 9. Test the printer by placing a small spooled file on the output queue. 10. Test the multiple copy function by changing the spooled file copies attribute with the CHGSPLFA command before placing it in the output queue. This confirms that a printer is directly attached to the network, rather than attached through a print serer. The printer is now ready to use. Additional information on this topic can be found in these sources: Printing and deice programming Preparing to print Printing files using TCP/IP is accomplished by sending spooled files. Do the following tasks to determine if you hae the authorization necessary to send and receie spooled files, and to start a LAN-attached printer session, see the following topics: Authorizations for sending jobs Authorizations for sending jobs Authorizations for receiing jobs How the system uses authorizations for receiing jobs on page 103 Starting an LPD serer job Commands to start an LPD serer job on page 103 Authorizations for sending jobs To send a spooled file, users need to hae one of the following authorities to the file or to the output queue in which the file resides: Be the owner of the spooled file. Hae spool control authority (*SPLCTL). Hae job control (*JOBCTL) special authority on an operator-controlled (OPRCTRL(*YES)) output queue. Be the owner of the output queue. Hae add, delete, and read authority to an output queue created with AUTCHK(*DTAAUT). Hae read authority to output queues created with DSPDTA(*YES). 102 iseries: Getting started with iseries

This information is common to all printers. How the system uses authorizations for receiing jobs This information is applicable to LAN-attached print jobs only. The destination system administrator restricts output queue access for users without user IDs on the destination system. This is done by restricting the access authorities of the QTMPLPD user ID, which is the default profile used by any user ID that is not found. Howeer, this restriction does not affect user IDs that are found on the destination system. If you set the *PUBLIC authority of the user profile QTMPLPD to *EXCLUDE, only users with user IDs that are the same on both the sending and receiing systems receie spooled files on the destination system. The QTMPLPD user profile ships with an authority of *OBJOPR. If you do not hae a user ID on the destination system, you are still able to send spooled files to the destination system under the QTMPLPD user profile. Haing a user ID defined on the receiing system can be adantageous. If you hae the same user ID on both systems, you are the owner of the spooled file on the receiing system, making it easier to find the spooled file with the Work with Spooled Files (WRKSPLF) command. If you do not hae a user ID on the receiing system, then QTMPLPD owns the file. Because you do not own the spooled file, you might hae limited access to the spooled file. Your authority to the output queue on which the spooled file is located determines your access to the spooled file. If you are using a security leel of 50, the system alue QALWUSRDMN must contain the library name QTEMP to enable LPR serice. For LPD serice, the required library is QTCP. Commands to start an LPD serer job LPR and LPD do not support the ability to print page ranges. To do that you must configure your printers as *LAN type printers by creating a printer deice type. To receie spooled files from other LPR clients, you must start the serer job for the LPD application in the QSYSWRK subsystem. You must also ensure that the QALWUSRDMN system alue is set to *ALL or has the library QTCP included in it. This is required for the LPD serice to function. The Start TCP/IP Serer (STRTCPSVR *LPD) command starts the LPD serer that is shipped with the TCP/IP Utilities licensed program. You can also start the LPD serer job with the AUTOSTART parameter of the Change LPD Attributes (CHGLPDA) command. Howeer, the STRTCPSVR command oerrides or ignores the AUTOSTART parameter on the CHGLPDA command. The Start TCP/IP (STRTCP) command starts all of the serers that hae been started automatically. If your LPD serer did not start, check the LPD Autostart attributes by typing CHGLPDA and pressing F4. The STRTCPSVR command starts the number of serers configured in the CHGLPDA command. After you start the minimum number of LPD serers, the STRTCPSVR command starts only one additional serer at a time. LPD works most efficiently when two or more serers are running. Each serer processes one job; LPD cannot receie any jobs while a current job is running. Hae an additional LPD serer aailable to preent delays for other LPR clients. You can use the Configure TCP/IP LPD (CFGTCPLPD) command or the CHGLPDA command to work with the LPD attributes. Chapter 8. Managing system operations 103

Additional information on this topic can be found in these sources: Starting printer output Printing and deice programming Starting printer output LPR/LPD Printing is accomplished by sending spooled files to a predefined printer. You can send a print job to a printer by following these steps: 1. Expand the system you are configuring. 2. Expand Basic Operations. 3. Right-click the printer you wish to print to and select Start. 4. When the start dialog is displayed, confirm the alues in the fields and click OK to start the printer. Additional information on this topic can be found in these sources: Printing and deice programming Changing a format to ASCII before printing If a spooled file has the printer deice type of Systems Network Architecture (SNA) character string (*SCS) or Adanced Function Printing Data Stream (AFPDS), the file format needs to be changed on an iseries serer prior to sending it to a system printer. Files with the printer deice type of Intelligent Printer Data Stream (IPDS) cannot be transformed. If you attempt to change the format, no conersion will occur, the file will not be sent, and an error message will be issued. If you know that the destination system supports the printer deice type of the spooled file, send the file without transforming it. When sending files, you must consider any external resources of that file. These resources, such as fonts and oerlays, must also reside on the destination system in order for the file to print correctly. ASCII printers cannot print spooled files that hae a printer deice type of Systems Network Architecture character string (*SCS) or Adanced Function Printing Data Stream (AFPDS). The data stream needs to be conerted to ASCII before the file can be printed. The Host Print Transform (HPT) function proides a means to transform spooled files prior to sending them to the printer. Using the system to transform the spooled files takes less time than haing the printer transform the file. Newer releases of the operating system proide support to transform PostScript files to ASCII format by using the Image Print Transform function. If you need to change the format of a spooled file, specify *YES on the Transform parameter of the SNDTCPSPLF or LPR command to hae the data stream transformed when you send spooled files. Using LPD to print ASCII files conerted to EBCDIC LPD can also receie printer files from ASCII hosts running LPR and print them in EBCDIC. There are some limitations on character conersion, howeer. In particular, line feed and form feed printer control characters may not function properly. The ASCII hosts must be able to conert the printer data stream to EBCDIC prior to sending it using LPR. In addition, ariable length records are not handled well. Pad each record with blanks to a fixed width, and specify the width option or flag on the LPR command. To do this, you need to customize the LPD printer file on the iseries. Do not change the original printer file in QTCP. Instead, make a copy of it, change the copy, and include it higher up in the user library list portion of the *LIBL for the user profile receiing the file. 104 iseries: Getting started with iseries

You hae two options for changing the LPD printer file: 1. Change the QUSRSYS/QPTMPLPD working copy from *USERASCII to *SCS. This affects all LPR clients because it resides in the *SYSLIBL path and is found first by all user profiles. This means that all LPR clients must send EBCDIC data streams (or at least only send EBCDIC streams until the QUSRSYS/QPTMPLPD printer file is restored to *USERASCII type). 2. Change the QUSRSYS/QPTMPLPD working copy of the *USERASCII to *SCS, and moe it to another library that is your *CURLIB or somewhere in your *USERLIBL path. Ensure that your target library is found ahead of library QTCP, which has the installation copy of the printer file. You must also ensure that the target library is unique to your user profile, *LIBL, in order to aoid affecting other users. Your *LIBL is considered to be one that exists when your user profile is signed on. You cannot run any programs when you sign on to set the library list. Any change to your current interactie session has no effect upon the *LIBL used. This is because the user profile *LIBL is checking eents occuring in an LPD serer batch job and not your interactie job. To receie EBCDIC files, the LPR client must be any user with an iseries user profile that has the *SCS working copy in its *LIBL path. For example, if someone moes the printer file to library JOHNDOE, any user profile with JOHNDOE as its *CURLIB or in its *USRLIBL uses the *SCS printer file. Remoing the working copy from library QUSRSYS forces eery user profile that does not hae library JOHNDOE in its *LIBL to find the installation copy of QTCP. If library QTCP is not already in the *LIBL, then the system adds it as the last library in *LIBL for all user profiles. This insures that the system finds a printer file. Do not change the installation copy in QTCP. This insures that other user profiles, including the default profile QTMPLPD, still receie ASCII data streams as usual. Additional information on this topic can be found in these sources: Printing and deice programming How spooled files are named Spooled files that LPD receies hae file names in the form LPDxxxx. The x represents any alid hexadecimal character (from A-F and 0-9). These hex characters are the result of cyclic redundancy checking that is performed on client information to identify the LPR client for LPRM support. áspooled files that are named in this manner are unique to each client.áthe system uses the name as a signature. All files from a single client hae the same signature. A client must generate a matching signature to use LPRM to delete any LPR spooled file. Clients can use LPQ (line printer queue) and LPRM (line printer remoal) commands to query and remoe LPR spooled files, as LPD supports both functions. Howeer, the system that acts as a client cannot issue these commands. If the LPR client is another iseries 400 using DESTTYP(*AS400) and TRANSFORM(*NO) parameters, the spooled file has exactly the same attributes on the receiing queue as it had on the sending queue. The spooled file name is not conerted to LPDxxxx form and is left unchanged. The LPQ command sent to an iseries 400 system requires a job list parameter, or more specifically, a user profile under which the query is performed.á Additional information on this topic can be found in these sources: Printing and deice programming Chapter 8. Managing system operations 105

Ownership of spooled files If the user ID on the sending system exists on the destination system, the spooled file is created under that user profile.áhoweer, if the user profile does not exist on the destination system, then the spooled file is created under the QTMPLPD user profile. When sending from a non-iseries 400 system to an iseries 400 system, the file is always created using the QTMPLPD user profile.áthis is also true when sending fromáone iseries to another with the TRANSFORM(*YES) parameter.áin these cases, spooled files receied by the LPD serer are placed under special jobs. For example, if user ID JOHN exists, the file is placed under job 999999/JOHN/QPRTJOB.á If user ID JOHN does not exist, the file is placed under 999999/QTMPLPD/QPRTJOB. Additional information on this topic can be found in these sources: Printing and deice programming Deleting printers that are no longer needed on the system As a part of regular system maintenance, delete printers that you no longer want on your system. This eliminates the problem of users attempting to send spooled files to printers that no longer exist on the system. Deleting LAN-attached printers Perform the following steps to remoe a LAN attached printer from the system: 1. Enter the WRKCFGSTS *DEV command on any command line. 2. Enter Option 2=Vary off next to the printer you are remoing. 3. Enter the WRKOUTQ command on any command line. 4. Enter Option 3=Hold next to the printer you are remoing. 5. Enter the WEKDEVD command on any command line. 6. Enter option 4=Delete next to the printer that you are remoing. Deleting printer writers To remoe an ASCII printer from the system, perform the following steps: 1. Enter the WRKWTR *ALL command on any command line. 2. Enter Option 4=End next to the printer that you are remoing. 3. Enter the WRKOUTQ command on any command line. 4. Enter Option 4=Delete next to the printer that you are remoing. Additional information on this topic can be found in these sources: Printing and deice programming CLROUTQ command Setting up Telnet printer pass-through The Telnet printer pass-through mode allows system users with a Telnet client that supports client emulation to attach printer deices on the system oer the network. This support is accomplished by negotiating the 3812 or 5553 deice type support with the remote client Telnet application. If you intend to use the TCP/IP Telnet printer pass-through, check with the client endor or with third parties that are known to proide 5250 clients for the aailability of the printer pass-through function. Client Access supports this function, as do many third-party clients. 106 iseries: Getting started with iseries

Telnet printer pass-through deliers the printer data stream between the two systems as either EBCDIC or ASCII depending on the preferences of the requesting client. Telnet printer pass-through supports the following generic EBCDIC printer deices: IBM-312-1 for single byte character set support (SBCS) IBM-5553-B01 for double byte character set deices (DBCS) Client Access supports 3 additional transform mechanisms, called Host Print Transform (HPT), Printer Definition Table (PDT), and Graphical Deice Interface (GDI). When using Telnet printer pass-through, the print data must be spooled to a print writer queue (direct printing to the deice is not supported). To ensure this, the print file used must specify *YES for the SPOOL parameter. The name of the print writer output queue is the same as the name of the printer. Use the Configure TCP/IP Telnet (CFGTCPTELN) command to set up your Telnet session. Use the following steps to set up your Telnet printer pass-through mode session: 1. Start the Telnet serer job 2. Set the number of irtual deices 3. Create irtual controllers and deices 4. Actiate the QSYSWRK subsystem 5. Security considerations Additional information on this topic can be found in these sources: Starting printer output Printing and deice programming Setting the number of irtual deices Virtual deices are used by the serer system to direct output to deices on your system. iseries 400 Telnet serer support automatically selects (and creates if necessary) these deices for you. You may also choose to create your own irtual deice under the QVIRDCnnnn irtual controller. You can choose to allow the Telnet serer support on the system to automatically configure irtual controllers and deices. The QAUTOVRT system alue specifies the maximum number of deices that are automatically configured by the system. Use the Change System Value (CHGSYSVAL) command to change the alue of the QAUTOVRT system alue. For example, entering the following command string changes the number of irtual deices that can be allocated on a system to 50: CHGSYSVAL SYSVAL(QAUTOVRT) VALUE(50) QAUTOVRT supports numeric alues of 0 through 32500, and a special alue of *NOMAX. Maximum number of users To determine and set the maximum number of users you want signed on to the system at any one time: 1. Set the QAUTOVRT alue to 32500, the maximum alue allowed, or use the *NOMAX alue. 2. Let your users use pass-through, Telnet, the irtual application program interface and Telnet printer pass-through until you decide that the number of irtual deices created is sufficient for normal system operation. 3. Change the QATUOVRT alue from 32500 to the number you hae determined is optimal for your system. Virtual deice configuration If you hae neer allowed automatic irtual deice configuration on your system, the QAUTOVRT alue is 0. A Telnet connection attempt with a dependence on automatic creation of the irtual deice then fails Chapter 8. Managing system operations 107

because the Telnet serer does not create more than the specified QAUTOVRT deices (in this case, 0). If you try to connect, you will receie a message (TCP2504) that indicates the Telnet client session has ended and the connection is closed. Additionally, QTVTelnet and QTVDEVICE in the QSYSWRK subsystem on the Telnet serer will send a message (CPF8940) indicating that a irtual deice cannot be automatically selected. If deices already exist on the system and are not currently in use, Telnet will reuse an existing, aailable deice that fits the deice name criteria, een if it means it must delete and recreate that existing deice to match the deice type.á Some users may still be able to connect for this reason. If you change the QAUTOVRT alue to 10, the next Telnet connection attempt causes the Telnet serer to create a irtual deice.á This irtual deice is created because the number of irtual deices on the controller (0) is less than the number specified in the QAUTOVRT.á Een if you change the specified number to 0 again, the next user attempting a Telnet connection succeeds.á When a Telnet connection attempt fails, the CPF87D7 message is sent to the system operator message queue on the Telnet serer system.á The CPF87D7 message indicates that the serer is not able to create a irtual deice. Additional information on this topic can be found in these sources: Deice system alues iseries system alues Configuring the Telnet serer Virtual controllers and deices created by the system When your system creates irtual deices, it follows these guidelines: The irtual controller is named QPACTLnn, where nn is an integer 01 or greater. The irtual deice is named QPACDEVxxxx, where xxxx is an alphanumeric character from 0001 to ZZZZ, with the exception of the letters a,e,i,o,u,y, allowing a maximum of 809,999 deices with unique deice names. User-selected names hae no restrictions on them. Note: If you want to use more than 32,500 deices, you can set the QAUTOVRT system alue to *NOMAX. The Telnet serer attempts to use existing irtual deices by matching the deice type and model. If no match is found, then a irtual deice is created. If necessary, the existing deice is deleted and recreated if it is not already in use. This applies to named deices (that is, when a specific deice is requested, rather than a default one assigned). This is true een if the named deice requested is of QPADEVxxx type. Telnet knows that a deice name was specifically requested and applies these rules to the QPADEVxxxx deice just like any other named deice. If your Telnet client supports deice naming, you can specify which deice to use. Otherwise, you can assign the deice name to a Telnet session with the Telnet exit programs. The exit program always oerrides any negotiated deice name. In this way, the system administrator always has final control oer the name assigned, simply by implementing the Telnet user exit program. The administrator can therefore block or oerride TN5250E requests if necessary. Actiating the QSYSWRK subsystem You can work with any subsystem by using Work Management in Operations Naigator. 1. Determine the status of the QSYSWRK subsystem a. In Operations Naigator, select the system you want to work with. b. Expand Work Management. c. Expand Subsystems. d. Locate the QSYSWRK subystem. It may be necessary to expand further to find this subsystem. 108 iseries: Getting started with iseries

e. The status of the subsystem is displayed in the right panel of the Operations Naigator window. 2. If the status is inactie, type STRSBS QSYSWRK on the command line to start the subsystem. 3. Start the Telnet serer job. The interactie subsystem needs to be actie. The default interactie subsystem is QINTER. Howeer, it may not be the subsystem that you hae created for interactie jobs. If you are not sure which subsystem you use for interactie jobs, type WRKSBSD *ALL. The Work Station Type Entries shows which deices are to be allocated to which subsystems. If you are using QINTER, start it by typing STRSBSQINTER. Interactie jobs can be sent to any subsystem, based on the deice name assigned to the job. To change the entries for a subsystem, use ADDWSE or RMVWSE. The spooling subsystem (QSPL) needs to be actie to run printer pass-through sessions. Additional information on this topic can be found in these sources: Work management: managing subsystems Printer security considerations Profile and passwords are not required for printer sessions. Howeer, they are required for a bypass of signon displays. The passwords can be encrypted if the Telnet client supports the function. The System Administrator can deny users printer sessions if necessary. Additional information on this topic can be found in these sources: Printing and deice programming Tips and Tools for securing your iseries Using remoeable media The iseries uses the following media for saing or restoring data: Tape CD-ROM Optical library To ensure a successful backup, it is important to handle and maintain the media properly. Using Tapes and Tape Units General Tape Usage Information Using CD-ROM Using CD-ROM Storage on page 116 Using Optical Media Libraries Using Optical Media Libraries on page 118 Additional information on this topic can be found in these sources: Tape drie enironment and use Using quarter-inch cartridges Using 1/2-Inch and Magstar MP Tape Cartridges Using 1/2-Inch and Magstar MP Tape Units Using 1/2-Inch and Magstar MP Tape Units on page 130 Using 8-Millimeter Tape Units Using 8-Millimeter Tape Units on page 128 Using 1/2-Inch tape reels Chapter 8. Managing system operations 109

Using tapes and tape units There are seeral types of tape cartridges and tape units that are commonly used on the iseries system: 1/4-inch tape cartridge and tape unit 8-mm tape cartridge and tape unit 1/2-inch tape cartridge and tape unit Magstar MP tape cartridge and tape unit You can also use 1/2-inch tape reel and tape unit on the iseries. Term Tape Cartridge Tape Reel Tape Drie Tape Unit Tape Library Description A tape cartridge is a case containing a reel of magnetic tape that can be put into a tape unit without stringing the tape between reels. A tape reel is a round deice on which magnetic tape is wound. A tape drie is a deice that is used to moe the tape and read and write information on magnetic tapes. A tape unit is a physical enclosure that contains the tape drie. The complete collection of tapes aailable for use on the system (including all new, scratch, used tape cartridges, or reels) is a tape library. For all tapes, you need to establish a procedure for maintaining a tape library which includes: Assigning each tape a unique olume ID. Each tape must hae a unique olume ID to maintain the accuracy of tape olume statistics as shown in monitoring tape olume statistics Monitoring Tape Volume Statistics on page 113. On barcoded tapes, the olume ID must match the bar code. Establishing a temperature and humidity controlled tape media storage area. Maintaining records for each tape olume including: Date the tape was purchased Problems encountered Correctie action taken Regardless of the type of tape you are using, follow these guidelines to aoid damage and loss of the data on the tape. Remember: Leae the reels or cartridges in their protectie container until you use them. Place reels or cartridges in the computer room for 24 hours before using them. Remoe the reel or cartridge from the tape unit when it is not in use. Store reels or cartridges in the protectie container. Copy and then throw away reels and cartridges that hae a high number of temporary errors. See monitoring tape olume statistics Monitoring Tape Volume Statistics on page 113 for information on how to obtain the number of errors. Operate tape units in a relatiely clean, dust-free enironment. Storing and operating tape media and tape deices in a dirty enironment may cause errors and early life failures. 8mm 160-meter tapes must hae media recognition system (MRS), or the tapes will not load. Apply an external label to the outside of each reel or cartridge and to the protectie container when you store data on a tape. These labels can be ordered separately. Record information such as: Name or number of the reel or cartridge Type of data stored on the reel or cartridge Date the data was stored on the tape 110 iseries: Getting started with iseries

Tape olume ID Do not: Carry cartridges loosely in a box or basket because the leader blocks can catch on other tapes and become unlatched. Stack more than six cartridges on top of each other. Open a cartridge. Release the leader block and pull the tape from the cartridge. Touch any exposed tape. Expose the tape to direct sunlight, moisture, or high magnetic fields. Drop the tape reel or cartridge. Apply an external label to the outside top of the cartridge or reel. This could interfere with the drie or media operation. Tapes, tape units, and diskettes are used primarily for saing and restoring system data. A tape unit is the physical enclosure that holds the tape drie. Verifying that your tape unit works correctly To erify that your tape unit is working correctly, do the following: 1. Remoe the reel or cartridge from the tape unit. 2. Type WRKCFGSTS *DEV *TAP on any command line and make the tape unit unaailable to the iseries (ary off). 3. Clean the tape unit. Refer to the cleaning instructions for the tape unit you are using. 4. Type the Verify Tape (VFYTAP) command on any command line and press Enter. Errors That Can Occur with Tape Units: If an error message appears during tape usage, you can put the cursor under the message, and press F1 or HELP. Then follow the instruction in the online help information to resole the problem. Using 1/4-Inch Tape Units: Internal tape features 7207 Model 122 The iseries system supports the following 1/4-inch tape units: For more information about the 7207 Model 122, refer to the following publication: SA37-0400, 7207 Model 122 4GB External SLR5 Quarter-Inch Cartridge Tape Drie Setup, Operator, and Serice Guide. Note: The tape unit installed in the 7207 Model 122 is functionally the same as the internal feature identified as QIC-4GB-DC. General Tape Usage Information Tape Volume, Initialization, and Volume ID A olume is a tape reel, a tape cartridge, or a diskette. Each olume must be initialized before data files can be recorded on the tape (or diskette) magnetic medium. A tape olume ID is a name or number identification that is recorded in a standard olume label at the beginning of the tape when a tape is initialized. Initializing Tape: Use the Initialize Tape (INZTAP) command to initialize a tape. When you run this command, a standard olume label is recorded at the beginning of the magnetic tape medium. When a tape is initialized, any information preiously recorded on the tape medium is erased and written oer with new information. Information is also written oer when new data files are appended to the newly recorded olume label. Chapter 8. Managing system operations 111

Note: Do not reuse an old tape olume if permanent read or write errors hae been detected more than two times. Also do not reuse an old tape olume if temporary read or write errors for that olume are excessie. To determine if temporary errors are excessie, see Monitoring Tape Volume Statistics. Commonly Used Parameters of the INZTAP Command: are: New olume identifier (Volume ID) Check for actie files Tape density The most commonly used INZTAP parameters New Volume Identifier (Volume ID) Use the new olume identifier parameter to proide a unique olume identification (ID) for a tape being initialized for use as a standard labeled tape. This parameter is required for tape cartridges. This option is not required by 1/2-inch tape reels. On the Initialize Tape display, type the olume identifier of your choice in the new olume identifier parameter. The identifier can be no longer than six characters in length and should not start with a *. Check for Actie Files An actie file has an expiration date that is equal to or later than the current date. Select one of three options to complete the parameter: Type *YES in the check for actie files parameter if you want all data files on the tape to be checked before the tape is initialized. If an actie file is found, the tape olume is not initialized and you receie an error message. Important: Check for actie files=*yes is the default option. The processing of tapes that hae a large file, or tapes that hae many files, may take a long time. The processing of 8-millimeter tapes may take up to 3.5 hours. Type *NO in the check for actie files parameter if you want the tape to be initialized immediately without checking for actie files. Use *NO when: The tape or data cartridge is new. You are sure you want the olume initialized and you want the INZTAP processing to complete in the minimum amount of time. You are sure you want the olume initialized and the INZTAP command failed when you entered *YES or *FIRST in the parameter field. IMPORTANT:If you type *NO in the Check for actie files parameter, the system writes oer all data that is on your tape. Make sure the tape cartridge you are using is new. If the tape you are using is not new, be certain that you want the tape olume initialized regardless of the data that is on the tape. Type *FIRST in the check for actie files parameter if you want to check only the first file on the tape. If this file is actie, the tape olume is not initialized. The processing time for this parameter option depends on the size of the first file on the tape. Tape Density The tape density parameter determines the amount of data recorded per inch of tape. The choice of density also changes the format of 1/4-inch and 8-mm tape cartridges. If you are initializing two or more reels or cartridges for a multi-olume SAVE operation, the density and format of all olumes must be the same. Clear 112 iseries: Getting started with iseries

The clear parameter is used to erase all of the data on the tape medium that follows the standard olume label record at the beginning of the tape. The Magstar MP, 1/2-inch, and all 1/4-inch tape dries except the QIC-5010 tape drie hae an erase head that erases all data tracks in one pass. The QIC-5010 1/4-inch tape drie and the 8-mm tape drie erases at the normal write speed. This can take a ery long time. Note: Using the clear parameter to erase QIC-5010 1/4-inch tapes and 8-mm tapes is not recommended because the process time for erasing 8-mm tapes can be up to 3.5 hours. Copying Tapes To copy a tape: 1. You must hae two tape dries. 2. Make sure the tape units are turned on. 3. Load the tape to be copied into one tape unit. 4. Load the tape receiing the information in the other tape unit. Note: If the tape that receies the information is new, you must initialize it before continuing. See Tape Volume, Initialization, and Volume ID Tape Volume, Initialization, and Volume ID on page 111 for information on how to initialize a tape. 5. Enter the Duplicate Tape (DUPTAP) command and press F4 (Prompt). 6. Specify the name of the tape unit from which the information is to be copied in the From deice (FROMDEV) parameter. 7. Specify the name of the tape unit to which the information is to be copied in the To deice (TODEV) parameter. 8. Press Enter. A message is displayed when it is time to insert a new tape. Monitoring Tape Volume Statistics To ensure that your tapes are in good condition, you should monitor the tape olume statistics on your iseries system. 1. Use the Start System Serice Tools (STRSST) command. 2. Select option 1 (Start a serice tool) on the System Serice Tools menu. 3. Select option 1 (Product Actiity Log) on the Start a Serice Tool menu. 4. Select option 4 (Work with remoable media lifetime statistics) on the Product Actiity Log menu. 5. Select the type of remoable media for which you want data on the Select Media Option display. The Work with Lifetime Statistics display appears. +--------------------------------------------------------------------------------+ Work with Lifetime Statistics Remoable media...... : 1/4 inch cartridge tape Type options, press Enter. 4=Delete entry 6=Print entry Volume --Temporary Errors--- --------K Bytes------- Option IDRead Write Read Written >>PHB021 23452450 23450 23457123 97689690 THB021 2 0 14307 0 AIPLT 0 3 214494 137546 AD0000 0 0 3 0 AIPL 0 0 2 27620 IVIHE 0 0 1 0 MM 0 0 361 0 PHB031 0 0 2 0 PTFFIX 0 0 3 432 F3=Exit F5=Refresh F10=Delete all F11=Print all F12=Cancel Chapter 8. Managing system operations 113

(C) COPYRIGHT IBM CORP. +--------------------------------------------------------------------------------+ 6. If you see the following symbols preceding the olume ID on the Work with Lifetime Statistics display, take the appropriate action: Symbol Explanation Action to take >> Media replacement recommended Copy the contents of the media to a new tape and discard the old tape. > Media approaching replacement criteria Replace the tape if the tape format is: QIC-120 7208 2.3GB 6250 bpi density If the tape format does not fulfill the aboe conditions, continue to monitor this tape to ensure that media replacement is not necessary. Note: To ensure accurate statistics, each tape cartridge or reel must hae a unique olume ID. When to Clean After 400 MB of data transfers hae occurred for the olume ID, the Error Log Utility uses the following guidelines to determine whether a particular tape should no longer be used. Discard tape reels and tape cartridges that hae a permanent read or write error. If all tapes used in a single drie exceed the criteria that follows this list, the read/write head are probably dirty and should be cleaned. If a specific tape exceeds the criteria that follows this list, copy the contents to a new tape and discard the old tape. Storage Deice Ready Conditions Use the table below if you are haing trouble making a deice ready. All the conditions listed for each deice must be correct for the deice to be ready. If you are not able to make a deice ready, contact your serice representatie. Storage Deice Ready Conditions Tape Unit Ready Description Reference Information 2440 Power light is on Tape is loaded Status display shows A 0 Online light is on IBM 2440 Magnetic Tape Subsystem Operator s Manual G571-0149. 114 iseries: Getting started with iseries

Tape Unit Ready Description Reference Information 1/4-inch Tape cartridge is inserted. The tape cartridge must be changed or, to reuse the same cartridge, the tape cartridge must be reloaded under the following conditions: - The tape unit was made unaailable (aried off). - The tape application program ended with the *UNLOAD option. 7208/6390 8mm Power light is on Tape cartridge is inserted Ready light is on See the appropriate operator s guide for your specific model. 9347 Power light is on Load/Rewind light is on Online light is on 7208 20 GB External 8mm Tape Unit Model 342 Setup and Operator s Guide, SA37-0319. 9348 Power light is on Tape is loaded Status display shows 00 A002 Online light is on 9348 Customer Information, SA21-9567. 3422/3430 Power light is on Enable/Disable switch is set to the Enable position Tape is loaded Ready light is on IBM 3422 Magnetic Tape Subsystem Operator s Guide, GA32-0090. 3480/3490/3490E Power light is on DC Power light is on Control unit Online switch is set to the Online position Control unit Normal/Test switch is set to the Normal position Control unit channel Enable/Disable switch is set to the Enable position Tape unit Online/Offline switch is set to the Online position Tape is loaded Tape unit displays Ready U or Ready F See the appropriate operator s guide for your specific model. 3570/3590 Tape is loaded Tape unit displays Ready Chapter 8. Managing system operations 115

Using CD-ROM Storage The CD-ROM drie is a read-only drie. The feature code for the iseries CD-ROM drie is 6320 or 6321. The figure below shows the CD-ROM dries on the 9402/9404 Models 4xx and 9404/9406 Models 5xx. Note: The CD-ROM drie on the iseries system is not enabled for the digital audio disc. Loading and unloading a CD 1. Remoe the CD from the protectie case. RV3P172-0 2. Slide the CD into the CD tray with the label side showing. If your CD-ROM is ertically positioned, make sure that the CD is secured by the two tabs at the bottom of the CD tray as shown on the left in the following illustration. 116 iseries: Getting started with iseries

3. When you hae properly positioned the CD in the CD tray, press the Eject button or push the tray into the CD-ROM drie. RV3P174-0 4. To remoe the CD from the CD-ROM drie, press the Eject button. RV3P175-0 Cleaning No preentie maintenance is necessary for the CD-ROM drie. Always handle discs by the edges to aoid finger prints. Discs can be wiped with a soft lint-free cloth or lens tissue. Always wipe in a straight line from the inner hub to the outer rim. Verify Optical Deice The Verify Optical(VFYOPT) command can be used to detect hardware errors, or erify whether a problem has been resoled. This function can be used to erify a CD-ROM drie or a directly attached optical media library deice. To use this function, do the following: 1. On any command line, type VFYOPT DEV(xxxxxxxxxx) where xxxxxxxxxx is the deice name. A display is shown with instructions on how to perform erification test. Chapter 8. Managing system operations 117

2. Follow the instructions, and press the Enter key. The erification test is run. If the test completes successfully, you will receie a message about the successful completion. If hardware errors occur during the test, you will receie an error message. Using Optical Media Libraries The IBM 3995 Optical Library Dataserer is a storage deice for the iseries system that proides remoable and permanent storage of information on optical media. The 3995 Optical Library lets you access data right at your work station. It is an alternatie to retrieing data that is traditionally kept on paper, stored on diskette, stored on microfilm, or stored on magnetic tape. If you are using the 3995 Optical Media Library and would like more information, see the following manuals: IBM 3995áAS/400 Optical Library Dataserer: Operator s Guide Models 142 and 042, GA32-0140 Optical Support Tape Drie Enironment and Use IBM s goal is to proide you with a product that you can configure and use reliably. Tape dries require specific maintenance and enironmental conditions to operate well oer time. Using high quality, data grade media, handling and storing this media properly, operating the tape drie in a clean enironment and keeping the tape drie properly cleaned can help you to aoid problems with your IBM tape drie. Media Grades IBM uses two different grades of media. We supply program temporary fixes (PTF) on a tape that is designed to be written to only once and read from a few times. This tape is designed for limited use, not as a backup medium. IBM also sells media that are designed for storage use. IBM supports the tape that we sell. If analysis by IBM serice personnel indicates a problem with non-ibm media, it may be necessary for the customer to replace the media. Tape Handling and Storage Most tape arries in a sealed cartridge so that the tape will remain in a clean enironment. Opening the cartridge allows dirt and airborne particles to enter and then become a source of contamination. Only the tape drie should open the cartridge; not an operator. Inside the cartridge, the tape is under proper tension. If the cartridge is dropped, this tension will be relaxed. Inserting a dropped cartridge into a tape drie can cause incorrect loading and result in a jam. This will ruin the tape and can cause physical damage if the cartridge is not remoed properly. To store the tapes properly, put them in their protectie containers and store them on their ends. The storage area must be clean, dry, normal room temperature and away from any magnetic fields. Enironmental Issues Tape dries are designed to operate in a clean enironment. Problem factors are dirt, dust, fibers, and airborne particles. Airborne particles are the most difficult to address. When you install a tape in the tape drie, the clearance between the heads and the tape is measured in microns. Particles can damage the tape or the head if they come in contact with either. IBM offers a tape drie filter enclosure for some systems to sole this problem. The enclosure draws air in through a filter and supplies the tape drie with clean air. Customers are responsible to proide a clean operating enironment for the tape drie and system. Tape Drie Cleaning Dirt may build up on the heads of any tape drie, no matter how clean the enironment. Eery time tape motion occurs, some of the media surface comes off on the heads. Oer time, this builds up and causes errors in reading and writing. 118 iseries: Getting started with iseries

We only recommend that you use IBM cleaning cartridges for IBM tape dries. You can use cleaning cartridges a limited number of times. Once a cleaning cartridge has been used to its maximum number of times, the usefulness of the cartridge expires. When cartridges expire, replace them. Neer reuse an expired cleaning cartridge. Doing so allows preiously remoed dirt to be reintroduced to the tape drie. When you hae cleaned the tape drie, mark the usage on the cartridge in order to best determine when your IBM cleaning cartridge has expired. Microcode Updates IBM constantly works to proide the best possible tape drie products. To make certain that the dries work their ery best, IBM occasionally releases changed microcode for the tape dries. When a microcode change is deeloped, IBM makes it aailable to you through the serice organization or by electronic deliery. Microcode changes are also aailable by downloading and installing fixes using Electronic Customer Support, or by ordering and installing cumulatie fix packages from IBM Global Serices. Summary Install your tape drie in the cleanest possible enironment. IBM tape dries require high quality, data grade tapes, and cleaning on a regular basis. Store and handle media properly. Improper use, storage, or handling of tape dries or media may oid your IBM warranty, or serice agreement. If a tape drie stops functioning due to a component failure during the tape drie warranty or maintenance time, IBM will replace the tape drie unit. IBM will replace any defectie tape drie under the terms and conditions of the IBM warranty or serice agreement. It is our objectie to work with you to identify the cause of any tape drie problems and proide a solution. Using 1/2-Inch and Magstar MP Tape Cartridges Before You Start: Inspect the cartridge and do not use it if: The cartridge case is cracked or broken. The leader block or the latch is broken. The file-protect selector is damaged. The cartridge case contains any liquid. The cartridge case has any other obious damage. The tape is wound completely out of the cartridge onto the machine reel and then reattached to the cartridge reel by the serice representatie. This repair is temporary and permits the cartridge to be loaded one time so that the data can be copied on a replacement cartridge. Note: If you hae a damaged cartridge, substitute a backup ersion of the data from another cartridge. If the cartridge has a detached leader block but no other damage, you can repair the cartridge with the IBM Leader Block Repair Kit. If dirt appears on the external surface of a cartridge, lightly moisten a lint-free cloth (IBM part 2108930) with IBM cleaning fluid (IBM part 8493001), or its equialent, and wipe the outside surfaces. Important: Do not allow anything wet, including the cleaning fluid, to contact the tape. Make sure all cartridge surfaces are dry and the leader block is snapped into place before you load the tape cartridge. Protecting Data Stored on 1/2-Inch Tape Cartridge To protect the data, roll the thumbwheel selector on the side of the cartridge left or right until it is in the correct position. Chapter 8. Managing system operations 119

The 3570 and 3590 data cartridges are preformatted with data sero tracks. These cartridges should not be bulk erased. The 3570 and 3590 tape deices hae control data at the beginning of each cartridge. The deice updates (writes) this region eery time a cartridge is loaded. As a result, the deice display will state writing een if you hae file protected the cartridge. This data is separate from the user data. Note: For more detailed information about using 1/2-inch tape cartridges, see Care and Handling of the IBM Magnetic Tape Cartridge GA32-0047 Protecting Data Stored on Magstar MP Tape Cartridge To protect the data, slide the file protect selector on the end of the cartridge until it is in the correct position. Note: For more detailed information about using Magstar MP tape cartridges, see the IBM 3570 Magnetic Tape Subsystem Operator s Guide Using 1/4-Inch Cartridges The image below shows a 1/4-inch tape cartridge and the box used for storage. Attention: Do not attach labels to the edges of the 1/4-inch tape cartridges; this may interfere with the cartridge sensors and cause the tape to run off the end of the spools. Tape Cartridge and 1/4-Inch Tape Unit Compatibility: For full read/write capability, follow the guidelines in the table below to determine which tape cartridges to use for each tape unit. Compatibility Between Tape Cartridges and Tape Units Capacity and Date Rate by Media Type/Format Read/Write Support by Tape Unit Feature Code Number 1,2 Media Type (IBM P/N) iseries Format (density) Data Capacity Compaction3 and Data Rate4 6380 6480 6381 6481 4482 4582 6382 6482 4483 4583 6383 6483 6385 6485 4486 4586 6386 6486 MLR3-25GB (59H4128) MLR3 Yes 2.5GB 2.0MB/s No No No No No R/W 120 iseries: Getting started with iseries

Capacity and Date Rate by Media Type/Format Read/Write Support by Tape Unit Feature Code Number 1,2 MLR1-16GB (59H4175) DC5010 (16G8574) SLR5-4GB (59H3660) SLR5-4GB (59H3660) QIC5010 Yes 16GB 1.5MB/s QIC5020 Yes 13GB 1.5MB/s QIC4DC Yes* 8GB 760KB/s QIC4GB No 4GB 380KB/s DC9250 (16GB8436) QIC2DC Yes* 5GB 600KB/s DC9200 QIC2DC Yes* 4GB (16G88541) 600KB/s DC9250 (16G8436) DC9200 (16G8541) DC9120 (21F8730) DC9100 (16G8539) DC6525 (21F8597) DC6320 (21F8583) DC6150 (21F8578) DC6150 (21F8578) QIC2GB No 2.5GB 300KB/s QIC2GB No 2GB 300KB/s QIC1000 No 1.2GB 300KB/s QIC1000 No 1GB 300KB/s QIC525 No 525MB 200KB/s QIC525 No 320MB 200KB/s QIC120 No 120MB 120KB/s QIC24 No 60MB 92KB/s No No No R/W R/W R/W No No No R/W R/W R/W No No R/W R No R No No R/W R No R No R/W R/W R No R No R/W R/W R No R R/W R/W R/W R R/W R R/W R/W R/W R R/W R R/W R/W R/W No R/W No R/W R/W R/W No R/W No R/W R/W R/W No R/W No R/W R/W R/W No R/W No R/W R/W R/W No R/W No R R No No No No 1. Refer to Recommended cleaning cartridges to correlate the tape unit feature code number to the tape unit front bezel label. 2. In the Tape Unit Feature Code # columns, R/W indicates both read and write support of the associated media type and format. An R indicates read only. No indicates that the media type and format is not supported. 3. Data Compaction is a term used to describe a data recording option for compacting (or compressing) data prior to writing to the tape media. Selecting the data compaction option will usually result in an increase in both capacity and data transfer rate. The typical compaction ratio is 2:1, but is dependent upon the type of data. A Yes in the Data Compaction column means that the associated media type and format supports data compaction. The OS/400 SAVE command parameter COMPACT is used to select the data compaction option, except for those cases identified by a Yes*. A Yes* indicates that the compaction option is controlled entirely by the format (density) that is selected during the tape initialization operation. The OS/400 SAVE command parameter COMPACT will hae No effect in these cases. QIC2DC is a compaction format (density) for the DC9250 and DC9200 media type. QIC4DC is a compaction format (density) for the SLR5-4GB media type. 4. Cartridge capacities and data transfer rates shown are for non-compacted data, except for the QIC4DC and QIC2DC cases. For the QIC4DC and QIC2DC formats (densities), the capacities and the data transfer rates shown assume a typical 2:1 data compaction. See Note 2. If the QIC format and the tape cartridge are not compatible, an error message displays. Errors that can occur are: Chapter 8. Managing system operations 121

Selecting a QIC format that cannot be written on the tape. For example, inserting a DC6150 tape cartridge and specifying a QIC1000 format. Attempting to process a high density tape cartridge in a low density tape unit. For example, you try to process an SLR5-4GB cartridge in a 6381 tape unit. Attempting to add a file and selecting a QIC format different from the format preiously recorded on the tape. For example, inserting a tape cartridge recorded in QIC525 format and specifying a QIC120 format. Note: When purchasing non-ibm tape cartridges, purchase a small quantity to erify the tape quality. Quality tape reduces the possibility of tape cartridge problems. Loading 1/4-Inch Tape Cartridges: To load a 1/4-inch tape cartridge in a QIC-4GB-DC, QIC-2GB(DC), or QIC-2GB tape unit: 1. Push the pushbutton on the tape unit door to release the door. 2. Pull the tape unit door out, then push it down. 3. Insert the tape cartridge into the tape unit. The cartridge should be inserted firmly until it cannot go any further into the tape unit. About 10-mm (3/8 inch) of the cartridge remains outside the tape unit. 4. Lift up the tape unit door, then push it closed. The cartridge does not go all the way into the tape unit until the tape unit door is closed. Use moderate force to close the door. Slamming the door shut may damage the tape unit. Push the door until the latch holds the door closed. To load a 1/4-inch tape cartridge in an MLR3 or an MLR1 tape unit, insert a tape cartridge through the coer door until the loading mechanism pulls the cartridge into the drie. This allows the door to close. For older tape cartridge types, the 1/4-inch tape units run a retension operation wheneer a tape cartridge is loaded. The tape unit will also run a retension operation if a tape cartridge is in the tape unit when the door is closed. Retension means that the tape unit moes the tape to the end-of-tape position and rewinds it to the beginning-of-tape position. The retension operation is part of the load sequence. When using MLR3-25GB, DC5010, and MLR1-16GB tape cartridges, the tape units run the retension operation only when necessary (as determined by the tape unit) to maintain correct tape tension. The approximate retension times are as follows: Retension Times for 1/4-Inch Tape Cartridges Tape Cartridge MLR3-25GB MLR1-16GB DC5010 SLR5-4GB DC9250 DC9120 DC6525 DC6320 DC6150 Approximate Retension Time Less than 8 minutes Less than 8 minutes Less than 6 minutes Less than 8 minutes Less than 4 minutes Less than 4 minutes Less than 4 minutes Less than 3 minutes Less than 3 minutes Unloading 1/4-Inch Cartridges: Important: For the QIC-4GB-DC, QIC-2GB(DC), or QIC-2GB tape unit, do not remoe a tape cartridge if the tape unit status light is green. For the MLR3 and MLR1 tape units, do not remoe a tape cartridge if the tape unit actiity light is on. Only a cleaning cartridge can be remoed when the status light is green or the actiity light is on. If you remoe a tape cartridge while the status light is green, or the actiity light is on, you may hae the following problems: 122 iseries: Getting started with iseries

A system message indicates that an error has occurred and the tape job must be repeated. You may not be able to retriee data already on the cartridge because end-of-tape processing did not complete. To unload the MLR3 or MLR1 1/4-inch tape unit, wait until the actiity light is off. Press the unload button. The tape drie rewinds the tape, unloads and ejects the tape cartridge. If the tape cartridge cannot unload and has to be remoed manually from the tape drie, contact your serice representatie. To unload 1/4-inch tape cartridges from the QIC-4GB-DC, QIC-2GB(DC), or QIC-2GB tapes units: 1. Push the pushbutton on the tape unit door to release the door. 2. Pull the tape cartridge unit door out, then push it down. Moderate force is necessary to fully open the door with the tape cartridge in the tape unit. Excessie force damages the tape unit. 3. Grasp the tape cartridge and pull the cartridge straight out of the slot. Turning the cartridge or pulling too hard may damage the door mechanism. 4. Lift up the tape unit door, then push it closed. Little force is required to close and latch the door when the tape unit is empty. Moderate force is required when a tape cartridge is in the tape unit. Be sure to close the door on the first attempt. If the door does not close completely and pops open, the tape drie may receie two retension commands. This condition may cause an error which requires an initial program load (IPL) to recoer. If you remoe the tape cartridge while the green light is on, turn the light off by: Inserting the cartridge again. Run the Check Tape (CHKTAP) command and specify *REWIND for the End of tape option (ENDOPT) parameter. Remember: Do not remoe a tape cartridge from the tape unit unless the last command was run with *REWIND or *UNLOAD specified for the End of tape option (ENDOPT) parameter. If the last command ends with *LEAVE, the tape unit heads might be oer a data area. To aoid this, specify *REWIND or *UNLOAD for the End of tape option (ENDOPT) parameter of the last tape command. You may also use the Check Tape (CHKTAP) command with *REWIND specified for the End of tape option (ENDOPT) parameter. Tape cartridges can be left in the drie for seeral hours or oernight if: The green light is off (*REWIND is specified for the End of tape option (ENDOPT) parameter). The room temperature does not ary by more than 9.5 C (15 F). Humidity leels are within the range that is shown in the table in Shipping, Storage, and Operating Enironments for 1/4-Inch Tape Cartridges Shipping, Storage, and Operating Enironments for 1/4-Inch Tape Cartridges on page 127. Status Lights for MLR3 or MLR1 Tape Units: The MLR3 and the MLR1 tape units hae three indicator lights: two green and one amber. These status lights are turned on and off in arious combinations to indicate the status of the tape unit. Chapter 8. Managing system operations 123

The symbols that are located next to the status lights are the International Organization for Standardization (ISO) symbols that define the general function of the status lights as follows: (A) (B) (C) Ready. This light indicates the following conditions: Off - No cartridge installed or no fault condition Green - Cartridge installed, loading or unloading Green flashing - Power on self-test in progress. Actiity. This light indicates the following conditions: Off - No cartridge installed. No actiity or fault condition Green flashing - Cartridge actiity Fault. This light indicates the following conditions: Off - No fault condition Amber - Cleaning required or worn tape media Amber flashing - Fault condition The arious on/off combinations of the status lights are shown in the following chart. 124 iseries: Getting started with iseries

Chapter 8. Managing system operations 125

Cleaning the 1/4-Inch Tape Unit: The 1/4-inch tape unit requires periodic head cleaning. Cleaning the tape unit read/write head is important. This cleaning preents a build up of debris that could cause unrecoerable errors when writing or reading data. In general, the clean the head after eery 8 hours of tape moement when using IBM tape cartridges. Other tape media may require cleaning more frequently. If using new tape cartridges it is adisable to clean the head after two (2) hours of tape moement, or before loading each new tape cartridge. Note: System messages are posted when the tape unit determines that cleaning is required. The MLR1, MLR1-S, and MLR3 tape units also hae a cleaning status light that indicates that cleaning is required. It is ery important to respond to these cleaning indicators and clean the head using a recommended cleaning method. Use the IBM Cleaning Cartridge Kits as recommended below. Recommended IBM Cleaning Cartridges Tape Unit Identification Front Bezel Label MLR3 4486 4586 6386 6486 MLR1 QIC-5010-DC 6385 6485 MLR1-S QIC-5010-DC Feature Code Numbers 4483 4583 6383 6483 QIC-4GB-DC 4482 4582 6382 6482 Recommended IBM Cleaning Cartridges P/N 59H4366 Note 1, 2 P/N 46G2674 Note 1 Yes No No Yes Yes No Yes Yes No Yes Yes Yes QIC-2GB (DC) 6381 Yes Yes Yes 6481 QIC-2GB 6380 Yes Yes Yes 6480 Notes: 1. The cleaning cycle takes place automatically when the cleaning cartridge is loaded. P/N 16G8572 For the MLR1, MLR1-S, and MLR3 tape units, the amber actiity light flashes at a rate of 2 cycles per second during the cleaning operation. For the QIC-4GB-DC, QIC-2GB (DC), and QIC-2GB tape units, the status light flashes at a rate of 1 cycle per second during the cleaning operation. After the flashing stops, remoe the cartridge. 2. The MLR3 tape unit uses an enhanced cleaning procedure. The duration of this procedure is approximately three (3) minutes. Protecting Data Stored on 1/4-Inch Tape Cartridges: To protect data from being oerwritten: Set the pointer toward SAFE for older style tape cartridges, as shown in the first image below. Set the pointer toward the locked padlock icon for the newer style tape cartridges, as shown in the second image below. 126 iseries: Getting started with iseries

To not protect the data: Set the pointer away from SAFE for the older style tape cartridges, as shown in the first image below. Set the pointer toward the unlocked padlock icon, for the newer style tape cartridges, as shown in the second image below. SAFE Write-Protected OR SAFE Not Write-Protected RV2P749-0 Write-Protected OR Not Write-Protected RV2P986-0 Shipping, Storage, and Operating Enironments for 1/4-Inch Tape Cartridges The recommended enironment for operation, storage, and shipment of 1/4-inch tape cartridges is a temperature of 15 to 25 C (59 to 77 F), and a relatie humidity of 40 to 60%. The table below proides maximum and minimum enironmental conditions for safe shipment, storage, and use of the tape cartridges for an iseries tape unit. A hyphen (-) indicates that the dry bulb temperature is outside the recommended range for safe operation, storage, or shipment. Chapter 8. Managing system operations 127

Enironment Ranges for 1/4-Inch Tape Cartridges Dry Bulb Temperature Degrees Relatie Humidity (Percent) Celsius Fahrenheit Operating Storage Shipping -40-40.2 - - 20to80 10 50 20 to 80 20 to 80 20 to 80 20 68 20 to 80 20 to 80 20 to 80 30 86 20 to 55 20 to 73 20 to 73 40 104-20to32 20to32 Using 8-Millimeter Tape Units The iseries supports the following tape units: 7208 Models 002, 012, 222, 232, 234, and 342 9427 Models 210, 211 Feature Code 6390 The 7208 Models 002, 012, 222, 232, 234, and 342 are external tape units for the iseries System Units. For the 7208 Model 002, refer to the following publication: IBM 7208 Model 002 2.3GB External 8mm Tape Operator Guide SA23-2675. For the 7208 Model 012, refer to the following publication: IBM 7208 5.0GB External 8mm Tape Unit Model 012 Operator Guide, SA26-7036. For the 7208 Model 222, refer to the following publication: IBM 7208 7.0GB External 8mm Tape Unit Model 222 Operator Guide, SA26-7117. For the 7208 Model 232 and 234, refer to the following publication: IBM 7208 External 8mm Tape Subsystem Models 232 and 234 operator s Guide, SA26-7104. For the 7208 Model 342, refer to the following publication: IBM 7208 20GB External 8mm Tape Unit Model 342 Setup and Operator Guide, SA37-0380. Note: The 7208-342 can read tapes written at the 2GB, 5GB, or 7GB formats. Howeer, if a 20GB tape is inserted after the drie has been using a lower density tape, the 20GB tape is ejected and the drie will post a must clean message. The drie must be cleaned using the correct cleaning cartridge before it may be used again. For the 9427 Models 210 and 211, refer to the following publication: IBM 7208 External 8mm Tape Subsystem Models 210 and 211 operator s Guide, SA26-7108. The feature code 6390 is an 8mm tape unit that is internal to the iseries. Status Lights for 8MM Tape Units: The 8mm tape units that support the 5.0GB, 7.0GB or 20GB format hae three indicator lights: two green and one amber. These status lights are turned on and off in arious combinations to indicate the status of the tape units. 128 iseries: Getting started with iseries

RV3P177-0 The symbols located next to the status lights are the International Organization for Standardization (ISO) symbols that define the general function of the status lights as follows: (A) (B) (C) Disturbance. The amber status light flashes wheneer the tape unit encounters an irrecoerable fault. It is on solid wheneer the tape drie requires cleaning. Ready. The green status light is on solid wheneer the tape unit is ready to receie the tape backup commands. Read-Write. The green status light flashes wheneer the tape unit is moing the tape. The arious on/off combinations of the status lights are shown in the following chart. Chapter 8. Managing system operations 129

Status Lights State On On On Status The Power-on Self Test (POST) is running or the system has issued a reset to the drie. Note: The POST condition can occur either when the power is first applied or after use of the diagnostic cartridge. Off Off Off One of the following has occurred: 1. The power is off. 2. The POST has completed successfully but no tape cartridge was inserted. Off Off A tape cartridge has been inserted and the tape drie is performing a tape load/unload operation. Flashing Off On The tape load operation has completed and the tape drie is ready to receie commands from the system. Off Off On The tape is in motion and the tape drie is busy running a deice operation. Flashing Flashing Off Off The flash rate is fast (4 flashes per second) when using the test cartridge. The flash rate is slow (1 flash per second) when the tape drie has detected an internal fault that requires correctie action. Refer to your Serice Guide or contact your serice representatie. or or On Off or On Off or Flashing The tape path requires cleaning. RV3P176-1 Using 1/2-Inch and Magstar MP Tape Units The iseries supports the following 1/2-inch tape units: 3480 3490 3490E 3494 3590 130 iseries: Getting started with iseries

The iseries supports the following Magstar MP tape units: 3570 Tape Unit with Automatic Cartridge Loader: with the automatic cartridge loader: There are two ways that tape cartridges can be loaded Manual Mode: You insert tape cartridges one at a time by pressing the Start key. Auto Mode: You can preload multiple tape cartridges. The tape cartridges will automatically load when the preious cartridge is unloaded. Note: For the 3570, 3490Fxx, 3590, and 3494, the tape deice supports a random mode of operation. In random mode, the tape deice operates as a tape library. Tape libraries require special considerations. For more information, see the following book: Automated Tape Library Planning and Management. Sharing Systems with a 3480, 3490, 3490E, or 3590 Tape Unit: units can be attached to: One or two input/output processors on the same iseries system. Two iseries systems. An iseries system and a System/390*. The 3480, 3490, 3490E, or 3590 tape You can choose whether or not you want your 3480, 3490, 3490E, or 3590 tape unit assigned to an iseries system when the tape unit is aried on (made aailable for intended use). Assigning a tape unit reseres the tape unit specifically for one system. To assign a 3480, 3490, 3490E, 3570, or 3590 Tape Unit: 1. Use the Work with Deice Description (WRKDEVD *TAP) command to work with a tape deice description. in the Assign deice at ary on field and press Enter to assign the tape unit to the system. Note: *YES is the default for Version 2 Release 3. For Version 2 Releases 1 and 2, the assign deice at ary on parameter was not optional. For releases prior to Version 2 Release 1, the assign function did not exist. 2. Use the Vary Configuration (VRYCFG) command to ary off the tape unit. Note: The Vary Configuration (VRYCFG) command can be run by using the VRYCFG command or by using the Work with Configuration Status (WRKCFGSTS) command. To use the Work with Configuration Status command, type WRKCFGSTS *DEV *TAP and press Enter. 3. Use the VRYCFG command to ary on the tape unit and assign it to the system. If the tape unit is being used by the other system, a message is displayed that indicates the tape unit is assigned elsewhere. The tape unit must be aried off (made unaailable) at the other system before it can be aried on (made aailable) at a new system. To leae a tape unit unassigned: 1. Use the Work with Deice Description (WRKDEVD *TAP) command to work with a tape deice description. In the Assign deice at ary on field and press Enter to leae the tape unit unassigned. Remember: A tape unit that is unassigned may be aried on to both systems. The operator must control the tape application programs so that the two systems do not interfere with each other. The results of failing to control the tape application programs may be unpredictable. 2. Use the Vary Configuration (VRYCFG) command to ary off the tape unit. 3. Use the VRYCFG command to ary on the tape unit. Chapter 8. Managing system operations 131

Remember: When a tape unit is being shared by two iseries systems, the tape unit can only be in VARY ON status on one system at a time. To use a drie, ary it on by typing the following on any command line and pressing Enter: VRYCFG CFGOBJ(TAPxx) CFGTYPE(*DEV) STATUS(*ON) If you do not want to ary on tape units during future IPLs, type the following on any command line and press Enter: CHGCTLTAP CTLD(TAPCTLxx) ONLINE(*NO) After doing an IPL, to ary on only the controller, type the following on any command line and press Enter: VRYCFG CFGOBJ(TAPCTLxx) CFGTYPE(*CTL) STATUS(*ON) RANGE(*OBJ) 1/2-Inch and Magstar MP Tape Unit Addressing: For a 34xx or 35xx tape deice attached to a type 6501 or 6534 IOP or a type 2729 IOA, the SCSI address must be set to 0 when the deice is used for IPL. The SCSI address can be set to any address except 7 when the deice is not being used for initial program load. For a 34xx tape deice attached to a type 2644 IOP, the controller address must be set to address 7. The deice address must be set to address 0 when the deice is used for IPL. Address 8 can be used when there is no deice at address 0. The controller and deice can be set to any alue when the deice is not being used for IPL. Backing Up and Restoring Data with the 1/2-Inch and Magstar MP Tape Unit: The 3480, 3490, 3490E, 3570, or 3590 attached tape unit is most often used to back up and restore data. You can use multiple tape units to back up and restore data plus the automatic cartridge load function to do an unattended backup. When using multiple tape units, the sequence of tape media used is across the tape units: the first tape is on tape unit 1, and the second on tape unit 2. For example, if you use the 3490 tape unit (model D32) with the automatic cartridge load function to back up the data, 12 cartridges can be loaded using the automatic cartridge load function. When the job is complete, tapes 1, 3, 5, 7, 9, and 11 are in tape unit 1. Tapes 2, 4, 6, 8, 10, and 12 will be in tape unit 2. To restore the data, the odd-numbered tapes must be loaded into tape unit 1 and the een-numbered tapes in tape unit 2. Before backing up data, all tapes should be initialized on the model and type of tape unit that will be used to do the backup. Tapes that are initialized on other tape units may not be recognized by the system. Tapes that are initialized on a 3490 D3x tape unit cannot be used on 3490E D4x or Cxx tape units. Cleaning the 3480, 3490, 3490E, and 3590 Tape Unit: On the aerage, clean the tape path on each drie eery seen days. If you use an unusually large amount of tape, clean the tape path more often. If the drie displays a *CLEAN message, clean the tape unit path as soon as possible. You should also clean the tape path after each initial program load (IPL), after a drie is reset, or wheneer the power on the tape drie has been interrupted. To clean the tape path, insert the special cleaning cartridge as you would a normal tape cartridge. The part number for the 3490 cleaning cartridge is 4780527. The part number for the 3590 cleaning cartridge is 05H4435. Keep track of the number of uses on the label proided with each cleaning cartridge and then throw the cartridge away after 500 uses. Tip: 1. Do not use a grease pencil on the label. 2. The cleaning cartridge should be undamaged and clean when it is inserted into a tape unit. 132 iseries: Getting started with iseries

If your tape unit has the automatic cartridge loader feature, put the cartridge into the feed position and press the start pushbutton. The cleaning cartridge can also be put into the input stack, and the cleaning procedure takes place wheneer the cleaning cartridge is loaded into the drie. If you start cleaning during a job, an inquiry message is displayed. After responding to the message, the drie threads the cleaning tape, cleans the read/write head, and then rewinds and unloads the cleaning cartridge. When the cartridge has been unloaded, remoe it and mark the usage label. Cleaning the 3490 Fxx, 3494, and 3570 Tape Units: These tape units proide random access to the tape cartridges. When the deice detects that cleaning is needed, the tape unit will perform the cleaning operation automatically, if the cleaning cartridge is in the internal cell (known only to the Random Access Cartridge Loader). The tape unit keeps track of the number of cleaning operations performed by the cleaning cartridge and ejects the cleaning cartridge through the priority cell when the cleaning cycles allowed for the cleaning cartridge hae been used up. The part number for the 3590 Tape Cleaning Cartridge is 05H4435. The part number for the 3570 Tape Cleaning Cartridge is 05H2463. Using 8-Millimeter Tape Cartridges The following are the cartridges you can use in the 8-mm tape unit: Cartridge Name Description Notes Test Cartridge #21F8577 Test Cartridge #21F8577 is used to write test data onto a tape cartridge. The tape unit reads the recorded data to check the write operation. Do not use this cartridge to sae programs or data. This test cartridge may be used with the 2.3GB, 5.0GB, and 7.0GB 8-mm tape units. Test Cartridge #59H2677 Diagnostic Cartridge #46G2660 8-mm (112-m) Tape Cartridge #21F8595 8-mm (160-m) Tape Cartridge #87G1601 8-mm Tape Cartridge #59H2678 Test Cartridge #59H2677 is used to write test data onto a tape cartridge. The tape unit reads the recorded data to check the write operation. Do not use this cartridge to sae programs or data. Only use the Diagnostic Cartridge when the system is not aailable and you are not able to use Test Cartridge #21F8577. This diagnostic cartridge contains a program that tests only the read capability of the tape drie. Use this cartridge to sae your programs or data. Each tape cartridge proides up to 2.3GB of storage with the 7208 Model 002 or 5.0GB of storage on the 8-mm 5.0GB or 7.0GB tape units. Use this cartridge to sae your programs or data. Each tape cartridge proides up to 7.0GB of storage with the 7208 Models 222 and 234, 9427 Models 210 and 211, and Feature Code 6390. Use this cartridge to sae your programs and data with the 7208 Model 342. This test cartridge can only be used with the 20GB 8mm tape unit. Diagnostic Cartridge #46G2660 may not be used with the 7208 Model 002 or Model 342 tape units. Call your serice representatie for additional copies of the Diagnostic Cartridge. Tape cartridges 21F8595 and 87G1601 can be read in the 7208 Model 342 but cannot be written. á This cartridge cannot be used in the 7208 Models 002, 012, 222, 232, 234 or in the 9427 Models 210, 211, or in the feature code 6390. Chapter 8. Managing system operations 133

Cleaning Cartridge #21F8593 and #16G8467 Cleaning Cartridge #59H2898 Use this cartridge for cleaning the 2.3GB, 5.0GB, and 7.0GB 8-mm tape unit heads. #16G8467 is a mildly abrasie cleaning tape and should be used wheneer tape unit problems are encountered. Use this cartridge for cleaning the 7208 Model 342. á This cartridge cannot be used in the 7208 Models 002, 012, 222, 232, 234 or in the 9427 Models 210, 211, or in the feature code 6390. Loading the 8-Millimeter Tape Cartridge To load a tape cartridge, push the blue load/unload pushbutton on the tape drie. For the 7208 Model 002 tape unit, the tape drie opens, and a cartridge tray ejects. After a tape cartridge is inserted, push the tape drie door until the mechanical latch holds the door closed. The tape drie loads the tape from the tape cartridge. For all the other 8mm tape units, insert a tape cartridge through the coer door into the tape drie. The tape drie loads the tape from the tape cartridge. If you need more information, see Using 8-Millimeter Tape Units Using 8-Millimeter Tape Units on page 128. The tape takes about 25 seconds to load. When the green ready light comes on, the drie is ready for data operations. You can type commands on your display station while the tape is loading. Any commands to the tape unit start running once the tape has finished loading. Commands that do not require the tape cartridge are run immediately. Unloading the 8-Millimeter Tape Cartridge You can unload a tape cartridge by a system command or by pushing the load/unload pushbutton on the tape drie. Depending on the position of the tape, the time for rewind and unload is between 18 seconds and 3 minutes. The drie rewinds the tape within the cartridge. The 7208 Model 002 tape unit ejects the tray containing the tape cartridge. After a cartridge is remoed, another cartridge may be inserted. To keep dust and other contaminants out of the tape drie, push the drie door closed until the mechanical latch holds the door closed. The 7208 Models 012, 222, 232, 234, 342 or the 6390 tape unit ejects the tape cartridge, which can then be remoed. If the tape cartridge cannot unload and has to be remoed manually from the drie, contact your serice representatie. Protecting Data Stored on 8-Millimeter Tape Cartridges The window on the tape cartridge that is shown here controls write protection. To preent data from being written on the tape cartridge, slide the tab so that the window is closed. To allow data to be written on the tape cartridge, slide the tab so that the window is open. 134 iseries: Getting started with iseries

Erasing Data on the 8-Millimeter Tape Cartridge To erase data on an 8-mm tape cartridge, use a tape erasing deice that has a magnetic coerciity strength of 1500 oersteds or more. Note: You may also erase the tape by specifying *YES for the Clear parameter on the Initialize Tape (INZTAP) command. Howeer, this method takes up to 3.5 hours. For the 160-m tape unit, it may take up to 5 hours. Using 1/2-Inch tape reels Use the following tape and reel recommendations for maximum performance and reliability: Tapes 1.5 mil thick A maximum of 733.7 meters (2400 feet) Reels 15.24 cm (6.0 inches) 17.78 cm (7.0 inches) 21.58 cm (8.5 inches) 26.67 cm (10.5 inches) Using tapes that are longer than 2400 feet is not recommended. Using these tapes will cause the tape unit head to wear incorrectly. You could hae an increase in read and write errors. Chapter 8. Managing system operations 135

17.78 cm (7.0 inches) 21.58 cm or (8.5 inches) 26.67 cm (10.5 inches) Tape must be 1.5 mils thick Tape no longer than 733.7 meters (2400 feet) RV2P719-2 Follow these tips to ensure that your tape reels are used correctly: Important: Secure the end of the tape with a tape end fastener when not in use. Keep the reel protected with a locking collar when not in use. Store tapes in a ertical position. Do Not: Squeeze the outer flanges of the reels when handling and loading tape. Hold the tape eenly around the outer edge by the palm of your hand. Allow tape ends to drag on the floor and get dirty. Touch the tape surface. Preparing a Tape Leader A tape leader that is square or damaged can cause the tape to load incorrectly in units that automatically load tapes. When using this type of tape unit, ensure that the tape loads correctly by: Preparing the tape leader with the tape leader tool (IBM part 2512063). Pressing hard when cutting the tape. This preents static problems on the tape leader. The figure below shows how to correctly prepare a tape leader. 136 iseries: Getting started with iseries

Loading the 1/2-Inch Tape Reel When loading 6-inch and 10-inch reels of tape on the 9348, carefully place the tape reel on the center of the hub. When loading a tape reel, ensure that the loose end of the tape is on the tape reel and not under the reel. Protecting Data Stored on the 1/2-Inch Tape Reel To preent the drie from writing data, remoe the write enable ring (shown below). To allow the drie to write on the tape, install the write enable ring. Chapter 8. Managing system operations 137

Cleaning the 1/2-Inch Tape Reel Unit Use the table below as a guide to establish how often to clean your tape reel unit. Cleaning the 1/2-Inch Tape Reel Unit When: Less than ten reels are used in eight hours. More than 10 reels are used in eight hours. Particles appear on the tape path or you are using new or seldom used tapes. Clean the tape path: Eery eight hours. Eery one to two hours of running. After each reel. Use the following cleaning supplies: Tape cleaning kit, IBM part 352465 or equialent Cleaning fluid, IBM part 8493001, 13F5647, or equialent Lint-free cloth, IBM part 2108930 Rigid cleaning tool, IBM part 2200574 or equialent To clean the tape reel unit: 1. Set the power switch to the Off position. 2. Clean the following areas using a lint-free cloth or swab and cleaning fluid: Read/write head Tape cleaner block Tape guides General tape path 138 iseries: Getting started with iseries

Pay particular attention to the read/write head and tape cleaner block. Push hard against the read/write head. Dry the areas with a lint-free cloth until the cloth comes away clean. If the tape unit is cleaned thoroughly and a particular tape is causing errors, discard the tape. Chapter 8. Managing system operations 139

140 iseries: Getting started with iseries

Chapter 9. Handling system problems and getting help through electronic customer support When something goes wrong, help is aailable to get your system up and running again. These articles help you determine exactly what the problem is and how you can resole it. Start here to sole problems: Go here... If you want to... Troubleshoot printer problems Sole printing difficulties. Resole Uniersal Connection Wizard problems Sole problems before re-running the wizard. Locate the serice agent that you need. Contact electronic customer support Choose the fix you need from IBM s support page. Get fixes View your system configuration list View your current configuration information. Use the troubleshooting flowchart Determine what the problem is and how you can sole it. Troubleshooting with Systems Management Get help with system and application problems. Additional information on this topic can be found in these sources: Getting help with system operation problems Troubleshooting printer problems Printing is a two-step process on your system, and problems can arise in either step: you cannot send material to the printer, or your printer is not receiing the material you send. This topic describes steps to take to soleáthese problems and other printing problems. Soling problems with sending jobs (LPR) Soling problems with receiing jobs (LPD) Finding an unprinted job Reasons Why a Printer Will Not Print Additional information on this topic can be found in these sources: Printing and deice programming Soling problems with sending jobs The system handles the arious parameters passed to the LPR command. Sometimes, they need to be formatted in a particular way to work correctly. Examples are gien for some of the most common error conditions. LPR command considerations When the system passes alphabetic characters to a command processing program from a command, it conerts all of the characters to uppercase. Enclosing the parameter in apostrophes preseres the case of the characters. This is required if you use filters for the DESTOPT parameter. It may be required for the PRTQ parameter of the LPR command, depending on the case sensitiity of the destination system. Copyright IBM Corp. 1998, 2001 141

Common error messages If a problem is detected when usingáyour system s LPR client, most problem analysis can be done by examining the job logs of the user and the message help text for the issued error message. Send request failed for spooled file XYZ is the error message for both TCP3701 and TCP3719. Examine the message help text, howeer. If the message is TCP3719, the error may be that the printer queue name is incorrectly spelled or the case of the printer queue name does not match that of the printer queue on the destination system. If the message is TCP3701, look in the job log for the preious messages to determine the failure.á Common failures are caused by the following: Destination system name is misspelled. Destination system name is not defined in the TCP/IP host table LPD serer is not started on the destination system TCP/IP is not started on the destination system Examine the message help text for any preious messages to determine error recoery procedures. Materials required for reporting LPR problems Include the following information when reporting any LPR problem to IBM: The QTCPIP and LPR client job logs. If file or data integrity is compromised, then any files that were being sent. If the file being sent is being transformed, a copy of the workstation customizing object being used. All options taken on the LPR command when trying to send a file. The type of remote host, operating system, and operating system ersion to which the LPR command was attempted, for example, PS/2 to OS/2, PS/2 to DOS, or RS/6000 to AIX. Special authorities in the user profile of the sender; the owner of the file; and the output queue parameters AUTCHK, OPRCTL, and the DSPOBJAUT to get all authorities of the user to the output queue. A communications trace from the time of the failure (Format TCP/IP data only field), formatted for ASCII. If you are not familiar with the procedure for collecting a communications trace, refer to Collecting a communications trace and Formatting and saing the communications trace. Additional information on this topic can be found in these sources: Printing and deice programming Soling problems with receiing jobs The most common problems, causes, and solutions for LPD are shown below: Problem Cause Solution All files on the receiing system are of the same printer deice type but not *USERASCII The QPTMPLPD printer file is set to a type other than *USERASCII Change the printer file (CHGPRTF command) to printer deice type *USERASCII 1 142 iseries: Getting started with iseries

Problem Cause Solution Spooled file is not on the print queue that you requested LPD receies only a portion of the spooled file sent Spooled files do not show up on the receiing system from a non-iseries 400, een though LPR indicates it was successfully sent Destination print queue name is misspelled. User did not hae authority to the requested print queue. The requested print queue is not in the user ID library list path. The LPR job failed before sending all the data. LPD assumes that when the connection is closed, all the data has been sent. If the sending user ID does not match a user ID on the receiing system, LPD uses QTMPLPD user profile to spool the file. Howeer, if the QTMPLPD user profile does not exist, or the PUBLIC authority is set to *EXCLUDE, the file is not spooled. 2 Display the messages sent by LPD to check where the spooled file was placed (you must be logged on the system where the LPD serer is running to see the messages). If you are logged on with the same user ID as was used to issue the LPR command, use the Display the Message (DSPMSG) command. If you are logged on to a different user ID than was used to send the LPR command, you must use the DSPMSG userid command if the user ID exists. If the user ID does not exist, use DSPMSG QTCP/QTMPLPD. Use QTMPLPD as the default user profile if there are any problems with the client profile. If the messages are not able to help locate the file or the problem, then check the print queue QPRINT in library QGPL. If there are any problems with the requested print queue, QPRINT is the default destination where all files are spooled. Send the spooled file again. Change the authority for the QTMPLPD profile to *OBJOPR, or find a system with a matching user ID to accept the spooled files. 1. Set the QPTMPLPD printer file to *USERASCII because LPD expects to receie ASCII data from non-iseries 400 systems. The *USERASCII deice type on the printer file does not mean that the data stream of the spooled file is ASCII. If, for example, AFPDS data is sent from a non-iseries 400 system, the data is sent as *USERASCII and will not print correctly. 2. The sending system does not know that the file was not spooled because LPD does not search for a place to store the file until after it has receied all the data from the sending system. Materials Required for Reporting LPD Problems Include the following information when reporting any LPD problem to IBM: Any problems that cause LPD to fail unexpectedly will generate spooled files as part of the LPD error handling. Three spooled files are created inside the failing job from these commands: SYS/DSPJOBLOG JOB(*) OUTPUT(*PRINT) QSYS/DSPJOB OUTPUT(*PRINT) QSYS/DMPOBJ OBJ(QUSRSYS/QTMPLPD8MM) OBJTYPE(*USRQ) Chapter 9. Handling system problems and getting help through electronic customer support 143

These 3 files are owned by either the sending user profile, the default user profile QTMPLPD or the QTCP user profile. The QTCPIP and LPD client job logs. If file or data integrity is compromised, then any files that are being sent. If the file being sent is being transformed, a copy of the workstation customizing object being used. If the file being receied is an iseries 400 spooled file sent with TRANSFORM=*YES, or is coming from a non-iseries 400 client, include the description of the QUSRSYS/QPTMPLPD printer file. The type of remote host, operating system, and operating system ersion from which the LPR command was attempted, for example, PS/2 to OS/2, PS/2 to DOS, or RS/6000 to AIX. A communications trace from the time of the failure (format TCP/IP data only), formatted for both ASCII and EBCDIC. If you are not familiar with the procedure for collecting a communications trace, refer to iseries Communication. Additional information on this topic can be found in these sources: Printing and deice programming Finding a job that did not print Your users are frustrated because jobs that their print job has disappeared. You can look either on the serer, or on the client, to discoer what went wrong with the print job, and then begin to sole that problem. On the serer One method of determining what went wrong with a print job on the serer side is to use the QEZJOBLOG log on the serer that is running LPD for the print job. To get to the job log, follow these steps: 1. On any command line, enter the WRKOUTQ command. 2. Find the QEZJOBLOG and use option 5 to work with the job log. 3. Find the print job with the user of QTCP. Use option 5 to iew the spooled file to determine what type of errors were encountered. On the client Another method of determining what went wrong with a print job on the client side is to find the job log for the print job. Follow these steps to get to the job log: 1. Enter the WRKOUTQ command on any command line. 2. Press F20 to work with print writers. 3. Find the writer with your job and use option 5 to work with the job log. 4. Press F17 to work with the writer. 5. Use option 10 to display the job log associated with the file. 6. Press F10 to display detailed messages. A message appears that describes the problem that occurred. Additional information on this topic can be found in these sources: Printing and deice programming Resoling problems with the Uniersal Connection wizard If you hae been unable to successfully run the Uniersal Connection wizard, answer the questions below and then re-run the wizard. 1. Is the Uniersal Connection wizard unaailable to you? 144 iseries: Getting started with iseries

You must hae installed both Client Access Express and the optional Network component. You must also hae *ALLOBJ and *IOSYSCFG authorities to run the wizard. 2. If you are using an internatl modem, does your Modem Country ID Network Attribute correspond to the location of your iseries? To erify that this attribute is correct: a. On any command line, enter DSPNETA (Display Network Attribute command). b. Press Enter. c. If the alue is correct, moe to the next question. d. If the alue is incorrect, modify it by entering CHGNETA MDMCNTRYID(XX), where XX is the appropriate Country Identifier. 3. Is the QRETSVRSEC system alue correct? In order for the authentication information required to connect to IBM to be retained on your system, this system alue must be set to 1 (Retain Data). To make this change: a. On any command line, enter CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE( 1 ) b. Press Enter. 4. Is TCP started? TCP must be started in order for the Uniersal Connection wizard to run successfully. In addition, TCP must be actie wheneer the Uniersal Connection is to be used. To start: a. On any command line, enter STRTCP (Start TCP command). b. Press Enter. 5. Is your Virtual Priate Network (VPN) functioning correctly? Refer to the VPN Troubleshooting documentation in the Information Center for assistance. 6. Does your modem selection exist or do you need to modify some of the default parameters? To modify the modem list: a. From Operations Naigator, select the system you want to work with. b. Expand Network. c. Click Remote Access Serices. d. Click on modems. e. Add or modify modems as needed. Refer to your modem manual for the proper settings. You can also modify the modem list this way: a. On any command line, enter CFGTCPPTP. b. Press Enter. c. Select Option 11 (Work with modem information). d. Select options to add or modify modems as needed. Refer to your modem manual for the proper settings. 7. Is your modem configured with a framing type of asynchronous? If not, you may hae to change dip-switch and other hardware settings. Refer to your modem manual for more information, or to Configuring your modem. If you re using an internal modem or an IBM 7852-400, no change is required. 8. Did problems occur when you attempted to test the connection? Refer to Troubleshooting your PPP Connection. 9. Are you trying to use an existing SNA electronic customer support switched connection as a backup? Ensure that the QESLINE line description specifies a alid resource name (DSPLIND QESLINE) and is connected to a synchronous capable modem. The same IBM 7852-400 modem can be used for both the Uniersal Connection and an SNA backup. It is also possible to use two separate modems. Chapter 9. Handling system problems and getting help through electronic customer support 145

AT&T customers: If you are using AT&T for your electronic customer support connection, please be aware of the following information: Eery 30 days (or wheneer you use the Uniersal Connection after that 30 day period), an updated AT&T telephone list is downloaded by your system. This ensures that the telephone numbers aailable for the Uniersal Connection remain current. When this download occurs, a message is posted to the system operator s message queue. If the Uniersal Connection Profile being used contains a telephone number that is no longer in the current AT&T telephone list, a diagnostic message will be issued. The purpose of this message is to notify you to re-run the wizard to update the telephone numbers. When you re-run the wizard, updated telephone numbers will be aailable for you to choose from. To iew the ery latest telephone numbers, isit the AT&T website. Contacting electronic customer support Wait! Before You Access the Internet... The iseries 400 Serice Web site deliers fixes to your PC console, which acts as a gateway between IBM s serer and your system. Theáfix information flows through your PC console onto your system. The iseries 400 Serice Web site guides you through this process. Howeer, before you access this information on the Internet, you need to be aware of some security issues. Read this page before linking to the iseries 400 Serice web site. 1. End your console session to the iseries. Why? Someone with malicious intent could gain access to your PC anytime you are connected to an external network and do significant damage to your system. If your PC is compromised, either by direct control or through a irus, your system could be accessed through the PC console connection. Ending your PC console session before connecting to the Internet reduces the possibility that yourásystem might be damaged. 2. Reduce the security risks to your system. Do not hae any shared dries on your PC Stop FTP and Telnet on your PC Run irus scan on your PC after ending your Internet actiity (before starting the console session to your iseries) Note: Consider directly accessing the Internet with your PC console a short-term option only. If you foresee continued Internet access or an Internet presence as part of your business goals, architect a complete Internet security strategy and educate yourself on Internet security risks, secure gateways, and Web sering. 3. Proceed to the fixes on the iseries 400 Serice Home page. Viewing system configuration lists Operations Naigator allows you to iew your current system configuration and monitor performance. Use this information to schedule maintenance or plan upgrades. Management Central also allows you to iew and export hardware and software inentories. Get more information on Management Central now. 146 iseries: Getting started with iseries

Hardware 1. Select the system you want to work with. 2. Expand Configuration and Serice. 3. Expand Hardware. 4. Expand All Hardware. You can iew all of the hardware resources, organized by name, status, and description. Use this information as a diagnostic tool if you suspect that a hardware resource is not operational. Print a copy of your system s configuration list periodically. This is a useful way to plan for changes to your system s hardware configuration. To print this list: 1. Select All Hardware. 2. From the File menu, select Print. Software 1. Select the system you want to work with. 2. Expand Configuration and Serice. 3. Expand Software. 4. Expand All Software. You can iew all of the software on your system. You can look at the general properties of the software product you select, including the name of the product, a brief description, and other information. Additional information on this topic can be found in these sources: Management Central hardware inentory Management Central software inentory Printing system configuration for logical partitions Troubleshooting your system You can often sole problems that occur on your system with methodical analysis. Howeer, on other occasions, you will need the assistance of a serice representatie or technical support person. If you do call on external help, you need to hae as much information to offer that person as possible.ádetailsáaboutáyour system s problemáare required for accurate diagnosis of the situation and rapid resolution. Before you call Before you call a support person, ask yourself these questions: Has there been an external power outage or momentary power loss? Has the hardware configuration changed? Hasásystem software been added? Hae any new programs or program changes been recently installed? To make sure that your licensed programs and products hae been properly installed, use the Check Product Option (CHKPRDOPT) command. Hae any system alues changed? Has any system tuning been done? Keep these questions in mind while you are diagnosing the problem. Chapter 9. Handling system problems and getting help through electronic customer support 147

If the system is logically partitioned, references in this document to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. References to the system control display refer to the Work with partition status display functions if the problem is in a secondary partition. References to the system control display refer to the actual system control display if the problem is in the primary partition. How to use this flowchart Work through these questions. As you answer each, follow the link to the next question that has releance to your problem. For instance, if you are told to go to Step 10, for instance, click the link and continue answering questions. Begin troubleshooting now 1. Can you power on your system? Yes, go to Step 2. No, go to Analyzing problems with a symptom. Additional information on this topic can be found in these sources: How the iseries manages problems Getting help with system operation problems Troubleshooting your system: Step 2 1. Does the Function/Data display on the system control display start with Function 11-3, or is the System Attention light on? Use the up and down arrow buttons to cycle through the functions to determine if a 11-3 exists. Yes, go to Step 19. No, go to Step 3. Additional Information: Press the Enter pushbutton to alternate between function and data. Troubleshooting your system: Step 3 1. Is the system logically partitioned? Yes, go to Step 4. No, go to Step 5. Troubleshooting your system: Step 4 1. Using system serice tool (SST)/dedicated serice tool (DST) from the primary partition console, select Work with system partitions, then select Work with partition status. Is there a partition with the state of Failed or Unit Attn? Yes, go to Step 19. No, go to Step 5. Troubleshooting your system: Step 5 1. Does the console show a Main Storage Dump Manager display? Yes, perform a Main Storage Dump. No, go Step 6. Troubleshooting your system: Step 6 1. Does the display station that was in use when the problem occurred (or any display station) appear to be operational? 148 iseries: Getting started with iseries

Yes, go to Step 7. No. If your console cannot ary on, go to Procedure 11. For all other workstations, go to Procedure 5. Additional Information: The display station is operational if there is a signon display or a menu with a command line. If another display station is operational, use that display station to resole the problem. Troubleshooting your system: Step 7 1. Is a message related to this problem shown on the display station? Yes, go to Step 8. No, go to Step 12. Troubleshooting your system: Step 8 1. Is this a system operator message? Yes, go to Step 9. No, go to Step 10. Additional Information: A message is a system operator message if the display indicates that the message is in the QSYSOPR message queue. Critical messages can be found in the QSYSMSG message queue. Troubleshooting your system: Step 9 1. Is the system operator message highlighted or does it hae an asterisk (*) by it? Yes, go to Step 18. No, go to Step 14. Troubleshooting your system: Step 10 1. Moe the cursor to the message line and press the Help key, or use Option 5 Display details and reply). Does the Additional Message Information display appear? Yes, go to Step 11. No, go to Step 12. Troubleshooting your system: Step 11 1. Record the message information that is shown on the problem summary form. If possible, follow the recoery instructions on the Additional Message Information display. Did this sole the problem? Yes, end of procedure. No, go to Step 12. Troubleshooting your system: Step 12 1. Type dspmsg qsysopr on any command line and press Enter to display system operator messages. Did you find a message that is highlighted or has an asterisk(*) by it? Yes, go to Step 18. No, go to Step 13. Management Central s message monitor can also inform you when a problem has deeloped. Troubleshooting your system: Step 13 1. Did you find a message at or near the time the problem occurred? Yes, go to Step 14. No, go to Step 16. System Operator Messages Chapter 9. Handling system problems and getting help through electronic customer support 149

To determine the time a message occurred, display additional information about the message by using Option 5 (Display details and reply) on the Work with Messages display. The Additional Message Information display shows the time that the message was sent. If the problem seems to affect only one display station, you might be able to use information from the Job (JOB) menu to diagnose and sole the problem. Type GO JOB on any command line and press Enter to find this menu. End of procedure. Troubleshooting your system: Step 14 1. Use option 5 (Display details and reply) to display additional information about the message; otherwise, moe the cursor to the message line and press the Help key. Record the message information that is shown on the problem summary form. If possible, follow any recoery instructions that are shown. Did this sole the problem? Yes, end of procedure. No, go to Step 15. Additional Information: If the additional message information tells you to run problem analysis, go to Step 18. Troubleshooting your system: Step 15 1. Were you instructed by the message information to look for additional messages in the system operator s message queue (QSYSOPR)? Yes, Press F12 (Cancel) to return to the list of messages, then look for other related messages. to Step 12. No, go to Step 16. Go Troubleshooting your system: Step 16 1. Do you know which input/output deice you are haing a problem with? Yes, a. Type ANZPRB on the command line and press Enter. b. See Analyzing a new problem for information on using the Analyze Problem (ANZPRB) command. c. Report the problem. d. See Reporting problems detected by the system for information about using the problem log to report a problem electronically. e. End of procedure. No, go to Step 17. Troubleshooting your system: Step 17 1. If you do not know the input/output deice, describe the problems that you hae obsered by doing the following: a. Type go userhelp on any command line and press Enter. b. Select option 10 (Sae information to help resole a problem) on the Information and Problem Handling (USERHELP) menu. c. Type a brief description of the problem and press Enter on the Sae Information to Help Resole a Problem display. (If you specify the default Y for the Enter notes about problem field and press Enter, the Select Text Type display appears that allows you to enter more text to describe your problem). d. Report the problem. 150 iseries: Getting started with iseries

Creating your own problem record This step helps you isolate and describe the problems that you obsered. You can store system and job-related information in spooled files and create an entry (identified by the problem ID) in the system problem log. This information can be used to assist your technical support representatie in soling the problem. Note: Using go userhelp, you can create a brief note describing the problem you obsered. To describe your problem in greater detail, use the Analyze Problem (ANZPRB) command. Using the Analyze Problem (ANZPRB) command may also run a test to further isolate the problem. See Problem reporting for additional information. End of procedure. Troubleshooting your system: Step 18 1. Moe the cursor to the message line and press the Help key. Press F14, or use the Work with Problem (WRKPRB) command as instructed. If this does not sole the problem, begin analyzing the problem. Running Problem Analysis With problem analysis you can gather more information about the problem to either sole it or report it without the help of a serice representatie. You can run problem analysis on messages that are highlighted (basic assistance leel) or hae an asterisk (*) next to them intermediate assistance leel). If you do not see any of these messages, you may not be authorized to the Work with Problem (WRKPRB) command, or the message does not support additional problem analysis. Besides running problem analysis on messages, you can also use F14 (Work with problem) if it is aailable on your display. If F14 is not aailable, use the Work with Problem (WRKPRB) command to run problem analysis. From the Work with Problems display, select Option 8 (Work with Problem), and then select Option 1 (Analyze problem) from the Work with Problem menu. If you do not see Option 1 on the Work with Problem menu, analyze the problem before reporting it to IBM. See Problem reporting for additional information about analyzing and reporting problems. End of procedure. Troubleshooting your system: Step 19 1. Record the system reference codes on the problem summary form in Problem Summary Forms. Make sure you hae collected all of the codes. Go to Procedure 2. Collecting System Reference Codes If you hae a Model 270 or 8xx: a. Press the increment button until 05 appears on the Function/Data display. b. Press the Enter pushbutton. c. Record the information displayed. d. Press the increment button again until 11 appears in the Function/Data display. e. Press the Enter pushbutton. f. Record the information displayed. g. Press the increment button again. The number 12 displays on the first line of the Function/Data display. h. Press the Enter pushbutton. Chapter 9. Handling system problems and getting help through electronic customer support 151

i. Record the 32-character code: 16 characters from line one, and 16 characters from line two, of the Function/Data display. j. Press the increment button again. The number 13 displays on the first line of the Function/Data display. k. Press the Enter pushbutton. l. Record the 32-character code: 16 characters from line one, and 16 characters from line two, of the Function/Data display. m. Press the increment button again until the number 20 displays on the first line of the Function/Data display. n. Press the Enter pushbutton. o. Record the 32-character code: 16 characters from line one, and 16 characters from line two, of the Function/Data display. For earlier models, if you hae system expansion or extension tower attached to your system, select Function 05, and record the system reference code. If 11-3 is shown in the Function/Data display on the control display, then the numbers that follow are the system reference code. If a number other than 11-3 is shown in the Function/Data display, the number may not indicate a problem with the system. These codes may indicate functions you select from the control panel display. Note: If you hae a display station with Type and Reference Code columns on it, record the data under the Type column as the first 4 characters of function 11 on the problem summary form. If an A, B, C, or D is displayed as the first digit in the Type column, use the data in the Reference Code column as the last four characters of function 11. Go to Getting Help with Problems for information on who to contact if you need more help. Analyzing problems with a symptom Please read the symptom index from top to bottom. Find the symptom that describes the problem, and click the procedure name listed. Symptoms Recoery Procedure You cannot power on the system Procedure 1 The system attention light is on, or a system reference Procedure 2 code is displayed on the control panel. The Operations Console Remote Control Panel feature is Procedure 2A not working properly. A pushbutton or light onthe control panel is not working Procedure 3 properly. You cannot perform an initial program load (IPL) or you Procedure 4 suspect an operating system failure. Your workstation or deice (such as display or printer) is Procedure 5 not working. You are haing a problem with a tape or optical deice. Procedure 6 You are haing a problem with a disk or diskette deice. Procedure 7 You cannot communicate with another deice or Procedure 8 computer. Your system seems to be in a loop or hang condition. Procedure 9 152 iseries: Getting started with iseries

Symptoms Recoery Procedure You are haing an intermittent problem Procedure 10 You are haing data compression problems and receie this message: Message ID CPPEA02 along with system reference code (SRC) 6xxx 7501 - Compressed deice and compression input-ouput adapter (IOA) are not compatible. You are haing data compression problems and receie this message: Message ID CPPEA03 along with SRC 6xxx 7052 - Data compression warning. The system has logical partitions and a state of Failed or Unit Attn is displayed on the Partition Status display of a secondary partition. There is a reference code. The system is logically partitioned and your partition seems to be in a loop or hang condition. The system is logically partitioned and you cannot perform an initial program load (IPL) or you suspect an operating system failure. No symptom to match in the table. Go to Recoering from SRC 6xxx 7501 in Backup and Recoery Go to Recoering from SRC 6xxx 7502 in Backup and Recoery Procedure 2 Procedure 9 Procedure 4 Go to Getting help with system operation problems Procedure 1: Recoering from system power problem 1. Make sure that the power that is supplied to the system is adequate. If your system units are protected by an emergency power off (EPO) circuit, check that the EPO switch is not actiated. 2. Verify that your system power cables are properly connected to the electrical outlet. When power is aailable, the Function/Data display on the control panel is lit. 3. If you hae an uninterruptible power supply (UPS), erify that the cables are properly connected to the system that the UPS is functioning. 4. Make sure all system units are powered on. 5. Turn on the system again. 6. Is a system reference code displayed on the control panel? Yes. Go to Procedure 2. No. Call your hardware serice representatie. Procedure 2: Recoering when attention light is on or the System Reference Code (SRC) is displayed Use the table below to locate the SRC that is displayed. In the table, xxxx can be any number 0 through 9 or letter A through F. If you cannot find the SRC in this table, go to Getting help with system operation problems. The SRCs are grouped together in ranges. The recoery for each range may not apply to eery SRC within a specified range. The recoery procedure is attempting to clean up your systemand get it back to a minimum operating enironment. For a list of SRCs and their descriptions that are specific to logical partitions, see Troubleshooting logical partitions. Chapter 9. Handling system problems and getting help through electronic customer support 153

System Reference Code starting with 11-3 0000 AABB 0000 AACC What you should do You attempted a timed, remote, or automatic IPL (initial program load) with the system in the Secure or Manual mode. 1. Set the system to the Normal or Auto mode and do the IPL again. 2. If you are still not able to do an IPL, call your hardware serice representatie. 0000 AADD You attempted a manual IPL with the system in the Secure or Auto mode. 1. Set the system to the Normal or the Manual mode and try the operation again. 2. If you are still not able to do an IPL, call your hardware serice representatie. 1xxx D101 1xxx D102 Battery Power Unit x failed. Battery Power Unit x test failed. Replace the battery power unit.. If the battery still does not work after the replacement, call your hardware serice representatie. 63xx xxxx The tape unit failed. See Procedure 6. 93xx xxxx A disk or diskette unit failed. See Procedure 7. A6xx 0277 A compression disk unit cannot complete an operation. Do not power off the system when performing this procedure. Look at the 4 characters that are to the left of the Data display of function 17-3. These 4 characters indicate the type of problem that exists and the recoery action to perform. If these characters are 8402 or 2002, the compression disk unit is temporarily full of data. The command to the compression disk is being held. When the subsystem controller has created sufficient space on the compression disk unit to contain the data, the command that is being held is released and the system resumes normal processing. If the system does not resume normal processing within 20 minutes, call your hardware serice representatie. If these characters are 8400 or 2000, the compression disk unit is full o f data. The command to the compression disk is being held. Go to Disk unit full considerations in Backup and Recoery. A6xx 500x Work station controller failure. See Procedure 5. A1xx xxxx IPL load deice failure. See Procedure 4. B1xx xxxx 154 iseries: Getting started with iseries

System Reference Code starting with 11-3 A900 2000 What you should do The IPL completed normal, does the system console hae a sign-on screen? B0xx xxxx If the system console did not ary on, see Procedure 11. If the system completed the IPL, check the QSYSARB job log for the message and follow the correctie actions indicated in the message. To iew the QSYSARB job log, use the Work with Actie Jobs (WRKACTJOB) command, then type 5 (Work with) next to the QSYSARB job. Select Option 10 (Display jobs) to iew the job log. You need *QSECOFR user class, or *ALLOBJ and *JOBCTL special authority to iew the job log. If the problem persists, call your hardware serice representatie. Failure detected by communication Licensed Internal Code. 1. Make sure the latest fix package is installed. 2. If this does not sole the problem, call your software serice representatie. B6xx xxxx Not enough auxiliary storage. 1. If your system unit has some disk storage space aailable, add more to auxiliary storage pool 1. 2. If this does not sole the problem, call your software sreice representatie. B9xx xxxx OS/400 IPL failure. See Procedure 4. C1xx xxxx C3xx xxxx C5xx xxxx D1xx xxxx IPL status. This is a normal indication during the IPL. You may suspect a hang or loop condition if the SRC does not change during the two-minute period. See Procedure 9. Diagnostic status. This is a normal indication while the system main storage is being saed to disk. D6xx xxxx If the system is still not running correctly after 30 minutes, call your hardware serice representatie. Diagnostic Status. This is a normal indication while the system is being powered down. If the system does not start normally after 30 minutes, call your software serice representatie. B2xx xxxx When xxxx is changing, the system is doing a main storage dump. IPL load failure. 1. Verify that the partition state is Failed. If the partition state is not Failed, this SRC may disappear from the partition status screen by refreshing the screen. Refresh the screen until either the partition state changes to Failed or the SRC disappears. 2. If the partition state is Failed, see Procedure 4. Chapter 9. Handling system problems and getting help through electronic customer support 155

System Reference Code starting with 11-3 C2xx xxxx What you should do IPL status. This is a normal indication during the IPL. You may suspect a hang or loop condition if the SRC does not change in 15 minutes. See Procedure 9. D2xx xxxx Diagnostic status. This is a normal indication while the panel functions and system code are powering down the system. Procedure 2A: Recoering when Operations Console Remote Control Panel feature is not working properly 1. Are you able to change modes or select system functions using the Remote Control Panel feature? Yes. Continue to step 2. No. Make sure the Operations Console cable is attached properly. Using the Operations Console display, disconnect and then reconnect the serer connection. If the same failure occurs, call your hardware serice representatie. 2. Are the Remote Control Panel functions (Function/Data, Mode and Power) properly displayed? Yes. Use the Remote Control Panel to start an IPL (initial program load) and continue to step 3. No. Call your hardware serice representatie. 3. Was the IPL successfully started? Yes. Continue the IPL process. No. Call your hardware serice representatie. Procedure 3: Recoering when control panel pushbuttons or lights are not working properly 1. Are your control panel pushbuttons working properly? Yes. Continue to step 2. No. Try turning on the system again. If the same failure occurs, call your hardware serice representatie. 2. Are the control panel lights working properly? Yes. End of the procedure. No. Call your hardware serice representatie. Procedure 4: Recoering from IPL or system failure If the system is logically partitioned, references to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. References to the system control panel refer to the Work with partition status display functions if the problem is in a secondary partition. References to the system control panel refer to the actual system control panel if the problem is in the primary partition. If your system has logical partitions, see Troubleshooting logical partitions. Verify the following: The deice from which you did the IPL (initial program load) is powered on. The tape and CD are loaded properly. The sign-on User ID and password are correct. The system is set to the correct mode (Manual, Normal, Auto, or Secure) The system alue for date/time and control panel mode is set correctly if this is a timed IPL. 156 iseries: Getting started with iseries

The phone, modem, control panel mode, and QRMTIPL alue are set up ocrrectly if this is a remote IPL. Follow these steps: 1. Do an IPL from the system control panel or Operations Console Remote Control panel as follows: a. Set the system to the Manual mode. b. If the system is powered on: 1) Select Function 03. 2) Press the Enter pushbutton to start an IPL c. If the system is powered off, ensure that the control panel is in either Normal or Manual mode and press the power on pushbutton. 2. Sign on the system when the Sign On display appears. If you do not see the Sign On display, do you hae a new SRC? Yes. Go to Procedure 2. No. Go to Getting help with system operation problems. 3. On the IPL Options display, specify Yes for the following parameters: Define or change the system at IPL Clear output queues Clear job queues Clear incomplete job logs 4. Change the system alue for QMCHPOOL to a smaller alue. 5. Make sure the system alue for QCTLSBSD has the correct spelling, or assign an alternatie controlling subsystem. 6. Change the system alue for QPWRDWNLMT to a larger alue. 7. Continue the IPL process. If the same failure occures, set the system to the Normal mode, and then call your hardware serice representatie. Procedure 5: Recoering from workstation failure 1. Make sure all workstations and deices (such as displays or printers) are turned on. 2. If the Operations Console is being used as the console, ensure that the cable from the PC to the system is attached properly. Make sure that the PC has been properly configured. 3. Make sure all workstation cables are attached properly and set to the proper address. For information about workstation address, see Determining the primary or alternatie consoles if you are using system console, or Local Deice Configuration if you are using other workstations. 4. Make sure recently attached workstations hae been properly configured to the systm. Workstation addreses are unique (if applicable). Workstations are terminated (if applicable). 5. Check all workstation printers for mechanical problems such as paper jams, ribbon failure and so on. 6. Vary off the failing workstation controller if any other workstation is operational, and then ary it on again. End all actie jobs before arying off the workstation controller. To end actie jobs, use the Work with Actie Jobs (WRKACTJOB) command. To ary on or off the workstation controller: a. Enter WRKCFGSTS *CTL on any command line. The Work with Configuration Status display appears. b. Specify 1 (Vary on) or 2 (Vary off) in the opt column next to your workstation controller, and press Enter. 7. Try the operation again. If you are still haing the same problem, call your hardware serice representatie. Chapter 9. Handling system problems and getting help through electronic customer support 157

Procedure 6: Recoering from tape or optical deice problem Verify the following: All tapes or optical deices are powered on and in a Ready (enabled) condition. Cables between the system and the tape or optical deice are properly connected (if applicable). Tape density and tape bits per inch (BPI) match. Tape path is cleaned. CD-ROM disc is clean, the format is supported, and the disc is loaded properly with the label side showing. Do the following: Do all the tapes or CD-ROM deice fail to read or write? Yes. Call your hardware serice representatie. No. Replace the tape and CD, and try the operation again. If the same failure occurs, call your hardware serice representatie. Procedure 7: Recoering from disk or diskette drie problem 1. Make sure that all disk and diskette deices are powered on and enabled. Some disk units may hae enable switches. 2. Make sure cables are properly connected between the system and disk or diskette deice (if applicable). 3. Do all diskettes fail to read or write? Yes. Call your hardware serice representatie. No. Replace the diskette and dtry the operation again. If the same failure occurs, call your hardware serice representatie. Procedure 8: Recoering from communication problem 1. Make sure that all communication equipment such as modems or transceier are powered on. Make sure all communication cables are properly connected. 2. Make sure the remote system is ready to receie your communication. 3. Verify the network equipment (or proider) is functional. This includes phone serice (for example, erify the status of communication lines). 4. Verify that the configuration is correctly specified for the failing communication or LAN facility. If you still hae the same problem, call your hardware serice representatie. Procedure 9: Recoering from system hang or loop condition If the system is logically partitioned, references to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. The system appears unable to accept commands. This problem can be caused by the system hardware or the system may be in a loop or hang condition. Complete the following tasks: 1. Perform a system main storage dump A system main storage dump gathers data on the current state of the system during the loop or hang condition. This information is critical for problem soling. Valuable diagnostic information will be lost if you do not collect the storage dump information before you try to do an IPL. 2. Call IBM Software Serice after performing the system main storage dump. 158 iseries: Getting started with iseries

Procedure 10: Recoering from intermittent problem 1. Enter the Analyze Problem (ANZPRB) command on any command line. The Select Type of System display appears. 2. Select Option 1 (This serer or attached deice). The Analyze problem display appears. 3. Select Option 3 (Hardware problem). The Problem Frequency display appears. 4. Select Option 1 (Yes) to get an intermittent checklist and follow instructions. If you still hae the same problem, call your hardware serice representatie. Procedure 11: Recoering when system console did not ary on If the system is logically partitioned, references to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. References to the system control panel refer to the Work with partition status display functions if the problem is in a secondary partition. References to the system control panel refer to the actual system control panel if the problem is in the primary partition. 1. Locate the workstation that is used as the primary system console. See Determining the primary or alternatie consoles for information about determining system consoles. 2. Make sure the workstation cables are attached properly, and set to the correct address. 3. Can you sign on to an alternatie console? Yes. Go to Step 4. No. Go to Step 5. 4. If you can sign on to an alternatie console, do the following: a. Make sure the primary console controller (for example, CTL01) and deice description (for example, DSP01) hae been created or restored. To check the deice description, use the command WRKCFGSTS *CTL. b. If descriptions exist, check the system operator message to determine why the primary console failed. Take correctie actions indicated in the message. If you still cannot sole the problem, set the system to the Normal mode, and call your software serice representatie. 5. If you cannot sign on to an alternatie console, do the following: a. Set the system to the Manual mode, select function 3, and press the Enter pushbutton to start an IPL (initial program load) until you see the IPL Option display. b. Were you able to get to the IPL Option display? Yes. Continue with Step 5c. No. Contact your IBM serice representatie. c. On the IPL Options display, specify Y (Yes) in the Define or change system at IPL field, N (No) in the Set major system option field and press Enter. d. On the Define or Change the System at IPL display, select Option 1 (Configuration commands), and press Enter. The Configuration Commands menu appears. e. Select Option 2 (Controller description commands) to see the controller description for the system console. Very that the controller (for example, CTL01) was created correctly. If the name has been changed, see Finding the primary console when system is operational Finding the primary console when system is operational on page 175. f. Select Option 3 (Deice description commands) to see the deice description for the system console. Verify that the deice (for example, DSP01) was created correctly. If the name has been changed, see Finding the primary console when system is operational Finding the primary console when system is operational on page 175. Chapter 9. Handling system problems and getting help through electronic customer support 159

Problem summary forms The problem summary form is used to record information displayed on the system unit control panel. When you perform problem analysis, you may be instructed to fill out this form so that your serice representatie can further analyze the problem. There are four forms, one for each of the following: 1. Systems with a single partition (except Model 270 and 8xx) 2. Systems with multiple partitions (except Model 8xx) 3. Model 270 and 8xx systems with a single partition 4. Model 8xx systems with multiple partitions Print out additional forms as required. Problem summary form for systems with a single partition (except Model 270 and 8xx) Date and time that the problem occurred: PRM or serice request number: Describe the problem: / / : : Message ID Message Text From/Send Program Instruction Number To/Receie Program Instruction Number 1. Record the mode. 2. Set the mode to Manual. 3. Place a check on the lines below to indicate which lights on the panel are on. Refer to control panel for the system units for a diagram of the control panel. Power On Processor Actie/Actiity System Attention 4. Press the Increment/Decrement buttons until 11-3 is shown in the Function/Data display. Press the Enter pushbutton. 5. Record the 8 characters shown in the Data display for function 11-3. 05 11xx 12xx 13xx 14xx 15xx 16xx 17xx 18xx 19xx 20xx Some systems will not hae the 05 on the Function/Data display. 160 iseries: Getting started with iseries

6. Press the Increment button. This action steps the Function/Data display to the next higher number (12, 13, and so on) and blanks the Data display. 7. Press the Enter pushbutton. This action shows a new set of 8 characters in the Data display. Record this data on the form. 8. Repeat steps 6 and 7 until data has been recorded through function 20. All functions may not be displayed, depending on the failure. 9. Set the same mode as recorded in step 1 of this form. Press the Increment/Decrement buttons until the number 11-3 is shown in the Function/Data display. Press the Enter pushbutton. The original system reference code (SRC) appears. 10. Return to the step that sent you here. Comments: Problem summary form for systems with multiple partitions (except Model 8xx) Date and time that the problem occurred: Partition state: Partition ID: Partition ersion: Partition name (optional): Partition release: Describe the problem: / / : : Message ID Message Text From/Send Program Instruction Number To/Receie Program Instruction Number 1. Record the mode. 2. From Work with Partitions screen, use option 10 to set the mode to Manual. For help getting to this screen, refer to Accessing panel functions on a secondary partition. 3. Place a check on the lines below to indicate which lights on the panel are on. Refer to control panel for the system units for a diagram of the control panel. Power On Processor Actie/Actiity System Attention 4. Record the 8 characters shown in the Display Partition Status screen for Reference Codes 11x through 19xx. 05 11xx 12xx 13xx 14xx 15xx 16xx 17xx 18xx 19xx 20xx Chapter 9. Handling system problems and getting help through electronic customer support 161

5. Go to the system control panel to find and record the alue for the 20xx Reference Code. 6. Set the same mode as recorded in step 1 of this form. 7. Return to the step that sent you here. Comments: Problem summary form for Model 270 and 8xx systems with a single partition Date and time that the problem occurred: Describe the problem: / / : : Message ID Message Text From/Send Program Instruction Number To/Receie Program Instruction Number 1. Record the mode. 2. Place a check on the lines below to indicate which lights on the panel are on. Refer to control panel for the system units for a diagram of the control panel. Power On Processor Actie/Actiity System Attention 3. Go to the system control panel to find and record the alue for functions 05, 11, 12, and 13. See Collecting System Reference Codes for step-by-step instructions on finding System Reference Codes. Use the grid below to record the characters shown on the Function/Data display. 4. Set the same mode as recorded in step 1 of this form. Comments: 05 11 162 iseries: Getting started with iseries

12 13 20 Problem summary form for Model 8xx systems with multiple partitions Date and time that the problem occurred: Partition state: Partition ID: Partition ersion: Partition name (optional): Partition release: Describe the problem: / / : : Message ID Message Text From/Send Program Instruction Number To/Receie Program Instruction Number 1. Record the mode. 2. From Work with Partitions screen, use option 10 to set the mode to Manual. For help getting to this screen, refer to Accessing panel functions on a secondary partition. 3. Place a check on the lines below to indicate which lights on the panel are on. Refer to control panel for the system units for a diagram of the control panel. Power On Processor Actie/Actiity System Attention 4. On the grid below, record the characters shown on the Display Partition Status screen for functions 05, 11, 12, 13. Chapter 9. Handling system problems and getting help through electronic customer support 163

In the product actiity log and other software displays, the System Reference Code (SRC) appears much like it does for earlier releases. One differenc eis that the first word will hae up to 32 characters of text. Another difference is that the word will be a number from 1 to 9 instead of 11 to 19. This helps to aoid confusing the word number with the function number used to find it. 5. Go to the system panel to find and record the alue for function 20. See Collecting system reference codes for step-by-step instructions. Comments: 05 11 12 13 20 Accessing panel functions on a secondary partition Note: Most partition panel functions for a secondary partition are aailable from the console of the secondary partition. All partition panel functions for a secondary partition are aailable from the partition status screens on the primary partition console. If the panel function required is not aailable from the console of the secondary partition, go to the primary partition console to access that panel function. 1. From the console of the primary partition or the secondary partition, enter STRSST on any command line to start SST (or enter STRDST on any command line to start DST). 164 iseries: Getting started with iseries

2. From the SST or DST screen, select Option 11 (Work with system partitions). 3. From Work with System Partitions, select Option 2 (Work with partition status). Additional panel functions and information are aailable by pressing F10 (Display partition status), F11 (Work with partition configuration), and F23 (More options). For panel functions 11 through 19: Press F10 (Display partition status). Press F9 (Include reference code detail). 4. For panel function 20, use the system control panel. Additional information on this topic can be found in these sources: Logical partitions Analyzing a new problem A new problem is one that you detect while using the system and which has not been recorded in the problem log, or one that is in the problem log with a status of opened. If the system is logically partitioned, references to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. When reporting problems electronically, use the same contact information for each partition on the system. To analyze a new problem that has not been recorded in the problem log 1. Use the Analyze Problem (ANZPRB) command. 2. Select the option that most closely corresponds to the problem you hae encountered on the Analyze a New Problem display. A series of steps then guides you through problem analysis. As you progress, a symptom string is built from your responses. If you encounter the Problem Analysis display while you are building your symptom string, contact IBM serice before continuing. See Getting help with problems for more information on who to call. 3. When you complete problem analysis, the collected information is placed in the problem log. To analyze a problem that has been recorded in the problem log with opened status 1. Type DSPMSG QSYSOPR on any command line and press Enter to see the system operator messages. If the message is highlighted, use option 5 (Display details and reply) for the message. On the Additional Message Information display, press F14 (Work with problem). If the message has an asterisk (*) next to it, press F14 (Work with problme) on the Display Messages display. 2. Select option 8 (Work with problem), and then option 1 (Analyze problem). As you probgress through problem analysis, a symptom string is built from your responses. 3. When you complete problem analysis, the collected information is placed in the problem log. You can also use the following method to analyze a problem with open status in the problem log: 1. Enter the Work with problem (WRKPRB) command on any command line. 2. Select option 8 (Work with problem) for the problem, and then option 1 (Analyze problem). Reporting hardware and software problems For hardware failures that do not disable system operation, electronic customer support proides a fast, electronic method for requesting the assistance of an IBM serice representatie with replacement parts. Using this method, you may report failures occuring on your system and selected input or output deices. Chapter 9. Handling system problems and getting help through electronic customer support 165

For problems with software or Licensed Internal Code, you should notify the IBM serice system of the failure and related symptoms. The problems that are detected by the system can be reported either manually Reporting problems detected by the system or automatically Setting Up Automatic Cleanup on page 57. The system searches a file of known problems and, if aailable, sends a fix to your system for installation. If a problem is new, a problem management record (PMR) is created by the IBM serice system. The PMR number is returned to your iseries system. Depending on your contract with IBM, you may or may not be entitled to oice support (telephone). If you hae oice support, IBM serice center personnel will contact you, if requested, and work with you to resole the problem. If you do not hae oice support, you may iew the serice centers response by using the Query Problem Status (QRYPRBSTS) command. For more information on the QRYPRBSTS command, see Querying problem status Querying problem status on page 167. To send a serice request or log a problem, go to one of the following: Sending a serice request immediately Sending a serice request immediately on page 167 Sending a serice request later Sending a serice request later on page 168 Reporting problems by oice Reporting problems by oice on page 169 Adding notes to your problem record Adding notes to your problem record on page 169 For information on how to find a problem, see Finding a preiously reported problem Finding a preiously reported problem on page 169. Reporting problems detected by the system The system problem log allows you to display a list of all the problems recorded on the system. You can also display detailed information about a specific problem. For example, you can see the product type and serial number of the deice that had the problem, the date and time of the problem, the part that failed, where the part is found, and the problem status. You can also analyze and report a problem, or determine any serice actiity. To report a problem that has an entry in the problem log, do the following: 1. Type WRKPRB on any command line and press Enter. The Work with Problems (WRKPRB) display appears. 2. If you hae a problem ID, look for an entry with the same ID on the Work with Problems display. Select option 8 (Work with problem) for the problem you want to work with. Press Enter and the Work with Problems display appears. 3. Select option 2 (Report problem) on the Work with Problems display. Press Enter and the Verify Contact Information display appears. 4. To change any fields that appear on the Verify Contact Information display, type oer the current information and press Enter. The system includes the new information in the serice request. 5. Select the seerity leel that closely relates to the seerity of the problem on the Select Problem Seerity display. 6. Select who should receie and process your request on the Select Serice Proider display. 7. Select when and how you want to send the serice request on the Select Reporting Option display. Automatic problem reporting The automated problem analysis function runs problem analysis routines automatically when the system detects a problem. The problem reporting function notifies the serice proider of the software problem. To run these functions, the appropriate serice attributes must be set to *YES. If these attributes are set to *NO, you will need to run the problem analysis manually. The default alue for serice attributes is *NO. Use the Display Serice Attribute (DSPSRVA) command to display the serice attributes, or use the Change Serice Attributes (CHGSRVA) command to change the serice attributes. 166 iseries: Getting started with iseries

To change serice attributes, fill in the appropriate information in the fields. Specify *YES in the Analyze problem field to automatically run problem analysis at the time of the failure. Problem analysis includes programs that attempt to isolate or correct the problems. Automated problem analysis applies mostly to hardware problems, and some software problems in Licensed Internal Code. To determine which problems are analyzed automatically and which ones are not, use the Work with Problem (WRKPRB) command. If the status is Opened, it indicates that the problem has not been analyzed. For problems that are not analyzed automatically, you can use the Work with Problems (WRKPRB) command to run the problem analysis manually. Go to Problems with a symptom for detailed information about the command, and for examples of how the command is used. When *YES is specified in the Report problem automatically field, software problems are reported automatically to the serice proider. Your serice proider is specified in the Control point name field. For hardware problem reporting, contact your serice proider. Querying problem status To retriee the latest status of a preiously reported problem Finding a preiously reported problem on page 169, use one of the following methods: Method 1: 1. On any command line, type QRYPRBSTS on any command line, and press F4. The Query Problem Status (QRYPRBSTS) display appears. Note: Currently, the QRYPRBSTS command is not enabled to query hardware problems. 2. If you know the problem management record (PMR) number, type *PMR in the Problem identifier field and press Enter. Additional fields appear on the display. Type the PMR number in the Serice number field and press Enter. If you know the WRKPRB problem ID number, type the 10-digit ID number for the problem in the Problem identifier field and press Enter. If you don t know the problem ID number, see Finding a preiously reported problem Finding a preiously reported problem on page 169 for instructions on how to find this 10-digit number. 3. After the query is complete, enter: WRKPRB xxxxxxxxxx where xxxxxxxxxx is the 10-digit problem ID number. The Work with Problem display appears. 4. Type Option 12 (Enter text) next to the problem entry and press Enter. The Select Text Type display appears. 5. Select Option 10 (Query Status text). The Query results are shown. Method 2: 1. On any command line, type WRKPRB and press Enter. The Work with Problems display appears. 2. Find the problem entry for which you want to query the status. To start a query, the problem entry must hae a status of Answered or Sent. 3. Type Option 8 (Work with problem) next to the problem entry. The Work with Problem menu appears. 4. Select Option 41 (Query problem status text). The Results of the query are shown. Note: The QRYPRBSTS command does not apply to problem entries that hae a Fix request specified in the problem description column of the Work with Problem display. Sending a serice request immediately If you decide to send a serice request now, select option 1 (Send serice request now) on the Select Reporting Option display. The system packages the problem log entry as a serice request. Then your iseries system automatically dials the IBM serice proider system, and the system transmits the problem to the serice proider. Chapter 9. Handling system problems and getting help through electronic customer support 167

The serice proider determines whether the request is for hardware or software serice, and takes the appropriate action that is described below. Hardware Serice: If the serice proider is IBM, and if no fixes are found that match your problem symptoms, one of the following happens: Your request is sent to an IBM serice representatie. An IBM Customer Assistance Group representatie calls you to assist in further problem definition. The connection to the serice proider system ends, and the status of the problem in the problem log is changed to SENT. Software Serice: A search is performed against the database of fixes by using the symptom string you created during problem analysis. If the serice proider is IBM, a match is found, and a fix is aailable, IBM transmits the fix to you electronically. Or, IBM sends a fix tape to you through normal mail channels. The size of the fix and its requisites determine whether IBM sends the fix electronically or through the mail. The fixes that you receie electronically are placed in the QGPL library with a file name of the fix number that is preceded by a Q and a file type of SAVF. If a match is not found or the fix is not aailable, you see the Sae APAR Data display. This display saes the following information about your problem: History log Job information Hardware and software resources Error log entries Vertical Licensed Internal Code log entries Problem log entries Pictures of displays You can then forward this information to the IBM Software Support Center to help you sole your problem. The connection to the serice proider ends when you receie a fix or when your problem is opened for further inestigation. The system changes the status of the problem to SENT or to ANSWERED in the problem log. Note: Wheneer you use electronic customer support, the iseries needs to dial out to the IBM system. Remember to hae the electronic customer support modem aailable and powered on. Sending a serice request later If you decide to send a serice request later, select option 2 (Do not send serice request) on the Select Reporting Option display. The status of the problem in the problem log changes to PREPARED. To submit a problem with PREPARED status, follow the directions in Reporting problems detected by the system Reporting problems detected by the system on page 166. When the system reports the problem, the problem log entry is packaged as a serice request. Then your system automatically dials the serice proider system, and the system transmits the problem to the serice proider. To report all problems in the problem log that hae a status of PREPARED, do one of the following: 1. On the Work with Problems display, press F16 (Report prepared problems). 168 iseries: Getting started with iseries

2. On any command line, type SNDSRVRQS *PREPARED and press Enter. The connection to the serice proider system ends when you receie a fix or when your problem is opened for further inestigation. The system changes the status of the problem to SENT or to ANSWERED in the problem log. Note: Wheneer you use electronic customer support, the iseries needs to dial out to the IBM system. Remember to hae the electronic customer support modem aailable and powered on. Reporting problems by oice If you find that you are not connected to a telephone line, or your communications lines are down, you can report a problem with your system by oice (telephone). To report the problem by telephone, follow the directions in Reporting problems detected by the system Reporting problems detected by the system on page 166. When you get to the Select Reporting Option display, select option 3 (Report serice request by oice). The Report Serice Request by Voice display gies you the telephone number of the serice proider for your specific problem. Note: If the serice proider is IBM, IBM assigns a serice number to the problem. To put this number in the problem log, press F14 (Specify serice-assigned number) on the Report Serice Request by Voice display. Adding notes to your problem record To attach a note or add to an existing note in the problem record, do the following: 1. Use the Work with Problem (WRKPRB) command. 2. Select option 12 (Enter text) on the Work with Problems display. The Select Text Type display appears. 3. Select Option 1 (Problem description) to enter problem description. Only the text that is entered with this option is sent to the serice proider along with the problem. Notes should be typed in the following format to keep a chronological record of eents. On the first line, type a brief description of the problem. On the second line, type the current date. On the third line, type in the note that you want to send. Use as many additional lines (up to 20) as you need. Include the following information in your notes: Any recent release update that you hae applied to the system Any changes you made in the system configuration Any new program or feature that you are using Anything that may be different since the last time the program was run Finding a preiously reported problem To find a preiously reported problem, you need to know the IBM Serice-assigned number, also known as the problem management record (PMR). Once you hae this number, type the following on any command line: WRKPRB SRVID(XXXXX) where XXXXX is the PMR number, then press the Enter key. Chapter 9. Handling system problems and getting help through electronic customer support 169

If you do not hae the PMR number, use the Work with Problem (WRKPRB) command and search the list for the problems with a status of SENT, VERIFIED, ANSWERED, and CLOSED. Replacing Battery Power Unit on Models 5xx, and Tower FC507x and FC508X The part number for the battery power unit is 86G8040. 1. Do not power off the system. 2. Remoe the front coer (1). 3. Pull out and lift to remoe the screen (2). Attention: Remoing the battery power unit while the system is running on battery power will cause the system to fail and may damage the battery power unit and the card enclosure. Ensure that the system is not running on battery power. As a test, be sure that the console accepts system commands before remoing the battery power unit. 4. Caution: Be careful when remoing or installing this part or unit. This part or unit is heay, but has a weight smaller than 18 kilograms (39.7 pounds). (RSFTC201) 170 iseries: Getting started with iseries

Loosen the screws and use two hands to pull the battery power unit out (3). 5. Install the battery power unit by reersing the remoal procedure. Caution: The battery is a lead-acid battery. To aoid possible explosion, do not burn. Exchange only with the IBM-approed part. Recycle or discard the battery as instructed by local regulations. In the United States, IBM has a process for the collection of this battery. For information, call 1-800-426-4333. Hae the IBM part number for the battery unit aailable when you call. Performing a main storage dump If the system is logically partitioned, references to the system, system console, displays, system commands, and system alues are relatie to the partition haing a problem. A main storage dump (MSD) is a process of collecting data from the system s main storage. A main storage dump can be formed in the following ways: Automatically: by the serice processor as the result of a system failure. Manually: by performing a function 22 on the control panel when the system waits, loops, or appears to hae an operating system failure. You can perfrom this task by selecting option 22 from the Work with partition status display. Choose the task to perform: Performing an automatic MSD Setting Up Automatic Cleanup on page 57 Performing a manual MSD Performing a manual MSD on page 172 Performing a manual MSD on a logical partition6 on page 172 Reporting and copying a current MSD Copying a profile on page 34 Reporting a MSD Reporting a MSD on page 173 Deleting an MSD Deleting an MSD on page 174 Performing an automatic MSD After a failure that causes the system to perform an MSD, the Main Storage Dump Occurred display will appear. When that happens, go to reporting and copying a current MSD Copying a profile on page 34 Main Storage Dump Occurred +--------------------------------------------------------------------------------+ Main Storage Dump Occurred S/N 10xxxxx The system has failed. Report the following information to your IBM Serice representatie. Function 11...: A1D03000 Function 12...: 69E0015F Function 13...: 0000308F Function 14...: FFFFFC00 Function 15...: 0C211008 Function 16...: 00000000 Function 17...: 00000000 Function 18...: 003954B0 Function 19...: 00311050 Type/Model/Feature...: 9402 400 2131 Warning: The Main Storage Dump (MSD) must be copied for serice. Failure to copy the Main Storage Dump will limit the ability to diagnose the failure. Press Enter to copy the MSDfor serice or iew the MSD. Chapter 9. Handling system problems and getting help through electronic customer support 171

F3=Exit F12=Cancel +--------------------------------------------------------------------------------+ Performing a manual MSD Use this procedure on the primary partition or on a system without logical partitions. To place the data from the system s main storage to the load-source disk, perform the following procedure: 1. If your system has logical partitions, try to power them off. 2. Verify that there are no interactie jobs running. a. Select Manual mode. b. Use the Increment/Decrement buttons to display function 22 (main storage dump). c. Press Enter pushbutton on the control panel. 3. Is 0000 0000 displayed on the control panel for more than 30 seconds? Yes. The multiple function IOP or serice processor is not responding to a request from the control panel. Go to Getting help with problems. This ends the procedure. No. Continue to the next step. 4. An attention SRC, A1xx 3022, is displayed, which indicates that function 22 has been selected. Reselect function 22, press Enter on the control panel, and wait for the dump to complete. When the dump is complete, the Main Storage Dump Occurred display is shown as below. 5. Did the MSD complete successfully? The appearance of an A1D0 300x or A6Dx 3000 SRC on the Main Storage Dump Occurred display indicates a successful manual MSD. 6. Go to Getting help with problems. This ends the procedure. Performing a manual MSD on a logical partition Use this procedure on a logical partition. You should only perform a secondary partition MSD if under the direction of customer support. To place the data from system s main storage to the load-source disk, perform the following procedure: 1. On the logical partition or on the primary partition, start Dedicated Serice Tools (DST). 2. Select option 11 (Work with system partitions). 3. Select option 2 (Work with partition status). 4. Select the logical partition on which you want to perform the MSD. Initiating a MSD against the primary partition is equialent to initiating a MSD from the control panel. 5. Is the partition in Manual mode? Yes. Continue to the next step. No. Select option 10 (Mode manual). 6. Select option 22 (Force Main Storage Dump). 7. Select option 10 to confirm. Wait for the dump to complete. When the dump is complete, the Main Storage Dump Occurred display is shown on the selected logical partition. 8. Did the MSD complete successfully? The appearance of an A1D0 300x or A6Dx 3000 SRC on the Main Storage Dump Occurred display indicates a successful manual MSD. 9. Go to Getting help with problems. This ends the procedure. Reporting and copying a current MSD This procedure copies a MSD to a predefined storage area on the system. This will preent MSD from being oerwritten in the eent another dump occurs. 1. From the Main Storage Dump Occurred display, press Enter. The Main Storage Dump Manager appears. 2. Select option 1 (Work with current main storage dump). The Work with Current Main Storage Dump display appears. 172 iseries: Getting started with iseries

3. Select option 1 (Display/Print). The Display Main Storage Dump display appears. 4. Select option 1 (MSD summary). The Main Storage Dump Summary display appears. This display shows the system reference code, date, and time of the MSD, and Licensed Internal Code leel. 5. Record the summary information and report it to your serice proider. 6. Press F12 (Cancel) twice to return to the Main Storage Dump Manager display. 7. Select option 3 (Copy to ASP). The Copy Main Storage Dump to ASP display appears. Type a dump description, then press Enter to start copying the dump. After the dump is copied, a message will be displayed indicating whether the MSD copy completed. If the message indicates Copy completed normally, you are done with this procedure. If you do not see this message, continue to the next step. 8. Has your serice proider requested a tape copy of the MSD? Yes. Continue to the next step. No. Work with your serice proider on the problem. 9. To copy MSD to a tape deice, do the following: a. Select option 2 (Copy to media). The Copy Main Storage Dump to Media display appears. b. Load the media and follow the instruction on the display. c. When the copy procedure is successfully completed, process the tape according to your serice proider s instruction. If you encounter a problem with the copy procedure, contact your serice proider. This ends the procedure. Reporting a MSD If your system has the Main Storage Dump auto copy enabled, your system may hae automatically copied the current MSD to the ASP using dump description Auto Copy, and then re-ipled the system. 1. On any command line, enter STRSST. 2. Select option 1 (Start a serice tool). The Start a Serice Tool display appears. 3. Select option 6 (Main storage dump manager). The Main Storage Dump Manager display appears. 4. Select option 2 (Work with copies of main storage dumps). The Work with Copies of Main Storage Dumps display appears. 5. Find the dump with the description of Auto Copy and select option 5 (Display/Print). The Display Main Storage Dump display appears. 6. Select option 1 (MSD Summary). The Main Storage Dump Summary display appears. This display shows the system reference code, date, and time of the MSD, and Licensed Internal Code leel. 7. Report the summary information to your serice proider. 8. Press F3 (Exit) to return to the Work with Copies of Main Storage Dumps Display. 9. If the dump has a description of Auto Copy, rename it so that another auto copy and re-ipl can occur if necessary. Select option 7 (Rename). The Rename Main Storage Dump display appears. Type a new dump description, then press Enter. 10. Has your serice proider requested a tape copy of the MSD? Yes. Continue to the next step. No. Work with your serice proider on the problem. 11. To copy MSD to a tape deice, do the following: a. Select option 8 (Copy to media). The Copy Main Storage Dump to Media display appears. b. Load the media and follow the instructions on the display. c. When the copy procedure is successfully completed, process the tape according to your serice proider s instruction. If you encounter a problem with the copy procedure, contact your serice proider. Continue with the procedure in Deleting an MSD Deleting an MSD on page 174 Chapter 9. Handling system problems and getting help through electronic customer support 173

Deleting an MSD This procedure is used when dump copies are no longer needed by your serice proider. 1. On any command line, enter STRSST. 2. Select option 1 (Start a serice tool). The Start Serice Tool display appears. 3. Select option 6 (Main storage dump manager). The Main Storage Dump Manager display appears. 4. Select option 2 (Work with copies of main storage dumps). The Work with Copies of Main Storage Dumps display appears. From this display you can see the list of dump copies. If you want to delete any dump compies, type 4 next to the dump copies, and press Enter twice. To exit SST, press F3 (Exit) three times, and then press Enter. Determining the primary or alternate consoles If the Operations Console has been configured as the primary console, the system will start the Operations Console. If the Operations Console has not been configured, the primary console is a workstation that is attached to the first Input/Output Processor (IOP) that is capable of supporting workstations. In addition to the primary console, the system can assign up to two alternatie consoles. The first alternatie console can only be a TWINAX workstation tat is attached to the same IOP as the primary console. The second alternatie console is a workstation that is attached to the next IOP or Input/Output Adaptor (IOA) that is capable of supporting workstations. The IOP that supports the console must be on the first system bus (bus 1). If a workstation is not correctly attached to the first IOP that is capable of attaching workstations, then the system will not assign a primary console. The system will display a reference code on the operator s panel. In addition, if the IPL (initial program load) mode is set to Manual, the system will stop. Primary console workstation requirements In order to be the primary console, the workstation must be operational and hae the correct port and address. If the workstation is a PC, it must also hae anactie emulation program on the workstation. The workstation requirements are: TWINAX workstation - Port 0 Address 0 ASCII workstation - Port 0 PC attached to ASCII IOP or IOA - Port 0 - PC software to emulate a 316x or 3151 terminal PC attached to TWINAX IOP - Port 0 Address 0-5250 emulator software actie on PC PC attached to a LocalTalk IOA (6054) - SNAps 5250 Version 1.2 (or aboe) application - Console capable selected on MacIntosh (IOA conerts to Port 0 Address 0) PC attached to a 2609, 2612, 2699, or 2721 communications IOA - Client Access Console cable attached to the 2609 or 2612 P2 port (part number 46G0450 or 46G0479), 2699 (part number 21H3779), or 2721 (part number 44H7504) - Operations Console cable attached to the 2609 or 2612 (part number 97H7555), 2699 (part number 97H7556), or 2721 (part number 97H7557) - 5250 emulation or Rumba actie on PC 174 iseries: Getting started with iseries

Finding the primary console when system is operational The following methods can be used to find the primary console: Method 1: Look for a sign-on display with a DSP01 in the upper-right corner. Method 2: If the deice name (DSP01) for the console has been changed, you can erify the deice name for the primary console by doing the following: 1. Enter DSPCTLD QCTL on any command line. The Display Controller Description display appears. Find the Resource name parameter (such as CTL01) and record it. 2. Enter PRTDEVADR rrrrr on any command line, where rrrr is the resource name you recorded. If the printer is actie, the data will be printed. Method 3: 1. Enter STRSST on any command line. The System Serice Tools display appears. 2. Select option 1 (Start a serice tool). The Start a Serice Tool display appears. 3. Select option 7 (Hardware serice manager). The Hardware Serice Manager display appears. 4. Select option 2 (Logical hardware resources). The Logical Hardware Resources display appears. 5. Select option 1 (System bus resources). The Logical Hardware Resources on System Bus display appears. The < symbol indicates the IOP that the system console is attached to. Use option 9 (Resource associate with IOP and display detail) to find the location of the system bus, board, and card. Finding the primary console when system power is off Use one of the following: Power on the system in the Manual mode and look for the IPL and Install System display. Power on the system in the Normal mode and look for DSP01 on the sign on display. Note that the name may hae been changed. See Finding the primary console when system is operational Finding the primary console when system is operational to determine the display name. Getting help with system operation problems The following table shows an oeriew of the system support structure and gies you guidelines on who to call for your specific problem. Before calling for help, fill out the appropriate problem summary form. Your serice representatie may need the information you hae filled in to further analyze the problem. For up-to-date contact information, isit the IBM web site. Then, print this page and use information from the site to complete the table below. Refer to the page wheneer you need contact information. Chapter 9. Handling system problems and getting help through electronic customer support 175

Type of Problem Call Telephone Numbers Question Adice IBM iseries 400 Support Line or 1-800-237-5511 Migrating IBM Business Partner How to Operating Configuring Ordering Performance 1-800-IBM-CALL General information iseries 400 Marketing Specialist or IBM Direct Support Line or IBM Business Partner 1-800-IBM-4YOU Software Fix information Operating system problem IBM application program Loop, hang, or message Hardware IBM system hardware broken Hardware system reference code (SRC) IBM input/output (I/O) problem Upgrade IBM Software Serice 1-800-237-5511 IBM Hardware Serice 1-800-IBM-SERV 176 iseries: Getting started with iseries

Printed in U.S.A.