AS/400 Advanced Series
IBM
Operator Tasks –
AS/400 Advanced Series
IBM
Operator Tasks –
Take Note!
Before using this information and the product it supports, be sure to read the general information under “Notices” on page ix.
Second Edition (November 1996)
This edition applies to the licensed programs IBM System/36 System Support Program Products, (Program 5716-SSP), Release 7 | Modification 5; IBM Operating System/400, (Program 5716-SS1), Version 3 Release 7 Modification 0, and to all subsequent releases
and modifications until otherwise indicated in new editions.
Make sure that you are using the proper edition for the level of the product.
Order publications through your IBM representative or the IBM branch serving your locality. If you live in the United States, Puerto Rico, or Guam, you can order publications through the IBM Software Manufacturing Solutions at 800+879-2755. Publications are not stocked at the address given below.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication. You can also mail your comments to the following address:
IBM Corporation Attention Department 542 IDCLERK
3605 Highway 52 N
Rochester, MN 55901-7829 USA or you can fax your comments to:
United States and Canada: 800+937-3430 Other countries: (+1)+507+253-5192
If you have access to Internet, you can send your comments electronically to [email protected]; IBMMAIL, to IBMMAIL(USIB56RZ).
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Contents
Notices . . . . ix
Trademarks . . . . ix
About Operator Tasks – Multiple Operating Systems (SC21-8384) . . . xi
Who Should Use This Book . . . xi
What You Should Do Before You Use this Book . . . xii
Where to Go for Other Information . . . xiii
AS/400 System Operation
| Chapter 1. AS/400 System Operations Tasks . . . 1-1 What You Need to Know about Your Control Panel . . . 1-1 IPL Types and Modes . . . 1-5 | Uninterrupted Power System . . . 1-6 Quick Reference to Operator Tasks . . . 1-7 | Additional Information that Applies to the AS/400 System . . . 1-8
OS/400 for the SSP Operator
Chapter 2. Starting the System Unit and OS/400 Operating System . . . 2-1 Using the OS/400 Sign On Display during an IPL . . . 2-3 Chapter 3. Stopping the System Unit . . . 3-1 Stopping the AS/400 System . . . 3-1 Chapter 4. The OS/400 System Console . . . 4-1 Device Name of the System Console . . . 4-1 How the System Console Display is Different from Other Displays . . . 4-1 Chapter 5. Handling OS/400 Messages . . . 5-1 Most Common Types of OS/400 Messages . . . 5-1 Displaying OS/400 Messages . . . 5-1 Identifying Messages from the System . . . 5-5 How to Handle Break Messages . . . 5-7 Displaying OS/400 System Operator Messages . . . 5-7 Working with OS/400 Message Queues . . . 5-10 Handling OS/400 Error Messages . . . 5-14 Understanding OS/400 Keyboard Error Messages . . . 5-15 Sending OS/400 Messages . . . 5-16 Chapter 6. Using OS/400 CL Commands to Do Tasks . . . 6-1 CL Commands — Overview . . . 6-1 Using Operational Assistant Displays . . . 6-2 Using Assistance Levels and User Profiles . . . 6-3 Doing Specific Tasks (GO) . . . 6-9 Chapter 7. Printing with OS/400 . . . 7-1 Definitions . . . . 7-1 Finding OS/400 Printer Output . . . 7-3
Managing Printed Output . . . 7-7 Working with Printers . . . 7-10 Working with Spooled Files . . . 7-13 Working with All Output Queues . . . 7-14 Comparing System/36 Print Commands to OS/400 Print Commands . . . 7-15 Chapter 8. Working with OS/400 Subsystems . . . 8-1 Definitions . . . . 8-1 Working with a Subsystem . . . 8-2 Chapter 9. OS/400 System Security . . . 9-1 Levels of Security . . . 9-1 Changing Passwords . . . . 9-2 Chapter 10. Controlling OS/400 Jobs . . . 10-1 Submitting Batch Jobs . . . 10-1 Working with Batch Jobs . . . 10-5 Looking at Job Queues . . . 10-10 Working with Signed-On Users . . . 10-12 Displaying Detailed Job Information . . . 10-14 Changing How a Job Is Run . . . 10-16 Working with Job Logs . . . 10-19 Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1 Displaying and Changing Device Status . . . 11-1 Renaming a Device . . . 11-2 Displaying and Changing a Device Description . . . 11-3 Printing Local Device Addresses . . . 11-3 Activating Communications Lines and Controllers . . . 11-4 Configuring Remote Communications . . . 11-5 Using a Switched Communications Line . . . 11-6 Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . 12-1 Saving the Entire System . . . 12-1 Restoring the Entire System . . . 12-2 Saving the OS/400 Operating System . . . 12-2 Restoring the OS/400 Operating System . . . 12-3 Saving AS/400 Storage . . . 12-3 Restoring AS/400 Storage . . . 12-3 Saving Individual OS/400 Objects . . . 12-3 Restoring Individual OS/400 Objects . . . 12-5 Chapter 13. Working with Licensed Internal Code and OS/400 Program
Temporary Fixes . . . . 13-1 AS/400 Program Maintenance Strategy . . . 13-1 Ordering LIC and OS/400 PTFs and PTF Information . . . 13-2 Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . 14-1 Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . 14-3 Transferring to an AS/400 Advanced 36 Machine Using the STRM36PRC
Command . . . . 14-6 Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7
SSP for the OS/400 Operator
Chapter 15. Starting an AS/400 Advanced 36 Machine . . . 15-1 Starting the AS/400 Advanced 36 Machine from the OS/400 Command line 15-1 Starting the AS/400 Advanced 36 Machine Automatically . . . 15-5 Chapter 16. Stopping an AS/400 Advanced 36 Machine . . . 16-1 Putting the AS/400 Advanced 36 Machine In a Dedicated State . . . 16-1 Stopping an AS/400 Advanced 36 Machine from the SSP System Console . 16-2 Stopping an AS/400 Advanced 36 Machine from the OS/400 Operating
System . . . . 16-3 Chapter 17. Operating the SSP Console and SSP Subconsoles . . . 17-1 The SSP Console: A Way of Controlling the AS/400 Advanced 36 Machine 17-1 The SSP Subconsole: A Way of Controlling SSP Printers . . . 17-1 Transferring the SSP Console Function to an Alternative SSP Console . . . 17-2 Using the SSP Console Display . . . 17-4 Using the Subconsole Display . . . 17-5 Chapter 18. Handling SSP Messages . . . 18-1 How You Know That You Have an SSP Message . . . 18-1 Types of SSP Messages . . . 18-2 Displaying SSP Messages at the SSP Console or Subconsole . . . 18-6 Replying to SSP Messages at the SSP Console or Subconsole . . . 18-7 Sending SSP Messages . . . 18-9 SSP Keyboard Error Messages . . . 18-10 Displaying Keyboard Messages . . . 18-11 Chapter 19. Using SSP Commands and Procedures to Do Tasks . . . . 19-1 Using Help for Commands and Procedures . . . 19-1 Chapter 20. Printing with SSP . . . 20-1 Finding SSP Printer Output . . . 20-2 Managing Printer Output — Command Summary . . . 20-3 Managing Printer Output — Complete Details . . . 20-3 Working with Spool Writers . . . 20-6 Creating Printed Output — Selected Examples . . . 20-8 Configuring Printer Options . . . 20-8 Chapter 21. Working with SSP Subsystems . . . 21-1 Definitions . . . . 21-1 Starting an SSP Subsystem . . . 21-2 Ending an SSP Subsystem . . . 21-2 Displaying the Status of an SSP Subsystem . . . 21-2 Chapter 22. SSP Security . . . . 22-1 Password Security . . . . 22-1 Menu Security . . . . 22-1 Badge Security . . . . 22-2 Communications Security . . . . 22-2 Resource Security . . . . 22-3 Working with SSP Security . . . 22-3
Chapter 23. Controlling SSP Jobs . . . 23-1 Working With Current Running Jobs . . . 23-2 Working with the History File . . . 23-2 Chapter 24. Working with SSP Devices and Communications . . . 24-1 Displaying and Changing Device Status . . . 24-1 Printing Local Device Addresses . . . 24-1 Displaying Communications Lines and Controllers . . . 24-1 Configuring Remote Communications Lines . . . 24-1 Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine
Information . . . . 25-1 Saving and Restoring an AS/400 Advanced 36 Machine . . . 25-1 Saving and Restoring the SSP Operating System, Licensed Programs, and
Other SSP System Files . . . 25-2 Chapter 26. Working with SSP Program Temporary Fixes . . . 26-1 AS/400 Advanced 36 Program Maintenance Strategy . . . 26-1 Ordering SSP PTFs and PTF Information . . . 26-3 Displaying or Printing Cumulative PTF Information . . . 26-3 Installing Cumulative SSP PTF Packages . . . 26-5 Corrective SSP PTFs (Patches) . . . 26-5 Mapping the TC Device ID to the CD-ROM Drive . . . 26-16 What to Do if the Mapping Failed . . . 26-17 Changing the TC Device ID Back to a Tape Cartridge Drive . . . 26-17 Chapter 27. Establishing a Communications Link for Remote
Workstations . . . . 27-1 Using Remote Work Station Support . . . 27-1
AS/400 System Common Operator Tasks
Chapter 28. Problem Handling . . . . 28-1 Hardware Problem Isolation . . . 28-1 Handling AS/400 Advanced 36 Machine Error Codes . . . 28-9 Chapter 29. System-to-System Communications - ILAN
Communications . . . . 29-1 Setting up ILAN Communications . . . 29-3 Understanding Default Startup Settings . . . 29-3 Manually Starting the ILAN . . . 29-3 Automatically Starting ILAN Communications . . . 29-6 Disabling Automatic Startup of ILAN . . . 29-7 Finding Out the OS/400 Control Point Name . . . 29-8 Stopping ILAN Communications . . . 29-8 ILAN Communications Verification . . . 29-10 Finding Out Why ILAN Is Not ACTIVE or VARIED ON . . . 29-13 Using Display Station Pass-Through . . . 29-15 Chapter 30. Using CL Commands to Manage AS/400 Advanced 36
Configurations and Machines . . . 30-1 Using the Work with AS/400 Advanced 36 Machine Command . . . 30-1 Using the Work with AS/400 Advanced 36 Machine Configuration Command 30-8
Summary Table of CL Commands for Managing AS/400 Advanced 36
Machines . . . . 30-13 Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-1 Configuration That Exists Immediately after Installation . . . 31-2 Defining a Communications Line or a LAN . . . 31-4 Defining a Diskette Device . . . 31-8 Defining a Tape or CD-ROM Device . . . 31-10 Defining Printers and Display Stations Using Device Mapping . . . 31-12 Defining Printers and Display Stations Using Controller Mapping . . . 31-17 Changing a Workstation Controller from Controller Mapping to Device
Mapping . . . . 31-22 Defining Whether SSP or OS/400 Controls SSP Printer Output . . . 31-26 Defining Whether SSP or OS/400 Controls the Display Station . . . 31-36 Validating an AS/400 Advanced 36 Machine Configuration . . . 31-39 Chapter 32. Displaying Information About an AS/400 Advanced 36
Configuration and Machine . . . 32-1 Displaying a Configuration . . . 32-1 Displaying a Machine . . . 32-2
Other Useful Information
Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1 System/36 Procedures to AS/400 Commands Cross-Reference . . . A-1 System/36 Control Commands to AS/400 Commands Cross-Reference . . . A-27 System/36 OCL Statements to AS/400 Commands Cross-Reference . . . A-32 | Appendix B. Displaying and Setting the IPL Mode For a 9402 Model 436 B-1 Displaying the IPL Mode . . . B-1 Setting the IPL Mode . . . B-3 Appendix C. Performance Considerations . . . . C-1 Understanding Server Jobs . . . C-1 Understanding Prestart Jobs . . . C-2 Setting Attributes For the AS/400 Advanced 36 Server Job . . . C-3 Setting attributes for the AS/400 Advanced 36 SLIC Tasks . . . C-5 Setting Attributes for the AS/400 Advanced 36 Prestart Jobs . . . C-6 Appendix D. Using Electronic Customer Support . . . D-1 Reporting a Problem . . . D-1 Reviewing Status of an Open Problem . . . D-3 Ordering PTFs . . . . D-3 Appendix E. Preparing SSP for Dedicated State . . . E-1 Bibliography . . . . H-1 Index . . . . X-1
Notices
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user.
IBM may have patents or pending patent applications covering subject matter in this document. The fur-nishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY 10594, U.S.A.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact the software interop-erability coordinator. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
Address your questions to: IBM Corporation
Software Interoperability Coordinator 3605 Highway 52 N
Rochester, MN 55901-7829 USA
This publication could contain technical inaccuracies or typographical errors.
This publication may refer to products that are announced but not currently available in your country. This publication may also refer to products that have not been announced in your country. IBM makes no commitment to make available any unannounced products referred to herein. The final decision to announce any product is based on IBM's business and technical judgment.
This publication contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
This publication contains small programs that are furnished by IBM as simple examples to provide an illustration. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. All programs contained herein are provided to you "AS IS". THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED.
Trademarks
Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Cor-poration.
PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
C-bus is a trademark of Corollary, Inc.
Other company, product, and service names, which may be denoted by a double asterisk (**), may be trademarks or service marks of others.
Advanced Peer-to-Peer Networking Advanced Function Printing
AFP Apple Application Development Application System/400 APPN AS/400 C/400 CICS DisplayWrite FORTRAN/400 IBM IMS Information Assistant IPX PSF OfficeVision/400 Operating System/400 Operational Assistant OS/400 Q & A Question RPG/400 RM/COBOL-85 SystemView System/36 System/38 SUN TRN Ultimedia 400 486
About Operator Tasks – Multiple Operating Systems
(SC21-8384)
Who Should Use This Book
| This book is intended for use by a system operator who operates an AS/400 | system on which SSP and OS/400 operating systems are both installed. | For information about operating an AS/400 system that is running the System | Support Program (SSP) operating system, where the SSP operating system is the | only operating system installed see the Operating Your Computer–SSP Operating
System book, SC21-8297.
For information about operating an AS/400 system with only OS/400 installed, see the System Operation book, SC41-4203.
That part of the system that contains the SSP operating system and related data and programs is referred to as an AS/400 Advanced 36 machine.
Many of the tasks that were done on a System/36 work the same on an AS/400 Advanced 36 machine. The tasks that were previously done using OS/400 are unchanged. However, there are some things the OS/400 operator will need to know in order to do tasks with the AS/400 Advanced 36 machine. There are also additional OS/400 CL commands. As the system operator, you have many respon-sibilities.
This book provides information about day-to-day tasks, such as how to do the following:
Work with jobs or printer output.
Respond to messages sent to the system operator message queue (QSYSOPR), change message queues, and respond to error messages.
Use the support functions available on the AS/400 system.
Clean up your system periodically to improve performance and maintain good running condition.
Save and restore all of the important data that you keep on your system.
Work with the system unit control panel and OS/400 console.
Start and stop the AS/400 system.
Start and stop each AS/400 Advanced 36 machine
Pass through to SSP or OS/400
Handle OS/400 and SSP messages. | Install program temporary fixes (PTFs).
Use OS/400 commands to do tasks.
Print.
Change security levels with OS/400.
Use security with SSP.
Transfer to an AS/400 Advanced 36 machine
Run SSP procedures from an OS/400 display station.
Control SSP jobs.
Use System to System Communications.
Change your AS/400 Advanced 36 machine configuration.
Display and set the IPL Mode.
Use Electronic Customer Support The book is divided into several parts:
| Part 1: AS/400 System Operation
– Contains information on how to use the system control panel. – Contains a quick reference table of where to find operator tasks.
Part 2: OS/400 for the SSP Operator
– Contains information on tasks you can do to manage the OS/400 part of the system.
Part 3: SSP for the OS/400 Operator
– Contains information on tasks you can do to manage the AS/400 Advanced 36 machines that are on the system.
Part 4: AS/400 Advanced 36 Common Operator Tasks – Contains information on handling problems.
– Contains information on managing AS/400 Advanced 36 system operations. – Contains information on managing system-to-system communications using
an Internal Local Area Network (ILAN).
– Contains information on managing AS/400 Advanced 36 machines and their configurations.
Part 5: Other Useful Information
– Appendix A: System/36 and AS/400 Commands Cross-Reference – Appendix B: Control Language Commands
– Appendix C: Displaying and Setting the IPL Mode – Appendix D: Performance Considerations
– Appendix E: Using Electronic Customer Support
What You Should Do Before You Use this Book
To use this book effectively, you should have: Completed the installation instructions in the Getting SSP and OS/400 Installed and Running book, SC21-8377.
Learned how to interpret the display indicators and the control panel on the display station that is attached to your system.
Learned how to use the keyboard that is attached to your display station.
Where to Go for Other Information
For operating instructions for your display station, refer to the operator's guide for the display station that is attached to your system.
For information about OS/400 system operator tasks that are not included in this book, see the System Startup and Problem Handling book, SC41-4206. That book contains information about:
Loading Program Temporary Fixes (PTFs) for (OS/400)
Problem Handling (for OS/400)
You may need to refer to other IBM books for more specific information about a particular topic.
For information about Advanced 36 publications, see the Advanced 36 Information Directory book, SC21-8292.
For information about other AS/400 publications (except Advanced 36), see either of the following:
The Publications Reference book, SC41-4003, in the AS/400 Softcopy Library.
The AS/400 Information Directory, a unique, multimedia interface to a
searchable database containing descriptions of titles available from IBM or from selected other publishers. The AS/400 Information Directory is shipped with the OS/400 operating system at no charge.
For a list of related publications, see the Bibliography.
Note: AS/400 book numbers start with SC41. SSP book numbers start with SC21.
If you are using your AS/400 system in a System/36 environment, start the AS/400 system using an attended initial program load (IPL), and select the kind of environ-ment you want to use. When you have completed the IPL, see the following manuals for information about the System/36 environment:
System/36 Environment Programming, SC41-4730
AS/400 System Operation
| Chapter 1. AS/400 System Operations Tasks . . . 1-1 What You Need to Know about Your Control Panel . . . 1-1 Control Panel Details . . . 1-2 IPL Types and Modes . . . 1-5 | Uninterrupted Power System . . . 1-6 Quick Reference to Operator Tasks . . . 1-7 | Additional Information that Applies to the AS/400 System . . . 1-8Control Panel
|
Chapter 1. AS/400 System Operations Tasks
This chapter contains information on:
The system control panel
The uninterruptible power supply
A quick reference to OS/400 and SSP tasks
What You Need to Know about Your Control Panel
System operators and service representatives use the control panel to:
Do an initial program load (IPL)
Do problem analysis
Stop the system if the system cannot be stopped from a workstation. | Figure 1-1 shows the control panel for a 9402 Model 436 with the cover closed. | Other AS/400 models can differ in appearance.
RV3P218-0
D C
Figure 1-1. Control Panel with Cover Closed
When the control panel is closed, two lights are visible:
The processor activity light .C/ The system attention light .D/
These lights are defined on page 1-3. To use the control panel, you must open the cover. To open the cover, do as follows:
Control Panel
1. If you have a lock on your control panel, unlock the cover.
2. Find the place on your control panel cover on the side of the machine that is indented.
If you have difficulty locating the indentation, look at the diagram in Figure 1-1 on page 1-1.
3. Use your thumb to open the control panel.
| Figure 1-2 shows the control panel for a 9402 Model 436 without the cover. Other | AS/400 models can differ in appearance.
Function 01 Display Selected IPL 02 Select IPL 03 Start IPL 04 Lamp Test 11 System Reference Code
Enter Function/Data RTSP035-2 A B D G F E C
Figure 1-2. Control Panel Without a Cover
Control Panel Details
.A/ Power On light:
The light comes on and stays on when there is power to the system unit. The Power On light blinks when:
The system is being started up
The system is being manually turned off
Note: When the Power Down System (PWRDWNSYS) command or the options on the Power On and Off Tasks (POWER) menu are used, the Power On light does not blink.
.B/ Power pushbutton: Use the power pushbutton to start the system and stop the system. To start the system, press the pushbutton once. To stop or power off the system, press the pushbutton twice.
Control Panel
Power on is allowed in Manual or Normal mode. Power off is allowed in Manual mode only.
Note: In most cases, to stop the system, use the Power Down System (PWRDWNSYS) command on any command line of your OS/400 display station after stopping all AS/400 Advanced 36 machines. If you use the Power pushbutton to turn off the system, errors may occur with data files. For more information on stopping the
system, see “Stopping the AS/400 System” on page 3-1.
.C/ Processor Active light: The system unit has one Processor Active light. The light blinks when programs are running that use the processor.
.D/ System Attention light: This light comes on when the system requires oper-ator attention, such as correcting a severe system failure. For information about correcting system problems, see the System Startup and Problem Han-dling book, SC41-4206.
.E/ Function/Data display: The same display and pushbuttons are used for both function and data. When you press a Select pushbutton (.F/), the function numbers on the Function/Data display increase or decrease. For example, 01 becomes 02 and A M becomes B M.
When you press the Enter pushbutton (.G/), displayed data may disappear. Note: For example, when you press the Enter pushbutton, 02 B M
becomes 02.
Only the numbers that can be used in the present mode are displayed. The Function/Data display can display up to 8 digits. The selected function is not processed until the Enter pushbutton (.G/) is pressed.
System reference codes or other information from the processing unit or control panel are also shown in the Function/Data display.
Note: If the system attention light comes on, it indicates the system requires operator attention. In this case, a code of 11-3 becomes the System Reference Code (SRC) when you push the Enter pushbutton. An example of an SRC is A6ððð9ð2.
.F/ Select pushbuttons: There are two select pushbuttons. These buttons are used to increase or decrease the number shown in the Function/Data display. The select pushbutton on the left increases the values in the Function/Data display. The select pushbutton on the right decreases the values in the Function/Data display.
Either pushbutton can be used to change the data shown in the Function/Data display when you are selecting an initial program load (IPL) type and mode. The IPL type (A, B, C or D) and the IPL mode (M or N) can be selected by using Function 02. To select IPL type, do the following:
1. Press one of the Select pushbuttons until 02 is visible in the function/data display area.
2. Press the Enter pushbutton (.G/).
3. Press one of the Select pushbuttons until the IPL type and mode you want is visible in the function/data display area.
Control Panel
5. Press one of the select pushbuttons until ð1 is visible in the function/data display area.
6. Press the Enter pushbutton.
ð1 and the IPL type and mode are displayed in the function/data display. Attention: Do not use Function code ð8 unless it is an emergency. This is the emergency power off code. Use of Function code 08 may cause unpredictable results.
.G/ Enter pushbutton: The Enter pushbutton is used to send function informa-tion shown in the Funcinforma-tion/Data display to the processing unit or to save the type of IPL type and mode you selected.
Note: You can also display the IPL type and mode. To do so, follow steps 5 and 6 on page 1-4 described under the .F/ Select pushbuttons topic.
IPL Types and Modes
IPL Types and Modes
The IPL types and modes are:
A M Performs a Manual IPL from the A side of the disk. This mode may be used when applying or removing Licensed Internal Code (LIC) PTFs. It can also be used to power off the system.
Use this type and mode only under the direction of your support repre-sentative.
A N Performs a Normal IPL from the A side of the disk.
This mode should only be used when B N does not work and you are told to do so by your support representative.
B M Performs a Manual IPL from the B side of the disk. This mode should only be used when an attended IPL must be performed or you need to power off the system. This type of IPL is used when you need to change the system date and time permanently.
B N Performs a normal IPL from the B side of the disk. This is the type and mode used most of the time. It is also the mode the system must be in if you want to do an unattended IPL.
C M Allows service representatives to perform a special IPL. This mode is for use only by service representatives. Never IPL in this type and mode.
C N Allows service representatives to perform a special IPL. This mode is for use only by service representatives. Never IPL in this type and mode.
D M Performs a manual IPL from either CD-ROM or tape. This mode is used to install Licensed Internal Code and the OS/400 operating system in attended mode. This is the most often used IPL type and mode for installation.
D N Performs a normal IPL from either CD-ROM or tape. This mode is used to install Licensed Internal Code and the OS/400 operating system in unattended mode.
Manual When the mode is set to Manual (M), the system allows you to do all manual IPLs, such as an operator-attended IPL from disk, CD-ROM or tape. Manual mode also allows you to do some manual control func-tions, such as selecting an IPL type and mode or displaying the kind of IPL that the system is set to run. However, in manual mode, you cannot do a remote IPL, an IPL by date and time, or an IPL after a power failure.
Note: You should set the mode to Manual only when it is necessary. This ensures that no one accidentally presses the Power push-button and causes the system to stop.
Normal The Normal mode allows you to turn the power on and then automat-ically start the system in any of the following ways:
IPL remotely
IPL by date and time
Uninterrupted Power System
Note: Your system should be in Normal mode most of the time. The table in Figure 1-3 on page 1-6 summarizes what operations you can do in the Manual (M) or Normal (N) IPL modes:
Note: You can display the kind of IPL the system is set to do when the system is in any mode.
If you want to stop the system when the mode is set to Normal, use the Power Down System (PWRDWNSYS) command at any display station after you stop the AS/400 Advanced 36 machines. You must have QSYSOPR authority to use the Power Down System (PWRDWNSYS) command.
Figure 1-3. Operation Summary for Manual and Normal Modes
Operation
Manual Mode
Normal Mode
Turn on system (Power pushbutton)
Allowed Allowed
Power off (Power push-button)
Allowed Not allowed
Display Selected IPL Allowed Allowed
Select IPL Allowed Allowed
Start IPL Allowed Not allowed
Display system reference code
Allowed Allowed
Remote IPL Not allowed Program control allowed Timed IPL Not allowed Program control allowed Restart IPL (after power
failure)
Not allowed Program control allowed
Power Down System command
Program control allowed Program control allowed
|
Uninterrupted Power System
| The AS/400 system supports an external uninterruptible power system (UPS). You can install UPS to protect your AS/400 system from temporary power loss. Your AS/400 system unit and the OS/400 console should be connected to the UPS. If the UPS is installed, it automatically activates when there is a utility power loss. The UPS provides full operating power to all system components for a short time.
Quick Reference
Quick Reference to Operator Tasks
This table provides information on where to find out how to do OS/400 and SSP operator tasks.
Figure 1-4 (Page 1 of 2). Quick Reference to OS/400 and SSP Operator Tasks
Operator Task OS/400 Operating System SSP Operating System
Starting the System Chapter 2, “Starting the System Unit and OS/400 Operating System”
Chapter 15, “Starting an AS/400 Advanced 36 Machine”
Stopping the System Chapter 3, “Stopping the System Unit”
Chapter 16, “Stopping an AS/400 Advanced 36 Machine”
Understanding Consoles and Sub-consoles
Chapter 4, “The OS/400 System Console”
Chapter 17, “Operating the SSP Console and SSP Subconsoles” Handling Messages Chapter 5, “Handling OS/400
Messages”
Chapter 18, “Handling SSP Messages”
Using Commands to Do Tasks Chapter 6, “Using OS/400 CL Commands to Do Tasks”
Chapter 19, “Using SSP Com-mands and Procedures to Do Tasks”
Printing Chapter 7, “Printing with OS/400” Chapter 20, “Printing with SSP” Working with Subsystems Chapter 8, “Working with OS/400
Subsystems”
Chapter 21, “Working with SSP Subsystems”
Understanding Security Chapter 9, “OS/400 System Security”
Chapter 22, “SSP Security”
Controlling Jobs Chapter 10, “Controlling OS/400 Jobs”
Chapter 23, “Controlling SSP Jobs”
Working with Devices and Commu-nications
Chapter 11, “Working with OS/400 Devices and Communications”
Chapter 24, “Working with SSP Devices and Communications” Saving and Restoring Chapter 12, “Saving and Restoring
OS/400 and OS/400 Objects”
Chapter 25, “Saving and Restoring the AS/400 Advanced 36 Machine Information”
Working with Program Temporary Fixes (PTFs)
Chapter 13, “Working with Licensed Internal Code and OS/400 Program Temporary Fixes”
Chapter 26, “Working with SSP Program Temporary Fixes”
Transferring to an AS/400 Advanced 36 machine
Chapter 14, “Transferring to an AS/400 Advanced 36 Machine”
Not applicable
Establishing communication with a remote workstation
Not applicable Chapter 27, “Establishing a Com-munications Link for Remote Workstations”
Solving Problems Chapter 28, “Problem Handling” Chapter 28, “Problem Handling” Establishing Internal System
Com-munications Chapter 29, “System-to-System Communications - ILAN Communications” Chapter 29, “System-to-System Communications - ILAN Communications” Managing Your AS/400 Advanced
36 Machines and Their Configura-tions. (For example, creating, starting, or deleting an AS/400 Advanced 36 machine)
Chapter 30, “Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines”
Chapter 30, “Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines”
Quick Reference
Figure 1-4 (Page 2 of 2). Quick Reference to OS/400 and SSP Operator Tasks
Operator Task OS/400 Operating System SSP Operating System
Changing an AS/400 Advanced 36 Configuration
Chapter 31, “Changing Your AS/400 Advanced 36 Machine Configuration”
Chapter 31, “Changing Your AS/400 Advanced 36 Machine Configuration”
Displaying Information About an AS/400 Advanced 36 Configuration and Machine
Chapter 32, “Displaying Informa-tion About an AS/400 Advanced 36 Configuration and Machine”
Chapter 32, “Displaying Informa-tion About an AS/400 Advanced 36 Configuration and Machine” Using Media Chapter 4 of the System Startup
and Problem Handling book, SC41-4206.
Chapter 7 of the Operating Your Computer–SSP Operating System book, SC21-8297.
|
Additional Information that Applies to the AS/400 System
Other Useful Information is included in the following:. Appendix A, “System/36 and AS/400 Commands Cross-Reference”
Appendix B, “Displaying and Setting the IPL Mode For a 9402 Model 436”
Appendix C, “Performance Considerations”
Appendix D, “Using Electronic Customer Support”
OS/400 for the SSP Operator
Chapter 2. Starting the System Unit and OS/400 Operating System . . . 2-1 Using the OS/400 Sign On Display during an IPL . . . 2-3 Chapter 3. Stopping the System Unit . . . 3-1 Stopping the AS/400 System . . . 3-1 Preparing to Stop the System . . . 3-1 Using the POWER Menu to Stop the System . . . 3-2 Using the Power Down System Command to Stop the System . . . 3-3 Using the Power Pushbutton to Stop the System . . . 3-4 Chapter 4. The OS/400 System Console . . . 4-1 Device Name of the System Console . . . 4-1 How the System Console Display is Different from Other Displays . . . 4-1 Chapter 5. Handling OS/400 Messages . . . 5-1 Most Common Types of OS/400 Messages . . . 5-1 Displaying OS/400 Messages . . . 5-1 Finding Additional Information about Your Messages . . . 5-3 Identifying Messages from the System . . . 5-5 Message Severity Codes . . . 5-5 How to Handle Break Messages . . . 5-7 Displaying OS/400 System Operator Messages . . . 5-7 Your User Profile Message Queue . . . 5-8 Responding to OS/400 Messages . . . 5-9 Working with OS/400 Message Queues . . . 5-10 Changing a Message Queue . . . 5-12 Handling OS/400 Error Messages . . . 5-14 Handling Important System Messages in the QSYSMSG Message Queue 5-14 Creating the QSYSMSG Message Queue . . . 5-14 Error Messages on Menus and Displays . . . 5-15 Using the Work with Problems Command . . . 5-15 Understanding OS/400 Keyboard Error Messages . . . 5-15 Sending OS/400 Messages . . . 5-16 Using the Send Message Command to Send a Message . . . 5-16 Using the Send Break Message Command to Send a Message . . . 5-17 Chapter 6. Using OS/400 CL Commands to Do Tasks . . . 6-1 CL Commands — Overview . . . 6-1 Using Operational Assistant Displays . . . 6-2 Using Assistance Levels and User Profiles . . . 6-3 Changing Assistance Level Displays . . . 6-4 Changing Assistance Levels Temporarily — Examples . . . 6-5 Changing Assistance Levels in Your User Profile . . . 6-7 Using CL Commands with the Operational Assistant Displays . . . 6-8 Doing Specific Tasks (GO) . . . 6-9 Menus for System Operations . . . 6-9 Chapter 7. Printing with OS/400 . . . 7-1 Definitions . . . . 7-1 Spooled Files . . . . 7-1Printer Writers . . . . 7-1 Output Queues . . . . 7-1 Printers . . . . 7-2 Finding OS/400 Printer Output . . . 7-3 Getting to the Work with Printer Output Display Using Operational Assistant 7-3 Getting to the Work with Printer Output Display Using a CL Command . . . 7-3 Using the Work with Printer Output Display to Find Output . . . 7-4 Understanding Printing Problems . . . 7-5 Printing Priorities . . . . 7-6 Managing Printed Output . . . 7-7 Holding Printer Output . . . 7-7 Releasing Printer Output . . . 7-7 Deleting Printer Output . . . 7-7 Changing Printer Output . . . 7-7 What to Do if the Printer Output Is Not Already Printing . . . 7-8 Assigning Printer Output to a Printer . . . 7-9 Working with Printers . . . 7-10 Starting a Printer . . . 7-10 Stopping a Printer . . . 7-11 Restarting a Printer . . . 7-11 Answering Printer Messages . . . 7-11 Changing Forms on a Printer . . . 7-13 Working with Spooled Files . . . 7-13 Working with All Output Queues . . . 7-14 Comparing System/36 Print Commands to OS/400 Print Commands . . . 7-15 Chapter 8. Working with OS/400 Subsystems . . . 8-1 Definitions . . . . 8-1 OS/400 Subsystems . . . . 8-1 SSP Subsystems . . . . 8-1 Working with a Subsystem . . . 8-2 Working with Subsystem Descriptions . . . 8-2 Chapter 9. OS/400 System Security . . . 9-1 Levels of Security . . . 9-1 Changing the Security Level . . . 9-1 Changing Passwords . . . . 9-2 Chapter 10. Controlling OS/400 Jobs . . . 10-1 Submitting Batch Jobs . . . 10-1 Submitting a Batch Job to Run Immediately . . . 10-2 Scheduling a Batch Job to Run Later . . . 10-2 Changing a Job Schedule to Run at a Different Date or Time . . . 10-3 Scheduling a Job Using Job Schedule Entries . . . 10-3 Adding a Job Schedule Entry . . . 10-4 Saving a Job Schedule Entry . . . 10-4 Removing a Job Schedule Entry . . . 10-4 Changing a Job Schedule Entry . . . 10-5 Holding and Releasing a Job Schedule Entry . . . 10-5 Scheduling a Batch Job to Start an AS/400 Advanced 36 Machine . . . 10-5 Working with Batch Jobs . . . 10-5 Displaying Batch Jobs of Other Users . . . 10-6 Displaying All Batch Jobs . . . 10-6 Displaying Batch Jobs by Status . . . 10-7
Holding a Batch Job . . . 10-8 Releasing a Batch Job . . . 10-9 Ending a Batch Job . . . 10-9 Working with Job Queues . . . 10-9 Looking at Job Queues . . . 10-10 Holding a Job Queue . . . 10-11 Releasing a Job Queue . . . 10-11 Working with Unassigned Job Queues . . . 10-11 Working with Signed-On Users . . . 10-12 Displaying Signed-On Users . . . 10-12 Creating a Customized Work with User Jobs Command . . . 10-12 Signing Users Off the System . . . 10-13 Finding Signed-On Users and Sorting the User List . . . 10-14 Finding Additional Information about Signed-On Users . . . 10-14 Sending Messages to Signed-On Users . . . 10-14 Displaying Detailed Job Information . . . 10-14 Displaying Job Status Attributes . . . 10-15 Displaying Job Definition Attributes . . . 10-15 Displaying Job Run Attributes . . . 10-15 Displaying the Call Stack . . . 10-15 Displaying Open Files . . . 10-15 Changing How a Job Is Run . . . 10-16 Changing a Job’s Priority on a Job Queue . . . 10-16 Moving a Job to a Different Job Queue . . . 10-17 Changing How an Active Job Is Run . . . 10-17 Changing a Job’s Print Priority . . . 10-18 Assigning a Job to a Different Output Queue . . . 10-18 Working with Job Logs . . . 10-19 Displaying a Job Log . . . 10-19 Printing a Job Log . . . 10-19 Changing the Logging Level for a Job . . . 10-20 Filtering Messages from the Job Log . . . 10-20 Sending Job Log Output Files to a Separate Output Queue . . . 10-21 Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1 Displaying and Changing Device Status . . . 11-1 Device Status Restrictions . . . 11-2 Renaming a Device . . . 11-2 Considerations for Renaming Devices . . . 11-2 Displaying and Changing a Device Description . . . 11-3 Printing Local Device Addresses . . . 11-3 Activating Communications Lines and Controllers . . . 11-4 Configuring Remote Communications . . . 11-5 Using a Switched Communications Line . . . 11-6 Using Manual Dial . . . 11-6 Using Manual Answer . . . 11-7 Using Manual Answer for Countries Other Than the United States . . . . 11-7 Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . 12-1 Saving the Entire System . . . 12-1 Restoring the Entire System . . . 12-2 Saving the OS/400 Operating System . . . 12-2 Restoring the OS/400 Operating System . . . 12-3 Saving AS/400 Storage . . . 12-3
Restoring AS/400 Storage . . . 12-3 Saving Individual OS/400 Objects . . . 12-3 Saving Objects in Directories . . . 12-4 Saving Calendar . . . . 12-4 Saving Configuration Objects . . . 12-4 Saving Changed Objects . . . 12-4 Saving Documents, Folders, and Mail . . . 12-4 Saving Libraries . . . . 12-4 Saving Licensed Programs . . . 12-5 Saving Specific Objects . . . 12-5 Saving Security Data . . . 12-5 Restoring Individual OS/400 Objects . . . 12-5 Restoring Objects in Directories . . . 12-5 Restoring Calendar . . . . 12-5 Restoring Configuration Data . . . 12-6 Restoring Changed Objects . . . 12-6 Restoring Documents, Folders, and Mail . . . 12-6 Restoring Libraries . . . . 12-6 Restoring Licensed Programs . . . 12-6 Restoring Specific Objects . . . 12-7 Restoring User Profiles . . . 12-7 Restoring Object Authority . . . 12-7 Chapter 13. Working with Licensed Internal Code and OS/400 Program
Temporary Fixes . . . . 13-1 AS/400 Program Maintenance Strategy . . . 13-1 Preventive Service (Cumulative PTF Packages) . . . 13-1 Corrective Service . . . . 13-1 Ordering LIC and OS/400 PTFs and PTF Information . . . 13-2 Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . 14-1 Important Information about Transferring . . . 14-1 Restrictions on Transfers using the TFRM36 and STRM36PRC Commands 14-1 Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . 14-3 Transferring to an AS/400 Advanced 36 Machine . . . 14-3 Using the TFRM36 Command — Examples . . . 14-4 | How to Allow for Automatic Sign-On . . . 14-5 | Selecting the Correct User Profile . . . 14-5
Transferring to an AS/400 Advanced 36 Machine Using the STRM36PRC
Command . . . . 14-6 Using the STRM36PRC Command . . . 14-6 Running an SSP Procedure from OS/400 — Examples . . . 14-7 Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7 Running the STRPASTHR command: . . . 14-8
Transferring to an AS/400 Advanced 36 Machine Using the
Starting System Unit
Chapter 2. Starting the System Unit and OS/400 Operating
System
| This chapter contains directions on how to start a system unit for a 9402 model 436 | that contains both the SSP and OS/400 operating systems. For directions on how | to start other models, see the System Startup and Problem Handling book,
| SC41-4206.
| Note: You can run OS/400 simultaneously with as many as three AS/400
| Advanced 36 machines.
| When you start the system unit, you are starting OS/400 and any AS/400 Advanced 36 machines that are set up to automatically start. For information on starting AS/400 Advanced 36 machines, see Chapter 15, “Starting an AS/400 Advanced 36 Machine.”
| Note: To perform the tasks in this chapter, you must have OS/400 installed on | your system. If you have SSP installed on your system and OS/400 is not | installed, see the Getting SSP and OS/400 Installed and Running book,
| SC21-8377.
To start the system, turn the system power on by pressing the white power push-button once.
This does an initial program load (IPL). During an IPL, system programs are loaded from the system auxiliary storage and the system hardware is checked. When the IPL is finished, the AS/400 Sign On display is shown on all workstations available to OS/400. For information on assigning workstations to OS/400 or SSP, see “Defining Whether SSP or OS/400 Controls the Display Station” on
page 31-36.
The following situations typically require an IPL:
Starting normal system operations
Starting a remote system
Changing configuration options
Recovering 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 to the system is turned on.
An attended IPL shows various displays on the display station used for the OS/400 console and allows you to change configuration options or change certain system values to affect how the system runs.
The table in Figure 2-1 on page 2-1 is a summary of how to do IPLs and what the IPL mode should be set to on the system control panel.
Starting System Unit
Figure 2-1. Performing IPLs
System State Unattended IPL Attended IPL
Running 1. Set IPL mode to Normal. 2. Stop any AS/400 Advanced 36
machines that are running. 3. Set QIPLTYPE system value to 0
(Unattended).
4. Type PWRDWNSYS *IMMED RESTART(*YES) on any command line and press Enter.
1. Set IPL mode to Manual.
2. Stop any AS/400 Advanced 36 machines that are running.
3. Type PWRDWNSYS *IMMED
RESTART(*YES) on any command line and press Enter.
4. Follow the display on the console to complete the IPL.
5. Set the mode to Normal. Not Running 1. Set IPL mode to Normal.
2. Power on all devices.
3. Press the Power Pushbutton Once.
1. Set IPL mode to Manual. 2. Power on all devices.
3. Press the Power Pushbutton Once. 4. Follow the directions on the OS/400
console to complete the IPL. 5. Set the mode to Normal.
Note: Always set the mode to Normal after the IPL is finished.
For more information on the following IPL options, see the System Startup and Problem Handling book, SC41-4206.
Setting Up Your Automatic Power On and Off Schedules
Starting a Remote System
Changing Your System during IPL
Starting System Unit
Using the OS/400 Sign On Display during an IPL
à
@
ð
Sign On System . . . : SYSTEMð1 Subsystem . . . . : QBASE Display . . . : DSPð1 User . . . __________ Password . . . . Program/procedure . . . __________ Menu . . . __________ Current library . . . __________Figure 2-2. Sign On Display To sign on the OS/400 system:
1. Type your user ID, your password (if security is active), and fill in any of the optional entry fields you want to use. Use the Tab key to move the cursor from field to field on the display.
Notes:
a. The Password field is shown only if password security is active on the system and the security level is higher than 10.
b. In the top right corner of the Sign On display the following are shown.
The name of the system you are using
The subsystem the system is using
For more information on OS/400 subsystems, see Chapter 8, “Working with OS/400 Subsystems.”
The workstation identifier (ID) 2. Press Enter.
If this is an attended IPL, the IPL Options display is shown. The IPL options display is used to clear job logs or spool files and to set the system time and date fields. For more information about the IPL Options display, see the System Startup and Problem Handling book, SC41-4206.
If this is an unattended IPL, (depending on what options you select on this display or what is defined in your user profile), one or more of the following occurs:
The AS/400 Main Menu is shown.
Another menu is shown.
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 shown, the program or procedure is run first and then the menu is shown.
Now that your system is up and running be aware that:
Starting System Unit
The system cleanup functions are automatically started with default values. For more information about customizing the cleanup function, see chapter 8 of the System Operation book, SC41-4203.
The Attention key program defaults to display the Operational Assistant (ASSIST) menu.
For more information on signon displays, see the System Startup and Problem Handling book, SC41-4206.
Stopping the AS/400 System
Chapter 3. Stopping the System Unit
This chapter contains directions on how to stop the system unit.
When you stop the system unit, you are stopping OS/400 and any AS/400 Advanced 36 machines that are not already stopped.
Attention: If you power off the system unit without stopping the AS/400 Advanced 36 machines,
Jobs running under SSP will end abnormally.
SSP files will not be closed and may be in an unknown state.
For information on stopping AS/400 Advanced 36 machines, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine.”
Stopping the AS/400 System
You can stop the system in several different ways:
POWER menu
Power Down System (PWRDWNSYS) command
Power Pushbutton
Preparing to Stop the System
1. Make sure all batch jobs are finished and all users are signed off.
2. Check to make sure no AS/400 Advanced 36 machines are currently active. a. Type
WRKM36 M36(\ALL/\ALL) b. Press Enter.
The Work with M36 Machines display appears.
c. From the SSP console, stop all AS/400 Advanced 36 machines that have a status of Started and return here.
For directions, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine.”
d. From the OS/400 console, stop all AS/400 Advanced 36 machines that have a status of Starting or Job Queue. To do so, use the End AS/400 Advanced 36 Machine (ENDM36) command. For information on using the WRKM36 command to stop AS/400 Advanced 36 machines which could not be stopped in the usual way, see “Ending an AS/400 Advanced 36 Machine” on page 30-7.
e. From the OS/400 console, press F3 (End) to end the WRKM36 command. 3. Unload all media in the devices before the system is powered down to ensure
Stopping the AS/400 System
Using the POWER Menu to Stop the System
To power off the system immediately:1. Follow the directions in “Preparing to Stop the System” on page 3-1. 2. Type
GO POWER
on any OS/400 command line. 3. Press Enter.
The Power On and Off Tasks (POWER) menu appears. From this menu you can:
Display the schedule
Change the schedule
Power off the system immediately
Power off the system and then power on
Examples of using options 3 and 4 are included in this chapter.
4. To keep the power off until the next time the system is scheduled to power on: a. In the option field, type
3
to select Power off the system immediately. b. Press Enter.
The Confirm Power Off of System display appears as shown in Figure 3-1.
à
@
ð
Confirm Power Off of System
System: SYSTEMð1
Next scheduled power on:
Date . . . : ð5/19/95
Time . . . : ð5:4ð:ðð
To confirm immediate power off, press F16. To cancel, press F12.
Figure 3-1. Confirm Power Off of System Display for Immediate Power Down c. Press F16.
When you press F16 (Confirm), an immediate power down occurs that causes the subsystems to end all active jobs.
Note: 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, then turn itself off in a few minutes.
5. To power off the system and then restart the system immediately after it powers off:
a. In the option field, type 4
Stopping the AS/400 System
b. Press Enter.
The Confirm Power Off of System display appears as shown in Figure 3-2.
à
@
ð
Confirm Power Off of System
To confirm immediate power off and then immediate power on, press F16. To cancel, press F12.
Figure 3-2. Confirm Power Off of System Display for Immediate Power On c. Press F16.
When you press F16 (Confirm), the system stops running and then starts again automatically.
Note: 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, then turn itself off in a few minutes.
Important Note
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 value (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 value, enter the following command on any command line and then press Enter.
CHGPWRSCDE DAY(\TODAY) PWRONTIME(\SAME) PWROFFTIME(\SAME)
Using the Power Down System Command to Stop the System
The Power Down System (PWRDWNSYS) command prepares the system for ending and then starts the power-down sequence. All active subsystems are noti-fied that the system is being powered down. No new jobs or routing steps can be started by any subsystem. For example, jobs that are on a job queue as a result of a Transfer Job (TFRJOB) command are not allowed to complete. During the sub-sequent initial program load (IPL), they are removed from the job queue and their job logs are produced.
Note: All media in the devices are unloaded before the system is powered down to ensure the integrity of data on the media.
The Power Down System (PWRDWNSYS) command can be used on any OS/400 command line. To use the PWRDWNSYS command:
1. Follow the directions in “Preparing to Stop the System” on page 3-1. 2. On an OS/400 command line, type
PWRDWNSYS 3. Press F4.
Stopping the AS/400 System
4. Specify the options you want and then press Enter.
Note: Positioning the cursor on one of the input fields and pressing F4 dis-plays the values that can be specified for that parameter. Pressing the Help key or F1 provides additional information about that parameter.
Using the Power Pushbutton to Stop the System
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 or the PWRDWNSYS command to stop the system, you can turn the power off using the Power pushbutton when the mode is set to Manual. Pow-ering off this way causes the next IPL to be abnormal.
There are two ways to power off the system using the Power Pushbutton.
Normal sequence
Emergency sequence 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 will take longer to com-plete.
Make sure that no media is left in the media devices and that the mode is set to Manual.
Note: 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, then turn itself off in a few minutes.
Normal Sequence
1. Press the Power pushbutton. The Function/Data display blinks with O?. (the international power off symbol).
Note: To cancel the power off operation, press any other pushbutton on the control panel.
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.
If the system does not turn the power off within 30 minutes or the System Attention light does not come on, see the System Startup and Problem Handling book, SC41-4206, for further directions.
Emergency Sequence
1. Set 08 (fast power off) in the Function/Data display. 2. Press the Enter Pushbutton.
A System Reference Code (SRC) of A1ðð 8ðð8 is shown in the Function/Data display.
3. Press the Power Pushbutton. The Function/Data display blinks with O? (The international power off symbol).
OS/400 System Console
Chapter 4. The OS/400 System Console
The OS/400 system console is the workstation that allows you to control and observe system operations. It is the workstation attached to the first input/output processor capable of supporting workstations.
The system controls which display station is the OS/400 console. The system moves the OS/400 console only if the display station at the first workstation I/O processor, port 0, address 0 no longer works.
For more information in determining which workstation is the OS/400 console, see the System Startup and Problem Handling book, SC41-4206.
Device Name of the System Console
To find out the device-name for the OS/400 console, type: DSPSYSVAL QCONSOLE
QCONSOLE is the value that specifies the name of the display device that is the console. You cannot change this system value.
How the System Console Display is Different from Other Displays
The console display is like any other display with the exception of system break messages and commands. Unless the CHGMSGQ QSYSOPR *BREAK command is issued, break messages are displayed only on the console. However, you can view these system messages using the DSPMSG QSYSOPR command from an OS/400 command line on any display station. For more information on messages, see Chapter 5, “Handling OS/400 Messages.”Most commands can be entered from any OS/400 display, the following commands must be run from the OS/400 system console:
DST commands
ENDSBS command if the subsystem you are ending is the controlling sub-system.
Displaying Messages
Chapter 5. Handling OS/400 Messages
Note: The displays shown in this chapter are those you would see if you were running at a basic assistance level. You would see different displays at other assistance levels.
A message is any communication sent from one point to another point on the AS/400 system. The communication may be between you and the system or between you and another person using the system.
The system communicates with you by sending Informational and Inquiry mes-sages.
Most Common Types of OS/400 Messages
Informational messages do not require a reply. These messages give you status on what the system is doing, errors that you make, and responses that you make to messages. Informational messages appear directly on the workstation display in the message line. The message line is the bottom line of the display.
Inquiry messages give you information about the system, but request a reply. These messages are sent to either the system operator message queue (QSYSOPR), a user message queue, or the workstation message queue.
Displaying OS/400 Messages
A message sent to your message queue is not usually shown automatically. A message interrupts you if:
Your message queue is set to interrupt you (break mode).
A message is sent with the Send Break Message (SNDBRKMSG) command. If you are interrupted, the Display Messages display is shown automatically as in Figure 5-1 on page 5-2.
Note: If you are interrupted, the Display Messages display is always shown. It does not change based on the assistance level you are running with.
Displaying Messages
à
@
ð
Display Messages
System: SYSTEMð1
Queue . . . : SMITHS1 Program . . . . : \DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : ðð Delivery . . . : \NOTIFY
Type reply (if required), press Enter.
From . . . : QSYSOPR ð1/1ð/91 13:31:33
This system will go down in 1ð mins
Bottom
F3=Exit F11=Remove a message F12=Cancel
F13=Remove all F16=Remove all except unanswered F24=More keys
á
ñ
Figure 5-1. Display Messages display
If your messages do not interrupt you whenever they are sent, you can see them by:
Using the Display Messages (DSPMSG) command.
Using the Work with Messages (WRKMSG) command.
Selecting option 3 (Work with messages) on the Operational Assistant (ASSIST) menu.
Displaying Messages
à
@
ð
Work with Messages
System: SYSTEMð1
Messages for: SMITH
Type options below, then press Enter.
4=Remove 5=Display details and reply
Opt Message
Messages needing a reply
_ Controller SYSTEMð1 contact not successful. Probable remote station
problem (C R)
Messages not needing a reply
_ System is scheduled to be powered off at 22:3ð:ð1 on ð5/17/92.
From . . : QPGMR ð5/17/92 22:15:ðð
_ System is scheduled to be powered off at 22:3ð:ð1 on ð5/16/92.
From . . : QPGMR ð5/16/92 22:15:ðð
_ System is scheduled to be powered off at 22:45:ð1 on ð5/15/92.
From . . : QPGMR ð5/15/92 22:3ð:ðð
From . . : QPGMR ð5/14/92 22:3ð:ðð
Bottom
F1=Help F3=Exit F5=Refresh F6=Display system operator messages
F16=Remove messages not needing a reply F17=Top F24=More keys
á
ñ
Figure 5-2. Work with Messages display
Note: By displaying all of your message queues that are in break mode or notify mode, you turn the message waiting light off.
To print the messages in a message queue if your assistance level is *BASIC, use the Work with Messages (WRKMSG) command as follows:
WRKMSG MSGQ(msgqname) OUTPUT(\PRINT)
where msgqname is the name of the message queue that contains the messages you want to print.
You can also print messages contained in a message file with the Display Message Description (DSPMSGD) command and F4 (Prompt). Specify a range of message identifiers and *PRINT for the Output (OUTPUT) parameter.
Finding Additional Information about Your Messages
To find out more information about messages on the Work with Messages display, use option 5 (Display details and reply). When you use option 5 for a message that does not need a reply, you receive the additional information about that message. If the message requires a reply, you can type your reply in the field provided at the bottom of the Additional Message Information display.
For example, Figure 5-3 on page 5-4 shows additional information about the first inquiry message in Figure 5-2:
Displaying Messages
à
@
ð
Additional Message Information
Message ID . . . : CPA57EF
Date sent . . . : 11/18/91 Time sent . . . : 15:43:ð2
Message . . . . : Controller SYSTEMð1 contact not successful. Probable remote
station problem. (C R)
Cause . . . : The system was trying to exchange identifiers with the
station when an error occurred. The probable causes are:
-- The controller description on the remote system is not varied on. -- A configuration problem.
-- A remote hardware problem.
-- A local hardware problem or network problem if on an Ethernet network. -- A timing or performance problem.
Recovery . . . : Do the following:
-- Contact the remote operator to verify the remote system is not
More... Type reply below, then press Enter.
Reply . . . . _______________________________________________________
F1=Help F3=Exit F6=Print F9=Display message details F12=Cancel
F21=Select assistance level
á
ñ
Figure 5-3. Additional Message Information Display – Basic Assistance Level
Press the Page Down key to see the rest of the information about the message. When you have read the information, type a reply in the Reply field at the bottom of the display and press Enter.
To see more details about the message, press F9 (Display message details). Figure 5-4 shows the Display Message Details display.
à
@
ð
Display Message Details
Message ID . . . : CPA57EF Severity . . . : 99
Date sent . . . : 11/18/91 Time sent . . . : 15:43:ð2
Message type . . . : Inquiry
CCSID . . . : 65535
From job . . . : QSYSARB
User . . . : QSYS
Number . . . : ðð93ð2
From program . . . : QSWCDCR
To message queue . . . : QSYSOPR
Library . . . : QSYS
Bottom Press Enter to continue.
F1=Help F3=Exit F12=Cancel
á
ñ
Displaying Messages
To print a single message, use F6 (Print) on the Additional Message Information display. This prints all the information about the message shown on the display.
Identifying Messages from the System
On some message displays, the message is accompanied by a letter and number code as shown in Figure 5-5.
CPF 0083
↑
↑
.A/ .B/
Figure 5-5. Example of a Message ID
This is the message identifier (ID) that is used to distinguish a message from others in the message file. The first three letters .A/ indicate the message category. The following list shows some typical message categories:
CPA through CPZ Messages from the operating system CBE through CBX COBOL messages
CSC COBOL language syntax checker messages LBE through LSC COBOL messages
MCH Licensed Internal Code messages
QRG RPG language messages
RPG through RXT RPG language messages SBX through SSC COBOL messages
SQL Structured Query Language (SQL) messages
The remaining four digits .B/ indicate the sequence number of the message. The example message ID shown indicates this is a message from the operating system, number 0083. A message ID is shown when you press the Help key for an error message and additional message information is shown.
Message Severity Codes
Figure 5-6 shows the different severity codes of the messages and the types they are associated with.
Figure 5-6 (Page 1 of 2). Message Severity Codes
Message Type Severity Code
Informational messages. For informational purposes only; no reply
is needed. The message can indicate that a function is in progress or that a function has completed successfully.
00
Warning. A potential error condition exists. The program may have
taken a default, such as supplying missing data. The results of the operation are assumed to be successful.
Displaying Messages
Figure 5-6 (Page 2 of 2). Message Severity Codes
Message Type Severity Code
Error. An error has been found, but it is one for which automatic
recovery procedures probably were applied; processing has con-tinued. A default may have been taken to replace the wrong data. The results of the operation may not be correct. The function may not have completed; for example, some items in a list ran correctly, while other items did not.
20
Severe error. The error found is too severe for automatic recovery
procedures and no defaults are possible. If the error was in the source data, the entire data record was skipped. If the error occurred while a program was running, it leads to an abnormal end of program (severity 40). The results of the operation are not correct.
30
Severe error: abnormal end of program or function. The
opera-tion has ended, possibly because the program was not able to handle data that was not correct or because the user canceled it.
40
Abnormal end of job or program. The job was not started or failed
to start, a job-level function may not have been done as required, or the job may have been canceled.
50
System status. Issued only to the system operator message queue.
It gives either the status of or a warning about a device, a subsystem, or the system.
60
Device integrity. Issued only to the system operator message
queue, indicating that a device is not working correctly or is in some way no longer operational.
70
System alert and user messages. A condition exists that, although
not severe enough to stop the system now, could become more severe unless preventive measures are taken.
80
System integrity. Issued only to the system operator message
queue. Describes a condition where either a subsystem or system cannot operate.
90
Action. Some manual action is required, such as entering a reply or
changing printer forms.
