Iseries

449
AS/400 Advanced Series IBM Operator Tasks – Multiple Operating Systems SC21-8384-01

description

Operations

Transcript of Iseries

Page 1: Iseries

AS/400 Advanced Series IBM

Operator Tasks –Multiple Operating Systems

SC21-8384-01

Page 2: Iseries
Page 3: Iseries

AS/400 Advanced Series IBM

Operator Tasks –Multiple Operating Systems

SC21-8384-01

Page 4: Iseries

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, PuertoRico, or Guam, you can order publications through the IBM Software Manufacturing Solutions at 800+879-2755. Publications are notstocked 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 mailyour comments to the following address:

IBM CorporationAttention Department 542IDCLERK3605 Highway 52 NRochester, MN 55901-7829 USA

or you can fax your comments to:

United States and Canada: 800+937-3430Other countries: (+1)+507+253-5192

If you have access to Internet, you can send your comments electronically to [email protected]; IBMMAIL, toIBMMAIL(USIB56RZ).

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believesappropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1995, 1996. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Page 5: Iseries

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About Operator Tasks – Multiple Operating Systems (SC21-8384) . . . . . . xiWho Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiWhat You Should Do Before You Use this Book . . . . . . . . . . . . . . . . . . xiiWhere to Go for Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

AS/400 System Operation

| Chapter 1. AS/400 System Operations Tasks . . . . . . . . . . . . . . . . . 1-1What You Need to Know about Your Control Panel . . . . . . . . . . . . . . . . 1-1IPL Types and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

| Uninterrupted Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Quick 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-1Using the OS/400 Sign On Display during an IPL . . . . . . . . . . . . . . . . . 2-3

Chapter 3. Stopping the System Unit . . . . . . . . . . . . . . . . . . . . . . 3-1Stopping the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter 4. The OS/400 System Console . . . . . . . . . . . . . . . . . . . . . 4-1Device Name of the System Console . . . . . . . . . . . . . . . . . . . . . . . . 4-1How the System Console Display is Different from Other Displays . . . . . . . 4-1

Chapter 5. Handling OS/400 Messages . . . . . . . . . . . . . . . . . . . . . 5-1Most Common Types of OS/400 Messages . . . . . . . . . . . . . . . . . . . . 5-1Displaying OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Identifying Messages from the System . . . . . . . . . . . . . . . . . . . . . . . 5-5How to Handle Break Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Displaying OS/400 System Operator Messages . . . . . . . . . . . . . . . . . . 5-7Working with OS/400 Message Queues . . . . . . . . . . . . . . . . . . . . . . 5-10Handling OS/400 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Understanding OS/400 Keyboard Error Messages . . . . . . . . . . . . . . . . 5-15Sending OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Chapter 6. Using OS/400 CL Commands to Do Tasks . . . . . . . . . . . . 6-1CL Commands — Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Using Operational Assistant Displays . . . . . . . . . . . . . . . . . . . . . . . . 6-2Using Assistance Levels and User Profiles . . . . . . . . . . . . . . . . . . . . . 6-3Doing Specific Tasks (GO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Chapter 7. Printing with OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Finding OS/400 Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Copyright IBM Corp. 1995, 1996 iii

Page 6: Iseries

Managing Printed Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Working with Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Working with Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Working with All Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Comparing System/36 Print Commands to OS/400 Print Commands . . . . . 7-15

Chapter 8. Working with OS/400 Subsystems . . . . . . . . . . . . . . . . . 8-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Working with a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Chapter 9. OS/400 System Security . . . . . . . . . . . . . . . . . . . . . . . 9-1Levels of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Chapter 10. Controlling OS/400 Jobs . . . . . . . . . . . . . . . . . . . . . 10-1Submitting Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Working with Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5Looking at Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10Working with Signed-On Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Displaying Detailed Job Information . . . . . . . . . . . . . . . . . . . . . . . 10-14Changing How a Job Is Run . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16Working with Job Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19

Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1Displaying and Changing Device Status . . . . . . . . . . . . . . . . . . . . . . 11-1Renaming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Displaying and Changing a Device Description . . . . . . . . . . . . . . . . . 11-3Printing Local Device Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Activating Communications Lines and Controllers . . . . . . . . . . . . . . . . 11-4Configuring Remote Communications . . . . . . . . . . . . . . . . . . . . . . . 11-5Using a Switched Communications Line . . . . . . . . . . . . . . . . . . . . . 11-6

Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . . . 12-1Saving the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Restoring the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Saving the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . . . 12-2Restoring the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . 12-3Saving AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Restoring AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Saving Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Restoring Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Chapter 13. Working with Licensed Internal Code and OS/400 ProgramTemporary Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

AS/400 Program Maintenance Strategy . . . . . . . . . . . . . . . . . . . . . . 13-1Ordering LIC and OS/400 PTFs and PTF Information . . . . . . . . . . . . . . 13-2

Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . . . . 14-1Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . . . . . 14-3Transferring to an AS/400 Advanced 36 Machine Using the STRM36PRC

Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7

iv AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 7: Iseries

SSP for the OS/400 Operator

Chapter 15. Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . 15-1Starting the AS/400 Advanced 36 Machine from the OS/400 Command line 15-1Starting the AS/400 Advanced 36 Machine Automatically . . . . . . . . . . . 15-5

Chapter 16. Stopping an AS/400 Advanced 36 Machine . . . . . . . . . . 16-1Putting the AS/400 Advanced 36 Machine In a Dedicated State . . . . . . . . 16-1Stopping an AS/400 Advanced 36 Machine from the SSP System Console . 16-2Stopping an AS/400 Advanced 36 Machine from the OS/400 Operating

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Chapter 17. Operating the SSP Console and SSP Subconsoles . . . . . 17-1The SSP Console: A Way of Controlling the AS/400 Advanced 36 Machine 17-1The SSP Subconsole: A Way of Controlling SSP Printers . . . . . . . . . . . 17-1Transferring the SSP Console Function to an Alternative SSP Console . . . 17-2Using the SSP Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4Using the Subconsole Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Chapter 18. Handling SSP Messages . . . . . . . . . . . . . . . . . . . . . 18-1How You Know That You Have an SSP Message . . . . . . . . . . . . . . . . 18-1Types of SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2Displaying SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-6Replying to SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-7Sending SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9SSP Keyboard Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-10Displaying Keyboard Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-11

Chapter 19. Using SSP Commands and Procedures to Do Tasks . . . . 19-1Using Help for Commands and Procedures . . . . . . . . . . . . . . . . . . . 19-1

Chapter 20. Printing with SSP . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Finding SSP Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2Managing Printer Output — Command Summary . . . . . . . . . . . . . . . . 20-3Managing Printer Output — Complete Details . . . . . . . . . . . . . . . . . . 20-3Working with Spool Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6Creating Printed Output — Selected Examples . . . . . . . . . . . . . . . . . 20-8Configuring Printer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

Chapter 21. Working with SSP Subsystems . . . . . . . . . . . . . . . . . 21-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1Starting an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Ending an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Displaying the Status of an SSP Subsystem . . . . . . . . . . . . . . . . . . . 21-2

Chapter 22. SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Menu Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Badge Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2Communications Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2Resource Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3Working with SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3

Contents v

Page 8: Iseries

Chapter 23. Controlling SSP Jobs . . . . . . . . . . . . . . . . . . . . . . . 23-1Working With Current Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . 23-2Working with the History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

Chapter 24. Working with SSP Devices and Communications . . . . . . 24-1Displaying and Changing Device Status . . . . . . . . . . . . . . . . . . . . . . 24-1Printing Local Device Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1Displaying Communications Lines and Controllers . . . . . . . . . . . . . . . . 24-1Configuring Remote Communications Lines . . . . . . . . . . . . . . . . . . . 24-1

Chapter 25. Saving and Restoring the AS/400 Advanced 36 MachineInformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1

Saving and Restoring an AS/400 Advanced 36 Machine . . . . . . . . . . . . 25-1Saving and Restoring the SSP Operating System, Licensed Programs, and

Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2

Chapter 26. Working with SSP Program Temporary Fixes . . . . . . . . 26-1AS/400 Advanced 36 Program Maintenance Strategy . . . . . . . . . . . . . . 26-1Ordering SSP PTFs and PTF Information . . . . . . . . . . . . . . . . . . . . . 26-3Displaying or Printing Cumulative PTF Information . . . . . . . . . . . . . . . 26-3Installing Cumulative SSP PTF Packages . . . . . . . . . . . . . . . . . . . . 26-5Corrective SSP PTFs (Patches) . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5Mapping the TC Device ID to the CD-ROM Drive . . . . . . . . . . . . . . . 26-16What to Do if the Mapping Failed . . . . . . . . . . . . . . . . . . . . . . . . 26-17Changing the TC Device ID Back to a Tape Cartridge Drive . . . . . . . . . 26-17

Chapter 27. Establishing a Communications Link for RemoteWorkstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1

Using Remote Work Station Support . . . . . . . . . . . . . . . . . . . . . . . 27-1

AS/400 System Common Operator Tasks

Chapter 28. Problem Handling . . . . . . . . . . . . . . . . . . . . . . . . . 28-1Hardware Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1Handling AS/400 Advanced 36 Machine Error Codes . . . . . . . . . . . . . . 28-9

Chapter 29. System-to-System Communications - ILANCommunications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1

Setting up ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . 29-3Understanding Default Startup Settings . . . . . . . . . . . . . . . . . . . . . . 29-3Manually Starting the ILAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3Automatically Starting ILAN Communications . . . . . . . . . . . . . . . . . . . 29-6Disabling Automatic Startup of ILAN . . . . . . . . . . . . . . . . . . . . . . . . 29-7Finding Out the OS/400 Control Point Name . . . . . . . . . . . . . . . . . . . 29-8Stopping ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . . 29-8ILAN Communications Verification . . . . . . . . . . . . . . . . . . . . . . . . 29-10Finding Out Why ILAN Is Not ACTIVE or VARIED ON . . . . . . . . . . . . 29-13Using Display Station Pass-Through . . . . . . . . . . . . . . . . . . . . . . . 29-15

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36Configurations and Machines . . . . . . . . . . . . . . . . . . . . . . . . . . 30-1

Using the Work with AS/400 Advanced 36 Machine Command . . . . . . . . 30-1Using the Work with AS/400 Advanced 36 Machine Configuration Command 30-8

vi AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 9: Iseries

Summary Table of CL Commands for Managing AS/400 Advanced 36Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-1Configuration That Exists Immediately after Installation . . . . . . . . . . . . . 31-2Defining a Communications Line or a LAN . . . . . . . . . . . . . . . . . . . . 31-4Defining a Diskette Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-8Defining a Tape or CD-ROM Device . . . . . . . . . . . . . . . . . . . . . . . 31-10Defining Printers and Display Stations Using Device Mapping . . . . . . . . 31-12Defining Printers and Display Stations Using Controller Mapping . . . . . . 31-17Changing a Workstation Controller from Controller Mapping to Device

Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-22Defining Whether SSP or OS/400 Controls SSP Printer Output . . . . . . . 31-26Defining Whether SSP or OS/400 Controls the Display Station . . . . . . . 31-36Validating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 31-39

Chapter 32. Displaying Information About an AS/400 Advanced 36Configuration and Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1

Displaying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1Displaying a Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-2

Other Useful Information

Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1System/36 Procedures to AS/400 Commands Cross-Reference . . . . . . . . A-1System/36 Control Commands to AS/400 Commands Cross-Reference . . . A-27System/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-1Displaying the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Setting the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Appendix C. Performance Considerations . . . . . . . . . . . . . . . . . . C-1Understanding Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1Understanding Prestart Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2Setting Attributes For the AS/400 Advanced 36 Server Job . . . . . . . . . . C-3Setting attributes for the AS/400 Advanced 36 SLIC Tasks . . . . . . . . . . C-5Setting Attributes for the AS/400 Advanced 36 Prestart Jobs . . . . . . . . . C-6

Appendix D. Using Electronic Customer Support . . . . . . . . . . . . . . D-1Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1Reviewing Status of an Open Problem . . . . . . . . . . . . . . . . . . . . . . D-3Ordering PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Appendix E. Preparing SSP for Dedicated State . . . . . . . . . . . . . . . E-1

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Contents vii

Page 10: Iseries

viii AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 11: Iseries

Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends tomake 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 equivalentproduct, program, or service may be used instead of the IBM product, program, or service. The evaluationand 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, NY10594, U.S.A.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange 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 CorporationSoftware Interoperability Coordinator3605 Highway 52 NRochester, 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. Thispublication may also refer to products that have not been announced in your country. IBM makes nocommitment to make available any unannounced products referred to herein. The final decision toannounce 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 illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

This publication contains small programs that are furnished by IBM as simple examples to provide anillustration. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannotguarantee or imply reliability, serviceability, or function of these programs. All programs contained hereinare provided to you "AS IS". THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED.

Trademarks

The following terms are trademarks of the IBM Corporation in the United States or other countries or both:

Copyright IBM Corp. 1995, 1996 ix

Page 12: Iseries

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 throughX/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 betrademarks or service marks of others.

Advanced Peer-to-Peer NetworkingAdvanced Function PrintingAFPAppleApplication DevelopmentApplication System/400APPNAS/400C/400CICSDisplayWriteFORTRAN/400IBMIMSInformation AssistantIPXPSF

OfficeVision/400Operating System/400Operational AssistantOS/400Q & AQuestionRPG/400RM/COBOL-85SystemViewSystem/36System/38SUNTRNUltimedia400486

x AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 13: Iseries

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, seethe System Operation book, SC41-4203.

That part of the system that contains the SSP operating system and related dataand 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/400Advanced 36 machine. The tasks that were previously done using OS/400 areunchanged. However, there are some things the OS/400 operator will need toknow in order to do tasks with the AS/400 Advanced 36 machine. There are alsoadditional 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 thefollowing:

� 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 goodrunning 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.

� Work with subsystems.

Copyright IBM Corp. 1995, 1996 xi

Page 14: Iseries

� 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 ofthe system.

� Part 3: SSP for the OS/400 Operator

– Contains information on tasks you can do to manage the AS/400 Advanced36 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 usingan Internal Local Area Network (ILAN).

– Contains information on managing AS/400 Advanced 36 machines andtheir 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 BookTo use this book effectively, you should have:

� Completed the installation instructions in the Getting SSP and OS/400 Installedand Running book, SC21-8377.

� Read the General Information for SSP Operating System book, SC21-8299.

xii AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 15: Iseries

� Learned how to interpret the display indicators and the control panel on thedisplay 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 InformationFor operating instructions for your display station, refer to the operator's guide forthe display station that is attached to your system.

For information about OS/400 system operator tasks that are not included in thisbook, see the System Startup and Problem Handling book, SC41-4206. That bookcontains 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 aparticular topic.

For information about Advanced 36 publications, see the Advanced 36 InformationDirectory book, SC21-8292.

For information about other AS/400 publications (except Advanced 36), see eitherof 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 fromselected other publishers. The AS/400 Information Directory is shipped withthe 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 withSC21.

If you are using your AS/400 system in a System/36 environment, start the AS/400system 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 followingmanuals for information about the System/36 environment:

� System/36 Environment Programming, SC41-4730

� System/36 Environment Reference, SC41-4731

About Operator Tasks – Multiple Operating Systems (SC21-8384) xiii

Page 16: Iseries

xiv AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 17: Iseries

AS/400 System Operation

| Chapter 1. AS/400 System Operations Tasks . . . . . . . . . . . . . . . . . 1-1What You Need to Know about Your Control Panel . . . . . . . . . . . . . . . . 1-1

Control Panel Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2IPL Types and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

| Uninterrupted Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Quick Reference to Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

| Additional Information that Applies to the AS/400 System . . . . . . . . . . . . 1-8

Copyright IBM Corp. 1995, 1996

Page 18: Iseries

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 19: Iseries

Control 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 PanelSystem 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 thecover. To open the cover, do as follows:

Copyright IBM Corp. 1995, 1996 1-1

Page 20: Iseries

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 isindented.

If you have difficulty locating the indentation, look at the diagram in Figure 1-1on 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.

Function01 Display Selected IPL02 Select IPL03 Start IPL04 Lamp Test11 System Reference Code

Enter

Function/Data

RTSP035-2

AB

D

GF

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 theoptions on the Power On and Off Tasks (POWER) menu are used, thePower On light does not blink.

.B/ Power pushbutton: Use the power pushbutton to start the system and stopthe system. To start the system, press the pushbutton once. To stop orpower off the system, press the pushbutton twice.

1-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 21: Iseries

Control Panel

� Power on is allowed in Manual or Normal mode. Power off is allowed inManual mode only.

Note: In most cases, to stop the system, use the Power Down System(PWRDWNSYS) command on any command line of your OS/400display station after stopping all AS/400 Advanced 36 machines.If you use the Power pushbutton to turn off the system, errors mayoccur with data files. For more information on stopping thesystem, see “Stopping the AS/400 System” on page 3-1.

.C/ Processor Active light : The system unit has one Processor Active light. Thelight 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 informationabout 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 bothfunction and data. When you press a Select pushbutton (.F/), the functionnumbers on the Function/Data display increase or decrease. For example, 01becomes 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 Mbecomes 02.

Only the numbers that can be used in the present mode are displayed. TheFunction/Data display can display up to 8 digits. The selected function is notprocessed until the Enter pushbutton (.G/) is pressed.

System reference codes or other information from the processing unit orcontrol panel are also shown in the Function/Data display.

Note: If the system attention light comes on, it indicates the system requiresoperator attention. In this case, a code of 11-3 becomes the SystemReference Code (SRC) when you push the Enter pushbutton. Anexample of an SRC is A6ððð9ð2.

.F/ Select pushbuttons: There are two select pushbuttons. These buttons areused to increase or decrease the number shown in the Function/Data display.The select pushbutton on the left increases the values in the Function/Datadisplay. The select pushbutton on the right decreases the values in theFunction/Data display.

Either pushbutton can be used to change the data shown in the Function/Datadisplay 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 byusing Function 02. To select IPL type, do the following:

1. Press one of the Select pushbuttons until 02 is visible in the function/datadisplay area.

2. Press the Enter pushbutton (.G/).

3. Press one of the Select pushbuttons until the IPL type and mode youwant is visible in the function/data display area.

4. Press the Enter pushbutton.

Chapter 1. AS/400 System Operations Tasks 1-3

Page 22: Iseries

Control Panel

5. Press one of the select pushbuttons until ð1 is visible in the function/datadisplay 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 theemergency power off code. Use of Function code 08 may cause unpredictableresults.

.G/ Enter pushbutton: The Enter pushbutton is used to send function informa-tion shown in the Function/Data display to the processing unit or to save thetype of IPL type and mode you selected.

Note: You can also display the IPL type and mode. To do so, follow steps 5and 6 on page 1-4 described under the .F/ Select pushbuttons topic.

1-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 23: Iseries

IPL Types and Modes

IPL Types and ModesThe IPL types and modes are:

A M Performs a Manual IPL from the A side of the disk. This mode may beused when applying or removing Licensed Internal Code (LIC) PTFs. Itcan 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 aretold to do so by your support representative.

B M Performs a Manual IPL from the B side of the disk. This mode shouldonly be used when an attended IPL must be performed or you need topower off the system. This type of IPL is used when you need tochange the system date and time permanently.

B N Performs a normal IPL from the B side of the disk. This is the type andmode used most of the time. It is also the mode the system must be inif you want to do an unattended IPL.

C M Allows service representatives to perform a special IPL. This mode isfor use only by service representatives. Never IPL in this type andmode.

C N Allows service representatives to perform a special IPL. This mode isfor use only by service representatives. Never IPL in this type andmode.

D M Performs a manual IPL from either CD-ROM or tape. This mode isused to install Licensed Internal Code and the OS/400 operating systemin attended mode. This is the most often used IPL type and mode forinstallation.

D N Performs a normal IPL from either CD-ROM or tape. This mode is usedto install Licensed Internal Code and the OS/400 operating system inunattended mode.

Manual When the mode is set to Manual (M), the system allows you to do allmanual IPLs, such as an operator-attended IPL from disk, CD-ROM ortape. Manual mode also allows you to do some manual control func-tions, such as selecting an IPL type and mode or displaying the kind ofIPL that the system is set to run. However, in manual mode, youcannot do a remote IPL, an IPL by date and time, or an IPL after apower 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

� IPL after a power failure

Chapter 1. AS/400 System Operations Tasks 1-5

Page 24: Iseries

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 inthe Manual (M) or Normal (N) IPL modes:

Note: You can display the kind of IPL the system is set to do when the system isin any mode.

If you want to stop the system when the mode is set to Normal, use the PowerDown System (PWRDWNSYS) command at any display station after you stop theAS/400 Advanced 36 machines. You must have QSYSOPR authority to use thePower Down System (PWRDWNSYS) command.

Figure 1-3. Operation Summary for Manual and Normal Modes

OperationManualMode

NormalMode

Turn on system (Powerpushbutton)

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 referencecode

Allowed Allowed

Remote IPL Not allowed Program control allowed

Timed IPL Not allowed Program control allowed

Restart IPL (after powerfailure)

Not allowed Program control allowed

Power Down Systemcommand

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. YourAS/400 system unit and the OS/400 console should be connected to the UPS. Ifthe 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.

1-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 25: Iseries

Quick Reference

Quick Reference to Operator TasksThis table provides information on where to find out how to do OS/400 and SSPoperator 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 SystemUnit and OS/400 OperatingSystem”

Chapter 15, “Starting an AS/400Advanced 36 Machine”

Stopping the System Chapter 3, “Stopping the SystemUnit”

Chapter 16, “Stopping an AS/400Advanced 36 Machine”

Understanding Consoles and Sub-consoles

Chapter 4, “The OS/400 SystemConsole”

Chapter 17, “Operating the SSPConsole and SSP Subconsoles”

Handling Messages Chapter 5, “Handling OS/400Messages”

Chapter 18, “Handling SSPMessages”

Using Commands to Do Tasks Chapter 6, “Using OS/400 CLCommands to Do Tasks”

Chapter 19, “Using SSP Com-mands and Procedures to DoTasks”

Printing Chapter 7, “Printing with OS/400” Chapter 20, “Printing with SSP”

Working with Subsystems Chapter 8, “Working with OS/400Subsystems”

Chapter 21, “Working with SSPSubsystems”

Understanding Security Chapter 9, “OS/400 SystemSecurity”

Chapter 22, “SSP Security”

Controlling Jobs Chapter 10, “Controlling OS/400Jobs”

Chapter 23, “Controlling SSPJobs”

Working with Devices and Commu-nications

Chapter 11, “Working with OS/400Devices and Communications”

Chapter 24, “Working with SSPDevices and Communications”

Saving and Restoring Chapter 12, “Saving and RestoringOS/400 and OS/400 Objects”

Chapter 25, “Saving and Restoringthe AS/400 Advanced 36 MachineInformation”

Working with Program TemporaryFixes (PTFs)

Chapter 13, “Working withLicensed Internal Code andOS/400 Program Temporary Fixes”

Chapter 26, “Working with SSPProgram Temporary Fixes”

Transferring to an AS/400Advanced 36 machine

Chapter 14, “Transferring to anAS/400 Advanced 36 Machine”

Not applicable

Establishing communication with aremote workstation

Not applicable Chapter 27, “Establishing a Com-munications Link for RemoteWorkstations”

Solving Problems Chapter 28, “Problem Handling” Chapter 28, “Problem Handling”

Establishing Internal System Com-munications

Chapter 29, “System-to-SystemCommunications - ILANCommunications”

Chapter 29, “System-to-SystemCommunications - ILANCommunications”

Managing Your AS/400 Advanced36 Machines and Their Configura-tions. (For example, creating,starting, or deleting an AS/400Advanced 36 machine)

Chapter 30, “Using CL Commandsto Manage AS/400 Advanced 36Configurations and Machines”

Chapter 30, “Using CL Commandsto Manage AS/400 Advanced 36Configurations and Machines”

Chapter 1. AS/400 System Operations Tasks 1-7

Page 26: Iseries

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 36Configuration

Chapter 31, “Changing YourAS/400 Advanced 36 MachineConfiguration”

Chapter 31, “Changing YourAS/400 Advanced 36 MachineConfiguration”

Displaying Information About anAS/400 Advanced 36 Configurationand Machine

Chapter 32, “Displaying Informa-tion About an AS/400 Advanced 36Configuration and Machine”

Chapter 32, “Displaying Informa-tion About an AS/400 Advanced 36Configuration and Machine”

Using Media Chapter 4 of the System Startupand Problem Handling book,SC41-4206.

Chapter 7 of the Operating YourComputer–SSP Operating Systembook, SC21-8297.

| Additional Information that Applies to the AS/400 SystemOther 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”

� Appendix E, “Preparing SSP for Dedicated State”

1-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 27: Iseries

OS/400 for the SSP Operator

Chapter 2. Starting the System Unit and OS/400 Operating System . . . 2-1Using the OS/400 Sign On Display during an IPL . . . . . . . . . . . . . . . . . 2-3

Chapter 3. Stopping the System Unit . . . . . . . . . . . . . . . . . . . . . . 3-1Stopping the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Preparing to Stop the System . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Using the POWER Menu to Stop the System . . . . . . . . . . . . . . . . . . 3-2Using the Power Down System Command to Stop the System . . . . . . . . 3-3Using the Power Pushbutton to Stop the System . . . . . . . . . . . . . . . . 3-4

Chapter 4. The OS/400 System Console . . . . . . . . . . . . . . . . . . . . . 4-1Device Name of the System Console . . . . . . . . . . . . . . . . . . . . . . . . 4-1How the System Console Display is Different from Other Displays . . . . . . . 4-1

Chapter 5. Handling OS/400 Messages . . . . . . . . . . . . . . . . . . . . . 5-1Most Common Types of OS/400 Messages . . . . . . . . . . . . . . . . . . . . 5-1Displaying OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Finding Additional Information about Your Messages . . . . . . . . . . . . . 5-3Identifying Messages from the System . . . . . . . . . . . . . . . . . . . . . . . 5-5

Message Severity Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5How to Handle Break Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Displaying OS/400 System Operator Messages . . . . . . . . . . . . . . . . . . 5-7

Your User Profile Message Queue . . . . . . . . . . . . . . . . . . . . . . . . 5-8Responding to OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Working with OS/400 Message Queues . . . . . . . . . . . . . . . . . . . . . . 5-10Changing a Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Handling OS/400 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Handling Important System Messages in the QSYSMSG Message Queue 5-14Creating the QSYSMSG Message Queue . . . . . . . . . . . . . . . . . . . 5-14Error Messages on Menus and Displays . . . . . . . . . . . . . . . . . . . . 5-15

Using the Work with Problems Command . . . . . . . . . . . . . . . . . 5-15Understanding OS/400 Keyboard Error Messages . . . . . . . . . . . . . . . . 5-15Sending OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Using the Send Message Command to Send a Message . . . . . . . . . . 5-16Using the Send Break Message Command to Send a Message . . . . . . 5-17

Chapter 6. Using OS/400 CL Commands to Do Tasks . . . . . . . . . . . . 6-1CL Commands — Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Using Operational Assistant Displays . . . . . . . . . . . . . . . . . . . . . . . . 6-2Using Assistance Levels and User Profiles . . . . . . . . . . . . . . . . . . . . . 6-3

Changing Assistance Level Displays . . . . . . . . . . . . . . . . . . . . . . . 6-4Changing Assistance Levels Temporarily — Examples . . . . . . . . . . . . 6-5Changing Assistance Levels in Your User Profile . . . . . . . . . . . . . . . . 6-7Using CL Commands with the Operational Assistant Displays . . . . . . . . 6-8

Doing Specific Tasks (GO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Menus for System Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Chapter 7. Printing with OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Copyright IBM Corp. 1995, 1996

Page 28: Iseries

Printer Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Finding OS/400 Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Getting to the Work with Printer Output Display Using Operational Assistant 7-3Getting to the Work with Printer Output Display Using a CL Command . . . 7-3Using the Work with Printer Output Display to Find Output . . . . . . . . . . 7-4Understanding Printing Problems . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Printing Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Managing Printed Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Holding Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Releasing Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Deleting Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Changing Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7What to Do if the Printer Output Is Not Already Printing . . . . . . . . . . . . 7-8Assigning Printer Output to a Printer . . . . . . . . . . . . . . . . . . . . . . . 7-9

Working with Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Starting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Stopping a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Restarting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Answering Printer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Changing Forms on a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Working with Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Working with All Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Comparing System/36 Print Commands to OS/400 Print Commands . . . . . 7-15

Chapter 8. Working with OS/400 Subsystems . . . . . . . . . . . . . . . . . 8-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

OS/400 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1SSP Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Working with a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Working with Subsystem Descriptions . . . . . . . . . . . . . . . . . . . . . . 8-2

Chapter 9. OS/400 System Security . . . . . . . . . . . . . . . . . . . . . . . 9-1Levels of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Changing the Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Chapter 10. Controlling OS/400 Jobs . . . . . . . . . . . . . . . . . . . . . 10-1Submitting Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Submitting a Batch Job to Run Immediately . . . . . . . . . . . . . . . . . . 10-2Scheduling a Batch Job to Run Later . . . . . . . . . . . . . . . . . . . . . 10-2

Changing a Job Schedule to Run at a Different Date or Time . . . . . . 10-3Scheduling a Job Using Job Schedule Entries . . . . . . . . . . . . . . . 10-3Adding a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Saving a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Removing a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . 10-4Changing a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . 10-5Holding and Releasing a Job Schedule Entry . . . . . . . . . . . . . . . 10-5Scheduling a Batch Job to Start an AS/400 Advanced 36 Machine . . . 10-5

Working with Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5Displaying Batch Jobs of Other Users . . . . . . . . . . . . . . . . . . . . . 10-6Displaying All Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6Displaying Batch Jobs by Status . . . . . . . . . . . . . . . . . . . . . . . . 10-7

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 29: Iseries

Holding a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8Releasing a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9Ending a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9Working with Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Looking at Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10Holding a Job Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11Releasing a Job Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11Working with Unassigned Job Queues . . . . . . . . . . . . . . . . . . . . 10-11

Working with Signed-On Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Displaying Signed-On Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Creating a Customized Work with User Jobs Command . . . . . . . . . . 10-12Signing Users Off the System . . . . . . . . . . . . . . . . . . . . . . . . . 10-13Finding Signed-On Users and Sorting the User List . . . . . . . . . . . . 10-14Finding Additional Information about Signed-On Users . . . . . . . . . . 10-14Sending Messages to Signed-On Users . . . . . . . . . . . . . . . . . . . 10-14

Displaying Detailed Job Information . . . . . . . . . . . . . . . . . . . . . . . 10-14Displaying Job Status Attributes . . . . . . . . . . . . . . . . . . . . . . . . 10-15Displaying Job Definition Attributes . . . . . . . . . . . . . . . . . . . . . . 10-15Displaying Job Run Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 10-15Displaying the Call Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15Displaying Open Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15

Changing How a Job Is Run . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16Changing a Job’s Priority on a Job Queue . . . . . . . . . . . . . . . . . 10-16Moving a Job to a Different Job Queue . . . . . . . . . . . . . . . . . . . 10-17Changing How an Active Job Is Run . . . . . . . . . . . . . . . . . . . . . 10-17Changing a Job’s Print Priority . . . . . . . . . . . . . . . . . . . . . . . . 10-18Assigning a Job to a Different Output Queue . . . . . . . . . . . . . . . . 10-18

Working with Job Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19Displaying a Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19Printing a Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19Changing the Logging Level for a Job . . . . . . . . . . . . . . . . . . . . 10-20Filtering Messages from the Job Log . . . . . . . . . . . . . . . . . . . . . 10-20Sending Job Log Output Files to a Separate Output Queue . . . . . . . 10-21

Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1Displaying and Changing Device Status . . . . . . . . . . . . . . . . . . . . . . 11-1

Device Status Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Renaming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Considerations for Renaming Devices . . . . . . . . . . . . . . . . . . . . . 11-2Displaying and Changing a Device Description . . . . . . . . . . . . . . . . . 11-3Printing Local Device Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Activating Communications Lines and Controllers . . . . . . . . . . . . . . . . 11-4Configuring Remote Communications . . . . . . . . . . . . . . . . . . . . . . . 11-5Using a Switched Communications Line . . . . . . . . . . . . . . . . . . . . . 11-6

Using Manual Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Using Manual Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7Using Manual Answer for Countries Other Than the United States . . . . 11-7

Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . . . 12-1Saving the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Restoring the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Saving the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . . . 12-2Restoring the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . 12-3Saving AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

OS/400 for the SSP Operator

Page 30: Iseries

Restoring AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Saving Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Saving Objects in Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Saving Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Saving Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Saving Changed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Saving Documents, Folders, and Mail . . . . . . . . . . . . . . . . . . . . . 12-4Saving Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Saving Licensed Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Saving Specific Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Saving Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Restoring Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . 12-5Restoring Objects in Directories . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Restoring Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Restoring Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Restoring Changed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Restoring Documents, Folders, and Mail . . . . . . . . . . . . . . . . . . . . 12-6Restoring Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Restoring Licensed Programs . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Restoring Specific Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Restoring User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Restoring Object Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Chapter 13. Working with Licensed Internal Code and OS/400 ProgramTemporary Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

AS/400 Program Maintenance Strategy . . . . . . . . . . . . . . . . . . . . . . 13-1Preventive Service (Cumulative PTF Packages) . . . . . . . . . . . . . . . 13-1Corrective 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-1Important Information about Transferring . . . . . . . . . . . . . . . . . . . 14-1Restrictions on Transfers using the TFRM36 and STRM36PRC Commands 14-1

Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . . . . . 14-3Transferring 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 STRM36PRCCommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

Using the STRM36PRC Command . . . . . . . . . . . . . . . . . . . . . . . 14-6Running an SSP Procedure from OS/400 — Examples . . . . . . . . . 14-7

Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7Running the STRPASTHR command: . . . . . . . . . . . . . . . . . . . . . 14-8

Transferring to an AS/400 Advanced 36 Machine Using theSTRPASTHR Command — Examples . . . . . . . . . . . . . . . . . . . 14-8

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 31: Iseries

Starting System Unit

Chapter 2. Starting the System Unit and OS/400 OperatingSystem

| 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 Advanced36 machines that are set up to automatically start. For information on startingAS/400 Advanced 36 machines, see Chapter 15, “Starting an AS/400 Advanced 36Machine.”

| 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 areloaded 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 workstationsavailable to OS/400. For information on assigning workstations to OS/400 or SSP,see “Defining Whether SSP or OS/400 Controls the Display Station” onpage 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. Anunattended IPL is done automatically by the system after the power to the systemis turned on.

An attended IPL shows various displays on the display station used for the OS/400console and allows you to change configuration options or change certain systemvalues 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 theIPL mode should be set to on the system control panel.

Copyright IBM Corp. 1995, 1996 2-1

Page 32: Iseries

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 36machines that are running.

3. Set QIPLTYPE system value to 0(Unattended).

4. Type PWRDWNSYS *IMMEDRESTART(*YES) on any commandline and press Enter.

1. Set IPL mode to Manual.

2. Stop any AS/400 Advanced 36 machinesthat are running.

3. Type PWRDWNSYS *IMMEDRESTART(*YES) on any command lineand press Enter.

4. Follow the display on the console tocomplete 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/400console 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 andProblem Handling book, SC41-4206.

� Setting Up Your Automatic Power On and Off Schedules

� Starting a Remote System

� Changing Your System during IPL

� System Password

2-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 33: Iseries

Starting System Unit

Using the OS/400 Sign On Display during an IPL

à@ ð Sign On

System . . . . . : SYSTEMð1Subsystem . . . . : QBASEDisplay . . . . . : 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 theoptional entry fields you want to use. Use the Tab key to move the cursor fromfield to field on the display.

Notes:

a. The Password field is shown only if password security is active on thesystem 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, “Workingwith OS/400 Subsystems.”

� The workstation identifier (ID)

2. Press Enter .

If this is an attended IPL, the IPL Options display is shown. The IPL optionsdisplay is used to clear job logs or spool files and to set the system time anddate fields. For more information about the IPL Options display, see theSystem Startup and Problem Handling book, SC41-4206.

If this is an unattended IPL, (depending on what options you select on thisdisplay or what is defined in your user profile), one or more of the followingoccurs:

� 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, theprogram 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.

Chapter 2. Starting the System Unit and OS/400 Operating System 2-3

Page 34: Iseries

Starting System Unit

� The system cleanup functions are automatically started with default values.For more information about customizing the cleanup function, see chapter 8of 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 ProblemHandling book, SC41-4206.

2-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 35: Iseries

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/400Advanced 36 machines that are not already stopped.

Attention: If you power off the system unit without stopping the AS/400 Advanced36 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 SystemYou can stop the system in several different ways:

� POWER menu

� Power Down System (PWRDWNSYS) command

� Power Pushbutton

Preparing to Stop the System1. 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 astatus of Started and return here.

For directions, see Chapter 16, “Stopping an AS/400 Advanced 36Machine.”

d. From the OS/400 console, stop all AS/400 Advanced 36 machines thathave a status of Starting or Job Queue. To do so, use the End AS/400Advanced 36 Machine (ENDM36) command. For information on using theWRKM36 command to stop AS/400 Advanced 36 machines which couldnot be stopped in the usual way, see “Ending an AS/400 Advanced 36Machine” 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 ensurethe integrity of data on the media.

Copyright IBM Corp. 1995, 1996 3-1

Page 36: Iseries

Stopping the AS/400 System

Using the POWER Menu to Stop the SystemTo 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 youcan:

� 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/95Time . . . . . . . . . . . : ð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 thatcauses the subsystems to end all active jobs.

Note: Do not turn the modem on or off when the system is turned off andis made ready for remote IPL. Otherwise, the system may startunexpectedly, then turn itself off in a few minutes.

5. To power off the system and then restart the system immediately after itpowers off:

a. In the option field, type

4

to select Power off the system immediately and then power on.

3-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 37: Iseries

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 startsagain automatically.

Note: Do not turn the modem on or off when the system is turned off andis made ready for remote IPL. Otherwise, the system may startunexpectedly, then turn itself off in a few minutes.

Important Note

If you stop the system using the automatic power schedule or one of theoptions on the Power On and Off Tasks (POWER) menu, the IPL date and timesystem value (QIPLDATTIM) is checked and, if necessary, reset to the nextscheduled power-on time. This checking does not occur if you power off inanother way, so the system may not power on automatically. To force thepower schedule to update the QIPLDATTIM system value, enter the followingcommand on any command line and then press Enter .

CHGPWRSCDE DAY(\TODAY) PWRONTIME(\SAME) PWROFFTIME(\SAME)

Using the Power Down System Command to Stop the SystemThe Power Down System (PWRDWNSYS) command prepares the system forending 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 bestarted by any subsystem. For example, jobs that are on a job queue as a result ofa 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 theirjob logs are produced.

Note: All media in the devices are unloaded before the system is powered downto ensure the integrity of data on the media.

The Power Down System (PWRDWNSYS) command can be used on any OS/400command 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.

The Power Down System (PWRDWNSYS) command prompt appears.

Chapter 3. Stopping the System Unit 3-3

Page 38: Iseries

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 theHelp key or F1 provides additional information about that parameter.

Using the Power Pushbutton to Stop the SystemIf you cannot use option 3 (Power off the system immediately) or option 4 (Poweroff 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 turnthe 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 thatcannot 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 toManual.

Note: Do not turn the modem on or off when the system is turned off and is madeready for remote IPL. Otherwise, the system may start unexpectedly, thenturn itself off in a few minutes.

Normal Sequence

1. Press the Power pushbutton. The Function/Data display blinks with O?. (theinternational power off symbol).

Note: To cancel the power off operation, press any other pushbutton on thecontrol panel.

2. Press the Power pushbutton again. The Power On light blinks as the system isbeing 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 Attentionlight 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/Datadisplay.

3. Press the Power Pushbutton. The Function/Data display blinks with O? (Theinternational power off symbol).

4. Press the Power Pushbutton again. The system will immediately power off.

3-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 39: Iseries

OS/400 System Console

Chapter 4. The OS/400 System Console

The OS/400 system console is the workstation that allows you to control andobserve system operations. It is the workstation attached to the first input/outputprocessor capable of supporting workstations.

The system controls which display station is the OS/400 console. The systemmoves the OS/400 console only if the display station at the first workstation I/Oprocessor, port 0, address 0 no longer works.

For more information in determining which workstation is the OS/400 console, seethe System Startup and Problem Handling book, SC41-4206.

Device Name of the System ConsoleTo 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 theconsole. You cannot change this system value.

How the System Console Display is Different from Other DisplaysThe console display is like any other display with the exception of system breakmessages and commands. Unless the CHGMSGQ QSYSOPR *BREAK commandis issued, break messages are displayed only on the console. However, you canview these system messages using the DSPMSG QSYSOPR command from anOS/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 commandsmust be run from the OS/400 system console:

� DST commands

� ENDSBS command if the subsystem you are ending is the controlling sub-system.

Copyright IBM Corp. 1995, 1996 4-1

Page 40: Iseries

OS/400 System Console

4-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 41: Iseries

Displaying Messages

Chapter 5. Handling OS/400 Messages

Note: The displays shown in this chapter are those you would see if you wererunning at a basic assistance level. You would see different displays atother assistance levels.

A message is any communication sent from one point to another point on theAS/400 system. The communication may be between you and the system orbetween 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 MessagesInformational messages do not require a reply. These messages give you status

on what the system is doing, errors that you make, and responses thatyou make to messages. Informational messages appear directly on theworkstation display in the message line. The message line is thebottom 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 messagequeue.

Displaying OS/400 MessagesA message sent to your message queue is not usually shown automatically. Amessage 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 inFigure 5-1 on page 5-2.

Note: If you are interrupted, the Display Messages display is always shown. Itdoes not change based on the assistance level you are running with.

Copyright IBM Corp. 1995, 1996 5-1

Page 42: Iseries

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:33This 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 themby:

� 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.

Figure 5-2 on page 5-3 shows the Work with Messages display.

5-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 43: Iseries

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 MessageMessages needing a reply

_ Controller SYSTEMð1 contact not successful. Probable remote stationproblem (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ð:ðð

BottomF1=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 notifymode, you turn the message waiting light off.

To print the messages in a message queue if your assistance level is *BASIC, usethe 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 youwant to print.

You can also print messages contained in a message file with the Display MessageDescription (DSPMSGD) command and F4 (Prompt). Specify a range of messageidentifiers and *PRINT for the Output (OUTPUT) parameter.

Finding Additional Information about Your MessagesTo 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 messagethat does not need a reply, you receive the additional information about thatmessage. If the message requires a reply, you can type your reply in the fieldprovided at the bottom of the Additional Message Information display.

For example, Figure 5-3 on page 5-4 shows additional information about the firstinquiry message in Figure 5-2:

Chapter 5. Handling OS/400 Messages 5-3

Page 44: Iseries

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 remotestation problem. (C R)

Cause . . . . . : The system was trying to exchange identifiers with thestation 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 ofthe 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 . . . . . . . . . . . : QSYSARBUser . . . . . . . . . . . . : QSYSNumber . . . . . . . . . . . : ðð93ð2

From program . . . . . . . . . : QSWCDCR

To message queue . . . . . . . : QSYSOPRLibrary . . . . . . . . . . : QSYS

Bottom Press Enter to continue.

F1=Help F3=Exit F12=Cancel

á ñ

Figure 5-4. Display Message Details display

5-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 45: Iseries

Displaying Messages

To print a single message, use F6 (Print) on the Additional Message Informationdisplay. This prints all the information about the message shown on the display.

Identifying Messages from the SystemOn some message displays, the message is accompanied by a letter and numbercode 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 othersin 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. Theexample 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 errormessage and additional message information is shown.

Message Severity CodesFigure 5-6 shows the different severity codes of the messages and the types theyare associated with.

Figure 5-6 (Page 1 of 2). Message Severity Codes

Message Type Severity Code

Informational messages. For informational purposes only; no replyis needed. The message can indicate that a function is in progress orthat a function has completed successfully.

00

Warning. A potential error condition exists. The program may havetaken a default, such as supplying missing data. The results of theoperation are assumed to be successful.

10

Chapter 5. Handling OS/400 Messages 5-5

Page 46: Iseries

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 automaticrecovery 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 maynot 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 recoveryprocedures and no defaults are possible. If the error was in thesource data, the entire data record was skipped. If the error occurredwhile 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 handledata that was not correct or because the user canceled it.

40

Abnormal end of job or program. The job was not started or failedto start, a job-level function may not have been done as required, orthe 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 messagequeue, indicating that a device is not working correctly or is in someway no longer operational.

70

System alert and user messages . A condition exists that, althoughnot severe enough to stop the system now, could become moresevere unless preventive measures are taken.

80

System integrity. Issued only to the system operator messagequeue. Describes a condition where either a subsystem or systemcannot operate.

90

Action. Some manual action is required, such as entering a reply orchanging printer forms.

99

5-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 47: Iseries

Displaying Messages

How to Handle Break MessagesThe following is an example of the Display Messages display which appears whena break message is sent.

à@ ð 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:33This 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

á ñ

When you receive break messages that do not need a reply,

1. Read the message carefully.

2. Press Enter to get back to the display you were working on before the inter-ruption.

If the break message needs a reply, just type the reply on the line provided andpress Enter . If you don’t want to reply to the break message, just press F12 tocancel. The display you were working on before the interruption appears again,and you can continue your work.

Notes:

1. Remember, occasionally the last few characters entered before an interruptionmay be lost.

2. To display more information about a message, place the cursor under themessage and press Enter. The Additional Message Information displayappears.

Displaying OS/400 System Operator MessagesTo display messages in the system operator message queue (QSYSOPR), do oneof the following:

� Press F6 (Display system operator messages) on the Work with Messagesdisplay.

Chapter 5. Handling OS/400 Messages 5-7

Page 48: Iseries

Displaying Messages

� Type DSPMSG QSYSOPR ASTLVL(*BASIC) on any command line and pressEnter .

� Select option 1 (Display messages for system operator) on the TechnicalSupport Tasks (TECHHELP) menu.

� Select option 3 (Work with system operator messages) on the Manage YourSystem, Users, and Devices (MANAGESYS) menu.

� Select option 6 (Display system operator messages) on the System Requestmenu.

Figure 5-7 shows the Work with Messages display with system operator messages.

à@ ðWork with Messages

System: SYSTEMð1 Messages for: System Operator

Type options below, then press Enter. 4=Remove 5=Display details and reply

Opt MessageMessages needing a reply

_ Device PRTð1 not available (C R)

Messages not needing a reply_ An adapter has inserted or left the token-ring on line TOKENRING._ An adapter has inserted or left the token-ring on line TOKENRING._ An adapter has inserted or left the token-ring on line TOKENRING._ An adapter has inserted or left the token-ring on line TOKENRING._ An adapter has inserted or left the token-ring on line TOKENRING._ Device ABRS2 no longer communicating._ Device ABRS1 no longer communicating._ Communications device ABRðð was allocated to subsystem QCMN.

More...F1=Help F3=Exit F5=Refresh F6=Display your messages F16=Remove messages not needing a reply F17=Top F24=More keys

á ñ

Figure 5-7. System Operator Message Queue

You can work with the system operator messages exactly as you would any othermessages. See “Responding to OS/400 Messages” on page 5-9 for information onhow to reply or get additional information about these messages.

Your User Profile Message QueueWhen signing on to the system, the message queue defined in your user profile isput into the delivery mode specified in your user profile. For the system operator(user profile QSYSOPR), this message queue is QSYSOPR, unless it has beenchanged.

Whenever you transfer to an alternative job, your user profile message queue is setto hold the messages. This allows your user profile message queue to move withyou when you transfer back and forth between these two jobs.

However, if you transfer to an alternative job and then sign on as a different user,the user profile message queue defined in the other user’s user profile will have itsdelivery mode set. At this time someone else can change the delivery mode ofyour user profile message queue, so when you transfer back, your user profile

5-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 49: Iseries

Displaying Messages

message queue will not be set back to the delivery mode it was set to when doingthe first transfer.

Responding to OS/400 MessagesThe system sometimes sends you error messages that require you to choose aresponse code option. Based on the option codes given (always in parentheses),this is generally a one-character response.

For example, notice the five response option codes for this message:

Verify alignment on device PRTð1. (I C G N R)

Messages of this kind with response option codes most often appear on the systemoperator message queue. However, under certain circumstances, they can alsoappear on your own message queue.

You do not have to know or remember the meanings of the numbers or letters inany response option code. The Additional Message Information display providesinformation about these option codes. In addition, this display also provides a replyline on which you can type your reply (if a reply is needed).

To get to the Additional Message Information display from the Work with Messagesdisplay:

1. Position the cursor on the option line in front of the message you want torespond to.

2. In the option field, type

5

to select Display details and reply.

3. Press Enter .

The Additional Message Information display appears.

4. Page down through the information to find the option you need.

The following is an example of the Additional Message Information display.

Chapter 5. Handling OS/400 Messages 5-9

Page 50: Iseries

Working with Message Queues

à@ ðAdditional Message Information

Message ID . . . . . . : CPA5335 Date sent . . . . . . . : 11/27/95 Time sent . . . . . . : ð8:31:42

H -- To hold the file,1. Press Stop only if Start and Stop are two separate keys.2. Load the new forms.3. Press Cancel.4. Press Stop and Start, or press Start/Stop.5. Type an H.

I -- To continue printing starting with the next line of the file,1. Press Stop only if Start and Stop are two separate keys.2. Load the new forms.3. Press Start or Start/Stop.4. Type an I.

More... Type reply below, then press Enter.

Reply . . . ____________________________________________________________

F1=Help F3=Exit F6=Print F9=Display message details F12=Cancel F21=Select assistance level

á ñ

Working with OS/400 Message QueuesA message queue is like a mail box for messages sent to a user. Each workstationhas a message queue with the same name as the device description name. Eachuser has a message queue with the same name as the user profile name (or userID), and the system operator has a message queue named QSYSOPR. When auser signs on the system for the first time, the system automatically creates a usermessage queue. When a workstation is connected to the system for the first time,the system automatically creates a workstation message queue. When the systemis configured for the first time, the system operator queue is created.

You can see the messages from your workstation and personal message queueson the Work with Messages display. To see how your message queue is set up,press F24 (More keys) on the Work with Messages display and then press F22(Display list details). Figure 5-8 on page 5-11 shows the Display List Detailsdisplay.

5-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 51: Iseries

Working with Message Queues

à@ ðDisplay List Details

Message queue . . . . . : SMITHS1Library . . . . . . . : QSYS

Delivery . . . . . . . : \NOTIFY Program . . . . . . . . : \DSPMSG Severity . . . . . . . : ð Allow alerts. . . . . . : \YES CCSID . . . . . . . . . : Description . . . . . . : Work Station Message Queue

Message queue . . . . . : SMITHLibrary . . . . . . . : QUSRSYS

Delivery . . . . . . . : \NOTIFY Program . . . . . . . . : \DSPMSG Severity . . . . . . . : ð Allow alerts. . . . . . : \NO CCSID . . . . . . . . . : 65535 Description . . . . . . : Jim Smith

Press Enter to continue.

F1=Help F3=Exit F12=Cancel

á ñ

Figure 5-8. Display List Details display

This display shows the following information about your user and workstationmessage queues:

Message QueueThis is the name of the message queue on which the messages are found.

LibraryThis is the library that contains the message queue.

DeliveryThis is the method by which messages are delivered, whether they interruptyou, sound an alarm, hold until answered, or automatically send a default reply.

ProgramThis is the name of the program called when a message arrives in a queue thatis set to interrupt and the severity of the message is equal to or greater thanthe queue severity value.

SeverityMessages sent to the message queue with a severity level equal to or greaterthan this severity level interrupt you or turn on the message waiting lightdepending on how your message delivery is set.

Allow alertsThis value indicates whether messages sent to this message queue might alsogenerate an alert.

CCSIDThis is the coded character set identifier associated with the message queue.

DescriptionThis is the description of the message queue, usually the name and address ofthe message queue owner.

Chapter 5. Handling OS/400 Messages 5-11

Page 52: Iseries

Working with Message Queues

Changing a Message QueueYou can change the way a message queue notifies you of messages, change themessage queue severity level, or the break-handling program. To change the infor-mation shown on the Display List Details display:

1. On an OS/400 command line, type

CHGMSGQ

2. Press F4.

The Change Message Queue (CHGMSGQ) display appears.

3. Specify the name of the message queue you want to change for the Messagequeue (MSGQ) parameter and the name of the library containing the messagequeue you selected.

Note: Steps 4 through 12 on page 5-13 are optional.

4. Specify the delivery mode you want to use for the Delivery (DLVRY) parameter.

� *SAME: The method of message delivery does not change. If this param-eter has not been changed in a previous command, *SAME means that*HOLD is the method of delivery. However, if the specified message queueis a workstation message queue, it is automatically changed to *NOTIFY bythe system at sign-on.

� *BREAK: When you receive a message, your work is interrupted, and aseparate message display that contains the message is shown (unless youhave specified a program to handle the message).

� *NOTIFY: When you receive a message, your work is not interrupted. Youare notified that a message has arrived by the workstation attention lightand an alarm (if your workstation has one) that sounds. You can use eitherthe Display Messages (DSPMSG) command or Work with Messages(WRKMSG) command to see the message.

� *HOLD: The message queue keeps or holds the messages until yourequest them using the Display Messages (DSPMSG) or Work with Mes-sages (WRKMSG) command. You are not notified when a new messagearrives.

� *DFT: All messages are ignored, and any messages requiring a reply aresent the default reply. For the system operator message queue(QSYSOPR), the messages are kept in the queue and logged in the historylog, QHST; this is known as unattended operation. For any other user orworkstation message queue, none of the messages are kept in the queue.

5. Specify the severity code you want to use for the Severity code filter (SEV)parameter.

The severity code is used to filter messages that interrupt your work or turn onyour Message Waiting light. For example, if you enter a message severitycode of 59 and the message queue is in break mode, the system shows mes-sages with codes of 59 or greater. After you make this change, any messagewith a severity code of 59 or greater sent to the same message queue causesthe Display Message display to be shown (unless you have specified a differentprogram to handle the message).

If you type a message severity code of 59, and the message queue is in notifymode, the system notifies the user of any messages in the message queue that

5-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 53: Iseries

Working with Message Queues

have a severity code of 59 or greater. After you make this change, anymessage with a severity code of 59 or greater sent to the same messagequeue causes a light to turn on at the workstation and the alarm (if your work-station has one) to sound. See “Message Severity Codes” on page 5-5 formore information on the types of messages and what they mean.

6. Type the text that describes the purpose for the message queue.

7. Press F10 (Additional parameters) to display more parameters you can use.

8. Specify the name of the program (and library) to be called for the Break han-dling program (PGM) parameter if you specified *BREAK for the Delivery(DLVRY) parameter.

9. Specify *NO for the Reset old messages (RESET) parameter to prevent mes-sages you have already displayed but not removed from your message queuefrom being reset to the same status as new messages. Specify *YES to resetmessages you have displayed on the message queue to the same status asnew messages. Resetting old messages to new allows you to receive themagain.

10. For the Force to auxiliary storage (FORCE) parameter, specify one of thefollowing:

� *SAME to use the value specified in the identified message queue.

� *NO to specify that changes made to the message queue, including itsmessages, are not immediately forced into auxiliary storage.

� *YES to specify that all changes made to the message queue descriptionand to the messages in the queue are immediately forced into auxiliarystorage. If this field value is changed to *YES, the message queue isforced into auxiliary storage each time it is changed. This is an importantrecovery tool for message queues that provides communications betweenprograms, but it may slow down system performance.

11. Specify the value you want to use for the allow alerts (ALWALR) parameter:

� *SAME uses the value specified in the identified message queue.

� *NO specifies that this message queue does not allow alerts to be gener-ated from messages sent to it.

� *YES specifies that this message queue does allow alerts to be generatedfrom messages sent to it.

12. Specify the character value you want to use for the coded character set identi-fier (CCSID) parameter:

� *SAME uses the value specified in the identified message queue.

� *HEX specifies that messages on this message queue cannot be con-verted.

� *MSG specifies that the CCSID of a message on this message queue is tobe determined from the message.

� *JOB specifies that the CCSID of all messages on this message queue areto be considered in the CCSID of the job.

� Any valid job CCSID specifies that the CCSID of all messages on thismessage queue are to be considered in this CCSID.

13. Press Enter to change the message queue.

Chapter 5. Handling OS/400 Messages 5-13

Page 54: Iseries

Handling OS/400 Error Messages

Handling OS/400 Error MessagesYou will receive a variety of system messages that indicate conditions ranging fromsimple typing errors to problems with system devices or programs. The messagemay be one of the following:

� An error message on your current display.

� A message regarding a system problem that is sent to the system operatormessage queue and shown on a separate Work with Messages display.

� A message regarding a system problem that is sent to the message queuespecified in a device description.

� A message regarding a potential severe system condition that is sent to theQSYSMSG message queue, the system operator message queue, and othermessage queues specified by the users.

Handling Important System Messages in the QSYSMSG MessageQueue

The QSYSMSG message queue is an optional message queue that you create inthe QSYS library. The QSYSMSG message queue can be used to monitor specificsystem messages that indicate potentially severe system conditions. Only mes-sages that require immediate action are sent to the QSYSMSG message queue.Monitor the QSYSMSG message queue to be aware of critical messages related toyour system.

Creating the QSYSMSG Message QueueTo create the QSYSMSG message queue:

1. On an OS/400 command line, type

CRTMSGQ QSYS/QSYSMSGTEXT ('optional MSGQ to receive specific system messages')

2. Press Enter .

Once the QSYSMSG message queue is created, certain specific system messagesare directed to it. For example, the following message would be sent to theQSYSMSG message queue:

CPF0907 Serious storage condition may exist. Press HELP.

For a complete listing and description of these messages, see Chapter 8, “WorkingWith Messages” in the CL Programming book.

You can write a break-handling program that monitors messages sent to theQSYSMSG message queue and takes action on specific messages you identify.To set up a program to receive messages from the QSYSMSG message queue,see Chapter 8, “Working With Messages” in the CL Programming book.

5-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 55: Iseries

Handling OS/400 Error Messages

Error Messages on Menus and DisplaysIf you request a task the system cannot run because of an error, an error messageappears at the bottom of the display. Depending on the workstation, the keyboardmay also lock.

Note: Displays of some application programs may not have message lines.

To obtain additional information about the error:

1. Move the cursor to the same line as the message, if you can move the cursor.

2. Press the Help key. The Additional Message Information display is shown.This display gives you more information about the error.

Some messages allow you to run problem analysis. When you display a messagequeue, these messages have an asterisk (*) in front of them (intermediate assist-ance level) or are highlighted (basic assistance level).

Note: Messages about critical system errors or conditions are reverse-imaged(intermediate assistance level), or highlighted (basic assistance level).

Using the Work with Problems CommandTo run the Work with Problems (WRKPRB) command:

� Intermediate Assistance Level

1. From the Display Messages display, move the cursor to the message thathas an asterisk (*) beside it.

2. Press Help .

� Basic Assistance Level

1. From the Work with Messages display, type

5

in the Opt field to select Display Details and Reply.

2. Press Enter .

The Additional Message Information display is shown. Press the F14 (Work withproblem) key. From the Work with Problem (WRKPRB) display, you can show thedetails of the problem and work directly with the problem.

To run the Work with Problem (WRKPRB) command for critical messages, pressF15 (Work with critical problems) from the Additional Message Information display.

Problem analysis helps you resolve an error that you could not resolve from themessage or the Additional Message Information display. For more informationabout handling problems, see Chapter 6 of the System Startup and Problem Han-dling book, SC41-4206.

Understanding OS/400 Keyboard Error MessagesWhen you press the wrong keyboard keys by mistake, the computer simply stopsand tells you what is wrong. The computer has simply locked up the keyboard soyou cannot continue your task until you make the necessary correction.

Chapter 5. Handling OS/400 Messages 5-15

Page 56: Iseries

Sending OS/400 Messages

If you make an error, you should get a flashing number in the lower left corner ofthe display. In many cases, the number is ððð5. Some workstations show thenumber briefly and then replace it with a statement. The statement is called anerror message .

To find out what the error message means, press the key marked Help . If yourkeyboard does not have a Help key, press F1.

The number is replaced with text. For example, the text might read: Cursor inprotected area of display. The computer does not have a precise message forevery error because it does not know why the wrong keys were pressed.

Press the Error Reset key and the message disappears.

The keyboard is now back to normal and you can continue with your task.

Sending OS/400 MessagesAs the system operator, you can send Informational messages like System BeingShut Down at 6:ðð.

Messages are sent to any of the following:

� QSYSOPR (The system operator message queue)

� A user message queue

� The workstation message queue

Using the Send Message Command to Send a MessageThe Send Message (SNDMSG) command is used by a person to send an imme-diate message to one or more message queues. An immediate message is amessage that is not predefined and is not stored in a message file.

The message can be sent to the system operator, to other user ID's, to a user'smessage queue, to all currently active message queues or to the system historylog, QHST. The sender can also require a reply from the message receiver.

To send a message,

1. On an OS/400 command line, type

SNDMSG

2. Press F4.

3. Type a message in the Message text field.

The message you type can contain a maximum of 512 characters. If the textcontains blanks or other special characters, the text must be enclosed in apos-trophes.

5-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 57: Iseries

Sending OS/400 Messages

4. Type one of the allowable values in the To user profile field.

In the To user profile field, you can specify any of the following:

user-profile-name Specify the user profile name of the user to whom themessage is sent.

*SYSOPR Sends the message to the system operator message queue,QSYS/QSYSOPR.

*REQUESTER Sends the message to the user profile message queue for inter-active jobs or to the system operator's message queue(QSYS/QSYSOPR) for batch jobs.

*ALLACT Sends a copy of the message to the user profile message queue ofeach user profile with an interactive job currently running. *ALLACTcannot be specified with inquiry messages.

5. Press Enter .

The message is sent.

Using the Send Break Message Command to Send a MessageThe Send Break Message (SNDBRKMSG) command is used to send an immediatemessage to one or more workstation message queues. This command temporarilyinterrupts the tasks being done by those who receive the message.

To send a break message, do the following:

1. On an OS/400 command line, type

SNDBRKMSG

2. Press F4.

3. Type a message in the Message text field.

The message you type can contain a maximum of 512 characters. If the textcontains blanks or other special characters, the text must be enclosed in apos-trophes. If you use the command prompter (F4), the apostrophes are automat-ically added.

4. Complete the other required fields.

5. Press Enter .

The message is sent.

You use the other fields on the Send Break Message (SNDBRKMSG) display asfollows:

To workstation message queue (TOMSGQ) Specifies the names of one or moreworkstation message queues to which the break message is sent. Onlythe names of workstation message queues can be specified and only*LIBL or QSYS can be specified for the library value.

You can enter more than one value. If you are on an entry display andyou need additional entry fields to enter more values, type a plus sign(+) in the entry field opposite the phrase "+ for more" and press Enter .

*ALLWS The break message is sent to all workstation and PersonalComputer message queues. *ALLWS cannot be specified foran inquiry message.

Chapter 5. Handling OS/400 Messages 5-17

Page 58: Iseries

Sending OS/400 Messages

message-queue-name Specify the name of the message queue towhich the break message is being sent. The possible libraryvalues are:

*LIBL All libraries in the job's library list are searcheduntil the first match is found.

library-name Specifies the library where the message queueis located.

Message type (MSGTYPE) Specifies the type of message that is sent in breakmode. Only informational or inquiry message types can be specified.Inquiry messages may require a response.

*INFO Send an information only message.

*INQ Send an inquiry message. The workstation receiving themessage is expected to reply to it. An inquiry messagecannot be sent to multiple queues with only one command.

Message queue to get reply (RPYMSGQ) Specifies, only if an inquiry message issent, the name of the message queue that the workstation user's replyis sent to.

QSYSOPR Specifies the replies to the break message are sent to thesystem operator's message queue, QSYSOPR.

message-queue-name Specifies the name of the message queue towhich a reply to the break message is sent. Only a user orworkstation message queue can be specified.

The possible library values are:

*LIBL All libraries in the job's library list are searcheduntil the first match is found.

library-name Specify the library where the message queueis located.

Coded character set ID (CCSID) Specifies the coded character set identifier(CCSID) that the specified message text is in. The text supplied in theMessage field is assumed to be in the CCSID supplied by this param-eter.

The possible values are:

*JOB The message text is assumed to be in the CCSID of the jobrunning this command.

*HEX The message text is not converted. CCSID 65535 is used.

coded-character-set-identifier Specify a valid CCSID in which youwant your message text to be considered in. Valid valuesrange from 1 through 65535.

5-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 59: Iseries

Sending OS/400 Messages

Chapter 6. Using OS/400 CL Commands to Do Tasks

OS/400 CL commands are commands run from the OS/400 command line. Thesecommands allow you to give explicit instructions to the system without usingmenus.

CL Commands — OverviewExcept for special commands like GO, CL commands have a verb part and anobject part. The verb part is a three letter prefix. Some examples are as follows:

The object part of the CL command is all of the characters after the first three char-acters. This second part of the command identifies the type of object you areworking with. Some examples are as follows:

The format of a CL command is:

command parameter(value) parameter(value) parameter

Some CL commands do not require parameters or have default parameters. If youdo not know which parameters can be specified for a specific command, type thecommand and then press F4. A display is displayed for that specific command.

There are three columns on the display. The left column shows the name of theparameters, the center column is where you type the parameter values, and theright column shows the values that are allowed for the parameters.

The defaults are filled in for you if defaults exist. If you want to use a differentvalue, you can type that value over the default. If a value is required, the line ishighlighted and no default is filled in.

Figure 6-1. Verb Part of CL Command

Verb Abbreviated CommandPrefix

Example command

Change CHG CHGPF

Create CRT CRTLIB

Display DSP DSPMSGQ

Start STR STRBGU

Work with WRK WRKJOBQE

Figure 6-2. Object Part of CL Command

Object Abbreviated CommandSuffix

Example command

Physical file PF CHGPF

Library LIB CRTLIB

Message Queue MSGQ DSPMSGQ

Business Graphics Utility BGU STRBGU

Job Queue Entry JOBQE WRKJOBQE

Copyright IBM Corp. 1995, 1996 6-1

Page 60: Iseries

What are the Operational Assistant Displays?

If you do not know what a value means or what a parameter is, move your cursorto the value or parameter and press F1. A new display overlays the existing onewith information about the value or parameter.

When you are more comfortable with commands, you may choose to type the com-mands in without using prompting. If you do this, you only have to type therequired parameters. The defaults are known already to the system. You can alsotype as many parameters on the command line as you remember and then promptusing F4.

When you type the command on the command line, remember to:

� Start with the command.

� Follow the command by the required parameters.

� Use parentheses around the values for the required parameters.

� Leave no space between the required parameter and the value in parentheses.

� Press F4 if you cannot remember all of the required parameters.

� Press Enter when your command is complete.

A cross-reference of System/36 commands and AS/400 CL commands is included| in Appendix A, “System/36 and AS/400 Commands Cross-Reference.” A complete| list of CL commands is included in chapter 6 of Programming Reference Summary| book, SX41-4720. For more information on a specific CL command, you can do

either of the following:

� Type the command on an OS/400 command prompt and press F4. Move thecursor to a value or parameter and press F1.

� Refer to CL Reference book, SC41-4722.

Using Operational Assistant DisplaysThe Operational Assistant* displays are a menu-driven interface that allow you todo commonly performed system tasks quickly and easily. The OperationalAssistant displays:

� Simplify everyday tasks such as controlling printer output, controlling jobs, andhandling messages

� Allow you to set up a schedule for automatic power on and off, automaticcleanup, and backup

� Allow you to backup your system

� Allow you to manage the devices attached to your system, users enrolled onthe system, signed-on users, and disk space storage

All of these tasks can be done by selecting options from the Operational Assistantmenu. The Operational Assistant menu can be displayed in the following ways:

� Type go assist on any command line, and press Enter .

OR

� Press the Attention key.

Figure 6-3 on page 6-3 shows the Operational Assistant menu.

6-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 61: Iseries

Using Assistance Levels

Security Consideration

You must have at least a user class of system operator (*SYSOPR) to see all ofthe options on this menu.

à@ ð ASSIST AS/4ðð Operational Assistant (TM) Menu System: SYSTEMð1 To select one of the following, type its number below and press Enter:

1. Work with printer output2. Work with jobs3. Work with messages4. Send messages5. Change your password

1ð. Manage your system, users, and devices11. Customize your system, users, and devices

75. Information and problem handling

8ð. Temporary sign-off

Type a menu option below __

F1=Help F3=Exit F9=Command line F12=Cancel

á ñ

Figure 6-3. Operational Assistant (ASSIST) Menu

When you install the current release of the OS/400 licensed program, the Opera-tional Assistant function is ready to use.

Using Assistance Levels and User ProfilesYou can choose the level of information you want when you interact with thesystem. There are three levels of information called assistance levels:

1=BasicShows the displays that provide the most assistance. Basic assistancelevel supports the more common operator tasks and user tasks, anddoes not use computer terminology. Some less often used functions arenot shown.

2=IntermediateShows the displays that support all system tasks and uses computer ter-minology. Complicated tasks can be done by using this level.

3=AdvancedShows the displays that provide the same functions as the intermediateassistance level. However, the displays contain as much information aspossible by not displaying the allowed function keys and options.

Note: The advanced assistance level is only available for some dis-plays.

Chapter 6. Using OS/400 CL Commands to Do Tasks 6-3

Page 62: Iseries

Using Assistance Levels

Changing Assistance Level DisplaysYou can change from one assistance level to another on most OperationalAssistant displays. For example, to change assistance levels on the Work withMessages (WRKMSG) display:

1. Press F21 (Select assistance level).

Figure 6-4 shows the Select Assistance Level window.

à@ ðWork with Messages

................................................................ m: SYSTEMð1 : Select Assistance Level : : : : Current assistance level . : Basic : : : : : : Type choice below, then press Enter. : : : : Assistance level . . . . . 2 1=Basic : : 2=Intermediate : : : : : : : : F1=Help F12=Cancel : : : :..............................................................:

An adapter has inserted or left the token-ring on line TOKENRING.An adapter has inserted or left the token-ring on line TOKENRING.Writer ð11286/QSPLJOB/PRTð1 started.

More...F1=Help F3=Exit F5=Refresh F12=Cancel F17=Top F18=Bottom F21=Select assistance level F22=Display list details

á ñFigure 6-4. Select Assistance Level Window

The value in the Assistance level field shows the assistance level you are cur-rently using and the assistance levels that are available.

2. Type a 1 (Basic) to select the basic assistance level, a 2 (Intermediate) toselect the intermediate assistance level, or a 3 (Advanced) to select theadvanced assistance level (if available).

3. Press Enter .

4. The display you see on your system corresponds to the assistance level youselected.

You can also change the assistance level by typing the command you want runfollowed by astlvl(\xxxxx) where \xxxxx is \basic for basic assistance level,\intermed for intermediate assistance level, and \advanced for advanced assistancelevel. You can designate the assistance level for the following CL commands:

� Display Messages (DSPMSG)� Display System Status (DSPSYSSTS)� Work with Configuration Status (WRKCFGSTS)� Work with Messages (WRKMSG)� Work with Spooled Files (WRKSPLF)� Work with System Status (WRKSYSSTS)� Work with User Jobs (WRKUSRJOB)� Work with User Profiles (WRKUSRPRF)

6-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 63: Iseries

Using Assistance Levels

� Work with Writers (WRKWTR)

Changing Assistance Levels Temporarily — ExamplesExample 1

To change the assistance level for the Work with User Jobs (WRKUSRJOB)command and reach the Work with Signed-On Users display:

1. On an OS/400 command line, type

WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\INTERACT) ASTLVL(\BASIC)

2. Press Enter .

Example 2

To change the assistance level for the Work with Users Jobs (WRKUSRJOB)command and reach the Work with Jobs display :

1. Type

WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\BATCH) ASTLVL(\BASIC)

2. Press Enter .

Note: If you follow the directions in examples 1 and 2, you only change the assist-ance level for one use of the command. If you issue another command andthen use the WRKUSRJOB command again, you return to the intermediateassistance level.

Example 3

To see messages at the basic assistance level as shown in Figure 6-5 onpage 6-6:

1. Type

DSPMSG ASTLVL(\BASIC) MSGQ(QSYSOPR)

2. Press Enter .

OR

1. Type

DSPMSG MSGQ(QSYSOPR)

2. Press Enter .

3. Press F21 (Select assistance level).

4. Type

1

to select Basic.

5. Press Enter .

Chapter 6. Using OS/400 CL Commands to Do Tasks 6-5

Page 64: Iseries

Using Assistance Levels

à@ ðWork with Messages

System: SYSTEMð1 Messages in: QSYSOPR

Type options below, then press Enter. 4=Remove 5=Display details and reply

Opt MessageMessages needing a reply

_ Device RMTPRTðð13 not available. (C R)_ Device RMTPRTðð12 not available. (C R)_ Device RMTPRTððð9 not available. (C R)_ Device RMTPRTðððð not available. (C R)_ Load form type '\STD' device PRTð1 writer PRTð1. (H C G I R)_ Device KOLUMDEV not available. (C R)

Messages not needing a reply_ An adapter has inserted or left the token-ring on line TRNLINE._ Controller KK33 contacted on line TRNLINE._ Device K33SS3 no longer communicating.

More... F1=Help F3=Exit F5=Refresh F16=Remove messages not needing a replyF17=Top F18=Bottom F24=More keys

á ñ

Figure 6-5. Work with Messages Display—Basic Assistance Level

Example 4

To see messages at an intermediate assistance level as shown in Figure 6-6 onpage 6-7:

1. Type

DSPMSG ASTLVL(\INTERMED) MSGQ(QSYSOPR)

2. Press Enter .

OR

1. Type

DSPMSG MSGQ(QSYSOPR)

2. Press Enter .

3. Press F21 (Select assistance level).

4. Type

2

to select Intermediate.

5. Press Enter .

6-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 65: Iseries

Using Assistance Levels

à@ ð Display Messages System: SYSTEMð1 Queue . . . . . : QSYSOPR Program . . . . : \DSPMSG

Library . . . : QSYS Library . . . : Severity . . . : 7ð Delivery . . . : \HOLD

Type reply (if required), press Enter.All sessions ended for device BIGELOW.Controller BIGELOW has disconnected.Controller BIGELOW contacted on line TRNLINE.All sessions ended for device BIGELOW.Writer ð11921/QSPLJOB/BIGELOWS5 started.An adapter has inserted or left the token-ring on line TRNLINE.An adapter has inserted or left the token-ring on line TRNLINE.An adapter has inserted or left the token-ring on line TRNLINE.Controller KODO failed. Automatic recovery started.Device KODOS4 no longer communicating.Device KODOS3 no longer communicating.Controller KODO contacted on line TRNLINE.An adapter has inserted or left the token-ring on line TRNLINE.

Bottom F3=Exit F11=Remove a message F12=Cancel F13=Remove all F16=Remove all except unanswered F24=More keys

á ñ

Figure 6-6. Display Messages Display—Intermediate Assistance Level

Changing Assistance Levels in Your User ProfileYou can also change your default assistance level in your user profile. To do this,change the Assistance level field by using the Change User Profile (CHGUSRPRF)command.

Note: You must have *SECADM special authority to issue the CHGUSRPRF CLcommand.

The Operational Assistant function keeps track of what assistance level you haverequested for each of the following groups of displays:

� Printer output � Printers � Jobs � Handling messages � Device status � User enrollment � System status

The assistance level is set for each command, so you can use the basic assistancelevel for some displays and the intermediate assistance level for other displays.For each command, select the assistance level that you feel most comfortableworking with and that allows you to get your work done the easiest way.

Note: Your current assistance level for each command is stored. So when yousign on again, your assistance level remains the same.

Chapter 6. Using OS/400 CL Commands to Do Tasks 6-7

Page 66: Iseries

Using CL Commands with the Operational Assistant Displays

Using CL Commands with the Operational Assistant DisplaysAs you become an experienced AS/400 system user, you may prefer to do sometasks by using commands rather than menus. When you are using the interme-diate or the advanced assistance level, you usually have a command line at thebottom of your display. You can type any control language (CL) command on thiscommand line.

Note: To control whether or not a user has use of a command line, type N (No) inthe Restrict command line use field on the Add User or Change Userdisplay. You can add or change a user on the Work with User Enrollmentdisplay. To find this display, type go setup and select option 10 (Work withuser enrollment) or use the command WRKUSRPRF *ALLASTLVL(*BASIC).

To display a command line when you are using the basic assistance level, press F9(Command line). Figure 6-7 shows the command window that appears at thebottom of your display.

à@ ð ASSIST AS/4ðð Operational Assistant (TM) Menu System: SYSTEMð1 To select one of the following, type its number below and press Enter:

1. Work with printer output2. Work with jobs3. Work with messages4. Send messages5. Change your password

1ð. Manage your system, users, and devices11. Customize your system, users, and devices

75. Information and problem handling

8ð. Temporary sign-off

.............................................................................. : Command : : : : ===> go disktasks_______________________________________________________ :: F4=Prompt F9=Retrieve F12=Cancel : : : :............................................................................:

á ñ

Figure 6-7. Operational Assistant Command Window

If you know the name of the command, you can type the name of the command onthe command line and press F4. A display is shown with all of the fields you needto fill in for that command. Press the Help key or F1 while your cursor is on anyfield to get an explanation of its function and a list of the possible values you cantype in the field.

If you do not know the name of the command you want, you can press F4 withouttyping anything while your cursor is on the command line. The Major CommandGroups menu is shown where you can begin your search for the command youwant.

6-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 67: Iseries

Using CL Commands with the Operational Assistant Displays

Doing Specific Tasks (GO)To get to any menu on the AS/400 system quickly, type go plus the menu ID onany command line, then press Enter . For example, if you want to run your dailybackup, you can get to the Run Backup menu by typing go runbckup on anycommand line and press Enter . The menu ID is shown in the top left corner of thedisplay as in Figure 6-8.

àRUNBCKUP

Figure 6-8. Example of a Menu ID

To find a list of all of the menus on the system:

1. On any OS/400 command line, type

WRKMNU \ALL

Or,

GO \ALL

2. Press Enter .

When a menu name is mentioned in this topic, the menu ID is shown in paren-theses next to the menu name, for example, the Run Backup (RUNBCKUP) menu.

Menus for System OperationsThe following is a list of menus that are particularly useful in controlling and oper-ating the system. You can get to any of these menus directly from any displayhaving a command line. Just type GO plus a menu ID from the following list:

ASSIST The Operational Assistant (ASSIST) menu simplifiessome of the common user tasks, such as working withprinter output, jobs, messages, and changing your pass-word.

In addition, users with proper authority can select optionsto manage or customize the system, check the systemstatus, clean up objects, power the system on and off,enroll users, change some system options, and collectdisk space information.

BACKUP The Backup Tasks (BACKUP) menu allows you to backup (save) the system and initialize the tapes that areused during backup.

CLEANUP The Cleanup (CLEANUP) menu allows you to start, end,or change automatic cleanup. The cleanup functiondeletes old job logs, history logs, messages, office cal-endar items, and journal receivers that take up storagespace.

CMNCFG The Communications Configuration (CMNCFG) menucan be used to configure communications to otherAS/400 systems, System/36s, or to remote work stationcontrollers and attached devices.

Chapter 6. Using OS/400 CL Commands to Do Tasks 6-9

Page 68: Iseries

Using CL Commands with the Operational Assistant Displays

DEVICESTS The Device Status (DEVICESTS) menu allows you tochoose options for working with system devices, such asdisplay stations, printers, tape drives, and diskettedrives.

DISKETTE The Diskette (DISKETTE) menu allows you to work withdiskettes.

DISKTASKS The Disk Space Tasks (DISKTASKS) menu provides theoption for collecting disk space information to help showhow storage is being used on your system. After col-lecting the information, you can specify what informationto include in a report and then print the report.

FILE The Files (FILE) menu allows you to work with files onthe system.

FOLDER The Folders (FOLDER) menu allows you to managefolders. Folders can be used to store other folders anddocuments.

INFO The Information Assistant* Options (INFO) menu allowsyou to find out where to look for information about yourAS/400 system and how to comment on that information.You can also use this menu to find out what is new inthis release of the AS/400 system and what newenhancements and functions will be available in the nextrelease.

LIBRARY The Libraries (LIBRARY) menu allows you to work withlibraries.

MANAGESYS The Manage Your System, Users, and Devices(MANAGESYS) menu allows you to display what activityis going on in the system, run backup, and work with thedevices on the system.

POWER The Power On and Off Tasks (POWER) menu allowsyou to display the power-on and off schedule. If youhave the correct authority, you can also change theschedule or power off the system and then power it onagain.

PROBLEM The Problem Handling (PROBLEM) menu allows you towork with problems, ask questions, and receive answersusing the question and answer database, display systemoperator messages, display the history log, and startsystem service tools (SST).

RESTORE The Restore (RESTORE) menu allows you to restoresaved information from tape, or save file (SAVF) on thesystem.

RUNBCKUP On the Run a Backup (RUNBCKUP) menu you canselect a menu option to specify the type of backup youwant to run.

6-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 69: Iseries

Using CL Commands with the Operational Assistant Displays

SETUP The Customize Your System, Users, and Devices(SETUP) menu lets you customize automatic cleanup,schedule when your system will power on and off, andenroll users.

SETUPBCKUP The Set Up Backup (SETUPBCKUP) menu allows you tochange backup options, lists, and schedules.

STATUS The Status (STATUS) menu allows you to display thestatus of jobs, devices, and system activities.

SYSTEM The General System Tasks (SYSTEM) menu allows youto control system operations, devices, and all jobs on thesystem.

TAPE The Tape (TAPE) menu allows you to use and controltape devices.

TECHHELP The Technical Support Tasks (TECHHELP) menu pro-vides options to help resolve problems on the system.

USERHELP The Information and Problem Handling (USERHELP)menu provides additional information about the systemand is useful in attempting to resolve problems.

Figure 6-9 lists other commonly used AS/400 menu IDs.

If you use the word GO followed by CMD and the verb part or object part of a CLcommand, you go to a menu that lists all commands which contain that part. Verband object parts are explained in “CL Commands — Overview” on page 6-1.

Figure 6-9. Other Commonly Used Menu IDs

Menu ID Description of Menu

DATA Files, Libraries, and Folders

DEFINE Define or Change the System

DEVICE Device Operations (printer, tape, and diskette)

DOCUMENT Documents

FILE2 Files (DDM, System/36)

JOB Jobs

MAIN AS/400 Main Menu

MAJOR Major Command Groups

MESSAGE MESSAGES

OFCTSK Office Tasks

PCSTSK Configure AS/400 for PC Support (PC Support Tasks)

PRINTER Printer

SUPPORT User Support and Education

SYSTEM General System Tasks

USER User Tasks

USER2 User Tasks (remote jobs, Q and A, System/36 environment)

Chapter 6. Using OS/400 CL Commands to Do Tasks 6-11

Page 70: Iseries

Using CL Commands with the Operational Assistant Displays

6-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 71: Iseries

Printing with OS/400

Chapter 7. Printing with OS/400

Note: The displays shown in this chapter are those you would see if you wererunning at a basic assistance level. You would see different displays atother assistance levels.

When you use OS/400, printing is handled differently than when you use SSP. Youdo not need to know everything about printing. To work with your printer outputand printer output created by others, you need to know only the essentials.

DefinitionsThe key elements you need to know about are:

� Spooled files � Printer writers � Output queues � Printers

Spooled FilesIn OS/400, a spooled file is a file that holds output data that is waiting to print. Itis also known as a spooled output file. Multiple spooled files might be waiting toprint. The spooled files are controlled by the person who created them or by theoperator. The operator needs spool control (*SPLCTL) or job control (*JOBCTL)special authorities to work with other people's output.

| In SSP, spool file entries in the spool file hold output data that is waiting to print.The spool file entries are controlled by the person who created them or by theoperator. There is one spool file shared by everyone on the system. All printeroutput goes to this spool file.

Printer WritersIn OS/400, the printer writer is a system program that writes spooled files to aprinter.

In SSP, the spool writer (printer writer) is the part of SSP that prints output saved inspool file entries.

Output QueuesIn OS/400, an output queue contains a list of spooled files that are waiting to print.There can be multiple output queues in OS/400.

| The equivalent to an output queue in SSP is the spool file . The spool file contains| a list of spool file entries waiting to print. There is only one spool file in SSP. All

output waiting to print is in this spool file.

For directions on setting up an AS/400 Advanced 36 machine to send output to anOS/400 output queue, see “Defining Whether SSP or OS/400 Controls SSP PrinterOutput” on page 31-26.

Copyright IBM Corp. 1995, 1996 7-1

Page 72: Iseries

Printing with OS/400

PrintersThe operating systems can share the same printer. For directions on sharingprinters, see “Giving SSP Control of AS/400 Advanced 36 Machine Printer Output”on page 31-26.

The printer can only be used by one operating system at a time. The printer iscontrolled by a subsystem named QSPL. If an SSP job tries to use a printer thatanother SSP or OS/400 job is using, the job receives an error stating that theprinter is in use.

Additional reading: For detailed information about printing elements, printerdevice support, printer spooling support, and Advanced Function Printing* (AFP*),see the Printer Device Programming book, SC41-4713.

7-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 73: Iseries

Finding OS/400 Printer Output

Finding OS/400 Printer Output

Getting to the Work with Printer Output Display Using OperationalAssistant

It is easy to check on a submitted print job when you use Operational Assistant.To see your printer output:

1. On any OS/400 command line, type

GO ASSIST

2. Press Enter .

The AS/400 Operational Assistant Menu appears.

3. In the Type a menu option below field, type

1

to select Work with printer output.

4. Press Enter .

If the Work with All Spooled Files display appears instead of the Work withPrinter Output display:

a. Press F21 so you can change your assistance level.

The Select Assistance Level display appears.

b. In the Assistance Level field, type

1

to select Basic.

c. Press Enter .

The Work with Printer Output display appears.

Getting to the Work with Printer Output Display Using a CL CommandYou could also reach the Work with Printer Output display, by using a CLcommand.

1. On any OS/400 command line, type

WRKSPLF ASTLVL(\BASIC)

2. Press Enter .

The Work with Printer Output display appears.

Figure 7-1 on page 7-4 shows the Work with Printer Output display.

Chapter 7. Printing with OS/400 7-3

Page 74: Iseries

Finding OS/400 Printer Output

Using the Work with Printer Output Display to Find Output

à@ ðWork with Printer Output

System: SYSTEMð1 User . . . . . : PARENTIS Name, \ALL, F4 for list

Type options below, then press Enter. To work with printers, press F22. 2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Message

9=Work with printing status 1ð=Start printing 11=Restart printing

Printer/ Opt Output Status PRTð1__ INVENTORY Printer stopped (use opt 1ð)__ ORDENTRY Printer stopped (use opt 1ð)

PRTð2__ PAYROLL Printing page 3 of 1ðððð

Not Assigned__ TIMECRD Not assigned to a printer (use opt 1ð)

Bottom F1=Help F3=Exit F5=Refresh F6=Completed printer output F11=Dates/pages/forms F2ð=Include system output F24=More keys

á ñ

Figure 7-1. Work with Printer Output display

Initially, only your own printer output is shown. However, you can see the output ofothers if:

� You have job control (*JOBCTL) authority and the output queue was createdwith operator control (OPRCTL) set to *YES. The default is *YES.

Or,

� You have spool control (*SPLCTL) special authority

If you are authorized, you can see the printer output for a specific person or foreveryone. To see the printer output of someone other than yourself,

1. Type the user ID of the other person whose printed output you want to workwith in the User field.

Note: If you do not know the user ID, press F4. This shows the Select a Userdisplay. This display allows you to select a user ID from a list of allusers on the system.

2. If you want to see output for all user IDs that start or end with specific letters,type the letters followed or preceded by an *.

For example, if you want to see output for all the user IDs that start with “AR,”type AR* in the User field.

3. If you want to see the printer output for all users, type *ALL in the User field.

4. After you type your choice in the User field, press Enter .

The printer output on this display is sorted by printer. Some printer output mayhave a status of Not assigned to a printer. Printer output that is notassigned to a printer appears last in the list on your display.

7-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 75: Iseries

Finding OS/400 Printer Output

This display shows you information about your printer output. It shows thePrinter ID, the name of the output sent to that printer, and the status of theoutput.

This display also allows you to release jobs, resume printing, hold jobs, deletejobs, respond to messages about forms, and change the order in which jobsprint.

5. Press F11 (Dates/pages/forms) to see another view of this display that showswhen printer output was created, the number of pages, what forms types areused, and how many copies print.

Understanding Printing ProblemsFigure 7-2 provides some tips on how to solve some common printing problems:

Figure 7-2. Why My Printer Output Does Not Print

Problem Suggested Solution

Unanswered printer messages. Use option 7 Message on the Work with Printer Output display to respondto the message.

Printer is not started. Use option 10 Start printing on the Work with Printer Output display.

Printer output is not assigned to aprinter.

Use option 10 Start printing on the Work with Printer Output display.

Printer output has a forms typethat has not been started for theprinter.

Stop the printer and start it for the desired forms type.

1. Press F22 on the Work with Printer Output display.

2. Use Option 4 on the Work with Printers display to stop the printer.

3. Change the forms if necessary.

4. Use Option 1 on the Work with Printers display to start the printer.

Printer output has a value of*JOBEND in the Schedule fieldand the job has not finished.

Use the Change Spooled File Attributes (CHGSPLFA) CL command tochange the value in the Schedule field to *FILEEND.

Printer output is held. Release the printer output using option 6 Release on the Work with PrinterOutput display.

Nothing is printing on the system. Verify that the QSPL subsystem is started with the WRKSBS CLcommand. If QSPL is not started, use the STRSBS CL command to startit.

Check for messages sent to the QSYSOPR message queue in the QSPLsubsystem. Respond to the messages.

Printer status says Messagewaiting or MSGW, but you cannotfind the message.

See if the printer's message queue is too full to receive new messages. Ifso, remove some messages from the message queue.

It is also possible that the printer's message queue was cleared. If so,check to see if the printer is ready.

If you have followed all of these suggestions and still have printing problems, seethe information on getting help with problems in Chapter 13 of the System Startupand Problem Handling book, SC41-4206.

Chapter 7. Printing with OS/400 7-5

Page 76: Iseries

Printing Priorities

Printing PrioritiesFigure 7-3 maps OS/400 and SSP printing priorities.

Figure 7-3. SSP and OS/400 Printing Priorities

SSPPrinting Priorities

OS/400Printing Priorities

5 3

4 4

3 5

2 6

1 7

0 7 and put in HELD status

7-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 77: Iseries

Managing Printer Output

Managing Printed OutputTo manage printer output, use the Work with Printer Output display.

Holding Printer OutputTo hold printer output, on the Work with Printer Output display:

1. In the option field beside the printer output you want held, type

3

to select the Hold option.

2. Press Enter .

3. Press F5 to refresh the display.

The status of the printer output changes to \Held.

Releasing Printer OutputTo release printer output, on the Work with Printer Output display:

1. In the option field beside the printer output you want released, type

6

to select the Release option.

2. Press Enter .

3. Press F5 to refresh the display.

The status of the printer output changes to \Released.

Deleting Printer OutputTo delete printer output, on the Work with Printer Output display:

1. In the option field beside the printer output you want to delete, type

4

to select Delete.

2. Press Enter .

The Confirm Delete of Printer Output display appears.

3. Press Enter to delete the selected output.

The printer output you deleted no longer appears on the Work with PrinterOutput display.

Changing Printer OutputTo change the attributes of printer output, on the Work with Printer Output display:

1. In the option field beside the printer output for which you want to change attri-butes, type

2

to select Change.

2. Press Enter .

Chapter 7. Printing with OS/400 7-7

Page 78: Iseries

Managing Printer Output

The Change Printer Output display appears. Figure 7-4 on page 7-8 showsthe Change Printer Output display.

à@ ðChange Printer Output

User . . . . . . . . : SMITH Date . . . . . . . . : 1ð/21/9ð Printer output . . . : ACCTPAY Time . . . . . . . . : 13:4ð:ð1 Pages . . . . . . . : 1ð Status . . . . . . . : Waiting to print

Type choices below, then press Enter.

Printer to use . . . . PRTð1_____ Name, F4 for list

Copies and pages:Number of copies . . . . 1 1-255First page to print . . 1 NumberLast page to print . . . \LAST Number, \LAST

Type of forms . . . . \STD______ Form type, \STD

Print this output next N Y=Yes, N=No

Save printer output . . . N Y=Yes, N=No

F1=Help F3=Exit F5=Refresh F12=Cancel

á ñFigure 7-4. Change Printer Output Display

3. Make your choices on the Change Printer Output display.

4. Press Enter .

The Work with Printer Output display appears again. The status of the printeroutput is now \Status changed.

What to Do if the Printer Output Is Not Already PrintingIf printer output is not already printing, you can make choices to do the following.

Assign Printer Output to a Printer: To assign this printer output to a printer, typethe printer’s name in the Printer to use field.

If you do not know which printer to use, press F4 to use the Select Printer displayto select a printer.

Change the Number of Copies to Print: To change the number of copies toprint, type the new number in the Number of copies field.

Specify the Page to Start On: To specify the page that this printer output shouldbegin printing on, type the page number in the First page to print field.

If you do not want the entire report to print, type the page number in the Last pageto print field. The First page to print and Last page to print fields can be usedtogether if part of your report was damaged by a paper jam or if you only want toprint part of a report.

7-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 79: Iseries

Managing Printer Output

Change the Form Type: To change the form type for a report, type the name ofthe form in the Type of forms field. This can be useful during application testing.For example, you may want to test programs, such as check or invoice printing onordinary paper.

Change when Printer Output Prints: To move printer output to the front of theline for printing, type a Y in the Print this output next field.

Your user profile controls the highest priority you can use when changing printeroutput. The printer output you select only prints next if your user profile has higherpriority than the printer output next in line.

Save Your Printer Output after It Prints: To save your printer output after it isprinted, type a Y in the Save printer output field. Normally, you would want printeroutput deleted to avoid cluttering up your system. However, for output that printson special forms, you may want to save your printer output. If you discover analignment problem after the output has printed, you can reprint without having torerun the program.

If the printer output you want to change is currently printing, you can change onlythe Number of copies and Save printer output fields. If you want to change theother fields, hold the printer output, make your change, and then release the printeroutput.

Assigning Printer Output to a PrinterTo assign printer output to a printer, on the Work with Printer Output display:

1. In the option field beside the printer output you want to assign to a printer, type

to select Start printing.

2. Press Enter .

3. Type the name of the printer you want to use in the Printer field.

If you do not know the name of the printer, press F4 to select from a list of allthe printers on the system on the Assign Output to a Printer display.

4. Press Enter .

If the printer you select is not started, the Start Printing display appears.

5. Type the name of the form type in the Type of forms on printer field.

6. Press Enter .

The Work with Printer Output display appears again.

7. Press F5.

The printer output that you assigned now appears under the name of theprinter.

Chapter 7. Printing with OS/400 7-9

Page 80: Iseries

Working with Printers

Working with PrintersTo work with printers, press F22 (Work with printers) on the Work with PrinterOutput display or use the following command:

WRKWTR ASTLVL(\BASIC)

Figure 7-5 shows the Work with Printers display.

à@ ðWork with Printers

User . . . . . : SMITH

Type options below, then press Enter. 1=Start 4=Stop 7=Message 8=Display output for printer 11=Restart

Opt Printer Form Type Status __ PRTð1 \STD Message waiting (use opt 7) __ PRTð2 CHECKS Stopped (use opt 1) __ PRTð3 INVOICES Printing __ PRTð4 \STD Held (use opt 6) __ PRTð5 \STD Printing

Figure 7-5. Work with Printers display

To see all printers on the system, press F6 (Include all printers).

Starting a PrinterTo start a printer, on the Work with Printers display:

1. In the option field beside the printer you want to start, type

1

to select Start.

2. Press Enter .

3. On the Start Printer display, use the Type of forms on printer field to specify thetype of forms you want to print.

4. Change the forms if necessary.

5. Press Enter .

The Work with Printers display appears. The printer’s status is \Attempting tostart. This means the system has started finding the printer output assignedto this printer.

6. Press F5.

The status usually changes to Message waiting which means there is a formsalignment message waiting.

7. In the Opt field, type

7

to select Message

8. Press Enter .

After you respond to this message, printing begins.

7-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 81: Iseries

Working with Printers

You can also start a printer on the Work with Printer Output display by using option10 (Start printing).

Stopping a PrinterTo stop a printer:

1. In the option field beside the printer you want to stop, type

4

to select Stop.

2. Press Enter .

3. On the Confirm Stop of Printer display, press Enter to confirm your choices, orpress F12 (Cancel) to return to the Work with Printers display without stoppingthe printer.

4. Press F5 to see which printers are stopped.

If you pressed Enter , the printer’s status is \Stopped.

Restarting a PrinterTo restart a printer, on the Work with Printers display:

1. In the option field beside the printer you want to start again, type

11

to select Restart.

2. Press Enter .

The Restart Printer display appears.

3. Type the page number of the first page you want to print in the Restart on pagefield.

4. Press Enter .

The printer’s status is changed to \Attempting to restart.

5. Press F5 to see if the printer has started.

A forms alignment message may appear when the printing restarts. Once yourespond to the message, printing starts on the page you requested.

You can also restart a printer on the Work with Printer Output display using option11 (Restart printing).

Answering Printer MessagesTo see a printer message and find out what action is needed, on the Work withPrinters display:

1. In the option field beside a printer that has a status of Message waiting, type

7

to select Message.

2. Press Enter .

Note: You can also answer printer messages on the Work with Printer Outputdisplay using option 7 (Messages).

Chapter 7. Printing with OS/400 7-11

Page 82: Iseries

Working with Printers

For more information about responding to printer messages, see “Responding toOS/400 Messages” on page 5-9.

7-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 83: Iseries

Working with Printers

Two messages that you may see frequently are:

� Load form type (CPA3394 or CPA3395)

The most common replies to the load form type message (CPA3394 orCPA3395) are G, B, or I.

� Verify alignment on printer (CPA4002)

The most common reply to the Verify alignment on printer message (CPA4002)is I.

Changing Forms on a PrinterTo change the form type for a printer, on the Work with Printers display:

1. In the option field beside the printer for which you want to change forms, type

4

to select Stop.

2. Press Enter .

The Confirm Stop of Printer display appears.

3. Press Enter .

The Work with Printer Output display appears again.

4. In the option field beside the printer for which you want to change forms, type

1

to select Start.

5. Press Enter

The Start Printer display appears.

6. Type the name of the form you want to use in the Type of forms on printerfield.

7. Press Enter .

Working with Spooled FilesThe Work with Spooled Files (WRKSPLF) command lets you display or print all (ora specified portion) of the spooled files that are currently on the system. Thiscommand is useful in locating lost printer output.

To use this command:

1. On an OS/400 command prompt, type

WRKSPLF

2. Press F4.

The Work with Spooled Files (WRKSPLF) display appears.

3. In the User field, type

\ALL

Or,

the name of the user whose spooled files you want to work with.

Chapter 7. Printing with OS/400 7-13

Page 84: Iseries

Working with Printers

4. Press Enter .

The Work with Printer Output display appears.

From the Work with Printer Output display you can:

� Change the attributes of a spooled file

� Hold a spooled file

� Delete a spooled file

� Display the contents of a spooled file

� Release a held spooled file

� Answer a printer message

� Work with printing status

� Start printing

� Restart printing

Working with All Output QueuesThe Work with Output Queue (WRKOUTQ) CL command shows you the overallstatus of the output queues or the detailed status of a specific output queue.

From the Work with All Output Queues (WRKOUTQ) display, you can change, hold,delete, and release spooled files. The change option can be used for movingoutput from one queue to another.

To use this command:

1. On an OS/400 command prompt, type

WRKOUTQ

2. Press F4.

The Work with Output Queue (WRKOUTQ) display appears.

3. In the Output queue field, type

\ALL

Or,

the name of a specific output queue.

4. Press Enter .

The Work with All Output Queues display appears.

From the Work with All Output Queues display, you can do the following:

� Change the output description

� Hold an output queue

� Delete an output queue

� Work with spooled files on an output queue

� Release a held output queue

� Display the description of an output queue

7-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 85: Iseries

Working with Printers

� Work with printers started to an output queue

� Clear all the spooled files from an output queue

Comparing System/36 Print Commands to OS/400 Print CommandsThe following list shows the System/36 commands that are used for controllingprinters and output with the AS/400 command that is used to do the same function.

System/36 Command AS/400 Equivalent

ASSIGN (A P) Assigns a printer ID for the new System Printer. Thereis no AS/400 equivalent command.

BALPRINT You can balance printer output on AS/400 by using theStart Printer Writer (STRPRTWTR) command to startanother printer writer to the same output queue.

CANCEL (C P) Option 4 (Delete) on either the Work with All OutputQueues display or the Work with Printer Output display.Use the WRKOUTQ command or the WRKSPLFcommand, respectively, to go to these displays.

You can also use the Clear Output Queue (CLROUTQ)command to remove spooled files from a specifiedoutput queue.

CHANGE (G) Option 2 (Change) on either the Work with All OutputQueues display or the Work with Printer Output display.Use the WRKOUTQ command or the WRKSPLFcommand, respectively, to go to these displays.

HOLD (H P) Option 3 (Hold) on either the Work with All OutputQueues display or the Work with Printer Output display.Use the WRKOUTQ command or the WRKSPLFcommand, respectively, to go to these displays.

RELEASE (L P) Option 6 (Release) on either the Work with All OutputQueues display or the Work with Printer Output display.Use the WRKOUTQ command or the WRKSPLFcommand, respectively, to go to these displays.

RESTART (T P) The Restart printing field on the Change Spooled FileAttributes display lets you specify which page to restartprinting the spooled file. This display lets you changemany attributes of the spooled file, such as the numberof copies to print, the forms types, and print sequence.Use the CHGSPLFA command to go to the ChangeSpooled File Attributes display.

START (S P) Option 1 (Start) on the Work with All Printers display.Use the WRKWTR command to go to this display.

STATUS PRT (D P) Same as the WRKOUTQ or WRKSPLF command.

STATUS WRT (D WRT) Same as the WRKWTR command.

STATUSF PRT (DF P) Same as the WRKOUTQ or WRKSPLF command.

STOP (P P) Option 4 (End) on the Work with All Printers display.Use the WRKWTR command to go to this display.

Chapter 7. Printing with OS/400 7-15

Page 86: Iseries

Working with Printers

TEXTPRTQ Same as the Work with Documents to be Printed(WRKDOCPRTQ) command.

For more information on working with printer output, refer to the System Operationbook, SC41-4203. The Printer Device Programming book, SC41-4713, also con-tains information on printing on the AS/400 system and examples of how to findyour printer output.

7-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 87: Iseries

OS/400 Subsystems

Chapter 8. Working with OS/400 Subsystems

DefinitionsJust as the word master has more than one meaning, subsystem has more thanone meaning. Subsystem means something quite different to OS/400 than it doesto SSP.

OS/400 SubsystemsFor OS/400, a subsystem is an operating environment where the system coordi-nates processing of jobs and resources for the jobs. There is a default startupprogram that is supplied by IBM. If you use the startup program and you use theCHGSYSVAL command to set the system value QCTLSBSD to:

� QCTL in library QSYS

The subsystems that start when you IPL include: QCTL, QSPL, QINTER,QBATCH, QCMN, and QSERVER.

� QBASE in library QSYS

The subsystems that start when you IPL are: QBASE and QSPL

Once your system is successfully powered on, you may need to start additionalsubsystems to make your system ready to use if:

� You created a subsystem which is not automatically started, such as a sub-system which runs only at night.

� You ended all but the controlling subsystem to bring your system to a restrictedstate to back it up.

All user jobs are run in a subsystem. A subsystem creates a suitable environmentfor a job to do its work. The AS/400 system can contain one or many subsystems.These can be created or deleted by those who have proper authority.

As the number of different types of jobs increases in the system, more subsystemscan be defined to manage those jobs. All interactive processing can occur in onesubsystem, all batch processing in another, system operator jobs in a third, and soon.

This makes it easier to control the different jobs in the system because subsystemscan be started and ended individually.

SSP SubsystemsFor SSP, a subsystem is the part of communications that handles the require-ments of the remote system. It isolates most system-dependent considerationsfrom the application program.

The only SSP subsystems are:

� SSP-ICF subsystems

� APPC subsystems

Copyright IBM Corp. 1995, 1996 8-1

Page 88: Iseries

OS/400 Subsystems

The SSP-ICF subsystem is required for running ICF sessions.

The APPC subsystem allows the System/36 to communicate with other systemsthat have compatible support.

Working with a SubsystemThe Work with Subsystem (WRKSBS) command allows you to work with eachactive subsystem in the system. Also, if you select one of the subsystems shownon the display, you can see additional information on all the jobs that are active inthat subsystem.

To use the WRKSBS command:

1. On an OS/400 command line, type

WRKSBS

2. Press F4.

The Work with Subsystems (WRKSBS) display appears.

3. If you want all the output displayed, press Enter .

4. If you want the output printed with the job's spooled output:

a. In the Output field, type

\PRINT

b. Press Enter .

If you selected to display the subsystems, the Work with Subsystems displayappears. From the Work with Subsystems display you can do the following:

� End a subsystem

� Display a subsystem description

� Work with subsystem jobs

Working with Subsystem DescriptionsThe Work with Subsystem Description (WRKSBSD) command allows you to workwith a specific subsystem or all subsystems currently on the system.

To use the WRKSBSD command:

1. On an OS/400 command line, type

WRKSBSD

2. Press F4.

The Work with Subsystem Description display appears.

3. In the Subsystem description field, type

\ALL

Or,

the name of a specific subsystem.

4. Press Enter .

The Work with Subsystem Description display appears.

8-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 89: Iseries

OS/400 Subsystems

From the Work with Subsystem Description display you can do the following:

� Create a new subsystem description.

� Change a subsystem description.

� Delete a subsystem description.

� Display a subsystem description.

� Work with subsystem jobs.

� Start a subsystem.

� End a subsystem.

Chapter 8. Working with OS/400 Subsystems 8-3

Page 90: Iseries

OS/400 Subsystems

8-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 91: Iseries

OS/400 System Security

Chapter 9. OS/400 System Security

This chapter is an overview of security on the OS/400 operating system.

Levels of SecurityThe system administrator can use a combination of system values, user profileparameters, and resource security to protect the information on your computer. Forexample, a system value called the security level determines how much security isenforced on your system.

The security level for your system is the same for all users on the system. Whenthe system is set up, your system Security Officer sets the security level as one ofthe following:

10 This is the lowest level of security. When the system security is set atlevel 10 and you sign on, the system checks for a user profile. If thesystem does not find a user profile, it creates one.

20 At level 20, a user profile must already exist. The system verifies thatthe user ID and password entered match that of the existing profile.Users who can sign on can access any object.

30 At security level 30, the user ID and password are checked. In addition,a user cannot work with objects (files or libraries) without authorization.

40 All security considerations for level 30 also apply to level 40. However,at level 40, operating system integrity is ensured.

50 This is the highest level of security. All security considerations for level40 also apply to level 50. In addition, level 50 is designed to meet theC2 security requirements defined by the United States Department ofDefense.

Changing the Security LevelThe security level of the system is set in the QSECURITY system value. Tochange the value, do as follows:

1. Type

CHGSYSVAL QSECURITY 'xx'

where xx is the security level that you want to use.

Note: The single quotes are required.

2. Press Enter .

The security administrator can use system values and parameters in your userprofile to enforce your company’s security policy, such as:

How often you must change your password.What the system does if you forget to sign off.Whether you are allowed to enter commands.Whether you can manage job queues and output queues.

Copyright IBM Corp. 1995, 1996 9-1

Page 92: Iseries

OS/400 System Security

Changing PasswordsTo change your password, do the following:

1. Type

GO ASSIST

2. Press Enter .

The following display appears.

à@ ð ASSIST AS/4ðð Operational Assistant (TM) Menu System: RCHASLðG To select one of the following, type its number below and press Enter:

1. Work with printer output2. Work with jobs3. Work with messages4. Send messages5. Change your password

1ð. Manage your system, users, and devices11. Customize your system, users, and devices

75. Information and problem handling

8ð. Temporary sign-off

Type a menu option below 5

F1=Help F3=Exit F9=Command line F12=Cancel

á ñ 3. Type

5

to select the Change your password option.

4. Press Enter .

The Change Password display appears.

9-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 93: Iseries

OS/400 System Security

à@ ð Change Password

Password last changed . . . . . . . . . . : 1ð/16/92

Type choices, press Enter.

Current password . . . . . . . . . . . .

New password . . . . . . . . . . . . . .

New password (to verify) . . . . . . . .

F3=Exit F12=Cancel

á ñ5. Fill in the choices with your current password and what you want your new

password to be. You need to type your new password twice: once for the Newpassword field and once in the New password (to verify) field.

6. Press Enter .

For more information on OS/400 security, see the Security – Basic book,SC41-4301 and the Security – Reference book, SC41-4302.

Chapter 9. OS/400 System Security 9-3

Page 94: Iseries

OS/400 System Security

9-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 95: Iseries

Working with Batch Jobs

Chapter 10. Controlling OS/400 Jobs

Note: The displays shown in this chapter are those you would see if you wererunning at a basic assistance level. You would see different displays atother assistance levels.

The key element used by the AS/400 system to organize and manage work is thejob . A job usually includes all necessary programs, files, connections andinstructions to the Operating System/400 licensed program.

A job can be one very short and simple task such as printing a report. It can alsobe a series of tasks, such as:

� Calculating total sales by product� Calculating total sales by area� Calculating total sales by sales person� Printing sales reports

Figure 10-1 provides an overview of how jobs are run.

BatchJob

Writer Printer

SBMJOB

Sign On Job Queue Subsystem Output Queue

InteractiveJob

BatchJob

Writer Printer

SBMJOB

Sign On Job Queue Subsystem Output Queue

InteractiveJob

RSLP109-0

Figure 10-1. Overview of Job Processing

There are two basic types of jobs: batch jobs and interactive jobs. “SubmittingBatch Jobs” gives you information about how to display, end, hold, release andschedule batch jobs as well as work with job queues. “Working with Signed-OnUsers” on page 10-12 gives information on how to display and end interactive jobs.Also included in this chapter is information on how to display detailed informationabout your job, changing how a job is run, and working with job logs.

Additional Reading: For more detailed information about jobs, job descriptions,job logs, job queues, output queues, and how to manage any of these, see theWork Management book, SC41-4306.

Submitting Batch JobsA batch job does not require constant interaction with the user. Once you havesubmitted a batch job, you are free to do other work at your work station withoutwaiting for the job to run. Two examples of jobs that are commonly run in batchare printing reports and doing month-end data summaries.

Copyright IBM Corp. 1995, 1996 10-1

Page 96: Iseries

Working with Batch Jobs

When you submit a batch job, it is placed on a job queue. Then, the subsystem towhich the job queue is assigned takes the jobs off the job queue in order and runsthem. For more information, see Chapter 8, “Working with OS/400 Subsystems”on page 8-1.

You can submit a batch job to run immediately or to run at a scheduled date andtime.

Submitting a Batch Job to Run ImmediatelyTo submit a job that runs immediately:

1. Type

SBMJOB

2. Press F4.

The Submit Job (SBMJOB) display appears.

3. On the Submit Job (SBMJOB) display, in the Command to run field, type thecommand you want to run in a batch job.

� If the job you want to submit is a program, type call and the name of theprogram; for example, CALL PAYROLL. If the job you want to run is aREXX procedure, use the Start REXX Procedure (STRREXPRC)command.

� If the job you want to run is a CL command, type the name of thecommand. You can use prompting to assist you with the parameters forthe command. Type the name of the command and then press F4 whileyour cursor is positioned in the Command to run field. If you want, you canalso change the value already specified for any of the other entry fields.

� Press Enter . The job is submitted. A message is shown at the bottom ofyour display that tells you the qualified job name that the system hasassigned to your job and the name of the job queue to which it has beensubmitted.

The qualified job name is used by the system and by system users to locate jobs.It consists of three parts:

Job number Assigned by the system to make sure every qualified job name isunique.

User ID The user profile under which the job is running, usually the profile ofthe submitter.

Job name A short descriptive title of the job, such as PRTINV for “printinvoices.”

Scheduling a Batch Job to Run LaterTo schedule a batch job using the Submit Job (SBMJOB) command, use theSchedule date (SCDDATE) and Schedule time (SCDTIME) parameters.

Schedule date (SCDDATE) parameter: Specifies the day the job is released onthe job queue. The possible values are:

*CURRENT Today’s date

*MONTHSTR First day of the month

10-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 97: Iseries

Working with Batch Jobs

*MONTHEND Last day of the month

*MON – *SUN The next occurrence of the specified day of the week

01/26/96 A specific day (job date format is defined in the system valueQDATFMT)

Schedule time (SCDTIME) parameter: Specifies the time on the scheduled datewhen the job will be marked released on the job queue. The actual time may varydepending on the activity involved in releasing the job and the load on the systemwhen the job is scheduled to be started.

*CURRENT The current time

17:00:00 A specific time (job time separator may vary)

Note: If the schedule date is the current date and the schedule time is the currenttime the job will be placed on the job queue with a status of \Released.

At the time indicated, the job’s status changes from \Scheduled to \Released and itis processed as a normal job on the job queue. If a scheduled job is held on thejob queue, the job’s status changes from \Scheduled to \Held at the time indicated.As with other batch jobs, in order to run, the job must:

� Be in a job queue allocated to an active subsystem

� Not be held

Note: Additionally, the maximum number of jobs must not already be active in thesubsystem.

Changing a Job Schedule to Run at a Different Date or TimeTo change the date and time for a scheduled job or to change a non-scheduled jobto be scheduled, use the Schedule date (SCDDATE) and Schedule time(SCDTIME) parameters on the Change Job (CHGJOB) command.

Scheduling a Job Using Job Schedule EntriesA job schedule entry contains the information needed to submit a batch job onceor at regular intervals. The Work with Job Schedule Entries (WRKJOBSCDE)

| command allows you to perform time-dependent scheduling for OS/400 batch jobs.You schedule the date and time at which a job is submitted to the job queue.

When you add a job schedule entry, a job will be submitted at the specified time.When you remove a job schedule entry, the job will not be submitted. You canalso change the information in the job schedule entries, or hold and release a jobschedule entry. Each entry has a unique job name and entry number.

This section contains an overview of the job scheduling function. See the WorkManagement book, SC41-4306, for complete and detailed information about the jobscheduling function and working with the job schedule entries.

Figure 10-2 on page 10-4 shows the Work with Job Schedule Entries display.

Chapter 10. Controlling OS/400 Jobs 10-3

Page 98: Iseries

Working with Batch Jobs

à@ ðWork with Job Schedule Entries RCH3836ð

ð3/25/91 ð8:15:ð4

Type options, press Enter. 2=Change 3=Hold 4=Remove 5=Display details 6=Release

8=Work with last submission 1ð=Submit immediately

Next -----Schedule------ Recovery SubmitOpt Job Status Date Time Frequency Action Date __ ____________ DAILYJOB SCD USER DEF 17:ðð:ðð \WEEKLY \NOSBM ð3/25/91__ PRTREPORT HLD ð3/28/91 23:ðð:ðð \ONCE \SBMRLS ð3/28/91

Bottom Parameters or command ===> _________________________________________________________________________F3=Exit F4=Prompt F5=Refresh F6=Add F9=Retrieve F11=Display job queue data F12=Cancel F17=Top F18=Bottom

á ñ

Figure 10-2. Work with Job Schedule Entries Display

Adding a Job Schedule EntryTo schedule a job once, weekly, or monthly, use F6 (Add) on the Work with JobSchedule Entries display, or use the Add Job Schedule Entry (ADDJOBSCDE)command. The job is submitted at the specified time by the Submit Job (SBMJOB)command. For the job to start running, make sure:

� The job queue is allocated to an active subsystem.� The job queue is not held.� Maximum jobs are not already active.

Saving a Job Schedule EntryIf you want to prevent the entry from being automatically deleted after a job is sub-mitted from a job schedule entry that is used only once to submit a job, type \yesfor the Save (SAVE) parameter on the Add Job Schedule Entry (ADDJOBSCDE)command.

Removing a Job Schedule EntryTo remove a job schedule entry so that it is not used to submit a job, use option 4(Remove) on the Work with Job Schedule Entries display or use the Remove JobSchedule Entry (RMVJOBSCDE) command. If a job from this entry has alreadybeen submitted to the job queue, you can end it using the Work with User Jobs(WRKUSRJOB) command or the Work with Submitted Jobs (WRKSBMJOB)command.

10-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 99: Iseries

Working with Batch Jobs

Changing a Job Schedule EntryTo change a job schedule entry, use option 2 (Change) on the Work with JobSchedule Entries display or use the Change Job Schedule Entry (CHGJOBSCDE)command. This changes the entry in the job schedule but does not affect any jobsalready submitted for this entry.

Holding and Releasing a Job Schedule EntryTo hold a job schedule entry, use option 3 (Hold) on the Work with Job ScheduleEntries display or use the Hold Job Schedule Entry (HLDJOBSCDE) command.When the time occurs for the job to be submitted, the entry is ignored.

To release a job schedule entry, use option 6 (Release) on the Work with JobSchedule Entries display or use the Release Job Schedule Entry (RLSJOBSCDE)command. If the time has not passed, the job is submitted as scheduled. If thescheduled time has passed, a message is displayed indicating that jobs weremissed.

Scheduling a Batch Job to Start an AS/400 Advanced 36MachineBecause the unattended power-on functions for both the TIMERSET OCL state-ment and the SSP TIMER procedure are not valid when OS/400 is present on thesystem, this type of function needs to be performed by OS/400. To schedule abatch job to start an AS/400 Advanced 36 machine, use the Submit Job (SBMJOB)command along with the Schedule Date (SCDDATE) and Schedule Time(SCDTIME) parameters. On the Submit Job display, in the Command to Run field,type the STRM36 command with the appropriate parameters. For information onstarting an AS/400 Advanced 36 machine in other ways, see Chapter 15, “Startingan AS/400 Advanced 36 Machine.”

Working with Batch JobsYou can hold, release, end, and check the status of batch jobs on the Work withJobs display. To find the Work with Jobs display:

1. On any OS/400 command line, type

go assist

2. Press Enter to display the Operational Assistant menu.

3. In the Opt field, type

2

to select Work with jobs.

4. Press Enter .

The Work with Jobs display appears.

Another way to find the Work with Jobs display is to do as follows:

1. On an OS/400 command line, type

WRKUSRJOB JOBTYPE(\BATCH) ASTLVL(\BASIC)

2. Press Enter .

Figure 10-3 on page 10-6 shows the Work with Jobs display.

Chapter 10. Controlling OS/400 Jobs 10-5

Page 100: Iseries

Working with Batch Jobs

à@ ðWork with Jobs

System: SYSTEMð1 User . . . . . . SMITH_____ Name, \ALL, F4 for list

Type options below, then press Enter. 3=Hold 4=Delete (End) 6=Release 7=Display message

8=Work with printer output

Job Queue/ Opt Job Status QBATCH_ BONUS2 Message waiting (use opt 7)

_ BONUS Running_ NOBONUS Running job held (use opt 6)

_ PAYCODE Ending_ PAYROLL Waiting to run (2 of 4)_ OVERTIME Scheduled 11/3ð/91 12:ðð:ðð_ TIMECARD Held (use opt 6)_ HOLIDAY Held (use opt 6)

BottomF1=Help F3=Exit F5=Refresh F9=Command line F11=Display dates/times F12=Cancel F14=Select other jobs F22=Work with job queues F24=More keys

á ñ

Figure 10-3. Work with Jobs Display for the Status of a Single User

Note: Jobs resulting from job schedule entries do not appear on this display untilthe time they are scheduled to be submitted.

Displaying Batch Jobs of Other UsersYou can select whose jobs to view on the Work with Jobs display.

Security Consideration

To view and manage the jobs of other users, you must have job control(*JOBCTL) authority in your user profile.

If you want to see all of the jobs for a user, type the user ID of the person whosejobs you want to see in the User field and press Enter .

The Work with Jobs display appears for the user you selected.

Displaying All Batch JobsTo see all batch jobs, on the Work with Jobs display, type *all in the User field andpress Enter . You can enter a generic name, for example A\ shows you all of thejobs for all users whose names start with an A. You can also press F14 to go tothe Select Other Jobs display where you can type a generic name.

The Work with Jobs display appears with a new column called User.

Figure 10-4 on page 10-7 shows all of the batch jobs on the system.

10-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 101: Iseries

Working with Batch Jobs

à@ ðWork with Jobs

System: SYSTEMð1 User . . . . . . \ALL______ Name, \ALL, F4 for list

Type options below, then press Enter. 3=Hold 4=Delete (End) 6=Release 7=Display message

8=Work with printer output

Job Queue/ Opt Job User Status QBATCH_ BONUS SMITH Message waiting (use opt 7)

_ MYJOB HARRY Running _ BONUS2 SHEMP Ending QS36EVOKE_ PAYROLL DUNNJ2 Waiting to run (1 of 4)_ INVOICES MAHONEY Waiting to run (2 of 4)_ INVOICES2 MONTEY Waiting to run (3 of 4)_ INVOICES3 GEORGE Scheduled 12/15/91 22:ðð:ðð

Bottom F1=Help F3=Exit F5=Refresh F9=Command line F11=Display dates/times F12=Cancel F14=Select other jobs F22=Work with job queues F24=More keys

á ñ

Figure 10-4. Work with Jobs Display for the Status of Multiple Users

The jobs on this display are sorted by job queue. Within each job queue, the jobsare grouped by status.

Performance Note

Whenever possible, select a user ID instead of typing *all in the User field ofthe Work with Jobs display. If there are many jobs on the system, the perfor-mance of other jobs is affected when you use *ALL.

Displaying Batch Jobs by StatusTo find jobs based on status:

1. On the Work with Jobs display, press F14 (Select other jobs). Figure 10-5 onpage 10-8 shows the Select Other Jobs window.

Chapter 10. Controlling OS/400 Jobs 10-7

Page 102: Iseries

Working with Batch Jobs

à@ ðWork with Jobs

.............................................................................. : Select Other Jobs : : : : Select the following jobs for the list. : : : : Type choices below, then press Enter. : : : : User . . . . . . . . . . . . . \ALL______ Name, \ALL, F4 for list : : Status: : : Message waiting . . . . . . Y Y=Yes, N=No : : Running . . . . . . . . . . Y Y=Yes, N=No : : Running job held . . . . . . Y Y=Yes, N=No : : Ending . . . . . . . . . . . Y Y=Yes, N=No : : Waiting to run/Scheduled . . Y Y=Yes, N=No : : Held . . . . . . . . . . . . Y Y=Yes, N=No : : Job queue held . . . . . . . Y Y=Yes, N=No : : Queue not assigned . . . . . Y Y=Yes, N=No : : Printer output . . . . . . . N Y=Yes, N=No : : : : :: F1=Help F5=Refresh F12=Cancel : : : :............................................................................:

á ñFigure 10-5. Select Other Jobs Window

2. Leave the Y (Yes) next to each status whose jobs you want included on yourdisplay in the Select Other Jobs window.

3. Type an N (No) next to each status you do not want included.

4. Press Enter .

The Work with Jobs display appears again, including only those jobs that havethe statuses you selected.

You can also see when jobs were started by pressing F11 (Display dates/times) onthe Work with Jobs display. To return to the status version of this display, pressF11 (Display statuses).

Holding a Batch JobTo hold a batch job, on the Work with Jobs display:

1. Select option 3 (Hold) for the job or jobs you want held.

The status of the job changes to \Held.

2. Press F5.

The status of the job changes to either Running job held (use Opt 6) or Held(use Opt 6).

Holding Printer Output from a Batch Job: Once a job has a status of Printeroutput, it has finished running. Any reports it has created are waiting to print orare printing. If you do not want these reports to print, use option 8 (Work withprinter output) on the Work with Jobs display. On the Work with Job Printer Outputdisplay, use option 3 (Hold).

Note: Printer output is not included unless you type a Y in the Printer output fieldin the Select Other Jobs window.

10-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 103: Iseries

Working with Job Queues

Releasing a Batch JobTo release a batch job, on the Work with Jobs display:

1. Select option 6 (Release) for the job or jobs you want released.

The status of the job changes to \Released.

2. Press F5.

The status of the job changes to either Running, Waiting to run, or Scheduled.

Ending a Batch JobAttention: Use caution when ending a job. Ending a job may interrupt job or fileupdates.

To end a batch job, on the Work with Jobs display:

1. Select option 4 (Delete (End)) for the job or jobs you want ended.

The Confirm Delete (End) of Jobs display appears.

2. Press Enter to end the jobs.

Note: You would press F12 (Cancel) to keep the jobs.

The Work with Jobs display appears. The job you ended only appears on thedisplay if it has a status of Printer output. This status does not appear unlessY is specified in the Printer output field on the Select Other Jobs display.

Deleting Batch Job Printer Output: Once a job has a status of Printer output,it has finished running. Any reports that it created are either printing or waiting toprint. To cancel a report, use option 8 (Work with printer output). On the Workwith Job Printer Output display, select option 4 (Delete) for the printer output youwant to delete.

Working with Job QueuesBefore a batch job is run, it waits in line on the job queue of the subsystem that willrun it. The job can be waiting because other jobs are in front of it on the queue,the job is held, the job queue is held, or the job queue is not allocated to an activesubsystem. A waiting job also has a priority (its place in the queue).

Figure 10-6 shows an overview of a subsystem processing jobs from a job queue.

┌───────────┐ ┌──────────┐│ Job 1 ├──────5│ Run Job 1│

│ Job 2 │ └──────────┘ │ Job 3 │ Subsystem │ Job 4 │ │ Job 5 │ SBMJOB──────5│ Job 6 │ └───────────┘ Job QueueFigure 10-6. Overview of Job Queue Processing

Chapter 10. Controlling OS/400 Jobs 10-9

Page 104: Iseries

Working with Job Queues

Looking at Job QueuesIf you submitted batch jobs, the Work with Jobs display gives you the status ofthose jobs, including where they are on the job queue if they are waiting to run.

However, you may want to know which jobs are scheduled to run ahead of yourjob. Or, as the system operator, you may want to monitor the activity on the jobqueues. You can see this information on the Work with Job Queues display. Tofind this display:

1. On the Operational Assistant (ASSIST) menu, select option 2 (Work with jobs).

2. On the Work with Jobs display, press F22 (Work with job queues).

Figure 10-7 shows the Work with Job Queues display.

à@ ðWork with Job Queues

System: SYSTEMð1 User . . . . . : \ALL

Type options below, then press Enter. 3=Hold 6=Release

Job Queue/ Opt Job Status_ HILGEREL Job queue not assigned_ MHJOBQ Job queue not assigned_ NORBERT Held (use Opt 6)

_ NORBERT2 Ready_ NOBELL Job queue not assigned

_ QBATCH Ready _ QCTL Ready _ QSNADS Ready _ QXFPCS Ready_ SCHMALL Job queue not assigned_ TLMJOBQ Job queue not assigned

More...F1=Help F3=Exit F5=Refresh F11=Display libraries/descriptions F12=Cancel F14=Include jobs on job queue

á ñFigure 10-7. Work with Job Queues Display - Summary

3. To see the individual jobs on the queues, press F14 (Include jobs on jobqueue).

The Work with Job Queues display appears again with the jobs included.

4. From either of these displays, press F11 (Display libraries/descriptions) to seeanother version that shows descriptive information about the job queues.

Working with an Empty Job Queue and Displaying Job Priority: To view anempty job queue or job priority within the queue, use the Work with Job Queue(WRKJOBQ) command to display the Work with All Job Queues display.

On the Work with All Job Queues display, you can hold or release any job queue.This holds all jobs already on the job queue as well as any jobs that are submittedto that job queue.

10-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 105: Iseries

Working with Job Queues

To find priorities of jobs on a job queue use option 5 (Work with). When you pressEnter , the Work with Job Queue display is shown for the queue you selected. ThePriority column contains the priority of each job in the job queue.

Holding a Job QueueTo hold a job queue, on the Work with Job Queues display:

1. Use option 3 (Hold) for the job queue or queues you want to hold.

The status of the queue is changed to \Job queue held.

2. Press F5.

The status of the queue is changed to Held.

Note: The Work with Job Queues display shows only those job queues whichhave waiting or running jobs. If no jobs are associated with a job queue,the Work with Job Queues display is empty. An empty job queue is heldwhen you know that the job queue is empty and choose to hold it so youcan stop all future jobs from coming into the system.

Releasing a Job QueueTo release a job queue, on the Work with Job Queues display:

1. Use option 6 (Release) for the job queue or queues you want to release.

The status of the job queue changes to \Job queue released.

2. Press F5.

The status changes to Ready.

Working with Unassigned Job QueuesJobs waiting on the job queue do not run if the job queue is not assigned to anactive subsystem. To run these jobs, do one of the following:

� Move the jobs on the unassigned queue to a different job queue:

1. On either the Work with Jobs or the Work with Job Queues display, find thejob queues that are ready to run jobs.

2. If you need additional information about which job queues are assigned towhich subsystems, use the Work with Job Queues (WRKJOBQ) command.

3. On the Work with All Job Queues display, look at the Subsystem column totell which job queues are assigned to active subsystems.

4. Move the jobs between job queues using the Change Job (CHGJOB)command. See “Moving a Job to a Different Job Queue” on page 10-17for instructions on how to do this.

� Start the subsystem to which the job queue is assigned using the STRSBScommand. See Chapter 2 of the System Startup and Problem Handling book,SC41-4206, for more information on starting subsystems.

Note: To determine which subsystem uses the job queue, display the sub-system description. See Chapter 2 of the System Startup and ProblemHandling book, SC41-4206 for information on how to display a sub-system description.

Chapter 10. Controlling OS/400 Jobs 10-11

Page 106: Iseries

Working with Signed-On Users

On the Display Subsystem Description display, select option 6 (Jobqueue entries). The Display Job Queue Entries display is shown withall of the job queues assigned to the subsystem.

� Assign the job queue to a subsystem. If you have determined that none of thesubsystems have a job queue entry for this job queue, you can assign it to asubsystem using the Add Job Queue Entry (ADDJOBQE) command.

Working with Signed-On UsersWhen you are signed on the system, you type one request at a time (such asselecting an option or typing a command). The system responds to each typedrequest after Enter is pressed.

This session, sometimes called an interactive job , begins when you sign onto aworkstation and ends when you sign off. During the session, your interaction withthe system is similar to a conversation. The AS/400 system links together all of thetasks you do from the time you sign on until you sign off. This makes it easier foryou to manage your work environment, find your output, and keep track of whatyou have done.

Displaying Signed-On UsersTo display all users signed on the system, select option 12 (Work with signed-onusers) on the Manage Your System, Users, and Devices (MANAGESYS) displaywhich can be reached using option 10 on the ASSIST menu.

You can also use the Work with User Jobs command as follows:

1. On an OS/400 command line, type

WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\INTERACT) ASTLVL(\BASIC)

2. Press Enter .

Creating a Customized Work with User Jobs CommandIf you do not want to type the Work with User Jobs (WRKUSRJOB) command withall the parameters to get to the Work with Signed-On Users display, you can createyour own copy of the Work with User Jobs (WRKUSRJOB) command in yourlibrary, changing the defaults to show the Work with Signed-On Users display. Todo this:

1. On an OS/400 command line, type

CRTDUPOBJ

2. Press F4.

3. Type the following values for the parameters listed and press Enter :

From object (OBJ) WRKUSRJOB

From library (FROMLIB) QSYS

Object type (OBJTYPE) *CMD

To library (TOLIB) Your library name

New object (NEWOBJ) Name of the new command (for example,WRKSGNON)

10-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 107: Iseries

Working with Signed-On Users

4. On an OS/400 command line, type

CHGCMDDFT

5. Press F4.

6. Type the following values for the parameters and press Enter :

Command (CMD) WRKSGNON (or the name of the newcommand)

Library Your library name

New default (NEWDFT) USER(*ALL) STATUS(*ACTIVE)JOBTYPE(*INTERACT) ASTLVL(*BASIC)

Figure 10-8 shows the Work with Signed-On Users display.

à@ ðWork with Signed-On Users

System: SYSTEMð1 Find user . . . . . . . . . . . . . _________ Starting characters

Type options below, then press Enter. 3=Send message 4=Sign off 5=Display details 7=Display message

Display Opt User Station Activity _ BRUNS BRUNSS3 ASSIST menu _ EVERLY EVERLYS2 INVENTORY program _ GOETZ QPADEVððð4 Command entry_ JACK JACKS4 Message waiting (use Opt 7)

_ SMITH SMITHS1 WRKUSRJOB command _ TELLY QPADEVððð8 MAIN menu _ TUBER QPADEVððð2 WRKSPLF command

BottomF1=Help F3=Exit F5=Refresh F1ð=Send message to all F11=Display additional information F13=Sort list F24=More keys

á ñ

Figure 10-8. Work with Signed-On Users Display

Signing Users Off the SystemWhen you sign a user off the system, you interrupt the user's interactive job in themiddle of processing and remove the job from the system.

Attention: Use caution when signing a user off the system. Ending a user’s inter-active job may interrupt job or file updates.

To sign a user off the system:

1. Use option 4 (Sign off), on the Work with Signed-On Users display, for the useror users you want to sign off the system.

2. Press Enter .

On the Confirm Sign Off display, press Enter to sign users off the system orF12 (Cancel) to leave the users signed on to the system.

Chapter 10. Controlling OS/400 Jobs 10-13

Page 108: Iseries

Displaying Job Information

The Work with Signed-On Users display is shown without the users you signedoff the system.

Finding Signed-On Users and Sorting the User ListTo find a specific user signed on to the system, type the first few characters of theuser's name in the Find user field and press Enter . The list is positioned at thefirst user matching the characters you typed.

The list is initially sorted by user name and shows the activities of each user. Tosort the list by user name or display station name, press F13 (Sort list). To selectother users and display stations, use F14 (Select other users and display stations).Users who are temporarily signed off are not included in this list. To include them,type a Y in the Include temporarily signed-off users and suspended group jobs fieldon the Select Other Users and Display Stations window.

Finding Additional Information about Signed-On UsersThere are two ways you can display additional information about the users currentlysigned on to the system. For a single user listed on the Work with Signed-OnUsers display, select option 5 (Display details). This shows the Display Detailsdisplay, which gives the user, display station description, and the current activity ofthe user.

To get additional information for all users shown on the Work with Signed-On Usersdisplay, press F11 (Display additional information). This displays a pop-up windowwhere you can select to see activities, workstation descriptions, or user descriptionsin the third column of the display.

For additional information about all aspects of every job on the system, see “Dis-playing Detailed Job Information.”

Sending Messages to Signed-On UsersFrom the Work with Signed-On Users display, you can send messages to one,several, or all users signed on the system.

� To send a message to one or several signed-on users, use option 3 for eachuser. To send a message to all signed-on users, press F10 (Send message toall).

� Type your message in the Message text field on the Send a Message displayand press F10 (Send).

Note: The Send a Message display is set up to interrupt the users signed onthe system. If you do not want to interrupt them, change the value inthe Interrupt user field to an N.

Displaying Detailed Job InformationThe system keeps a comprehensive record of all aspects of every job. This infor-mation is available to you through the Work with Job menu.

To find this information for your own interactive job, use the Work with Job(WRKJOB) command.

To display the Work with Job menu for any other job on the system:

10-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 109: Iseries

Displaying Job Information

1. Use the Work with User Jobs (WRKUSRJOB) command selecting all jobs (orthe job name if you know it) with the intermediate assistance level.

2. Use option 5 (Work with) for the job you want more information about on theWork with User Jobs menu.

The Work with Job menu for the job you selected appears.

To help you monitor jobs and find out why problems with jobs occur, use theDisplay Job (DSPJOB) command or the Work with Job menu. You can do thesame tasks with the DSPJOB or WRKJOB commands except:

� The WRKJOB menu has a command line where you can change the job.

� DSPJOB only allows you to display the JOB.

Displaying Job Status AttributesTo display the identifying characteristics and the status of the job, select option 1(Display job status attributes) on the Work with Jobs display. For example, you cansee when the job entered the system and when it started running. For a batch job,this information can help you determine whether or not the job has been runningtoo long and might be in a loop.

Displaying Job Definition AttributesTo display the current job definition attributes, select option 2 (Display job definitionattributes) on the Work with Jobs display. This display provides information suchas job queue assignment and priority, output queue assignment and priority,message queue assignment, and logging level.

Many of these definition attributes can be changed using the Change Job(CHGJOB) command or F9 (Change job) on the Display Job Definition Attributesdisplay. See “Changing How a Job Is Run” on page 10-16 for information on howto change a job.

Displaying Job Run AttributesTo display the current job run attributes, select option 3 (Display job run attributes,if active) on the Work with Jobs display. You can find out what a job’s run priorityis on this display.

Displaying the Call StackIf an active job has stopped or seems to be in a loop, the call stack can help todetermine where the problem is. It shows what program line numbers the job iscurrently trying to run. To display the call stack, select option 11 (Display callstack, if active) on the Work with Job menu.

Displaying Open FilesYou can see information about all of the files that the job is currently using byselecting option 14 (Display open files, if active) on the Work with Job menu.

The Display Open Files display is useful in detecting a program loop. Press F5continually and look at the data in the Relative Record column to see if the job isrepeating the same relative record number.

Chapter 10. Controlling OS/400 Jobs 10-15

Page 110: Iseries

Changing How a Job Is Run

You can also use this option to monitor the progress of a long-running batch job.For example, if you know that the job updates 15,000 records in a file, you cancheck the I/O Count field for the input/output count in that file to find out how thejob is progressing.

Changing How a Job Is RunOnce you have used the options on the Work with Job menu to do research, youmight want to change some of the attributes of a job that is running or waiting torun. You can change a number of job attributes. For example, if you have*JOBCTL authority, you can:

� Change the job queue priority� Change the run priority� Change the output priority� Move a job to a different job queue or output queue

Note: Display the current value of any job attributes before you change them.

You can change attributes of a job with the Change Job (CHGJOB) command.Select option 40 (Change job) on the Work with Job menu.

The following are tasks that can be done on the Change Job (CHGJOB) promptdisplay. You can do any of the following by changing the value for the specifiedparameter.

Changing a Job’s Priority on a Job QueueEach job on a job queue has an assigned priority (position on the queue). Tochange a job’s position on the queue, type a number (0 to 9) in the Job priority (onJOBQ) field on the Change Job (CHGJOB) display. Raising a job’s priority(changing the priority to a number closer to 0) can move it closer to the top of thequeue. Then the job begins running sooner than jobs with lower priority on thatqueue.

The highest priority is 0. The lowest priority is 9. Jobs with a higher priority arerun before jobs with a lower priority. There may be a limit on how high you can setthe priority, depending on the number specified in the Priority limit (PTYLMT)parameter of your user profile.

Note: When you submit a job, the highest priority allowed is 1. Priority 0 isreserved for changing a job to move it to the very top of the queue.

Figure 10-9 on page 10-17 shows how job priorities work when selecting jobs torun:

10-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 111: Iseries

Changing How a Job Is Run

1 2 3 4 9

To Processing

Priorities

If a job thathas a priorityof 1 is addedto the queue, itwould go here.

0

RV2P721-4

Figure 10-9. Job Queue Priority

This change only affects the job once. If the same job is submitted to the jobqueue again, it has its original priority. If you want to make a permanent change tothe job’s priority on the job queue, you need to change either the job description ituses or the procedure that submits the job.

Moving a Job to a Different Job QueueYou may have more than one job queue on your AS/400 system. Sometimescertain job queues are set aside for work that does not require immediate running.These job queues can be released and held depending on how busy your systemis. Or, your system may have a job queue assigned to a subsystem that has lesssystem resources than the interactive subsystem.

If you have more than one job queue on your system, you can move a job fromone queue to another by typing the new job queue in the Job queue field. Thischange only affects the job once. If the same job is submitted again in the sameway, it goes to the original job queue. If you want to make a permanent change tothe queue this job uses, you need to change either the job description it uses or theprocedure that submits the job.

Changing How an Active Job Is RunTo change how a job is run, change either the Run priority or Time slice fields onthe Change Job (CHGJOB) display. The control program decides which jobs to runin what order and for how long. Here’s how it happens:

� Every job has a time slice and a run priority . The time slice sets a limit onhow long the processor works on one job before switching to another job.Time slices are measured in milliseconds. The run priority determines whichjob the processor selects next.

� Once the processor has started processing the instructions for a job, it con-tinues with that job until one of the following happens:

– The job reaches time slice end.

– The job needs to wait for something. For example, an interactive job mightsend a new display to your display station. Then the system has to wait foryou to type another request and press Enter . This is known as a longwait .

Chapter 10. Controlling OS/400 Jobs 10-17

Page 112: Iseries

Changing How a Job Is Run

� When one of the previous events occurs, the system has to decide which job torun next.

� It looks at a list of jobs that are ready to be run and chooses the highest priorityjob.

You can see that both run priority and time slice can affect how a job is run. Youshould use great care in changing either of these. If you give any job too high apriority or too long a time slice, it can negatively affect everything else running onthe system.

When you use the Change Job (CHGJOB) command, it only affects the job once.If the same job runs again, it returns to the original priority and time slice. If youwant to make a permanent change to how the job runs, you need to change eitherthe characteristics of the class it uses or have it run using a different class. Formore information on class, see the Work Management book, SC41-4306.

Changing a Job’s Print PriorityEach printer output on an output queue has an assigned priority (position on thequeue that was obtained from the job’s print priority). To change this priority, typea number from 1 to 9 in the Output priority (on OUTQ) field. Raising a job’s priority(changing the priority to a number closer to 1) can move the job’s printer outputcloser to the top of the output queue. Then it begins printing sooner than printeroutput with lower priority on that output queue. Output queue priorities work in thesame way as job queue priorities (see Figure 10-9 on page 10-17).

Changing print priority using the Change Job (CHGJOB) command only affects thejob once. If the same job runs again, it returns to the original output priority. If youwant to make a permanent change to the job’s output priority, you need to changeeither the job description it uses or change the procedure for submitting the job.

Assigning a Job to a Different Output QueueWhen a batch job that creates printed output is waiting to run, you can change theoutput queue to which it is assigned by changing the Output queue field on theChange Job (CHGJOB) display. Once the batch job starts to run, it begins creatingits spooled file in its assigned output queue. At that point, you would need to movethe spooled file to a different output queue.

For an interactive job, you may want to change the assigned output queue beforeyou use the Print key or run a program that creates a report.

Using the Change Job (CHGJOB) command only affects the job once. If the samejob runs again, it is assigned to the original output queue. If you want to make apermanent change to a batch job’s output queue, you need to change either the jobdescription it uses or change the procedure for submitting the job. If you want tomake a permanent change to an interactive job’s output queue, you need tochange either the job description it uses, the user profile, or the work station devicedescription. For more information on the CHGJOB command, see the CL Refer-ence book, SC41-4722.

10-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 113: Iseries

Working with Job Logs

Working with Job LogsA job log is a system record of what happened when the job was processed.Each job has an associated job log that may contain the following information:

� The commands in the job

� The commands in any programs that were run as part of the job

� Any messages that were issued when the job ran, as well as the messageonline help information (second level text)

When a job is finished, a job log output file called QPJOBLOG is created. Usually,when a batch job ends, the job log remains on the output queue and can be viewedor printed. When an interactive job ends normally, the job log is usually not sent toan output queue. When an interactive job ends abnormally, the job log output fileis sent to an output queue.

The job log is a useful tool in diagnosing problems with a job. However, when thesystem creates and prints detailed job logs, it can slow the system down. It is agood idea to balance how much information you need in your job logs against howtheir creation affects system performance.

Displaying a Job LogYou can display a job log several different ways:

� For a job that has ended, on the Work with User Jobs menu:

1. Use option 8 (Work with spooled files) for the job whose log you want tosee.

2. On the Work with Job Spooled Files display, find the file calledQPJOBLOG.

3. Use option 5 (Display) to view it.

� For a job that is still running, on the Work with User Jobs menu:

1. Use option 5 (Work with) for the job whose log you want to see.2. On the Work with Job menu, select option 10 (Display job log, if active or

on job queue)

� To display the job log for your own work station session, use the Display JobLog (DSPJOBLOG) command.

Printing a Job LogWhen an interactive job is running, a job log is being created. If the interactive jobends normally, for example, when you sign off without problems, this job log is notsent to the output queue.

To print a log for your interactive job during sign-off:

1. On any OS/400 command line, type

signoff \list

2. Press Enter .

To print the job log for another job:

1. On any OS/400 command line, type

Chapter 10. Controlling OS/400 Jobs 10-19

Page 114: Iseries

Working with Job Logs

dspjoblog job(job-number/user/job-name) output(\print)

where job-number is the six-digit number of the job whose job log is to beprinted on the system, user is the name of the user of the job whose job log isto be printed, and job-name is the name of the job whose job log is to beprinted.

2. Press Enter

Your job log output file is printed or placed in an output queue, depending on howyour system is set up.

Changing the Logging Level for a JobTo minimize the size of job logs on your system, use the log level to limit howmuch information about a job is written to the job log.

To change the logging level for an active job:

1. Enter the Change Job (CHGJOB) command and press F4.

2. Press F10 (Additional parameters).

3. Press the Page Down key to find the Message logging and Log CL programcommand fields.

4. Type in the changes and press Enter .

Note: If you change the logging level to 0, F9 (Retrieve) does not work forcommand displays.

Using the Change Job (CHGJOB) command changes the logging level temporarily.If the same job runs again, it runs with its original log level.

To make a permanent change to the log level for a job, change the job descriptionunder which the job runs, using the Change Job Description (CHGJOBD)command.

Note: The same job description may be used by many jobs on the system. Inves-tigate the possible effect before making this type of global change.

Filtering Messages from the Job LogFiltering is the process of removing messages from the job log based on themessage logging level set for the job. Filtering occurs before each new request isreceived by a request processing program. If you run a CL program interactively orin batch and fill in the Message logging fields (on the Change Job command) asshown:

Level 0Severity 00Text *NOLIST

filtering would be run only once after the program ends. Filtering does not occurafter every CL command is run within the program. After the program ends, allmessages are removed from the job log because the message level is 0. A job logis not spooled if the job ended normally because *NOLIST is specified for themessage text level.

Note: When the job log is not spooled, system resource to remove messagesfrom the job log is wasted.

10-20 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 115: Iseries

Working with Job Logs

Sending Job Log Output Files to a Separate Output QueueThe Operational Assistant automatic cleanup function deletes old job logs byassigning them to the QEZJOBLOG output queue in the QUSRSYS library. Formore information about automatic cleanup, see chapter 8 of the System Operationbook, SC41-4203.

All of the job logs are conveniently stored for you in one output queue. You canview them when you need to. If you need a printed copy of a log, you can move itto an active output queue and print it.

To send your job logs to a separate output queue if you are not using the Opera-tional Assistant cleanup function, change the description for the job log printer fileto use the shipped output queue for job logs using the Change Printer File(CHGPRTF) command as follows:

1. On any OS/400 command prompt, type

CHGPRTF FILE(QPJOBLOG) OUTQ(QEZJOBLOG)

2. Press Enter .

Chapter 10. Controlling OS/400 Jobs 10-21

Page 116: Iseries

Working with Job Logs

10-22 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 117: Iseries

Displaying and Changing Device Status

Chapter 11. Working with OS/400 Devices andCommunications

In operating the system, you sometimes have to change device status (makingdevices available or unavailable for use). Each device (such as a diskette device,display station, printer, and tape device) has a status that determines if it is readyto use. A device is ready to use if its status is Available to use or Varied on.Display devices may also show a status of Sign-on display when waiting for auser to sign on. A device is not ready to use if its status is any of the following:

� Powered off or not yet available

� Varied off

� Session held

� Not assigned to active subsystem

Additional Reading: For conceptual information on configuration and how to do alocal configuration, see the Local Device Configuration book, SC41-4121. For infor-mation on how to do a remote configuration, see the Communications Configurationbook, SC41-3401.

Note: With the following tasks, make sure you are using the basic assistance levelof the Operational Assistant functions. Otherwise the displays you see willnot match the displays shown in this manual. For more information onassistance levels, see “Using Assistance Levels and User Profiles” onpage 6-3.

Displaying and Changing Device StatusTo change the status of your devices, use the Device Status (DEVICESTS) menu.

To display this menu, select option 10 (Manage your system, users, and devices)on the Operational Assistant (ASSIST) menu. Then, select option 20 (Device statustasks). To display the Work with Devices display where you can see different kindsof devices at once, use the Work with Configuration Status (WRKCFGSTS)command specifying *BASIC for the Assistance level (ASTLVL) parameter and*DEV for the Type (CFGTYPE) parameter.

To display and change the status of a device on the Device Status Tasks(DEVICESTS) menu, select the option number that corresponds to the type ofdevice (display, printer, tape, and diskette) whose status you want to see.

Security Consideration

Only the devices for which you have object operational authority are displayed.

On all of the device displays, the device status can be changed with option 1 (Makeavailable) or 2 (Make unavailable) after selecting the corresponding option on theDevice Status Tasks menu. The status for all of the devices is shown in the Statuscolumn.

Copyright IBM Corp. 1995, 1996 11-1

Page 118: Iseries

Renaming a Device

Device Status Restrictions� Making media devices ready for use may include answering messages sent to

the system operator. To display system operator messages, press F6 (Displaysystem operator messages) on the Work with Messages display.

� Before a printer can print, the printer’s power and ready lights must be on, andthe error light must be off. If the printer’s error light is on, you may need toanswer messages sent to the system operator. To do this, make the printeravailable (vary it on), start it, then answer any printer messages.

� Virtual devices, used by display station pass-through, are made available auto-matically by the pass-through function. This means that:

– You do not have to make a virtual device available.

– A virtual device is made available by the pass-through function unless youreach the limit specified for the QAUTOVRT system value. To display theQAUTOVRT system value, on an OS/400 command line, typeDSPSYSVAL QAUTOVRT and press Enter . To change the system value,use the Work with System Value (WRKSYSVAL) command. You musthave *ALLOBJ authority to change this system value.

For information on activating communications lines and controllers, see “ActivatingCommunications Lines and Controllers” on page 11-4.

Renaming a DeviceTo rename any device, on the Device Status Tasks menu:

1. Select the option that corresponds to the type of device you want to rename.For example, if you want to rename a display, select option 1 (Work withdisplay devices).

2. Vary off the device.

3. Use option 9 (Rename).

4. On the Rename Device display, type the new name of the device in the Newname field and press Enter . If necessary, the system tries to make theselected device unavailable so it can be renamed, and then makes it availableagain with the new name.

Considerations for Renaming DevicesIf you rename a device, there are other places where you will need to change thename.

Display Device

� Subsystem description work station entries entered by name � Display files � CD-ROM device� CL programs referring to this device

Printer Device

� Printer files� QPRTDEV system value� User profiles that refer to this device

11-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 119: Iseries

Printing Local Device Addresses

� CL programs referring to this device� Job descriptions that refer to this device by name� Display descriptions referring to this as an auxiliary printer

Tape device

� Tape files� CL programs referring to this device

Diskette device

� Diskette files� CL programs referring to this device

Displaying and Changing a Device DescriptionTo see the text description (location and owner) of any device on the system, pressF11 (Display descriptions) on any of the device displays. The display remains thesame except the description is shown next to the device it describes. In addition tothe name of the person who operates the device, it is helpful to include the physicallocation of the device in the Description column.

To return to the original display, just press F11 (Display types/statuses).

To change the device description, use option 13 (Change description). On theChange Description display, type the new description over the current description inthe New description field and press Enter . The Work with Display Devices displayis shown with the new description in the Description column.

Printing Local Device AddressesYou can print a diagram that shows the device location, by port number and switchsetting, for the devices attached to all local work station controllers.

This printout can help you know where to attach new devices.

To print the addresses of your local devices:

1. Type go devicests .

2. Press Enter to display the Device Status Tasks menu.

3. Select option 10 (Print local device addresses).

A message is displayed when printer output is created.

4. Type go assist .

5. Press Enter to display the Operational Assistant menu.

6. Select option 1 (Work with printer output).

7. Look for printer output named QPDCDEVA and follow the instructions on thedisplay to make sure it is printing.

Chapter 11. Working with OS/400 Devices and Communications 11-3

Page 120: Iseries

Activating Communications Lines and Controllers

Activating Communications Lines and ControllersFigure 11-1 illustrates how communications lines and controllers are connected toenable the devices to communicate with each other.

System 1

LIND LINDLineDescription

Controller CTRL CTRL

Devices Devices

System 2(or remotecontroller)

RV2P705-0

Figure 11-1. Relationship Between Controllers and Lines in Communications

To activate, change the text descriptions, or rename your communications lines andcontrollers, on the Device Status Tasks (DEVICESTS) menu:

1. Select the option that corresponds to the device that you want to work with.For example, to work with controllers and lines that connect display stations onthe AS/400 system, select option 1 (Work with display devices).

2. On the Work with Display Devices display (shown in Figure 11-2) use option 8(Work with controller and line) to show the controller and line to which thedevice is attached. For example, the following display shows the line and con-troller for RMTDEV1 which is a remote display station.

Note: If you used option 8 (Work with controller and line) for a local displaystation, you would see the Work with Controller display because a localdisplay does not have a communications line.

à@ ðWork with Controller and Line

System: SYSTEMð1 Type options below, then press Enter. 1=Make available 2=Make unavailable 5=Display details 7=Display message 9=Rename 13=Change description

Line/ Controller/ Opt Device Type Status __ LINð2 \SDLC Active __ RMTCTLð3 5394 Active __ RMTDEV1 318ð Sign-on display__ RMTDEV2 318ð Powered off or not yet available

F1=Help F3=Exit F5=Refresh F9=Command line F11=Display descriptionsF12=Cancel F17=Top F18=Bottom

á ñFigure 11-2. Work with Controller and Line Display

11-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 121: Iseries

Activating Communications Lines and Controllers

3. The Work with Controller and Line display shows the controller and line towhich the display is attached as well as the other local, remote, and virtual dis-plays and printers that are attached to that specific controller and line. On thisdisplay, you can do the following:

� To make a line, controller, or device available, use option 1 (Make avail-able).

� To make a line, controller, or device unavailable, use option 2 (Make una-vailable).

� To display a description of the line, controller, or device, use option 5(Display details).

� To rename the line, controller, or device, use option 9 (Rename) to see theRename Controller display.

On the Rename Controller display, you can change the name of the con-troller. If necessary, the system tries to make the selected controller una-vailable so it can be renamed, and then makes it available again with thenew name.

Note: When you change the name of a line or controller, other objects onthe system need to be updated with the new name. If you changethe name of a line or controller, check to ensure that any controllanguage (CL) programs that refer to that line or controller areupdated as well. Also, check the Alert Controller Description(ALRCTLD) network attribute on the Display Network Attribute(DSPNETA) command or Change Network Attribute (CHGNETA)command to see if it refers to the controller whose name waschanged.

� To change the text description of the line, controller, or device type, useoption 13 (Change description). On the Change Description display, typethe new description over the current description in the New descriptionfield. For example, if a new remote display station were added, RMTDEV3,you could change the description to include that display station.

Configuring Remote CommunicationsTo configure remote communications, use option 20 (Communications configurationtasks) on the Customize Your System, Users, and Devices (SETUP) menu or typego cmncfg on any command line and press Enter .

With the Communications Configuration menu you can easily configure:

� 5250 remote work station controllers and devices

� 3270 remote attach controllers and devices

� AS/400 system to AS/400 system using advanced program-to-program commu-nications (APPC) and Advanced peer-to-peer networking* (APPN*)

� AS/400 system to System/36 using APPN and APPC

For more information on remote communications, see the Communications Config-uration book, SC41-3401.

Chapter 11. Working with OS/400 Devices and Communications 11-5

Page 122: Iseries

Using a Switched Communications Line

Using a Switched Communications LineYou can establish a connection to a remote controller or another system by makinga telephone call to the remote location or by answering a telephone call from theremote location. If you do not have an automatic dial modem, you must place thecall manually, using manual dial. If you do not have an automatic answer modem,calls to you must be answered manually.

Using Manual DialGenerally, a communications request is made to the system by an applicationprogram. When the request is made, you manually connect the line by doing thefollowing:

1. A message is sent by the system to the system operator message queue. Ifyou are authorized as the system operator, a message light comes on at yourwork station, and an alarm, if your work station has one, sounds to indicate thata message has arrived.

2. Display the messages sent to the system operator:

a. On the Operational Assistant (ASSIST) menu, select option 3 (Work withmessages). The Work with Messages display is shown.

b. Press F6 (Display system operator messages). A message similar to thefollowing is displayed:

Manually dial 123-4567 for controller CTLUð2 line LINEð2. (C G)

3. Dial the indicated telephone number on the indicated line (in the examplemessage shown, the number is 123-4567 and the line is LINE02).

4. When the call is answered, type

5

to select Display details and reply.

5. Press Enter to respond to the message.

6. Type

g

in the response area.

7. Press Enter .

8. Put the telephone or modem in data mode. For information about how to dothis, see the appropriate modem instructions.

When you complete this manual dial sequence, another message is sent to thesystem operator. Display the message using option 3 (Work with messages).

The system operator message queue is shown with a message indicatingwhether the controller was contacted successfully or not. Sometimes theremote controller cannot be contacted or the line is busy.

Note: You have a limited amount of time to complete this manual dial sequence,or the communications program does not finish, therefore, you shouldmonitor the messages at a work station near the phone or modem.

11-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 123: Iseries

Using a Switched Communications Line

Using Manual AnswerConnect the line by doing the following:

1. When the telephone connected to the data line rings, answer it, and make surethe person calling is authorized, if possible. If it is a modem from anothersystem calling your number, listen for a buzz.

2. Type

ANSLIN

3. Press F4.

4. On the Answer Line (ANSLIN) prompt display, type the line name in the Linefield.

5. Press Enter .

A message is sent by the system to the system operator message queue.

6. On any command line, type

dspmsg qsysopr

7. Press Enter to display the messages sent to the system operator messagequeue. A message similar to the following should be displayed:

Type g and place modem for line LINEð2 in data mode. (C G)

8. Type

5

to select Display details and reply.

9. Press Enter to respond to the message.

10. Do one of the following:

� Type g in the response area and press Enter . Put the telephone ormodem in data mode.

For information about how to do this, see the appropriate modeminstructions.

� Type c and press Enter to cancel the operation.

11. Press F12 (Cancel) to return to your previous display.

When you complete this manual answer sequence, another message is sent tothe system operator message queue.

12. Display the message as in step 6 on page 11-7.

The system operator message queue is shown with a message indicating thatthe controller was contacted successfully.

Using Manual Answer for Countries Other Than the United StatesFor countries other than the United States, the government-operated common

| carrier Post Telephone and Telegraph Administration (PTT) and your X.21 BIS| modem allow you to contact remote systems using manual answer (a switched line| network). The X.21 BIS modem you are using differs from the X.21 modem in that| X.21 BIS converts analog signals used by older equipment to the digital signals

used by newer equipment.

Chapter 11. Working with OS/400 Devices and Communications 11-7

Page 124: Iseries

Using a Switched Communications Line

To start manual answer:

1. Type

ANSLIN

2. Press F4.

3. On the Answer Line display, type the line name in the Line field and pressEnter . A message is sent by the system to the system operator.

4. Display the messages sent to the system operator:

a. On the Operational Assistant (ASSIST) menu, type

3

to select Work with messages.

The Work with Messages display is shown.

b. Press F6 (Display system operator messages).

A message similar to the following should be displayed:

Enter G and place modem for line LINEð2 in data mode. (C G)

5. Type

5

to select Display details and reply.

6. Press Enter .

7. Type

g

in the response area.

8. Press Enter .

Attention: Do not press the answer button on the modem at this time.

9. When an incoming call is indicated by a signal from the data communicationsequipment, press the answer button within 60 seconds.

When you complete the manual answer sequence, another message is sent tothe system operator. Display the message using the Work with Messagesdisplay. The system operator message queue is shown with a message indi-cating that the controller was contacted successfully.

Note: It is helpful to display the status of the line and controller when you aretrying to make a dial connection. Press F5 to see what is currently hap-pening on the line and controller.

11-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 125: Iseries

Saving and Restoring OS/400

Chapter 12. Saving and Restoring OS/400 and OS/400Objects

This chapter contains an overview of how to save and restore OS/400 objects andthe OS/400 operating system.

You can save or restore an entire system or individual objects in the system. Usethe save and restore commands and functions to ensure that, following any type offailure, information exists that allows you to recover your system or to re-create anyobjects on your system that were damaged. The media that are used for saving orrestoring objects and information include tape, diskette, and optical storage.

You can use the save and restore functions by using specific commands or byusing menu options on the Save and Restore menus.

To display the Save menu, type GO SAVE on any command line and press Enter .

To display the Restore menu, type GO RESTORE on any command line and pressEnter .

Saving the Entire SystemYou should develop a disaster recovery plan:

� To ensure that you can respond to a disaster or other emergency that mightaffect your system

� To minimize the effect on your business operations

Part of the disaster recovery plan should be saving your entire system. The entiresystem includes:

� Licensed internal code� OS/400 operating system� OS/400 user profiles� OS/400 private authorities� OS/400 configuration objects� OS/400 optional libraries� OS/400 licensed program libraries� OS/400 IBM libraries with user data� OS/400 user libraries� OS/400 documents and folders� OS/400 distribution objects� OS/400 objects in directories

| Note: Your AS/400 Advanced 36 machines are saved when you save your| OS/400 user libraries. If you want to be able to restore individual files or| programs that are on your AS/400 Advanced 36 machines, you must also| use the SSP save procedures to individually save files, folders and libraries| that are on your AS/400 Advanced 36 machines. For directions, see

Chapter 25, “Saving and Restoring the AS/400 Advanced 36 MachineInformation.”

To save the entire system:

Copyright IBM Corp. 1995, 1996 12-1

Page 126: Iseries

Saving and Restoring OS/400

1. Stop each AS/400 Advanced 36 machine.

For directions, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine.”

2. Initialize tapes and load the first tape.

For information on how to initialize and load tapes, see Chapter 4 of theSystem Startup and Problem Handling book, SC41-4206 or Chapter 7 of theOperating Your Computer–SSP Operating System book, SC21-8297.

3. Use the Save Menu.

The simplest way to save your entire system is to use option 21 on the Savemenu. For directions, see chapter 4 in the Backup and Recovery – Basic book,SC41-4304.

This book also contains complete and detailed information on how to save andrestore objects and information and how to plan more advanced strategies forbackup and recovery.

Restoring the Entire SystemTo recover after a complete system loss, see “Recovering from a complete Loss” inChapter 9 in the Backup and Recovery – Basic book, SC41-4304.

To recover after a disk failure, see “Choosing the Recovery for a disk failure” inChapter 9 in the Backup and Recovery – Basic book, SC41-4304.

After either of these recoveries, if you have a more recent copy of your AS/400Advanced 36 machine data, restore that data.

If you did individual saves of your AS/400 Advanced 36 machine, restore theAS/400 Advanced 36 machine. For directions, see Chapter 25, “Saving andRestoring the AS/400 Advanced 36 Machine Information.”

Saving the OS/400 Operating SystemThe Save System (SAVSYS) CL command saves:

� A copy of the Licensed Internal Code

� The QSYS library (including security information and configuration objects)

These are saved in a format compatible with the installation of the AS/400system.

SAVSYS does not save:

� Any AS/400 Advanced 36 machine

For directions on saving an AS/400 Advanced 36 machine, see Chapter 25,“Saving and Restoring the AS/400 Advanced 36 Machine Information” onpage 25-1.

� Libraries other than QSYS

For directions on saving the entire system including the AS/400 Advanced 36machine, see “Saving the Entire System” on page 12-1.

12-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 127: Iseries

Saving and Restoring OS/400

Restoring the OS/400 Operating SystemRestoring the OS/400 operating system from SAVSYS media is made up of twotasks:

� Restoring the Licensed Internal Code

For directions, see “Recovering Licensed Internal Code” in the Backup andRecovery – Basic book, SC41-4304.

� Restoring the operating system

For directions, see “Restoring the Operating System” in the Backup andRecovery – Basic book, SC41-4304.

For directions on restoring other libraries from SAVSYS media, the directions arealso included in the Backup and Recovery – Basic book, SC41-4304.

For directions on how to restore an AS/400 Advanced 36 machine that was savedindividually, see Chapter 25, “Saving and Restoring the AS/400 Advanced 36Machine Information.”

Saving AS/400 StorageThe Save Storage (SAVSTG) CL command causes the Licensed Internal Code andthe contents of the auxiliary storage to be saved to tape. When you run theSAVSTG command, the save function causes an IPL of the system. This functionis intended for disaster recovery backup. Individual libraries or objects cannot berestored from a save storage tape. For more information on the SAVSTGcommand, see the CL Reference book, SC41-4722.

Restoring AS/400 StorageTo use the restore storage function,

� The system must be in a DST-restricted state.

� The disk storage configuration must be the same as it was when the SAVSTGcommand was used.

The restore storage process is started by using an option on the Dedicated ServiceTools (DST) menu. The restore storage operation can only be started when theoperating system is not active (before an IPL of the operating system). This func-tion is intended for disaster recovery backup. The procedure does not restoresingle objects or libraries.

Saving Individual OS/400 ObjectsThis section contains an overview of the CL commands that can be used to saveOS/400 objects. For more information about these CL commands, see the CL Ref-erence book, SC41-4722.

Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-3

Page 128: Iseries

Saving and Restoring OS/400

Saving Objects in DirectoriesThe Save (SAV) command saves a copy of one or more objects that can be usedin the integrated file system. For more information about the integrated file system,see the Integrated File System Introduction book, SC41-4711.

Saving CalendarThe Save Calendar (SAVCAL) CL command saves of calendars and calendaritems.

Saving Configuration ObjectsThe Save Configuration (SAVCFG) command saves all configuration and systemresource management (SRM) objects without requiring a system in a restrictedstate .

Saving Changed ObjectsThe Save Changed Objects (SAVCHGOBJ) command saves a copy of eachchanged object (since a specified date and time). The SAVCHGOBJ command isthe same as the SAVOBJ command except that the SAVCHGOBJ command savesonly changed objects and members.

Saving Documents, Folders, and MailThe Save Document Library Object (SAVDLO) command saves copies of the fol-lowing:

� Documents � Folders� Distribution objects (mail)

Documents can be saved individually or in a group using the SAVDLO command.

Distribution objects (mail) cannot be saved or restored for individual users. Mailcan only be saved for all users.

The SAVDLO DLO(*ALL) FLR(*ANY) command saves a copy of all documents,folders, and distribution objects (mail).

The SAVDLO DLO(*CHG) saves all documents created or changed, all folderscreated since the last complete save operation, and all mail.

Saving LibrariesThe Save Library (SAVLIB) command allows you to save a copy of one or morelibraries.

An AS/400 Advanced 36 machine is stored as an object in a library. By saving thatlibrary, you can save the entire AS/400 Advanced 36 machine. A library containingan AS/400 Advanced 36 machine can be restored just like any other library.

Attention : You must stop the AS/400 Advanced 36 machine in order to save thelibrary in which the AS/400 Advanced 36 machine is contained.

The SAVLIB command saves the entire library, including the library description, theobject descriptions, and the contents of the objects in the library. You can save 1 to

12-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 129: Iseries

Saving and Restoring OS/400

300 libraries using the SAVLIB command. If you specify multiple libraries, youoverlap processing, which can improve performance. All libraries, including all userlibraries, can be saved to diskette or tape using the SAVLIB command. Userlibraries are defined as libraries that you create or IBM-supplied libraries that areintended to contain user data.

The SAVLIB LIB(*NONSYS) command saves all user-created libraries, the QGPLlibrary, and licensed program libraries, such as QRPG and QIDU.

The SAVLIB LIB(*IBM) command saves all system (IBM) libraries.

The SAVLIB LIB(*ALLUSR) command saves all user libraries. To determine whichlibraries are IBM libraries and which libraries are user libraries, see the Backup andRecovery – Basic book, SC41-4304.

Note: When you save this way, you cannot restore individual System/36 files orprograms. You must restore the entire library. You should continue to usethe directions in Chapter 25, “Saving and Restoring the AS/400 Advanced36 Machine Information” to save specific files and program libraries.

Saving Licensed ProgramsThe Save Licensed Programs (SAVLICPGM) CL command saves a copy of theobjects that make up a licensed program.

Saving Specific ObjectsThe Save Object (SAVOBJ) CL command saves a copy of a single object or agroup of objects located in the same library.

Saving Security DataThe Save Security Data (SAVSECDTA) command saves all security informationwithout requiring a system in a restricted state .

Restoring Individual OS/400 ObjectsThis section contains an overview of the CL commands that can be used to restoreOS/400 objects. For more information about these CL commands, see the CL Ref-erence book, SC41-4722.

Restoring Objects in DirectoriesThe Restore (RST) command restores a copy of one or more objects that can beused in the integrated file system. For more information about integrated filesystem, see the Integrated File System Introduction book, SC41-4711.

Restoring CalendarThe Restore Calendar (RSTCAL) CL command allows you to restore calendars andcalendar items.

Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-5

Page 130: Iseries

Saving and Restoring OS/400

Restoring Configuration DataThe Restore Configuration (RSTCFG) command restores a device configurationobject to the system. The command restores any device configuration object thatwas saved to tape by the Save System (SAVSYS) command or the Save Config-uration (SAVCFG) command.

Restoring Changed ObjectsThe Restore Changed Objects (RSTCHGOBJ) CL command restores eachchanged object (since a specified date and time). The RSTCHGOBJ command isthe same as the RSTOBJ command except that the RSTCHGOBJ command onlyrestores changed objects and members.

Restoring Documents, Folders, and MailThe Restore Document Library Object (RSTDLO) command restores documents,folders, and distribution objects (mail).

The RSTDLO DLO(*ALL) SAVFLR(*ANY) command restores to the system all doc-uments, folders, and distribution objects (mail) saved on media, regardless of thefolders (if any) from which they were saved.

Restoring LibrariesThe Restore Library (RSTLIB) command restores a single saved library or a groupof libraries. The RSTLIB command restores the entire library, including the librarydescription, object descriptions, and the contents of the other objects. Any librarythat was saved by the Save Library (SAVLIB) command can be restored by theRSTLIB command.

The AS/400 Advanced 36 machine is stored as a library. If you have used theSAVLIB command to save the library in which the AS/400 Advanced 36 machine isstored, you can use the RSTLIB command to restore the entire AS/400 Advanced36 machine.

The RSTLIB SAVLIB(*IBM) command restores to the system all system (IBM)libraries (with the exception of the QSYS library).

The RSTLIB SAVLIB(*ALLUSR) command restores to the system all user libraries.See the Backup and Recovery – Basic book, SC41-4304, to determine whichlibraries are IBM libraries and which libraries are user libraries.

The RSTLIB SAVLIB(*NONSYS) command restores to the system all librariessaved by SAVLIB LIB(*NONSYS) command.

Restoring Licensed ProgramsThe Restore Licensed Program (RSTLICPGM) CL command restores a copy of theobjects that make up a licensed program.

12-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 131: Iseries

Saving and Restoring OS/400

Restoring Specific ObjectsThe Restore Object (RSTOBJ) command restores objects to a library. Objects canonly be restored to one library at a time with the RSTOBJ command.

Attention: When you restore an object, it replaces any existing object in the samelibrary with the same name and object type.

Restoring User ProfilesThe Restore User Profile (RSTUSRPRF) command restores the basic parts of auser profile or a set of user profiles. The command restores any user profiles thatwere saved by the Save System (SAVSYS) command or the Save Security Data(SAVSECDTA) command.

Restoring Object AuthorityThe Restore Authority (RSTAUT) command restores object authorities. When yourestore objects and user profiles, you do not simultaneously restore the authority tothose objects. Authority is only restored by using the RSTAUT command.

Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-7

Page 132: Iseries

Saving and Restoring OS/400

12-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 133: Iseries

Working with LIC and OS/400 PTFs

Chapter 13. Working with Licensed Internal Code and OS/400Program Temporary Fixes

IBM periodically creates program temporary fixes (PTFs) to correct problems orpotential problems found within a particular IBM licensed program. PTFs may fixproblems that appear to be hardware failures, or they may provide new functions.

PTFs are designed to replace one or more objects in the licensed program. Gener-ally, PTFs are incorporated in a future release of the system.

PTFs packaged using the SystemView* System Manager/400 licensed programmay also be available for non-IBM programs. See the System Manager Use, book,SC41-3321, for information on this licensed program.

The program maintenance strategy discussed in this chapter applies specifically toIBM AS/400 system service and delivery.

AS/400 Program Maintenance StrategyThe AS/400 program maintenance strategy consists of preventive service and cor-rective service.

Preventive Service (Cumulative PTF Packages)Preventive service helps you avoid problems that have been resolved since thestart of the current release.

Cumulative PTF packages contain PTFs which have been ordered a specificnumber of times. If a PTF provides a change for a limited set of users or requiresspecial handling, it may not be included in the package. Cumulative PTF packageapplication is useful for ensuring you have key changes and improvements for your

| system. The entire cumulative PTF package should be installed after you load or| reload a different version, release or modification of the OS/400 operating system.

Cumulative PTF packages can be ordered electronically or by telephone and arealways sent by mail on a CD-ROM or tape.

Cumulative PTF packages should be installed every three to four months if there isno change to the equipment or programs on your system. Between releases ofcumulative PTF packages, IBM service support provides PTFs that may be impor-tant to your system. You should periodically order preventive service planninginformation and review the PTFs listed. If any of these PTFs are needed for yoursystem, you should order and install them.

Corrective ServiceCorrective service corrects problems reported to IBM service support. If you havea problem with an IBM licensed program, you can describe the problem using theAnalyze Problem (ANZPRB) command or the Work with Problem (WRKPRB)command. You can report the problem electronically or by calling your service pro-vider. You can also have the system analyze or report any problems automatically.For more information on reporting problems, see System Startup and Problem Han-dling book, SC41-4206.

Copyright IBM Corp. 1995, 1996 13-1

Page 134: Iseries

Ordering PTFs and PTF Information

Ordering LIC and OS/400 PTFs and PTF InformationFor information on the following topics, see Chapter 5 of the System Startup andProblem Handling book, SC41-4206.

� Ordering PTFs and PTF Information

� Installing PTFs

� System Storage Areas A and B

� Advanced PTF Topics

13-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 135: Iseries

Transferring to M36

Chapter 14. Transferring to an AS/400 Advanced 36 Machine

There are three ways of transferring to an AS/400 Advanced 36 machine:

� The Transfer to AS/400 Advanced 36 (TFRM36) CL Command

The TFRM36 command transfers control of a display device from an OS/400job to the specified AS/400 Advanced 36 machine. The display device that istransferred is the one on which the command is run.

� The Start AS/400 Advanced 36 Procedure (STRM36PRC) CL Command

The STRM36PRC command transfers control from an OS/400 job to the speci-fied AS/400 Advanced 36 machine and runs the specified SSP procedure. Thedisplay device that is transferred is the one on which the command is run.

� The Start Pass-Through (STRPASTHR) CL Command

The STRPASTHR command allows you to pass through to an AS/400Advanced 36 machine where you can sign on as if your display station wereattached locally. The display device where STRPASTHR is run is the displaythat is transferred to the AS/400 Advanced 36 machine.

Important Information about Transferring| You can use the TFRM36 and STRM36PRC commands to transfer the display| station to an AS/400 Advanced 36 machine.

| You can also use the pass-through support to transfer the display station to an| AS/400 Advanced 36 machine. When the OS/400 operating system and the| AS/400 Advanced 36 machine are on the same physical system, the APPC or| APPN support uses the Internal Local Area Network (ILAN) to link for the pass-| through.

| Attention : You should not transfer the OS/400 console to an AS/400 Advanced 36| machine.

OS/400 allows up to ten characters for a user ID. An AS/400 Advanced 36machine allows up to eight characters for the user ID. For this reason, when youchoose to automatically sign on to the AS/400 Advanced 36 machine, the first eightcharacters of the OS/400 user ID are used. If two user IDs start with the sameeight characters, this could be a security problem. For example, the following userIDs would all be shortened to MICHAELS:

MICHAELS MICHAELSON MICHAELSEN MICHAELSRM

Restrictions on Transfers using the TFRM36 and STRM36PRCCommands

The following restrictions apply when using the TFRM36 or the STRM36PRC CLcommand to transfer to an AS/400 Advanced 36 machine:

� The AS/400 Advanced 36 machine specified on the M36 parameter must beSTARTING or STARTED. If the STATUS of the machine is STARTED, the

Copyright IBM Corp. 1995, 1996 14-1

Page 136: Iseries

Transferring to M36

transfer request proceeds immediately. If the machine STATUS changes toSTARTED before two minutes are up, the transfer proceeds. After twominutes, if the machine STATUS is still STARTING, the transfer request endswith an error. The STATUS of the AS/400 Advanced 36 machine can be foundby using the Work AS/400 Advanced 36 Machine (WRKM36) CL command.

| For more information on the WRKM36 CL command, see “Using the Work with| AS/400 Advanced 36 Machine Command” on page 30-1.

� If the AUTOSIGNON function is used during the transfer, the AS/400 Advanced36 machine being transferred to must have AUTOSIGNON(*ENABLE) specifiedor a message is issued. For TFRM36, the transfer continues andAUTOSIGNON(*NO) is used.

When you set up your AS/400 Advanced 36 machine, you need to decidewhether to allow automatic sign-on or not. If you allow automatic signon, anSSP signon display is not seen because the user ID is already signed on toOS/400.

A user ID that is greater than eight characters is truncated to an eight-characteruser ID when they transfer to an AS/400 Advanced 36 machine.

� The STRM36PRC command cannot be sent to an AS/400 Advanced 36machine display station that is configured as an AS/400 Advanced 36 machinedata display station. It must be sent to an AS/400 Advanced 36 machinedisplay station that is configured as a command display station.

� If you specify automatic signon for the TFRM36 command and specify a menu,library, or procedure, the command must be sent to a display station which isconfigured as a command display station. These parameters are not allowedwhen you sign on to an AS/400 Advanced 36 machine data display station.

� Problems can occur if the TFRM36 or STRM36PRC CL commands are usedwhile you are reloading SSP. The TFRM36 or STRM36PRC commands can bediscarded and there may be no record that the commands did not completesuccessfully.

| � From a non-local display station that was transferred to an AS/400 Advanced| 36 machine using the TFRM36 or STRM36PRC commands, functions like| display station passthru and 3270 device emulation might not work correctly. In| some cases, the format of the data returned to the application for signed| numeric processing and trailing nulls processing will be different on the AS/400| Advanced 36 machine than it was on a System/36.

| � If the Test Request key is pressed on a non-local display that is transferred to| an AS/400 Advanced 36 machine using the TFRM36 or STRM36PRC, an error| message is shown that indicates the key is not supported.

| � From a non-local display station that was transferred to an AS/400 Advanced| 36 machine using the TFRM36 or STRM36PRC commands, some text pro-| cessing functions (for example, editing a document) do not work like they did| on a System/36.

| – Help and print keys

| When you edit a document, the modified data in the document is not| returned to the system when either the help key or print key is pressed.

| – Supported Emulators

14-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 137: Iseries

Transferring to M36

| Some non-local displays do not support the System/36 TEXTDOC proce-| dure. If the system can determine that the display does not support| System/36 text, the following error message is shown:

| Text processing is not supported on this display.

| – 3477 Extended Attributes

| The AS/400 Advanced 36 machine never sends the 3477 extended attri-| butes to non-local transferred displays. Some display station emulators| (For example: Personal Communications 5250 (PCOM), Client Access for| Windows, Client Access for OS/2, Connection Program/6000) expect the| 3477 extended attributes to be sent. If you do any text processing from| any of these displays, an error message is shown that indicates the display| station has a program error.

| � The PASSTHRU procedure will not work from a non-local display that was| transferred to an AS/400 Advanced 36 machine using the TFRM36 or| STRM36PRC commands. If you want to passthru to another system from one| of these displays, use the RUN400 OCL statement to run the OS/400| STRPASTHR CL command to passthru to the other system.

| � From a non-local display station that was transferred to an AS/400 Advanced| 36 machine using the TFRM36 or STRM36PRC commands, if data is to be| returned to the application on a read immediate operation, the application will| not work like it did on the System/36. On the System/36, the data was always| returned regardless of whether the modified data tag was set. On an AS/400| Advanced 36 machine, the data is only returned if the modified data tag is set.| The modified data tag can be set when the field is defined or when the data in| the field is modified.

Transferring to an AS/400 Advanced 36 Machine Using TFRM36The Transfer to AS/400 Advanced 36 Machine (TFRM36) command transferscontrol of a display device from an OS/400 job to the specified AS/400 Advanced36 machine. The display device that is transferred is the one on which thecommand is run. Control returns to OS/400 when you sign off the SSP operatingsystem.

There are certain restrictions you should be aware of when using the TFRM36. Forinformation on the restrictions, see “Restrictions on Transfers using the TFRM36and STRM36PRC Commands” on page 14-1. For more information on theTFRM36 command, see the CL Reference book, SC41-4722.

Transferring to an AS/400 Advanced 36 Machine1. On an OS/400 command line or in a CL source program, type

TFRM36

2. Press F4.

3. Type values in the fields that apply.

| 4. Press Enter .

| More fields are shown.

| 5. Type values in the fields that apply.

| 6. Press Enter .

Chapter 14. Transferring to an AS/400 Advanced 36 Machine 14-3

Page 138: Iseries

Transferring to M36

Using the TFRM36 Command — ExamplesExample 1

TFRM36 M36(MYM36)

This command transfers the display station, on which the command is run, to anAS/400 Advanced 36 machine named MYM36. It is located through the library list ofthe OS/400 job. If the machine allows automatic sign on, the user of the displaydevice is automatically signed on to the AS/400 Advanced 36 machine using thedefault menu, library, and procedure identified in the user's SSP user profile.

| Because a workstation identifier was not specified on the transfer, the system| determines the SSP logical workstation identifier. If the machine does not allow| automatic signon, the SSP signon display for that workstation appears.

If the display device is defined in the AS/400 Advanced 36 machine's configuration(*M36CFG) through either controller or device mapping, the controller, port, andaddress of the display station in the AS/400 Advanced 36 machine configuration isused to determine the SSP logical display station. For example, if your displaystation is defined as controller 2, port 3, address 4, then the SSP logical work-station will be the display station that is defined at controller 2, port 3 and address4 in the SSP master configuration record.

If the display station is not defined in the AS/400 Advanced 36 machine configura-tion, the SSP logical display station is chosen by the system from a list of displaystations that are defined in the SSP master configuration record that are not in theAS/400 Advanced 36 machine configuration.

Example 2

TFRM36 M36(\CURLIB/MYM36) WSID(W7) AUTOSIGNON(\YES) MENU(INV) LIB(INVAPPL) PRC(INVPREP) IGC(\NO)

This command transfers the display device, on which it is run, to an AS/400Advanced 36 machine named MYM36, located in the current library of the OS/400job. The user of the display device is automatically signed on to the AS/400

| Advanced 36 machine if it is configured to allow automatic signons. If the machine| does not allow automatic signon, the SSP signon display for that workstation| appears.

| The display device is assigned the M36 workstation identifier W7, if it is available foruse by this display device. If it is not available, an error message is returned andthe transfer request is refused.

If the user can be automatically signed on to workstation W7, the library INVAPPL willbe the default library for the user's AS/400 Advanced 36 machine session. Addi-tionally, the procedure INVPREP will be run before the user menu INV is shown onthe user's display device. The user is not given an ideographic session. If therequested library, procedure, or menu for the TFRM36 command cannot be found,the System/36 signon display is shown and a message which identifies the erroralso appears on the signon display. The user has the option of correcting the errorand signing on or pressing Cmd7 to return to OS/400.

Example 3

TFRM36 M36(JOG/ADV36) AUTOSIGNON(\NO)

14-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 139: Iseries

Transferring to M36

This command transfers the display device, on which it is run, to an AS/400Advanced 36 machine named ADV36, located in a library named JOG. The SSPworkstation identifier that is assigned to the display device, is based on whether thedisplay device is currently configured in the AS/400 Advanced 36 machine. Theuser of the display device must sign on to the AS/400 Advanced 36 machine.

| For more information on this command, type the command on an OS/400| command line and press F1.

| How to Allow for Automatic Sign-On| If you decide you want to allow automatic sign-on, set up the AS/400 Advanced 36| machine as follows:

| 1. Stop the AS/400 Advanced 36 machine.

| For directions, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine.”

| 2. On an OS/400 command line, type

| CHGM36 library-name/machine-name

| where machine-name is the name of the AS/400 Advanced 36 machine and| library-name is the name of the library that contains the AS/400 Advanced 36| machine.

| 3. Press F4.

| 4. Change the Automatic sign-on field to *ENABLE .

| 5. Press Enter .

| 6. Start the AS/400 Advanced 36 machine.

| For directions, see Chapter 15, “Starting an AS/400 Advanced 36 Machine” on| page 15-1.

| 7. On an OS/400 command line, type

| TFRM36 library-name/machine-name

| where machine-name is the name of the AS/400 Advanced 36 machine and| library-name is the name of the library that contains the AS/400 Advanced 36| machine.

| 8. Press F4.

| The Transfer to Machine (TFRM36) display appears.

| 9. Make sure the value in the automatic sign-on field is \YES.

| 10. Press Enter .

| Your display station is transferred to the AS/400 Advanced 36 machine and you| are signed on to the machine.

| Selecting the Correct User Profile| When you transfer to an AS/400 Advanced 36 machine using the TFRM36 or| STRM36PRC CL commands, most of the S/36 printed output that is sent to an| OS/400 output queue is owned by the user's OS/400 user profile. However, in the| case of the following:

| � Print key output

| � Printed output from jobs put on the JOBQ

Chapter 14. Transferring to an AS/400 Advanced 36 Machine 14-5

Page 140: Iseries

Transferring to M36

| � Printed output from evoked jobs

| � Printed output from NRT programs

| � Printed output from MRT procedures

| the output that goes to an OS/400 output queue is owned by the user profile asso-| ciated with the AS/400 Advanced 36 machine. Similar processing also applies| when one of the above jobs executes a RUN400 OCL statement. The CL| command executes under the user profile associated with the AS/400 Advanced 36| machine. If you want all printed output and all your RUN400 OCL statement jobs| to use your OS/400 user profile, you should change the SSP HOSTUPRF system| value from OFF to ON. The default value is OFF. To change the SSP HOSTUPRF| value to ON, use the CHGSYSVL procedure:

| CHGSYSVL HOSTUPRF,ON

| This change remains in effect until the SSP HOSTUPRF system value is changed| to OFF.

| Whether HOSTUPRF is ON or OFF, the M36 server job opens the output queue| and executes the RUN400 CL command for the type of jobs listed in this topic.| The M36 server job might have a different library list or other job attributes than| those of the job which executed the TFRM36 or STRM36PRC command.

| For more information on the SSP HOSTUPRF system value, see the General Infor-| mation for SSP Operating System book, SC21-8299.

Transferring to an AS/400 Advanced 36 Machine Using theSTRM36PRC Command

The Start AS/400 Advanced 36 Procedure (STRM36PRC) CL command transferscontrol from an OS/400 job to the specified AS/400 Advanced 36 machine and runsthe specified SSP procedure. Control returns to OS/400 when the SSP procedureends.

There are certain restrictions you should be aware of when using the STRM36PRCcommand. For information on the restrictions, see “Restrictions on Transfers usingthe TFRM36 and STRM36PRC Commands” on page 14-1.

For more information on the STRM36PRC command, see the CL Reference book,SC41-4722.

Using the STRM36PRC Command1. On an OS/400 command line or in a CL source program, type

STRM36PRC

2. Press F4.

3. Type values in the fields that apply.

4. Press Enter .

14-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 141: Iseries

Transferring to M36

Running an SSP Procedure from OS/400 — ExamplesExample 1

The following example runs an SSP procedure named CATALOG on an AS/400Advanced 36 machine named PARENTIS.

STRM36PRC M36(PARENTIS) PRC(CATALOG)

The AS/400 Advanced 36 machine first checks for the procedure in the defaultsession library identified in the user's SSP user profile. If the AS/400 Advanced 36machine does not find the procedure in the default session library, SSP automat-ically searches the AS/400 Advanced 36 machine system library (#LIBRARY). Noparameters are passed to the procedure.

Example 2

The following example shows how to run an SSP procedure and pass parameters.

STRM36PRC M36(JML/CLASSOF96) PRC(TRNSCRPT) CURLIB(STUDENTS) PARM('LIST,ALL') IGC(\NO)

This command runs an SSP procedure named TRNSCRPT on an AS/400 Advanced36 machine named CLASSOF96, located in a library named JML. First, the AS/400Advanced 36 machine checks for the procedure in a library named STUDENTSbecause this was specified as the current library for the procedure. If the AS/400Advanced 36 machine does not find the procedure in the specified library, SSPautomatically searches the AS/400 Advanced 36 machine system library(#LIBRARY). If the PRC or CURLIB values are not found, an error message isreturned to OS/400 and the STRM36PRC command is not successful. The posi-tional parameters LIST and ALL are passed to the procedure. Any system mes-sages or displays that are shown use single-byte characters only.

| Note: Positional parameters (such as LIST and ALL) must be typed in upper case.

To find out more about what you can do with the STRM36PRC CL command, typethe command on an OS/400 command line and press F1.

Transferring to an AS/400 Advanced 36 Machine using STRPASTHRThe Start Pass-Through (STRPASTHR) command allows you to pass through to anAS/400 Advanced 36 machine where you can sign on as if you were attachedlocally. The display device where STRPASTHR was run is the display that is trans-ferred to the AS/400 Advanced 36 machine. In order to use the STRPASTHRcommand:

� The AS/400 Advanced 36 machine you are passing through to must beSTARTED. If the STATUS of the machine is STARTED, the transfer requestproceeds immediately. If the machine STATUS is something other thanSTARTED, the transfer fails.

The STATUS of the AS/400 Advanced 36 machine can be found by using theWork with AS/400 Advanced 36 Machine (WRKM36) CL command. For moreinformation on the WRKM36 CL command, see the CL Reference book,SC41-4722.

Chapter 14. Transferring to an AS/400 Advanced 36 Machine 14-7

Page 142: Iseries

Transferring to M36

� ILAN communications must be set up. For directions on setting up ILAN, seeChapter 4 in the Getting SSP and OS/400 Installed and Running book,SC21-8377.

For more information on the STRPASTHR command, see CL Reference book,SC41-4722.

Running the STRPASTHR command:1. On an OS/400 command line, type

STRPASTHR

2. Press F4.

3. Type values in the fields that apply.

4. Press Enter .

Transferring to an AS/400 Advanced 36 Machine Using theSTRPASTHR Command — ExamplesExample 1 — Pass Through to an AS/400 Advanced 36 Machine

On an OS/400 command line, type:

STRPASTHR RMTLOCNAME(IBMM36ð1)

This command specifies a pass-through to an AS/400 Advanced 36 machine at alocation of IBMM36ð1. The defaults for all the other parameters are used.

When the pass-through has completed, an SSP sign-on display will appear at thedisplay device on which the STRPASTHR command was typed.

Example 2 — Pass Through and Automatically Sign on to an AS/400 Advanced 36Machine

On an OS/400 command line, type:

STRPASTHR RMTLOCNAME(IBMM36ð1) RMTUSER(USER1) RMTPWD(X1T4)

This command specifies a pass-through to an AS/400 Advanced 36 machine at alocation of IBMM36ð1. A user ID of USER1 and password of X1T4 are passed to theAS/400 Advanced 36 machine. The defaults for the other parameters are used. IfUSER1 is authorized to the AS/400 Advanced 36 machine and has enabled theAS/400 Advanced 36 machine for automatic sign on, an SSP command displayappears on the display where the STRPASTHR command was typed.

For more information on using STRPASTHR, see “Using Display Station Pass-Through” on page 29-15.

14-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 143: Iseries

SSP for the OS/400 Operator

Chapter 15. Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . 15-1Starting the AS/400 Advanced 36 Machine from the OS/400 Command line 15-1

Requirements for Using the Start AS/400 Advanced 36 Machine Command 15-1Using the IPL Type (IPLTYPE) Parameter . . . . . . . . . . . . . . . . . . . 15-2Using the User Profile (USRPRF) Parameter . . . . . . . . . . . . . . . . . 15-2Using the Apply AS/400 Advanced 36 Machine Configuration

(APYM36CFG) Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Starting an AS/400 Advanced 36 Machine — Examples . . . . . . . . . . . 15-4

Starting the AS/400 Advanced 36 Machine Automatically . . . . . . . . . . . 15-5How To Change a Configuration for an AS/400 Advanced 36 Machine That

Starts Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5Creating a Customized IPL Start-Up Program . . . . . . . . . . . . . . . . . 15-5Sample QSYS/QSTRUP Start-up Program . . . . . . . . . . . . . . . . . . 15-7

Chapter 16. Stopping an AS/400 Advanced 36 Machine . . . . . . . . . . 16-1Putting the AS/400 Advanced 36 Machine In a Dedicated State . . . . . . . . 16-1Stopping an AS/400 Advanced 36 Machine from the SSP System Console . 16-2Stopping an AS/400 Advanced 36 Machine from the OS/400 Operating

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Chapter 17. Operating the SSP Console and SSP Subconsoles . . . . . 17-1The SSP Console: A Way of Controlling the AS/400 Advanced 36 Machine 17-1The SSP Subconsole: A Way of Controlling SSP Printers . . . . . . . . . . . 17-1Transferring the SSP Console Function to an Alternative SSP Console . . . 17-2

Transferring the SSP Console Function During an Attended IPL . . . . . . 17-2Transferring the SSP Console Function When the SSP Console Is in

Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3Transferring the SSP Console Function to an Alternative SSP Console

When the Console Is in Operation . . . . . . . . . . . . . . . . . . . . . . 17-3Making an Alternative SSP Console the SSP Console . . . . . . . . . . . . 17-3Transferring the SSP Console Function When the SSP Console Is Not in

Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4Using the SSP Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

Requesting a Help Menu from the SSP Console Display . . . . . . . . . . 17-5Using the Subconsole Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Requesting a Help Menu from the Subconsole Display . . . . . . . . . . . 17-6

Chapter 18. Handling SSP Messages . . . . . . . . . . . . . . . . . . . . . 18-1How You Know That You Have an SSP Message . . . . . . . . . . . . . . . . 18-1Types of SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Messages That Instruct You to Perform an Action . . . . . . . . . . . . . . 18-2Messages That Require a Response . . . . . . . . . . . . . . . . . . . . . . 18-2Additional Information for a Message . . . . . . . . . . . . . . . . . . . . . . 18-5Informational Messages at the SSP Console . . . . . . . . . . . . . . . . . 18-5

Specifying That Informational Messages Are Not to Be Displayed at theSSP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6

Displaying SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-6Replying to SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-7

Replying to Messages - Example . . . . . . . . . . . . . . . . . . . . . . . . 18-8Sending SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9

Copyright IBM Corp. 1995, 1996

Page 144: Iseries

Using the MSG Control Command to Send an SSP Message . . . . . . . 18-9Using the MSG OCL Statement to Send an SSP Message . . . . . . . . 18-10Using the OFCMSG Procedure to Send a Message . . . . . . . . . . . . 18-10

SSP Keyboard Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-10Error Reset Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10

Displaying Keyboard Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-11

Chapter 19. Using SSP Commands and Procedures to Do Tasks . . . . 19-1Using Help for Commands and Procedures . . . . . . . . . . . . . . . . . . . 19-1

When You Know the Name of a Command or a Procedure . . . . . . . . . 19-1When You Do Not Know the Name of a Command or a Procedure . . . . 19-4

Chapter 20. Printing with SSP . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Printer Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Finding SSP Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2Using SSP Help Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2Using the Work with Spool File (WRKSPL) Command . . . . . . . . . . . . 20-2

Managing Printer Output — Command Summary . . . . . . . . . . . . . . . . 20-3Managing Printer Output — Complete Details . . . . . . . . . . . . . . . . . . 20-3

Changing Printer Output with a Control Command . . . . . . . . . . . . . . 20-4Changing Printer Output with an Option from a Menu . . . . . . . . . . . . 20-4Changing Printer Output with an Option from a Display . . . . . . . . . . . 20-4Holding Printer Output Using a Control Command . . . . . . . . . . . . . . 20-4Holding Printer Output Using an Option from a Menu . . . . . . . . . . . . 20-4Holding Printer Output Using an Option from a Display . . . . . . . . . . . 20-4Releasing Printer Output Using a Control Command . . . . . . . . . . . . . 20-4Releasing Printer Output Using an Option from a Menu . . . . . . . . . . . 20-5Releasing Printer Output Using an Option from a Display . . . . . . . . . . 20-5Deleting Printer Output Using a Control Command . . . . . . . . . . . . . . 20-5Deleting Printer Output Using an Option from a Menu . . . . . . . . . . . . 20-5Deleting Printer Output Using an Option from a Display . . . . . . . . . . . 20-5Copying Printer Output Using a Procedure . . . . . . . . . . . . . . . . . . 20-5

| Copying Printer Output Using an Option from a Display . . . . . . . . . . . 20-5| Displaying Printer Output Using an Option from a Display . . . . . . . . . 20-5

Balancing Spooled Output Between Printers Using a Procedure . . . . . . 20-6Working with Spool Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

Starting a Spool Writer Using a Control Command . . . . . . . . . . . . . . 20-6Starting a Spool Writer Using an Option from a Menu . . . . . . . . . . . . 20-7Stopping a Spool Writer Using a Control Command . . . . . . . . . . . . . 20-7Stopping a Spool Writer Using an Option from a Menu . . . . . . . . . . . 20-7Restarting a Spool Writer Using a Control Command . . . . . . . . . . . . 20-7Restarting a Spool Writer Using an Option from a Menu . . . . . . . . . . 20-7Assign a Printer as the System Printer . . . . . . . . . . . . . . . . . . . . . 20-8

Creating Printed Output — Selected Examples . . . . . . . . . . . . . . . . . 20-8Configuring Printer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

Chapter 21. Working with SSP Subsystems . . . . . . . . . . . . . . . . . 21-1Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

SSP Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1OS/400 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Starting an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 145: Iseries

Ending an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Displaying the Status of an SSP Subsystem . . . . . . . . . . . . . . . . . . . 21-2

Chapter 22. SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Menu Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Badge Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2Communications Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2Resource Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3Working with SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3

Chapter 23. Controlling SSP Jobs . . . . . . . . . . . . . . . . . . . . . . . 23-1Working With Current Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . 23-2Working with the History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

Chapter 24. Working with SSP Devices and Communications . . . . . . 24-1Displaying and Changing Device Status . . . . . . . . . . . . . . . . . . . . . . 24-1Printing Local Device Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1Displaying Communications Lines and Controllers . . . . . . . . . . . . . . . . 24-1Configuring Remote Communications Lines . . . . . . . . . . . . . . . . . . . 24-1

Chapter 25. Saving and Restoring the AS/400 Advanced 36 MachineInformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1

Saving and Restoring an AS/400 Advanced 36 Machine . . . . . . . . . . . . 25-1Saving the AS/400 Advanced 36 Machine Library . . . . . . . . . . . . . . 25-1Saving the AS/400 Advanced 36 Machine Object and Configuration Object 25-1Restoring the AS/400 Advanced 36 Machine Library . . . . . . . . . . . . . 25-2Restoring the AS/400 Advanced 36 Machine Object and Configuration

Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2Saving and Restoring the SSP Operating System, Licensed Programs, and

Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2Initializing Tapes to Save the SSP Operating System, Licensed Program

Product and Other SSP System Files . . . . . . . . . . . . . . . . . . . . . 25-2Saving the SSP Operating System Using the SAVELIBR Procedure . . . 25-3Saving the Licensed Program Products . . . . . . . . . . . . . . . . . . . . 25-3

Saving the Licensed Program Products Interactively . . . . . . . . . . . 25-5Creating a Procedure to Save Licensed Program Products . . . . . . . 25-7Saving the Licensed Program Products Using a Previously Created

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8Saving Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . 25-12

Saving Other SSP System Files Interactively . . . . . . . . . . . . . . 25-13Creating a Procedure to Save Other SSP System Files . . . . . . . . 25-16Saving the Other SSP System Files Using a Previously Created

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-18Restoring the SSP Operating System . . . . . . . . . . . . . . . . . . . . 25-18

Using the Restore Library Procedure to Restore the SSP OperatingSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19

Restoring the SSP Operating System Using the Start AS/400Advanced 36 Machine Command . . . . . . . . . . . . . . . . . . . . 25-21

Restoring the Licensed Program Products . . . . . . . . . . . . . . . . . . 25-24Restoring the Licensed Program Products Interactively . . . . . . . . . 25-25Creating a Procedure to Restore Licensed Program Products . . . . . 25-27Restoring the Licensed Program Products from a Previously Created

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-29

SSP for the OS/400 Operator

Page 146: Iseries

Restoring the Other SSP System Files . . . . . . . . . . . . . . . . . . . . 25-32Restoring the Other SSP System Files Interactively . . . . . . . . . . . 25-33Creating a Procedure to Restore the Other Saved SSP System Files 25-35Restoring the Other SSP System Files from a Previously Created

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-37

Chapter 26. Working with SSP Program Temporary Fixes . . . . . . . . 26-1AS/400 Advanced 36 Program Maintenance Strategy . . . . . . . . . . . . . . 26-1

Preventative Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1Cumulative PTF Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1

Corrective Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2Corrective Service SSP PTFs . . . . . . . . . . . . . . . . . . . . . . . . 26-2

Ordering SSP PTFs and PTF Information . . . . . . . . . . . . . . . . . . . . . 26-3Displaying or Printing Cumulative PTF Information . . . . . . . . . . . . . . . 26-3Installing Cumulative SSP PTF Packages . . . . . . . . . . . . . . . . . . . . 26-5Corrective SSP PTFs (Patches) . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5

Installing Corrective SSP PTFs from CD-ROM or Tape . . . . . . . . . . . 26-5| Installing Corrective SSP PTFs That Were Sent Electronically . . . . . . . 26-7| Getting Electronic Customer Support Up and Running . . . . . . . . . . 26-7| Getting ILAN Up and Running . . . . . . . . . . . . . . . . . . . . . . . . 26-7| Using DDM for PTFs Sent Electronically from the OS/400 operating| system to the SSP operating system . . . . . . . . . . . . . . . . . . . 26-7

Electronic Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . 26-9Installing SSP PTFs That Were Sent Electronically . . . . . . . . . . . . . 26-9

Installing a Saved PTF That Was Sent Electronically . . . . . . . . . . 26-13Displaying or Printing Corrective SSP PTF Information . . . . . . . . . . 26-14Removing Corrective SSP PTFs . . . . . . . . . . . . . . . . . . . . . . . 26-15

Mapping the TC Device ID to the CD-ROM Drive . . . . . . . . . . . . . . . 26-16What to Do if the Mapping Failed . . . . . . . . . . . . . . . . . . . . . . . . 26-17Changing the TC Device ID Back to a Tape Cartridge Drive . . . . . . . . . 26-17

Chapter 27. Establishing a Communications Link for RemoteWorkstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1

Using Remote Work Station Support . . . . . . . . . . . . . . . . . . . . . . . 27-1Establishing the Communications Link . . . . . . . . . . . . . . . . . . . . . 27-1Ending the Communications Link . . . . . . . . . . . . . . . . . . . . . . . . 27-2

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 147: Iseries

Starting an AS/400 Advanced 36 Machine

Chapter 15. Starting an AS/400 Advanced 36 Machine

Although the commands you use to start an AS/400 Advanced 36 machine areOS/400 commands, directions for starting your AS/400 Advanced 36 machines arein this chapter since you cannot use SSP without starting the AS/400 Advanced 36machine.

For directions on using SSP sign-on displays, see Chapter 2 of the Operating YourComputer–SSP Operating System book, SC21-8297.

Starting the AS/400 Advanced 36 Machine from the OS/400 Commandline

You use the Start AS/400 Advanced 36 Machine (STRM36) command to start anAS/400 Advanced 36 machine.

The STRM36 command starts an existing AS/400 Advanced 36 machine as a guestof the OS/400 operating system. Essentially, an IPL of the AS/400 Advanced 36machine is performed.

You can either type the command and the appropriate parameters on an OS/400command line or you can type the command and press F4. After you press F4,you can get information on all of the parameters by positioning the cursor on aparameter and pressing F1.

The AS/400 Advanced 36 machine must already be created. The AS/400Advanced 36 machine contains a copy of the last applied AS/400 Advanced 36machine configuration.

If you want to create an AS/400 Advanced 36 machine configuration, use theCreate AS/400 Advanced 36 Machine Configuration (CRTM36CFG) command. Formore information on the CRTM36CFG command, see the CL Reference book,SC41-4722.

Requirements for Using the Start AS/400 Advanced 36 MachineCommand

� If the SSP needs to be loaded onto the AS/400 Advanced 36 machine, aswould be the case if the AS/400 Advanced 36 machine was just created, thenIPLTYPE is a required parameter. Specify the device in which media (adiskette, tape or CD-ROM) that contains the SSP operating system is loaded.

� If an AS/400 Advanced 36 machine configuration has never been applied to themachine, and the machine was not created through a conversion of a 236/436AS/400 Advanced 36 machine definition to an AS/400 Advanced 36 machine,then APYM36CFG is a required parameter.

Copyright IBM Corp. 1995, 1996 15-1

Page 148: Iseries

Starting an AS/400 Advanced 36 Machine

Using the IPL Type (IPLTYPE) ParameterThis parameter specifies the type of IPL to perform and the device from which it isperformed. You can specify any of the following keywords for the parameter:

*M36 This is the default. This specifies to use the type of IPL (attendedor unattended) defined in the AS/400 Advanced 36 machine.

*UNATTEND An unattended IPL is performed from the fixed disk of the AS/400Advanced 36 machine. In an unattended IPL, the system operatorcannot sign on either to change the system date and time, or tospecify IPL overrides.

*ATTEND An attended IPL is performed from the fixed disk of the AS/400Advanced 36 machine. In an attended IPL, the system operatormust sign on to the AS/400 Advanced 36 machine. The systemdate and time of the AS/400 Advanced 36 machine can bechanged and IPL overrides can be specified.

*I1 An attended IPL is performed from the diskette drive. Fordirections on defining a diskette drive, see “Defining a DisketteDevice” on page 31-8.

*T1 An attended IPL is performed from the media drive defined for T1.For directions on defining a media drive, see “Defining a Tape orCD-ROM Device” on page 31-10.

*T2 An attended IPL is performed from the media drive defined for T2.For directions on defining a media drive, see “Defining a Tape orCD-ROM Device” on page 31-10.

*TC An attended IPL is performed from the media drive defined for TC.For directions on defining a media drive, see “Defining a Tape orCD-ROM Device” on page 31-10.

device-name Specify the name of the OS/400 device description from which youwant to IPL. An attended IPL is performed from the drive by thatname.

For information on how the IPLTYPE parameter affects the starting of an AS/400Advanced 36 machine, see Figure 15-1 on page 15-4.

Using the User Profile (USRPRF) ParameterThis parameter controls the OS/400 job attributes and the authority available to theAS/400 Advanced 36 server job. For information on AS/400 Advanced 36 serverjobs, see “Understanding Server Jobs” on page C-1.

If you sign on to an SSP display station that was automatically acquired by theAS/400 Advanced 36 machine or run an SSP batch job and:

� You use the RUN400 OCL statement, the job runs under the USRPRF userprofile.

� You send printed output to an OS/400 output queue, the printed output belongsto the USRPRF user ID instead of your user ID.

The possible values you can specify for the USRPRF parameter are:

*M36 This is the default. This specifies to use the user profile defined in theAS/400 Advanced 36 machine.

15-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 149: Iseries

Starting an AS/400 Advanced 36 Machine

user-profile-name Specify the name of the user profile to use.

For information on how the USRPRF parameter affects the starting of an AS/400Advanced 36 machine, see Figure 15-1 on page 15-4.

Using the Apply AS/400 Advanced 36 Machine Configuration(APYM36CFG) Parameter

The APYM36CFG parameter specifies which AS/400 Advanced 36 machine config-uration to apply to the AS/400 Advanced 36 machine before the machine is started.

Note: After you change an AS/400 Advanced 36 machine configuration with theChange AS/400 Advanced 36 Machine Configuration (CHGM36CFG)command, you must use the APYM36CFG parameter on the STRM36command to apply the changes to the AS/400 Advanced 36 machine. Thechanges will not affect an AS/400 Advanced 36 machine until you do this.For more information on using the CHGM36CFG command, seeChapter 31, “Changing Your AS/400 Advanced 36 Machine Configuration.”

The possible values you can specify for the APYM36CFG parameter are:

configuration-object-name Specify the name of an existing AS/400 Advanced 36machine configuration.

The name of the AS/400 Advanced 36 machine configuration can bequalified by one of the following library values:

*LIBL All libraries in the job's library list are searched until the firstmatch is found.

*CURLIB The current library for the job is searched. If no library isspecified as the current library for the job, the QGPL library issearched.

library-name Specify the name of the library to be searched.

For information on how the APYM36CFG parameter affects the starting of anAS/400 Advanced 36 machine, see Figure 15-1.

Chapter 15. Starting an AS/400 Advanced 36 Machine 15-3

Page 150: Iseries

Starting an AS/400 Advanced 36 Machine

Advanced 36 MachineConfiguration Object

Advanced 36 Machine Object

USRPRF

STRM36 APLYM36CFG(config name)

STRM36 USRPRF

Overwrite at IPL

CHGSYSVLDEVMAP

2. Display and printer devices3. Display and printer device

CRTM36CFGor

CHGM36CFG

attributes4. Tape and optical devices5. Diskette devices6. Communication lines

Applied Advanced 36Machine Configuration

Temporary Advanced 36Machine Configuration

1. Attributes: IPLTYPEand USRPRF

2. Display and printer devices

3. Display and printer deviceattributes

4. Tape and optical devices5. Diskette devices6. Communication lines

2. Display and printer devices3. Display and printer device

attributes

4. Tape and optical devices5. Diskette devices6. Communication lines

STRM36 IPLTYPE IPLTYPE

1. Attributes

1. Attributes

(user profile)

(IPL type)

Temporary

STRM36 USRPRF(*M36) IPLTYPE(*M36)

(SSP procedure)

RV3P219-0

Figure 15-1. How the STRM36 Parameters Affect an AS/400 Advanced 36 Machine

Starting an AS/400 Advanced 36 Machine — ExamplesExample 1

STRM36 M36(ADV36M)

This command performs an IPL of an AS/400 Advanced 36 machine named ADV36Mthat is located through the library list of the OS/400's job in which the STRM36command is run.

The IPL type and user profile are taken from the configuration last applied to theAS/400 Advanced 36 machine. You can display the current IPL type and userprofile by using the Display AS/400 Advanced 36 Machine (DSPM36) command.For information on using this command, see “Displaying a Machine” on page 32-2.

If you want the default values to be different than those stored in the AS/400Advanced 36 machine, change the IPL type and user profile values as follows:

1. Use the Change AS/400 Advanced 36 Machine Configuration (CHGM36CFG)command to change the IPL type and user profile in the machine configuration.

Note: You can use the DSPM36 command to determine the name of the lastmachine configuration object that was applied to the AS/400 Advanced36 machine.

2. Stop the machine. For directions, see Chapter 16, “Stopping an AS/400Advanced 36 Machine.”

3. Start the machine again using the APYM36CFG parameter on the STRM36command to apply that machine configuration to the machine.

Example 2

15-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 151: Iseries

Starting an AS/400 Advanced 36 Machine

STRM36 M36(MYLIB/ADVM36) IPLTYPE(\TC) USRPRF(QUSER) APYM36CFG(MYLIB/MYM36CFG)

Note: This is an example of how to load or reload #LIBRARY because of changesto the IPLTYPE parameter.

This command performs an IPL of an AS/400 Advanced 36 machine named ADVM36that is located in the library named MYLIB. The IPL is performed from the mediadrive configured for the AS/400 Advanced 36 machine as the tape cartridge (TC)drive. The IBM-defined user profile QUSER is used to define the OS/400 defaultauthority and job attributes of the AS/400 Advanced 36 machine. The AS/400Advanced 36 machine configuration named MYM36CFG which is located in the librarynamed MYLIB is applied to the AS/400 Advanced 36 machine.

Starting the AS/400 Advanced 36 Machine AutomaticallyIf you want your AS/400 Advanced 36 machines to start up automatically when youIPL your AS/400 system, you need to create a customized start-up program. Fordirections, see “Creating a Customized IPL Start-Up Program” on page 15-5.

How To Change a Configuration for an AS/400 Advanced 36 MachineThat Starts Automatically

Any AS/400 Advanced 36 machine you automatically start will always use the con-figuration information contained in the AS/400 Advanced 36 machine. You mayneed to apply a new configuration at some time in the future in order to change the:

� User profile for the AS/400 Advanced 36 machine

� Devices used by the AS/400 Advanced 36 machine

� Type of IPL that is done when the AS/400 Advanced 36 machine is started.

Because the AS/400 Advanced 36 machine is always active if you start it automat-ically, in order to apply changes to the AS/400 Advanced 36 machine configuration,you must:

1. Stop the AS/400 Advanced 36 machine.

For directions, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine.”

| 2. To apply the changed configuration, start the machine using the STRM36| command while specifying the APYM36CFG parameter.

You can use the USRPRF and IPLTYPE parameters on the STRM36 command totemporarily change the user profile or the type of IPL. The next time you do an IPLof the AS/400 Advanced 36 machine without specifying these parameters, thevalues in the machine configuration are used.

Creating a Customized IPL Start-Up ProgramTo change the IPL start-up program, complete the following steps from an OS/400command prompt unless directed otherwise:

1. If you do not already have an editor installed with which you can edit a sourcemember, install an editor. If you choose to install the PW1 licensed program(5716-PW1), see the Software Installation book, SC41-4120, for instructions.

2. If you do not already have a file in which to store your start-up program, createone as follows:

Chapter 15. Starting an AS/400 Advanced 36 Machine 15-5

Page 152: Iseries

Starting an AS/400 Advanced 36 Machine

a. Type

CRTLIB yourlib

where yourlib is the name of the library in which you want to store thestart-up program source member.

b. Press Enter .

3. If you do not already have a file in which to store your start-up program sourcemember, create one as follows:

a. Type

CRTSRCPF yourlib/yourfile

where yourlib is the name of the library in which you want to store thestart-up program source member and yourfile is the name of the file inwhich you want to store your start-up program source.

b. Press Enter .

4. Retrieve the shipped IPL start-up program source into your own source file asfollows:

a. Type

RTVCLSRC PGM(QSYS/QSTRUP) SRCFILE(yourlib/yourfile)

Where yourlib is the name of the library in which you want to store thestart-up program source member and yourfile is the name of the file inwhich you want to store your start-up program source.

b. Press Enter .

5. You need to add the following lines to your start-up program source file.

QSYS/STRM36 library-name/machine-nameMONMSG MSGID(CPFðððð)

where library-name is the name of the library that contains the AS/400Advanced 36 machine and machine-name is the name of the AS/400 Advanced36 machine you want to start automatically.

Notes:

a. The number .1/, shown in reverse highlighting in Figure 15-2 onpage 15-8, indicates where to add the lines to the sample start-up programto start the AS/400 Advanced 36 machine automatically.

b. Repeat step 5 on page 15-6 for each AS/400 Advanced 36 machine thatyou want to start automatically.

6. Create your customized start-up program:

a. Type

CRTCLPGM

b. Press F4.

c. In the Program field, type

yourpgm

where yourpgm is the name of your program.

d. In the first library field, type the library name you used for yourlib.

e. In the Source file field, type the name you used for yourfile.

15-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 153: Iseries

Starting an AS/400 Advanced 36 Machine

f. In the second library field, type the library name you used for yourlib.

g. In the Source member field, type

QSTRUP

h. Press Enter .

7. Define the start-up program at IPL time to be your customized start-upprogram:

a. Type

CHGSYSVAL

b. Press F4.

8. In the System value field, type

QSTRUPPGM

9. In the New value field, type

yourpgm yourlib

where yourpgm is the name of your program and yourlib is the name of thelibrary where you stored your start-up program.

10. Press Enter .

Sample QSYS/QSTRUP Start-up ProgramFigure 15-2 on page 15-8 shows the source for a CL program highlighted with thechanges you make. The changed start-up program resides on OS/400. You willadd two lines where .1/ is shown in reverse highlighting in Figure 15-2 onpage 15-8. You replace library-name with the name of the library in which theAS/400 Advanced 36 machine resides, and you replace machine-name with thename of the AS/400 Advanced 36 machine that you want to start. You can addadditional lines for your other AS/400 Advanced 36 machines.

Chapter 15. Starting an AS/400 Advanced 36 Machine 15-7

Page 154: Iseries

Starting an AS/400 Advanced 36 Machine

Figure 15-2. Example of Modified QSYS/QSTRUP Startup Program. This example program starts a single AS/400Advanced 36 machine whenever the AS/400 is IPLed.SEQNBR\... ... 1 ... ... 2 ... ... 3 ... ... 4 ... ... 5 ... ... 6 ... ... 7 ... ... 8 1ðð /\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/ 2ðð /\ \/3ðð /\5716SS1 V3R6Mð 951222 RTVCLSRC Output ð4/ð1/96 14:ð3:47 \/

4ðð /\ \/5ðð /\ Program name . . . . . . . . . . . . . . : QSTRUP PN\/6ðð /\ Library name . . . . . . . . . . . . . . : QSYS PL\/7ðð /\ Original source file . . . . . . . . . . : SN\/8ðð /\ Library name . . . . . . . . . . . . . . : SL\/9ðð /\ Original source member . . . . . . . . . : SM\/

1ððð /\ Source File change \/ 11ðð /\ date/time SC\/ 12ðð /\ Patch option . . . . . . . . . . . . . . : \NOPATCH PO\/ 13ðð /\ User profile . . . . . . . . . . . . . . : \USER UP\/ 14ðð /\ Text . . . : TX\/ 15ðð /\ Owner . . . . . . . . . . . . . . . . . : QSYS OW\/ 16ðð /\ Patch change ID . . . . . . . . . . . . : PC\/ 17ðð /\ Patch APAR ID . . . . . . . . . . . . . : PA\/ 18ðð /\ User mod flag . . . . . . . . . . . . . : \NO UM\/ 19ðð /\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/ 2ððð PGM 21ðð DCL VAR(&STRWTRS) TYPE(\CHAR) LEN(1) 22ðð DCL VAR(&CTLSBSD) TYPE(\CHAR) LEN(2ð) 23ðð DCL VAR(&CPYR) TYPE(\CHAR) LEN(9ð) VALUE('+ 24ðð 5716-SS1 (C) COPYRIGHT IBM CORP 198ð, 1995. + 25ðð LICENSED MATERIAL - PROGRAM PROPERTY OF IBM') 26ðð 27ðð QSYS/STRSBS SBSD(QSPL) 28ðð MONMSG MSGID(CPFðððð) 29ðð 3ððð QSYS/RLSJOBQ JOBQ(QGPL/QS36MRT) 31ðð MONMSG MSGID(CPFðððð) 32ðð 33ðð QSYS/RLSJOBQ JOBQ(QGPL/QS36EVOKE) 34ðð MONMSG MSGID(CPFðððð) 35ðð 36ðð QSYS/STRCLNUP 37ðð MONMSG MSGID(CPFðððð) 38ðð 39ðð 4ððð QSYS/RTVSYSVAL SYSVAL(QCTLSBSD) RTNVAR(&CTLSBSD) 41ðð IF ((&CTLSBSD \NE 'QCTL QSYS ') + 42ðð \AND (&CTLSBSD \NE 'QCTL QGPL ')) GOTO DONE 43ðð 44ðð QSYS/STRSBS SBSD(QINTER) 45ðð MONMSG MSGID(CPFðððð) 46ðð 47ðð QSYS/STRSBS SBSD(QBATCH) 48ðð MONMSG MSGID(CPFðððð) 49ðð 5ððð QSYS/STRSBS SBSD(QCMN) 51ðð MONMSG MSGID(CPFðððð) 52ðð 53ðð QSYS/STRSBS SBSD(QSERVER) 54ðð MONMSG MSGID(CPFðððð) 55ðð 56ðð 57ðð 58ðð 59ðð DONE: 6ððð .1/ QSYS/STRM36 library-name/machine-name 61ðð MONMSG MSGID(CPFðððð) 62ðð 63ðð QSYS/RTVSYSVAL SYSVAL(QSTRPRTWTR) RTNVAR(&STRWTRS) 64ðð IF (&STRWTRS = 'ð') GOTO NOWTRS 65ðð 66ðð CALL PGM(QSYS/QWCSWTRS) 67ðð MONMSG MSGID(CPFðððð) 68ðð 69ðð NOWTRS: 7ððð RETURN 71ðð CHGVAR VAR(&CPYR) VALUE(&CPYR) 72ðð /\ Needed to include CPYR variable in program. \/ 73ðð ENDPGM

15-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 155: Iseries

Starting an AS/400 Advanced 36 Machine

For information on automatically starting ILAN communications, see “AutomaticallyStarting ILAN Communications” on page 29-6.

For information on manually starting ILAN communications, see “Manually Startingthe ILAN” on page 29-3.

Chapter 15. Starting an AS/400 Advanced 36 Machine 15-9

Page 156: Iseries

Starting an AS/400 Advanced 36 Machine

15-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 157: Iseries

Stopping SSP

Chapter 16. Stopping an AS/400 Advanced 36 Machine

This chapter describes the steps that you can use to stop your AS/400 Advanced36 machine. You should always use the SSP POWER OFF command to stop yourAS/400 Advanced 36 machines. If the AS/400 Advanced 36 machine is stopped inany other way:

� Jobs running in the AS/400 Advanced 36 machine will not end normally.

� Opened files on the AS/400 Advanced 36 disk will not close normally and mightbe in an unknown condition.

This chapter discusses how to:

� Send a message to all users informing them what is about to happen.

� Put the AS/400 Advanced 36 machine in a dedicated state.

� Stop an AS/400 Advanced 36 machine from the SSP system console undernormal circumstances.

� Stop an AS/400 Advanced 36 machine from the OS/400 operating system onlywhen you cannot stop it normally from the SSP system console.

Putting the AS/400 Advanced 36 Machine In a Dedicated StateCertain operations, such as stopping an AS/400 Advanced 36 machine, require theAS/400 Advanced 36 machine to be in a dedicated state.

Note: The following steps refer to the SSP command display and the SSP consoledisplay. The SSP command display is the display where an operator candisplay or send messages and use control commands and procedures tostart and control jobs. The SSP console display is a display that can onlybe requested from the SSP system console. From this display, the operatorcan control the operation of the AS/400 Advanced 36 machine. For moreinformation on the SSP command display and the SSP console display andhow to switch between the two, see “Using the SSP Console Display” onpage 17-4.

To put an AS/400 Advanced 36 machine in a dedicated state:

1. Ensure that all users are signed off except for the user ID signed on to the SSPsystem console.

a. Send a message to all users to inform them that you are going to put thesystem in a dedicated state:

1) On the command display of the SSP system console, type:

MSG ALL, SYSTEM BEING PLACED IN DEDICATED STATE, PLEASE SIGN OFF NOW

2) Press Enter .

Review any replies sent by the users. A critical job may need to becompleted before you stop the system.

b. Verify that all users have signed off the system:

1) On the command display of the SSP system console, type

STATUS WORKSTN

Copyright IBM Corp. 1995, 1996 16-1

Page 158: Iseries

Stopping SSP

Or,

D W

2) Press Enter .

c. If users are still signed on, you can send them another message or useoption 9 (Cancel a session) on the DEVICES menu to sign off the user.

d. If you used option 9 to cancel a session, press Cmd3 .

e. Press Cmd3 again to end the display.

2. On the SSP console display, type:

STOP SYSTEM (or P S)

3. Press Enter .

You will immediately receive the following message at the system console:

SYS-5676 STOP SYSTEM command in progress.

After a few minutes the following message should be shown at the systemconsole:

SYS-5677 STOP SYSTEM command has completed.

4. If the SYS-5677 message is not shown,

a. On the SSP console display, type

START SYSTEM (or S S)

b. Press Enter .

c. Go to Appendix E, “Preparing SSP for Dedicated State” on page E-1, andperform the steps defined there.

5. When the following message is shown:

SYS-5677 STOP SYSTEM command has completed

the AS/400 Advanced 36 machine is in a dedicated state.

Stopping an AS/400 Advanced 36 Machine from the SSP SystemConsole

This is the preferred method for stopping the AS/400 Advanced 36 machine.

1. Put the AS/400 Advanced 36 machine in a dedicated state. For directions, see“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.

2. Type the following command on the SSP console display:

POWER OFF

3. The Message POWER OFF command successful should be shown at the SSPconsole display. A few minutes later the AS/400 Advanced 36 machine ends.

Each AS/400 Advanced 36 machine should be stopped in this way before youpower down or IPL the AS/400 system.

16-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 159: Iseries

Stopping SSP

Stopping an AS/400 Advanced 36 Machine from the OS/400 OperatingSystem

| The End AS/400 Advanced 36 Machine (ENDM36) CL command can be used to| abnormally stop an AS/400 Advanced 36 machine.

Important Note

You should only use the ENDM36 command if you cannot stop the AS/400Advanced 36 machine from the SSP console using the POWER OFF command.When you use the ENDM36 command to stop the AS/400 Advanced 36machine:

� Jobs running in the AS/400 Advanced 36 machine will not end normally.

� Opened files on the AS/400 Advanced 36 disk will not close normally andmight be in an unknown condition.

The ENDM36 command ends (stops) the AS/400 Advanced 36 machine imme-diately.

To use the ENDM36 command:

1. On any OS/400 command line, type

ENDM36

2. Press F4 to show the prompt display for the command.

3. In the Machine field, type the name of the AS/400 Advanced 36 machine thatyou want to end.

4. In the Library field, type the name of the library that contains the AS/400Advanced 36 machine, *LIBL if your library list is to be searched for the AS/400Advanced 36 machine or *CURLIB if the current library is to be searched forthe AS/400 Advanced 36 machine.

5. In the Dump the machine field, type

\YES

Specifying *YES in the Dump the machine field, prior to ending the AS/400Advanced 36 machine, causes the OS/400 operating system to attempt todump the contents of the AS/400 Advanced 36 machine to disk. A message issent to the QSYSOPR message queue. The message indicates whether thedump was successful. If the dump was created, the message tells you the typeof object the dump was written to, the name of the object and the library theobject is located in.

You can use either the OS/400 Dump Object (DMPOBJ) command or theOS/400 Dump System Object (DMPSYSOBJ) command to copy the dump to aspool file for viewing or printing. You can use the OS/400 Save Object(SAVOBJ) command to save the object that contains the dump to tape, disketteor a *SAVF.

If you call your service representative to report the problem, this dump will bevery helpful in solving the problem.

6. Press Enter .

The Confirm End of Machine display is shown.

Chapter 16. Stopping an AS/400 Advanced 36 Machine 16-3

Page 160: Iseries

Stopping SSP

7. Press Enter .

The AS/400 Advanced 36 machine is ended.

Two examples of using the ENDM36 command are as follows:

Example 1

ENDM36 M36(MYM36)

This command immediately ends an AS/400 Advanced 36 machine which is namedMYM36, located through the library list of the OS/400 job in which the command isrun. A main storage dump of the AS/400 Advanced 36 machine is not generatedbecause the default is *NO.

Example 2

ENDM36 M36(MYLIB/MYM36) DUMP(\YES)

This command immediately ends an AS/400 Advanced 36 machine named MYM36,located in a library named MYLIB. A main storage dump of the AS/400 Advanced36 machine is generated while the AS/400 Advanced 36 machine is ending.

16-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 161: Iseries

Using SSP Console, Subconsoles

Chapter 17. Operating the SSP Console and SSPSubconsoles

This chapter describes how to use the SSP console and SSP subconsole after yousign on. You can:

� Transfer the SSP console function to an alternative SSP console (CONSOLEGIVE control command and CONSOLE TAKE control command).

� Use the SSP subconsole display station.

� Use the SSP console display station.

For information about the differences among data displays, command displays, sub-console displays, and console displays, refer to the Using Your Display Station –Advanced 36 book, SC21-0209.

The SSP Console: A Way of Controlling the AS/400 Advanced 36Machine

An SSP console, like other display stations, is made up of a keyboard and adisplay. Using the keyboard and display, the SSP console operator can enter infor-mation into and retrieve information from the system. However, in addition to this,you can also monitor and control system activity, because during system configura-tion, this display station was selected to serve as the SSP console. As an SSPconsole operator, you can:

� Use it as a data display station that is controlled by a program

� Use it as an SSP console to:

– Control all jobs entered at all display stations.

– Control all printers from this display station.

– Control all jobs on the system.

– Control the entire operation of the system.

You can also transfer control of the SSP console to someone else's commanddisplay station or SSP subconsole, provided their display station was configured asan alternative SSP console. For example, you may want to do this if you are plan-ning to be out of the office for a while. For more information about transferring thecontrol of the SSP console to an alternative SSP console, refer to “Transferring theSSP Console Function to an Alternative SSP Console” on page 17-2.

The SSP Subconsole: A Way of Controlling SSP PrintersDuring system configuration, you may have had one or more display stations con-figured as an SSP subconsole. An SSP subconsole operator may then use theSSP subconsole:

� As a data display station controlled by a program.

� As a command display station to control jobs entered at this display station.

� As an SSP subconsole to control one or more printers from this display station.

Copyright IBM Corp. 1995, 1996 17-1

Page 162: Iseries

Using SSP Console, Subconsoles

For more information about data display stations and command display stations,refer to the Using Your Display Station – Advanced 36 book, SC21-0209.

Transferring the SSP Console Function to an Alternative SSP ConsoleThe SSP console and the alternative SSP consoles are specified during systemconfiguration. You can transfer the SSP console function to an alternative SSPconsole:

� During an attended IPL.

� If you are using the SSP console, and you find it necessary to leave the SSPconsole (you may want another operator to control the system in yourabsence).

� If the SSP console does not work.

Transferring the SSP Console Function During an Attended IPLTurn on the display station that was specified as an alternative SSP console and isto become the SSP console. The following message .A/ appears:

à@ ð IPL

IPL is in progress. please wait. .A/ CONSOLE .B/

á ñ

1. Type CONSOLE as shown in .B/.

2. Press Enter .

The IPL Sign On display is shown.

3. Complete the IPL Sign On display.

4. Press Enter .

The workstation can now be operated as the SSP console.

17-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 163: Iseries

Using SSP Console, Subconsoles

Transferring the SSP Console Function When the SSP Console Is inOperation

To transfer the SSP console function to an alternative SSP console, the CONSOLEGIVE command must be entered at the SSP console and the CONSOLE TAKE (orCONSOLE) command must be entered at an alternative SSP console.

Note: If the CONSOLE GIVE command is entered at the SSP console and thenthe CONSOLE TAKE command is entered at the SSP console, theCONSOLE GIVE command is canceled.

Transferring the SSP Console Function to an Alternative SSP ConsoleWhen the Console Is in Operation

1. At the SSP console, on either a Command display or a Console display, type

CONSOLE GIVE

2. Press the Help key.

The Status Work Station display is shown.

3. Type the ID of the display station that was specified as an alternative SSPconsole and is to become the SSP console. The ID is shown in the WS-IDcolumn, and the alternative SSP console (Alt Console) is shown in the TYPEcolumn.

Note: If you do not type the ID, any display station that was defined as analternative SSP console during system configuration can become theSSP console.

4. Press Enter .

Making an Alternative SSP Console the SSP ConsoleTo have an alternative SSP console become the SSP console, use a commanddisplay at the alternative SSP console. For this example, the Main System Helpmenu is used.

1. On a command display at an alternative SSP console, type

CONSOLE

Or,

CONSOLE TAKE

Note: If a display station ID was entered with the CONSOLE GIVE commandat the SSP console, only the alternative SSP console with that displaystation ID can be used to enter the CONSOLE or CONSOLE TAKEcommand.

If a display station ID was not entered with the CONSOLE GIVE command atthe SSP console, any alternative SSP console can be used to enter theCONSOLE or CONSOLE TAKE command.

2. Press Enter .

The SSP Console display is shown.

Note: The SSP console function is transferred if a command display is used atthe SSP console or if the SSP console is signed off, in error, or turnedoff.

Chapter 17. Operating the SSP Console and SSP Subconsoles 17-3

Page 164: Iseries

Using SSP Console, Subconsoles

Transferring the SSP Console Function When the SSP Console Is Notin Operation

When the SSP console does not work, type CONSOLE or CONSOLE TAKE on thecommand display at any alternative SSP console. The alternative SSP console canthen operate as the SSP console.

Note: If you have interrupted a job (Inquiry Options display), you cannot use theCONSOLE command. For more information about the Inquiry Optionsdisplay, refer to the Using Your Display Station – Advanced 36 book,SC21-0209.

Using the SSP Console DisplayThe SSP Console display can be displayed only at the display station designatedas the SSP console. To request this display from a command display:

1. Press the System Request key documented in the user's guide for your work-station. A blank line is shown at the bottom of the display.

2. Press Enter with the input line blank. A display similar to the following SSPConsole display is shown:

à@ ðSYSTEM CONSOLE W1

á ñ

You can use the SSP Console display to receive and send messages, and to enterall control commands except JOBQ, MENU, MODE, and OFF. The control com-mands enable you to control AS/400 Advanced 36 machine activity.

You cannot use the SSP Console display, or any display that has the wordCONSOLE in the upper-right corner or the lower-right corner, to enter procedurecommands. These commands must be entered on a Command display. To returnto a display after using the SSP Console display:

1. Press the System Request key documented in the user's guide for your work-station. A blank line is shown at the bottom of the display.

2. Press Enter with the input line blank.

17-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 165: Iseries

Using SSP Console, Subconsoles

You return to the original display.

Requesting a Help Menu from the SSP Console DisplayTo request a help menu when the SSP Console display is shown, do as follows:

� Press Cmd5 , or type HELP MAIN and press Enter to display the Main helpmenu.

� Type the name of a help menu and press the Help key.

� Type HELP, leave one space, and type the name of a help menu. Then, pressEnter .

Using the Subconsole DisplayThe Subconsole display can be displayed only at a display station that was config-ured as a subconsole (a display station that controls one or more printers). Torequest this display:

1. Press the System Request key documented in the user's guide for your work-station. A blank line is shown at the bottom of the display.

2. Press Enter with the input line blank.

A display similar to the following Subconsole display is shown:

à@ ðSYSTEM SUB CONSOLE W2

á ñ

You can use the Subconsole display to receive and send messages, and to entercontrol commands except JOBQ, MENU, MODE, and OFF. You cannot entercontrol commands that are restricted to the system console, such as STARTSYSTEM and STOP SYSTEM. You may want to use this display to monitorsystem activity, respond to messages, or send messages when the SSP console isbeing repaired or replaced.

You cannot use the Subconsole display, or any display that has the word SUB-CONSOLE in the upper-right corner or the lower-right corner, to enter procedurecommands. These commands must be entered on a command display.

Chapter 17. Operating the SSP Console and SSP Subconsoles 17-5

Page 166: Iseries

Using SSP Console, Subconsoles

To return to a display after using the Subconsole display:

1. Press the System Request key documented in the user's guide for your work-station. A blank line is shown at the bottom of the display.

2. Press Enter with the input line blank.

You return to the original display.

Requesting a Help Menu from the Subconsole DisplayTo request a help menu when the Subconsole display is shown, do one of the fol-lowing:

� Press Cmd5 , or type HELP MAIN and press Enter , to display the Main helpmenu.

� Type the name of a help menu and press the Help key.

� Type HELP, leave one space, and type the name of a help menu. Then, pressEnter .

17-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 167: Iseries

SSP Messages

Chapter 18. Handling SSP Messages

A message is a way for SSP operating system to communicate with you and foryou to communicate with display station operators.

This chapter contains information about:

� The kinds of messages that are displayed

– Messages that instruct you to perform an action

– Messages that require a response

� Displaying additional information for a message

� Informational messages at the SSP console

� Displaying messages that are waiting

� Displaying messages at the SSP console or subconsole

How You Know That You Have an SSP MessageThe following summarizes how you know that SSP or another operator has sentyou a message:

� A blinking 4-digit number appears in the lower-left corner of your display, andthe Input Inhibited light is on at your display station. You have a keyboardmessage waiting to be displayed. For information on keyboard errors, see“SSP Keyboard Error Messages” on page 18-10 or see “Displaying KeyboardMessages” in the Using Your Display Station – Advanced 36 book, SC21-0209.

� A message appears and an alarm may sound. A procedure that you arerunning displayed the message. For information on keyboard errors, see “SSPKeyboard Error Messages” on page 18-10 or see “Understanding the Kinds ofMessages that Are Displayed” in the Using Your Display Station – Advanced 36book, SC21-0209.

� An alarm sounds and the Message Waiting light is on at your display station.Another operator or a job that is running sent you a message. See “DisplayingSSP Messages at the SSP Console or Subconsole” on page 18-6 in this bookor “Displaying Messages that Are Waiting” in the Using Your Display Station –Advanced 36 book, SC21-0209.

When you want to communicate with another display station operator, see “SendingSSP Messages” on page 18-9.

When you want to display local or remote messages while in a Display StationPass-Through session, see “Displaying Messages While in a Display Station Pass-Through Session” in the Using Your Display Station – Advanced 36 book,SC21-0209.

Copyright IBM Corp. 1995, 1996 18-1

Page 168: Iseries

SSP Messages

Types of SSP MessagesWhen an alarm sounds and a message appears, or if there is no alarm but amessage appears, the message may:

� Not require a response since it is an informational message

Note: Informational messages are described later in this chapter.

� Instruct you to perform an action

� Require a response

Messages That Instruct You to Perform an ActionSSP may display messages that instruct you to perform an action. For example:

End of volume-insert next diskette

Printer P1 is not ready

To respond to these messages, perform the action that is required.

Messages That Require a ResponseSSP displays a message for various reasons. For example, you might use acommand or a procedure that requests SSP to perform an action that is notallowed. When this happens, you need to enter a response to the message. Themessage has an identifier, options that you can enter, and text that explains themessage. Following is an example of a message that requires a response:

RTSP033-0

A BB

F C

D E

You can have SSP respond to some messages for you. This is called automaticresponse. For more information on automatic response, see “NOHALT Procedure”in the S/36 System Reference book, SC21-9020.

18-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 169: Iseries

SSP Messages

� The message identifier .A/ is 3- or 4-alphabetic characters followed by a dashand four numbers. Each message that has an identifier, other than USER, isdescribed in a messages book. Figure 18-1 on page 18-3 shows the char-acter code, the code meaning, and the manual where the messages aredescribed:

Figure 18-1. Character Codes and Meanings for Messages

Code Meaning Book

ASM Assembler S/36 Assembler Messages book, SC21-7942

BAS BASIC S/36 BASIC Messages book, SC21-7943

BGU Business graphics utilities S/36 System Messages book, SC21-7938

CBL COBOL S/36 COBOL Messages book, SC21-7941

CGU Character generator utility S/36 Character Graphic Utility Guide (Japan only) book,SC09-1055

CNFG Configuration S/36 System Messages book, SC21-7938

DDM Distributed data management S/36 Distributed Data Management Guide book, SC21-8011

DFU Data file utility S/36 Utilities Messages book, SC21-7939, General Informa-tion for SSP Operating System book, SC21-8299

DSNX Distributed systems node executive S/36 Communications and Systems Management Guidebook, SC21-8010

EMU, ESU 3270 device emulation S/36 3270 Device Emulation Messages book, SC21-7945

FORT FORTRAN S/36 FORTRAN IV Messages book, SC21-9055

FTS File transfer subroutine S/36 Using System/36 Communications book, SC21-9082

KBD Keyboard S/36 System Messages book, SC21-7938

MIGR Transition Aid Operating Your Computer–SSP Operating System,SC21-8297

NRD Network resource directory S/36 Distributed Data Management Guide book, SC21-8011

RJE Remote job entry S/36 Multiple Session Remote Job Entry Messages book,SC21-7944

RPG RPG II S/36 RPG II Messages book, SC21-7940 General Informa-tion for SSP Operating System book, SC21-8299

SDA Screen design aid S/36 Utilities Messages book, SC21-7939

SEU Source entry utility S/36 Utilities Messages book, SC21-7939

SORT Sort program System Messages–SSP Addendum book, SC21-8291

SRTX IGC sort utility S/36 Ideographic Sort Guide (Japan only) book, SC09-1054

SYS System support program product System Messages–SSP Addendum book, SC21-8291,General Information for SSP Operating System book,SC21-8299

VASP Value-Added Software feature Using Value-Added Software Package book, SC21-8368

WSU Work station utility S/36 Utilities Messages book, SC21-7939

The messages are listed in an ascending sequence within each book by the4-digit number. This number is called a message identification code.

� The options .B/ you can use to respond to the message are shown within theparentheses. Each message shows only the options that are allowed.

The following describes what generally happens when you select an option torespond to a message. Because each message has a different description,always refer to the Options part of each message description in the appropriatemessages book for specific details.

Chapter 18. Handling SSP Messages 18-3

Page 170: Iseries

SSP Messages

Option 0: When you select this option, generally the error is ignored and thejob continues.

Option 1: When you select this option, generally the operation that caused theerror is retried and you can continue the job.

Option 2: When you select this option, generally the job step is ended. If thisoption ends the job step, the job continues with the next job step.

Option 3: When you select this option, the job is canceled.

Option D: This option is available when option 3 is displayed; however, optionD is not displayed and is not described in the message description. When youselect option D, the contents of main storage and System/36 Emulator controlblock storage are copied into the dump area on disk. SSP actions describedfor option 3 occur.

Option H: This option is available when option 3 is displayed if you are using ahelp display. When you select this option, the display where you made theerror is shown again. You can then correct the error and continue your job.

� The message text .C/.

� Three periods .D/ at the end of the message text indicate there is additionalinformation that you can display for the message. If you press Enter or theHelp key without typing an option number, the additional message informationdisplay is shown.

� Use the message identifier .A/ to refer to the message description in theappropriate messages book (see Figure 18-1 on page 18-3). For some prob-lems, additional messages are sent to the SSP Console display that include an8-character system reference code in the message text .C/. If you are unableto solve the problem, refer to the appropriate system problem determinationbook. If you need to call for service, record the system reference codes(SRCs) by pressing the Print key. Give the printout to your service represen-tative.

� If you do not display the additional message information display, type yourresponse on the entry line .F/ and press Enter .

If you are using the Console display, you must respond to the message with theREPLY command, which is described later in this chapter.

18-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 171: Iseries

SSP Messages

Additional Information for a MessageFollowing is an example of an Additional Message Information display:

à@ ðADDITIONAL MESSAGE INFORMATION W1

──┐SYS-112ð Options (123) │ .G/Dedicated program $CNDED cannot be loaded now... │ ──┘ ───┐There are other programs or system tasks active at this time. │Select option 1 to retry; the other programs and task may have ended. │Select option 2 to end the job step; 3 to cancel the job. │ │ .H/ │ │If more information is needed before responding to the message, │refer to the appropriate messages book. ───┘

The allowed options are listed in parentheses.Option:.I/

á ñ

Note: See Figure 18-1 on page 18-3 for information on which book is appropriateto use for information on the messages.

� The message .G/ is shown again.

� Additional information for the message .H/ is shown.

� Type an option number .I/.

� Press Enter to respond to the message.

Informational Messages at the SSP ConsoleAn informational message could be displayed at your display station by an SSPprocedure or by a procedure that was written by a programmer.

Note: Any type of message sent to the SSP Console is also logged to the Historyfile.

The following messages are examples of informational messages because they donot require you to enter a response:

� LISTLIBR procedure is running (LISTLIBR is an SSP operating system proce-dure).

� PAYROLL procedure is running (PAYROLL could be a procedure that waswritten by a programmer).

Chapter 18. Handling SSP Messages 18-5

Page 172: Iseries

SSP Messages

Specifying That Informational Messages Are Not to Be Displayedat the SSP ConsoleIf you are using the SSP console, enter the INFOMSG NO command on acommand display. Then, if you do not want to use the REPLY command to replyto informational messages when they appear at the console display:

1. Type INFOMSG NO (on the console display).

2. Press Enter .

Notes:

a. After you enter the INFOMSG NO command, informational messages thatare responses to a command, such as CANCEL command successful, aredisplayed. An informational message such as Payroll procedure isrunning is not displayed.

b. If an alarm sounds and no apparent message has been sent to the consoledisplay, the job that sent the message has ended and the message wasremoved. This happens if, during SSP configuration, the option to keepinformational messages was not selected.

c. After you have used the INFOMSG NO command to prevent most informa-tional messages from being displayed, you can use the INFOMSGcommand to indicate that most informational messages are to be displayed.

Displaying SSP Messages at the SSP Console or SubconsoleTo display a message that was sent to the SSP Console display when you areusing a command display or when you are running a job, switch to the SSPconsole display or a Subconsole display. To switch:

1. Press the System Request key documented in the user's guide for your work-station. A blank line is shown at the bottom of the display.

2. Press Enter with the input line left blank. A console or subconsole display isshown with the message displayed.

To display messages when you are using the Console display, press Enter .

If the Message Waiting indicator stays on, one of the following conditions applies:

� The display is full of messages that have not been replied to. See “Replying toSSP Messages at the SSP Console or Subconsole” on page 18-7.

� A job that is running may have displayed a message. Return to the commanddisplay.

18-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 173: Iseries

SSP Messages

Replying to SSP Messages at the SSP Console or SubconsoleThe display you use when you reply to a message at the Console display and theSubconsole display contains a console roll area, message lines, and entry lines.Following is an example of a Console display:

à@ ðSYSTEM CONSOLE W1

ð1 PAYROLL is running ───┐ │ │ \\ Enter volume ID for output diskette │ S P │

START command successful │ ð4 SYS-14ð5 Options (ð12) │ .A/

Do you want spool separator pages on P1 ... │ 3,PMODS │

REPLY command successful │ 2 │

REPLY command successful │ ð5 SYS-9918 Options (ð ) │ W3171143

Magnetic tape error, SCR 638ðCCð6... │ ───┘.B/

__ .C/

á ñ

� The console roll area .A/ can contain messages sent from SSP or anotheroperator, and information that you have entered on the Console display. Whenthis area is full, the old (top) entries roll up and off the display and the newentries appear at the bottom of the display.

Messages that require a reply, which you have not replied to, will not roll off thedisplay. A message is displayed if the display is full of messages that youhave not replied to. You must reply to some of the messages to get any newmessages. If you do not reply to any of the messages, SSP saves the mes-sages that are waiting to be displayed.

� The message lines .B/ contain the most recently displayed messages.

� The entry lines .C/ are two lines on which you type commands and reply tomessages.

After a message is displayed on the Console display or the Subconsole display,you can:

� Reply to a message that has a reply ID.� Reply to a message that has a reply ID and response options.� Reply to all informational messages so they can be removed from the display.� Clear the display of all messages that you have replied to.

A reply ID is a 2-digit number that appears in the first two columns on the left sideof the display. After you reply to a message, the reply ID is replaced by two aster-isks (**).

Chapter 18. Handling SSP Messages 18-7

Page 174: Iseries

SSP Messages

Replying to Messages - ExampleFollowing is an example of messages displayed on the Console display, and how toreply to the messages:

à@ ðSYSTEM CONSOLE W1

ð1 PAYROLL is running .A/

\\ Enter volume ID for output diskette .C/ S P

START command successful ð4 SYS-14ð5 Options (ð12) .B/

Do you want spool separator pages on P1 . . . 3,PMODS

REPLY command successful ──┐ 2 │ .C/

REPLY command successful ──┘ ð5 SYS-9918 Options (ð ) .E/ .D/ W3171143

Magnetic tape error, SCR 638ðCCð6....F/

á ñ

� Message .A/ is an informational message. No options are displayed. Themessage has a reply ID of 01.

To reply to message 01, type one of the following:

– REPLY 01 – R 1 – 1

To reply to all informational messages that have a reply ID, type one of thefollowing:

– REPLY I – R I

If you do not want informational messages to be displayed, use the INFOMSGNO command. See “Specifying That Informational Messages Are Not to BeDisplayed” in the Using Your Display Station – Advanced 36 book, SC21-0209.

� Message .B/ (SYS-1405) has a reply ID of 04 and requires you to type anoption (012) when you reply. The three periods (...) indicate there is additionalinformation for this message.

To reply to this message with a 1 option, type one of the following:

– REPLY 04,1

– R 4,1

– 4,1

To display the additional information for this message, before you reply to it:

1. On the SSP command prompt, type

18-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 175: Iseries

SSP Messages

4 (or ð4)

2. Press Enter .

Possible options that could be displayed for a message and their meanings areexplained in “Messages That Require a Response” on page 18-2.

� These messages .C/ are responses to messages or messages that do notrequire a response. To clear (remove from the display) these messages andmessages that have been replied to, type one of the following:

– REPLY C – R C

� This is the 8-character ID .D/ of the job that received this message. This fieldshows SYSTEM if a message was issued by an SSP function.

� Use the message identifier .E/ to refer to the message description in theappropriate messages book (see Figure 18-1 on page 18-3). For some prob-lems, additional messages are sent to the SSP Console display that include an8-character system reference code .F/ in the message text. If you are unableto solve the problem, refer to the appropriate system problem determinationbook. If you need to call for service, record the system reference codes(SRCs) by pressing the Print key. Give the printout to your service represen-tative.

Sending SSP MessagesThere are three ways you can send SSP messages.

� MSG Control Command

� MSG OCL Statement

� OFCMSG Procedure

Using the MSG Control Command to Send an SSP MessageThe MSG Control Command can be used to send a message to

� The SSP console

� Another display station on the same AS/400 Advanced 36 machine

� Another display station operator on the same AS/400 Advanced 36 machine

� All display stations configured for the AS/400 Advanced 36 machine

� A personal computer on an IBM Token-Ring Network that communicates withthe AS/400 Advanced 36 machine

� A user on another AS/400 Advanced 36 machine for which communications areset up

� A user on OS/400 for which communications are set up

For example, you can use the MSG Control Command when you want to leteveryone know you are going to power down the AS/400 Advanced 36 machine.

Example

MSG ALL,SYSTEM GOING DOWN IN 5 MINUTES, PLEASE SIGN OFF NOW

Chapter 18. Handling SSP Messages 18-9

Page 176: Iseries

SSP Messages

This message was sent to all of the user IDs that were active on the AS/400Advanced 36 machine.

Using the MSG OCL Statement to Send an SSP MessageThe MSG OCL statement is similar to the MSG Control Command. The MSG OCLStatement can be used to send a message to:

� The SSP console

� Another display station on the same AS/400 Advanced 36 machine

� Another display station operator on the same AS/400 Advanced 36 machine

� All display stations configured for the AS/400 Advanced 36 machine

� A personal computer on an IBM Token-Ring Network that communicates withthe AS/400 Advanced 36 machine

� A user on another AS/400 Advanced 36 machine for which communications areset up

� A user on OS/400 for which communications are set up

For example, you can use the MSG OCL Statement when you want to let everyoneknow you are taking the system down.

Example

On an SSP command line, type

// MSG ALL,SYSTEM GOING DOWN IN 5 MINUTES, PLEASE SIGN OFF NOW

When you press Enter , this message is sent to all of the user IDs signed on to anyof the display stations currently signed on to that AS/400 Advanced 36 machine.

Using the OFCMSG Procedure to Send a MessageThe OFCMSG procedure allows you to send messages to more than one user ordisplay station in an office environment. The user or display station can be locallyattached or on another system. This is done interactively.

Note: The OFCMSG procedure can only be used if Personal Services/36 isinstalled on your system.

SSP Keyboard Error MessagesWhen you press the wrong keyboard keys by mistake, the computer simply stopsand tells you what is wrong. The computer has locked up the keyboard so youcannot continue your task until you make the necessary correction.

Error Reset KeyThe Error Reset key (or Reset key) is used to unlock the keyboard from a keyboarderror or an invalid answer to a prompt. The Error Reset key is also used to unlockthe keyboard following the use of the Print key. After pressing the Error Reset key,you can type a valid answer to a prompt.

The keyboard is now back to normal and you can continue with your task.

18-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 177: Iseries

SSP Messages

Displaying Keyboard MessagesIf you have a blinking 4-digit number in the lower left corner of the display and theInput Inhibited light is on at your display station, you have a keyboard messagewaiting to be displayed. If you know the cause of the error, press the Error Resetkey and enter the required data again.

If you do not know the cause of the error, press the Help key. A message appearson the bottom line of the display. If you need an explanation of the message, referto the S/36 System Messages book, SC21-7938. Then, take the recommendedaction to continue processing. Following is an example of a keyboard message:

W4COMMAND

Cmd3-Previous menu Cmd5-Main help menu Home-Sign on menu

Ready for command or procedure.

KBD-0009 This field requires numeric characters

Keyboard MessageRTSN017-0

Chapter 18. Handling SSP Messages 18-11

Page 178: Iseries

SSP Messages

18-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 179: Iseries

SSP Commands

Chapter 19. Using SSP Commands and Procedures to DoTasks

SSP Control Commands are used to control the AS/400 Advanced 36 machine, theprinters and the display stations. You can use the Help key or HELP procedure onControl Commands to find out more information about the commands. The ControlCommands can be entered from the keyboard or selected by a menu option. Theycannot be coded in a procedure.

SSP Procedures are used to do various tasks on the AS/400 Advanced 36 machinesuch as creating files, creating libraries, copying files and compiling programs. Youcan use the help key or HELP procedure on SSP procedures to find out more infor-mation about the SSP procedures.

Using Help for Commands and ProceduresWhen you are signed on the system, you can use the help support to do a task.The help support is made up of menus, command displays, procedure displays,and help text. You can use help support when:

� You know the name of the command or procedure that does the task.

� You know the task you want to do, but you do not know the name of thecommand or procedure that does the task.

When You Know the Name of a Command or a ProcedureUse the following steps when you know the name of the command or procedurethat does the task.

1. Type the name of the command or procedure on the entry line of a commanddisplay.

2. Press the Help key. A menu, a command, or a procedure display is shown atyour display station. This menu, command or procedure display enables you todo the task.

Note: You can accomplish the same thing by typing HELP followed by thename of the command or procedure on the entry line of a commanddisplay and pressing Enter .

3. If a menu is shown, you can select an option to do a specific task. If there isanother menu for the option and you press Cmd11 , the name of the next menufor the option is shown on the right side of the menu options. To show thatmenu, type the menu name of the command line and press the Help key. Ifyou press the Help key without typing anything, the help text for the menu thatis currently on your display station is shown.

4. If a command is shown, you can run that command by pressing Enter . If youpress the Help key again, the help text for the command that is on your displaystation is shown.

If a procedure display is shown, you can type the necessary parameters on theprompt lines. Then, press Enter to perform the task described at the top of theprocedure display. If you press the Help key again, the help text for the proce-dure display is shown.

Copyright IBM Corp. 1995, 1996 19-1

Page 180: Iseries

SSP Commands

Example 1

Type

HELP STATUS

When you press Enter , the following STATUS menu is shown at your displaystation:

à@ ð STATUS W1

Display general status information

Select one of the following:

1. Spool file entries (PRT) SPOOLJOB2. Spool writer (WRT) SPOOL3. Jobs on the job queue (JOBQ) JOBQUEUE4. Currently running jobs (USERS) JOBS5. Devices on the system (WORKSTN) DEVICES6. System activity (SYSTASK) SYSACT7. Session status (SESSION) JOBENVR8. Message at subconsoles (MESSAGE) SUBCMSG

9. Communications COMMSTAT1ð. Full display status STATUSF

Cmd3-Previous menu Cmd5-Main help menu Cmd7-End Hone-Sign on menu

Ready for option number or command

á ñ

Note: If you press Cmd11 , the menu names are shown to the right of each menuoption as they appear on this display.

To display the status on a spool writer, do one of the following:

� Select option 2 and press Enter

� Type SPOOL and press the Help key.

� Type STATUS WRT on the command line and press Enter .

The second parameter for the STATUS command is shown in parentheses next tothe description of the specific status that can be displayed. If any of the listedactions are done, the Spool Writer Status display is shown at your display station.

To display additional help text about displaying status, press the Help key. Thehelp for the STATUS menu is displayed at your display station.

19-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 181: Iseries

SSP Commands

Example 2

Type

HELP POWER

The following POWER command is shown at your display station:

à@ ðPOWER OFF COMMAND

Power off the system

Press the Enter key to power down the system.

Cmd3-Previous menu

á ñ

To power down the AS/400 Advanced 36 machine, simply press Enter .

To display additional help about the POWER command, press the Help key. Helpfor the POWER command is displayed at your display station.

Chapter 19. Using SSP Commands and Procedures to Do Tasks 19-3

Page 182: Iseries

SSP Commands

Example 3

Type

HELP RENAME

and press Enter .

The following RENAME procedure display is shown at your display station:

à@ ð RENAME PROCEDURE Optional-\

Changes the name of an existing disk file, library or folder

Current name of file, library or folder . . . . . . . . ________

New name of file, library or folder . . . . . . . . . . ________

Creation date of file to be renamed . . . . . . . . . . ______ \

Cmd3-Previous menu Cmd4-Put on job queue

á ñ

To rename a file currently named FILEOLD to FILENEW, type FILEOLD on the firstprompt line and FILENEW on the second prompt line. Then press Enter .

To display additional help about the RENAME procedure, press the Help key. Thehelp for the RENAME procedure will be shown at your display station.

For more information about help support, see “Help for Commands andProcedures” in the Using Your Display Station – Advanced 36 book, SC21-0209.

When You Do Not Know the Name of a Command or a ProcedureUse the following steps when you do not know the name of the command or proce-dure that does the task.

1. Begin on the Main menu. To display this menu, do one of the following:

a. Type MAIN on the entry line of a command display and press the Helpkey.

b. Type HELP MAIN on the line of a command display and press Enter .

Note: If there is another menu and you press Cmd11 , the name of the nextmenu for the option is shown on the right side of the menu options.That menu can be shown by typing the menu name on the commandline and pressing the Help key.

19-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 183: Iseries

SSP Commands

If you press the Help key without typing anything, the help text for the Mainmenu is shown.

2. Type the option number that generally describes the task that you want to do,and press Enter .

Another menu is displayed.

3. Type the option that more specifically describes the task that you want to do,and press Enter .

Another menu is displayed.

4. Continue to select options until the procedure display or command display thatdoes the task is displayed.

5. Type the necessary parameters on the input lines of the procedure orcommand display. If you need more information about the procedure,command, or any of the parameters:

a. Press the Help key to display the help text.

b. After you read the help text, press Cmd3 to return to the procedure displayor the command display.

c. Type the parameters.

6. Press Enter .

The task starts processing.

Example 1

You are asked to put a job on the job queue.

1. Type MAIN on the command line and press the Help key.

The Main menu is shown at your display station.

à@ ð MAIN W1

Main System/36 help menu

Select one of the following:

1. Display a user menu MENU2. Perform general System activities SYSSESN3. Use and control printers, diskettes, or tape USEDEV4. Work with files, libraries, or folders LIBRFILE5. Use programming languages and utilities PROGRAM6. Communicate with another system or user SYSCOMM7. Define the system and its users DEFSYS8. Use problem determination and service PROBSERV9. Use office products OFCPROD1ð. Sign off the system OFF

Cmd3-Previous menu Cmd7-End Cmd12-How to use help Home-Signon menu

Ready for option number or command

á ñThe option that best describes what you were asked to do (put a job on the jobqueue) is option 2 Perform general system activities.

2. Type a 2 on the command line and press Enter .

Chapter 19. Using SSP Commands and Procedures to Do Tasks 19-5

Page 184: Iseries

SSP Commands

The SYSSESN menu is shown at your display station.

à@ ð SYSSESN W1

Perform general system activities

Select one of the following:

1. Control session environment SESNENVR2. Handle messages MESSAGE3. Control printing (spool file) SPOOLJOB4. Control jobs and the job queue JOBS5. Work with files, libraries, and folders LIBRFILE6. List or work with history file HIST7. Display general status information STATUS8. Change or control the status of devices DEVICES9. Stop or start system activity SYSACT1ð. Help with system procedures and control commands COMMAND

Cmd3-Previous menu Cmd7-End Cmd12-How to use help Home-Signon menu

Ready for option number or command

á ñThe option that best describes what you were asked to do (put a job on the jobqueue) is option 4 Control jobs and the job queue.

3. On the command line, type

4

to select Control jobs and the job queue.

4. Press Enter .

The STATUS USERS display and the JOBS menu is shown at your displaystation.

à@ ð STATUS USERS W1

JOB PROC PROGRAM STATUS ATTRIBUTES PRTY RGN PGM BUFF

Cmd7-End Cmd8-Help Cmd15-Update Cmd16-Restart Roll-Page

-------------------------------------------------------------------- JOBS

Control jobs and the job queue1. Display a specific job 6. Change processing priority2. Jobs on the job queue 7. Prevent jobs from starting3. Stop a job 8. Allow jobs to start4. Restart a stopped job 9. Prevent SSP-ICF jobs5. Cancel a job 1ð. Allow SSP-ICH jobs to start

Ready for option number or command

á ñ

The option that best describes what you were asked to do (put a job on the jobqueue) is option 2 Jobs on the job queue.

19-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 185: Iseries

SSP Commands

5. On the command line, type

2

to select Jobs on the job queue

6. Press Enter .

The JOB QUEUE STATUS display and the JOBQUEUE menu is shown at yourdisplay station.

à@ ðComplete JOB QUEUE STATUS W1Jobs in Queue: ð of 8ð JOBQ PRTY STOPPED : ð

Max Active Jobs: 1 Max for PRTY 5:5ð 4:5ð 3:5ð 2:5ð 1:5ð ð:5ð

POS JOBNAME PROC/DOC LIBR/FLDR USER STATUS JOBQ PROC

SYS-5689 The job queue is empty now

Cmd7-End Cmd8-Help Cmd15-Update Cmd16-Restart Roll-Page-------------------------------------------------------------------- JOBQUEUE

Jobs on the job queue1. Display specific job(s) 6. Start the job queue2. Put a job on the queue 7. Stop the job queue3. Cancel a job 8. Change position of a job4. Hold a job 9. Change processing priority5. Release a job 1ð. Change maximum active jobs

Ready for option number or command

á ñThe option that best describes what you were asked to do (put a job on the jobqueue) is option 2 Put a job on the queue.

7. On the command line, type

2

to select Put a job on the queue.

8. Press Enter .

The JOBQ COMMAND display overlays the JOBQUEUE menu at your displaystation.

Chapter 19. Using SSP Commands and Procedures to Do Tasks 19-7

Page 186: Iseries

SSP Commands

à@ ðComplete JOB QUEUE STATUS W1Jobs in Queue: o of 8ð JOBQ PRTY STOPPED : ð

Max Active Jobs: 1 Max for PRTY 5:5ð 4:5ð 3:5ð 2:5ð 1:5ð ð:5ð

POS JOBNAME PROC/DOC LIBR/FLDR USER STATUS JOBQ PROC

SYS-5689 The job queue is empty now

Cmd7-End Cmd8-Help Cmd15-Update Cmd16-Restart Roll-Page-------------------------------------------------------------------- JOBQ COMMAND Optional-\

Job queue priority . . . . . . . ð , 1 , 2 , 3 , 4 , 5 3_______ \

Library containing the procedure . . . . . . . . . . . . ________ \

Procedure name . . . . . . . . . . . . . . . . . . . . . ________

Procedure parameters . . . . . _________________________________________________________________________________________________________

á ñ9. Type the necessary parameters on the command prompt lines.

10. Press Enter .

Once the job is put on the job queue, a message, Job Wnnnnnnn wassuccessfully added to the jobq, is shown at the bottom of the display.

11. To get back to the Main menu, press Cmd7 (End) twice.

For more information about help support, see “Help for Commands andProcedures” in the Using Your Display Station – Advanced 36 book, SC21-0209.

To see a list of other tasks you may want to do using the SSP operating system,see Chapter 5 in the Operating Your Computer–SSP Operating System book,SC21-8297.

19-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 187: Iseries

SSP Printing

Chapter 20. Printing with SSP

SSP commands can be used to print from an AS/400 Advanced 36 machine.However, you may share an output queue or printer with OS/400.

You do not need to know everything about printing. To work with your printeroutput and printer output created by others, you only need to know the essentials.

Spooled FilesIn OS/400, a spooled file is a file that holds output data waiting for printing. It isalso known as a spooled output file. Multiple spooled files might be waiting to print.The spooled files are controlled by the person who created them or by the operator.The operator needs spool control (*SPLCTL) or job control (*JOBCTL) specialauthorities to work with other people's output.

| In SSP, spool file entries in the spool file hold output data waiting for printing.| The spool file entries are controlled by the person who created them or by the

operator. There is one spool file shared by everyone on the system. All printeroutput goes to this spool file.

Printer WritersIn OS/400, the printer writer is a system program that writes spooled files to aprinter.

In SSP, the equivalent to a printer writer is the Spool Writer. The spool writer is thepart of SSP that prints output saved in spooled file entries.

Output QueuesIn OS/400, an output queue contains a list of spooled files waiting for printing.There can be multiple output queues in OS/400.

| In SSP, the equivalent to an output queue is the spool file . The spool file contains| a list of spool file entries waiting to print. There is only one spool file in SSP. All

output waiting to print is in this spool file.

For directions on setting up an AS/400 Advanced 36 machine to send output to anOS/400 output queue, see “Defining Whether SSP or OS/400 Controls SSP PrinterOutput” on page 31-26.

PrintersFor directions on specifying whether a printer is assigned to an AS/400 Advanced36 machine or shared with OS/400, see Chapter 31, “Changing Your AS/400Advanced 36 Machine Configuration” on page 31-1. For more information onOS/400 printing, see Chapter 7, “Printing with OS/400” on page 7-1.

The operating systems can share the same printer. For directions on sharingprinters, see “Giving SSP Control of AS/400 Advanced 36 Machine Printer Output”on page 31-26.

The printer can only be used by one operating system at a time. If an SSP jobtries to use a printer that another SSP or OS/400 job is using, the job receives an

Copyright IBM Corp. 1995, 1996 20-1

Page 188: Iseries

SSP Printing

error stating that the printer is in use. If an OS/400 job tries to use a printer that anSSP is using, the OS/400 job receives an error stating that the printer is not avail-able.

You have the option of spooling the output to an OS/400 output queue rather than| sending the output to the SSP spool file or directly to a printer. Specifying an

output queue allows the OS/400 Printer Writer to print all the output for both SSPand OS/400. This prevents SSP and OS/400 from trying to acquire the sameprinter. The output queue is specified either on the PRINTER OCL statement or inthe configuration of the Advanced 36 machine.

In order to use non-twinaxial printers, such as ASCII printers and LAN-attachedprinters, the output must be directed to an output queue and then printed using theOS/400 printer writers.

Additional reading: For detailed information about printing elements, printerdevice support, printer spooling support, and Advanced Function Printing* (AFP*),see the Printer Device Programming book, SC41-4713.

Finding SSP Printer OutputThere are two ways of finding all the SSP printer output for which you areauthorized:

� Using the SSP Help support

� If you have the Value Added Software Package installed on your AS/400Advanced 36 machine, you can use the WRKSPL command.

Using SSP Help SupportTo use the SSP Help support, do as follows:

1. On any SSP command line on the AS/400 Advanced 36 machine, type

HELP SPOOLJOB

2. Press Enter .

| The SPOOL FILE STATUS display and the SPOOLJOB menu are shown at your| display station. The SPOOL FILE STATUS display contains a list of all the spool| file entries for which you are authorized. The roll keys can be used to page

forward and backward through the list of entries. From the SPOOLJOB menu you| can control the spool writer and manage the spool file entries.

Using the Work with Spool File (WRKSPL) CommandTo use the WRKSPL command, do as follows:

1. On any SSP command line on the AS/400 Advanced 36 machine, type

WRKSPL

2. Press Enter .

The Work With Spool File display is shown at your display station.

| This display contains a list of all the spool file entries for which you are authorized.| From this display you can manage the spool file entries.

20-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 189: Iseries

SSP Printing

Managing Printer Output — Command SummaryThe following commands can be used from your AS/400 Advanced 36 machine tomanage your printed output.

SSP Command Function

ASSIGN (A P) Assigns a printer as the system printer.

BALPRINT Balances the printed output workload for a group ofprinters.

| CANCEL (C P) Deletes a spool file entry or entries.

CHANGE (G) Allows you to change:

� Defer status

� Destination printer

� Forms number

� Number of copies

� Number of separator pages

| � Position of a spool file entry

� Priority of the spool writer

| HOLD (H P) Prevents the spool file entry from printing

| RELEASE (L P) Releases a held spool file entry for printing

| RESTART (T P) Starts the printing of a spool file entry again.

| START (S P) Starts the printing of spool file entries.

| STATUS PRT (D P) Displays information about spool file entries on half of| the display.

| STATUS WRT (D WRT) Displays status of the spool writers.

| STATUSF PRT (DF P) Displays information about spool file entries on the| entire display.

| STOP (P P) Stops the printing of spool file entries.

| WRKSPL Allows a user to work with the overall status of all spool| file entries.

For more information on working with printer output, refer to the S/36 System Ref-erence book, SC21-9020. The Printer Device Programming book, SC41-4713, alsocontains information on printing concepts.

Managing Printer Output — Complete DetailsTo manage printer output you can use:

� Control commands

� Options selected from a menu

� Options from a display

Chapter 20. Printing with SSP 20-3

Page 190: Iseries

SSP Printing

Changing Printer Output with a Control Command| The CHANGE (G) Control Command can be used to change the following attributes| of spool file entries:

� Number of copies

� Defer status

� Forms number

� Assigned printer

� Position in the spool file

� Priority

� Number of separator pages

To use the CHANGE (G) Control Command, do as follows:

1. On any SSP command line on the AS/400 Advanced 36 machine, type

G

which is the abbreviation for the CHANGE command.

2. Press the Help key.

Changing Printer Output with an Option from a MenuSelect option 5 (Change entries) on the SPOOLJOB menu.

Changing Printer Output with an Option from a DisplayUse option 2 (Change) on the WRKSPL display.

Holding Printer Output Using a Control Command| The HOLD PRT (H P) Control Command can be used to hold a specific spool file| entry, all spool file entries or all spool file entries for a specified printer ID.

To hold printer output using the control command, you would:

1. On any SSP command line on the AS/400 Advanced 36 machine, type

HOLD PRT

2. Press the Help key.

Holding Printer Output Using an Option from a MenuSelect option 3 (Hold entries) on the SPOOLJOB menu.

Holding Printer Output Using an Option from a DisplayUse option 3 (Hold) on the WRKSPL display.

Releasing Printer Output Using a Control Command| The RELEASE PRT (L P) Control Command can be used to release a specific| spool file entry, all spool file entries or all spool file entries for a specific printer ID.

1. On any SSP command line on the AS/400 Advanced 36 machine, type

RELEASE PRT

20-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 191: Iseries

SSP Printing

2. Press the Help key.

Releasing Printer Output Using an Option from a MenuSelect option 4 (Release entries) on the SPOOLJOB menu.

Releasing Printer Output Using an Option from a DisplayUse option 6 (Release) on the WRKSPL display.

Deleting Printer Output Using a Control Command| The CANCEL PRT (C P) Control Command can be used to delete a specific spool| file entry, all spool file entries, all spool file entries with a specified forms number,| all spool file entries created by a specified user ID or all spool file entries for a| specified printer ID.

1. On any SSP command line on the AS/400 Advanced 36 machine, type

CANCEL PRT

2. Press the Help key.

Deleting Printer Output Using an Option from a MenuSelect option 2 (Cancel entries) on the SPOOLJOB menu.

Deleting Printer Output Using an Option from a DisplayUse option 4 (Delete) on the WRKSPL display.

Copying Printer Output Using a Procedure| The COPYPRT procedure can be used to copy spool file entries to a data file and| then display the printer output. The following can be copied to a data file:

| � A specific spool file entry

| � All spool file entries on the system

| � All spool file entries you created

� All spool file entries with a specific forms number

1. On any SSP command line on the AS/400 Advanced 36 machine, type

COPYPRT

2. Press the Help key.

| Copying Printer Output Using an Option from a DisplaySelect option 6 (Copy or display entries) on the SPOOLJOB menu.

| Displaying Printer Output Using an Option from a DisplaySelect option 5 (Browse) on the WRKSPL display.

Chapter 20. Printing with SSP 20-5

Page 192: Iseries

SSP Printing

Balancing Spooled Output Between Printers Using a ProcedureThe BALPRINT procedure allows you to balance spooled output between printers ina group.

1. On any SSP command line on the AS/400 Advanced 36 machine, type

BALPRINT

2. Press the Help key.

Note: You cannot balance spooled output between printers using an option from amenu or using an option from a display.

Working with Spool WritersThere are two ways of working with spool writers:

� Using a Control Command to Work with Spool Writers

The Control Command can be considered a fast path for working with spoolwriters.

1. On any SSP command line on the AS/400 Advanced 36 machine, type

STATUS WRT

Or

D WRT

2. Press Enter .

The SPOOL WRITER STATUS display and the SPOOL menu are shown atyour display station.

� Using a Menu to Work with Spool Writers

1. On any SSP command line on the AS/400 Advanced 36 machine, type

SPOOL

2. Press the Help key.

The SPOOL WRITER STATUS display and the SPOOL menu are shown atyour display station.

Starting a Spool Writer Using a Control CommandTo start a spool writer using a control command:

1. On any SSP command line on an AS/400 Advanced 36 machine, type

START PRT

Or,

S P

2. Press the Help key.

20-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 193: Iseries

SSP Printing

Starting a Spool Writer Using an Option from a MenuTo start a spool writer from a menu option:

1. Select option 3 on the SPOOL menu.

The START Command display overlays the SPOOL menu shown on the lowerhalf of your display station.

Stopping a Spool Writer Using a Control CommandIf you want to use a control command to stop a spool writer:

1. On an SSP command line on an AS/400 Advanced 36 machine, type one ofthe following:

STOP PRT

Or,

P P

2. Press the Help key.

Stopping a Spool Writer Using an Option from a MenuTo stop a spool writer using an option from a menu:

1. Select option 4 on the SPOOL menu.

The STOP Command display overlays the SPOOL menu shown on the lowerhalf of your display station.

Restarting a Spool Writer Using a Control CommandYou can use the RESTART command to restart printing in any of the followingplaces:

� At the beginning of the specified entry

� From the top of a specified page of that entry

� At the top of the last page that was partially printed by the spool writer

To use a control command to restart a spool writer:

1. On any SSP command line on an AS/400 Advanced 36 machine, type one ofthe following:

RESTART PRT

Or,

T P

2. Press the Help key.

Restarting a Spool Writer Using an Option from a MenuTo use an option from a menu to start a spool writer again:

1. Select option 5 on the SPOOL menu.

The RESTART Command display overlays the SPOOL menu shown on thelower half of your display station.

Chapter 20. Printing with SSP 20-7

Page 194: Iseries

SSP Printing

Assign a Printer as the System PrinterTo assign a printer as the system printer, do as follows:

1. On any SSP command line on the AS/400 Advanced 36 machine, type

HELP ASSIGN

2. Press Enter .

The STATUS WORK STATION display and the ASSIGN COMMAND menu isshown at your workstation.

3. On the ASSIGN COMMAND menu, select option 2 (Assign a printer as thesystem printer).

Creating Printed Output — Selected ExamplesLISTDATA Allows you to print or display the data records of a file

located on disk, diskette, or tape

LISTFILE Allows you to print or display the contents of a file located ondisk, diskette, or tape

CATALOG Allows you to print or display the names of all the files,libraries and folders located on disk, diskette, or tape

HISTORY Allows you to print or display the history file.

| WRKSPL Allows you to work with spool file entries

LISTLIBR Allows you to display or print the contents of a library

Configuring Printer OptionsThe following can be specified during system configuration using the CNFIGSSPprocedure:

� Whether you want print spooling active

� Whether to start the spool writer program automatically after an IPL

� The size of the spool file in blocks

� The size of spool file segments in blocks

� Which disk you want to use for the spool file

� A default forms identifier

� How many lines you want to print on each page

� The system printer

If you want to change any of the items in the previous list, see the Changing YourSystem Configuration–SSP book, SC21-8295

20-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 195: Iseries

SSP Subsystems

Chapter 21. Working with SSP Subsystems

Definitions

SSP SubsystemsFor SSP, a subsystem is the part of the operating system that handles commu-nication requirements of the remote system or remote drives. It isolates mostsystem dependent considerations from the application program. The following areexamples of SSP subsystems:

� SSP-ICF subsystems

� APPC subsystems

The SSP-ICF subsystem is required for running ICF sessions.

The APPC subsystem allows the AS/400 Advanced 36 machines to communicatewith other systems that have compatible support.

OS/400 SubsystemsFor OS/400, a subsystem is an operating environment where the system coordi-nates processing of jobs and resources for the jobs. If you use one of the defaultsubsystem configurations supplied by IBM, all of your OS/400 subsystems are auto-matically started when you do an IPL.

Once your system is successfully powered on, you may need to start additionalsubsystems to make your system ready to use if:

� You created a subsystem which is not automatically started, such as a sub-system which runs only at night.

� You ended all but the controlling subsystem to bring your system to a restrictedstate to back it up.

All jobs are run in a subsystem. A subsystem creates a suitable environment for ajob to do its work. The AS/400 system can contain one or many subsystems.These can be created or deleted by those who have proper authority.

As the number of different types of jobs increases in the system, more subsystemscan be defined to manage those jobs. All interactive processing can occur in onesubsystem, all batch processing in another, system operator jobs in a third, and soon.

This makes it easier to control the different jobs in the system because subsystemscan be started and ended individually.

Copyright IBM Corp. 1995, 1996 21-1

Page 196: Iseries

SSP Subsystems

Starting an SSP SubsystemTo start an SSP subsystem,

1. On any SSP command line, type

ENABLE

2. Press the Help key.

The ENABLE procedure display is shown at your display station.

3. Type the necessary parameters on the various prompt lines.

4. Press Enter .

A message is displayed telling you the subsystem has started.

Ending an SSP SubsystemTo end an SSP subsystem:

1. On any SSP command line, type

DISABLE

2. Press the Help key.

The DISABLE procedure display is shown at your display station.

3. Type the necessary parameters on the various prompt lines.

4. Press Enter .

A message is displayed indicating that the system has started to end the sub-system. Another message is sent when the subsystem has ended.

Displaying the Status of an SSP SubsystemTo display the status of the Communications subsystems:

1. On any SSP command line, type

STATUS SUBSYS

Or,

D I

2. Press Enter .

The STATUS Information display and the CNTLLINE menu are shown at yourdisplay station.

The status of the active subsystems are in the STATUS display. You can usethe CNTLLINE menu to control subsystems and communications lines.

21-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 197: Iseries

SSP Security

Chapter 22. SSP Security

This chapter provides basic information on security for SSP operating systems.

Attention : OS/400 system security is used to provide the security of the AS/400Advanced 36 machine objects (*M36 and *M36CFG). OS/400 system securitydoes not provide password, menu, badge, communications or resource security forthe AS/400 Advanced 36 machine. This security must be provided by SSP secu-rity.

Password SecurityPassword security helps prevent an unauthorized person from signing on to thesystem. When password security is active, you have specified that password infor-mation should be checked and verified. This requires that the password and theuser ID be entered when you sign on to the system. If the correct combination ofuser ID and password is entered on the sign-on display, the person is allowed onthe system.

Note: If password security is active for SSP, Master Security Officer authority isrequired to use certain commands such as the CHGSYSVL command. Ifpassword security is not active, the CHGSYSVL command and othersystem commands must be run from the SSP console.

A user ID can be any combination of up to 8 characters. The first character mustbe 0 through 9, A through Z, #, @, or $. The remaining characters can be anycharacter of the alphabet, any number, or any special character except a comma.Also, the user ID cannot contain any blanks between the characters.

A password must be 4 characters. Any letter of the alphabet, any number, or anyspecial character except a blank can be used.

When password security is not active, anyone can sign on to the system byentering any user ID.

Note: The difference between four-character passwords for SSP and ten-characterpasswords for OS/400 must be considered when you transfer to an AS/400Advanced 36 machine with autosignon enabled.

The password prompt appears on the Sign-On display only if password security isactive.

Menu SecurityPassword security must be active to use menu security. Menu security allows youto restrict a user to using a single menu or chain of menus. When menu security isin effect, the menu that you specify in the user profile as the mandatory defaultuser menu appears after the user signs on. Unless an option on the mandatorymenu causes another option menu, help menu, or help prompt to appear, a usercannot use another menu or the system help.

Copyright IBM Corp. 1995, 1996 22-1

Page 198: Iseries

SSP Security

When menu security is in effect, the user does not have to enter a menu name inthe menu field on the Sign On display. Once the default menu is displayed, theuser can only:

� Select the options on that menu

� Enter the MSG and OFF control commands

Badge SecurityIf password security is active, you can use another type of security called badgesecurity. Badge security prevents unauthorized users from signing on to a displaystation that has a magnetic stripe reader configured. When badge security isactive, the display station configured with a magnetic stripe reader has an Enterbadge prompt on the Sign On display.

The user must move a badge through the magnetic stripe reader as well as supplythe other information needed during sign-on. The badge has a magnetic stripe withspecially coded data. Consult your local IBM branch office for information aboutobtaining badges and magnetic stripe readers, and about coding the informationneeded on the magnetic stripe.

If the person does not have a badge or uses a badge with the wrong information,that person is unable to sign on at that display station.

Badge security requires a magnetic stripe reader at a display station and the hard-ware support for connecting the reader to the display station. The display stationswith badge readers are identified during system configuration.

Not every display station needs a magnetic stripe reader. A person with a badgecan still sign on at a display station without a magnetic stripe reader. You mightdecide to install magnetic stripe readers only at those display stations that are faraway from your central data processing center.

Communications SecurityIn order to use communications security, password security must be active forAPPC and ICF.

Communications security is only valid with the APPC (advanced program-to-program communications) subsystem when password security is active. APPC isthe communications support that allows the AS/400 Advanced 36 machine to com-municate with other systems having compatible support.

Communications security allows you to verify a remote location's identity before youallow it to run programs on your system. When communications security is ineffect, the local and remote locations must send and receive the same locationpassword to start an APPC session.

If both systems have communications security in effect, they verify each other'sidentity, by exchanging location passwords, before an APPC session can bestarted.

If neither system has communications security or password security, a user on onesystem can access:

22-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 199: Iseries

SSP Security

� Any resources that are not secured on the system

� Any secured resources he is authorized to access on the other system

If one system has password security and the other system does not, a user ID of*NULL allows users on the system that is not secured to access the securedsystem through the APPC subsystem. The secured system must create a userprofile with a user ID of *NULL. The user ID of *NULL and an access level shouldbe entered for the resources on your system that you will allow the system that isnot secured to access.

Note: Do not create a location profile for a remote location that does not use com-munications security.

You can use the DEFINEID procedure to set up communications security for theSSP ICF BSCEL subsystem if you use Bisynchronous Communications. When theAS/400 Advanced 36 machine is using BSCEL and is connected to a remotesystem by a switched communications line. The DEFINEID procedure comparesthe ID received from the remote system with the DEFINEID list. If the ID is in thelist, the communications line is connected successfully. If the ID is not found, theremote system is disconnected.

The DEFINLOC procedure can be used for an asynchronous system using X.25support to define remote locations that are allowed to call your system. When aconnect request is received, the location ID of the calling system is checked. If thelocation ID and name are listed in the DEFINLOC list, the call is accepted. If thelocation ID and name are not on the DEFINLOC list, the call is rejected.

Resource SecurityResource security helps prevent unauthorized access to disk files, libraries,folders, and folder members on your system.

When resource security is not active, anyone who can sign on to the system canuse any file, library, or folder on the system.

Note: Diskette and tape files cannot be secured using resource security.

Resource security is a good way of ensuring that only the people that you haveauthorized to use certain files, libraries, and folders can do so. You can, forexample, allow only the employees responsible for the payroll to update the per-sonnel files and to run the payroll programs.

Working with SSP SecurityTo work with SSP security, do one of the following:

� Use the SECURITY command.

1. On a command line on the AS/400 Advanced 36 machine console, type

SECURITY

2. Press the Help key.

Or,

� Use the HELP SECURITY command.

Chapter 22. SSP Security 22-3

Page 200: Iseries

SSP Security

1. On a command line on the AS/400 Advanced 36 machine console, type

HELP SECURITY

2. Press Enter .

In either case, the SECURITY help menu is shown. From this menu, you can:

� Update security information

� List security information

� Save the user ID file or resource security file

� Restore the user ID file or resource security file

� Define password security

� Define resource security

� Update your password

For more information on SSP security, see the S/36 System Security Guide,SC21-9042.

22-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 201: Iseries

Controlling SSP Jobs

Chapter 23. Controlling SSP Jobs

The STATUS JOBQ (D J) command can be used to control SSP JOBS. Thiscommand shows all the jobs on the job queue and allows the operator to:

� Display a specific job

� Put a job on the job queue

� Cancel a job on the job queue

� Hold a job on the job queue

� Release a job on the job queue

� Start the job queue

� Stop the job queue

� Change the position of a job in the job queue

� Change the processing priority of a job on the job queue

� Change the maximum number of active jobs

When you run the STATUS JOBQ or D J command, the following display appears:

à@ ðComplete JOB QUEUE STATUS W1Jobs in Queue: 4 of 8ð JOBQ PRTY STOPPED : ð

Max Active Jobs: 1 Max for PRTY 5:5ð 4:5ð 3:5ð 2:5ð 1:5ð ð:5ð PRIORITY

POS JOBNAME PROC/DOC LIBR/FLDR USER STATUS JOBQ PROC1 W1ð75ðð6 JOB5 JOBLIB USER1 -- 5 N2 W1ð75ðð1 JOB3 JOBLIB USER1 -- 3 N3 W1ð75ð15 JOB2 JOBLIB USER1 -- 3 N4 W1ð75ð25 JOB4 JOBLIB USER1 -- 3 N

Cmd7-End Cmd8-Help Cmd15-Update Cmd16-Restart Roll-Page --------------------------------------------------------------------------- JOB

Control jobs and the job queue1. Display specific job 6. Start the job queue2. Put a job on the job queue 7. Stop the job queue3. Cancel a job 8. Change position of a job4. Hold a job 9. Change processing priority5. Release a job 1ð. Change maximum active jobs

Ready for option number or command

á ñ

To perform any of the functions on the previous display, you type the optionnumber on the display and press Enter . The display will change to show thecommand prompt for that function.

Copyright IBM Corp. 1995, 1996 23-1

Page 202: Iseries

Controlling SSP Jobs

Working With Current Running JobsThe STATUS USERS (D U) command and the WRKUSER command show all thejobs currently running on the AS/400 Advanced 36 machine and allow the operatorto:

� Display a specific job

� Display jobs on the job queue

� Stop a job

� Restart a stopped job

� Cancel a job

� Change the processing priority of a job

� Prevent jobs from starting

� Prevent SSP-ICF jobs from starting

� Allow SSP-ICF jobs to start

When the STATUS USER or D U command is run, the following display appears:

à@ ð Complete STATUS USERS W1

JOB PROC PROGRAM STATUS ATTRIBUTES PRTY RGN PGM BUFFW1ð74951 JOB1 -------- MSG-Wait ----------- Norm 24K ---- ----W3113219 CATALOG $LABEL ACTIVE SRT Norm 24K 26K ----W3113234 DSPSYS $VAPS ACTIVE SRT Norm 24K 18K ----

Cmd7-End Cmd8-Help Cmd15-Update Cmd16-Restart Roll-Page --------------------------------------------------------------------------- JOBQUEUE

Jobs on the job queue1. Display specific job 6. Change processing priority2. Jobs on the job queue 7. Prevent jobs from starting3. Stop a job 8. Allow jobs to start4. Restart a job 9. Prevent SSP-ICF jobs5. Cancel a job 1ð. Allow SSP-ICF jobs to start

Ready for option number or command

á ñ

To perform any of the functions on the previous display, type the option on thedisplay and press Enter . The display changes to show the command prompt forthat function.

Working with the History FileThe history file contains the following information:

� OCL and utility control statements from user-written procedures

� Commands contained in jobs or entered from a display station

� All messages shown at a display station

23-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 203: Iseries

Controlling SSP Jobs

� All operator responses to messages and prompts

� The display station ID used by the job

� The operator's user ID

� The job name

� The start time and date

� The end time and date

To work with the history file, do one of the following:

� Use the HIST command.

1. On a command line on the AS/400 Advanced 36 machine, type

HIST

2. Press the Help key.

� Use the HELP HIST command.

1. On a command line on the AS/400 Advanced 36 machine, type

HELP HIST

2. Press Enter .

In either case, the Hist help menu appears. From this menu you can:

� Display the history file

� List the history file

� Copy the history file to a data file

� Erase the history file

Chapter 23. Controlling SSP Jobs 23-3

Page 204: Iseries

Controlling SSP Jobs

23-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 205: Iseries

SSP Devices and Communications

Chapter 24. Working with SSP Devices and Communications

The purpose of this chapter is to provide pointers to information that is needed towork with devices and communications from the SSP operating system. In thosecases where the information is limited, it is included in this chapter. For informationon doing these tasks from OS/400, see Chapter 11, “Working with OS/400 Devicesand Communications.”

Displaying and Changing Device StatusYou can use the following commands to display and change device status from theSSP operating system:

� STATUS LINE (D L)

The STATUS LINE command displays status and allows the operator tochange the communication line status.

� STATUS WORKSTN (D W)

The STATUS WORKSTN command displays status and allows the operator tochange workstation, diskette, or tape status.

Printing Local Device AddressesTo print the addresses of the local workstations and printers, follow the directions inChapter 5 of the Changing Your System Configuration–SSP book, SC21-8295.

Displaying Communications Lines and ControllersYou can start or stop a subsystem that controls a communications line using theSTATUS LINE (D L) command to show the status of the line. You can show thestatus of a specific line by changing the command as follows:

D L,x

where x is the line number for which you want status.

Configuring Remote Communications LinesYou can configure remote communications lines for your AS/400 Advanced 36machine using the CNFIGICF procedure.

Copyright IBM Corp. 1995, 1996 24-1

Page 206: Iseries

SSP Devices and Communications

24-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 207: Iseries

Saving and Restoring SSP

Chapter 25. Saving and Restoring the AS/400 Advanced 36Machine Information

This chapter contains information on how to save and restore the AS/400 Advanced36 machine as an OS/400 object. It also contains information on how to save andrestore the SSP operating system, the licensed program products and other SSPsystem files.

User data must also be backed up. User data is stored in files, folders and librariesin an AS/400 Advanced 36 machine. There are 6 procedures that can be used tosave and restore user data:

� SAVE and RESTORE - to save and restore user files.

� SAVEFLDR and RESTFLDR - to save and restore user folders.

� SAVELIBR and RESTLIBR - to save and restore user libraries.

You should set up a backup plan to use these procedures to save your vital userdata. For information on Backup and Recovery of your user data in the AS/400Advanced 36 machine, see the S/36 Concepts and Programmer’s Guide book,SC21-9019.

Saving and Restoring an AS/400 Advanced 36 Machine| The AS/400 Advanced 36 machine is an OS/400 object. The object type is *M36.| The *M36 object contains the SSP operating system, all the licensed program pro-

ducts, the other SSP system files and all the user data for that AS/400 Advanced| 36 machine. There are also AS/400 Advanced 36 machine configuration objects.| The object type for configuration objects is *M36CFG. The AS/400 Advanced 36| machine configuration object defines the OS/400 devices to the SSP operating| system. The AS/400 Advanced 36 machine object and the AS/400 Advanced 36| machine configuration object are stored in OS/400 libraries.

Saving the AS/400 Advanced 36 Machine LibraryThe OS/400 Save Library (SAVLIB) command can be used to save the library thatcontains the AS/400 Advanced 36 machine. The SAVLIB command saves theentire library, including the library description, the object descriptions, and the con-tents of the objects in the library. This type of save is intended for disasterrecovery. Individual files, folders or libraries in the AS/400 Advanced 36 machinecannot be restored from this type of save. For more information on the SAVLIBcommand, see “Saving Libraries” on page 12-4.

Saving the AS/400 Advanced 36 Machine Object and ConfigurationObject

The OS/400 Save Object (SAVOBJ) CL command can be used to save an AS/400Advanced 36 machine object and an AS/400 Advanced 36 machine configurationobject. This type of save is intended for disaster recovery. Individual files, foldersor libraries in the AS/400 Advanced 36 machine cannot be restored from this typeof save. For more information on the SAVOBJ command, see “Saving SpecificObjects” on page 12-5.

Copyright IBM Corp. 1995, 1996 25-1

Page 208: Iseries

Saving and Restoring SSP

Restoring the AS/400 Advanced 36 Machine LibraryThe OS/400 Restore Library (RSTLIB) CL command can be used to restore asaved library that contains the AS/400 Advanced 36 machine. This type of restoreis intended for disaster recovery. The entire library containing the AS/400Advanced 36 machine must be restored. Individual files, folders or libraries in theAS/400 Advanced 36 machine cannot be restored. For more information on theRSTLIB command, see “Restoring Libraries” on page 12-6.

Restoring the AS/400 Advanced 36 Machine Object and ConfigurationObject

The OS/400 Restore Object (RSTOBJ) CL command can be used to restore anAS/400 Advanced 36 machine object and an AS/400 Advanced 36 machine config-uration object. This type of restore is intended for disaster recovery. The entireobject containing the AS/400 Advanced 36 machine must be restored. Individualfiles, folders or libraries in the AS/400 Advanced 36 machine cannot be restored.For more information on the RSTOBJ command, see “Restoring Specific Objects”on page 12-7.

Saving and Restoring the SSP Operating System, Licensed Programs,and Other SSP System Files

This section discusses the following:

� Initializing tapes� Saving the SSP operating system� Saving the licensed program products� Saving other SSP system files� Restoring the SSP operating system� Restoring the licensed program products� Restoring other SSP system files

Initializing Tapes to Save the SSP Operating System, LicensedProgram Product and Other SSP System Files

Note: One 6150 tape initialized at QIC120 holds 120MB of data. This tape willhold the SSP, all of your programming support, and the other SSP systemfiles that you want to save.

For information on using different kinds of tape from your AS/400 Advanced 36machine, see Chapter 7 of the Operating Your Computer–SSP Operating Systembook, SC21-8297. For information on using different kinds of tape from OS/400,see Chapter 4 of the System Startup and Problem Handling book, SC41-4206.

To initialize the tape for saving the SSP operating system, licensed program pro-ducts and other SSP system files, do the following:

1. Insert a 1/4-inch tape cartridge into the tape drive.

2. Type the following procedure on the command line of the SSP system console:

TAPEINIT TC,SL,PPROD,CLEAR

Note: When you save the licensed program products, the volume ID of thetape must by PPROD. Therefore, it is recommended that you use thevolume ID of PPROD.

25-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 209: Iseries

Saving and Restoring SSP

3. Press Enter .

4. When the command entry display returns, remove the tape cartridge from thetape drive and label it PPROD - BACKUP 1.

Saving the SSP Operating System Using the SAVELIBR ProcedureUse the Save Library (SAVELIBR) procedure to save the SSP operating systemlibrary, #LIBRARY, to tape after you have applied PTFs.

Note: It is recommended that you place the AS/400 Advanced 36 machine in ded-icated state to ensure that all files, libraries, and folders are saved. Forinformation on putting the system in dedicated state, see “Putting theAS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.

To save the SSP operating system, do the following:

1. Insert the tape cartridge you initialized and labelled PPROD - BACKUP1 in thetape drive.

2. On the command line at the SSP system console type the following procedure:

SAVELIBR #LIBRARY,999,PPROD,,,TC,LEAVE

3. Press Enter .

When the command entry display returns, #LIBRARY (SSP operating system) hasbeen saved to tape.

If you put the AS/400 Advanced 36 machine in a dedicated state and you are goingto save the licensed program products or other SSP system files, you can leave theAS/400 Advanced 36 machine in dedicated state. If you are not going to performthese tasks, remove the dedication as follows:

1. On the command line of the SSP System Console for the AS/400 Advanced 36machine, type

START SYSTEM

2. Press Enter .

Saving the Licensed Program ProductsProduct libraries must be saved to tape using specific save commands for thatproduct (for example, RPGSAVE for RPG and SEUSAVE for SEU). Other files,folders, and libraries that are part of the program products must be saved using theSAVE, SAVEFLDR, and SAVELIBR procedures.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-3

Page 210: Iseries

Saving and Restoring SSP

Before Your Begin...

1. You must specify PPROD for the volume ID when you save the productlibraries to tape.

2. It is recommended that you save the licensed program products to thesame tape where you saved the SSP operating system.

3. Make sure the tape cartridge you initialized with a volume ID of PPROD isin the tape drive.

4. The session library must be set to #LIBRARY to use the procedures in thissection. Use the SLIB procedure to accomplish this.

a. On the command line of the SSP system console, type

SLIB ð

b. Press Enter .

Note: It is recommended that you place the AS/400 Advanced 36 machine in ded-icated state prior to saving the licensed program products. This will ensureall parts of the licensed program products are saved. If you left the AS/400Advanced 36 machine in dedicated state, you can proceed to save thelicensed program products. Otherwise, put the AS/400 Advanced 36machine in dedicated state. For information on how to put the AS/400Advanced 36 machine in dedicated state, see “Putting the AS/400Advanced 36 Machine In a Dedicated State” on page 16-1.

The licensed program products can be saved in the following ways:

1. Interactively

You key each save procedure on the command line at the SSP systemconsole. Saving the licensed program products this way is very time con-suming and the tape LEAVE option does not work properly. The advantage tosaving this way is that no previous preparation is required.

2. Using a previously created procedure

You use a previously created procedure that contains all the procedures youwould have keyed in if you were to save the licensed program products interac-tively. Saving the licensed program products this way is less time consumingand the tape LEAVE option does work properly. The disadvantage is that thisway requires previous preparation.

Note: During the saving of the licensed program products, if you receivemessage SYS-2509, #######--Specified members not in thislibrary, record the name of the member shown in the message text.Select option 1 for the message, this causes the save to continue. Ifyou are experiencing AS/400 Advanced 36 machine problems and havereported these problems to your service representative, contact themagain. This time mention you received message SYS-2509 during asave of your licensed program product and give them the name of themodule in the message text. If you are not experiencing any AS/400Advanced 36 machine problems, ignore the error message.

25-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 211: Iseries

Saving and Restoring SSP

Saving the Licensed Program Products InteractivelyTo save the licensed program products interactively:

1. Determine which programming support you have installed on your AS/400Advanced 36 machine.

2. Using Figure 25-1 on page 25-10, find the programming support functions youhave installed. If the procedure name for the programming support function isnot SAVE, SAVEFLDR, SAVELIBR or DICTSAVE:

a. Type that procedure name on the command line at the SSP systemconsole.

For example, if the programming support function was DFU, the procedurename is DFUSAVE. DFUSAVE is not SAVE, SAVEFLDR, SAVELIBR orDICTSAVE, so DFUSAVE would be typed on the command line at the SSPsystem console.

b. Press Enter .

If the procedure name for the programming support function is SAVE,SAVEFLDR, SAVELIBR or DICTSAVE, follow the steps below:

� If the procedure name is SAVE:

a. On the command line at the SSP system console, type

SAVE

b. Press the Help key.

The help display for the SAVE procedure appears.

c. In the Name of file to save field, type the file name. See Figure 25-1on page 25-10 for the file name of the programming support that is tobe saved.

d. Press Enter .

A second help display appears.

e. In the Retention days field, type

999

f. In the Volume ID field, type

PPROD

g. In the Location of file field, type

TC

h. Press Enter .

A third help display appears.

Note: No values need to be specified for the other parameters on theSAVE procedure. The default values will work.

i. Press Enter .

� If the procedure name is SAVEFLDR :

a. On the command line at the SSP system console, type

SAVEFLDR

b. Press the Help key.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-5

Page 212: Iseries

Saving and Restoring SSP

The help display for the SAVEFLDR procedure appears.

c. In the Name of folder to save field, type the folder name. SeeFigure 25-1 on page 25-10 for the folder name of the programmingsupport that is to be saved.

d. In the Volume ID field, type

PPROD

e. In the Location of file field, type

TC

f. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theSAVEFLDR procedure. The default values will work.

g. Press Enter .

� If the procedure name is SAVELIBR :

a. On the command line at the SSP system console, type

SAVELIBR

b. Press the Help key.

The help display for the SAVELIBR procedure appears.

c. In the Name of library to be saved field, type the library name. SeeFigure 25-1 on page 25-10 for the library name of the programmingsupport that is to be saved.

d. In the Volume ID field, type

PPROD

e. In the Location of file field, type

TC

f. Press Enter .

Note: No values need to be specified for the other parameters on theSAVELIBR procedure. The default values will work.

� If the procedure name is DICTSAVE:

a. On the command line at the SSP system console, type

DICTSAVE

b. Press the Help key.

The help display for the DICTSAVE procedure appears.

c. In the Dictionary to load field, type the dictionary ID. See Figure 25-1on page 25-10 for the dictionary ID of the programming support that isto be saved.

d. Press Enter .

3. Repeat step 2 on page 25-5 for each of the programming support functionsinstalled on your AS/400 Advanced 36 machine.

You have saved the Licensed Program Products interactively.

25-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 213: Iseries

Saving and Restoring SSP

4. If you put the AS/400 Advanced 36 machine in a dedicated state, and you aregoing to save the other SSP system files, leave the AS/400 Advanced 36machine in dedicated state.

5. If you are not going to save the other SSP system files, remove the dedicationas follows.

a. On the command line at the SSP system console, type

START SYSTEM

b. Press Enter .

Creating a Procedure to Save Licensed Program ProductsTo create a procedure to save the licensed program products (features andproducts):

1. Use DSU, FSEDIT or SEU to edit a new procedure library member. The nameof the procedure and the library you put the procedure in are your choice. Youmight choose SAVELPP in #LIBRARY.

For more information on creating a procedure, see “Making Procedures” in theS/36 System Reference book, SC21-9020.

2. Determine which programming support you have installed on your AS/400Advanced 36 machine.

3. Using Figure 25-1 on page 25-10, find the programming support functions youhave installed. If the procedure name for the programming support function isnot SAVE, SAVEFLDR, SAVELIBR or DICTSAVE, add that procedure name tothe procedure you are editing. For example, if the programming support func-tion was DFU, the procedure name is DFUSAVE. DFUSAVE is not SAVE,SAVEFLDR, SAVELIBR or DICTSAVE, so you need to add DFUSAVE to thenew procedure.

If the procedure name for the programming support function is SAVE,SAVEFLDR, SAVELIBR or DICTSAVE, add that procedure with all the neces-sary parameters to the new procedure.

� If the procedure name is SAVE,

add the following to the new procedure:

SAVE file name,999,,PPROD,TC,,,,,,,LEAVE

where file name is the file name of the programming support that is to besaved. See Figure 25-1 on page 25-10 for the file name of the program-ming support that is to be saved.

Note: On the SAVE procedure there are parameters that were not speci-fied (the null parameters ',,'). The default values are used for theseparameters.

� If the procedure name is SAVEFLDR ,

add the following to the new procedure:

SAVEFLDR folder name,999,PPROD,TC,,,LEAVE

where folder name is the file name of the programming support that is tobe saved. See Figure 25-1 on page 25-10 for the folder name of the pro-gramming support that is to be saved.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-7

Page 214: Iseries

Saving and Restoring SSP

Note: On the SAVEFLDR procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

� If the procedure name is SAVELIBR ,

add the following to the new procedure:

SAVELIBR library name,999,PPROD,,,TC,LEAVE

where library name is the file name of the programming support that is tobe saved. See Figure 25-1 on page 25-10 for the library name of the pro-gramming support that is to be saved.

Note: On the SAVELIBR procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

� If the procedure name is DICTSAVE,

add the following to the new procedure:

DICTSAVE dictionary ID

where dictionary ID is the file name of the programming support that is tobe saved. See Figure 25-1 on page 25-10 for the dictionary ID of the pro-gramming support that is to be saved.

4. Repeat step 3 on page 25-7 for each of the programming support functionsyou have installed on your AS/400 Advanced 36 machine.

5. After all the procedures used to save the program products are added to thenew procedure, end the edit session and replace the procedure member in thelibrary.

Saving the Licensed Program Products Using a PreviouslyCreated ProcedureTo save the licensed program products with a procedure you previously created:

1. If you have not created a procedure to save licensed program products, followthe steps described in section “Creating a Procedure to Save LicensedProgram Products” on page 25-7.

2. Set the session library to the library that contains the procedure you created tosave the licensed program products.

a. On the command line at the SSP system console, type

SLIB library name

where library name is the name of the library that contains the procedureyou created to save the licensed program products.

b. Press Enter .

3. On the command line at the SSP system console, type the name of the proce-dure you created to save the licensed program products.

4. Press Enter .

The procedure you created begins to run all the save procedures you added toit.

5. When the command entry display appears again, the procedure has ended andyou have completed the task of saving the licensed program products.

25-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 215: Iseries

Saving and Restoring SSP

6. If you put the AS/400 Advanced 36 machine in a dedicated state and you aregoing to save the other SSP system files, leave the AS/400 Advanced 36machine in dedicated state.

7. If you are not going to save the other SSP system files, do as follows:

a. On the command line at the SSP system console, type

START SYSTEM

b. Press Enter .

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-9

Page 216: Iseries

Saving and Restoring SSP

Figure 25-1 (Page 1 of 2). Licensed Program Product Save Procedures

Programming Support to beSaved

Procedure Name File, Folderor Library Nameor Dictionary ID

Programmer and OperatorProductivity Aid

POPSAVE

Value Added SoftwarePackage

VASPSAVE

Migration Analyzer ANLZSAVE

DFU DFUSAVE

WSU WSUSAVE

SEU SEUSAVE

SDA SDASAVE

RPG II RPGSAVE

COBOL COBSAVE

BASIC BASSAVE

FORTRAN FORTSAVE

Assembler ASMSAVE

DisplayWrite/36 TEXTSAVESAVEFLDR #PRFFLDR

Personal Service/36 OFCSAVE

Document Library Services DLSSAVE

PROFS Bridge PROFSAVE

QUERY/36 QRYSAVE

Object Distribution Facility ODFSAVE

Transition Aid TNSAVE

Online Information for:Object Distribution FacilityDisplayWrite/36

Personal Services/36

Document Library ServicesQuery/36IDDU

DSUShared Folders

SAVEFLDRSAVEFLDRSAVEFLDRSAVEFLDRSAVESAVELIBRSAVEFLDRSAVEFLDRSAVEFLDRSAVEFLDRSAVEFLDRSAVEFLDRSAVESAVESAVESAVEFLDRSAVEFLDR

#OFCFLDR 1

#WPFLDR 2

WPDOCS#OFCFLDR 1

$OUDRSMP#DQRYSMP#DIRSMP#DLSFLDR#QRYFLDR#IDDFLDR#IDDUSMP#USERDCTCUSTCDTNAMEADDRNAMEPHON#DSUFLDR#WPFLDR 2

25-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 217: Iseries

Saving and Restoring SSP

Figure 25-1 (Page 2 of 2). Licensed Program Product Save Procedures

Programming Support to beSaved

Procedure Name File, Folderor Library Nameor Dictionary ID

DisplayWrite/36Language Dictionaries:EnglishFrenchFrench-CanadianSpanishItalianDanishGermanSwedishNorwegianDutchIcelandicPortuguese

DICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVEDICTSAVE

ENGLISHFRENCHFRENCHCASPANISHITALIANDANISHGERMANSWEDISHNORWEGIANDUTCHICELANDICPORTUGUESE

Development Support Utility DSUSAVE

Business Graphics Utility/36 BGUSAVE

PC Support/36, including:Shared FoldersPC Support/36 OrganizerPC Support/36 Pass-Thru

IWSAVE 3

PC Support/36 IBM Token-Ring Network Support

LRTRSAVE

PC Support/36 Work StationFeature

WSFSAVE

Multinational Character Set 4

ConversionMCSTSAVE

Software Distribution Support SWDSAVE

LAN Communications Support LANSAVE

Character Generator Utility 4 CGUSAVE

IGC Sort 4 SRTXSAVE

Support for Printing/ReadingOnline Information

DOCPSAVE

3278 Device Emulation viaIBM Personal Computer

SAVE #EPPCLD1

Table notes:

1 #OFCFLDR is used by both Personal Services/36 and Object Distribution Facility. If youhave both functions on your AS/400 Advanced 36 machine, it is only necessary to save thefolder once.

2 #WPFLDR is used by both DisplayWrite/36 and Shared Folders. If you have both func-tions on your AS/400 Advanced 36 machine, it is only necessary to save the folder once.

3 The Shared Folders procedure (SHRFSAVE), the PC Support/36 Organizer procedure(PCOSAVE) and the PC Support/36 Pass-Thru procedure (IWPTSAVE) are included in thebase PC Support/36 procedure IWSAVE.

4 This programming support would only be supported on the Ideographic version of the SSP.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-11

Page 218: Iseries

Saving and Restoring SSP

Saving Other SSP System FilesThis section describes how to save the following SSP system files:

� Password security file

On your AS/400 Advanced 36 machine if password security is activated.

� Resource security file

On your AS/400 Advanced 36 machine if resource security is activated.

� Network Resource Directory

On your AS/400 Advanced 36 machine if you use Distributed Data Manage-ment, APPC or APPN.

� Extended Character Set files

On your AS/400 Advanced 36 machine if you have an Ideographic version ofthe SSP.

� SSP Configuration Members

Although SSP configuration members are not really files, they are included inthis section because they should be saved when you backup your AS/400Advanced 36 machine. Configuration members are used to change the SSPmaster configuration record on your AS/400 Advanced 36 machine.

Before You Begin...

1. It is recommended that you save these SSP system files to the same tapesthat were used to save the licensed program products.

2. If you are going to save the password or resource security files, you mustdetermine the name of the tape file these SSP system files are to be savedto (For example: USERIDFL and RESOURFL).

3. If you are going to save the extended character set files, you may want touse a name other than #EXT1818 and #EXT2424. If you do, you shoulddetermine these names before you start the save (For Example: EXT18FILand EXT24FIL).

4. Make sure the tape cartridge you initialized with a volume ID of PPROD isin the tape drive.

5. The session library must be set to #LIBRARY to use the procedures in thissection. Use the SLIB procedure to accomplish this.

a. On the command line at the SSP system console, type

SLIB ð

b. Press Enter .

Note: It is recommended that you place the AS/400 Advanced 36 machine in ded-icated state prior to saving the other SSP system files. This ensures thefiles get saved correctly. You may have done this earlier when saving theSSP operating system or the licensed program products. If you left theAS/400 Advanced 36 machine in dedicated state, you can proceed. Forinformation on how to put the AS/400 Advanced 36 machine in dedicatedstate, see “Putting the AS/400 Advanced 36 Machine In a Dedicated State”on page 16-1.

You can save other SSP system files in the following ways:

25-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 219: Iseries

Saving and Restoring SSP

1. Interactively

You key each save procedure on the command line at the SSP systemconsole. Saving the other SSP system files this way is very time consumingand the tape LEAVE option does not work properly. The advantage to savingfiles this way is that no previous preparation is required.

2. Using a previously created procedure

This previously created procedure contains all procedures you would havekeyed in if you were to save the other SSP system files interactively.

Saving the other SSP system files this way is less time consuming and thetape LEAVE option functions properly. The disadvantage to saving this way isthat some previous preparation is required.

Saving Other SSP System Files InteractivelyTo save any of these other SSP system files interactively, do as follows:

1. If you have password security activated on your AS/400 Advanced 36 machine,complete the following steps to save the password security file:

a. On the command line at the SSP system console, type

SECSAVE USERID

b. Press the Help key.

The help display for the SECSAVE procedure appears.

c. In the Name of file to create field, type the name of the tape file where youwant to save the password security file.

d. In the Location of file field, type

TC

e. Press Enter .

A second help display appears.

f. In the Volume ID of tape field, type the volume ID of the tape used for thesave. If this is the same tape that was used to save the licensed programproducts, the volume ID is PPROD.

Note: No values need to be specified for the other parameters on theSECSAVE procedure. The default values will work.

g. Press Enter .

The password security file is saved to tape.

2. If you have resource security activated on your AS/400 Advanced 36 machine,complete the following steps to save the resource security file:

a. On the command line at the SSP system console, type

SECSAVE RESOURCE

b. Press the Help key.

The help display for the SECSAVE procedure appears.

c. In the Name of file to create field, type the name of the tape file where youwant to save the resource security file.

d. In the Location of file field, type

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-13

Page 220: Iseries

Saving and Restoring SSP

TC

e. Press Enter .

A second help display appears.

f. In the Volume ID of tape field, type the volume ID of the tape used for thesave. If this is the same tape that was used to save the licensed programproducts, the volume ID is PPROD.

Note: No values need to be specified for the other parameters on theSECSAVE procedure. The default values will work.

g. Press Enter .

The resource security file is saved to tape.

3. If you have a Network Resource Directory (NRD) on your AS/400 Advanced 36machine, complete the following steps to save the Network Resource Directory:

a. On the command line at the SSP system console, type

SAVENRD

b. Press the Help key.

The help display for the SAVENRD procedure appears.

c. In the Name of directory to be saved field, type

#NRD.FLE

d. In the Volume ID field, type the volume ID of the tape used for the save. Ifthis is the same tape that was used to save the licensed program products,the volume ID is PPROD.

e. In the Location of directory field, type

TC

f. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theSAVENRD procedure. The default values will work.

g. Press Enter .

The Network Resource Directory is saved to tape.

4. If you have an Ideographic version of the SSP and you use the extended char-acter set files #EXT1818 or #EXT2424 on your AS/400 Advanced 36 machine,save the extended character set files.

To save the #EXT1818 file:

a. On the command line at the SSP system console, type

SAVEEXTN #EXT1818

b. Press the Help key.

The help display for the SAVEEXTN procedure appears.

c. In the Name of file field, type the name of the tape file where you want tosave the #EXT1818 file. If you want the name to be #EXT1818, leave theprompt blank.

25-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 221: Iseries

Saving and Restoring SSP

d. In the Volume ID field, type the volume ID of the tape used for the save. Ifthis is the same tape that was used to save the licensed program products,the volume ID is PPROD.

Note: No values need to be specified for the other parameters on theSAVEEXTN procedure. The default values will work.

e. Press Enter .

The extended character set file #EXT1818 is saved to tape.

To save the #EXT2424 file,

a. On the command line at the SSP system console, type

SAVEEXTN #EXT2424

b. Press the Help key.

The help display for the SAVEEXTN procedure appears.

c. In the Name of file field, type the name of the tape file where you want tosave the #EXT2424 file. If you want the name to be #EXT2424, leave theprompt blank.

d. In the Volume ID field, type the volume ID of the tape used for the save. Ifthis is the same tape that was used to save the licensed program products,the volume ID is PPROD.

Note: No values need to be specified for the other parameters on theSAVEEXTN procedure. The default values will work.

e. Press Enter .

The extended character set file #EXT2424 is saved to tape.

If you want to save the SSP configuration members on your AS/400 Advanced36 machine, complete the following steps:

a. On the command line at the SSP system console, type

SAVELIBR

b. Press the Help key.

The help display for the SAVELIBR procedure appears.

c. In the Name of library to be saved field, type the library name that containsthe SSP configuration members.

Normally, these members are stored in a library named #CNFGLIB.

d. In the 'Volume ID' field, type the volume ID of the tape used for the save.If this is the same tape that was used to save the licensed program pro-ducts, the volume ID is PPROD.

e. In the Location of file field, type

TC

Note: No values need to be specified for the other parameters on theSAVELIBR procedure. The default values will work.

f. Press Enter .

The library containing your configuration members is saved to tape.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-15

Page 222: Iseries

Saving and Restoring SSP

You have completed the task of saving the other SSP system files interactively.If you put the AS/400 Advanced 36 machine in a dedicated state, remove thededication:

a. On the command line at the SSP system console, type

START SYSTEM

b. Press Enter .

Creating a Procedure to Save Other SSP System FilesTo create a procedure to save the other SSP system files such as password secu-rity file and resource security file:

1. Use DSU, FSEDIT or SEU to edit a new procedure library member. The nameof the procedure and the library you put it in is your choice. It may beSAVEOSF in #LIBRARY. For more information on creating a procedure, see“Making Procedures” in the S/36 System Reference book, SC21-9020.

You may want to print a copy of the save procedure that you created to remindyou of the order the products were saved.

2. Copy the save procedure and give it a new name.

3. Replace the save statements as follows:

a. If you have password security activated on your AS/400 Advanced 36machine, add the following to the new procedure:

SECSAVE USERID,file name,TC,volume ID,999,,,LEAVE

where file name is the name of the tape file where you want to save thepassword security file and volume ID is the volume ID of the tape used forthe save. If this is the same tape that was used to save the licensedprogram products, the volume ID is PPROD.

Note: On the SECSAVE procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

b. If you have resource security activated on your AS/400 Advanced 36machine, add the following to the new procedure:

SECSAVE RESOURCE,file name,TC,volume ID,999,,,LEAVE

where file name is the name of the tape file where you want to save theresource security file and volume ID is the volume ID of the tape used forthe save. If this is the same tape that was used to save the licensedprogram products, the volume ID is PPROD.

Note: On the SECSAVE procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

c. If you have a Network Resource Directory (NRD) on your AS/400Advanced 36 machine, add the following to the new procedure:

SAVENRD #NRD.FLE,volume ID,TC,,,LEAVE,999

where volume ID is the volume ID of the tape used for the save. If this isthe same tape that was used to save the licensed program products, thevolume ID is PPROD.

25-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 223: Iseries

Saving and Restoring SSP

Note: On the SAVENRD procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

d. If you have the extended character set file #EXT1818 on your AS/400Advanced 36 machine, add the following to the new procedure:

SAVEEXTN #EXT1818,file name,volume ID,999,TC,,,,LEAVE

where file name is the name of the tape file where you want to save the#EXT1818 file and volume ID is the volume ID of the tape used for thesave. If this is the same tape that was used to save the licensed programproducts, the volume ID is PPROD.

If you want the file name to be #EXT1818, you could specify a null value(,,) for file name.

Note: On the SAVEEXTN procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

e. If you have the extended character set file #EXT2424 on your AS/400Advanced 36 machine, add the following to the new procedure:

SAVEEXTN #EXT2424,file name,volume ID,999,TC,,,,LEAVE

where file name is the name of the tape file where you want to save the#EXT2424 file and volume ID is the volume ID of the tape used for thesave. If you want the name to be #EXT2424, specify a null value (,,). Ifthis is the same tape that was used to save the licensed program products,the volume ID is PPROD.

Note: On the SAVEEXTN procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

f. If you want to save the SSP configuration members on your AS/400Advanced 36 machine, add the following to the new procedure:

SAVELIBR library name,999,volume ID,,,TC,LEAVE

where library name is the name of the library that contains the SSP config-uration members and volume ID is the volume ID of the tape used for thesave.

Normally, the SSP configuration members are stored in a library named#CNFGLIB. If the tape used for save is the same tape that was used tosave the licensed program products, the volume ID is PPROD.

Note: On the SAVELIBR procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

g. After all the procedures used to save the other SSP system files are addedto the new procedure, end the edit session and replace the proceduremember in the library.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-17

Page 224: Iseries

Saving and Restoring SSP

Saving the Other SSP System Files Using a Previously CreatedProcedureTo save the other SSP system files using a procedure you created previously, doas follows:

1. If you have not created the procedure, follow the steps described in section“Creating a Procedure to Save Other SSP System Files” on page 25-16.

2. Set the session library to the library that contains the procedure you created tosave the other SSP system files.

a. On the command line at the SSP system console, type

SLIB library name

where library name is the name of the library that contains the procedureyou created to save the other SSP system files.

b. Press Enter .

3. On the command line at the SSP system console, type the name of the proce-dure you created to save the other SSP system files.

4. Press Enter .

The procedure you created begins to run all the save procedures you added toit.

5. When the command entry display appears again, the procedure has ended andyou have completed the task of saving the other SSP system files using a pre-viously created procedure.

6. If you put the AS/400 Advanced 36 machine in a dedicated state, you must usethe START SYSTEM command to remove the dedication.

a. On the command line at the SSP system console, type

START SYSTEM

b. Press Enter .

Restoring the SSP Operating SystemYou may be directed by your software support personnel to restore the SSP oper-ating system if the SSP operating system is experiencing problems. You canrestore the SSP operating system from a backup tape in two ways:

� If the SSP operating system can still perform an IPL but is producing unex-pected results, use the Restore Library (RESTLIBR) procedure. Go to “Usingthe Restore Library Procedure to Restore the SSP Operating System” onpage 25-19 to restore the SSP operating system using the Restore Library pro-cedure.

� If the SSP operating system is damaged and cannot perform an IPL, use theStart AS/400 Advanced 36 Machine (STRM36) CL command to perform an IPL(restore) of the SSP operating system from tape. Go to “Restoring the SSPOperating System Using the Start AS/400 Advanced 36 Machine Command” onpage 25-21 to restore the SSP operating system.

25-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 225: Iseries

Saving and Restoring SSP

Using the Restore Library Procedure to Restore the SSPOperating SystemUse the Restore Library (RESTLIBR) procedure to restore the SSP operatingsystem library if it is running but is experiencing problems, or when you want to goback to the previous PTF level of SSP operating system.

Note: If Licensed program product libraries are to be restored, this must be doneafter the SSP operating system is loaded.

To restore the SSP operating system using the RESTLIBR procedure, do the fol-lowing:

1. Insert the tape containing the SSP operating system (PPROD - BACKUP1) inthe tape cartridge drive.

2. Type the following procedure on the command line at the SSP system console:

RESTLIBR #LIBRARY,,,,,,TC

3. Press Enter .

The following display appears.

à@ ð Input-Output

RESTLIBR #LIBRARY,,,,,,TC RESTLIBR procedure is running.

á ñ

After a few minutes, the display clears. The next display should be the SSPGENERATION AND RELOAD - SIGN ON display.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-19

Page 226: Iseries

Saving and Restoring SSP

à@ ðSSP GENERATION AND RELOAD - SIGN ON

User ID . . . . . . . . . . . . . . . . . . . SYSSSP__

Password . . . . . . . . . . . . . . . . . . _________

4. Enter the information on the SSP GENERATION AND RELOAD - SIGN ONdisplay using the following instructions:

a. User ID: Type your user ID (SYSSSP is the default). If the Passwordprompt is not displayed, the user ID could be your name or initials. If thePassword prompt is displayed, type the user ID assigned to you.

b. Password: Type your 4-character password. This password does notappear on the display when you type it. If security is not active, the Pass-word prompt is not displayed.

c. After you type the information on the SSP GENERATION ANDRELOAD – SIGN ON display, press Enter .

An initial program load (IPL) begins from tape. The display clears and the SSPGENERATION AND RELOAD – INPUT/OUTPUT display appears. If thisdisplay does not appear, refer to the System Problem Determination–SSPbook, SC21-8296.

à@ ðSSP GENERATION AND RELOAD - INPUT/OUTPUT

Processing input from:

Location - TC

Volume ID - SAVEDS

5. This display may ask you to perform an action, such as insert another tape. Ifyou are asked to perform an action, perform the action that is requested andpress Enter .

25-20 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 227: Iseries

Saving and Restoring SSP

After a few minutes, a display, similar to the following, appears:

à@ ðSSP GENERATION AND RELOAD - MESSAGES

SSP generation complete, MSIPL from disk started.

á ñ

This display informs you when the SSP operating system restore is complete.There is a delay of a few seconds, then the AS/400 Advanced 36 machineautomatically starts an IPL from disk. When this happens, the display clears.

After a few minutes, the AS/400 Advanced 36 machine SIGN ON displayappears. If this display does not appear, refer to the System ProblemDetermination–SSP book, SC21-8296.

Continue by signing on to the AS/400 Advanced 36 machine. For directions,see Chapter 2 of the Operating Your Computer–SSP Operating System book,SC21-8297.

Restoring the SSP Operating System Using the Start AS/400Advanced 36 Machine CommandIf the SSP operating system becomes damaged and you cannot perform an IPL,you can use the Start AS/400 Advanced 36 Machine (STRM36) CL command torestore the SSP operating system.

Before Your Begin...

1. If the AS/400 Advanced 36 machine is still running, stop it.

For directions, see Chapter 16, “Stopping an AS/400 Advanced 36Machine.”

2. Make sure the workstation designated as the SSP system console is turnedon.

To perform an IPL from tape:

1. Insert the tape that contains the backup of the SSP operating system (PPROD- BACKUP1) in the tape cartridge tape drive.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-21

Page 228: Iseries

Saving and Restoring SSP

2. On the command line of the OS/400 system console, type

STRM36

3. Press F4.

The command prompt for Start M36 (STRM36) appears.

4. In the Machine field, type the name of the AS/400 Advanced 36 machine that isto be restored.

5. In the Library field, type the name of the OS/400 library that contains theAS/400 Advanced 36 machine that is to be restored.

6. In the IPLtype field, type

\TC

7. Press Enter .

The following message appears at the bottom of the display:

Request to start machine-name put on job queue.

where machine-name is the name of the AS/400 Advanced 36 machine that youspecified.

After a few minutes, the display clears for the workstation designated as thesystem console for the AS/400 Advanced 36 machine that you are restoring.The next display should be the SSP GENERATION AND RELOAD - SIGN ONdisplay.

à@ ðSSP GENERATION AND RELOAD - SIGN ON

User ID . . . . . . . . . . . . . . . . . . . SYSSSP__

Password . . . . . . . . . . . . . . . . . . _________

8. Enter the following information on the SSP GENERATION AND RELOAD -SIGN ON display:

a. Type your user ID in the User ID field (SYSSSP is the default).

If the Password field is not shown, you could use your name, initials, orany other letters for the user ID.

b. If the Password field is shown, type your password in the Password field.

The password is the four-character user ID assigned to you. This pass-word does not appear on the display when you type it. If security is notactive, the Password field is not displayed.

c. Press Enter .

An initial program load (IPL) begins from tape. The display clears and the SSPGENERATION AND RELOAD – INPUT/OUTPUT display appears. If thisdisplay does not appear, refer to the System Problem Determination–SSPbook, SC21-8296.

25-22 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 229: Iseries

Saving and Restoring SSP

à@ ðSSP GENERATION AND RELOAD - INPUT/OUTPUT

Processing input from:

Location - TC

Volume ID - SAVEDS

9. This display may ask you to perform an action, such as insert another tape. Ifyou are asked to perform an action, perform the requested action and pressEnter .

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-23

Page 230: Iseries

Saving and Restoring SSP

After a few minutes, a display, similar to the following, appears:

à@ ðSSP GENERATION AND RELOAD - MESSAGES

SSP generation complete, MSIPL from disk started.

á ñ

This display informs you when the SSP operating system restore is complete.There is a delay of a few seconds, then the AS/400 Advanced 36 machineautomatically starts an IPL from disk. When this happens, the display clears.

After a few minutes, the AS/400 Advanced 36 machine SIGN ON displayappears. If this display does not appear, refer to the System ProblemDetermination–SSP book, SC21-8296.

Continue by signing on to the AS/400 Advanced 36 machine. For directions,see Chapter 2 of the Operating Your Computer–SSP Operating System book,SC21-8297.

Restoring the Licensed Program ProductsProduct libraries must be restored from tape using specific restore commands forthat product (for example, RPGLOAD for RPG and SEULOAD for SEU).

Other files, folders and libraries that are part of the program product must berestored using the RESTORE, RESTFLDR and RESTLIBR procedures.

Before Your Begin...

1. Insert the tape cartridge you used during the save of the licensed programproducts in the tape drive. The tape has a volume ID of PPROD.

2. The session library must be set to #LIBRARY to use the procedures in thissection. Use the SLIB procedure to set the session library as follows:

a. On the command line at the SSP system console, type

SLIB ð

b. Press Enter .

25-24 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 231: Iseries

Saving and Restoring SSP

You can restore the licensed program products in any of the following ways:

� Interactively

You key each restore procedure on the command line at the SSP systemconsole. Restoring the licensed program products this way is very time con-suming and the tape LEAVE option does not work properly. The advantage tothis way is that no previous preparation is required.

� Using a previously created procedure.

This previously created procedure contains all of the procedures you wouldhave typed if you were to restore the licensed program products interactively.Restoring the licensed program products this way is less time consuming andthe tape LEAVE option works properly. The disadvantage to this way ofrestoring is that some previous preparation is required.

Restoring the Licensed Program Products InteractivelyTo restore the licensed program products interactively:

1. Determine which licensed program products you want to restore to your AS/400Advanced 36 machine.

2. Using Figure 25-2 on page 25-30, find the programming support functions youwant to restore. If the procedure name for the programming support function isnot RESTORE, RESTFLDR, RESTLIBR or DICTLOAD:

a. Type that procedure name on the command line at the SSP systemconsole.

b. Press Enter .

For example, if the programming support function was DFU, the procedurename is DFULOAD. DFULOAD is not RESTORE, RESTFLDR, RESTLIBRor DICTLOAD, so DFULOAD would be typed on the command line at theSSP system console.

If the procedure name for the programming support function is RESTORE,RESTFLDR, RESTLIBR or DICTLOAD, follow the steps below:

� If the procedure name is RESTORE:

a. On the command line at the SSP system console, type

RESTORE

b. Press the Help key.

The help display for the RESTORE procedure appears.

c. In the Name of file to restore field, type the file name. See Figure 25-2on page 25-30 for the file name of the programming support that is tobe restored.

d. Press Enter .

A second help display appears.

e. In the Location of file field, type

TC

f. Press Enter .

A third help display appears.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-25

Page 232: Iseries

Saving and Restoring SSP

Note: No values need to be specified for the other parameters on theRESTORE procedure. The default values will work.

g. Press Enter .

� If the procedure name is RESTFLDR:

a. On the command line at the SSP system console, type

RESTFLDR

b. Press the Help key.

The help display for the RESTFLDR procedure appears.

c. In the Name of folder containing folder to restore field, type the foldername. See Figure 25-2 on page 25-30 for the folder name of the pro-gramming support that is to be restored.

d. In the Location of file field, type

TC

e. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theRESTFLDR procedure. The default values will work.

f. Press Enter .

� If the procedure name is RESTLIBR :

a. On the command line at the SSP system console, type

RESTLIBR

b. Press the Help key.

The help display for the RESTLIBR procedure appears.

c. In the Name of library to be restored field, type the library name. SeeFigure 25-2 on page 25-30 for the library name of the programmingsupport that is to be restored.

d. In the Location of file field, type

TC

e. Press Enter .

Note: No values need to be specified for the other parameters on theRESTLIBR procedure. The default values will work.

� If the procedure name is DICTLOAD :

a. On the command line at the SSP system console, type

DICTLOAD

b. Press the Help key.

The help display for the DICTLOAD procedure appears.

c. In the Dictionary to load field, type the dictionary ID. See Figure 25-2on page 25-30 for the dictionary ID of the programming support that isto be restored.

d. Press Enter .

25-26 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 233: Iseries

Saving and Restoring SSP

Note: No values need to be specified for the other parameters on theDICTLOAD procedure. The default values will work.

3. Repeat step 2 on page 25-25 for each of the programming support functionsyou want to restore.

4. You have completed the task of restoring the licensed program products inter-actively. If you are not going to restore the other SSP system files, remove thetape cartridge from the tape drive and return it to its protective container.

Creating a Procedure to Restore Licensed Program ProductsNote: The procedure you are creating will perform more efficiently if the order that

the products are restored is the same as the order that the products weresaved to tape. This efficiency is achieved because the tape does not needrewinding between restores. The procedure will work correctly even if theorder is the same.

To create a procedure to restore the licensed program products (features and pro-ducts), do as follows:

1. Do one of the following:

� Method 1

a. Use the print option P of the LIBR function to print a copy of the proce-dure you created to save the licensed program products. You can usethe printed copy as a reminder of the order the products are saved.

b. Complete the other steps in this section as they are written.

� Method 2

a. Use the copy option Y of the LIBR function to create a copy of the pro-cedure you created to save the licensed program products.

Note: Be sure you rename the procedure while you are making thecopy.

b. Instead of adding the statements indicated in the other steps in thistopic, replace the save statements with the restore statements.

2. Use DSU, FSEDIT or SEU to edit a new procedure library member. The nameof the procedure and the library you put it in is your choice. You could chooseRESTLPP in #LIBRARY. For more information on creating a procedure, see“Making Procedures” in the S/36 System Reference book, SC21-9020.

3. Determine which programming support you want to restore to your AS/400Advanced 36 machine.

4. Using the Figure 25-2 on page 25-30, find the programming support functionsyou want to restore.

5. If the procedure name for the programming support function is not RESTORE,RESTFLDR, RESTLIBR or DICTLOAD, add that procedure name to the proce-dure you are editing. For example, if the programming support function wasDFU, the procedure name is DFULOAD. DFULOAD is not RESTORE,RESTFLDR, RESTLIBR or DICTLOAD, so you would add DFULOAD to thenew procedure.

6. If the procedure name for the programming support function is RESTORE,RESTFLDR, RESTLIBR or DICTLOAD, add that procedure with all the neces-sary parameters to the new procedure.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-27

Page 234: Iseries

Saving and Restoring SSP

� If the procedure name is RESTORE:

add the following to the new procedure:

RESTORE file name,,,,,,TC,,,,,,,,,,,LEAVE

where file name is the file name of the programming support that is to berestored. See Figure 25-2 on page 25-30 for the file name of the program-ming support that is to be restored.

Note: On the RESTORE procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

� If the procedure name is RESTFLDR,

add the following to the new procedure:

RESTFLDR folder name,,,TC,,,LEAVE

where folder name is the folder name of the programming support that is tobe restored. See Figure 25-2 on page 25-30 for the folder name of theprogramming support that is to be restored.

Note: On the RESTFLDR procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

� If the procedure name is RESTLIBR ,

add the following to the new procedure:

RESTLIBR library name,,,,,,TC,LEAVE

where library name is the library name of the programming support that isto be restored. See Figure 25-2 on page 25-30 for the library name of theprogramming support that is to be restored.

Note: On the RESTLIBR procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

� If the procedure name is DICTLOAD ,

add the following to the new procedure:

DICTLOAD dictionary ID

where dictionary ID is the dictionary ID of the programming support thatis to be restored. See Figure 25-2 on page 25-30 for the dictionary ID ofthe programming support that is to be restored.

Note: On the DICTLOAD procedure there are parameters that were notspecified (the null parameters ',,'). The default values are used forthese parameters.

7. Repeat step 4 on page 25-27 for each of the programming support functionsyou want to restore.

8. After all the procedure names for the programming support you want to restoreare added to the new procedure, end the edit session and replace the memberin the library.

25-28 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 235: Iseries

Saving and Restoring SSP

Restoring the Licensed Program Products from a PreviouslyCreated ProcedureTo restore the licensed program products using a procedure you createdpreviously:

1. If you have not created the procedure, follow the steps described in section“Creating a Procedure to Restore Licensed Program Products” on page 25-27and then return here.

2. Set the session library to the library that contains the procedure you created torestore the licensed program products.

a. On the command line at the SSP system console, type

SLIB library name

where library name is the name of the library that contains the procedureyou created to restore the licensed program products.

b. Press Enter .

3. On the command line at the SSP system console, type the name of the proce-dure you created to restore the licensed program products.

4. Press Enter .

5. When the command entry display appears again, the procedure has ended andyou have completed the task of restoring the licensed program products.

6. If you are not going to restore the other SSP system files, remove the tapecartridge from the tape drive and return it to its protective container.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-29

Page 236: Iseries

Saving and Restoring SSP

Figure 25-2 (Page 1 of 3). Licensed Program Product Restore Procedures

Programming Support to beSaved

Procedure Name File, Folderor Library Nameor Dictionary ID

Programmer and OperatorProductivity Aid

POPLOAD

Value Added SoftwarePackage

VASPLOAD

Migration Analyzer ANLZLOAD

DFU DFULOAD

WSU WSULOAD

SEU SEULOAD

SDA SDALOAD

RPG II RPGLOAD

COBOL COBLOAD

BASIC BASLOAD

FORTRAN FORTLOAD

Assembler ASMLOAD

DisplayWrite/36 TEXTLOADRESTFLDR #PRFFLDR

Personal Service/36 OFCLOAD

Document Library Services DLSLOAD

PROFS Bridge PROFLOAD

Query/36 QRYLOAD

Object Distribution Facility ODFLOAD

Transition Aid TNLOAD

Online Information for:Object Distribution FacilityDisplayWrite/36

Personal Services/36

Document Library ServicesQuery/36IDDU

DSUShared Folders

RESTFLDRRESTFLDRRESTFLDRRESTFLDRRESTORERESTLIBRRESTFLDRRESTFLDRRESTFLDRRESTFLDRRESTFLDRRESTFLDRRESTORERESTORERESTORERESTFLDRRESTFLDR

#OFCFLDR 1

#WPFLDR 2

WPDOCS#OFCFLDR 1

$OUDRSMP#DQRYSMP#DIRSMP#DLSFLDR#QRYFLDR#IDDFLDR#IDDUSMP#USERDCTCUSTCDTNAMEADDRNAMEPHON#DSUFLDR#WPFLDR 2

25-30 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 237: Iseries

Saving and Restoring SSP

Figure 25-2 (Page 2 of 3). Licensed Program Product Restore Procedures

Programming Support to beSaved

Procedure Name File, Folderor Library Nameor Dictionary ID

DisplayWrite/36Language Dictionaries:EnglishFrenchFrench-CanadianSpanishItalianDanishGermanSwedishNorwegianDutchIcelandicPortuguese

DICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOADDICTLOAD

ENGLISHFRENCHFRENCHCASPANISHITALIANDANISHGERMANSWEDISHNORWEGIANDUTCHICELANDICPORTUGUESE

Development Support Utility DSULOAD

Business Graphics Utility/36 BGULOAD

PC Support/36, including:Shared FoldersPC Support/36 OrganizerPC Support/36 Pass-Thru

IWLOAD 3 and 4

PC Support/36 IBM Token-Ring Network Support

LRTRLOAD

PC Support/36 Work StationFeature

WSFLOAD

Multinational Character Set 5

ConversionMCSTLOAD

Software Distribution Support SWDLOAD

LAN Communications Support LANLOAD

Character Generator Utility 5 CGULOAD

IGC Sort 5 SRTXLOAD

Support for Printing/ReadingOnline Information

DOCPLOAD

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-31

Page 238: Iseries

Saving and Restoring SSP

Figure 25-2 (Page 3 of 3). Licensed Program Product Restore Procedures

Programming Support to beSaved

Procedure Name File, Folderor Library Nameor Dictionary ID

3278 Device Emulation viaIBM Personal Computer

RESTORE #EPPCLD1 4

Table notes:

1 #OFCFLDR is used by both Personal Services/36 and Object Distribution Facility. If youhave both functions on your AS/400 Advanced 36 machine, it is only necessary to restorethe folder once.

2 #WPFLDR is used by both DisplayWrite/36 and Shared Folders. If you have both func-tions on your AS/400 Advanced 36 machine, it is only necessary to restore the folder once.

3 The Shared Folders procedure (SHRFLOAD), the PC Support/36 Organizer procedure(PCOLOAD) and the PC Support/36 Pass-Thru procedure (IWPTLOAD) are included in thebase PC Support/36 procedure IWLOAD.

4 The virtual disk #EPPCLD1 is not a part of PC Support/36. The virtual disk #EPPCLD1must be restored prior to restoring PC Support/36. The virtual disk is then activated whenthe IWLOAD procedure is run.

5 This programming support would only be supported on the Ideographic version of the SSP.

Restoring the Other SSP System FilesThis section describes the steps that must be followed to restore any of the fol-lowing saved SSP system files:

� Password security file� Resource security file� Network Resource Directory� Extended character set files� SSP configuration members

Before You Begin...

1. Insert the tape cartridge you used during the save of the other SSP systemfiles in the tape drive.

2. The session library must be set to #LIBRARY to use the procedures in thissection. Use the SLIB procedure to accomplish this.

a. On the command line at the SSP system console type

SLIB ð

b. Press Enter .

The ways to restore other saved SSP system files are:

1. Interactively

You key each restore procedure on the command line at the SSP systemconsole. Restoring the other SSP system files this way is very time consumingand the tape LEAVE option does not work properly. The advantage torestoring this way is that no previous preparation is required.

2. Using a previously created procedure.

25-32 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 239: Iseries

Saving and Restoring SSP

This previously created procedure contains all the procedures you would havekeyed in if you were to restore the other SSP system files interactively.Restoring the other SSP system files this way is less time consuming and thetape LEAVE option works properly. The disadvantage to restoring this way isthat some previous preparation is required.

Restoring the Other SSP System Files InteractivelyTo restore the other SSP system files interactively, do as follows:

1. If you want to restore the password security file to your AS/400 Advanced 36machine:

a. On the command line at the SSP system console, type

SECREST USERID

b. Press the Help key.

The help display for the SECREST procedure appears.

c. In the Name of file to restore field, type the name of the tape file where yousaved the password security file.

d. In the Location of file field, type

TC

e. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theSECREST procedure. The default values will work.

f. Press Enter .

The password security file is restored from tape.

2. If you want to restore the resource security file to your AS/400 Advanced 36machine:

a. On the command line at the SSP system console, type

SECREST RESOURCE

b. Press the Help key.

The help display for the SECREST procedure appears.

c. In the Name of file to restore field, type the name of the tape file where yousaved the resource security file.

d. In the Location of file field, type

TC

e. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theSECREST procedure. The default values will work.

f. Press Enter .

The resource security file is restored from tape.

3. If you want to restore the Network Resource Directory (NRD) to your AS/400Advanced 36 machine:

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-33

Page 240: Iseries

Saving and Restoring SSP

a. On the command line at the SSP system console, type

RESTNRD

b. Press the Help key.

The help display for the RESTNRD procedure appears.

c. In the Name of directory to be restored field, type

#NRD.FLE

d. In the Location of directory field, type

TC

e. Press Enter .

A second help display appears.

Note: No values need to be specified for the other parameters on theRESTNRD procedure. The default values will work.

f. Press Enter .

The network resource directory is restored from tape.

4. If you have an Ideographic version of the SSP and you want to restore theextended character set file #EXT1818:

a. On the command line at the SSP system console, type

RESTEXTN

b. Press the Help key.

The help display for the RESTEXTN procedure appears.

c. In the Name of file to be restored field, type the name of the tape file whereyou saved the #EXT1818 file.

d. In the Name of the extended character file prompt, type

#EXT1818

Note: No values need to be specified for the other parameters on theRESTEXTN procedure. The default values will work.

e. Press Enter .

The extended character set file #EXT1818 is restored from tape.

5. If you have an Ideographic version of the SSP and you want to restore theextended character set file #EXT2424:

a. On the command line at the SSP system console, type

RESTEXTN

b. Press the Help key.

The help display for the RESTEXTN procedure appears.

c. In the Name of file to be restored prompt, type the name of the tape filewhere you saved the #EXT2424 file.

d. In the Name of the extended character file field, type

#EXT2424

Note: No values need to be specified for the other parameters on theRESTEXTN procedure. The default values will work.

25-34 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 241: Iseries

Saving and Restoring SSP

e. Press Enter .

The extended character set file #EXT2424 is restored from tape.

6. If you want to restore the SSP configuration members on your AS/400Advanced 36 machine:

a. On the command line at the SSP system console, type

RESTLIBR

b. Press the Help key.

The help display for the RESTLIBR procedure appears.

c. In the Name of library to be restored field, type the library name that con-tained the SSP configuration members when the save was done.

Normally, these members are stored in a library named #CNFGLIB.

d. In the Location of file field, type

TC

Note: No values need to be specified for the other parameters on theRESTLIBR procedure. The default values will work.

e. Press Enter .

The library containing your configuration members is restored from tape.

Creating a Procedure to Restore the Other Saved SSP SystemFilesNote: The procedure you are creating will perform more efficiently if the order that

the products are restored is the same as the order that the products weresaved to tape. This efficiency is achieved because the tape does not needrewinding between restores. The procedure will work correctly even if theorder is the same.

To create a procedure to restore the other saved SSP system files such as pass-word security file and resource security file:

1. Do one of the following:

� Method 1

a. Use the print option P of the LIBR function to print a copy of the proce-dure you created to save the licensed program products. You can usethe printed copy as a reminder of the order the products are saved.

b. Complete the other steps in this section as they are written.

� Method 2

a. Use the copy option Y of the LIBR function to create a copy of the pro-cedure you created to save the licensed program products.

Note: Be sure you rename the procedure while you are making thecopy.

b. Instead of adding the statements indicated in the other steps in thistopic, replace the save statements with the restore statements.

2. Use DSU, FSEDIT or SEU to edit a new procedure library member. The nameof the procedure and the library you put it in is your choice. You might choose

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-35

Page 242: Iseries

Saving and Restoring SSP

RESTOSF in #LIBRARY. For more information on creating a procedure, see“Making Procedures” in the S/36 System Reference book, SC21-9020.

3. If you have not created the procedure, follow the steps described in section“Creating a Procedure to Restore Licensed Program Products” on page 25-27and then return here.

4. If you want to restore the password security file to your AS/400 Advanced 36machine, add the following to the new procedure:

SECREST USERID,file name,,,TC,,,,LEAVE

where file name is the name of the tape file where the password security filewas saved.

Note: On the SECREST procedure there are parameters that were not speci-fied (the null parameters ',,'). The default values are used for theseparameters.

5. If you want to restore the resource security file to your AS/400 Advanced 36machine, add the following to the new procedure:

SECREST RESOURCE,file name,,,TC,,,,LEAVE

where file name is the name of the tape file where the resource security filewas saved.

Note: On the SECREST procedure there are parameters that were not speci-fied (the null parameters ',,'). The default values are used for theseparameters.

6. If you want to restore the Network Resource Directory to your AS/400Advanced 36 machine, add the following to the new procedure:

RESTNRD #NRD.FLE,TC,,,LEAVE

Note: On the RESTNRD procedure there are parameters that were not speci-fied (the null parameters ',,'). The default values are used for theseparameters.

7. If you want to restore the extended character set file #EXT1818 to your AS/400Advanced 36 machine, add the following to the new procedure:

RESTEXTN file name,,#EXT1818,TC,,,,,LEAVE

where file name is the name of the tape file where the #EXT1818 extendedcharacter set file was saved.

Note: On the RESTEXTN procedure there are parameters that were not spec-ified (the null parameters ',,'). The default values are used for theseparameters.

8. If you want to restore the extended character set file #EXT2424 to your AS/400Advanced 36 machine, add the following to the new procedure:

RESTEXTN file name,,#EXT2424,TC,,,,,LEAVE

where file name is the name of the tape file where the #EXT2424 extendedcharacter set file was saved.

Note: On the RESTEXTN procedure there are parameters that were not spec-ified (the null parameters ',,'). The default values are used for theseparameters.

9. If you want to restore the SSP configuration members to your AS/400Advanced 36 machine, add the following to the new procedure:

25-36 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 243: Iseries

Saving and Restoring SSP

RESTLIBR library name,,,,,,TC,LEAVE

where file name is the name of the library that contained the SSP configura-tion members when they were saved.

Normally, these members are stored in a library named #CNFGLIB.

Note: On the RESTLIBR procedure there are parameters that were not speci-fied (the null parameters ',,'). The default values are used for theseparameters.

10. After all the procedures used to restore the other SSP system files are addedto the new procedure, end the edit session and replace the procedure memberin the library.

Restoring the Other SSP System Files from a Previously CreatedProcedureTo restore the other SSP system files using a procedure you created previously:

1. If you have not created the procedure, follow the steps described in section“Creating a Procedure to Restore the Other Saved SSP System Files” onpage 25-35 and then return here.

2. Set the session library to the library that contains the procedure you created torestore the other SSP system files.

a. On the command line at the SSP system console, type

SLIB library name

where library name is the name of the library that contains the procedureyou created to restore the other SSP system files.

b. Press Enter .

3. On the command line at the SSP system console, type the name of the proce-dure you created to restore the other SSP system files.

4. Press Enter .

5. When the command entry display appears again, the procedure has ended andyou have completed the task of restoring the other SSP system files.

6. Remove the tape cartridge from the tape drive and return it to its protectivecontainer.

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-37

Page 244: Iseries

Saving and Restoring SSP

25-38 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 245: Iseries

SSP PTFs

Chapter 26. Working with SSP Program Temporary Fixes

An SSP program temporary fix (PTF) is a solution to a problem or a potentialproblem that exists in the:

� SSP operating system (SSP)

� SSP features (For example: POP, VASP, and Transition Aid)

� Licensed program products (LPPs)

� Program Request for Price Quotation (PRPQ)

SSP PTFs could also fix problems that appear to be hardware failures or providenew functions.

SSP PTFs are designed to replace the failing load module(s) or procedure(s) in aproduct library. Generally, the failing load modules or procedures are incorporatedinto a future release of the system.

The program maintenance strategy discussed in this chapter applies to the IBMAS/400 system service and delivery, specifically the AS/400 Advanced 36 system.

AS/400 Advanced 36 Program Maintenance StrategyThe AS/400 program maintenance strategy consists of preventative service andcorrective service.

Preventative ServicePreventative service helps you avoid problems that have been found and fixedsince the start of the current release. Cumulative PTF Packages are used toperform preventative service.

Cumulative PTF Packages| The cumulative PTF contains PTFs for:

| � Licensed Internal Code (LIC)

| � OS/400 operating system

| � OS/400 licensed programs

| � SSP operating system

| � SSP licensed program products

| The cumulative PTF package is given a name with the following format:

| CYJJJVRM

| where:

| C Indicates cumulative PTF package

| Y Is the last digit of the year in which the package was released

| JJJ Is the Julian date the package was released

Copyright IBM Corp. 1995, 1996 26-1

Page 246: Iseries

SSP PTFs

| VRM Is the version, release and modification level of the software running on| the system.

| An example of a cumulative PTF package name is C611537ð. The cumulative PTF| package was released April 15, 1996 for software at version 3, release 7 and mod-| ification 0.

| The Cumulative PTF package is created so OS/400 can load and apply the PTFs| for:

| � The Licensed Internal code

| � The OS/400 operating system

| � The OS/400 licensed programs

| and the SSP can copy and apply PTFs for:

| � The SSP operating system

| � The SSP licensed program products

| Cumulative PTF packages contain all PTFs from the previous Cumulative PTF| package plus any new preventative PTFs. A corrective PTF becomes a preventa-| tive PTF after it has gone through extensive testing and after it does not require| any special instructions or handling. Cumulative PTFs can be ordered electron-| ically or by telephone. Cumulative PTF packages are sent to you by mail on a| CD-ROM. If your service representative is not from IBM, you might receive your| cumulative PTF package on a tape cartridge.

Corrective ServiceCorrective service corrects problems reported to IBM service support. If you havea problem with the SSP, SSP features or LPPs, you use the System ProblemDetermination–SSP book, SC21-8296, to help isolate the problem. This book mightdirect you to contact your service representative for assistance. If there is aproblem with the IBM supplied software, a PTF is made available to fix theproblem.

Corrective Service SSP PTFsThere are three types of PTFs for corrective service:

� Test PTFs

Development cannot adequately test the PTF, so the customer is asked to helptest the PTF.

� Traps PTFs

Development cannot recreate the reported problem. They need additionalinformation to solve the problem. A trap is developed to get that additionalinformation and is supplied as a PTF.

� Corrective PTFs (sometimes called Patches)

These PTFs fix a specific problem reported by a customer.

Corrective service SSP PTFs could be sent to you in the following ways:

� On a corrective cumulative PTF package on a CD-ROM sent by IBM.

26-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 247: Iseries

SSP PTFs

� On a corrective cumulative PTF package on a tape cartridge sent to you byyour service representative.

� Electronically using Electronic Customer Support.

An electronically sent SSP PTF is sent to the OS/400 operating system usingElectronic Customer Support. For more information on Electronic CustomerSupport see Appendix D, “Using Electronic Customer Support.”

Ordering SSP PTFs and PTF InformationPreventative cumulative PTF packages or Corrective PTFs can be ordered by:

� Contacting your service provider and asking for the latest AS/400 Advanced 36Cumulative PTF package.

� Using the OS/400 Send PTF Order (SNDPTFORD) command and ElectronicCustomer Support. For information on using SNDPTFORD and Electronic Cus-tomer Support, see Appendix D, “Using Electronic Customer Support.”

Displaying or Printing Cumulative PTF InformationYou can choose to either display or print information about IBM-supplied PTFs. Todo so, perform the following steps:

1. Select a PTF media device that contains the IBM-supplied PTFs.

The PTFs could be on 1/4-inch tape or on CD-ROM. The PTF procedure readsonly from the tape cartridge (TC) device. If the PTF media is 1/4-inch tape,continue with step 2.

If the media that contains the IBM-supplied PTFs is on CD-ROM, you mustremap the device TC to be the CD-ROM drive. For directions, see “Mappingthe TC Device ID to the CD-ROM Drive” on page 26-16.

2. Remove the PTF media from its protective container and insert it into theappropriate drive.

Note: For information on using different kinds of media from your AS/400Advanced 36 machine, see Chapter 7 of the Operating YourComputer–SSP Operating System book, SC21-8297. For informationon using different kinds of media from OS/400, see Chapter 4 of theSystem Startup and Problem Handling book, SC41-4206.

3. Type PTF NEWS,RESTORE on the entry line.

4. Press Enter .

The PTFNEWS library is restored to the disk.

5. Type PTF NEWS on the entry line.

6. Press the Help key.

Chapter 26. Working with SSP Program Temporary Fixes 26-3

Page 248: Iseries

SSP PTFs

à@ ð PTF PROCEDURE

Applies PTFs (program temporary fixes) and patches toIBM-supplied and user programs that are found to bein error, or provides information about IBM-supplied

PTFs.

Function to be performed . . . . . . APPLY,COPY,DELETE,DIRECT, LIST,PATCH,REMOVE,RESTORE,SAVE,MAPPLY,MCOPY,MREMOVE,NEWS NEWS___

PTF news function to be performed . . . . . . . . . . . . . . . ALL,BULLETIN,DELETE,PTFINDEX,PTFXREF,RESTORE,newsletter name ALL_____

7. Type one of the following in the PTF news function to be performed field.

a. Type ALL to receive:

� All of the newsletters in the PTFNEWS library� A list of cross-referenced PTFs� A PTF index

b. Type BULLETIN to select the printing or displaying of the PTFNEWSlibrary.

8. Press Enter .

à@ ð PTF PROCEDURE

Applies PTFs (program temporary fixes) and patches toIBM-supplied and user programs that are found to bein error, or provides information about IBM-supplied

PTFs.

Function to be performed . . . . . . APPLY,COPY,DELETE,DIRECT, LIST,PATCH,REMOVE,RESTORE,SAVE,MAPPLY,MCOPY,MREMOVE,NEWS NEWS___

PTF news function to be performed . . . . . . . . . . . . . . . ALL,BULLETIN,DELETE,PTFINDEX,PTFXREF,RESTORE,newsletter name ALL_____

Type of output . . . . . . . . . . . . . . . . . DISPLAY,PRINT DISPLAY

9. In the Type of output field, type

PRINT

to have the PTF information printed.

Or,

DISPLAY

to have the PTF information shown on your display.

10. Press Enter .

Depending on your selection, information similar to the following is shown orprinted:

26-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 249: Iseries

SSP PTFs

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ RELEASE 7.5 PTF BULLETIN FILE\\ THE PTF BULLETIN FILE CONTAINS IMPORTANT "READ-ME-FIRST" DATA.\ THE "ABSTRACT" ALLOWS YOU TO DETERMINE WHETHER OR NOT THE DATA\ IS APPROPRIATE TO YOUR SYSTEM USAGE. "ADDITIONAL INFORMATION"\ PROVIDES MORE DETAIL ON THE "READ-ME-FIRST" DATA WHENEVER IT\ IS NECESSARY.\\ CURRENT PTF LEVEL: LAST BULLETIN UPDATE:\\ TAPE MEDIA IN xxxxxxxx PREVENTATIVE PTF PACKAGE:\ SYSTEM UNIT: 94ð2 ONE QIC525 1/4 INCH TAPE CARTRIDGE\\ TAPE MEDIA IN xxxxxxxx CORRECTIVE PTF PACKAGE:\ SYSTEM UNIT: 94ð2 ONE QIC525 1/4 INCH TAPE CARTRIDGE

Look through the information for descriptions of what the PTFs in the packageare fixing.

11. If you changed the device mapping of the TC device to be the CD-ROM device,and you are not going to use the CD-ROM drive in later steps, you mustchange it back to the tape cartridge tape drive.

To change it back, follow the directions in “Changing the TC Device ID Back toa Tape Cartridge Drive” on page 26-17 and then return here.

Installing Cumulative SSP PTF PackagesThe installation of a cumulative SSP PTF package is a two-step process:

1. Copying SSP preventative PTFs from the PTF media to the system

2. Applying SSP preventative PTFs

For detailed information on installing Cumulative SSP PTF packages use the PTFShipping Information Letter that comes with the Cumulative PTF package.

Note: It is important to remember, the SSP PTF procedure only installs PTFs froma device that has a device ID of TC.

If you received a cumulative PTF package on CD-ROM, you must map the devicethat has an ID of TC to be the CD-ROM drive. Before you copy the PTFs, followthe steps in “Mapping the TC Device ID to the CD-ROM Drive” on page 26-16.

Corrective SSP PTFs (Patches)

Installing Corrective SSP PTFs from CD-ROM or TapeBefore you begin...

Prior to installing your corrective SSP PTF, review the PTF Shipping InformationLetter that came with the corrective PTF. There might be special instructionsyou must do when installing the PTF.

Chapter 26. Working with SSP Program Temporary Fixes 26-5

Page 250: Iseries

SSP PTFs

You use the AUTOPTCH procedure to install corrective SSP PTFs (patches) fromCD-ROM and tape. To install corrective SSP PTFs, do as follows:

1. If the corrective PTF is on a tape cartridge, go to step 3.

2. If the corrective PTF is on CD-ROM, you must map the device TC to be theCD-ROM drive. To do this, follow the steps in “Mapping the TC Device ID tothe CD-ROM Drive” on page 26-16.

3. Insert the media that contains the corrective PTF into the appropriate drive.

Note: For information on using different kinds of media from your AS/400Advanced 36 machine, see Chapter 7 of the Operating YourComputer–SSP Operating System book, SC21-8297. For informationon using different kinds of media from OS/400, see Chapter 4 of theSystem Startup and Problem Handling book, SC41-4206.

4. From the console for the AS/400 Advanced 36 machine, put the AS/400Advanced 36 machine in a dedicated state. To do this, follow the directions in“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.After this is done, return here.

If you completed this step, the AS/400 Advanced 36 machine is in a dedicatedstate.

5. On the AS/400 Advanced 36 machine console, type

AUTOPTCH APPLY,patchid,TC

Where:

APPLY Specifies you wish to apply (install) a corrective PTF.

patchid Is the patch ID of the SSP corrective PTF. The patch ID isalways 8 characters long. The first 2 characters are TF, PT orDT. The third character is the version of the patch (For example,A, B, or C) The remaining 5 characters are the last 5 digits of theAPAR that reported the problem this corrective PTF is going to fix.

TC Specifies the corrective PTF is to be installed from a tape car-tridge or a CD-ROM that was mapped to TC.

6. Press Enter .

A message

AUTOPTCH procedure is running.

is shown at the bottom of the display. The corrective PTF is installed.

7. If you changed the device mapping of the TC device to be the CD device, youshould change it back at this time. To do so, follow the directions in “Changingthe TC Device ID Back to a Tape Cartridge Drive” on page 26-17.

8. On the AS/400 Advanced 36 machine console, type

START SYSTEM

9. Press Enter .

The AS/400 Advanced 36 machine is no longer dedicated.

26-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 251: Iseries

SSP PTFs

| Installing Corrective SSP PTFs That Were Sent Electronically| If you have previously installed an electronically sent PTF, go to “Electronic Installa-| tion Checklist” on page 26-9.

| Getting Electronic Customer Support Up and Running| If you want to receive SSP PTFs electronically, you need to install the software and| hardware indicated in the Fastpath Installation of Your Advanced 36 book,| SA41-4138.

| Getting ILAN Up and Running| In order to install an electronically sent SSP PTF, ILAN must be running on your| system. ILAN communications allow you to send the PTF from OS/400 to the| AS/400 Advanced 36 machine. If you have not set up ILAN, follow the directions in| Chapter 4 of the Getting SSP and OS/400 Installed and Running book, SC21-8377.| Then, start the ILAN as directed in Chapter 29, “System-to-System Communica-| tions - ILAN Communications”

| Using DDM for PTFs Sent Electronically from the OS/400| operating system to the SSP operating system| In order for DDM to do this copy, the Network Resource Directory (NRD) must be| defined and an entry must be put in the NRD for the electronically sent PTF.

| The NRD:

| � Contains information about each remote file that can be accessed using DDM

| � Reflects the DDM network as seen from the AS/400 Advanced 36 machine's| viewpoint

| � Identifies the remote files that can be accessed by the AS/400 Advanced 36| machine

| � Identifies the remote system where the files are located.

| If you have not previously installed an electronically sent PTF, you need the Local| control point name of the AS/400 system. If you do not know the name, do the| following:

| 1. On an OS/400 command line, type

DSPNETA

2. Press Enter .

3. Find the line titled Local control point name. This is the name of the AS/400system in a Network.

4. Make note of the name.

5. Press Cmd3 (Exit) to return to a command line.

Because you have not previously installed an electronically sent PTF, you need todefine an entry in the Network Resource Directory. To define that entry, do asfollows:

| 1. On a command line on the AS/400 Advanced 36 machine console, type

EDITNRD

2. Press Enter .

Chapter 26. Working with SSP Program Temporary Fixes 26-7

Page 252: Iseries

SSP PTFs

If the NRD already exists, the NETWORK RESOURCE DIRECTORY editdisplay is shown. If this display is shown, go to step 5 on page 26-8.

If the NRD does not already exist, the NETWORK RESOURCE DIRECTORYcreate a new directory display is shown.

The NRD must be created.

à@ ðNETWORK RESOURCE DIRECTORY Optional-\

Creates a new Directory

Number of entries . . . . . . . . . . . . . . . . . 1-9999 ____

3. In the Number of entries field, type the number of remote files you plan toaccess.

Note: If you are only going to use the DDM for electronically sent PTFs, 40entries is large enough.

4. Press Enter .

The NETWORK RESOURCE DIRECTORY edit display is shown.

à@ ðNETWORK RESOURCE DIRECTORY

Edits entries in the directory

Scan for local label . . . . . . . . . . . . . . . . . . . ________

---------------------------------------------------------------------------

LOCAL REMOTE REMOTE LABEL LOCATION LABEL

________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________________ ________ _______________________________________________

Cmd4-Delete Cmd6-Print Cmd7-End Cmd8-Reset Cmd1ð-Add Roll keys-Page

á ñ5. Under the LOCAL LABEL heading, type

LOCPTFFL.

6. Under the REMOTE LOCATION heading, type the OS/400 local control pointname used when you set up ILAN communications.

7. Under the REMOTE LABEL heading, type

RMTPTFFL.

Note: This name is changed when your first electronically sent PTF arrives.

8. Press Enter .

26-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 253: Iseries

SSP PTFs

9. Press Cmd7 to end the edit session.

Other messages, such as COPYDATA is running, may roll up from the bottom ofthe display. These are normal and should be ignored.

Electronic Installation ChecklistDuring the actual install of the PTF, you need the following:

� ILAN Subsystem Configuration Member name.

The default subsystem shipped with the AS/400 Advanced 36 machine wasILANSBS. This was also the recommended name for any additional AS/400Advanced 36 machines you installed.

� The name of the library the ILAN Subsystem Configuration Member is stored in.

The default subsystem shipped with the AS/400 Advanced 36 machine is in#CNFGLIB. It was recommended that the subsystems for any additional AS/400Advanced 36 machines be placed in that library also.

� The name of the save file that contains the corrective SSP PTF.

This name must be in the following format:

QU57mnnn

where m is the modification level of release 7 (for example, 5 for Release 7.5)and nnn is the last three digits of the SSP PTF.

� The patch ID of the SSP corrective PTF.

The patch ID is always 8 character long. The first 2 characters are TF, PT orDT. The third character is the version of the patch (for example, A, B, or C).The last 5 characters are the last 5 digits of the APAR that reported theproblem this corrective PTF is going to fix.

� A tape cartridge with a volume ID of AUTOPT.

You use this tape cartridge to save the library that contains the corrective PTF.

Installing SSP PTFs That Were Sent ElectronicallyThe SSP PTF is sent to your OS/400 operating system as a save file (SAVF). Acover letter for the corrective PTF is also sent to your OS/400 operating system.

Before you begin...

Prior to installing the electronically sent PTF, you must review this cover letter.There may be special instructions you must do when installing the PTF.Instructions for displaying a cover letter are in the System Startup and ProblemHandling book, SC41-4206.

1. Make sure you have everything in the “Electronic Installation Checklist” onpage 26-9 and that you have read the cover letter for special instructions.

2. From the console for the AS/400 Advanced 36 machine, put the AS/400Advanced 36 machine in a dedicated state. To do this, follow the directions in“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.After this is done, return here.

Chapter 26. Working with SSP Program Temporary Fixes 26-9

Page 254: Iseries

SSP PTFs

If you completed this step, the AS/400 Advanced 36 machine is in a dedicatedstate. You need to start ILAN communications again on the dedicated AS/400Advanced 36 machine.

3. Start ILAN communications as follows:

a. On a command line on the AS/400 Advanced 36 machine console, type

ENABLE

b. Press the Help key.

c. In the Subsystem configuration name field, type the name of the ILAN Sub-system Configuration Member name. If you do not know the name, see the“Electronic Installation Checklist” on page 26-9.

d. In the Name of library field, type the name of the library that contains theILAN Subsystem Configuration Member. If you do not know the name, seethe list in “Electronic Installation Checklist” on page 26-9.

e. In the Line number field, type

15

This is the line number that is always used for ILAN communications.

f. Press Enter .

ILAN communications should now be started on the dedicated system.

4. Verify that the ILAN subsystem is enabled by following the directions in “ILANCommunications Verification” on page 29-10. If the ILAN subsystem is notenabled, see the directions in the System Problem Determination–SSP book,SC21-8296.

5. On a command line on the AS/400 Advanced 36 machine console, type

ECSAPTCH savfname,patchid

Where:

savfname Is the save file name that contains the corrective PTF (patch) thatyou determined earlier.

patchid Is the patch ID of the SSP corrective PTF you determined earlier.

6. Press Enter .

The message ECSAPTCH procedure is running is shown at the bottom of thedisplay.

After a few seconds the following will rollup from the bottom of the display.

When the NETWORK RESOURCE DIRECTORY display comes upfind the LOCAL LABEL - LOCPTFFL. Modify the REMOTELABEL on this entry to be: U57mnnnWhen you are done, press Cmd7 to end the edit.When ready to continue, respond with ð to SYS-3725.

SYS-3725 Options (ð )Pause--when ready, enter ð to continue.

Note: The message identified in the above text might be SYS-3726. If so, itrefers to the Pause message SYS-3725.

7. Write down the number that is in the form U57mnnn.

26-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 255: Iseries

SSP PTFs

8. After you have read the instructions on the display, type

ð

9. Press Enter .

The NETWORK RESOURCE DIRECTORY edit display appears.

10. Find the entry with a LOCAL LABEL of LOCPTFFL. The Roll keys can beused to page forward and backward through the entries.

11. In the REMOTE LABEL field for that entry, type the name that was shownearlier on the display. It was in the form, U57mnnn.

12. Press Enter .

13. Press Cmd7 to end the edit session. COPYDATA is running. These mes-sages are normal and should be ignored.

Eventually, the following message appears:

SYS-6111 Options ( 123 )Dedicated system required for this PTF function...

This message is informing you that the function that is going to install the cor-rective PTF requires that the system be dedicated. If you followed all of thesteps, the system is dedicated except for ILAN communications that wereneeded to get the PTF from the OS/400 operating system.

14. Press the Attention key.

The INQUIRY OPTIONS display appears.

à@ ð INQUIRY OPTIONS Current Interrupted job: W1234567 W1

ð. Resume current interrupted job1. Request Command display2. Cancel job and close files; new data is saved3. Cancel job; new files are lost4. Set inquiry condition for program5. Display session status6. Display messages sent to this display station

7.

Enter number to select option

á ñ15. Type

1

16. Press Enter .

17. On the command line, type

DISABLE

18. Press the Help key.

The DISABLE PROCEDURE help display appears.

19. In the Subsystem configuration name field, type the ILAN Subsystem Config-uration Member name.

If you do not know the name, see the “Electronic Installation Checklist” onpage 26-9.

Chapter 26. Working with SSP Program Temporary Fixes 26-11

Page 256: Iseries

SSP PTFs

20. In the Line number field, type

15

This is the line number that is always used for ILAN communications.

21. Press Enter .

ILAN communications should now be stopped and the system is again in adedicated state.

22. Press Cmd1 (Resume job) to resume the interrupted job. The followingmessage appears:

SYS-6111 Options ( 123 )Dedicated system required for this PTF function...

23. Type

1

24. Press Enter .

The corrective PTF continues to install.

25. The following message will prompt you to save the PTF to tape:

Insert a tape in the tape cartridge drive on whichyou want to backup the corrective PTF. The volume IDmust be AUTOPT.When ready to continue, respond with ð to SYS-3725.

SYS-3725 Options (ð )Pause--when ready, enter ð to continue.

26. Insert a tape that was initialized with a volume ID of AUTOPT.

Once saved, you can use the tape if you ever need to install this PTF again oryou can use the tape to install this PTF on another AS/400 Advanced 36machine.

Note: The message identified in the above text might be SYS-3726. If so, itrefers to the Pause message SYS-3725.

27. If you do not have a tape cartridge with a volume ID of AUTOPT, do asfollows:

a. Press the Attention key.

The INQUIRY OPTIONS display appears.

b. Type

1

c. Press Enter .

An INQUIRY command display is shown.

d. On the command line, type

TAPEINIT TC,SL,AUTOPT,CLEAR,,NOERASE,REWIND

e. Press Enter .

The tape is initialized. When the initialization is complete, the INQUIRYcommand display appears again.

f. Press Cmd1 (Resume job) to resume the interrupted job.

26-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 257: Iseries

SSP PTFs

28. Type

ð

29. Press Enter .

The library that contains the corrective PTF is saved to tape. When thecommand entry display appears, the electronically sent PTF has been installedand saved to tape. The save file that was sent to OS/400 and the LIBRFILEthat was in the save file have been deleted.

30. Remove the tape with the saved corrective PTF from the tape drive.

31. Put the tape in the protective case and store it in a safe place for use the nexttime you need it.

This completes the process of installing a corrective PTF.

32. To remove system dedication, on the AS/400 Advanced 36 machine console,type

START SYSTEM

33. Press Enter .

Installing a Saved PTF That Was Sent ElectronicallyIf you want to apply this PTF on another AS/400 Advanced 36 machine, you willneed to use the tape you saved this PTF to. You do this by following the directionsin this topic.

When you installed the electronically sent PTF, the library that contains the PTFwas saved to tape. The volume ID of this tape is AUTOPT.

During the actual install of the saved corrective PTF, you need the following:

� The patch ID of the SSP corrective PTF.

The patch ID is always 8 character long. The first 2 characters will be TF, PTor DT. The third character is the version of the patch (A, B, or C). The last 5characters are the last 5 digits of the APAR that reported the problem this cor-rective PTF is going to fix.

� The tape cartridge with a volume ID of AUTOPT.

This tape contains the save libraries for the electronically sent corrective PTF.

To install this PTF on your AS/400 Advanced 36 machine, do as follows:

1. From the console for the AS/400 Advanced 36 machine, put the AS/400Advanced 36 machine in a dedicated state. To do this, follow the directions in“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.After this is done, return here.

If you completed this step, the AS/400 Advanced 36 machine is in a dedicatedstate.

2. On the command line of the AS/400 Advanced 36 machine, type

RESTLIBR patchid,,,,,,TC

where patchid is the patch ID of the corrective PTF you determined earlier.

3. Press Enter .

4. When the command display is shown, type

Chapter 26. Working with SSP Program Temporary Fixes 26-13

Page 258: Iseries

SSP PTFs

AUTOPTCH APPLY,patchid,F1

where patchid is the patch ID of the corrective PTF you determined earlier.

5. Press Enter .

6. When the command display is shown, type

DELETE patchid,F1,,,LIBR

where patchid is the patch ID of the corrective PTF you determined earlier.

7. Press Enter .

When the command display is shown, the installation of the corrective PTF iscomplete. This completes the process of installing a saved electronically sentPTF.

8. To remove system dedication, on a command line on the AS/400 Advanced 36machine, type

START SYSTEM

9. Press Enter .

Displaying or Printing Corrective SSP PTF InformationAfter the corrective PTF is installed, you should review the information sent with thePTF. During the install process, a PTF backup library was created. In this libraryis a source member called README. This member contains any special informa-tion about the corrective PTF. The name of the backup library is #Bmnnnnn, wherem is the version of the corrective PTF (for example, A, B or C) and nnnnn is thelast 5 digits of the APAR that reported the problem this corrective PTF is going tofix.

| On either the AUTOPTCH or ECSAPTCH procedure you used to install the correc-tive PTF, the second parameter was the patch ID. It was in the format TFmnnnnn,DTmnnnnn or PTmnnnnn, where m and nnnnn are the same as in the backuplibrary name.

To display or print the corrective PTF information, you must display or print thesource member named README in the corrective PTF backup library #Bmnnnn.This can be done in the following ways:

� Using the LISTLIBR procedure.

1. On the AS/400 Advanced 36 machine command line, type

LISTLIBR README,SOURCE,#Bmnnnnn,,,,MEMBERS

where #Bmnnnnn is the name of the PTF back up library that was discussedearlier in this topic.

2. Press Enter .

This LISTLIBR procedure lists the contents of the source member README inlibrary #Bmnnnnn on the current system list device. If the system list device isCRT, the member is shown on your display. If the system list device is a printer,a spool file is created with the contents of the member. The spool file can thenbe printed or you can browse it using the WRKSPL procedure.

� Using the LIBR function of the Programmer and Operator Productivity Aid(POP):

1. On a command line on the AS/400 Advanced 36 machine, type

26-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 259: Iseries

SSP PTFs

LIBR #Bmnnnnn

where #Bmnnnnn is the name of the PTF back up library that was discussedearlier in this topic.

2. Press Enter .

This LIBR procedure shows you the members in the library #Bmnnnnn. You canuse the B (Browse) or P (Print) options to display or print the READMEmember.

Removing Corrective SSP PTFsYou use the AUTOPTCH procedure to remove corrective PTFs (patches) from theAS/400 Advanced 36 machine.

Note: You can only remove corrective PTFs if the PTF backup library is still be onthe system. If the PTF backup library is not on the system, it must berestored before you try to remove a corrective PTF.

To remove a corrective PTF:

1. From the console for the AS/400 Advanced 36 machine, put the AS/400Advanced 36 machine in a dedicated state. To do this, follow the directions in“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.After this is done, return here.

If you completed this step, the AS/400 Advanced 36 machine is in a dedicatedstate.

2. On the AS/400 Advanced 36 machine command line, type

AUTOPTCH REMOVE,patchid

Where:

REMOVE Specifies you wish to remove a corrective PTF.

patchid Is the patch ID of the SSP corrective PTF. The patch ID isalways 8 characters long. The first 2 characters will be TF, PT orDT. The second character is the version of the patch (forexample, A, B, or C). The last 5 characters are the last 5 digits ofthe APAR that reported the problem this corrective PTF is goingto fix.

3. Press Enter .

A message

AUTOPTCH procedure is running.

is shown at the bottom of the display. When the command display appears,the corrective PTF has been removed. The only thing left to do is remove thesystem dedication.

4. To remove system dedication:

a. On a command line on the AS/400 Advanced 36 machine console, type

START SYSTEM

b. Press Enter .

Chapter 26. Working with SSP Program Temporary Fixes 26-15

Page 260: Iseries

SSP PTFs

Mapping the TC Device ID to the CD-ROM DriveTo remap the device that has an ID of TC to be the CD-ROM drive:

1. On the command line of the AS/400 Advanced 36 machine console, type

SYSLIST CRT

2. Press Enter .

This changes the system list device to the display. This specifies that thesystem list output is to be shown at your display station.

3. On the command line of the AS/400 Advanced 36 machine console, type

DSPSYSVL

4. Press Enter .

The SSP SYSTEM VALUES start to roll up on your display.

5. Find the system value that starts DEVMAP TC.

Note: If it is not on the first display, press Enter to see the next display.

To the right of this entry is the OS/400 device name for the tape drive that iscurrently mapped to the SSP device named TC.

6. Make note of the name shown next to DEVICE TC.

You will use this name later to remap TC back to the current OS/400 devicename.

7. On the command line of the AS/400 Advanced 36 machine console, type

CHGSYSVL DEVMAP,TC

8. Press the Help key.

The help display for the CHGSYSVL procedure is shown.

9. In the OS/400 device name field, type

OPTð1

10. Press Enter .

The command line appears if the remapping was successful.

If the remapping was successful, until the AS/400 Advanced 36 machine isIPLed or device TC is remapped again, any reference to device ID TC actuallyrefers to the CD-ROM drive as OPT01.

11. If the remapping was successful, return to the topic that sent you here.

12. If error message

SYS-4725 Invalid parameter 3 in CHGSYSVL procedure

is issued, the remapping failed because OPTð1 is not the device name of theCD-ROM drive. Do as follows:

a. Respond to the message as follows:

1) Type

3

2) Press Enter .

b. Follow the directions in “What to Do if the Mapping Failed.”

26-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 261: Iseries

SSP PTFs

What to Do if the Mapping FailedYou are here because you received an error when you tried to map the device IDTC to the CD-ROM drive. The following steps will help you determine the OS/400device name of the CD-ROM device. Do as follows:

1. On a command line on the OS/400 system console, type

WRKCFGSTS CFGTYPE(\DEV) CFGD(\OPT) ASTLVL(\BASIC)

2. Press Enter .

The Work with Devices display appears.

3. Look in the Type column for 6320. Beside it in the Device column is theOS/400 device name of the CD-ROM drive. This is the name you must usewhen mapping TC to the CD-ROM drive.

4. Make note of the OS/400 device name.

5. Press Cmd3 (Exit) to end the Work with Devices job.

6. Repeat the steps in “Mapping the TC Device ID to the CD-ROM Drive,” startingwith step 7. When you get to step 9, make sure you type the OS/400 devicename you determined.

Changing the TC Device ID Back to a Tape Cartridge DriveAfter the operations that require you to use the CD-ROM drive are complete, theTC device ID should be mapped back to the 1/4-inch tape drive. To change themapping of TC back to the tape cartridge drive:

1. On the command line of the AS/400 Advanced 36 machine console, type

CHGSYSVL DEVMAP,TC

2. Press the Help key.

3. In the OS/400 device name field, type the OS/400 device name you determinedin step 6 on page 26-16.

4. Press Enter .

The TC device ID is now remapped back to the initial OS/400 device name.

5. Return to the step that sent you here.

Chapter 26. Working with SSP Program Temporary Fixes 26-17

Page 262: Iseries

SSP PTFs

26-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 263: Iseries

Remote Workstation Communications

Chapter 27. Establishing a Communications Link for RemoteWorkstations

To use the communications support on your system, you need to establish a com-munications link between your system and another location. The action required, ata display station or the system console, to establish the communications linkdepends upon which communications support you have.

This chapter contains a form for remote work station support (RWS) that your pro-grammer or system manager should fill in so you know the steps to use to establisha communications link with the communications support that is on your system.Forms establishing communications links for other communications support appearin the appropriate communications reference books, with examples of how to fill inthe form with telephone numbers, procedure names, and dial or answer proce-dures.

Steps 1 and 2 in the “Using Remote Work Station Support” topic should be filled inby your programmer or system manager.

The steps you can take to determine the cause of a problem for communicationslines are described in the System Problem Determination–SSP book, SC21-8296.

Using Remote Work Station Support

Establishing the Communications Link1. If you have system operator authority or higher, enter the VARY OFF command

at a display station for each line, cluster controller, or each device that is to bevaried online:

For each line, enter VARY ON,,X where X is the line number.

For each cluster controller, enter VARY ON,CXX where XX is the work stationaddress.

For each device, enter VARY ON,XX where XX is the device ID.

2. You may receive one of the following messages:

a. SYS-34ð1 SDLC (line number) Operator dial is required

This message is displayed because you have an SDLC switched line, andyou must call a remote location. Perform the following steps:

b. SYS-34ðð SDLC (line number) Operator answer is required

This message is displayed because you have an SDLC switched line, andyou must answer a call from a remote location. Perform the followingsteps:

Copyright IBM Corp. 1995, 1996 27-1

Page 264: Iseries

Remote Workstation Communications

c. Other message

See the S/36 System Messages book, SC21-7938, for an explanation ofthe message and the steps that you should follow.

Ending the Communications LinkIf you have system operator authority or higher, enter the VARY OFF command ata display station for each line, cluster controller, or for each device that is to bevaried offline:

� For each device, enter VARY OFF,XX where XX is the device address.

� For each cluster controller, enter VARY OFF,CXX where XX is the cluster con-troller address.

� For each line, enter VARY OFF,,X where X is the line number.

VARY OFF will not be performed if all display stations on the line are not signed offor if the spool writers for remote printers are not stopped.

27-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 265: Iseries

AS/400 System Common Operator Tasks

Chapter 28. Problem Handling . . . . . . . . . . . . . . . . . . . . . . . . . 28-1Hardware Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1

Hardware Problem Message Sent to SSP . . . . . . . . . . . . . . . . . . . 28-1Hardware Problem Message Sent to OS/400 . . . . . . . . . . . . . . . . . 28-1Using the Product Activity Log to Find out about Hardware Problems . . . 28-1Determining Who Owns the Device . . . . . . . . . . . . . . . . . . . . . . . 28-1

| Determining Who Owns a Printer, Display Station or Media Device . . 28-3| Determining the Owner of a Communication Port . . . . . . . . . . . . . 28-4

Determining Which SSP Job Owns a Device . . . . . . . . . . . . . . . . . 28-5| Determining the Owner of a Media Device . . . . . . . . . . . . . . . . . 28-5| Determining the Owner of a Printer or Display Station . . . . . . . . . . 28-6| Determining the Owner of a Communication Line . . . . . . . . . . . . . 28-8

How to Handle OS/400 and SSP Printer Conflicts . . . . . . . . . . . . . . 28-8Using the Work with Configuration Status Command to Determine If

Devices are Varied Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-8Handling AS/400 Advanced 36 Machine Error Codes . . . . . . . . . . . . . . 28-9

Determining What the Error Codes Mean . . . . . . . . . . . . . . . . . . . 28-9

Chapter 29. System-to-System Communications - ILANCommunications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1

Setting up ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . 29-3Understanding Default Startup Settings . . . . . . . . . . . . . . . . . . . . . . 29-3Manually Starting the ILAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3

Manually Starting the OS/400 Side of ILAN . . . . . . . . . . . . . . . . . . 29-3Manually Starting the SSP Side of ILAN (All Connections) . . . . . . . . . 29-4Manually Starting the SSP Side of ILAN (A Single Connection) . . . . . . 29-5

Automatically Starting ILAN Communications . . . . . . . . . . . . . . . . . . . 29-6Automatically Starting ILAN Communications for SSP . . . . . . . . . . . . 29-6Automatically Starting ILAN Communications for OS/400 . . . . . . . . . . 29-6

Disabling Automatic Startup of ILAN . . . . . . . . . . . . . . . . . . . . . . . . 29-7Finding Out the OS/400 Control Point Name . . . . . . . . . . . . . . . . . . . 29-8Stopping ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . . 29-8

Stopping ILAN Communications on the OS/400 Side . . . . . . . . . . . . 29-8Stopping ILAN Communications on the SSP Side (All Connections) . . . . 29-9Stopping ILAN on the SSP Side (Single Connection) . . . . . . . . . . . . 29-9

ILAN Communications Verification . . . . . . . . . . . . . . . . . . . . . . . . 29-10Verification for the First AS/400 Advanced 36 Machine . . . . . . . . . . 29-10Verification for the Second AS/400 Advanced 36 Machine . . . . . . . . 29-10Verification for the Third AS/400 Advanced 36 Machine . . . . . . . . . . 29-11OS/400 Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-12SSP Side Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-13

Finding Out Why ILAN Is Not ACTIVE or VARIED ON . . . . . . . . . . . . 29-13| Recovery When Communications Were Not Disabled Before Stopping an| AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . . . . . . . 29-14

Using Display Station Pass-Through . . . . . . . . . . . . . . . . . . . . . . . 29-15Running Display Station Pass-Through from OS/400 to SSP . . . . . . . 29-15Changing the QAUTOVRT Value . . . . . . . . . . . . . . . . . . . . . . . 29-15Running Pass-Through from SSP to OS/400 . . . . . . . . . . . . . . . . 29-16Running Pass-Through from SSP to SSP . . . . . . . . . . . . . . . . . . 29-16

Copyright IBM Corp. 1995, 1996

Page 266: Iseries

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36Configurations and Machines . . . . . . . . . . . . . . . . . . . . . . . . . . 30-1

Using the Work with AS/400 Advanced 36 Machine Command . . . . . . . . 30-1Creating An AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . 30-2Changing Attributes for AS/400 Advanced 36 Machines . . . . . . . . . . . 30-3Deleting an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . 30-4Displaying Information about an AS/400 Advanced 36 Machine and Its

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-4Printing Information about an AS/400 Advanced 36 Machine and Its

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-5Renaming an AS/400 Advanced 36 machine . . . . . . . . . . . . . . . . . 30-5Changing the Description for an AS/400 Advanced 36 Machine . . . . . . 30-6Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . . 30-6Ending an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . . 30-7Transferring to an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . 30-7

Using the Work with AS/400 Advanced 36 Machine Configuration Command 30-8Creating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 30-9Changing Attributes and Configuration Details for an AS/400 Advanced

36 Machine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 30-10Deleting an AS/400 Advanced 36 Machine Configuration . . . . . . . . . 30-11Displaying an AS/400 Advanced 36 Machine Configuration . . . . . . . . 30-11Printing an AS/400 Advanced 36 Machine Configuration . . . . . . . . . 30-12Renaming an AS/400 Advanced 36 Machine Configuration . . . . . . . . 30-12Changing the Description for an AS/400 Advanced 36 Machine

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13Summary Table of CL Commands for Managing AS/400 Advanced 36

Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-1Configuration That Exists Immediately after Installation . . . . . . . . . . . . . 31-2

OS/400 Added to a System That Previously Was SSP Only . . . . . . . . 31-2OS/400 and SSP Preloaded from IBM Manufacturing . . . . . . . . . . . . 31-3

Defining a Communications Line or a LAN . . . . . . . . . . . . . . . . . . . . 31-4Defining a Diskette Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-8Defining a Tape or CD-ROM Device . . . . . . . . . . . . . . . . . . . . . . . 31-10Defining Printers and Display Stations Using Device Mapping . . . . . . . . 31-12Defining Printers and Display Stations Using Controller Mapping . . . . . . 31-17Changing a Workstation Controller from Controller Mapping to Device

Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-22Defining Whether SSP or OS/400 Controls SSP Printer Output . . . . . . . 31-26

Giving SSP Control of AS/400 Advanced 36 Machine Printer Output . . 31-26Giving OS/400 Control of AS/400 Advanced 36 Machine Printer Output 31-30Giving OS/400 Control of Printer Output When There Is No Physical

Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-32Defining Whether SSP or OS/400 Controls the Display Station . . . . . . . 31-36Validating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 31-39

Chapter 32. Displaying Information About an AS/400 Advanced 36Configuration and Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1

Displaying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1Displaying a Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-2

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 267: Iseries

Hardware Problem Isolation

Chapter 28. Problem Handling

Hardware Problem IsolationWhen the system detects a hardware problem and you are running an AS/400Advanced 36 machine, the system reports the hardware problem to either the SSPoperating system or the OS/400 operating system.

Hardware Problem Message Sent to SSPIf the system determines that the hardware problem is with a single specific devicethat the SSP operating system is using, the system notifies the SSP operatingsystem about the error. The SSP operating system:

� Gives a return code to the application program.

� Issues an error message to the system console or subconsole for printer errormessages.

Note: If a message is sent to a console, you should follow the error recovery pro-cedure documented in the appropriate S/36 message manual. For informa-tion on how to respond to messages, see Chapter 18, “Handling SSPMessages.”

Hardware Problem Message Sent to OS/400If the system cannot determine that the hardware problems is with a single specificdevice, the system notifies the OS/400 operating system about the error. Usually,the system sends a message to the OS/400 QSYSOPR message queue. You canuse the Display Message (DSPMSG) CL command to display the QSYSOPRmessage queue.

Note: For many of the hardware error messages, you can press Cmd14 to startthe Work with problem support to try and determine the cause of the error.For more information on how to respond to OS/400 messages, seeChapter 5, “Handling OS/400 Messages.”

Using the Product Activity Log to Find out about Hardware ProblemsFor many hardware problems, an entry is placed in the Product Activity Log. Thislog is a list of errors that occurred on the various hardware devices. Examples ofhardware devices include: disks, tapes, diskettes, displays, printers, and commu-nication lines.

You can use the Start System Service Tools (STRSST) CL command to access theProduct Activity Log. For more information about the Product Activity Log, see theAS/400 Service Functions book, SY44-4902.

Determining Who Owns the DeviceDevices can be owned by an OS/400 user who has used the Allocate Object(ALCOBJ) command or by an OS/400 user who is using a CL command to access

| the device. OS/400 users can use the ALCOBJ command to allocate the device| even if they are not actually using the device. Devices can also be owned by an| AS/400 Advanced 36 machine.

Copyright IBM Corp. 1995, 1996 28-1

Page 268: Iseries

Hardware Problem Isolation

| This topic will assist you in determining who owns a device that you may want to| use. The type of owner determines what you need to do in order to use the device.

| � If the owner is an OS/400 user :

Locate the owner and ask if you can use the device. The OS/400 user can usethe Deallocate Object (DLCOBJ) CL command to release the device. If theOS/400 user is using a CL command to access the device, the user can endthe job to release the device. Devices are also given up when the OS/400 usersigns off the system.

� If the owner is an AS/400 Advanced 36 machine :

| If the device is a display station it is released when the AS/400 Advanced 36| machine is powered off. If the device is a tape drive, CD-ROM drive, diskette| drive, printer or communication port, it is released when:

| – The SSP job ends.

| – The SSP job uses a DEALLOC OCL statement to release the device.

| Or,

| – The AS/400 Advanced 36 machine is powered off.

| You can use the instructions in “Determining Which SSP Job Owns a Device” on| page 28-5 to find the SSP job which owns the device.

| On the OS/400 operating system, hardware resources (for example, printers, dis-| plays, and media devices), are defined to the system with device descriptions. A| media device is any CD-ROM drive, tape drive, or diskette drive. You refer to a| hardware resource by using the name of its device description. When someone is| using a resource (owns a resource), a lock is held on the device description by a| job that represents the owner.

| The initial device descriptions are created during an IPL when the system detects| that there are devices attached that do not have device descriptions associated| with them. The names of these device description are based on the the types of| devices (for example, PRT01 for a printer, DSP01 for a display, TAP01 for a tape| drive).

| You can create additional device descriptions for media devices. You might want| to do this to specify different device attributes in each of the device descriptions for| a particular resource. For example, you might have two device descriptions for the| same tape drive. One description might specify QIC525 format. The other might| specify QIC2GB format.

| When someone is using a resource for which there are multiple device descriptions,| the device can be in use by only one of those descriptions at a time. In order to| determine who is using a resource, you need to follow the instructions for each of| the device descriptions associated with the resource until you find the device| description which is in use.

28-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 269: Iseries

Hardware Problem Isolation

| Determining Who Owns a Printer, Display Station or Media| Device| To determine who owns a printer, display station or media device (not a commu-| nication port), you would:

| 1. On an OS/400 command line, type:

WRKOBJLCK device-name \DEVD

| where device-name is the name of the device description. (Examples are| DSP01, TAP01, and PRT03).

2. Press Enter .

| The Work with Objects Locks display is shown for that device. It shows a list of| jobs which are using the device or are waiting to use the device. For each job| in the list, the following information is shown:

| Job The name of the job which is using the device or waiting for the| device

| User The name of the user profile associated with the job

| Lock The type of lock which the job is holding or is waiting to obtain

| Status Information on whether the job is holding or waiting for the lock

| HELD Indicates the job is holding the lock

| REQ Indicates the job is waiting for (requesting) the lock

| 3. To determine who owns the device, you use only the jobs in the list which have| a status of HELD.

| � If there are two jobs which hold a lock on the device, one job with the| name QSYSARB, and the other with a name of the form QM36nnn, then| the device is owned by an AS/400 Advanced 36 machine . nnn are the| decimal digits that represent the ID assigned by the system to the AS/400| Advanced 36 machine. To determine the name of the AS/400 Advanced| 36 machine, use the Work with AS/400 Advanced 36 Machine (WRKM36)| CL command. For more information on the WRKM36 command, see| “Using the Work with AS/400 Advanced 36 Machine Command” on| page 30-1 When you determine which AS/400 Advanced 36 machine owns| the device, use the instructions “Determining Which SSP Job Owns a| Device” on page 28-5 to find the SSP user.

| � If there is a single job with a name other than QSYSARB which holds a| lock on the device, then the device is owned by an OS/400 user . The| displayed user name identifies the person to contact about releasing the| device.

| � If there is a single job with the name QSYSARB which holds a lock on the| device, the device is varied off. If there are multiple device descriptions| associated with the resource, only one of them can be varied on at at time.| You should repeat these steps for each of the other device descriptions,| until you have determined who is using the device.

| Note:

| a. To use a varied off device from an OS/400 job, you first need to vary it on.

| b. When an AS/400 Advanced 36 machine is using a device, that device| appears to OS/400 as varied off.

Chapter 28. Problem Handling 28-3

Page 270: Iseries

Hardware Problem Isolation

| Determining the Owner of a Communication Port| To determine who owns a communication resource, you would:

| 1. On an OS/400 command line, type:

| WRKHDWRSC \CMN

| 2. Press Enter .

| The Work with Communication Resource display is shown.

| 3. Search through the list of communication resources shown on the display until| you find the resource name you want. You may need to page down to find it.

| 4. In the Opt column next to the resource name, type:

| 5

| 5. Press Enter .

| The Work with Configuration Descriptions display is shown. This display con-| tains a list of the line descriptions associated with the communication resource.| Only one of them can use the communication resource at a time.

| 6. Until you determine which line description is using the resource, for each line| description in the list, do as follows:

| a. In the Opt column, next to a line description name, type:

| 8

| b. Press Enter .

| The Work with Configuration Status display is shown.

| c. Check the Status column.

| 1) If words other than VARIED OFF appear in the Status column, the line| description is using the communication resource. In this case, go to| step 7 on page 28-4.

| 2) If the words VARIED OFF appear in the Status column, the line| description is not the one which is using the communication resource.| In this case, continue with step 6c3.

| 3) Press Enter .

| The Work with Configuration Descriptions display is shown.

| 4) Select the next line description in the list.

| 5) Return to step 6a on page 28-4.

| 7. Note the name of the first or only line description shown on the display.

| 8. Use the first three characters of the name to determine whether the commu-| nication port is being used by an AS/400 Advanced 36 machine or is owned by| an OS/400 job. If the line description name:

| � Begins with the characters

| Q36

| an AS/400 Advanced 36 machine is using the communication port.

| � Begins with anything other than Q36, the communication resource is owned| by an OS/400 job.

| 9. If an AS/400 Advanced 36 machine is using the communication port:

28-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 271: Iseries

Hardware Problem Isolation

| a. Determine the machine ID and communication line number from the line| description name. The name is in the form:

| QM36nnnlxx

| where:

| nnn is the ID assigned by the system to the AS/400 Advanced 36 machine.

| l is the line number by which the AS/400 Advanced 36 machine refers to| the communication port. Values 1 through 9 identify lines 1 through 9. A| value of A identifies line 10.

| xx can be any characters.

| b. Press Enter three times to return to an OS/400 command line.

| c. Use the WRKM36 command to determine the name of the AS/400| Advanced 36 machine which owns the communication port. For more infor-| mation on the WRKM36 command, see “Using the Work with AS/400| Advanced 36 Machine Command” on page 30-1.

| d. After you determine which AS/400 Advanced 36 machine owns the commu-| nication port, use the instructions in “Determining Which SSP Job Owns a| Device” on page 28-5 to find the SSP owner.

| 10. If the communication port is owned by an OS/400 job:

| a. Look at the job name associated with the communication port. The job| name includes the name of the user profile which identifies the person to| contact about releasing the device.

| Note: You might need to page down to see the job name.

| b. Note the user profile name.

| c. Press Enter three times to return to an OS/400 command line.

Determining Which SSP Job Owns a Device| This topic includes information on how to determine who owns a

| � Media device

| � Printer or display station

| � Communication line

| Determining the Owner of a Media Device| To determine which SSP job is using a media device which is owned by an AS/400| Advanced 36 machine, do as follows:

| 1. From an SSP command display on the AS/400 Advanced 36 machine, type

| SYSLIST CRT

| 2. Press Enter .

| 3. Type

| DSPSYSVL

| 4. Press Enter .

| A list of SSP system values is displayed.

| 5. Find the system values that begin with DEVMAP

Chapter 28. Problem Handling 28-5

Page 272: Iseries

Hardware Problem Isolation

| 6. Find the one that refers to the device description of the media device.

| 7. Note the ID by which the SSP operating system refers to the device (For| example, T1, T2, TC, or I1).

| 8. Press Enter as many times as necessary to get back to the SSP command| display.

| 9. Type

| STATUS WORKSTN

| 10. Press Enter .

| The Status Work Station display is shown. All devices defined to the SSP are| listed under the WS-ID heading.

| 11. Find the device ID you noted in step 7. You might need to page down to find| it.

| The name of the user and the job which is using the device are displayed with| the device ID.

| Determining the Owner of a Printer or Display Station| To determine which SSP job is using a printer or display station which is owned by| an AS/400 Advanced 36 machine, do as follows:

| 1. On an OS/400 command line, type

| DSPM36 library-name/machine-name

| where library-name is the name of the library that contains the AS/400| Advanced 36 machine and machine-name is the name of the AS/400 Advanced| 36 machine.

| 2. Press Enter .

| The Display M36 Machine display is shown.

| 3. In the Selection field, type

| 2

| 4. Press Enter .

| The Display M36 Display and Printer Dev display is shown.

| 5. Press F21.

| The display changes to show the device description names of the various| display stations and printers defined to the SSP operating system on this work-| station controller.

| 6. Search through the list to find your device.

| 7. If you do not find your device,

| a. Press Enter

| b. Move the cursor to the next workstation controller.

| c. Return to step 5 on page 28-6.

| 8. If you find your device, note its port and address (row and column), and the| workstation controller number shown in the upper right corner on the display.

| 9. Press Enter twice.

| 10. Press F3.

28-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 273: Iseries

Hardware Problem Isolation

| 11. On the AS/400 Advanced 36 machine command display, type

| CNFIGSSP

| 12. Press Enter .

| The CNFIGSSP main menu is shown.

| 13. Type

| 3

| to select Review a configuration.

| 14. Press Enter .

| The CONFIGURATION MEMBER DEFINITION display is shown.

| 15. Type

| 5

| 16. Press Enter

| Screen 6.0 is shown.

| 17. Press Enter .

| Screen 5.0 is shown.

| 18. Type

| 1

| to select Work with display stations and printers.

| 19. Press Enter .

| Screen 27.0 is shown.

| 20. Type

| 6

| to select Change display stations or printer workstation IDs.

| 21. Press Enter .

| Screen 40.0 is shown.

| 22. Look at the port number that is shown.

| 23. Press Enter until the port you are looking for is shown.

| Note: Ports ðð through ð7 correspond to ports ð through 7 on workstation con-| troller 1.

| Ports ð8 through 15 correspond to ports ð through 7 on workstation con-| troller 2.

| Ports 16 through 23 correspond to ports ð through 7 on workstation con-| troller 3.

| Ports 24 through 31 correspond to ports ð through 7 on workstation con-| troller 4.

| 24. Find the workstation ID that corresponds to the address for which you are| looking.

| 25. Press Cmd 19 .

| 26. Press Cmd 3 .

Chapter 28. Problem Handling 28-7

Page 274: Iseries

Hardware Problem Isolation

| 27. Type

| STATUS WORKSTN

| 28. Press Enter .

| The Status Work Station display is shown. All devices defined to the SSP are| listed under the WS-ID heading.

| 29. Find the device ID you noted in step 24 on page 28-7. You might need to| page down to find it.

| 30. Find the user and jobname in the appropriate columns beside the device.

| Determining the Owner of a Communication Line| SSP communication lines are not owned by a particular job or user. However, the| directions here will help you find out how the line is being used.

| To determine how an SSP communication line is being used, do as follows:

| 1. On an SSP command display on the AS/400 Advanced 36 machine, type

| D L,line-number

| where line-number is the number of the communication line.

| The COMMUNICATIONS LINE ACTIVITY display and the Activate Communica-| tions line menu are shown.

| 2. Look at the User field shown in the upper right portion of the screen. This field| indicates the type of communications job which is using the line.

How to Handle OS/400 and SSP Printer ConflictsThere are a number of alternatives. If OS/400 and SSP printer conflicts frequentlyarise, choose to do one of the following:

� Use output queue support.

| Send SSP output to an OS/400 output queue and have the OS/400 spool writerprint SSP output along with OS/400 output. For directions, see “Giving SSPControl of AS/400 Advanced 36 Machine Printer Output” on page 31-26.

� Dedicate printers to SSP or OS/400. For directions, see “Defining WhetherSSP or OS/400 Controls the Display Station” on page 31-36.

� Get an additional printer.

Using the Work with Configuration Status Command to Determine IfDevices are Varied Off

The Work with Configuration Status (WRKCFGSTS) command should only be usedafter the WRKOBJLCK command.

When you use the WRKOBJLCK command, a display appears on which the ownerof the lock is identified. The user ID which owns the lock on the device has astatus of held in the Status field. Any other user IDs which have requested use ofthe device have REQ in the Status field.

Note: A lock on a printer or a display station is an exclusive read (*EXCLRD) lockheld by a single job on the system.

28-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 275: Iseries

What the Error Codes Mean

When a lock is given up by a display station, the lock request is satisfied and theQBASE subsystem owns the lock as it does when you are on a sign-on display.

When a lock is given up by a print writer, the system arbiter owns the lock. If aprinter is available, you see the following message:

There are no locks for the object.

Once you know whether there is a lock on a device, you are ready to use theWRKCFGSTS command to find out whether devices are varied on or varied off.

Handling AS/400 Advanced 36 Machine Error Codes

Determining What the Error Codes MeanErrors that are generated because there are problems related to using OS/400 andSSP on the same system, are included in this chapter.

If you were not referred to this book for recovery, move your cursor to the messageand press Cmd1 for more information.

If you were referred to this book for recovery, find the error code in the followinglist. Then, read the Message and Recovery column. The following error codes canbe shown for CPFACE0 exceptions:

Error Code Message and Recovery

00010001 AS/400 Advanced 36 machine not started. The machine stateis not valid because an internal processing error occurred.

Contact your service representative for help.

00010002 Object type or subtype is not valid because an internal pro-cessing error occurred.

Contact your service representative for help.

00010003 The AS/400 Advanced 36 machine is still active because themachine was not able to shutdown completely.

To recover, end each AS/400 Advanced 36 machine on thesystem. Then, do another IPL of the AS/400 system.

00010004 The function code is not valid because an internal processingerror occurred.

Contact your service representative for help.

00010005 The AS/400 Advanced 36 machine machine pointer is not validbecause an internal processing error occurred.

Contact your service representative for help.

00010006 Migration is pending and the state of the AS/400 Advanced 36machine is not valid.

Contact your service representative for help.

01010002 Insufficient storage space exists to create the minimum sizeAS/400 Advanced 36 machine.

To recover, free up disk storage or add another disk. The

Chapter 28. Problem Handling 28-9

Page 276: Iseries

What the Error Codes Mean

minimum storage space required to create an AS/400Advanced 36 machine is 80 megabytes.

01010003 User storage limit exceeded. The machine cannot be createdbecause it causes the user's storage limit to be exceeded.

Free up user storage or increase the storage limit specified inthe user profile for the user ID of the person creating theAS/400 Advanced 36 machine.

03010001 Configuration template bytes provided less than 16 megabytes.

Contact your service representative for help.

03010002 Configuration template device category mask is non-zero.

Contact your service representative for help.

03010003 Configuration template reserve bytes are non-zero.

Contact your service representative for help.

03010004 Invalid device category.

Contact your service representative for help.

03010005 Resource not compatible with device category. A hardwareresource was renamed after the machine configuration wasapplied.

To recover, start the machine again and apply the same config-uration.

03010006 Resource name not valid. A hardware resource was renamedafter the machine configuration was applied.

To recover, start the AS/400 Advanced 36 machine again andapply the same configuration.

03010007 Device code is not valid.

Contact your service representative for help.

03010008 IPL device category is not valid.

Contact your service representative for help.

03010009 IPL device code is not valid.

Contact your service representative for help.

0301000A IPL resource name is not valid. A hardware resource wasrenamed after the machine configuration was applied.

To recover, start the AS/400 Advanced 36 machine again andapply the same configuration.

0301000B The resource is not an IPL-able device. A hardware resourcewas renamed after the AS/400 Advanced 36 machine config-uration was applied.

To recover, start the AS/400 Advanced 36 machine again andapply the same configuration.

0301000C No configuration exists in the AS/400 Advanced 36 machine.

Apply a valid AS/400 Advanced 36 machine configuration usingthe APYM36CFG parameter on the STRM36 command.

28-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 277: Iseries

What the Error Codes Mean

0301000D The AS/400 Advanced 36 machine configuration is no longervalid. It is out of date.

Contact your service representative for help.

0301000E The configuration template has a duplicate device code.

Contact your service representative for help.

0301000F The configuration template has a duplicate resource name.

Contact your service representative for help.

03010010 An IPL from media is required. There is no SSP/reload inprogress.

To recover, load the SSP from tape, CD-ROM, or diskette.

03010011 There is at least one workstation controller missing.

Contact your service representative for help.

03010012 The AS/400 Advanced 36 machine configuration that is appliedis not capable of using a resource.

Restart the machine and apply the same configuration.

03010013 The AS/400 Advanced 36 machine cannot use the IPLresource because a hardware resource was renamed after themachine configuration was applied.

To recover, start the machine again and apply the same config-uration.

03010014 There is not enough disk storage to start the AS/400 Advanced36 machine.

To recover, free up some disk storage or add another disk.

05010001 The STRM36PRC CL command was entered but the OS/400user ID is not correct for the AS/400 Advanced 36 machine.

To recover, have the security officer add the OS/400 user ID tothe user ID file on the AS/400 Advanced 36 machine.

05010002 The STRM36PRC CL command was entered, but the defaultmenu is not correct for the specified user ID.

To recover, have the security officer for the AS/400 Advanced36 machine correct the default user menu or help menu for theuser ID. More information about the cause of the error can befound in the S/36 history file.

05010003 The STRM36PRC CL command was entered but the procedureis not correct. The procedure might not exist. It is also possiblethat you may not be authorized to use the procedure or youruser ID may be restricted to run only a specific procedure.

To recover, make sure the procedure you are trying to runexists on the AS/400 Advanced 36 machine. Get authorizationto run the procedure. More information about the cause of theerror is in the S/36 history file.

Chapter 28. Problem Handling 28-11

Page 278: Iseries

What the Error Codes Mean

05010004 The STRM36PRC CL command was entered but the library isnot correct. The library might not exist. You may not beauthorized to the library or your user ID may be restricted touse only a specific library.

Ensure that the library you are trying to use exists on theAS/400 Advanced 36 machine. Have the security officerauthorize you to this library. More information about the causeof the error can be found in the S/36 history file.

05010005 The procedure was terminated abnormally. The STRM36PRCCL command was entered but the procedure did not success-fully complete. Common reasons for this error are:

� Option 3 was taken to an error message

� The Attention key was pressed and the option to terminatethe procedure was selected.

More information about the cause of the error can be found inthe S/36 history file.

0501000F The STRM36PRC CL command was entered, but the proce-dure did not successfully complete.

More information about the cause of the error can be found inthe S/36 history file. Contact your service representative forhelp.

05010011 The STRM36PRC or TFRM36 CL command was entered butthere were no SSP workstations available for the transfer.

To recover, do the following. Display the job log for yourOS/400 job. If message CPIAC82 is in the job log, yourOS/400 display is probably not defined to this AS/400Advanced 36 machine. The CL command tried to find anunused SSP display station. However, all the display stationsdefined were in use.

If this error occurs frequently, the SSP configuration should be| updated to add additional display stations or the AS/400| Advanced 36 machine configuration should be updated to

include this OS/400 display so an SSP display station will bereserved for this OS/400 display.

If there is no CPIAC82 message in the job log, your display isconfigured in the AS/400 Advanced 36 machine for a specificcontroller, port and workstation address. The specific addressis already in use so the CL command failed.

There may be a display station error message that the systemoperator must respond to before this workstation address canbe used again.

Another reason for this error is another display station hasalready signed on to this specific address.

05010012 The STRM36PRC or TFRM36 CL command was entered and aworkstation ID was specified. However, the workstation ID isnot defined to the AS/400 Advanced 36 machine at this time.

28-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 279: Iseries

What the Error Codes Mean

To recover, issue the CL command again specifying a validworkstation ID.

If the system is be reloaded, no workstation IDs are defined bythe AS/400 Advanced 36 machine. If a display is defined in theAS/400 Advanced 36 machine at controller 1 port 0 address 0,only that display station is allowed to transfer into the AS/400Advanced 36 machine

To recover, issue the CL command specifying *DFT for theworkstation ID.

05010013 The STRM36PRC or TFRM36 CL command was entered, anda workstation ID was specified, but the workstation ID isalready in use or a display station error message is waiting fora response from the system operator.

To recover, check to see if there is display station errormessage that the system operator must respond to before thisworkstation ID can be used again. Try the command againafter the system operator responds to the message. If thatdoesn't work, try the command again with a different work-station ID.

05010014 The STRM36PRC or TFRM36 CL command was entered butthe address that was specified for the AS/400 Advanced 36machine was not configured for the AS/400 Advanced 36machine.

To recover, use the CHGM36CFG command to update the| AS/400 Advanced 36 machine configuration to include this| display station. The next time the AS/400 Advanced 36

machine is ended and started, apply the updated configurationthat includes the display station.

05010015 The STRM36PRC or TFRM36 CL command was entered butthe address that was specified to the SSP was already in useor a display station error message must be responded to by thesystem operator.

To recover, have the system operator respond to any waitingerror messages or try the command again with a differentdisplay station ID.

05010017 The STRM36PRC or TFRM36 CL command was entered butthe S/36 display station was varied off.

To recover, vary on the display station from the AS/400Advanced 36 machine console using the VARY command.

07010001 The configuration template provided less than sixteen bytes.

Contact your service representative for help.

07010002 The Configuration template device category mask is not valid.

Contact your service representative for help.

07010003 The configuration template reserved bytes that are nonzero

Contact your service representative for help.

Chapter 28. Problem Handling 28-13

Page 280: Iseries

What the Error Codes Mean

07010004 The AS/400 Advanced 36 machine has no configurationbecause the AS/400 Advanced 36 machine has never beenstarted.

To recover, start the AS/400 Advanced 36 machine and apply aconfiguration. Then, try your request again.

07010005 The AS/400 Advanced 36 machine configuration is out of date.A hardware resource was renamed after the AS/400 Advanced36 machine configuration was applied.

To recover, start the machine again and reapply the configura-tion. Then, try your request again.

08010001 The token is not valid.

Contact your service representative for help.

09010001 Unconverted AS/400 Advanced 36 machine does not existbecause an internal processing error occurred.

Contact your service representative for help.

0B010000 There is a communication object processing error.

Contact your service representative for help.

00FFnnnn Unexpected exception (nnnn)

Contact your service representative for help.

00FE0001 Configuration is missing

Contact your service representative for help.

00FE0002 Configuration has a resource name that is not valid.

Contact your service representative for help.

00FE0003 Configuration has invalid device class

Contact your service representative for help.

00FE0004 The configuration has a duplicate device code.

Contact your service representative for help.

00FE0005 The configuration has a duplicate resource name.

Contact your service representative for help.

00FE0006 The configuration has resource that the S/36 is not capable ofusing.

Contact your service representative for help.

00FE0007 The configuration has a new device code.

Contact your service representative for help.

28-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 281: Iseries

ILAN Communications

Chapter 29. System-to-System Communications - ILANCommunications

When multiple, different, operating systems exist on a single physical system, it isoften desirable for applications running on these operating systems to have a wayto communicate with each other. ILAN offers a way of doing this without physicalcommunication links. ILAN Communications are accomplished by defining anetwork within the system. This network is linked by what is called an InternalLocal Area Network (ILAN). Just as a Local Area Network (LAN) connects systems

| externally, an Internal Local Area Network (ILAN) connects operating systems| inside the AS/400 system.

| Any operating system running on the system can communicate with any other oper-| ating system running on the system.

On a LAN, you would find the following type of configuration:

RV3D360-2

OtherConnections

AS/400 AS/400

AS/400Advanced 36

AS/400Advanced 36

System/36

Token Ring

Copyright IBM Corp. 1995, 1996 29-1

Page 282: Iseries

ILAN Communications

On an ILAN, you would find the following type of configuration:

RV3D361-0

OtherConnections

OS/400

AS/400Advanced 36Machine

AS/400Advanced 36Machine

AS/400Advanced 36Machine

Token Ring

| The fact that there is no physical communications link is transparent to the applica-| tions that reside on the AS/400 system. APPC and APPN communications do not| require a physical communications link to connect with the operating systems within| the system. The connection takes place within the lower levels of the software.

APPC and APPN communications are supported over the ILAN. Some examplesare:

� DDM � SNADS

| � ODF� Display Station Pass-through� Customer-written APPC applications

Every physical LAN (such as Token-Ring or Ethernet) has the following threeunique identifiers for each operating system:

� Source Service Access Point (SSAP)� Destination Service Access Point (DSAP)

� Adapter address

However, on an ILAN, these identifiers are more specifically defined as follows:

| � An SSAP is defined for the AS/400 system itself and for each machine on the| system

� The DSAP identifier is the SSAP of the machine with which you want to com-municate.

� The adapter address is not used.

29-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 283: Iseries

ILAN Communications

To an external network, these coexisting operating systems or machines appear tobe independent systems. External networks are unaware that each of these oper-ating systems actually reside on the same piece of equipment.

Setting up ILAN CommunicationsInstructions on how to set up ILAN communications for your AS/400 Advanced 36machines are in chapter 4 of the Getting SSP and OS/400 Installed and Runningbook, SC21-8377.

Understanding Default Startup SettingsWhen the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

You need to decide whether you want to start ILAN manually or automatically andmake changes for SSP or for OS/400.

Notes:

1. If you create additional AS/400 Advanced 36 machines and you set up ILAN for| those AS/400 Advanced 36 machines, the OS/400 side of ILAN automatically| starts during the next IPL of OS/400. If you want to use ILAN communications

before the next IPL, you must manually start the OS/400 side.

2. If you do not stop ILAN communications before you power down the AS/400Advanced 36 machine, you must go to OS/400 (and any AS/400 Advanced 36machine connected to this AS/400 Advanced 36 machine) to stop and thenrestart the ILAN connections with this AS/400 Advanced 36 machine.

Manually Starting the ILANIn order for ILAN to establish a link between the OS/400 Operating System and theSSP Operating System, ILAN communications must be started on both operatingsystems.

On the OS/400 Operating System, the APPC Controller Description was createdwith ONLINE(*YES) specified. This starts and varies on the Controller Descriptionobjects at OS/400 Initial Program Load (IPL) time.

If you do not start the ILAN automatically, and you want to use ILAN, ILAN commu-nications must be started manually.

Manually Starting the OS/400 Side of ILANWhen the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

You must make changes to the OS/400 side if you want ILAN communications tomanually start for OS/400.

Chapter 29. System-to-System Communications - ILAN Communications 29-3

Page 284: Iseries

ILAN Communications

Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-| ically starts during the next IPL of OS/400. If you want to use ILAN com-

munications before the next IPL, you must manually start the OS/400 side.

The following steps are required to manually start the OS/400 side of ILAN for eachAS/400 Advanced 36 machine. They must be completed each time you do eitherof the following:

� IPL the system.

� Restart the AS/400 Advanced 36 machine unless the APPC subsystem is disa-bled before you end your AS/400 Advanced 36 machine.

Note: If your APPC subsystem is not disabled before you end your AS/400Advanced 36 machine, you must vary your AS/400 controllerdescription *OFF and then *ON again.

1. To start ILAN communications manually for the first AS/400 Advanced 36| machine each time you IPL the system, vary on the controller for the AS/400| Advanced 36 machine for which ILAN communications are set up:

a. On the OS/400 command line, for the first AS/400 Advanced 36 machine,type

VRYCFG QILANM36ð1 \CTL \ON

where QILANM36ð1 is the OS/400 APPC controller description name.

b. Press Enter .

ILAN communications are now started on the OS/400 side for the firstAS/400 Advanced 36 machine

| 2. To start ILAN communications manually for the second or third AS/400| Advanced 36 machine each time you IPL the system, vary on the controller for| the second or third AS/400 Advanced 36 machine for which ILAN communica-

tions are set up:

a. On the OS/400 command line, for each additional AS/400 Advanced 36machine, type

VRYCFG ILANM36ðx \CTL \ON

where x is the number of an AS/400 Advanced 36 machine that you wantto start. For the second AS/400 Advanced 36 machine, x is 2. For thethird AS/400 Advanced 36 machine, x is 3.

b. Press Enter .

ILAN communications are now started on the OS/400 side for either thesecond or third AS/400 Advanced 36 machine.

Manually Starting the SSP Side of ILAN (All Connections)When the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-

29-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 285: Iseries

ILAN Communications

| ically starts during the next IPL of OS/400. If you want to use ILAN com-munications before the next IPL, you must manually start the OS/400 side.

On the SSP Operating System, communication line 15 is used for ILAN commu-nications. To start the APPC subsystem:

1. On the command line, type

ENABLE ILANSBS,#CNFGLIB,15

2. Press Enter .

ILAN communications are now started on the SSP side.

Note: These steps must be completed each time you start an AS/400Advanced 36 machine.

Manually Starting the SSP Side of ILAN (A Single Connection)When the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-| ically starts during the next IPL of OS/400. If you want to use ILAN com-

munications before the next IPL, you must manually start the OS/400 side.

On the SSP Operating System, communication line 15 is used for ILAN commu-nications. To start the APPC subsystem:

1. On the command line, type

ENABLE ILANSBS,#CNFGLIB,15,NOSHOW,xxxxxxxx

where xxxxxxxx is the control point name.

� IBMM3601 is the control point name of the first AS/400 Advanced 36machine.

� IBMM3602 is the control point name of the second AS/400 Advanced 36machine.

� IBMM3603 is the control point name of the third AS/400 Advanced 36machine.

� Sxxxxxxx (S followed by the serial number of the AS/400 system) is theIBM-supplied control point name for OS/400. For directions on finding outwhat this name is see “Finding Out the OS/400 Control Point Name” onpage 29-8.

2. Press Enter .

ILAN communications are now started on the SSP side for the single con-nection you specified.

Chapter 29. System-to-System Communications - ILAN Communications 29-5

Page 286: Iseries

ILAN Communications

Automatically Starting ILAN CommunicationsIn order for ILAN to establish a link between the OS/400 operating system and anSSP operating system or between two SSP operating systems, ILAN communica-tions must be started.

When the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

You do not need to make changes to the OS/400 side unless ILAN communica-tions were changed to manually start OS/400.

Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-| ically starts during the next IPL of OS/400. If you want to use ILAN com-

munications before the next IPL, you must manually start the OS/400 side.

Automatically Starting ILAN Communications for SSPTo start ILAN communications automatically for SSP, do as follows:

1. From an SSP display, edit the #STRTUP2 procedure in the #LIBRARY.

2. Add the following line:

ENABLE ILANSBS,#CNFGLIB,15

3. Save and exit the #STRTUP2 procedure.

4. Stop the AS/400 Advanced 36 machine.

5. Start the AS/400 Advanced 36 machine.

ILAN communications will automatically start when that AS/400 Advanced 36machine is started until you change the instructions to start ILAN communica-tions manually.

Automatically Starting ILAN Communications for OS/400Directions in this section allow you to automatically start ILAN communications onthe OS/400 side of the ILAN. For directions on automatically starting the SSP sideof ILAN communications, see “Automatically Starting ILAN Communications” onpage 29-6.

When the system is shipped, ILAN communications are set to be started:

� Manually by you for SSP

� Automatically by the system for OS/400

You do not need to make changes to the OS/400 side unless ILAN communica-tions were changed to manually start OS/400.

Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-| ically starts during the next IPL of OS/400. If you want to use ILAN com-

munications before the next IPL, you must manually start the OS/400 side.

29-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 287: Iseries

ILAN Communications

To start ILAN communications for OS/400 automatically for your first AS/400Advanced 36 machine, do as follows:

1. On an AS/400 command line, type

CHGCTLAPPC QILANM36ð1 ONLINE(\YES)

where QILANM36ð1 is the name of the OS/400 APPC controller description forthe first AS/400 Advanced 36 machine.

2. Press Enter .

| Each time the system is IPLed, ILAN communications will automatically start for theOS/400 operating system.

To start ILAN communications for OS/400 automatically for the second or thirdAS/400 Advanced 36 machine, do as follows:

1. On an AS/400 command line, type

CHGCTLAPPC ILANM36ðx ONLINE(\YES)

where x is 2 for the second AS/400 Advanced 36 machine and where x is 3 forthe third AS/400 Advanced 36 machine if you used the recommended namesfor the AS/400 APPC controller description.

2. Press Enter .

Each time the AS/400 Advanced 36 system is IPLed, ILAN communications willautomatically start for the OS/400 operating system.

Disabling Automatic Startup of ILANIf OS/400 or SSP or both are automatically started, and you want to start themmanually, you need to disable automatic startup of ILAN.

| When the system is shipped, ILAN communications are set to be started:

| � Automatically by the system for OS/400.

| � Manually by you for SSP.

1. To disable ILAN communications on the OS/400 side, do the following:

a. On the OS/400 command line, type

CHGCTLAPPC QILANM36ð1 ONLINE(\NO)

for the first AS/400 Advanced 36 machine where QILANM36ð1 is the name ofthe OS/400 APPC controller description.

Or,

CHGCTLAPPC ILANM36ðx ONLINE(\NO)

Where x is the number of an AS/400 Advanced 36 machine that you wantto start. For the second AS/400 Advanced 36 machine, x is 2. For thethird AS/400 Advanced 36 machine, x is 3.

b. Press Enter .

This change to manual startup takes effect the next time the AS/400Advanced 36 machine is started.

Repeat steps 1a and 1b for each AS/400 Advanced 36 machine.

Chapter 29. System-to-System Communications - ILAN Communications 29-7

Page 288: Iseries

ILAN Communications

2. To disable ILAN communications on the SSP side, comment out or delete thefollowing statement from the #STRTUP2 procedure in the #LIBRARY:

ENABLE ILANSBS,#CNFGLIB,15

This change to manual startup takes effect after the next IPL of OS/400 or afterthe next startup of the AS/400 Advanced 36 machine.

Finding Out the OS/400 Control Point NameTo find out the name of the OS/400 control point, do as follows:

1. On a command line on the OS/400 system console, type

DSPNETA

2. Press Enter .

The Display Network Attributes display is shown.

3. On the Display Network Attributes display, find the line titled Local control pointname. This is the name of the AS/400 system in a network.

4. Make note of the name.

5. Press F3 (Exit) to return to a command line.

Stopping ILAN CommunicationsThe directions in this topic tell you how to stop ILAN communications. You muststop ILAN communications on the OS/400 side of the ILAN and on each AS/400Advanced 36 machine. This must be done manually. You cannot stop ILAN com-munications automatically.

Once you stop ILAN communications, you will need to manually restart ILAN com-munications if you want to use ILAN before the next IPL.

Note: Automatic starting of ILAN communications only occurs at IPL time.

Stopping ILAN Communications on the OS/400 SideTo stop ILAN communications on the OS/400 side of the ILAN:

| 1. Vary off the ILAN controller for each AS/400 Advanced 36 machine as follows:

a. On an OS/400 command line, type

VRYCFG QILANM36ð1 \CTL \OFF

| where QILANM36ð1 is the name of the controller description for the first| AS/400 Advanced 36 machine.

| b. Press Enter to vary off the ILAN controller for the first AS/400 Advanced 36| machine and stop ILAN communications for the first AS/400 Advanced 36

machine.

Note: If you have more than one AS/400 Advanced 36 machine on thisAS/400 system, continue with the next step.

2. On an OS/400 command line, type

VRYCFG ILANM36ðx \CTL \OFF

29-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 289: Iseries

ILAN Communications

where x is a 2 for the second AS/400 Advanced 36 machine and x is a 3 forthe third AS/400 Advanced 36 machine.

| 3. Press Enter to vary off the ILAN controller for the AS/400 Advanced 36| machine and stop ILAN communications for that AS/400 Advanced 36 machine.

4. If you have another AS/400 Advanced 36 machine, repeat step 2 and step 3 forthat AS/400 Advanced 36 machine.

Stopping ILAN Communications on the SSP Side (All Connections)To stop ILAN communications on the SSP side, do the following for each AS/400Advanced 36 machine:

1. From an SSP command prompt on the AS/400 Advanced 36 machine for whichyou want to stop ILAN communications, type

DISABLE ILANSBS

2. Press Enter .

3. If you get a SYS-8003 message ILANSBS -- DISABLE tried but subsystemactive., respond to the message with a 2 to immediately disable all active ses-sions.

ILAN communications are now stopped for the AS/400 Advanced 36 machine forwhich you completed the steps in this section.

Note: If you do not stop ILAN communications before you power down theAS/400 Advanced 36 machine, you must go to OS/400 (and any AS/400Advanced 36 machine connected to this AS/400 Advanced 36 machine) tostop and then restart the ILAN connections with this AS/400 Advanced 36machine.

Stopping ILAN on the SSP Side (Single Connection)To stop ILAN on the SSP side, do the following on the AS/400 Advanced 36machine from which you want to disconnect another AS/400 Advanced 36 machineor OS/400:

1. From an SSP command prompt on the AS/400 Advanced 36 machine for whichyou want to stop a single ILAN connection, type

DISABLE ILANSBS,xxxxxxxx

where xxxxxxxx is the control point name.

� IBMM3601 is the control point name of the first AS/400 Advanced 36machine.

� IBMM3602 is the control point name of the second AS/400 Advanced 36machine.

� IBMM3603 is the control point name of the third AS/400 Advanced 36machine.

� Sxxxxxxx (S followed by the serial number of the AS/400 system) is theIBM-supplied control point name for OS/400. For directions on finding outthis name, see “Finding Out the OS/400 Control Point Name” onpage 29-8.

2. Press Enter .

Chapter 29. System-to-System Communications - ILAN Communications 29-9

Page 290: Iseries

ILAN Communications

3. If you get a SYS-8003 message ILANSBS -- DISABLE tried but subsystemactive., respond to the message with a 2 to immediately disable all active ses-sions.

ILAN communications are now stopped for that single connection to the AS/400Advanced 36 machine for which you completed the steps in this section.

Note: If you do not stop ILAN communications before you power down an AS/400Advanced 36 machine, you must go to OS/400 (and any AS/400 Advanced36 machine connected to this AS/400 Advanced 36 machine) to stop andthen restart the ILAN connections with this AS/400 Advanced 36 machine.

ILAN Communications VerificationThis section explains how to verify that your ILAN communications are started. Youmust verify ILAN communications on both OS/400 and SSP. Directions for settingup ILAN communications are in Chapter 4 of Getting SSP and OS/400 Installedand Running book, SC21-8377.

Verification for the First AS/400 Advanced 36 Machine1. Get the OS/400 Control Point Name. For directions, see “Finding Out the

OS/400 Control Point Name” on page 29-8.

| 2. Go to the console for the first AS/400 Advanced 36 machine and manually start| the ILAN subsystem for the first AS/400 Advanced 36 machine. For directions,

see “Manually Starting the SSP Side of ILAN (All Connections)” on page 29-4.

| 3. Go to the OS/400 console and verify ILAN communications for the first AS/400| Advanced 36 machine. For directions, see “OS/400 Verification” on

page 29-12.

| Note: If the OS/400 ILAN controller was not started during IPL, follow the| directions in “Manually Starting the OS/400 Side of ILAN” on page 29-3.

| 4. Go to the console for the first AS/400 Advanced 36 machine and verify ILAN| communications for OS/400. For directions, see “SSP Side Verification” on

page 29-13.

5. Run Display Station Pass-through from OS/400 to SSP if you have an availableOS/400 workstation. For directions, see “Using Display Station Pass-Through”on page 29-15.

| Note: If you do not stop ILAN communications before you power off the AS/400| Advanced 36 machine, when you start the AS/400 Advanced 36 machine| again, you might need to stop and restart all of the ILAN connections to the| AS/400 Advanced 36 machine. For information on how to do this, see| “Recovery When Communications Were Not Disabled Before Stopping an| AS/400 Advanced 36 Machine” on page 29-14.

Verification for the Second AS/400 Advanced 36 Machine1. Get the OS/400 Control Point Name. For directions, see “Finding Out the

OS/400 Control Point Name” on page 29-8.

| 2. Go to the OS/400 console and manually start the ILAN controller for the second| AS/400 Advanced 36 machine. For directions, see “Manually Starting the

OS/400 Side of ILAN” on page 29-3.

29-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 291: Iseries

ILAN Communications

3. Go to the console for the first AS/400 Advanced 36 machine and manually start| the ILAN subsystem for the second AS/400 Advanced 36 machine. For| directions, see “Manually Starting the SSP Side of ILAN (A Single Connection)”| on page 29-5.

| 4. Go to the console for the second AS/400 Advanced 36 machine and manually| start the ILAN subsystem for the second AS/400 Advanced 36 machine. For

directions, see “Manually Starting the SSP Side of ILAN (All Connections)” onpage 29-4.

| 5. Go to the OS/400 console and verify ILAN communications for the second| AS/400 Advanced 36 machine. For directions, see “OS/400 Verification” on

page 29-12.

| 6. Go to the console for the first AS/400 Advanced 36 machine and verify ILAN| communications for the second AS/400 Advanced 36 machine. For directions,

see “SSP Side Verification” on page 29-13.

| 7. Go to the console for the second AS/400 Advanced 36 machine and verify| ILAN communications for connections for OS/400 and the first AS/400

Advanced 36 machine. For directions, see “SSP Side Verification” onpage 29-13.

| Note: If you do not stop ILAN communications before you power off the AS/400| Advanced 36 machine, when you start the AS/400 Advanced 36 machine| again, you might need to stop and restart all of the ILAN connections to the| AS/400 Advanced 36 machine. For information on how to do this, see| “Recovery When Communications Were Not Disabled Before Stopping an| AS/400 Advanced 36 Machine” on page 29-14.

Verification for the Third AS/400 Advanced 36 Machine1. Get the OS/400 Control Point Name. For directions, see “Finding Out the

OS/400 Control Point Name” on page 29-8.

2. Go to the OS/400 console and manually start the ILAN controller for the thirdAS/400 Advanced 36 machine. For directions, see “Manually Starting theOS/400 Side of ILAN” on page 29-3.

| 3. Go to the console for the first AS/400 Advanced 36 machine and manually start| the ILAN subsystem for the third AS/400 Advanced 36 machine. For directions,| see “Manually Starting the SSP Side of ILAN (A Single Connection)” on| page 29-5.

| 4. Go to the console for the second AS/400 Advanced 36 machine and manually| start the ILAN subsystem for the third AS/400 Advanced 36 machine. For| directions, see “Manually Starting the SSP Side of ILAN (A Single Connection)”| on page 29-5.

| 5. Go to the console for the third AS/400 Advanced 36 machine and manually| start the ILAN subsystem for the third AS/400 Advanced 36 machine. For

directions, see “Manually Starting the SSP Side of ILAN (All Connections)” onpage 29-4.

| 6. Go to the OS/400 console and verify ILAN communications for the third AS/400| Advanced 36 machine. For directions, see “SSP Side Verification” on

page 29-13.

Chapter 29. System-to-System Communications - ILAN Communications 29-11

Page 292: Iseries

ILAN Communications

| 7. Go to the console for the first AS/400 Advanced 36 machine and verify ILAN| communications for the third AS/400 Advanced 36 machine. For directions,

see “SSP Side Verification” on page 29-13.

| 8. Go to the console for the second AS/400 Advanced 36 machine and verify| ILAN communications for the third AS/400 Advanced 36 machine. For

directions, see “SSP Side Verification” on page 29-13.

| 9. Go to the console for the third AS/400 Advanced 36 machine and verify ILAN| communications for all connections for OS/400, the first AS/400 Advanced 36

machine and the second AS/400 Advanced 36 machine. For directions, see“OS/400 Verification” and “SSP Side Verification” on page 29-13.

| Note: If you do not stop ILAN communications before you power off the AS/400| Advanced 36 machine, when you start the AS/400 Advanced 36 machine| again, you might need to stop and restart all of the ILAN connections to the| AS/400 Advanced 36 machine. For information on how to do this, see| “Recovery When Communications Were Not Disabled Before Stopping an| AS/400 Advanced 36 Machine” on page 29-14.

OS/400 Verification| To verify ILAN communications for the first AS/400 Advanced 36 machine, do as| follows:

1. On an OS/400 command prompt, type

WRKCFGSTS \CTL QILANM36ð1

| where QILANM36ð1 is the OS/400 APPC controller description name for the first| AS/400 Advanced 36 machine.

2. Press Enter .

3. Check the Status column.

Communications are started properly if the status is ACTIVE or VARIED ON.

4. If the status is not ACTIVE or VARIED ON, go to “Finding Out Why ILAN IsNot ACTIVE or VARIED ON” on page 29-13.

5. If the status is ACTIVE or VARIED ON, and you only installed one AS/400Advanced 36 machine, go to “SSP Side Verification” on page 29-13 and verifythe SSP Side.

6. If the status is ACTIVE or VARIED ON, and you installed two or three AS/400| Advanced 36 machines, verify ILAN communications on the other AS/400| Advanced 36 machines.

| To verify ILAN communications for the second or third AS/400 Advanced 36| machine, do as follows:

1. On an OS/400 command prompt, type

WRKCFGSTS \CTL ILANM36ðx

where ILANM36ðx is the OS/400 APPC controller description name.

If you used the recommended names, this is ILANM36ð2 for the second AS/400Advanced 36 machine and ILANM36ð3 for the third AS/400 Advanced 36machine.

2. Press Enter .

29-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 293: Iseries

ILAN Communications

3. Check the Status column.

Communications are started properly if the status is ACTIVE or VARIED ON.

4. If the status is not ACTIVE or VARIED ON, go to “Finding Out Why ILAN IsNot ACTIVE or VARIED ON” on page 29-13.

5. If the status is ACTIVE or VARIED ON, and you have checked the OS/400side for each of your AS/400 Advanced 36 machines, go to “SSP SideVerification” on page 29-13 and verify the SSP Side.

6. If the status is ACTIVE or VARIED ON, and you installed a third AS/400Advanced 36 machine repeat these steps.

SSP Side VerificationFor each AS/400 Advanced 36 machine for which you set up ILAN communica-tions, do as follows:

1. On an SSP prompt on each AS/400 Advanced 36 machine, type

STATUS SUBSYS

Or,

D I

2. Press Enter .

3. Check the Line, Location name, and Communicating columns.

If the ILAN communications are started to a certain location on this AS/400Advanced 36 machine, there is a Y in the communicating column for thatLocation name.

Note: In this case, you have verified that communications are started. If pass-through works, the ILAN is completely functional. To find out how touse pass-through, go to “Using Display Station Pass-Through” onpage 29-15.

If there is an N in the communicating column, ILAN communications are notstarted on this AS/400 Advanced 36 machine for that Location name. Go to“Finding Out Why ILAN Is Not ACTIVE or VARIED ON” on page 29-13 forfurther directions.

Finding Out Why ILAN Is Not ACTIVE or VARIED ONIf you verified that your ILAN communications are not started on either the OS/400side or the SSP Side, do as follows:

1. Make sure the AS/400 Advanced 36 machines are started.

2. On an OS/400 command prompt, type

DSPMSG QSYSOPR

3. Press Enter to display messages sent to the OS/400 console.

4. If you are unable to correct the problem, look at messages on the SSPconsole.

5. Try setting up ILAN communications again for the AS/400 Advanced 36machine for which ILAN communications are not started.

Chapter 29. System-to-System Communications - ILAN Communications 29-13

Page 294: Iseries

ILAN Communications

| Recovery When Communications Were Not Disabled Before Stopping| an AS/400 Advanced 36 Machine

It is important to remember to disable communications before you power down orend each AS/400 Advanced 36 machine. The directions in this section tell you howto get your ILAN up and running again if you forgot to disable communications orwere unable to disable communications before you powered down or ended eachAS/400 Advanced 36 machine.

To recover,

1. Make sure all your AS/400 Advanced 36 machines are started.

2. Vary off each AS/400 APPC Controller Description as follows:

a. On an OS/400 command line, type

| VRYCFG QILANM36ðx \CTL \OFF

| where x is 1 for the first AS/400 Advanced 36 machine, 2 for the second| AS/400 Advanced 36 machine and 3 for the third AS/400 Advanced 36| machine.

| b. Press Enter to vary off the controller for the first AS/400 Advanced 36| machine on which you are doing recovery.

c. On an OS/400 command line, type

| VRYCFG QILANM36ðx \CTL \ON

| where x is 1 for the first AS/400 Advanced 36 machine, 2 for the second| AS/400 Advanced 36 machine and 3 for the third AS/400 Advanced 36| machine.

| d. Press Enter to vary on the controller for each AS/400 Advanced 36| machine on which you are doing recovery.

3. Disable and Enable ILAN communications for each AS/400 Advanced 36machine as follows:

a. On an SSP command line on each AS/400 Advanced 36 machine, type

DISABLE ILANSBS

b. Press Enter .

c. On an SSP command line on each AS/400 Advanced 36 machine, type

ENABLE ILANSBS,#CNFGLIB,15

d. Press Enter .

29-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 295: Iseries

ILAN Communications

Using Display Station Pass-Through

Running Display Station Pass-Through from OS/400 to SSPNote: You should not run Display Station Pass-Through from the OS/400 console.

To run Display Station Pass-Through from an OS/400 display station to SSP:

1. On an OS/400 command prompt, type

STRPASTHR IBMM36ðx

where IBMM360x is the control point name of the AS/400 Advanced 36machine that you want to pass through to.

If you set up your system as recommended:

� IBMM3601 is the control point name of the first AS/400 Advanced 36machine.

� IBMM3602 is the control point name of the second AS/400 Advanced 36machine.

� IBMM3603 is the control point name of the third AS/400 Advanced 36machine.

2. Press Enter .

The Display Status Passthru display appears briefly. Then, an SSP signondisplay appears.

3. After the signon display appears, sign-on and do the SSP operations you wantto do.

4. When completed with the operations, sign off as follows:

a. Type

OFF

b. Press Enter .

You return to the OS/400 command prompt.

Changing the QAUTOVRT ValueIf you want to pass through from an AS/400 Advanced 36 machine to OS/400,QAUTOVRT must be a number other than zero. To change this value, do asfollows:

1. On an OS/400 command line, type

CHGSYSVAL QAUTOVRT nnnn

| where nnnn is the number of virtual devices that can be auto-configured for| pass-through to OS/400.

2. Press Enter .

Chapter 29. System-to-System Communications - ILAN Communications 29-15

Page 296: Iseries

ILAN Communications

Running Pass-Through from SSP to OS/400Note: To use pass-through from SSP, you must install SSP Programming support

feature 6079: Display Station Pass-Through Support (DSPT).

To run pass-through from an SSP display station to OS/400:

1. On an SSP command line, type

PASSTHRU Sxxxxxxx

where xxxxxxx is the serial number of the AS/400 system if you are using theIBM-supplied control point name for OS/400.

2. Press Enter .

An OS/400 signon display appears.

3. Sign on and do the OS/400 operations you want to do.

4. When completed with the operations, sign off as follows:

a. Type

ENDPASTHR

b. Press Enter .

You return to the SSP command prompt.

For complete directions on using pass-through, see S/36 Using System/36 Commu-nications book, SC21-9082.

Running Pass-Through from SSP to SSPTo use pass-through from SSP, you must install SSP Programming support feature6079: Display Station Pass-Through Support (DSPT).

To run pass-through from an SSP display station to another AS/400 Advanced 36machine:

1. On an SSP command line, type

PASSTHRU IBMM36ðx

where IBMM360x is the control point name of the AS/400 Advanced 36machine that you want to pass through to.

If you set up your system as recommended:

� IBMM3601 is the control point name of the first AS/400 Advanced 36machine.

� IBMM3602 is the control point name of the second AS/400 Advanced 36machine.

� IBMM3603 is the control point name of the third AS/400 Advanced 36machine.

2. Press Enter .

An SSP signon display appears.

3. Sign on and do the SSP operations you want to do.

4. When completed with the operations, sign off as follows:

a. Type

29-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 297: Iseries

ILAN Communications

OFF

b. Press Enter .

| You return to the SSP command prompt.

For complete directions on using pass-through, see S/36 Using System/36 Commu-nications book, SC21-9082.

Chapter 29. System-to-System Communications - ILAN Communications 29-17

Page 298: Iseries

ILAN Communications

29-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 299: Iseries

Managing Machines and Configurations

Chapter 30. Using CL Commands to Manage AS/400Advanced 36 Configurations and Machines

There are fourteen CL commands that were developed specifically to help youmanage your AS/400 Advanced 36 machines. The two main commands are:

� Work with AS/400 Advanced 36 Machines (WRKM36)

� Work with AS/400 Advanced 36 Machine Configurations (WRKM36CFG)

Directions on how to use these two commands are included in this chapter. From| these two commands, you can use eleven of the other CL commands. The Start| AS/400 Advanced 36 Machine Procedure (STRM36PRC) command must be| entered from a command line or included in a CL program. Although directions on| using these other twelve CL commands are not included in this chapter, “Summary

Table of CL Commands for Managing AS/400 Advanced 36 Machines” onpage 30-13 tells you where the directions are included.

Note: You must have the proper authority to use these CL commands. For infor-mation, see the Security – Reference book, SC41-4302.

Using the Work with AS/400 Advanced 36 Machine CommandTo use the WRKM36 command, do as follows:

1. On an OS/400 command line, type

WRKM36

2. Press F4.

A display similar to the following appears.

à@ ðWork with Machines (WRKM36)

Type choices, press Enter.

Machine . . . . . . . . . . . . Name, generic\, \ALL Library . . . . . . . . . . . \LIBL Name, \LIBL, \CURLIB...

Figure 30-1. Work with Machines (WRKM36) display

3. In the Machine field, type

\ALL

4. In the Library field, type

\ALL

5. Press Enter .

A display similar to the following appears.

Copyright IBM Corp. 1995, 1996 30-1

Page 300: Iseries

Managing Machines and Configurations

à@ ðWork with M36 Machines

Type options, press Enter.1=Create 2=Change 4=Delete 5=Display 6=Print 7=Rename13=Change description 14=Start 15=End 16=Transfer

Opt M36 Library Status Description__ _________ _________ CHICAGO M361 Starting Branch Office in Chicago__ Test M363 Ended Test machine

If you prefer, instead of doing step 1 on page 30-1 through step 5 on page 30-1,you could do as follows:

1. On an OS/400 command line, type

WRKM36 \ALL/\ALL

2. Press Enter .

Creating An AS/400 Advanced 36 MachineYou can use the WRKM36 CL command to create an AS/400 Advanced 36machine.

Important Note

It is especially important that you make sure there is enough room on yoursystem for the AS/400 Advanced 36 machine before you try to create it. It ishighly recommended that you follow the directions in the Getting SSP andOS/400 Installed and Running book, SC21-8377 when you create an AS/400Advanced 36 machine.

To use the Work with M36 Machines display to create an AS/400 Advanced 36machine, you would:

1. In the Opt field, type

1

to select Create.

2. Press F4.

The Create Machine (CRTM36) display appears.

3. Type the necessary values.

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

4. Press Enter to create a new AS/400 Advanced 36 machine.

Note: Up to three AS/400 Advanced 36 machines are supported on each system.

30-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 301: Iseries

Managing Machines and Configurations

| You can also use the CRTM36 command to create an AS/400 Advanced 36| machine. For more information on using the CRTM36 command, see the CL Ref-| erence book, SC41-4722.

Changing Attributes for AS/400 Advanced 36 MachinesYou can use the WRKM36 CL command to change the attributes of AS/400Advanced 36 machines that have a status of ENDED, ABENDED, or INCOMPLETE.

To use the Work with M36 Machines display to change the attributes of an AS/400Advanced 36 machine, you would do as follows:

1. In the Opt field, type

2

to select Change.

2. Press Enter .

The Change Machine (CHGM36) display appears.

3. Type the necessary values.

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

4. Press Enter to change the attributes of the AS/400 Advanced 36 machine.

| You can also use the CHGM36 command to change the attributes of the AS/400| Advanced 36 machine. For more information on using the CHGM36 command, see| the CL Reference book, SC41-4722.

Attributes that you can change are:

� Automatic sign on

This parameter controls whether or not autosignon is allowed for this machine.

| If you change the Autosignon value to *ENABLE:

– Users automatically sign on if AUTOSIGNON(*YES) is specified on theTFRM36 command.

– Users are automatically signed on when they use the STRM36PRCcommand.

| If you change the Autosignon value to *DISABLE, the STRM36PRC command| will fail and users of the TFRM36 command will be required to sign on to SSP.

| For more information on using the STRM36PRC command, see “Transferring to| an AS/400 Advanced 36 Machine Using the STRM36PRC Command” on| page 14-6. For more information on using the TFRM36 command, see “Trans-| ferring to an AS/400 Advanced 36 Machine Using TFRM36” on page 14-3.

� Text 'description'

You can change the text that is used to describe the AS/400 Advanced 36machine. To do so, type a description in this field.

The description can contain up to 50 characters.

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-3

Page 302: Iseries

Managing Machines and Configurations

Deleting an AS/400 Advanced 36 MachineYou can use the WRKM36 CL command to delete an AS/400 Advanced 36machine which has a status of ENDED, ABENDED, or INCOMPLETE.

Important Note

If you delete an AS/400 Advanced 36 machine, you also delete all libraries,files, and folders that exist on that machine. All data on the machine is lost.

To use the Work with M36 Machines display to delete an AS/400 Advanced 36machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine that you want todelete, type

4

to select Delete.

2. Press Enter .

The Confirm Delete of Machine display appears.

3. To cancel the delete, press F12.

4. To delete the AS/400 Advanced 36 machine, press F2.

| You can also use the DLTM36 command to delete an AS/400 Advanced 36| machine. However, regardless of how you delete the machine, all of the libraries,| files, and folders that exist on that machine are lost. For more information on how

to use the DLTM36 command, see the CL Reference book, SC41-4722.

Displaying Information about an AS/400 Advanced 36 Machine and ItsConfiguration

You can use the WRKM36 CL command to display information about an AS/400Advanced 36 machine.

To use the Work with M36 Machines display to display information about anAS/400 Advanced 36 machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine that you want todisplay, type

5

to select Display.

| 2. Press Enter .

The Display M36 Machine display appears.

| 3. Type the necessary values. Select the option number for the information you| want to display.

If you are unsure what the options display, you can position the cursor on theoption and press F1.

| 4. Press Enter to display information about the AS/400 Advanced 36 machine.

30-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 303: Iseries

Managing Machines and Configurations

| You can also use the DSPM36 command to display information about an AS/400| Advanced 36 machine. For more information on how to use the DSPM36| command, see“Displaying a Machine” on page 32-2 .

Printing Information about an AS/400 Advanced 36 Machine and ItsConfiguration

You can use the WRKM36 CL command to print information about an AS/400Advanced 36 machine and its configuration.

To use the Work with M36 Machines display to print information about an AS/400Advanced 36 machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine that you want to printinformation about, type

6

to select Print.

2. Press F4.

| The Display Machine (DSPM36) display appears. *PRINT is placed in the| Output field for you. The information about the AS/400 Advanced 36 machine| will be printed. When the printing is complete, the following message appears| at the bottom of your display:

Object printed for machine-name in library-name type \M36.

where machine-name is the name of the AS/400 Advanced 36 machine andlibrary-name is the name of the library in which the AS/400 Advanced 36machine (object type *M36) is stored.

| You can also use the DSPM36 command to print information about an AS/400| Advanced 36 machine. For more information on how to use the DSPM36| command to print, see the CL Reference book, SC41-4722.

Renaming an AS/400 Advanced 36 machineYou can use the WRKM36 CL command to change the name of an AS/400Advanced 36 machine.

To use the Work with M36 Machines display to change the name of an AS/400Advanced 36 machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine that you want torename, type

7

to select Rename.

2. Press Enter .

The Rename Object (RNMOBJ) display appears.

There you can change the name of an object in a library. The new name spec-ified for the machine in the New object field must be unique in that library forobject type *M36. If the AS/400 Advanced 36 machine being renamed is inuse when you press Enter, the command is not run and a message is sent.

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-5

Page 304: Iseries

Managing Machines and Configurations

To rename any object, you must have object management authority for theobject. You must also have update authority and execute authority for thelibrary in which the object is located.

| You can also use the RNMOBJ command to change the name of an AS/400| Advanced 36 machine. For more information on how to use the RNMOBJ| command, see the CL Reference book, SC41-4722.

Changing the Description for an AS/400 Advanced 36 MachineYou can use the WRKM36 CL command to change the description of an AS/400Advanced 36 machine.

To use the Work with M36 Machines display to change the description of anAS/400 Advanced 36 machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine for which you want tochange the description, type

13

to select Change description.

2. Press Enter .

The Change Object Description (CHGOBJD) display appears.

3. Type the new description in the Text 'description' field.

The description can contain up to 50 characters.

4. Press Enter to rename the AS/400 Advanced 36 machine.

| You can also use the CHGOBJD and the CHGM36 CL commands to change the| description of an AS/400 Advanced 36 machine. For more information on how to| use these commands, see the CL Reference book, SC41-4722.

Starting an AS/400 Advanced 36 MachineYou can use the WRKM36 CL command to start an AS/400 Advanced 36 machine.

To use the Work with M36 Machines display to start an AS/400 Advanced 36machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine that you want to start,type

14

to select Start.

| 2. Press Enter twice.

An initial program load (IPL) of the specified AS/400 Advanced 36 machine objectoccurs which starts the AS/400 Advanced 36 machine.

| You can also use the STRM36 command to start an AS/400 Advanced 36 machine.| For more information on how to use the STRM36 command, see Chapter 15,

“Starting an AS/400 Advanced 36 Machine.”

30-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 305: Iseries

Managing Machines and Configurations

Ending an AS/400 Advanced 36 Machine| You can use the WRKM36 CL command to abnormally end an AS/400 Advanced

36 machine.

Important Note

This option immediately ends the specified AS/400 Advanced 36 machinewithout allowing any programs running in the AS/400 Advanced 36 machine toperform any cleanup.

| To use the Work with M36 Machines display to abnormally end an AS/400Advanced 36 machine, you would do as follows:

| 1. In the Opt field beside the AS/400 Advanced 36 machine that you want to| abnormally end, type

15

to select End.

2. Press F4.

The End Machine (ENDM36) display appears.

| 3. If the machine is being ended because of a problem and you want to collect| information about the problem, in the Dump the machine field, type

\YES

4. Press Enter .

If you are unsure what the other fields are used for, you can position the cursoron each field and press F1.

| 5. Press Enter to abnormally end the AS/400 Advanced 36 machine.

| You can also use the End AS/400 Advanced 36 Machine (ENDM36) command to| abnormally end an AS/400 Advanced 36 machine. For more information on how to

use the ENDM36 command and the restrictions and alternatives to using thatcommand, see “Stopping an AS/400 Advanced 36 Machine from the OS/400 Oper-ating System” on page 16-3.

Transferring to an AS/400 Advanced 36 MachineYou can use the WRKM36 CL command to transfer to an AS/400 Advanced 36machine.

To use the Work with M36 Machines display to transfer to an AS/400 Advanced 36machine, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine to which you want totransfer this display station, type

16

to select Transfer.

2. Press F4.

The Transfer to Machine (TFRM36) display appears.

3. Type the necessary values.

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-7

Page 306: Iseries

WRKM36CFG

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

| 4. Press Enter .

| More fields are shown.

| 5. Type the values in those fields that apply.

| 6. Press Enter .

| The display is transferred to the specified AS/400 Advanced 36 machine.

| You can also use the Transfer AS/400 Advanced 36 Machine (TFRM36) command| to transfer to an AS/400 Advanced 36 machine. For more information on how to| use the TFRM36 command see Chapter 14, “Transferring to an AS/400 Advanced

36 Machine.”

Using the Work with AS/400 Advanced 36 Machine ConfigurationCommand

To use the WRKM36CFG command, do as follows:

1. On an OS/400 command line, type

WRKM36CFG

2. Press F4.

A display similar to the following appears.

à@ ðWork with Machine Config (WRKM36CFG)

Type choices, press Enter.

Machine configuration . . . . . Name, generic\, \ALL Library . . . . . . . . . . . \LIBL Name, \LIBL, \CURLIB...

Figure 30-2. Work with Machines (WRKM36CFG) display

3. In the Machine configuration field, type

\ALL

4. In the Library field, type

\ALL

5. Press Enter .

A display similar to the following appears.

30-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 307: Iseries

WRKM36CFG

à@ ðWork with AS/4ðð Advanced 36 Machine Configurations

Type options, press Enter.1=Create 2=Change 4=Delete 5=Display 6=Print 7=Rename

13=Change description

M36Opt Configuration Library Text

| __ M36 M36 The configuration for the first machine__ MYM36 MYLIB

| __ TEST TESTLIB A configuration used for testing

If you prefer, instead of doing step 1 through step 5, you could do as follows:

1. On an OS/400 command line, type

WRKM36CFG \ALL/\ALL

2. Press Enter .

Creating an AS/400 Advanced 36 Machine ConfigurationYou can use the WRKM36CFG CL command to create an AS/400 Advanced 36machine configuration. Up to three AS/400 Advanced 36 machines are supportedon each system. However, you can have as many configurations as you want.

Note: A configuration must be applied to an AS/400 Advanced 36 machine usingthe APYM36CFG parameter on the STRM36 command before it affects anAS/400 Advanced 36 machine.

To use the Work with Machine Config (WRKM36CFG) display to create an AS/400Advanced 36 machine configuration, you would do as follows:

1. In the Opt field on the top line beside the blank line, type

1

to select Create.

2. Press F4.

The Create AS/400 Advanced 36 Machine Configuration (CRTM36CFG) displayappears.

3. Type the necessary values.

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

4. Press Enter to create a new AS/400 Advanced 36 machine configuration.

An AS/400 Advanced 36 machine configuration is similar to a configuration memberon a System/36.

| When creating a new AS/400 Advanced 36 machine configuration, you can specify| an existing AS/400 Advanced 36 machine or an existing AS/400 Advanced 36

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-9

Page 308: Iseries

WRKM36CFG

| machine configuration whose configuration information should be copied. If you donot specify a from object, you must supply all of the configuration information.

If you run the command interactively, a series of displays are shown which supplyconfiguration information. If you specified a from object, these displays show thecopied configuration information. You can change this configuration information orleave it as it is.

The configuration defines the attributes to be used for an AS/400 Advanced 36machine. When the configuration is applied to an AS/400 Advanced 36 machine, acopy of those attributes are stored in the *M36 object. This is done using theAPYM36CFG parameter with the Start AS/400 Advanced 36 Machine (STRM36)command.

It is acceptable to create an empty configuration. However, an AS/400 Advanced36 machine to which an empty configuration is applied will fail to start.

| You can also use the CRTM36CFG command to create an AS/400 Advanced 36| machine configuration. For more information on using the CRTM36CFG command,| see the CL Reference book, SC41-4722.

Changing Attributes and Configuration Details for an AS/400 Advanced36 Machine Configuration

You can use the WRKM36CFG CL command to change the attributes and config-uration details of an AS/400 Advanced 36 machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to change the attri-butes of an AS/400 Advanced 36 machine configuration, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine configuration that youwant to change, type

2

to select Change.

2. Press Enter .

The Change Machine Configuration (CHGM36CFG) display appears.

3. Type the necessary values.

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

4. Press Enter to change the AS/400 Advanced 36 machine configuration.

| You can also use the CHGM36CFG command to change the attributes and config-| uration details of an AS/400 Advanced 36 machine configuration. For more infor-| mation on using the CHGM36CFG command, see Chapter 31, “Changing Your| AS/400 Advanced 36 Machine Configuration” and the CL Reference book,| SC41-4722.

30-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 309: Iseries

WRKM36CFG

Deleting an AS/400 Advanced 36 Machine ConfigurationYou can use the WRKM36CFG CL command to delete an AS/400 Advanced 36machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to delete an AS/400Advanced 36 machine configuration, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine configuration that youwant to delete, type

4

to select Delete.

2. Press Enter .

The Confirm Delete of M36 Machine Configuration display appears.

3. If you want to cancel the delete, press F12.

4. If you want to continue with the delete, press Enter .

If you delete an AS/400 Advanced 36 machine configuration object, you do notaffect the AS/400 Advanced 36 machine to which it was applied. The AS/400Advanced 36 machine has its own copy of the last configuration applied to it.

| You can also use the DLTM36CFG command to delete an AS/400 Advanced 36| machine configuration. For more information on how to use the DLTM36CFG| command, see the CL Reference book, SC41-4722.

Displaying an AS/400 Advanced 36 Machine ConfigurationYou can use the WRKM36CFG CL command to display information about anAS/400 Advanced 36 machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to display informationabout an AS/400 Advanced 36 machine configuration, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine for which you want todisplay information, type

5

to select Display.

2. Press F4.

The Display M36 Configuration display appears.

You can choose other options that allow you to see information about the con-figuration.

3. Type a number in the Opt field.

If you are unsure what an option is used for, you can position the cursor on theoption and press F1.

4. Press Enter to display information about an AS/400 Advanced 36 machine.

| You can also use the DSPM36CFG command to display information about an| AS/400 Advanced 36 machine configuration. For more information on how to use| the DSPM36CFG command, see“Displaying a Configuration” on page 32-1 .

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-11

Page 310: Iseries

WRKM36CFG

Printing an AS/400 Advanced 36 Machine ConfigurationYou can use the WRKM36CFG CL command to print the AS/400 Advanced 36machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to print the AS/400Advanced 36 machine configuration, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine configuration that youwant to print, type

6

to select Print.

2. Press Enter .

When printing is complete, the following message appears at the bottom ofyour display:

Object printed for configuration-name in library-name type \M36CFG.

where configuration-name is the name of the AS/400 Advanced 36 machineconfiguration and library-name is the name of the library in which the AS/400Advanced 36 machine configuration (object type *M36CFG) is stored.

| You can also use the DSPM36CFG command to print information about an AS/400| Advanced 36 machine configuration. For more information on how to use the| DSPM36CFG command to print, see the CL Reference book, SC41-4722.

Renaming an AS/400 Advanced 36 Machine ConfigurationYou can use the WRKM36CFG CL command to change the name of an AS/400Advanced 36 machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to change the nameof an AS/400 Advanced 36 machine configuration, you would do as follows:

1. In the Opt field beside the AS/400 Advanced 36 machine configuration that youwant to rename, type

7

to select Rename.

2. Press Enter .

The Rename Object (RNMOBJ) display appears.

The new name specified for the machine configuration in the New object fieldmust be unique in that library for AS/400 Advanced 36 machine configurations.

3. Type the necessary values.

If you are unsure what a field is used for, you can position the cursor on thefield and press F1.

4. Press Enter to change the name of the AS/400 Advanced 36 machine config-uration.

To rename any object, you must have object management authority for theobject. You must also have update authority and execute authority for thelibrary in which the object is located.

30-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 311: Iseries

CL Command Summary Table

| You can also use the RNMOBJ command to rename an AS/400 Advanced 36| machine configuration. For more information on how to use the RNMOBJ| command, see the CL Reference book, SC41-4722.

Changing the Description for an AS/400 Advanced 36 MachineConfiguration

You can use the WRKM36CFG CL command to change the description of anAS/400 Advanced 36 machine configuration.

To use the Work with Machine Config (WRKM36CFG) display to change thedescription of an AS/400 Advanced 36 machine configuration, you would do asfollows:

1. In the Opt field beside the AS/400 Advanced 36 machine configuration youwant to change, type

13

to select Change description.

2. Press Enter .

The Change Object Description (CHGOBJD) display appears.

3. Type the new description in the Text 'description' field.

The description can contain up to 50 characters.

| You can also use the CHGOBJD and CHGM36CFG commands to change the| description of the AS/400 Advanced 36 machine configuration. For more informa-| tion on how to use these commands, see the CL Reference book, SC41-4722.

Summary Table of CL Commands for Managing AS/400 Advanced 36Machines

The Figure 30-3 table includes the CL commands used only to manage AS/400Advanced 36 machines, text which describes what each command does, and a ref-erence to where specific information is found on how to use each command.

Figure 30-3 (Page 1 of 3). AS/400 Advanced 36 Machine - CL Commands

CL Command Description Reference

CHGM36 Change AS/400 Advanced 36 Machine: Allows youto change attributes for a machine.

14-5

CHGM36CFG Change AS/400 Advanced 36 MachineConfiguration: Allows you to change an AS/400Advanced 36 machine configuration. The config-uration can be applied to an AS/400 Advanced 36machine. Once applied, the configuration of theAS/400 Advanced 36 machine is changed.

Chapter 31,“Changing YourAS/400Advanced 36MachineConfiguration”

CRTM36 Create AS/400 Advanced 36 Machine: Allows youto create an AS/400 Advanced 36 machine.

CL Referencebook,SC41-4722.

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-13

Page 312: Iseries

CL Command Summary Table

Figure 30-3 (Page 2 of 3). AS/400 Advanced 36 Machine - CL Commands

CL Command Description Reference

CRTM36CFG Create AS/400 Advanced 36 MachineConfiguration: Allows you to create an AS/400Advanced 36 machine configuration. You canapply the configuration to any AS/400 Advanced 36machine using the STRM36 command.

CL Referencebook,SC41-4722.

DLTM36 Delete an AS/400 Advanced 36 Machine: Allowsyou to delete an AS/400 Advanced 36 machine andall of the libraries, files, and folders that exist onthat machine.

CL Referencebook,SC41-4722.

DLTM36CFG Delete an AS/400 Advanced 36 MachineConfiguration: Allows you to delete an AS/400Advanced 36 machine configuration. This does notaffect any AS/400 Advanced 36 machine to which itwas applied.

CL Referencebook,SC41-4722.

DSPM36 Display AS/400 Advanced 36 Machine: Allows youto display information about an AS/400 Advanced36 machine.

“Displaying aMachine” onpage 32-2

DSPM36CFG Display AS/400 Advanced 36 MachineConfiguration: Allows you to display informationabout a configuration object that you can apply toan AS/400 Advanced 36 machine.

“Displaying aConfiguration”on page 32-1

ENDM36 End AS/400 Advanced 36 Machine: Used to stopan AS/400 Advanced 36 machine when it cannotbe stopped by other means.

“Stopping anAS/400Advanced 36Machine fromthe OS/400OperatingSystem” onpage 16-3

STRM36 Start AS/400 Advanced 36 Machine: Allows you tostart an AS/400 Advanced 36 machine.

Chapter 15,“Starting anAS/400Advanced 36Machine”

STRM36PRC Start AS/400 Advanced 36 Machine Procedure:Allows you to start an SSP procedure from anOS/400 command line for a specific AS/400Advanced 36 machine. If you want access to anAS/400 Advanced 36 machine to do more than run

| a procedure, you should use the TFRM36 or| STRPASTHR commands.

“Transferring toan AS/400Advanced 36Machine UsingtheSTRM36PRCCommand” onpage 14-6

TFRM36| Transfer to AS/400 Advanced 36 Machine: Allowsyou to transfer from an OS/400 display station toan SSP display station for a specific AS/400Advanced 36 machine. If you want access to anAS/400 Advanced 36 machine to just run a proce-dure, you could use the STRM36PRC command.

Chapter 14,“Transferring toan AS/400Advanced 36Machine”

WRKM36 Work with AS/400 Advanced 36 Machines: Allowsyou to work with all of your AS/400 Advanced 36machines at the same time.

This chapter

30-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 313: Iseries

CL Command Summary Table

Note: For additional information on any of these commands, type the commandon an OS/400 command line and press F4, or see the CL Reference book,SC41-4722.

Figure 30-3 (Page 3 of 3). AS/400 Advanced 36 Machine - CL Commands

CL Command Description Reference

WRKM36CFG Work with AS/400 Advanced 36 MachineConfiguration: Allows you to work with all the con-figurations that can be applied to an AS/400Advanced 36 machine.

This chapter

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-15

Page 314: Iseries

CL Command Summary Table

30-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 315: Iseries

Configuration

Chapter 31. Changing Your AS/400 Advanced 36 MachineConfiguration

You use the Change AS/400 Advanced 36 Machine Configuration (CHGM36CFG)command to change the configuration of an AS/400 Advanced 36 machine. Thechanges you make to the configuration only affect an AS/400 Advanced 36machine after you use the Apply AS/400 Advanced 36 Machine Configuration(APYM36CFG) parameter on the Start AS/400 Advanced 36 Machine (STRM36)command. Using the APYM36CFG parameter on the STRM36 command appliesthe updated configuration information to the AS/400 Advanced 36 machine. Thechanges will not affect an AS/400 Advanced 36 machine until you do this.

This chapter provides instructions on how to change your AS/400 Advanced 36configuration. The information includes instructions on:

� “Defining a Communications Line or a LAN” on page 31-4.

� “Defining a Diskette Device” on page 31-8.

� “Defining a Tape or CD-ROM Device” on page 31-10.

� “Defining Printers and Display Stations Using Device Mapping” on page 31-12.

� “Defining Printers and Display Stations Using Controller Mapping” onpage 31-17.

� “Changing a Workstation Controller from Controller Mapping to DeviceMapping” on page 31-22.

� “Defining Whether SSP or OS/400 Controls SSP Printer Output” onpage 31-26.

– “Giving SSP Control of AS/400 Advanced 36 Machine Printer Output” onpage 31-26.

– “Giving OS/400 Control of AS/400 Advanced 36 Machine Printer Output” onpage 31-30.

– “Giving OS/400 Control of Printer Output When There Is No PhysicalPrinter” on page 31-32.

� “Defining Whether SSP or OS/400 Controls the Display Station” onpage 31-36.

Note: The configuration changes in the previous list require no additional changesin the SSP operating system.

You might want to do additional work with your AS/400 Advanced 36 machine con-figuration by using the CNFIGSSP procedure to edit a configuration member. Thetasks you can do include:

� Defining what kind of communication line is attached.

� Assigning printers to display stations (default printers).

� Assigning display stations (subconsoles) that will control printers.

� Changing workstation IDs for display stations and printers.

� Changing the characteristics of display stations and printers.

� Changing the system printer.

Copyright IBM Corp. 1995, 1996 31-1

Page 316: Iseries

Configuration

� Adding, replacing or deleting remote service devices.

� Printing a configuration member.

� Applying the member to the master configuration record.

� Using the Configuration Support Aids.

Note: For instructions on making these additional changes to your configuration,see the Changing Your System Configuration–SSP book, SC21-8295. Allcommands must be entered from the console of the AS/400 Advanced 36machine for which you want to make configuration changes.

Configuration That Exists Immediately after Installation

OS/400 Added to a System That Previously Was SSP OnlyIf your system was previously an SSP-only system and you added OS/400 to it,then the configuration of your AS/400 Advanced 36 machine is exactly the same asthe configuration of your system before you added OS/400:

� When the SSP refers to T1, T2, TC, I1, and communications lines 1-10, it willrefer to the same physical resources as it did before OS/400 was added.

� When the SSP refers to its workstation controllers and the displays and printersattached to them, it will refer to the same physical workstation controllers andthe devices attached to them at the same physical ports and addresses as itdid before OS/400 was added.

There is one exception. It will normally be the case that the OS/400system console display is attached to the same physical workstation con-troller as appears to be workstation controller 1 to the AS/400 Advanced 36machine. When this is the case, then to prevent both OS/400 and SSPfrom trying to use the same display station as their system consoles, theremust be another display station physically attached to port 0 address 1.This display station will appear to the SSP operating system to be at port 0address 0. It is therefore the SSP system console. The display stationphysically cabled at port 0 address 0 will be the OS/400 system console,and if it were to be transferred into the AS/400 Advanced 36 machine, itwould appear to be at port 0 address 1.

In addition, the workstations will have the following attributes:

– Workstation controllers use controller mapping, not device mapping. Thismeans that entire physical workstation controllers are mapped to entirelogical workstation controllers on the AS/400 Advanced 36 machine. If youcable new displays or printers to the workstation controller, those deviceswill auto-configure into the master configuration record of the AS/400Advanced 36 machine.

– All display stations on mapped controllers will be automatically acquired bythe AS/400 Advanced 36 machine when it is started. The only exception tothis will be the display station which is the OS/400 console. That devicewill never be automatically acquired.

| – By default, printed output will not be routed to an OS/400 Output Queue| (OUTQ). All printed output will be printed directly from the SSP, either

spooled or non-spooled, unless overridden within the SSP by using theOUTQ parameter on the // PRINTER OCL statement.

31-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 317: Iseries

Configuration

| � An AS/400 Advanced 36 machine configuration object also reflects the config-| uration of your AS/400 Advanced 36 machine. This object has the same name

and is in the same library as your AS/400 Advanced 36 machine object.

OS/400 and SSP Preloaded from IBM ManufacturingIf your system was ordered with both OS/400 and SSP, the preloaded AS/400Advanced 36 machine shipped from IBM manufacturing came with the same config-uration as your system would have had if it had been an SSP-only system:

� When the SSP refers to TC, it will refer to the 1/4" or 8mm tape cartridge. Ifthere is more than one such resource, it will refer to the one with the lowestaddress on the system bus.

| Note: You can change the configuration to include the CD-ROM drive as atape drive.

� When the SSP refers to T1 or T2, it will refer to the 1/2" tape cartridge or reeldevices. T1 will refer to the one with the lowest address on the system bus,and T2 to the one with the second-lowest address on the system bus.

If you have 1/2" tape devices, it is possible the devices may not be included inthe configuration. This would be true if they were added to your system afterthe configuration was established in the manufacturing process. If this is thecase, you may change the configuration to add them yourself.

| Note: You can change the configuration to include the CD-ROM drive as atape drive.

� When the SSP refers to I1, it will refer to the diskette drive which has thelowest address on the system bus. It is possible that the diskette drive may notbe included in your configuration. This would be true if it was added after theconfiguration was established in the manufacturing process. If this is the case,you may change the configuration to add it yourself.

| � When the SSP refers to communications lines 1-8, it will refer to the commu-| nications ports which:

| – Support the Async, Bisync, SDLC, X.21 Short Hold Mode, or X.25 commu-nications methods

| And,

– Have the lowest addresses on the system bus respectively.

You might need to change the configuration to associate different SSP commu-nications lines with different communication port resources.

When the SSP refers to communications lines 9 and 10, it will refer to thetoken ring port resources which have the lowest addresses on the system busrespectively. You may need to change the configuration to associate differentSSP communications lines with different communications port resources.

| � When the SSP refers to its workstation controllers (1-4), it uses controller| mapping, and refers to the physical workstation controllers which have the| lowest addresses on the system bus respectively. It refers to the displays and

printers attached to those workstation controllers by their physical ports andaddresses.

There is one exception. It will normally be the case that the OS/400system console display is attached to the same physical workstation con-troller as appears to be workstation controller 1 to the AS/400 Advanced 36

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-3

Page 318: Iseries

Configuration

machine. When this is the case, then to prevent both OS/400 and SSPfrom trying to use the same display station as their system consoles, theremust be another display station physically attached to port 0 address 1.This display station will appear to the SSP to be at port 0 address 0, andwill be the SSP system console. The display station physically cabled atport 0 address 0 will be the OS/400 system console, and if it were to betransferred into the AS/400 Advanced 36 machine, it would appear to be atport 0 address 1.

In addition, the workstations will have the following attributes:

– Workstation controllers use controller mapping, not device mapping. Thismeans that entire physical workstation controllers are mapped to entirelogical workstation controllers on the AS/400 Advanced 36 machine. If youcable new displays or printers to the workstation controller, those deviceswill auto-configure into the master configuration record of the AS/400Advanced 36 machine.

– All display stations on mapped controllers will be automatically acquired bythe AS/400 Advanced 36 machine when it is started. The only exception tothis will be the display station which is the OS/400 console. That devicewill never be automatically acquired.

| – By default, printed output will not be routed to an OS/400 Output Queue| (OUTQ). All printed output will be printed directly from the SSP, either

spooled or non-spooled, unless overridden within the SSP by using theOUTQ parameter on the // PRINTER OCL statement.

| � An AS/400 Advanced 36 machine configuration object also reflects the config-| uration of your AS/400 Advanced 36 machine. This object has the same name

and is in the same library as your AS/400 Advanced 36 machine object.

| If for any type of device, you have more physical resources than the AS/400| Advanced 36 machine can use, then you may change the AS/400 Advanced 36| machine configuration object to configure resources other than those which were

configured for you by default. You must apply that configuration when you start theAS/400 Advanced 36 machine.

Defining a Communications Line or a LANIf you are connecting your AS/400 system to external communications you will needto physically connect the hardware. After you set up the hardware, add the com-munications line as directed in this section.

To add, change, or delete an AS/400 Advanced 36 machine communications line,do as follows:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

31-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 319: Iseries

Configuration

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. In the Selection field, type

6

to select Change M36 communication lines.

8. Press Enter .

The Change M36 Communication Lines display appears.

You can specify up to 10 communication lines. Lines 1 through 8 can be usedfor any of the following communications methods: Async, Bisync, SDLC, X.21Short Hold Mode, or X.25. Lines 9 and 10 can be used for Token Ring con-nections. Directions for setting up token-ring connections are in the LAN andFrame Relay Support book, SC41-3404. You should follow the example for theSystem/36 when setting-up the token-ring connection for an AS/400 Advanced36 machine.

9. If you want to add or replace a communication line, type the Resource Nameof the desired AS/400 communication port in the AS/400 CommunicationResource column by the line number in the M36 Communication Line column.Or, do one of the following:

a. Press F10 to have the system select the communication port resources foryou. The ports selected will be the same ones that would be used by SSPif OS/400 were not installed.

b. Use F4 to prompt, as follows:

1) Move the cursor to the entry in the AS/400 Communication Resourcecolumn corresponding to the desired line number.

2) Press F4 to see a list of the Resource Names that can be used for thatcommunication line.

3) Next to the name you want to select for the communication line, type

1

4) Press Enter .

10. If you want to delete a resource, use the space bar to space over the name ofthe resource with blanks.

11. Press Enter .

You return to the Change M36 Configuration display.

12. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

13. If you need to make any configuration changes, return to step 7 on page 31-5.

You may choose to make other changes as described in other sections of thischapter before exiting.

14. To save and exit,

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-5

Page 320: Iseries

Configuration

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

15. When you set up communications lines, follow the System/36 directions in theappropriate books:

Communications Protocol SSP Book Reference

Async S/36 Using the Asynchronous Communications Supportbook, SC21-9143.

Bisync S/36 Using System/36 Communications book,SC21-9082.

SDLC S/36 Using System/36 Communications book,SC21-9082.

X-21 short-hold mode S/36 Using System/36 Communications book,SC21-9082.

X-25 S/36 Using System/36 Communications book,SC21-9082.

Token-Ring S/36 Using System/36 Communications book,SC21-9082.

APPN S/36 Advanced Peer-to-Peer Networking (APPN) Guidebook, SC21-9471.

Some types of communications are allowed from OS/400 or from an AS/400Advanced 36 machine. However, you must set up ILAN to use these types of com-munications from an AS/400 Advanced 36 machine. Additionally, you must set upAPPN for all of these communications types except Apple Talk. These types ofcommunications are:

Communications Type Book References

Wireless LAN and Frame Relay Support book, SC41-3404.

Ethernet LAN and Frame Relay Support book, SC41-3404.

ISDN ISDN Support book, SC41-4403.

31-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 321: Iseries

Configuration

Frame Relay LAN and Frame Relay Support book, SC41-3404.

FDDI (DDI) LAN and Frame Relay Support book, SC41-3404.

Apple Talk LAN and Frame Relay Support book, SC41-3404.

Directions for setting up ILAN are included in Chapter 4 of the Getting SSP andOS/400 Installed and Running book, SC21-8377.

| The following type of communications can be done from OS/400 or from an AS/400Advanced 36 machine. However, you must send the AS/400 Advanced 36machine printer output to an OS/400 output queue to use the following type ofcommunications:

Communications Type Book References

Fax Local Device Configuration book, SC41-4121.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-7

Page 322: Iseries

Configuration

Defining a Diskette DeviceTo add, change, or delete a diskette device, do as follows:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. In the Selection field, type

5

to select Change M36 diskette devices

8. Press Enter .

The Change M36 Diskette Devices display appears.

The AS/400 Advanced 36 system supports only one diskette device. Thatdevice is known to the SSP operating system as I1. Any diskette devicedescription name can be specified for I1.

9. If you want to add a device or replace a device, type the name of the device inthe AS/400 Diskette Device column. Or, do one of the following:

a. Press F10 to have the system select the diskette drive for you. The deviceit selects is the same device the SSP operating system would select ifOS/400 was not installed.

b. Use F4 to prompt, as follows:

1) Press F4 to see a list of the diskette device names that can be used forI1.

2) Next to the device you want to use, type

1

3) Press Enter .

10. If you want to delete the device, use the space bar to space over the devicename.

11. Press Enter .

You return to the Change M36 Configuration display.

12. Press F19 to validate your changes.

31-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 323: Iseries

Configuration

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

13. If you need to make any configuration changes, return to step 7 on page 31-8.

You may choose to make other changes as described in other sections of thischapter before exiting.

14. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-9

Page 324: Iseries

Configuration

Defining a Tape or CD-ROM DeviceTo add, change, or delete a tape or CD-ROM device, do as follows:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. In the Selection field, type

4

to select Change M36 tape and optical devices.

8. Press Enter .

The Change M36 Tape and Optical Dev display appears.

The AS/400 Advanced 36 machine supports only three tape devices. Theseare known to the SSP operating system by the following device-IDs: T1, T2,and TC.

9. If you want to add or replace a tape or CD-ROM device, type the device-namein the AS/400 Tape or Optical Device column by the tape device-ID in the M36Tape Device column. Or, do one of the following:

a. Press F10 to have the system select the tape drives for you. The devicesit selects are the same devices the SSP operating system would select ifthe OS/400 operating system was not installed.

b. Use F4 to prompt, as follows:

1) Move the cursor to the entry in the AS/400 Tape or Optical Devicecolumn that corresponds to the device ID.

2) Press F4 to see a list of the tape and CD-ROM devices that can beused for that device-ID.

3) Next to the device you want to use, type

1

4) Press Enter .

10. If you want to delete a tape or CD-ROM device, use the space bar to spaceover the tape device-ID with blanks.

11. Press Enter .

You return to the Change M36 Configuration display.

31-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 325: Iseries

Configuration

12. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

13. If you need to make any configuration changes, return to step 7 onpage 31-10.

You may choose to make other changes as described in other sections of thischapter before exiting.

14. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-11

Page 326: Iseries

Configuration

Defining Printers and Display Stations Using Device MappingThis section assumes you have physically connected the hardware and defined theprinters and display stations to OS/400.

SSP supports a maximum of four workstation controllers. For this reason, anAS/400 Advanced 36 machine supports only four workstation controllers. However,since the AS/400 Advanced 36 machine's workstation controllers are logical andnot physical, you can map any display station or printer on any physical controllerto any AS/400 Advanced 36 machine workstation controller using device mapping.

Note: You can also choose to map an entire physical controller (including all ofthe printers and display stations attached to the physical controller) to aspecific workstation controller on an AS/400 Advanced 36 machine. This iscalled controller mapping. For directions on controller mapping, see“Defining Printers and Display Stations Using Controller Mapping” onpage 31-17.

Device mapping does not map an AS/400 Advanced 36 machine's workstation con-troller to a physical controller. Instead, the AS/400 Advanced 36 machine work-station controller is a logical workstation controller with physical display stations andprinters mapped to its logical ports and addresses. This is done without regard tothe physical controllers, ports, and addresses to which the devices are cabled.

The display station you map to port 0 address 0 of workstation controller 1 will bethe SSP system console. Other than that, you can map devices to any ports andaddresses. All fifty-six port and address combinations of each logical workstationcontroller may have a display station or printer mapped to them. All fifty-six can beused at the same time. The devices you map to each logical workstation controller

| will auto-configure into the SSP master configuration record at the ports andaddresses you specify.

To add , replace or delete a printer or display station using device mapping, do asfollows:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. In the Selection field, type

2

to select Change M36 display and printer devices.

31-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 327: Iseries

Configuration

8. Press Enter .

The Chg M36 Display and Printer Dev display appears.

9. To do device mapping of the local devices, do one of the following.

� If the workstation controller is already configured with device mapping:

a. Move the cursor to the line that corresponds to the workstation con-troller number (1-4).

Note: If it is already configured with device mapping, the line is filledin already with *DEV.

b. Go to step 10.

� To configure a new workstation controller with device mapping and addworkstation devices to it:

a. Move the cursor to the blank line that corresponds to the new work-station controller number (1-4).

| Note: If it is not configured, the line is blank.

b. Type *DEV on the line.

c. Go to step 10 to add the workstation devices.

� To change a workstation controller from controller mapping to devicemapping and map workstation devices to it:

a. Move the cursor to the line that corresponds to the workstation con-troller number (1-4).

Note: If the workstation controller is mapped with controller mapping,the line is filled in with an OS/400 Workstation ControllerDescription.

b. Type *DEV over the name.

After you have applied this configuration to your AS/400 Advanced 36machine, you may want to use the CNFIGSSP procedure to removeprinters or display stations that are no longer part of the AS/400Advanced 36 machine configuration from the master configurationrecord.

Note: Before you type over the controller name, you may want to savethe attributes. For directions, see “Changing a WorkstationController from Controller Mapping to Device Mapping” onpage 31-22.

c. Go to step 10 to add the workstation devices.

� To remove a workstation controller from the configuration:

a. Move the cursor to the line that corresponds to the workstation con-troller number (1-4).

b. Blank out the line.

After you have applied this configuration to your AS/400 Advanced 36machine, you may want to use the CNFIGSSP procedure to removethe display stations and printers associated with this workstation con-troller from the master configuration record.

c. Go to step 12 on page 31-15.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-13

Page 328: Iseries

Configuration

10. Press F21 to define the mappings of individual printers and display stations.

A grid with rows of ports and columns of addresses is shown for the work-station controller you specified. Each entry in the grid can contain the name ofa device description for the printer or display station that you want configured atthe corresponding port and address. You may use either or both of the fol-lowing techniques to configure display stations and printers:

� Technique 1

You may choose to use a physical OS/400 workstation controller as thebasis for the AS/400 Advanced 36 machine's workstation controller. If youdo this, all display stations and printers currently attached to that controllerwill be configured at the same ports and addresses to which they are phys-ically cabled. You can change the configuration afterwards.

To use this technique:

a. Press F16 (Autofill from controller).

The Select AS/400 Work Station Ctlr display overlays the Chg M36Display and Printer Dev display.

b. In the Opt field on the line with the name of the AS/400 workstationcontroller that contains the devices you want automatically filled in forthe AS/400 Advanced 36 machine's workstation controller, type

1

Note: F11 works as a toggle to allow you to see the controller namesand their descriptions or to see just controller names. Selectingjust controller names allows you to see more choices on asingle display. If necessary, you can use Page Down to seemore controller names.

c. Press Enter .

The Select AS/400 Work Station Ctlr display is replaced by the ChgM36 Display and Printer Dev display. This display is automatically filledin with the devices that are physically connected to the controller youchose.

If you are working with the AS/400 Advanced 36 machine's workstationcontroller 1 and you auto-filled it from the AS/400 workstation controllerthat contains the OS/400 system console, the devices at port 0addresses 0 and 1 were switched when they were filled in.

Notes:

1) If the OS/400 system console is physically cabled to port 0 address0, it will appear at port 0 address 1 in the display.

2) The device physically cabled to port 0 address 1 will appear in thedisplay at port 0 address 0, and will be the SSP system console.

3) Unless you change the mapping of these devices, the SSP oper-ating system acts as if they are at the ports and addresses you seeon the display instead of at the ports and addresses to which theyare physically cabled.

d. If you do not want to change the configuration of the workstation con-troller you just auto-filled, continue with step 11.

e. Otherwise, continue with Technique 2.

31-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 329: Iseries

Configuration

� Technique 2

You can add or replace a device at a particular port and address by typingthe desired device description name at the desired port and address. Youcan remove a device from a particular port and address by spacing over itsname with blanks.

Note the following considerations for device mapping:

– The display stations and printers you include in the configuration mustbe locally attached twinax or ASCII devices.

Note: Locally attached ASCII printers may only be configured asoutput queues. For information on how to configure theseprinters, see “Giving OS/400 Control of AS/400 Advanced 36Machine Printer Output” on page 31-30.

– The display stations and printers must be known to OS/400. They canbe cabled to any AS/400 workstation controller, at any port and

| address. The display stations can be any sessions of a multi-sessiondevice.

For information on restrictions on using the multi-session devices, seethe General Information for SSP Operating System book, SC21-8299.

| – To ensure the devices you add or you replace will auto-configure into| the SSP master configuration record, make certain that these devices| are powered on when you start the AS/400 Advanced 36 machine and| apply this configuration.

– The device you specify at port 0 address 0 of workstation controller 1will be the SSP system console for the AS/400 Advanced 36 machine.You should choose some device other than the OS/400 system consoleto be the SSP system console.

| – You may also want to remove any devices from the SSP master config-| uration record that you removed from the machine's configuration.

Note: You use the CNFIGSSP procedure to do this, after you haveapplied this configuration to the AS/400 Advanced 36 machine.

Repeat Technique 2 for all display stations and printers you want to add,change, or delete for this workstation controller.

11. Press Enter .

The original Chg M36 Display and Printer Dev display appears.

12. If you want to configure other workstation controllers, go back to step 9 onpage 31-13. Otherwise, continue with step 13 on page 31-15.

13. Press Enter .

The Change M36 Configuration display appears.

14. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

15. If you need to make any configuration changes, return to step 7 onpage 31-12.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-15

Page 330: Iseries

Configuration

You may choose to make other changes as described in other sections of thischapter before exiting.

16. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

31-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 331: Iseries

Configuration

Defining Printers and Display Stations Using Controller MappingThis section assumes you have physically connected the hardware and defined theprinters and display stations to OS/400.

SSP supports a maximum of four controllers. For this reason, an AS/400Advanced 36 machine supports only four controllers. These controllers are logicalso you can map any physical AS/400 workstation controllers to them. Mapping aphysical workstation controller also maps all the display stations and printers thatare cabled to it at the same logical ports and addresses to which they are phys-ically cabled.

Note: You can instead choose to map individual devices, rather than entire con-trollers, to an AS/400 Advanced 36 machine's workstation controller. This iscalled device mapping. You might choose to use device mapping to moreeffectively assign display stations and printers to multiple AS/400 Advanced36 machines. You would have to do this if you needed to include devicesthat were cabled to more than four physical workstation controllers. Fordirections on device mapping, see “Defining Printers and Display StationsUsing Device Mapping” on page 31-12.

Controller mapping maps an AS/400 Advanced 36 machine workstation controller toa physical AS/400 workstation controller. When you do controller mapping, you do

| not map individual devices. The devices are mapped implicitly when the controlleris mapped. All of the devices attached to the physical workstation controller willauto-configure into the corresponding mapped workstation controller of the AS/400Advanced 36 machine at the same ports and addresses to which they are phys-ically cabled.

| Note: To ensure the devices you add or you replace will auto-configure into the| SSP master configuration record, make certain that these devices are| powered on when you start the AS/400 Advanced 36 machine and apply| this configuration.

The SSP system console will be the display station cabled to port 0 address 0 ofthe AS/400 workstation controller to which workstation controller 1 of the AS/400Advanced 36 machine is mapped, unless that device is the OS/400 systemconsole. In that case, there must be a display station cabled at port 0 address 1 ofthat controller. This display station will appear to SSP to be at port 0 address 0.Therefore, the display station cabled at port 0 address 1 of that controller will bethe SSP system console.

To add or replace a printer or display station, cable it to the physical workstationcontroller at the desired port and address.

To remove a printer or display station, do the following:

1. Uncable the device from its workstation controller.

2. Delete the OS/400 Device Description for the device, as follows:

a. On an OS/400 command line, type

WRKCFGSTS \DEV

b. Press Enter .

The Work with Configuration Status display appears.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-17

Page 332: Iseries

Configuration

c. Find the name of the Device Description for the device you uncabled. Youmay have to page down to find the name.

d. In the Opt field, type

8

to select Work with description.

e. Press Enter .

The Work with Device Descriptions display appears.

f. In the Opt field, type

4

to select Delete.

g. Press Enter .

The Confirm Delete of Device Descriptions display appears.

h. Press Enter three times to delete the device description and to exit fromthe WRKCFGSTS command.

3. Use the CNFIGSSP procedure in the AS/400 Advanced 36 machine to removethe device from the master configuration record.

To configure workstation controllers with controller mapping, do as follows:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. In the Selection field, type

2

to select Change M36 display and printer devices.

8. Press Enter .

The Chg M36 Display and Printer Dev display appears.

9. To define display stations and printers using controller mapping, do one of thefollowing:

| � To configure the same workstation controllers that would be configured forthe SSP operating system if the OS/400 operating system was not installedon your system,

a. Press F10.

31-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 333: Iseries

Configuration

The list of workstation controllers on this display is filled in with thephysical workstation controller names available to SSP.

b. Then go to step 10 on page 31-20.

� To configure a new workstation controller using controller mapping,

a. Move the cursor to the blank line that corresponds to the workstationcontroller number (1-4).

Note: If this controller is not configured for the AS/400 Advanced 36machine, this line is blank.

b. If you know the name of the OS/400 Controller Description for theAS/400 workstation controller you want to map, type the name on theline.

c. Otherwise:

1) Press F4 to bring up a list of OS/400 Controller Description namesthat can be used.

2) Next to the workstation controller you want to map, type

1

3) Press Enter .

The list of OS/400 controller description names is replaced by theChg M36 Display and Printer Dev display and the selected name isfilled in on the display.

d. Go to step 10 on page 31-20.

� To change a workstation controller from device mapping to controllermapping, or to change the mapping to a different AS/400 workstationcontroller:

a. Move the cursor to the line that corresponds to the workstation con-troller number (1-4).

Note: If the workstation controller is device mapped, the line containsthe special value *DEV. If the workstation controller is alreadymapped to an AS/400 workstation controller, the line containsthe OS/400 Controller Description name.

b. If you know the name of the OS/400 controller description for the work-station controller you want to map for this controller number, type theOS/400 controller description on the line.

c. Otherwise:

1) Press F4 to bring up a list of OS/400 Controller Description names.

2) Beside the OS/400 Controller Description that you want to map tothe workstation controller, type

1

3) Press Enter .

The list of OS/400 controller description names is replaced by theChg M36 Display and Printer Dev display and the selected name isfilled in on the display.

d. Go to step 10.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-19

Page 334: Iseries

Configuration

� To remove a workstation controller from the configuration:

a. Move the cursor to the line that corresponds to the workstation con-troller number (1-4).

Note: If the workstation controller is defined in the AS/400 Advanced36 machine configuration, the line contains either the specialvalue *DEV or an OS/400 Controller Description name.

b. Space over the name with blanks.

c. Go to step 10.

10. Consider the following before you continue:

� After you change the mapping of a workstation controller and apply theconfiguration to your AS/400 Advanced 36 machine, you may want to usethe CNFIGSSP procedure to remove any printers or display stations thatare no longer in the machine configuration from the master configurationrecord.

� To see the OS/400 Device Description names for the display stations andprinters that are currently attached to an AS/400 workstation controller thatis mapped:

a. Move the cursor to the line that corresponds to the workstation con-troller number.

b. Press F21.

A grid with rows of ports and columns of addresses is displayed, withthe device description names filled in at the appropriate points.

Note: You cannot change any values on this display.

c. Press Enter to return to the Chg M36 Display and Printer Dev display.

11. Press Enter .

The Change M36 Configuration display appears.

12. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

13. If you need to make any configuration changes, return to step 7 onpage 31-18.

You may choose to make other changes as described in other sections of thischapter before exiting.

14. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

31-20 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 335: Iseries

Configuration

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-21

Page 336: Iseries

Configuration

Changing a Workstation Controller from Controller Mapping to DeviceMapping

A switch from controller mapping to device mapping may be required as the chal-lenge to map a fixed number of display stations and printers across several AS/400

| Advanced 36 machines prevents you from giving all of a controller's display stations| and printers to a single AS/400 Advanced 36 machine. The instructions in this

chapter assume that:

� You want to map your AS/400 Advanced 36 machine workstation controller withdevice mapping.

� You want the display stations and printers you have chosen to have the sameconfiguration attributes they currently have under controller mapping.

| By changing from controller mapping to device mapping, you lose the ability to| auto-configure a new device simply by cabling it to the controller. Instead, you| must do as follows:

| 1. Use the CHGM36CFG command to add the device to a logical port and| address on your device-mapped controller using the OS/400 device name.

| 2. Power off the AS/400 Advanced 36 machine.

| 3. Start the AS/400 Advanced 36 machine again using the APYM36CFG param-| eter on the STRM36 command to apply the AS/400 Advanced 36 machine con-| figuration.

Before you begin, you must find out the workstation controller number for the con-troller you want to change. For directions, see the Changing Your SystemConfiguration–SSP book, SC21-8295.

To change the workstation controller to device mapping from controller mapping, dothe following:

1. On an OS/400 command line, type

CHGM36CFG

2. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The rest of the parameters for the command appear on the display.

6. Press Enter .

The Change M36 Configuration display appears.

7. Determine whether there are any display stations or printers whose attributesare something other than the default values and make note of any of these thatare different from the default values. To do this, do the following:

a. In the Opt field, type

3

31-22 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 337: Iseries

Configuration

to select Change M36 display and printer device attributes.

b. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

c. Type the desired workstation controller number in the M36 Controller field.

d. Press Enter . The display changes to show you a list of information in thefollowing columns:

� Port � Address � AS/400 Device� Display M36 signon at IPL

� Spooling Attribute

e. Make a list of all the lines which have an AS/400 device name and either:

� An N in the Display M36 signon at IPL column

Or,

� A value other than *S36 in the Spooling Attribute column.

Note: It is not necessary to change any of the entries.

For each line, copy the information from all the columns into your list. Youmay need to page down to reach the bottom of the display.

f. Press F12 twice to return to the Change M36 Configuration display.

8. In the Opt field, type

2

to select Change M36 display and printer devices

9. Press Enter .

The Chg M36 Display and Printer Dev display appears.

10. Move the cursor to the line that corresponds to the workstation controllernumber. Write down the name of the workstation controller. You will need itlater.

11. Over the workstation controller name, type the special value

\DEV

12. Press F21.

The display changes to show a grid with rows of ports and columns ofaddresses.

13. Press F16 (Autofill from controller).

The Select AS/400 Work Station Ctlr display overlays the display.

14. Move the cursor to the line which has the name of the workstation controlleryou wrote down in step 10.

15. In the Opt field, type

1

16. Press Enter .

The Chg M36 Display and Printer Dev display returns.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-23

Page 338: Iseries

Configuration

The names of device descriptions for display stations and printers are now inthe port and address fields that correspond to how they are physically cabled.

17. Press Enter twice.

The Change M36 Configuration display appears.

18. If you did not list any information in step 7e on page 31-23, go to step 25 onpage 31-24. Otherwise, go to step 19.

19. In the Opt field, type

3

to select Change M36 display and printer device attributes.

20. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

21. In the M36 Controller field, type the workstation controller number.

22. Press Enter .

The display changes to show you a list of devices defined on the workstationcontroller. The following columns appear on the display:

� Port � Address � AS/400 Device� Display M36 signon at IPL

� Spooling Attribute

23. For each item in the list you created in step 7e on page 31-23:

a. Find the line on the display that has the port and address of an entry in thelist.

Note: You may need to page down to find it.

b. Change the Display M36 signon at IPL field or the Spooling Attribute on thedisplay to the value in the list.

c. Repeat step 23 on page 31-24 for each remaining item in your list.

24. Press Enter twice.

The Change M36 Configuration display appears.

25. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

26. If you need to make any configuration changes, return to step 7 on page 31-22or step 19 on page 31-24.

You may choose to make other changes as described in other sections of thischapter before exiting.

27. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

31-24 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 339: Iseries

Configuration

Note: If a 2 is in the Option field, and you proceed, the changes will notbe made.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears with the followingmessage at the bottom of the display:

Object changed for configuration_name in library_name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/Configuration_name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-25

Page 340: Iseries

Configuration

Defining Whether SSP or OS/400 Controls SSP Printer OutputYou can use the AS/400 Advanced 36 machine configuration object to give controlof your printer output either to SSP or to OS/400. The default is to give control toSSP. You do this on an individual basis, for printers defined to the SSP. If yougive control of the printer output for a printer to:

� SSP, then any printer output created within the AS/400 Advanced 36 machinefor that printer prints directly or goes into the SSP Spool File for later printing.In either case, the printer output is printed on the printer whose OS/400 DeviceDescription is mapped to the SSP printer for which the output was created.You can give control to SSP regardless of whether you use controller mappingor device mapping. For information on printing with SSP, see Chapter 20,“Printing with SSP.”

� OS/400, then any printer output created within the AS/400 Advanced 36machine for that printer is placed in an OS/400 output queue and is only visiblethrough OS/400. You can specify the particular output queue in the configura-tion object, in any of the following ways:

– You can choose the output queue with the same name as the OS/400Device Description for the printer to which the SSP operating system'sprinter is mapped. You can do this regardless of whether you used con-troller mapping or device mapping.

– You may choose any output queue by specifying its fully qualified nameand using it to override the OS/400 Device Description for the printer towhich the SSP's printer is mapped. You can do this regardless of whetheryou used controller mapping or device mapping.

– If you used device mapping, you can also specify the fully qualified name ofany output queue and map it directly to an SSP printer without associating

| it with an OS/400 printer Device Description. This is a way of configuringan output queue as a printer without having to base it on a printer devicedescription.

You would use OS/400 print spooling to print any output which is placed in anoutput queue regardless of whether the output came from an SSP program oran OS/400 program.

Note: You can also use the OUTQ parameter on the // PRINTER OCL statementto send the printer output to any OS/400 output queue that you specify.This overrides the SSP's normal mode of spooling the printer output orprinting it directly. For information on the // PRINTER OCL statement, seethe General Information for SSP Operating System book, SC21-8299.

Giving SSP Control of AS/400 Advanced 36 Machine Printer OutputThis section assumes you have physically connected the hardware and defined theprinter to OS/400. It also assumes you have added the printer to the AS/400Advanced 36 machine.

To give the SSP operating system control of AS/400 Advanced 36 machine printeroutput, do as follows:

1. Find out the controller number, port number, and address of the printer asdefined in the SSP configuration object using the CNFIGSSP procedure froman SSP command line on the AS/400 Advanced 36 machine.

31-26 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 341: Iseries

Configuration

For directions, see the Changing Your System Configuration–SSP book,SC21-8295.

2. On an OS/400 command line, type

CHGM36CFG

3. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

4. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

5. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

6. Press Enter .

The rest of the parameters for the command appear on the display.

7. Press Enter .

The Change M36 Configuration display appears.

8. In the Selection field, type

3

to select Change M36 display and printer device attributes.

9. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

10. In the M36 Controller field, type the identification number of the AS/400Advanced 36 machine controller that the SSP printer is attached to.

The identification number can only be: 1, 2, 3, or 4.

11. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display changes to show the attributes ofthe display stations and printers on the specified controller.

The following columns are displayed:

Port This column displays the logical AS/400Advanced 36 machine port.

Addr This column displays the logical AS/400Advanced 36 machine address.

AS/400 Device This column displays:

� The AS/400 device name that is mappedto the port and address listed on thesame line

� *OUTQ if you are mapping an AS/400Advanced 36 machine printer at this portand address to an OS/400 output queuebut you are not associating it with a phys-ical printer.

Display M36 Sign-on at IPL This column only applies to display stations.The two options for display stations are:

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-27

Page 342: Iseries

Configuration

Y Assigns the display station to theAS/400 Advanced 36 machine.The SSP Sign-On display is auto-matically shown on the displaystation when the AS/400 Advanced36 machine is started.

Note: If someone is alreadysigned-on to OS/400 at thedisplay station before theAS/400 Advanced 36machine is started, theSSP Sign-On displayappears after that personsigns off of OS/400.

N Causes the OS/400 Sign-Ondisplay to remain on the displaystation when the AS/400 Advanced36 machine is started. Once yousign on to the OS/400, you canuse the TFRM36 command totransfer to the AS/400 Advanced36 machine from this displaystation.

Spooling Attributes This column only applies to printers. Thereare three spooling options.

*S36 Specifies that no spooling is doneby the OS/400 operating system.*S36 is the default.

If there is a printer device-name inthe AS/400 device column, and*S36 is specified, the printer isacquired by SSP when a request ismade to send output to this printer.Printer output prints real time as itis sent to the printer.

OS/400 can use the printer whenthe AS/400 Advanced 36 machineis no longer using the printer.

*DEV Specifies the AS/400 printer deviceoutput queue that is in libraryQUSRSYS. Anytime SSP prints tothat printer, the output goes to theoutput queue in library QUSRSYSthat has the same name as theprinter in the AS/400 Device field.

qualified output queue name Specifies theoutput queue name that is to beused for spooled files. This mustbe specified if the AS/400 Deviceis specified as *OUTQ.

31-28 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 343: Iseries

Configuration

You are only interested in the printers in the AS/400 Device column.

12. Search through the list to find the entry corresponding to the printer's portnumber and address. You might need to page down to find it on the display.

13. When you have found the desired entry, move the cursor to the Spooling Attri-bute column for that entry.

14. In the Spooling Attribute column, beside the desired printer, type

\S36

to give control of printed output to the SSP operating system.

Note: You cannot choose this option if the name in the AS/400 Device columnis *OUTQ. In this case, there is no printer mapped to that port andaddress. See “Giving OS/400 Control of Printer Output When There IsNo Physical Printer” on page 31-32.

15. To change other printers on this workstation controller, return to step 12 onpage 31-29.

16. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears showing the M36 controllerfield.

17. If you want to change the Spooling Attributes on other AS/400 Advanced 36machine workstation controllers, return to step 10 on page 31-27.

18. Press Enter .

The Change M36 Configuration display appears.

19. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

20. If you need to make any configuration changes, return to step 8 onpage 31-27.

You may choose to make other changes as described in other sections of thischapter before exiting.

21. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe made.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears with the followingmessage at the bottom of the display:

Object changed for configuration_name in library_name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-29

Page 344: Iseries

Configuration

Note: Use the APYM36CFG (library-name/Configuration_name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

Giving OS/400 Control of AS/400 Advanced 36 Machine Printer OutputTo give the OS/400 operating system control of AS/400 Advanced 36 machineprinter output, do as follows:

1. Find out the controller number, port number, and address of the printer asdefined in the SSP configuration object using the CNFIGSSP procedure froman SSP command line on the AS/400 Advanced 36 machine.

For directions, see the Changing Your System Configuration–SSP book,SC21-8295.

2. On an OS/400 command line, type

CHGM36CFG

3. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

4. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

5. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

6. Press Enter .

The rest of the parameters for the command appear on the display.

7. Press Enter .

The Change M36 Configuration display appears.

8. In the Selection field, type

3

to select Change M36 display and printer device attributes.

9. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

10. In the M36 Controller field, type the identification number of the AS/400Advanced 36 machine controller that the SSP printer is attached to.

The identification number can only be: 1, 2, 3, or 4.

11. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display changes to show the attributes ofthe display stations and printers on the specified controller.

You are only interested in the printers in the AS/400 Device column. For infor-mation on which printer attributes you can choose, see step 11 on page 31-27and then return here.

12. Search through the list to find the entry corresponding to the printer's portnumber and address. You might need to page down to find it on the display.

13. When you have found the desired entry, move the cursor to the Spooling Attri-bute column for that entry. Do one of the following:

31-30 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 345: Iseries

Configuration

a. Type *DEV if you want to send the output to the output queue that has thesame name as the device description for the printer mapped at this portand address.

Note: You cannot choose this option if the name in the AS/400 Devicecolumn is *OUTQ. In this case, there is no printer mapped to theport and address. See “Giving OS/400 Control of Printer OutputWhen There Is No Physical Printer” on page 31-32.

b. Type a fully qualified name of the output queue if you want to give controlof the printer output to OS/400 but override the printer device descriptionand send it to a specified output queue. A fully qualified name contains:

� The name of the library where the output queue is found

� A slash

� The name of the output queue you want to use

For example, MYLIB/MYOUTQ.

14. To change other printers on this workstation controller, return to step 12 onpage 31-30.

15. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears showing the M36 controllerfield.

16. If you want to change the Spooling Attributes on other AS/400 Advanced 36machine workstation controllers, return to step 10 on page 31-30.

17. Press Enter .

The Change M36 Configuration display appears.

18. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

19. If you need to make any configuration changes, return to step 8 onpage 31-30.

You may choose to make other changes as described in other sections of thischapter before exiting.

20. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe made.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears with the followingmessage at the bottom of the display:

Object changed for configuration_name in library_name type \M36CFG.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-31

Page 346: Iseries

Configuration

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/Configuration_name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

| Note: An OS/400 Output Queue defined in the AS/400 Advanced 36 machine con-| figuration will not auto-configure printers into the SSP master configuration| record. To configure printers into the master configuration record at the| ports and addresses where you defined OS/400 Output Queues, you use| the CNFIGSSP procedure. For directions on using the CNFIGSSP proce-| dure, see the Changing Your System Configuration–SSP book, SC21-8295.

Giving OS/400 Control of Printer Output When There Is No PhysicalPrinter

You can send your output to OS/400 even if there is no physical printer.

Note: This can only be done for AS/400 Advanced 36 machine workstation con-trollers which are configured with device mapping.

To specify which OS/400 output queue will receive the AS/400 Advanced 36machine printer output, do as follows:

1. Find out the controller number, port number, and address of the printer asdefined in the SSP configuration object using the CNFIGSSP procedure froman SSP command line on the AS/400 Advanced 36 machine.

For directions, see the Changing Your System Configuration–SSP book,SC21-8295.

2. On an OS/400 command line, type

CHGM36CFG

3. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

4. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

5. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

6. Press Enter .

The rest of the parameters for the command appear on the display.

7. Press Enter .

The Change M36 Configuration display appears.

8. In the Selection field, type

2

to select Change M36 display and printer devices.

9. Press Enter .

The Chg M36 Display and Printer Dev display appears.

31-32 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 347: Iseries

Configuration

10. Position the cursor on the AS/400 Work Station Controller field of the controllerfor which you want to define the output queue for your printer output.

Note: The controller you choose must use device mapping (*DEV) to definedisplay stations and printers.

11. Press F21.

The Chg M36 Display and Printer Dev display changes to show the devicesdefined for the selected controller.

12. Find the port and address for which you want to define the output queue.There may already be a printer defined at that port and address.

13. Do one of the following:

a. To configure an output queue at a particular port and address, type *OUTQin the field corresponding to that port and address. If the field was empty,then you are adding a new printer to the configuration. If the field was not

| empty, then you are reconfiguring an existing device as a printer. Because| output queues do not auto-configure into the SSP master configuration

record, you may later want to use the CNFIGSSP procedure to configurethe printer at the desired port and address.

b. To remove an output queue from a particular port and address, space overthe *OUTQ at that port and address with blanks. You may later want touse the CNFIGSSP procedure to remove the printer at that port and

| address from the SSP master configuration record.

14. To change other printers on this workstation controller, return to step 12 onpage 31-33.

15. Press Enter .

The Chg M36 Display and Printer Dev display appears.

16. If you want to change another controller, return to step 10.

17. Press Enter .

The Change M36 Configuration display appears. Each *OUTQ you added isassociated with the OS/400 output queue that is QGPL/QPRINT.

18. If you want to change the library name or the output queue name:

a. In the Selection field, type

3

to select Change M36 display and printer device attributes.

b. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

c. In the M36 Controller field, type the identification number of the AS/400Advanced 36 machine workstation controller where you defined the *OUTQspecial value.

The identification number can only be: 1, 2, 3, or 4.

d. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display changes to show the attributesof the display stations and printers on the specified controller.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-33

Page 348: Iseries

Configuration

You are only interested in the special value *OUTQ in the AS/400 Devicecolumn. For information on which printer attributes you can specify, seestep 11 on page 31-27 and then return here.

e. Verify *OUTQ is specified for the correct port and address. You may needto page down to see the port and address.

f. In the Spooling Attribute field for that entry, you will find QGPL/QPRINT.Type over this library and output queue name with the qualified name ofthe output queue where printer output is to go for that printer. A fully quali-fied name contains:

� The name of the library where the output queue is found

� A slash

� The name of the output queue you want to use

For example, MYLIB/MYOUTQ.

g. To change another printer on this workstation controller, return to step 18e.

h. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears showing the M36 con-troller field.

i. If you want to change the Spooling Attributes on other AS/400 Advanced36 machine workstation controllers, return to step 18c on page 31-33.

Press Enter .

The Change M36 Configuration display appears.

19. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

20. If you need to make any configuration changes, return to step 8 on page 31-32or step 18 on page 31-33.

You may choose to make other changes as described in other sections of thischapter before exiting.

21. To save and exit.

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Note: If a 2 is in the Option field, and you proceed, the changes will notbe made.

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears with the followingmessage at the bottom of the display:

Object changed for configuration_name in library_name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

31-34 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 349: Iseries

Configuration

Note: Use the APYM36CFG (library_name/Configuration_name) param-eter on the STRM36 command to apply the configuration changes.

| Note: An output queue defined in the configuration object will not auto-configure| into the SSP master configuration record. Additionally, devices you remove

from the AS/400 Advanced 36 machine configuration are not automaticallyremoved from the master configuration record. If the changes you makerequire updates to the master configuration record, use the CNFIGSSP pro-cedure to make the changes. For directions on using the CNFIGSSP pro-cedure, see the Changing Your System Configuration–SSP book,SC21-8295.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-35

Page 350: Iseries

Configuration

Defining Whether SSP or OS/400 Controls the Display StationThis section assumes you have physically connected and defined the display

| station to OS/400. It also assumes you have added the display station to the| AS/400 Advanced 36 machine's configuration. You can specify whether the SSP

operating system or the OS/400 operating system controls the display station.

� If SSP controls the display station:

When the AS/400 Advanced 36 machine is started, the OS/400 sign-on displayis blanked out. Then, the SSP sign-on display appears. If the OS/400 sign-ondisplay is not shown when the AS/400 Advanced 36 machine is started, whenthe user signs off the SSP sign-on display appears.

� If OS/400 controls the display station:

When the AS/400 Advanced 36 machine is started, the OS/400 sign-on display| continues to be shown. To the SSP operating system, the display station| appears to be powered off until one of the following occurs:

| – The Transfer AS/400 Advanced 36 Machine (TFRM36) command is used totransfer the display station to an AS/400 Advanced 36 machine.

| – The Start AS/400 Advanced 36 Machine Procedure (STRM36PRC)| command is used to run an SSP procedure.

To specify whether a display station controlled by SSP or OS/400, do as follows:

1. Find out the controller number, port number, and address of the display stationas defined in the SSP configuration object using the CNFIGSSP procedurefrom an SSP command line on the AS/400 Advanced 36 machine.

2. On an OS/400 command line, type

CHGM36CFG

3. Press F4.

The Change Machine Configuration (CHGM36CFG) display appears.

4. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

5. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

6. Press Enter .

The rest of the parameters for the command appear on the display.

7. Press Enter .

The Change M36 Configuration display appears.

8. In the Selection field, type

3

to select Change M36 display and printer device attributes.

9. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

10. In the M36 Controller field, type the identification number of the AS/400Advanced 36 machine controller.

31-36 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 351: Iseries

Configuration

The identification number can only be: 1, 2, 3, or 4.

11. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears with different informationdisplayed.

| 12. Search the list and find the entry that corresponds to the port and address ofthe display station. You may need to page down to find the entry.

13. Look at the Display M36 signon at IPL column.

If there is a Y in this field, the display station is controlled by SSP. The SSPSign-On display is automatically shown on the display station when the AS/400Advanced 36 machine is started.

Note: If there is a Y in this field, it is ignored for the display station that is theOS/400 console.

If there is an N in this field, the display station is controlled by OS/400. AnOS/400 sign-on display remains on this display station when the system isstarted. You use the OS/400 TFRM36 CL command to transfer to the AS/400

| Advanced 36 machine when you want to use it. You can also use the OS/400| STRM36PRC command to run an SSP procedure from it.

| Note: You should not transfer the OS/400 console to an AS/400 Advanced 36| machine.

14. If you want OS/400 to control the display station, make sure there is an N in theDisplay M36 signon at IPL column.

15. If you want SSP to control the display station, make sure there is a Y in theDisplay M36 signon at IPL column.

16. If you want to change the attributes of other display stations, go back to step12 on page 31-37.

17. Press Enter .

The Chg M36 Dsp and Prt Dev Attr display appears.

18. If you want to change display stations on other workstation controllers, return tostep 10 on page 31-36.

19. Press Enter .

The Change M36 Configuration display appears.

20. Press F19 to validate your changes.

Note: For information on how to handle warnings and errors, go to “Validatingan AS/400 Advanced 36 Machine Configuration” on page 31-39 andthen return here.

21. If you need to make any configuration changes, return to step 8 onpage 31-36.

You may choose to make other changes as described in other sections of thischapter before exiting.

22. To save and exit,

a. Press F3.

The Exit M36 Configuration display appears.

b. Make sure a 1 is in the Option field.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-37

Page 352: Iseries

Configuration

Note: If a 2 is in the Option field, and you proceed, the changes will notbe saved.

c. Press Enter .

The configuration changes are saved and the display with the OS/400command line where you typed CHGM36CFG appears. The followingmessage appears:

Object changed for configuration object-name in library-name type \M36CFG.

where configuration_name is the name of the configuration you justchanged and library_name is the name of the library that contains the con-figuration.

Note: Use the APYM36CFG (library-name/configuration-name) parameteron the STRM36 command to apply the configuration changes to anAS/400 Advanced 36 machine. The changes will not affect anAS/400 Advanced 36 machine until you do this.

31-38 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 353: Iseries

Configuration

Validating an AS/400 Advanced 36 Machine ConfigurationTo validate a configuration, before saving and exiting the Change M36 Configura-tion display, you press F19. You always receive a message.

If everything is acceptable, you see a message that indicates the validation com-pleted.

If the validation completed with warnings, the configuration can be applied whenyou start the AS/400 Advanced 36 machine, but some devices may not be useable.

If the validation completed with errors, the configuration cannot be applied whenyou start an AS/400 Advanced 36 machine.

If there are warnings or errors, the devices you added are not configured correctly.

To determine the cause of any warning or error messages, do the following:

1. Move the cursor down to the error message.

2. Press F1.

The Additional Messages Information display appears.

3. Press F10.

All the messages between the following message:

Validation of machine configuration started

and the last displayed message are all problems found in the configuration.Most of the errors that would not allow an AS/400 Advanced 36 machine to bestarted with this configuration contain an (E) in the first-level text.

4. Press Enter twice to return to the Create M36 Configuration display.

5. Return to the step that sent you here.

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-39

Page 354: Iseries

Configuration

31-40 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 355: Iseries

Displaying Configuration and Machine

Chapter 32. Displaying Information About an AS/400Advanced 36 Configuration and Machine

You use the Display AS/400 Advanced 36 Machine Configuration (DSPM36CFG)command to display information about a specific AS/400 Advanced 36 machineconfiguration. You use the Display AS/400 Advanced 36 Machine (DSPM36)command to display information about the AS/400 Advanced 36 machine and theconfiguration that was last applied to the AS/400 Advanced 36 machine. When youuse the DSPM36CFG and DSPM36 commands, you cannot make any changes tothe configuration or to the machine information.

This chapter provides instructions on how to display your AS/400 Advanced 36 con-figuration or machine. The information includes instructions on:

� “Displaying a Configuration” on page 32-1.

� “Displaying a Machine” on page 32-2.

Displaying a ConfigurationTo display the configuration for an AS/400 Advanced 36 machine, do as follows:

1. On an OS/400 command line, type

DSPM36CFG

2. Press F4.

The Display Machine Configuration (DSPM36CFG) display appears.

3. In the Machine configuration field, type the name of the AS/400 Advanced 36machine configuration.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine configuration object is stored.

5. Press Enter .

The Display M36 Configuration display appears.

6. Type the number of the option that you want to display.

7. Press Enter .

The displays that appear are quite similar to the Change displays.

Note: You cannot make changes to any of these displays.

8. To display other options:

a. Press Enter .

The Display M36 Configuration display appears again

b. Repeat steps 6 and 7.

9. To exit, press F3.

Copyright IBM Corp. 1995, 1996 32-1

Page 356: Iseries

Displaying Configuration and Machine

Displaying a MachineYou can display the following for an AS/400 Advanced 36 machine:

� Status of the machine

� The attributes of the machine

� Information on the configuration that was last applied to the machine

You would want to look at the configuration information if you have deleted orchanged the configuration object and you want to know what the configurationobject looked like the last time it was applied to the machine.

To display the information for an AS/400 Advanced 36 machine, do as follows:

1. On an OS/400 command line, type

DSPM36

2. Press F4.

The Display Machine (DSPM36) display appears.

3. In the Machine field, type the name of the machine.

4. In the Library field, type the name of the library in which the AS/400 Advanced36 machine is stored.

5. Press Enter .

The Display M36 Machine display appears.

6. In the Selection field, type

1

to select Display M36 attributes.

7. Press Enter .

The Display M36 Attributes display appears.

The following information is shown on the display.

Machine The name of this AS/400 Advanced 36 machine.

Library The name of the library where the AS/400 Advanced 36 machineresides.

Console check When there is an SSP console check, the Console check fieldappears. If it appears, it always has a value of Y. The line thatcontains this field does not appear if there is not an SSP consolecheck for this AS/400 Advanced 36 machine.

M36 status The status of the AS/400 Advanced 36 machine. The possiblestatus values are as follows:

Incomplete The machine has no configuration applied. This is anempty machine.

Damaged The machine is damaged. If you know why the machineis damaged, you can attempt to fix the machine. If youcannot fix the machine, the machine should be deleted.You would then restore the machine and its data fromyour last backup.

32-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 357: Iseries

Displaying Configuration and Machine

Job Queue The AS/400 Advanced 36 machine is currently on a jobqueue where it is waiting to start. When you start anAS/400 Advanced 36 machine, the request is alwayssent to the QSYSNOMAX batch queue in the QSYSWRKsubsystem.

Starting The AS/400 Advanced 36 machine is starting. An IPL isin progress.

Started The AS/400 Advanced 36 machine is started and active.

Ending A request to power off the AS/400 Advanced 36 machineis in progress. This can be requested using the SSPPOWER OFF command or by using the OS/400ENDM36 command. This status also occurs if theAS/400 Advanced 36 machine session is ending abnor-mally.

Ended The AS/400 Advanced 36 machine is not started yet or isno longer active.

Abended The AS/400 Advanced 36 machine ended abnormally.Look at the SRC code on the line after M36 status.

M36 SRC code The current system reference code (SRC) for this AS/400Advanced 36 machine

M36 Id A three-character unique identification assigned by the system at thetime the AS/400 Advanced 36 machine was created.

M36 fixed disk size The size of the fixed disk reserved for the AS/400Advanced 36 machine in megabytes. You can change the size ofthe fixed disk using the SSP CHGSYSVL command.

M36 auto-signon Indicates whether the users can bypass the SSP Sign-Ondisplay when they transfer to an AS/400 Advanced 36 machine.

Note: The OS/400 STRM36PRC CL command only works if thisvalue is *ENABLE.

| M36 applied configuration The name of the AS/400 Advanced 36 machine| configuration that was most recently applied to the AS/400| Advanced 36 machine. It also shows the library where the listed

AS/400 Advanced 36 machine configuration resided when the con-figuration was applied.

| M36 server job The qualified job name of the AS/400 Advanced 36 server job| that was most recently associated with this AS/400 Advanced 36

machine.

The qualified job name is:

QM36xxx/user-profile/yyyyyy

where xxx is the number of the AS/400 Advanced 36 machine andyyyyyy is the batch job number. Both of these numbers areassigned by the system. The number of the AS/400 Advanced 36machine is in the M36 Id field on the Display M36 Attributes display.

IPL type Indicates whether the default IPL Type for this AS/400 Advanced 36machine is attended or unattended.

Chapter 32. Displaying Information About an AS/400 Advanced 36 Configuration and Machine 32-3

Page 358: Iseries

Displaying Configuration and Machine

User profile The name of the default AS/400 user profile associated with thisAS/400 Advanced 36 machine. This is the user profile used by theAS/400 Advanced 36 server job for handling AS/400 requests fromthe AS/400 Advanced 36 machine.

Text description The specified user description for this AS/400 Advanced 36machine.

Note: You cannot make changes to any of these displays.

8. Press Enter .

The Display M36 Machine display appears.

9. To display AS/400 Advanced 36 machine configuration information, type anumber (from 2 through 6) in the Opt field.

Note: These options are described in “Displaying a Configuration” onpage 32-1.

10. Press Enter to display the display with that configuration information.

11. If you want to see more configuration information, press Enter and return tostep 9.

12. To exit, press F3.

32-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 359: Iseries

Other Useful Information

Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1System/36 Procedures to AS/400 Commands Cross-Reference . . . . . . . . A-1System/36 Control Commands to AS/400 Commands Cross-Reference . . . A-27System/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-1Displaying the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Setting the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Appendix C. Performance Considerations . . . . . . . . . . . . . . . . . . C-1Understanding Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1Understanding Prestart Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2Setting Attributes For the AS/400 Advanced 36 Server Job . . . . . . . . . . C-3

Changing the Priority of an AS/400 Advanced 36 Server Job — Example C-4Setting attributes for the AS/400 Advanced 36 SLIC Tasks . . . . . . . . . . C-5Setting Attributes for the AS/400 Advanced 36 Prestart Jobs . . . . . . . . . C-6

Changing the Priority and Storage Pool for an AS/400 Advanced 36Prestart Job— Example . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

Changing the AS/400 Advanced 36 Prestart Job to Immediately UseChanged Values — Example . . . . . . . . . . . . . . . . . . . . . . . . C-7

Appendix D. Using Electronic Customer Support . . . . . . . . . . . . . . D-1Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

System Detected Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1Putting User-Detected Problems in the Problem Log . . . . . . . . . . . . . D-2What Happens After Submitting a Problem Through Electronic Customer

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2Reviewing Status of an Open Problem . . . . . . . . . . . . . . . . . . . . . . D-3Ordering PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Appendix E. Preparing SSP for Dedicated State . . . . . . . . . . . . . . . E-1

Copyright IBM Corp. 1995, 1996

Page 360: Iseries

AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 361: Iseries

Procedures

Appendix A. System/36 and AS/400 CommandsCross-Reference

System/36 procedures, control commands, and OCL statements are listed alpha-betically, with cross-references to AS/400* commands, beginning on the followingpages.

System/36 procedures Page A-1System/36 control commands Page A-27System/36 OCL statements Page A-32

System/36 Procedures to AS/400 Commands Cross-ReferenceThe first column lists the System/36 commands in alphabetic order. The secondcolumn lists the AS/400 commands with the same (or similar) function followed by abrief description of the AS/400 function.

Note: Some of the commands listed in the second column are not part of OS/400.They are part of an AS/400 licensed program. For example, STRPDM andSTRSEU are not part of OS/400.

System/36 AS/400 AS/400 Function#STRTUP1 ADDAJE Adds an autostart job entry to an existing sub-

system description

WRKSBSD Allows you to work with a list of subsystemdescriptions

#STRTUP2 ADDAJE Adds an autostart job entry to an existing sub-system description

WRKSBSD Allows you to work with a list of subsystemdescriptions

ALERT CHGMSGD Changes an existing message description stored ina specified message file

ALOCFLDR RGZDLO Allows a user to reorganize document libraryobjects

ALOCLIBR None Function not supported or no longer required onthe AS/400 system

ALTERCOM GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

APAR CRTAPAR Records data on tape, diskette, or a save file ondisk to submit with an authorized program analysisreport (APAR)

APPNINFO DSPAPPNINF Displays or prints APPN* network information

ARCHIVE SAVDLO Saves the specified documents or folders to tape,diskette, or a save file on disk

ASM None Function not supported or no longer required onthe AS/400 system

Copyright IBM Corp. 1995, 1996 A-1

Page 362: Iseries

Procedures

System/36 AS/400 AS/400 FunctionAUTOC CRTRPGPGM Creates (compiles) RPG with automatic report

specifications

AUTOPTCH GO CMDPTF Shows Program Temporary Fix (PTF) commandmenu

BALPRINT None Function not supported or no longer required onthe AS/400 system

BASIC STRBAS Starts a BASIC session

BASICP STRBASPRC Starts running a BASIC procedure saved as asource file member

BASICR CALL Calls a specified program and passes control to it

BASICS CRTBASPGM Creates (compiles) a BASIC program

BGUATTR STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

BGUCHART DSPCHT Displays an existing chart defined by the BusinessGraphics Utility (BGU) licensed program

DSPGDF Displays, prints, or plots a graphics data file

STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

BGUDATA STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

BGUGRAPH DSPGDF Displays, prints, or plots a graphics data file

DSPCHT Displays an existing chart defined by the BusinessGraphics Utility (BGU) licensed program

STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

BLDFILE CRTPF Creates a physical file

CRTSRCPF Creates a database file to contain source state-ments

BLDGRAPH CRTGDF Creates a graphics data file from a chart formatand a data file

STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

BLDINDEX CRTLF Creates a logical file

BLDLIBR CRTLIB Creates a user library

CPYSRCF Copy Source File

BLDMENU CRTMNU Creates either a display file or program menu

CRTMSGFMNU Creates a menu from specified message files

CRTS36MNU Creates a menu (display file and commandmessage file) from the user's source members

BUILD None Function not supported or no longer required onthe AS/400 system

A-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 363: Iseries

Procedures

System/36 AS/400 AS/400 FunctionCACHE None Function not supported or no longer required on

the AS/400 system

CATALOG DSPDKT Displays the volume label and the data file identi-fier on a diskette

DSPFD Displays the information retrieved from a filedescription of a database

DSPFFD Displays or prints field-level information for one ormore files in one library or all libraries that the usercan access

DSPFLR Displays or prints a list of folders and documents,or creates a database file containing the list

DSPLIB Displays the contents of one or more libraries

DSPOBJD Displays the names and attributes of specifiedobjects in a specified library

DSPTAP Displays the volume label and data file label infor-mation on a tape

CGU STRCGU Starts the Character Generator Utility (CGU) func-tion

CHGSYSVL CHGSYSVAL Changes the current value of a system value

CHGXLATE None Function not supported or no longer required onthe AS/400 system

CHNGEMEM RNMOBJ Renames a specified object name and object type

RNMM Renames a specified file member

CLRPF CLRPFM Clears data from a physical file member

CNFIGICF GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

CRTCTLxxxx Creates a controller description where xxxx is thecontroller class or type

CRTDEVxxxx Creates a device description where xxxx is thedevice class or type

CRTLINxxxx Creates a line description where xxxx is the lineclass or type

CHGCTLxxxx Changes a controller description where xxxx is thecontroller class or type

CHGDEVxxxx Changes a device description where xxxx is thedevice class or type

CHGLINxxxx Changes a line description where xxxx is the lineclass or type

CFGRPDS Configures the RSCS/PROFS* bridge application

DLTCTLD Deletes a controller description

DLTDEVD Deletes a device description

Appendix A. System/36 and AS/400 Commands Cross-Reference A-3

Page 364: Iseries

Procedures

System/36 AS/400 AS/400 FunctionDLTLIND Deletes a line description

CNFIGSSP CRTDEVxxxx Creates a device description where xxxx is thedevice class or type

CRTPRTF Creates a printer device file

CHGDEVxxxx Changes a device description where xxxx is thedevice class or type

CHGPRTF Changes one or more of the characteristics of thespecified printer device files

DLTDEVD Deletes a device description

GO LICPGM Shows the Work with Licensed Program display

CNFIGX25 GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

COBOLC CRTCBLPGM Creates (compiles) a COBOL program

CRTRMCPGM Allows a user to compile an RM/COBOL-85**source program into an program that can be run inthe AS/400 environment

COBOLONL STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

COBOLP STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

COBSDA STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSDA Starts the screen design aid main menu and allowsusers to create or change a display format interac-tively

COBSEU STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSEU Calls the source entry utility (SEU) program anddisplays the main menu

COMPRESS None Function not supported or no longer required onthe AS/400 system

CONDENSE None Function not supported or no longer required onthe AS/400 system (use RGZDLO to condense afolder)

A-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 365: Iseries

Procedures

System/36 AS/400 AS/400 FunctionCOPYDATA CPYF Copies all or part of a file from the database or

external device to the database or another externaldevice

CRTDUPOBJ Copies one or a group of objects from one libraryto another

RGZPFM Reorganizes a physical file member

COPYDIAG DUPDKT Duplicates the contents from one diskette onto oneor more other diskettes

COPYI1 DUPDKT Duplicates the contents from one diskette onto oneor more other diskettes

COPYPRT CPYSPLF Copies data records in a specified spooled outputfile to a user-defined physical database file

DSPSPLF Displays the contents of a specified spooled file

CREATE ADDMSGD Describes a message and stores it in a specifiedmessage file

CRTMSGF Creates a user-defined message file

CRTS36MSGF Creates a message file from the user's System/36message source member

CSALL DSCJOB Disconnect all interactive jobs

DATE CHGJOB Changes the attributes of a job

DEFINEID GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

DEFINEPN GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

DEFINLOC GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

DEFINX21 GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

DEFINX25 GO CFGCMN Shows the Configure Communications display(more command mapping information can be foundin the System/36 Migration book)

DEFSUBD CRTFLR Creates a folder

DLTDLO Deletes one or all documents or folders

DELETE DLTDKTLBL Deletes a data file identifier from a diskette

DLTDLO Deletes one or all documents or folders

DLTDTADCT Deletes a data dictionary

DLTF Deletes a specified database or device files

Appendix A. System/36 and AS/400 Commands Cross-Reference A-5

Page 366: Iseries

Procedures

System/36 AS/400 AS/400 FunctionDLTLIB Deletes a specified library after all objects in the

library are deleted or moved

WRKOBJ Allows a user to work with objects

DELNRD WRKDDMF Displays a list of DDM files, which allows you tochange, delete, create, and do other work withDDM files

DFA DMPCLPGM Dumps all variables declared in a CL program andall messages in the program's message queue to aspooled printer file

DMPDLO Dumps the contents and/or attributes, or both, offolders, documents, or internal document librarysystem objects to a printer file

DMPJOB Dumps the basic data structures or specific calls ofthe current job or the job being serviced

DMPJOBINT Dumps the machine internal data related to thecurrent job

DMPOBJ Dumps the contents and/or attributes of a specifiedobject stored in a library to a spooled printer file

DMPSYSOBJ Dumps the contents, attributes, or both, of anyobject, a generic group of objects, or all objects toa spooled printer file

DMPTAP Dumps label information, data blocks, or both, fromlabeled or unlabeled tapes to a spooled printer file

DMPTRC Dumps the performance data from the trace tableto a database file

PRTINTDTA Prints the dump file copied from DMPJOBINTcommand

STRSST Starts system service tools by showing the SystemService Tools main menu

DFU STRDFU Starts the Data File Utility (DFU) program

STRPGMMNU Starts the programmer menu

DISABLE VRYCFG Varies lines, controllers, or devices on or off, andoptionally resets the IOP associated with the speci-fied object

DOCCNV None Function not supported or no longer required onthe AS/400 system

DSPLOCKS DSPRCDLCK Show current records lock status

WRKOBJLCK Work with object locks

DSPMNU DSPMNUA Display menu attributes

DSPSYS WRKHDWPRD Work with system configuration information

WRKLICINF Show products and features on the system (Workwith Licensed Information)

A-6 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 367: Iseries

Procedures

System/36 AS/400 AS/400 FunctionWRKSYSSTS Work with information about status of system

DSPSYSVL DSPSYSVAL Display the current value of a system value

DSU STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRPGMMNU Starts the programmer menu

STRSEU Calls the source entry utility (SEU) program anddisplays the main menu

WRKMBRPDM Allows you to work with lists of members

DUMP DMPCLPGM Dumps all variables declared in a CL program andall messages in the program's message queue to aspooled printer file

DMPDLO Dumps the contents and/or attributes, or both, offolders, documents, or internal document librarysystem objects to a printer file

DMPJOB Dumps the basic data structures or specific calls ofthe current job or the job being serviced

DMPJOBINT Dumps the machine internal data related to thecurrent job

DMPOBJ Dumps the contents and/or attributes of a specifiedobject stored in a library to a spooled printer file

DMPSYSOBJ Dumps the contents, attributes, or both, of anyobject, a generic group of objects, or all objects toa spooled printer file

DMPTAP Dumps label information, data blocks, or both, fromlabeled or unlabeled tapes to a spooled printer file

DMPTRC Dumps the performance data from the trace tableto a database file

PRTINTDTA Prints the dump file copied from DMPJOBINTcommand

STRSST Starts system service tools by showing the SystemService Tools main menu

ECSAPTCH GO CMDPTF Shows the Program Temporary Fix (PTF)command menu

EDITNRD CHGDDMF Changes one or more of the values in the specifiedDDM file

CRTDDMF Creates a distributed data management file todefine a remote file to the local system

RNMOBJ Renames a specified object name and object type

WRKDIRE Work with Directory Entry

EM3270 ENDPRTEML Ends printer emulation without ending the job

Appendix A. System/36 and AS/400 Commands Cross-Reference A-7

Page 368: Iseries

Procedures

System/36 AS/400 AS/400 FunctionSTREML3270 Starts a 3270 device emulation session

STRPRTEML Starts 3270 printer emulation

ENABLE VRYCFG Varies lines, controllers, or devices on or off, andoptionally resets the IOP associated with the speci-fied object

ENTER STRDFU Starts the Data File Utility (DFU) program

CHGDTA Changes, adds, or deletes records in an existingdatabase file

EPDOWNL STREML3270 Starts a 3270 device emulation session

EPLMRG None Function not supported or no longer required onthe AS/400 system

EP3270 STREML3270 Starts a 3270 device emulation session

ERAP STRSST Starts system service tools by showing the SystemService Tools main menu

ERR SNDBRKMSG Sends a message to one or more work stationmessage queues

SNDPGMMSG Sends a message from a program to a user,system operator, user profile message queue, orall active users

SNDUSRMSG Sends a message from a program to a messagequeue and receives a reply

ES3270 STREML3270 Starts a 3270 device emulation session

STRPRTEML Starts 3270 printer emulation

FORMAT CRTDSPF Creates a device file to define a display station tothe system

CHGDSPF Changes (in the file description) one or more of theattributes of the specified display device file

CRTS36DSPF Creates a display file from System/36 SFGRsource

FORTGO CALL Calls a specified program and passes control to it

FORTONL STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

FORTP STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

FORTRANC CRTFTNPGM Compiles a FORTRAN/400* source program intoan object program

A-8 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 369: Iseries

Procedures

System/36 AS/400 AS/400 FunctionFORTSDA STRPDM Calls the Programming Development Manager

(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSDA Starts the screen design aid main menu and allowsusers to create or change a display format interac-tively

FORTSEU STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSEU Calls the source entry utility (SEU) program anddisplays the main menu

FROMLIBR CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

CPYTODKT Copies a database or device file to diskette

CPYTOTAP Copies records to a tape file from a physical,logical, or spooled inline file, from tape, or fromdiskette in a specified block format

SAVOBJ The Save Object (SAVOBJ) command saves acopy of a single object or a group of objectslocated in the same library. For job queues, outputqueues, data queues, message queues, andlogical files, only the object descriptions are saved,and the contents of the objects are not saved.

SAVS36LIBM Saves a copy of source file members on disketteor tape

HELP Replaced Replaced by online help information for commandsand the F4 prompt key

HISTORY DSPJOBLOG Displays commands and related job messages

DSPLOG Displays the contents of the history log

GO CMDLOG Displays a menu of commands relating to logs

ICFDEBUG TRCICF Traces all ICF functions that occur within the jobthat entered the command

ICVERIFY None Function not supported or no longer required onthe AS/400 system

IDDU STRIDD Starts IDDU

WRKDTADCT Allows a user to work with the contents of a datadictionary

IDDUDCT CRTDTADCT Creates a data dictionary

WRKDTADCT Allows a user to work with the contents of a datadictionary

Appendix A. System/36 and AS/400 Commands Cross-Reference A-9

Page 370: Iseries

Procedures

System/36 AS/400 AS/400 FunctionIDDUDFN STRIDD Starts IDDU

DSPDTADCT Displays or prints the contents of a field, recordformat, or file definition

DSPDBR Displays or prints relational information about data-base files, record formats, and libraries

DSPFFD Displays or prints field-level information for one ormore files in one library or all libraries that the usercan access

WRKDTADFN Allows a user to work with data definitions

IDDUDISK CRTPF Creates a physical file

STRDFU Starts the Data File Utility (DFU) program

WRKDBFIDD Shows the IDDU Work with Database Files displaywhere you can select an option to create physicalfiles or enter data into a file

IDDULINK STRIDD Starts IDDU

LNKDTADFN Links or unlinks file definitions in a dictionary andprogram-described files

IDDUPRT STRIDD Starts IDDU

DSPFFD Displays or prints field-level information for one ormore files in one library or all libraries that the usercan access

DSPDBR Displays or prints relational information about data-base files, record formats, and libraries

DSPDTADCT Displays or prints the contents of a field, recordformat, or file definition

IDDURBLD None Function not supported or no longer required onthe AS/400 system

IDDUXLAT None Function not supported or no longer required onthe AS/400 system

INIT CLRDKT Clears all files from a diskette

INZDKT Initializes identification information and sets theformat on a diskette

RNMDKT Changes the volume identifier of a diskette orchanges the name of its owner

INITDIAG INZDKT Initializes identification information and sets theformat on a diskette

INIT9332 None Function not supported or no longer required onthe AS/400 system

INQUIRY DSPDTA Displays the contents of a database physical fileunder control of a DFU program

STRDFU Starts the Data File Utility (DFU) program

IPL PWRDWNSYS Powers down the system

A-10 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 371: Iseries

Procedures

System/36 AS/400 AS/400 FunctionITF STRITF Starts sending and receiving data through different

applications

JOBSTR CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

RSTS36LIBM Reads a file containing library members, createsdatabase source or data file members on theAS/400 system, and copies the member data fromthe file into each restored member

SBMJOB Allows a job that is running to submit another jobto a job queue to be run later as a batch job

CPYFRMDKT Copies one or more files from diskette to an outputfile or to a printer

KEYS GO CMDKBD Displays a menu of commands relating to key-boards

KEYSORT None Function not supported or no longer required onthe AS/400 system

LIBRLIBR CPYLIB Copies a library and all of its objects to anotherlibrary

CRTDUPOBJ Copies one or a group of objects from one libraryto another

CRTSRCPF Creates a database file to contain source state-ments

LINES OVRPRTF Overrides the file named, overrides certain param-eters of that file, or overrides the file named andcertain parameters of the file that is processed

LIST GO CMDQRY Displays a menu of commands relating to queries

LISTDATA CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

CPYFRMDKT Copies one or more files from diskette to an outputfile or to a printer

CPYFRMTAP Copies records from a tape file to a physical file,diskette, tape, or program-described printer file

CPYSRCF Copies a database source file to a physical sourcefile

DSPPFM Displays a physical database file member

LISTFILE CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

CPYFRMDKT Copies one or more files from diskette to an outputfile or to a printer

Appendix A. System/36 and AS/400 Commands Cross-Reference A-11

Page 372: Iseries

Procedures

System/36 AS/400 AS/400 FunctionCPYFRMTAP Copies records from a tape file to a physical file,

diskette, tape, or program-described printer file

CPYSRCF Copies records from a tape file to a physical file,diskette, tape, or program-described printer file

DMPTAP Dumps label information, data blocks, or both, fromlabeled or unlabeled tapes to a spooled printer file

DSPDKT Displays the volume label and the data file identi-fier on a diskette

DSPTAP Displays the volume label and data file label infor-mation on a tape

LISTLIBR CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

DSPLIB Displays the contents of one or more libraries

DSPOBJD Displays the names and attributes of specifiedobjects in a specified library

STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

LISTNRD DSPDDMF Displays or prints detailed information about thespecified DDM file

WRKDDMF Displays a list of DDM files, which allows you tochange, delete, create, and do other work withDDM files

LOG CHGJOB Changes the attributes of a job

CHGSYSVAL Changes the current value of the specified systemvalue

CHGJOBD Changes the attributes specified for a jobdescription object

MAINTX25 None Function not supported or no longer required onthe AS/400 system

MCSCONV None Function not supported or no longer required onthe AS/400 system

MOVEFLDR None Function not supported or no longer required onthe AS/400 system

MSGFILE CRTMSGQ Creates a user-defined message queue

DLTMSGQ Deletes the specified message queue

DSPMSG Displays messages received at the specifiedmessage queue

GO CMDMSG Displays a menu of commands relating to mes-sages

A-12 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 373: Iseries

Procedures

System/36 AS/400 AS/400 FunctionRMVMSG Removes the specified message or group of mes-

sages from the specified message queue

MSRJE ENDRJESSN Ends a remote job entry session for a specifiedsession

GO CMDRJE Displays a menu of commands relating to remotejob entry

SBMRJEJOB Submits a remote job entry input stream to thehost system as a batch job

STRRJESSN Starts a remote job entry session for a specifiedsession

WRKRJESSN Allows a user to work with information about anactive remote job entry (RJE) session

NOHALT ADDMSGD Describes a message and stores it in a specifiedmessage file

CHGMSGD Changes an existing message description stored ina specified message file

CHGRPYLE Changes the message ID, comparison data,message, or dump attributes of the reply

DSPMSG Displays messages received at the specifiedmessage queue

DSPMSGD Displays detailed information about messages in amessage file

MONMSG Monitors the messages sent to the programmessage queue

WRKRPYLE Allows a user to work with reply entries currently inthe system message reply list

OFCBPRT STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCCAL STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCCANCL ENDSBS Ends the processing in a specified subsystem or allsubsystems

OFCCOMM None Function not supported or no longer required onthe AS/400 system

CFGDSTSRV Changes the configuration of the distributionnetwork

Appendix A. System/36 and AS/400 Commands Cross-Reference A-13

Page 374: Iseries

Procedures

System/36 AS/400 AS/400 FunctionOFCDATA SAVOBJ The Save Object (SAVOBJ) command saves a

copy of a single object or a group of objectslocated in the same library. The system saves thespecified objects by writing a copy of each one ondiskettes, tapes, CD-ROM volumes or in a savefile. For job queues, output queues, data queues,message queues, and logical files, only the objectdescriptions are saved, and the contents of theobjects are not saved.

SAVLIB Saves libraries to tape, diskette, or a save file ondisk

SAVDLO Saves the specified documents or folders to tape,diskette, or a save file on disk

RGZPFM Reorganizes a physical file member

OFCDFLT STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCDIR WRKDIR Allows user to work interactively with a set of dis-plays to view, add, change, and remove entries inthe system directory

OFCFILE WRKDOC Allows a user to work with the word processingfunction

OFCGRP WRKDSTL Allows a user to work with distribution lists

OFCINSTL RSTLICPGM Restores an IBM licensed program from tape forinitial installation or new release installation

OFCLDF STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCMAIL STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCMAINT CFGDSTSRV Changes the configuration of the distributionnetwork

OFCMSG SNDMSG Sends a message from one user to one or moremessage queues

STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCQ WRKDSTQ Allows the user to work with distribution requestson the distribution queues

WRKDOCPRTQ Allows the user to work with the word processingfunction

OFCSRCH STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCSTAT STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

OFCUSER STROFC Starts OfficeVision/400* which allows the user todo office functions interactively

A-14 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 375: Iseries

Procedures

System/36 AS/400 AS/400 FunctionOLINK None Function not supported or no longer required on

the AS/400 system

ORGANIZE CPYF Copies all or part of a file from the database orexternal device to the database or another externaldevice

RGZPFM Reorganizes a physical file member

PASSTHRU STRPASTHR Starts a pass-through session and allows the userto sign on a remote system as if the user werelocally attached

PASSWORD CHGDSTPWD Changes the password shipped with the system forthe security officer user profile (QSECOFR)

CHGPRF Changes the values of a user's profile

CHGPWD Changes a user's password

CHGUSRPRF Changes the values specified in a user profile

PATCH DMPOBJ Dumps the contents and/or attributes of a specifiedobject stored in a library to a spooled printer file

DMPSYSOBJ Dumps the contents, attributes, or both, of anyobject, a generic group of objects, or all objects toa spooled printer file

STRSST Starts system service tools by showing the SystemService Tools main menu

PCEXCH None Function not supported or no longer required onthe AS/400 system

PCEXEC STRPCCMD Starts a single PC application or DOS commandon the personal computer

PCOPROF CHGPCOPRF Allows you to specify if you want to useDisplayWrite* 4 or OfficeVision/400* as your texteditor

MENU PCOMNU GO PCOMNU Shows the AS/400 PC Support Organizer display

PCU CVTTOFLR Converts a virtual disk into a folder and PC docu-ments

CPYFRMPCD Copies the data from a PC document into a phys-ical database file on the AS/400 system

CPYTOPCD Copies the contents of a member from a physicaldatabase file on the AS/400 system to a PC docu-ment in a folder

POST GO CMDCPY Displays a menu of commands relating to copying

PRINT CHGDEVxxxx Changes a device description where xxxx is thedevice class or type

CHGJOB Changes the attributes of a job

CHGUSRPRF Changes the values specified in a user profile

CRTPRTF Creates a printer device file

Appendix A. System/36 and AS/400 Commands Cross-Reference A-15

Page 376: Iseries

Procedures

System/36 AS/400 AS/400 FunctionOVRPRTF Overrides the file named, overrides certain param-

eters of that file, or overrides the file named andcertain parameters of the file that is processed

PRINTKEY CHGDEVxxxx Changes a device description where xxxx is thedevice class or type

CHGUSRPRF Changes the values specified in a user profile

CHGJOB Changes the attributes of a job

PROBLEM ANZPRB Shows the Analyze Problems menu, and allows theuser to analyze or report problems not detected bythe system

DSPPRB Displays or prints service-related information forhardware or programming

WRKPRB Allows a user to work with the problems that weredetected by the system or by the user

PRTGRAPH DSPGDF Displays, prints, or plots a graphics data file

STRBGU Starts the Business Graphics Utility (BGU) licensedprogram

PTF APYPTF Applies PTFs to a specified licensed program

DSPPTF Displays or prints the program temporary fixes fora specified licensed program

LODPTF Loads program temporary fixes for a specifiedlicensed program from the service support system,tape, diskette, or a save file on disk

RMVPTF Removes a program temporary fix from a specifiedlicensed program

QRY GO CMDQRY Displays a menu of commands relating to queries

STRQRY Starts the Query function by showing the Querymain menu

WRKQRY Allows you to work with a query definition and torun a query

QRYDE STRDFU Starts the Data File Utility (DFU) program

STRQRY Starts the Query function by showing the Querymain menu

UPDDTA Creates and runs a temporary data file utility (DFU)program, which allows you to update a databasefile

QRYRUN RUNQRY Runs an existing query or a default query if onlythe file name is specified

STRQRY Starts the Query function by showing the Querymain menu

WRKQRY Allows you to work with a query definition and torun a query

A-16 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 377: Iseries

Procedures

System/36 AS/400 AS/400 FunctionREADINFO DSPDOC Allows the user to display a document using the

word processing function of the OfficeVision/400program

REMOVE DLTF Deletes a specified database or device files

DLTMSGF Deletes the specified message file includingmessage descriptions stored in the file

DLTPGM Deletes a compiled program or group of programs

RMVM Removes the specified member from a specifiedphysical or logical file

RENAME RNMDLO Changes the name of a document or folder

RNMOBJ Renames a specified object name and object type

REQUESTX None Function not supported or no longer required onthe AS/400 system

RESPONSE ADDMSGD Describes a message and stores it in a specifiedmessage file

ADDRPYLE Adds a message entry to the system-wide auto-matic message reply list

CHGMSGD Changes an existing message description stored ina specified message file

CHGRPYLE Changes the message ID, comparison data,message, or dump attributes of the reply

MONMSG Monitors the messages sent to the programmessage queue

RMVMSGD Removes a message description from a specifiedmessage file

WRKRPYLE Allows a user to work with reply entries currently inthe system message reply list

RESTEXTN CPYIGCTBL Copies part or all of a double-byte character setfont table from system storage to tape or diskette,or from tape or diskette into system storage

RESTFLDR RSTDLO Restores filed documents, distribution documents,and folders from tape, diskette, or a save file ondisk

RSTLIB Restores user libraries saved to tape, diskette, or asave file on disk

RESTLIBR RSTLIB Restores user libraries saved to tape, diskette, or asave file on disk

RSTS36LIBM Reads a file containing library members, createsdatabase source or data file members on theAS/400 system, and copies the member data fromthe file into each restored member

RESTNRD RSTLIB Restores user libraries saved to tape, diskette, or asave file on disk

Appendix A. System/36 and AS/400 Commands Cross-Reference A-17

Page 378: Iseries

Procedures

System/36 AS/400 AS/400 FunctionRSTOBJ Restores objects to a single library saved from

tape, diskette, or a save file on disk

RESTORE RSTOBJ Restores objects to a single library saved fromtape, diskette, or a save file on disk

RSTS36F Reads a file, (optionally) creates a database phys-ical or logical file (if it does not already exist), andcopies any data into the file

RETRIEVE RSTDLO Restores filed documents, distribution documents,and folders from tape, diskette, or a save file ondisk

RJFILE CVTRJEDTA Converts compressed AS/400 system databasefiles to decompressed database files written eitherto another database or to AS/400 system printerdevice files

STRRJERDR Starts reading a remote job entry (RJE) file

RJTABLE ADDFCTE Adds a forms entry to an existing forms controltable

CRTFCT Creates a forms control table with no entries

CRTFORMDF Creates a form definition from a physical file

ROLLKEYS CHGPRF Changes the values of a user's profile

CHGUSRPRF Changes the values specified in a user profile

SETKBDMAP Sets new key assignments for the Program Atten-tion (PA) and Program Function (PF) keys

RGZFILE CHGPF Changes the attributes of a physical file

CPYF Copies a file including or omitting records

RGZPFM Removes deleted records from a physical filemember

RPGC CRTRPGPGM Creates (compiles) an auto report RPG program

RPGONL STRPGMMNU Starts the programmer menu

STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

RPGP STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRPGMMNU Starts the programmer menu

RPGR STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

A-18 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 379: Iseries

Procedures

System/36 AS/400 AS/400 FunctionRPGSDA STRPDM Calls the Programming Development Manager

(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSDA Starts the screen design aid main menu and allowsusers to create or change a display format interac-tively

RPGSEU STRPDM Calls the Programming Development Manager(PDM) utility, which allows you to work withlibraries, objects, members, and user-definedoptions

STRSEU Calls the source entry utility (SEU) program anddisplays the main menu

RPGX CRTRPGPGM Creates (compiles) an auto report RPG program

SAVE SAVOBJ The Save Object (SAVOBJ) command saves acopy of a single object or a group of objectslocated in the same library. For job queues, outputqueues, data queues, message queues, andlogical files, only the object descriptions are saved,and the contents of the objects are not saved.

SAVS36F Creates a copy of a database physical or logicalfile to diskette or tape magnetic media that can berestored on a System/36 or to a physical file thatcan be sent to a System/36

SAVEEXTN CPYIGCTBL Copies part or all of a double-byte character setfont table from system storage to tape or diskette,or from tape or diskette into system storage

SAVEFLDR SAVDLO Saves the specified documents or folders to tape,diskette, or a save file on disk

SAVLIB Saves libraries to tape, diskette, or a save file ondisk

SAVSECDTA Saves all security information to tape, diskette, orsave file on disk

SAVELIBR SAVLIB Saves libraries to tape, diskette, or a save file ondisk

SAVS36LIBM Saves a copy of source file members on disketteor tape

SAVENRD SAVCHGOBJ Saves a changed object or group of objectslocated in the same library to tape, diskette, or asave file on disk

SAVLIB Saves libraries to tape, diskette, or a save file ondisk

Appendix A. System/36 and AS/400 Commands Cross-Reference A-19

Page 380: Iseries

Procedures

System/36 AS/400 AS/400 FunctionSAVOBJ The Save Object (SAVOBJ) command saves a

copy of a single object or a group of objectslocated in the same library. For job queues, outputqueues, data queues, message queues, andlogical files, only the object descriptions are saved,and the contents of the objects are not saved.

SAVSTG Saves the licensed internal code and the contentsof auxiliary storage to tape

SDA STRSDA Starts the screen design aid main menu and allowsusers to create or change a display format interac-tively

SECDEF CHGSYSVAL Changes the current value of the specified systemvalue

SECEDIT CHGAUTLE Changes user's authority or an authorization list

CHGCFGL Changes a configuration list

CHGDLOAUT Changes the authority to a document or folder

CHGDLOOWN Changes ownership of a document or folder fromone user to another

CHGDSTPWD Changes the Dedicated Service Tools (DST) pass-word

CHGOBJOWN Transfers ownership of an object from one user toanother

CHGPRF Changes the values of a user's profile

CHGPWD Changes a user's password

CHGUSRPRF Changes the values specified in a user profile

CHKPWD Checks the password associated with a user'sprofile

CRTCFGL Creates a list of remote location names and remotelocation identifiers for the specified communicationstype

CRTUSRPRF Creates a user profile to describe a user to thesystem

DLTAUTHLR Deletes an authority holder for an associatedresource

DLTCFGL Deletes a list of remote location names and remotelocation identifiers for the specified communicationstype

DLTUSRPRF Deletes an individual user profile or a group profilefrom the system

DSPDLOAUT Displays a list of users and their authoritiesassigned to a specified document or folder

GRTOBJAUT Grants specific authority for a named object, ageneric group of objects, or all objects

A-20 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Page 381: Iseries

Procedures

System/36 AS/400 AS/400 FunctionRMVAUTLE Removes a user from an authorization list

RMVDLOAUT Removes a user's specific authority to a documentor folder

RVKOBJAUT Deletes specific authorities to an object for a user

RVKUSRPMN Revokes the permission from a user to handle doc-uments and folders for another user

WRKOBJOWN Allows a user to work with a list of objects ownedby a specified user profile

WRKUSRPRF Allows a user to work with a description of anexisting user profile

SECLIST CHGCFGL Changes a configuration list

CHGDEVxxxx Changes a device description where xxxx is thedevice class or type

CRTCFGL Creates a list of remote location names and remotelocation identifiers for the specified communicationstype

CRTDEVxxxx Creates a device description where xxxx is thedevice class or type

DSPAUTHLR Displays all authority holders on the system

DSPAUTLDLO Displays a list of documents and folders whosesecurity is specified on the specified authorizationlist

DSPAUTUSR Displays a list of users and information about thoseusers who are authorized to use the system

DSPDLOAUT Displays a list of users and their authoritiesassigned to a specified document or folder

DSPOBJAUT Displays a list of users assigned to an object

DSPPGMADP Displays a list of pr