AS400 Operations Basic

AS/400 Advanced Series IBM
Operator Tasks –
Multiple Operating Systems
SC21-8384-01
AS/400 Advanced Series IBM
Operator Tasks –
SC21-8384-01
Take Note!
Before using this information and the product it supports, be sure to read the general information under “Notices” on page ix.
Second Edition (November 1996)
This edition applies to the licensed programs IBM System/36 System Support Program Products, (Program 5716-SSP), Release 7
| Modification 5; IBM Operating System/400, (Program 5716-SS1), Version 3 Release 7 Modification 0, and to all subsequent releases
and modifications until otherwise indicated in new editions.
Make sure that you are using the proper edition for the level of the product.
Order publications through your IBM representative or the IBM branch serving your locality. If you live in the United States, Puerto
Rico, or Guam, you can order publications through the IBM Software Manufacturing Solutions at 800+879-2755. Publications are not
stocked at the address given below.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication. You can also mail
your comments to the following address:
IBM Corporation
Attention Department 542
IDCLERK
3605 Highway 52 N
Rochester, MN 55901-7829 USA
or you can fax your comments to:
United States and Canada: 800+937-3430

Other countries: (+1)+507+253-5192
If you have access to Internet, you can send your comments electronically to IDCLERK@RCHVMW2.VNET.IBM.COM; IBMMAIL, to
IBMMAIL(USIB56RZ).
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
 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 to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About Operator Tasks – Multiple Operating Systems (SC21-8384) . . . . . . xi

Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
What You Should Do Before You Use this Book . . . . . . . . . . . . . . . . . . xii
Where to Go for Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
AS/400 System Operation
| Chapter 1. AS/400 System Operations Tasks . . . . . . . . . . . . . . . . . 1-1

What You Need to Know about Your Control Panel . . . . . . . . . . . . . . . . 1-1
IPL Types and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
| Uninterrupted Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Quick Reference to Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
| Additional Information that Applies to the AS/400 System . . . . . . . . . . . . 1-8
OS/400 for the SSP Operator
Chapter 2. Starting the System Unit and OS/400 Operating System . . . 2-1
Using the OS/400 Sign On Display during an IPL . . . . . . . . . . . . . . . . . 2-3
Chapter 3. Stopping the System Unit . . . . . . . . . . . . . . . . . . . . . . 3-1

Stopping the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Chapter 4. The OS/400 System Console . . . . . . . . . . . . . . . . . . . . . 4-1

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

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

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

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Finding OS/400 Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
 Copyright IBM Corp. 1995, 1996 iii

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

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Working with a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Chapter 9. OS/400 System Security . . . . . . . . . . . . . . . . . . . . . . . 9-1

Levels of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Chapter 10. Controlling OS/400 Jobs . . . . . . . . . . . . . . . . . . . . . 10-1

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

Displaying and Changing Device Status . . . . . . . . . . . . . . . . . . . . . . 11-1
Renaming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Displaying and Changing a Device Description . . . . . . . . . . . . . . . . . 11-3
Printing Local Device Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Activating Communications Lines and Controllers . . . . . . . . . . . . . . . . 11-4
Configuring Remote Communications . . . . . . . . . . . . . . . . . . . . . . . 11-5
Using a Switched Communications Line . . . . . . . . . . . . . . . . . . . . . 11-6
Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . . . 12-1
Saving the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Restoring the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Saving the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . . . 12-2
Restoring the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . 12-3
Saving AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Restoring AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Saving Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Restoring Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Chapter 13. Working with Licensed Internal Code and OS/400 Program
Temporary Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
AS/400 Program Maintenance Strategy . . . . . . . . . . . . . . . . . . . . . . 13-1
Ordering LIC and OS/400 PTFs and PTF Information . . . . . . . . . . . . . . 13-2
Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . . . . 14-1

Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . . . . . 14-3
Transferring to an AS/400 Advanced 36 Machine Using the STRM36PRC
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7
iv AS/400 Operator Tasks – Multiple Operating Systems R7.5

SSP for the OS/400 Operator
Chapter 15. Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . 15-1

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

Putting the AS/400 Advanced 36 Machine In a Dedicated State . . . . . . . . 16-1
Stopping an AS/400 Advanced 36 Machine from the SSP System Console . 16-2
Stopping an AS/400 Advanced 36 Machine from the OS/400 Operating
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Chapter 17. Operating the SSP Console and SSP Subconsoles . . . . . 17-1
The SSP Console: A Way of Controlling the AS/400 Advanced 36 Machine 17-1
The SSP Subconsole: A Way of Controlling SSP Printers . . . . . . . . . . . 17-1
Transferring the SSP Console Function to an Alternative SSP Console . . . 17-2
Using the SSP Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Using the Subconsole Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Chapter 18. Handling SSP Messages . . . . . . . . . . . . . . . . . . . . . 18-1

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

Using Help for Commands and Procedures . . . . . . . . . . . . . . . . . . . 19-1
Chapter 20. Printing with SSP . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

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

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Starting an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Ending an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Displaying the Status of an SSP Subsystem . . . . . . . . . . . . . . . . . . . 21-2
Chapter 22. SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Menu Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Badge Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Communications Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Resource Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Working with SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Contents v
Chapter 23. Controlling SSP Jobs . . . . . . . . . . . . . . . . . . . . . . . 23-1
Working With Current Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Working with the History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Chapter 24. Working with SSP Devices and Communications . . . . . . 24-1

Displaying Communications Lines and Controllers . . . . . . . . . . . . . . . . 24-1
Configuring Remote Communications Lines . . . . . . . . . . . . . . . . . . . 24-1
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine

Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
Saving and Restoring an AS/400 Advanced 36 Machine . . . . . . . . . . . . 25-1
Saving and Restoring the SSP Operating System, Licensed Programs, and
Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
Chapter 26. Working with SSP Program Temporary Fixes . . . . . . . . 26-1

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

Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1
Using Remote Work Station Support . . . . . . . . . . . . . . . . . . . . . . . 27-1
AS/400 System Common Operator Tasks
Chapter 28. Problem Handling . . . . . . . . . . . . . . . . . . . . . . . . . 28-1

Hardware Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1
Handling AS/400 Advanced 36 Machine Error Codes . . . . . . . . . . . . . . 28-9
Chapter 29. System-to-System Communications - ILAN

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

Configurations and Machines . . . . . . . . . . . . . . . . . . . . . . . . . . 30-1
Using the Work with AS/400 Advanced 36 Machine Command . . . . . . . . 30-1
Using the Work with AS/400 Advanced 36 Machine Configuration Command 30-8
vi AS/400 Operator Tasks – Multiple Operating Systems R7.5

Summary Table of CL Commands for Managing AS/400 Advanced 36
Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13
Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-1

Configuration That Exists Immediately after Installation . . . . . . . . . . . . . 31-2
Defining a Communications Line or a LAN . . . . . . . . . . . . . . . . . . . . 31-4
Defining a Diskette Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-8
Defining a Tape or CD-ROM Device . . . . . . . . . . . . . . . . . . . . . . . 31-10
Defining Printers and Display Stations Using Device Mapping . . . . . . . . 31-12
Defining Printers and Display Stations Using Controller Mapping . . . . . . 31-17
Changing a Workstation Controller from Controller Mapping to Device
Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-22
Defining Whether SSP or OS/400 Controls SSP Printer Output . . . . . . . 31-26
Defining Whether SSP or OS/400 Controls the Display Station . . . . . . . 31-36
Validating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 31-39
Chapter 32. Displaying Information About an AS/400 Advanced 36

Configuration and Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1
Displaying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-1
Displaying a Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-2
Other Useful Information
Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1

System/36 Procedures to AS/400 Commands Cross-Reference . . . . . . . . A-1
System/36 Control Commands to AS/400 Commands Cross-Reference . . . A-27
System/36 OCL Statements to AS/400 Commands Cross-Reference . . . . . A-32
| Appendix B. Displaying and Setting the IPL Mode For a 9402 Model 436 B-1
Displaying the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Setting the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Appendix C. Performance Considerations . . . . . . . . . . . . . . . . . . C-1

Understanding Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Understanding Prestart Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Setting Attributes For the AS/400 Advanced 36 Server Job . . . . . . . . . . C-3
Setting attributes for the AS/400 Advanced 36 SLIC Tasks . . . . . . . . . . C-5
Setting Attributes for the AS/400 Advanced 36 Prestart Jobs . . . . . . . . . C-6
Appendix D. Using Electronic Customer Support . . . . . . . . . . . . . . D-1

Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Reviewing Status of an Open Problem . . . . . . . . . . . . . . . . . . . . . . D-3
Ordering PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Appendix E. Preparing SSP for Dedicated State . . . . . . . . . . . . . . . E-1
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Contents vii
viii AS/400 Operator Tasks – Multiple Operating Systems R7.5
Notices
References in this publication to IBM products, programs, or services do not imply that IBM intends to
make these available in all countries in which IBM operates. Any reference to an IBM product, program,
or service is not intended to state or imply that only that IBM product, program, or service may be used.
Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent
product, program, or service may be used instead of the IBM product, program, or service. The evaluation
and verification of operation in conjunction with other products, except those expressly designated by IBM,
are the responsibility of the user.
IBM may have patents or pending patent applications covering subject matter in this document. The fur-
nishing of this document does not give you any license to these patents. You can send license inquiries,
in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY
10594, U.S.A.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact the software interop-
erability coordinator. Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
Address your questions to:
IBM Corporation
Software Interoperability Coordinator
3605 Highway 52 N
Rochester, MN 55901-7829 USA
This publication could contain technical inaccuracies or typographical errors.
This publication may refer to products that are announced but not currently available in your country. This
publication may also refer to products that have not been announced in your country. IBM makes no
commitment to make available any unannounced products referred to herein. The final decision to
announce any product is based on IBM's business and technical judgment.
This publication contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
This publication contains small programs that are furnished by IBM as simple examples to provide an
illustration. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot
guarantee or imply reliability, serviceability, or function of these programs. All programs contained herein
are provided to you "AS IS". THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED.
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
 Copyright IBM Corp. 1995, 1996 ix

Advanced Peer-to-Peer Networking OfficeVision/400
Advanced Function Printing Operating System/400
AFP Operational Assistant
Apple OS/400
Application Development Q&A
Application System/400 Question
APPN RPG/400
AS/400 RM/COBOL-85
C/400 SystemView
CICS System/36
DisplayWrite System/38
FORTRAN/400 SUN
IBM TRN
IMS Ultimedia
Information Assistant 400
IPX 486
PSF
Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Cor-
poration.
PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license.
UNIX is a registered trademark in the United States and other countries licensed exclusively through
X/Open Company Limited.
C-bus is a trademark of Corollary, Inc.
Other company, product, and service names, which may be denoted by a double asterisk (**), may be
trademarks or service marks of others.
x AS/400 Operator Tasks – Multiple Operating Systems R7.5

About Operator Tasks – Multiple Operating Systems
(SC21-8384)
Who Should Use This Book

| This book is intended for use by a system operator who operates an AS/400
| system on which SSP and OS/400 operating systems are both installed.
| For information about operating an AS/400 system that is running the System
| Support Program (SSP) operating system, where the SSP operating system is the
| only operating system installed see the Operating Your Computer–SSP Operating
System book, SC21-8297.
For information about operating an AS/400 system with only OS/400 installed, see
the System Operation book, SC41-4203.
That part of the system that contains the SSP operating system and related data
and programs is referred to as an AS/400 Advanced 36 machine.
Many of the tasks that were done on a System/36 work the same on an AS/400
Advanced 36 machine. The tasks that were previously done using OS/400 are
unchanged. However, there are some things the OS/400 operator will need to
know in order to do tasks with the AS/400 Advanced 36 machine. There are also
additional OS/400 CL commands. As the system operator, you have many respon-
sibilities.
This book provides information about day-to-day tasks, such as how to do the
following:
Work with jobs or printer output.
Respond to messages sent to the system operator message queue
(QSYSOPR), change message queues, and respond to error messages.
Use the support functions available on the AS/400 system.
Clean up your system periodically to improve performance and maintain good
running condition.
Save and restore all of the important data that you keep on your system.
Work with the system unit control panel and OS/400 console.
Start and stop the AS/400 system.
Start and stop each AS/400 Advanced 36 machine
Pass through to SSP or OS/400
Handle OS/400 and SSP messages.
| Install program temporary fixes (PTFs).
Use OS/400 commands to do tasks.
Print.
Work with subsystems.
 Copyright IBM Corp. 1995, 1996 xi

Change security levels with OS/400.
Use security with SSP.
Transfer to an AS/400 Advanced 36 machine
Run SSP procedures from an OS/400 display station.
Control SSP jobs.
Use System to System Communications.
Change your AS/400 Advanced 36 machine configuration.
Display and set the IPL Mode.
Use Electronic Customer Support
The book is divided into several parts:

| Part 1: AS/400 System Operation
– Contains information on how to use the system control panel.
– Contains a quick reference table of where to find operator tasks.
Part 2: OS/400 for the SSP Operator
– Contains information on tasks you can do to manage the OS/400 part of
the system.
Part 3: SSP for the OS/400 Operator
– Contains information on tasks you can do to manage the AS/400 Advanced
36 machines that are on the system.
Part 4: AS/400 Advanced 36 Common Operator Tasks
– Contains information on handling problems.
– Contains information on managing AS/400 Advanced 36 system operations.
– Contains information on managing system-to-system communications using
an Internal Local Area Network (ILAN).
– Contains information on managing AS/400 Advanced 36 machines and
their configurations.
Part 5: Other Useful Information
– Appendix A: System/36 and AS/400 Commands Cross-Reference
– Appendix B: Control Language Commands
– Appendix C: Displaying and Setting the IPL Mode
– Appendix D: Performance Considerations
– Appendix E: Using Electronic Customer Support
What You Should Do Before You Use this Book

To use this book effectively, you should have:
Completed the installation instructions in the Getting SSP and OS/400 Installed
and Running book, SC21-8377.
Read the General Information for SSP Operating System book, SC21-8299.
xii AS/400 Operator Tasks – Multiple Operating Systems R7.5

Learned how to interpret the display indicators and the control panel on the
display station that is attached to your system.
Learned how to use the keyboard that is attached to your display station.
Where to Go for Other Information

For operating instructions for your display station, refer to the operator's guide for
the display station that is attached to your system.
For information about OS/400 system operator tasks that are not included in this
book, see the System Startup and Problem Handling book, SC41-4206. That book
contains information about:
Loading Program Temporary Fixes (PTFs) for (OS/400)
Problem Handling (for OS/400)
You may need to refer to other IBM books for more specific information about a
particular topic.
For information about Advanced 36 publications, see the Advanced 36 Information

Directory book, SC21-8292.
For information about other AS/400 publications (except Advanced 36), see either
of the following:
The Publications Reference book, SC41-4003, in the AS/400 Softcopy Library.
The AS/400 Information Directory, a unique, multimedia interface to a
searchable database containing descriptions of titles available from IBM or from
selected other publishers. The AS/400 Information Directory is shipped with
the OS/400 operating system at no charge.
For a list of related publications, see the Bibliography.
Note: AS/400 book numbers start with SC41. SSP book numbers start with
SC21.
If you are using your AS/400 system in a System/36 environment, start the AS/400
system using an attended initial program load (IPL), and select the kind of environ-
ment you want to use. When you have completed the IPL, see the following
manuals for information about the System/36 environment:
System/36 Environment Programming, SC41-4730
System/36 Environment Reference, SC41-4731
About Operator Tasks – Multiple Operating Systems (SC21-8384) xiii

xiv AS/400 Operator Tasks – Multiple Operating Systems R7.5
AS/400 System Operation
| Chapter 1. AS/400 System Operations Tasks . . . . . . . . . . . . . . . . . 1-1
What You Need to Know about Your Control Panel . . . . . . . . . . . . . . . . 1-1
Control Panel Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
IPL Types and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
| Uninterrupted Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Quick Reference to Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
| Additional Information that Applies to the AS/400 System . . . . . . . . . . . . 1-8
 Copyright IBM Corp. 1995, 1996

AS/400 Operator Tasks – Multiple Operating Systems R7.5
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 Panel

System operators and service representatives use the control panel to:
Do an initial program load (IPL)
Do problem analysis
Stop the system if the system cannot be stopped from a workstation.
| Figure 1-1 shows the control panel for a 9402 Model 436 with the cover closed.
| Other AS/400 models can differ in appearance.
D C
RV3P218-0
Figure 1-1. Control Panel with Cover Closed
When the control panel is closed, two lights are visible:

The processor activity light .C/
The system attention light .D/
These lights are defined on page 1-3. To use the control panel, you must open the
cover. To open the cover, do as follows:
 Copyright IBM Corp. 1995, 1996 1-1

Control Panel
1. If you have a lock on your control panel, unlock the cover.

2. Find the place on your control panel cover on the side of the machine that is
indented.
If you have difficulty locating the indentation, look at the diagram in Figure 1-1
on page 1-1.
3. Use your thumb to open the control panel.
| Figure 1-2 shows the control panel for a 9402 Model 436 without the cover. Other
| AS/400 models can differ in appearance.
B A
D C
Function/Data
Enter
F G
Function
01 Display Selected IPL
02 Select IPL
03 Start IPL
04 Lamp Test
11 System Reference Code
RTSP035-2
Figure 1-2. Control Panel Without a Cover
Control Panel Details

.A/ Power On light:
The light comes on and stays on when there is power to the system unit.
The Power On light blinks when:
The system is being started up
The system is being manually turned off
Note: When the Power Down System (PWRDWNSYS) command or the
options on the Power On and Off Tasks (POWER) menu are used, the
Power On light does not blink.
.B/ Power pushbutton: Use the power pushbutton to start the system and stop
the system. To start the system, press the pushbutton once. To stop or
power off the system, press the pushbutton twice.
1-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Control Panel
Power on is allowed in Manual or Normal mode. Power off is allowed in

Manual mode only.
Note: In most cases, to stop the system, use the Power Down System
(PWRDWNSYS) command on any command line of your OS/400
display station after stopping all AS/400 Advanced 36 machines.
If you use the Power pushbutton to turn off the system, errors may
occur with data files. For more information on stopping the
system, see “Stopping the AS/400 System” on page 3-1.
.C/ Processor Active light: The system unit has one Processor Active light. The
light blinks when programs are running that use the processor.
.D/ System Attention light: This light comes on when the system requires oper-
ator attention, such as correcting a severe system failure. For information
about correcting system problems, see the System Startup and Problem Han-
dling book, SC41-4206.
.E/ Function/Data display: The same display and pushbuttons are used for both
function and data. When you press a Select pushbutton (.F/), the function
numbers on the Function/Data display increase or decrease. For example, 01
becomes 02 and A M becomes B M.
When you press the Enter pushbutton (.G/), displayed data may disappear.
Note: For example, when you press the Enter pushbutton, 02 B M
becomes 02.
Only the numbers that can be used in the present mode are displayed. The
Function/Data display can display up to 8 digits. The selected function is not
processed until the Enter pushbutton (.G/) is pressed.
System reference codes or other information from the processing unit or
control panel are also shown in the Function/Data display.
Note: If the system attention light comes on, it indicates the system requires
operator attention. In this case, a code of 11-3 becomes the System
Reference Code (SRC) when you push the Enter pushbutton. An
example of an SRC is A6ððð9ð2.
.F/ Select pushbuttons: There are two select pushbuttons. These buttons are
used to increase or decrease the number shown in the Function/Data display.
The select pushbutton on the left increases the values in the Function/Data
display. The select pushbutton on the right decreases the values in the
Function/Data display.
Either pushbutton can be used to change the data shown in the Function/Data
display when you are selecting an initial program load (IPL) type and mode.
The IPL type (A, B, C or D) and the IPL mode (M or N) can be selected by
using Function 02. To select IPL type, do the following:
1. Press one of the Select pushbuttons until 02 is visible in the function/data
display area.
2. Press the Enter pushbutton (.G/).
3. Press one of the Select pushbuttons until the IPL type and mode you
want is visible in the function/data display area.
4. Press the Enter pushbutton.
Chapter 1. AS/400 System Operations Tasks 1-3

Control Panel
5. Press one of the select pushbuttons until ð1 is visible in the function/data

display area.
6. Press the Enter pushbutton.
ð1 and the IPL type and mode are displayed in the function/data display.
Attention: Do not use Function code ð8 unless it is an emergency. This is the

emergency power off code. Use of Function code 08 may cause unpredictable
results.
.G/ Enter pushbutton: The Enter pushbutton is used to send function informa-
tion shown in the Function/Data display to the processing unit or to save the
type of IPL type and mode you selected.
Note: You can also display the IPL type and mode. To do so, follow steps 5
and 6 on page 1-4 described under the .F/ Select pushbuttons topic.

IPL Types and Modes
IPL Types and Modes

The IPL types and modes are:
AM Performs a Manual IPL from the A side of the disk. This mode may be
used when applying or removing Licensed Internal Code (LIC) PTFs. It
can also be used to power off the system.
Use this type and mode only under the direction of your support repre-
sentative.
AN Performs a Normal IPL from the A side of the disk.
This mode should only be used when B N does not work and you are
told to do so by your support representative.
BM Performs a Manual IPL from the B side of the disk. This mode should
only be used when an attended IPL must be performed or you need to
power off the system. This type of IPL is used when you need to
change the system date and time permanently.
BN Performs a normal IPL from the B side of the disk. This is the type and
mode used most of the time. It is also the mode the system must be in
if you want to do an unattended IPL.
CM Allows service representatives to perform a special IPL. This mode is
for use only by service representatives. Never IPL in this type and
mode.
CN Allows service representatives to perform a special IPL. This mode is
for use only by service representatives. Never IPL in this type and
mode.
DM Performs a manual IPL from either CD-ROM or tape. This mode is
used to install Licensed Internal Code and the OS/400 operating system
in attended mode. This is the most often used IPL type and mode for
installation.
DN Performs a normal IPL from either CD-ROM or tape. This mode is used
to install Licensed Internal Code and the OS/400 operating system in
unattended mode.
Manual When the mode is set to Manual (M), the system allows you to do all
manual IPLs, such as an operator-attended IPL from disk, CD-ROM or
tape. Manual mode also allows you to do some manual control func-
tions, such as selecting an IPL type and mode or displaying the kind of
IPL that the system is set to run. However, in manual mode, you
cannot do a remote IPL, an IPL by date and time, or an IPL after a
power failure.
Note: You should set the mode to Manual only when it is necessary.
This ensures that no one accidentally presses the Power push-
button and causes the system to stop.
Normal The Normal mode allows you to turn the power on and then automat-
ically start the system in any of the following ways:
IPL remotely
IPL by date and time
IPL after a power failure

Uninterrupted Power System
Note: Your system should be in Normal mode most of the time.
The table in Figure 1-3 on page 1-6 summarizes what operations you can do in
the Manual (M) or Normal (N) IPL modes:
Figure 1-3. Operation Summary for Manual and Normal Modes

Manual Normal
Operation Mode Mode
Turn on system (Power Allowed Allowed
pushbutton)
Power off (Power push- Allowed Not allowed
button)
Display Selected IPL Allowed Allowed
Select IPL Allowed Allowed
Start IPL Allowed Not allowed
Display system reference Allowed Allowed
code
Remote IPL Not allowed Program control allowed
Timed IPL Not allowed Program control allowed
Restart IPL (after power Not allowed Program control allowed
failure)
Power Down System Program control allowed Program control allowed
command
Note: You can display the kind of IPL the system is set to do when the system is
in any mode.
If you want to stop the system when the mode is set to Normal, use the Power
Down System (PWRDWNSYS) command at any display station after you stop the
AS/400 Advanced 36 machines. You must have QSYSOPR authority to use the
Power Down System (PWRDWNSYS) command.
| Uninterrupted Power System

| The AS/400 system supports an external uninterruptible power system (UPS). You
can install UPS to protect your AS/400 system from temporary power loss. Your
AS/400 system unit and the OS/400 console should be connected to the UPS. If
the UPS is installed, it automatically activates when there is a utility power loss.
The UPS provides full operating power to all system components for a short time.

Quick Reference
Quick Reference to Operator Tasks

This table provides information on where to find out how to do OS/400 and SSP
operator tasks.
Figure 1-4 (Page 1 of 2). Quick Reference to OS/400 and SSP Operator Tasks
Operator Task OS/400 Operating System SSP Operating System
Starting the System Chapter 2, “Starting the System Chapter 15, “Starting an AS/400
Unit and OS/400 Operating Advanced 36 Machine”
System”
Stopping the System Chapter 3, “Stopping the System Chapter 16, “Stopping an AS/400
Unit” Advanced 36 Machine”
Understanding Consoles and Sub- Chapter 4, “The OS/400 System Chapter 17, “Operating the SSP
consoles Console” Console and SSP Subconsoles”
Handling Messages Chapter 5, “Handling OS/400 Chapter 18, “Handling SSP
Messages” Messages”
Using Commands to Do Tasks Chapter 6, “Using OS/400 CL Chapter 19, “Using SSP Com-
Commands to Do Tasks” mands and Procedures to Do
Tasks”
Printing Chapter 7, “Printing with OS/400” Chapter 20, “Printing with SSP”
Working with Subsystems Chapter 8, “Working with OS/400 Chapter 21, “Working with SSP
Subsystems” Subsystems”
Understanding Security Chapter 9, “OS/400 System Chapter 22, “SSP Security”
Security”
Controlling Jobs Chapter 10, “Controlling OS/400 Chapter 23, “Controlling SSP
Jobs” Jobs”
Working with Devices and Commu- Chapter 11, “Working with OS/400 Chapter 24, “Working with SSP
nications Devices and Communications” Devices and Communications”
Saving and Restoring Chapter 12, “Saving and Restoring Chapter 25, “Saving and Restoring
OS/400 and OS/400 Objects” the AS/400 Advanced 36 Machine
Information”
Working with Program Temporary Chapter 13, “Working with Chapter 26, “Working with SSP
Fixes (PTFs) Licensed Internal Code and Program Temporary Fixes”
OS/400 Program Temporary Fixes”
Transferring to an AS/400 Chapter 14, “Transferring to an Not applicable
Advanced 36 machine AS/400 Advanced 36 Machine”
Establishing communication with a Not applicable Chapter 27, “Establishing a Com-
remote workstation munications Link for Remote
Workstations”
Solving Problems Chapter 28, “Problem Handling” Chapter 28, “Problem Handling”
Establishing Internal System Com- Chapter 29, “System-to-System Chapter 29, “System-to-System
munications Communications - ILAN Communications - ILAN
Communications” Communications”
Managing Your AS/400 Advanced Chapter 30, “Using CL Commands Chapter 30, “Using CL Commands
36 Machines and Their Configura- to Manage AS/400 Advanced 36 to Manage AS/400 Advanced 36
tions. (For example, creating, Configurations and Machines” Configurations and Machines”
starting, or deleting an AS/400
Advanced 36 machine)

Quick Reference
Figure 1-4 (Page 2 of 2). Quick Reference to OS/400 and SSP Operator Tasks
Operator Task OS/400 Operating System SSP Operating System
Changing an AS/400 Advanced 36 Chapter 31, “Changing Your Chapter 31, “Changing Your
Configuration AS/400 Advanced 36 Machine AS/400 Advanced 36 Machine
Configuration” Configuration”
Displaying Information About an Chapter 32, “Displaying Informa- Chapter 32, “Displaying Informa-
AS/400 Advanced 36 Configuration tion About an AS/400 Advanced 36 tion About an AS/400 Advanced 36
and Machine Configuration and Machine” Configuration and Machine”
Using Media Chapter 4 of the System Startup Chapter 7 of the Operating Your
and Problem Handling book, Computer–SSP Operating System
SC41-4206. book, SC21-8297.
| Additional Information that Applies to the AS/400 System

Other Useful Information is included in the following:.
Appendix A, “System/36 and AS/400 Commands Cross-Reference”
Appendix B, “Displaying and Setting the IPL Mode For a 9402 Model 436”
Appendix C, “Performance Considerations”
Appendix D, “Using Electronic Customer Support”
Appendix E, “Preparing SSP for Dedicated State”

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

Stopping the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Preparing to Stop the System . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Using the POWER Menu to Stop the System . . . . . . . . . . . . . . . . . . 3-2
Using the Power Down System Command to Stop the System . . . . . . . . 3-3
Using the Power Pushbutton to Stop the System . . . . . . . . . . . . . . . . 3-4
Chapter 4. The OS/400 System Console . . . . . . . . . . . . . . . . . . . . . 4-1

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

Most Common Types of OS/400 Messages . . . . . . . . . . . . . . . . . . . . 5-1
Displaying OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Finding Additional Information about Your Messages . . . . . . . . . . . . . 5-3
Identifying Messages from the System . . . . . . . . . . . . . . . . . . . . . . . 5-5
Message Severity Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
How to Handle Break Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Displaying OS/400 System Operator Messages . . . . . . . . . . . . . . . . . . 5-7
Your User Profile Message Queue . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Responding to OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Working with OS/400 Message Queues . . . . . . . . . . . . . . . . . . . . . . 5-10
Changing a Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Handling OS/400 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Handling Important System Messages in the QSYSMSG Message Queue 5-14
Creating the QSYSMSG Message Queue . . . . . . . . . . . . . . . . . . . 5-14
Error Messages on Menus and Displays . . . . . . . . . . . . . . . . . . . . 5-15
Using the Work with Problems Command . . . . . . . . . . . . . . . . . 5-15
Understanding OS/400 Keyboard Error Messages . . . . . . . . . . . . . . . . 5-15
Sending OS/400 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Using the Send Message Command to Send a Message . . . . . . . . . . 5-16
Using the Send Break Message Command to Send a Message . . . . . . 5-17
Chapter 6. Using OS/400 CL Commands to Do Tasks . . . . . . . . . . . . 6-1

CL Commands — Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Using Operational Assistant Displays . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Using Assistance Levels and User Profiles . . . . . . . . . . . . . . . . . . . . . 6-3
Changing Assistance Level Displays . . . . . . . . . . . . . . . . . . . . . . . 6-4
Changing Assistance Levels Temporarily — Examples . . . . . . . . . . . . 6-5
Changing Assistance Levels in Your User Profile . . . . . . . . . . . . . . . . 6-7
Using CL Commands with the Operational Assistant Displays . . . . . . . . 6-8
Doing Specific Tasks (GO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Menus for System Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Chapter 7. Printing with OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

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

Printer Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Finding OS/400 Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Getting to the Work with Printer Output Display Using Operational Assistant 7-3
Getting to the Work with Printer Output Display Using a CL Command . . . 7-3
Using the Work with Printer Output Display to Find Output . . . . . . . . . . 7-4
Understanding Printing Problems . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Printing Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Managing Printed Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Holding Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Releasing Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Deleting Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Changing Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
What to Do if the Printer Output Is Not Already Printing . . . . . . . . . . . . 7-8
Assigning Printer Output to a Printer . . . . . . . . . . . . . . . . . . . . . . . 7-9
Working with Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Starting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Stopping a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Restarting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Answering Printer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Changing Forms on a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Working with Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Working with All Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Comparing System/36 Print Commands to OS/400 Print Commands . . . . . 7-15
Chapter 8. Working with OS/400 Subsystems . . . . . . . . . . . . . . . . . 8-1

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
OS/400 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
SSP Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Working with a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Working with Subsystem Descriptions . . . . . . . . . . . . . . . . . . . . . . 8-2
Chapter 9. OS/400 System Security . . . . . . . . . . . . . . . . . . . . . . . 9-1

Levels of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Changing the Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Chapter 10. Controlling OS/400 Jobs . . . . . . . . . . . . . . . . . . . . . 10-1

Submitting Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Submitting a Batch Job to Run Immediately . . . . . . . . . . . . . . . . . . 10-2
Scheduling a Batch Job to Run Later . . . . . . . . . . . . . . . . . . . . . 10-2
Changing a Job Schedule to Run at a Different Date or Time . . . . . . 10-3
Scheduling a Job Using Job Schedule Entries . . . . . . . . . . . . . . . 10-3
Adding a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Saving a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Removing a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . 10-4
Changing a Job Schedule Entry . . . . . . . . . . . . . . . . . . . . . . . 10-5
Holding and Releasing a Job Schedule Entry . . . . . . . . . . . . . . . 10-5
Scheduling a Batch Job to Start an AS/400 Advanced 36 Machine . . . 10-5
Working with Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Displaying Batch Jobs of Other Users . . . . . . . . . . . . . . . . . . . . . 10-6
Displaying All Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Displaying Batch Jobs by Status . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Holding a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Releasing a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Ending a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Working with Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Looking at Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Holding a Job Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Releasing a Job Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Working with Unassigned Job Queues . . . . . . . . . . . . . . . . . . . . 10-11
Working with Signed-On Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Displaying Signed-On Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Creating a Customized Work with User Jobs Command . . . . . . . . . . 10-12
Signing Users Off the System . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Finding Signed-On Users and Sorting the User List . . . . . . . . . . . . 10-14
Finding Additional Information about Signed-On Users . . . . . . . . . . 10-14
Sending Messages to Signed-On Users . . . . . . . . . . . . . . . . . . . 10-14
Displaying Detailed Job Information . . . . . . . . . . . . . . . . . . . . . . . 10-14
Displaying Job Status Attributes . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Displaying Job Definition Attributes . . . . . . . . . . . . . . . . . . . . . . 10-15
Displaying Job Run Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Displaying the Call Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Displaying Open Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Changing How a Job Is Run . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Changing a Job’s Priority on a Job Queue . . . . . . . . . . . . . . . . . 10-16
Moving a Job to a Different Job Queue . . . . . . . . . . . . . . . . . . . 10-17
Changing How an Active Job Is Run . . . . . . . . . . . . . . . . . . . . . 10-17
Changing a Job’s Print Priority . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Assigning a Job to a Different Output Queue . . . . . . . . . . . . . . . . 10-18
Working with Job Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Displaying a Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Printing a Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Changing the Logging Level for a Job . . . . . . . . . . . . . . . . . . . . 10-20
Filtering Messages from the Job Log . . . . . . . . . . . . . . . . . . . . . 10-20
Sending Job Log Output Files to a Separate Output Queue . . . . . . . 10-21
Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1

Device Status Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Renaming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Considerations for Renaming Devices . . . . . . . . . . . . . . . . . . . . . 11-2
Displaying and Changing a Device Description . . . . . . . . . . . . . . . . . 11-3
Activating Communications Lines and Controllers . . . . . . . . . . . . . . . . 11-4
Configuring Remote Communications . . . . . . . . . . . . . . . . . . . . . . . 11-5
Using a Switched Communications Line . . . . . . . . . . . . . . . . . . . . . 11-6
Using Manual Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Using Manual Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Using Manual Answer for Countries Other Than the United States . . . . 11-7
Chapter 12. Saving and Restoring OS/400 and OS/400 Objects . . . . . 12-1
Saving the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Restoring the Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Saving the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . . . 12-2
Restoring the OS/400 Operating System . . . . . . . . . . . . . . . . . . . . . 12-3
Saving AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Restoring AS/400 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Saving Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Saving Objects in Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Changed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Documents, Folders, and Mail . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Saving Licensed Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Saving Specific Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Saving Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Restoring Individual OS/400 Objects . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Restoring Objects in Directories . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Restoring Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Restoring Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Restoring Changed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Restoring Documents, Folders, and Mail . . . . . . . . . . . . . . . . . . . . 12-6
Restoring Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Restoring Licensed Programs . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Restoring Specific Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Restoring User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Restoring Object Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Chapter 13. Working with Licensed Internal Code and OS/400 Program
Temporary Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
AS/400 Program Maintenance Strategy . . . . . . . . . . . . . . . . . . . . . . 13-1
Preventive Service (Cumulative PTF Packages) . . . . . . . . . . . . . . . 13-1
Corrective Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Ordering LIC and OS/400 PTFs and PTF Information . . . . . . . . . . . . . . 13-2
Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . . . . 14-1

Important Information about Transferring . . . . . . . . . . . . . . . . . . . 14-1
Restrictions on Transfers using the TFRM36 and STRM36PRC Commands 14-1
Transferring to an AS/400 Advanced 36 Machine Using TFRM36 . . . . . . . 14-3
Transferring to an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . 14-3
Using the TFRM36 Command — Examples . . . . . . . . . . . . . . . . 14-4
| How to Allow for Automatic Sign-On . . . . . . . . . . . . . . . . . . . . . . 14-5
| Selecting the Correct User Profile . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Transferring to an AS/400 Advanced 36 Machine Using the STRM36PRC
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Using the STRM36PRC Command . . . . . . . . . . . . . . . . . . . . . . . 14-6
Running an SSP Procedure from OS/400 — Examples . . . . . . . . . 14-7
Transferring to an AS/400 Advanced 36 Machine using STRPASTHR . . . . 14-7
Running the STRPASTHR command: . . . . . . . . . . . . . . . . . . . . . 14-8
Transferring to an AS/400 Advanced 36 Machine Using the
STRPASTHR Command — Examples . . . . . . . . . . . . . . . . . . . 14-8

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

System
| This chapter contains directions on how to start a system unit for a 9402 model 436
| that contains both the SSP and OS/400 operating systems. For directions on how
| to start other models, see the System Startup and Problem Handling book,
| SC41-4206.
| Note: You can run OS/400 simultaneously with as many as three AS/400
| Advanced 36 machines.
| When you start the system unit, you are starting OS/400 and any AS/400 Advanced
36 machines that are set up to automatically start. For information on starting
AS/400 Advanced 36 machines, see Chapter 15, “Starting an AS/400 Advanced 36
Machine.”
| Note: To perform the tasks in this chapter, you must have OS/400 installed on
| your system. If you have SSP installed on your system and OS/400 is not
| installed, see the Getting SSP and OS/400 Installed and Running book,
| SC21-8377.
To start the system, turn the system power on by pressing the white power push-
button once.
This does an initial program load (IPL). During an IPL, system programs are
loaded from the system auxiliary storage and the system hardware is checked.
When the IPL is finished, the AS/400 Sign On display is shown on all workstations
available to OS/400. For information on assigning workstations to OS/400 or SSP,
see “Defining Whether SSP or OS/400 Controls the Display Station” on
page 31-36.
The following situations typically require an IPL:

Starting normal system operations
Starting a remote system
Changing configuration options
Recovering after a power failure
When your system is sent to you, it is set to do a normal or unattended IPL. An

unattended IPL is done automatically by the system after the power to the system
is turned on.
An attended IPL shows various displays on the display station used for the OS/400
console and allows you to change configuration options or change certain system
values to affect how the system runs.
The table in Figure 2-1 on page 2-1 is a summary of how to do IPLs and what the
IPL mode should be set to on the system control panel.

Figure 2-1. Performing IPLs

System State Unattended IPL Attended IPL
Running 1. Set IPL mode to Normal. 1. Set IPL mode to Manual.
2. Stop any AS/400 Advanced 36 2. Stop any AS/400 Advanced 36 machines
machines that are running. that are running.
3. Set QIPLTYPE system value to 0 3. Type PWRDWNSYS *IMMED
(Unattended). RESTART(*YES) on any command line
and press Enter.
4. Type PWRDWNSYS *IMMED
RESTART(*YES) on any command 4. Follow the display on the console to
line and press Enter. complete the IPL.
5. Set the mode to Normal.
Not Running 1. Set IPL mode to Normal. 1. Set IPL mode to Manual.
2. Power on all devices. 2. Power on all devices.
3. Press the Power Pushbutton Once. 3. Press the Power Pushbutton Once.
4. Follow the directions on the OS/400
console to complete the IPL.
5. Set the mode to Normal.
Note: Always set the mode to Normal after the IPL is finished.
For more information on the following IPL options, see the System Startup and
Problem Handling book, SC41-4206.
Setting Up Your Automatic Power On and Off Schedules
Starting a Remote System
Changing Your System during IPL
System Password

Using the OS/400 Sign On Display during an IPL
à@ ð
Sign On
System . . . . . : SYSTEMð1
Subsystem . . . . : QBASE
Display . . . . . : DSPð1
User . . . . . . . . . . . . . . __________
Password . . . . . . . . . . . .
Program/procedure . . . . . . . . __________
Menu . . . . . . . . . . . . . . __________
Current library . . . . . . . . . __________
Figure 2-2. Sign On Display
To sign on the OS/400 system:

1. Type your user ID, your password (if security is active), and fill in any of the
optional entry fields you want to use. Use the Tab key to move the cursor from
field to field on the display.
Notes:
a. The Password field is shown only if password security is active on the
system and the security level is higher than 10.
b. In the top right corner of the Sign On display the following are shown.
The name of the system you are using
The subsystem the system is using
For more information on OS/400 subsystems, see Chapter 8, “Working
with OS/400 Subsystems.”
The workstation identifier (ID)
2. Press Enter.
If this is an attended IPL, the IPL Options display is shown. The IPL options
display is used to clear job logs or spool files and to set the system time and
date fields. For more information about the IPL Options display, see the
System Startup and Problem Handling book, SC41-4206.
If this is an unattended IPL, (depending on what options you select on this
display or what is defined in your user profile), one or more of the following
occurs:
The AS/400 Main Menu is shown.
Another menu is shown.
A program or procedure is run.
A current library is inserted into your library list.
If you specify a program or procedure to run and a menu to be shown, the
program or procedure is run first and then the menu is shown.
Now that your system is up and running be aware that:
The Operational Assistant* displays are now the default.
Chapter 2. Starting the System Unit and OS/400 Operating System 2-3
The system cleanup functions are automatically started with default values.
For more information about customizing the cleanup function, see chapter 8
of the System Operation book, SC41-4203.
The Attention key program defaults to display the Operational Assistant
(ASSIST) menu.
For more information on signon displays, see the System Startup and Problem
Handling book, SC41-4206.

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

This chapter contains directions on how to stop the system unit.
When you stop the system unit, you are stopping OS/400 and any AS/400
Advanced 36 machines that are not already stopped.
Attention: If you power off the system unit without stopping the AS/400 Advanced
36 machines,
Jobs running under SSP will end abnormally.
SSP files will not be closed and may be in an unknown state.
For information on stopping AS/400 Advanced 36 machines, see Chapter 16,

“Stopping an AS/400 Advanced 36 Machine.”

You can stop the system in several different ways:
POWER menu
Power Down System (PWRDWNSYS) command
Power Pushbutton
Preparing to Stop the System

1. Make sure all batch jobs are finished and all users are signed off.
2. Check to make sure no AS/400 Advanced 36 machines are currently active.
a. Type
WRKM36 M36(\ALL/\ALL)
b. Press Enter.
The Work with M36 Machines display appears.
c. From the SSP console, stop all AS/400 Advanced 36 machines that have a
status of Started and return here.
For directions, see Chapter 16, “Stopping an AS/400 Advanced 36
Machine.”
d. From the OS/400 console, stop all AS/400 Advanced 36 machines that
have a status of Starting or Job Queue. To do so, use the End AS/400
Advanced 36 Machine (ENDM36) command. For information on using the
WRKM36 command to stop AS/400 Advanced 36 machines which could
not be stopped in the usual way, see “Ending an AS/400 Advanced 36
Machine” on page 30-7.
e. From the OS/400 console, press F3 (End) to end the WRKM36 command.
3. Unload all media in the devices before the system is powered down to ensure
the integrity of data on the media.

Using the POWER Menu to Stop the System

To power off the system immediately:
1. Follow the directions in “Preparing to Stop the System” on page 3-1.
2. Type
GO POWER
on any OS/400 command line.
3. Press Enter.
The Power On and Off Tasks (POWER) menu appears. From this menu you
can:
Display the schedule
Change the schedule
Power off the system immediately
Power off the system and then power on
Examples of using options 3 and 4 are included in this chapter.
4. To keep the power off until the next time the system is scheduled to power on:
a. In the option field, type
3
to select Power off the system immediately.
b. Press Enter.
The Confirm Power Off of System display appears as shown in Figure 3-1.
à@ ð
Confirm Power Off of System
System: SYSTEMð1
Next scheduled power on:
Date . . . . . . . . . . . : ð5/19/95
Time . . . . . . . . . . . : ð5:4ð:ðð
To confirm immediate power off, press F16.

To cancel, press F12.
Figure 3-1. Confirm Power Off of System Display for Immediate Power Down
c. Press F16.
When you press F16 (Confirm), an immediate power down occurs that
causes the subsystems to end all active jobs.
Note: Do not turn the modem on or off when the system is turned off and
is made ready for remote IPL. Otherwise, the system may start
unexpectedly, then turn itself off in a few minutes.
5. To power off the system and then restart the system immediately after it
powers off:
a. In the option field, type
4
to select Power off the system immediately and then power on.

b. Press Enter.
The Confirm Power Off of System display appears as shown in Figure 3-2.
à@ ð
Confirm Power Off of System
To confirm immediate power off and then immediate power on, press F16.
To cancel, press F12.
Figure 3-2. Confirm Power Off of System Display for Immediate Power On
c. Press F16.
When you press F16 (Confirm), the system stops running and then starts
again automatically.
Note: Do not turn the modem on or off when the system is turned off and
is made ready for remote IPL. Otherwise, the system may start
unexpectedly, then turn itself off in a few minutes.
Important Note
If you stop the system using the automatic power schedule or one of the
options on the Power On and Off Tasks (POWER) menu, the IPL date and time
system value (QIPLDATTIM) is checked and, if necessary, reset to the next
scheduled power-on time. This checking does not occur if you power off in
another way, so the system may not power on automatically. To force the
power schedule to update the QIPLDATTIM system value, enter the following
command on any command line and then press Enter.
CHGPWRSCDE DAY(\TODAY) PWRONTIME(\SAME) PWROFFTIME(\SAME)
Using the Power Down System Command to Stop the System

The Power Down System (PWRDWNSYS) command prepares the system for
ending and then starts the power-down sequence. All active subsystems are noti-
fied that the system is being powered down. No new jobs or routing steps can be
started by any subsystem. For example, jobs that are on a job queue as a result of
a Transfer Job (TFRJOB) command are not allowed to complete. During the sub-
sequent initial program load (IPL), they are removed from the job queue and their
job logs are produced.
Note: All media in the devices are unloaded before the system is powered down
to ensure the integrity of data on the media.
The Power Down System (PWRDWNSYS) command can be used on any OS/400
command line. To use the PWRDWNSYS command:
1. Follow the directions in “Preparing to Stop the System” on page 3-1.
2. On an OS/400 command line, type
PWRDWNSYS
3. Press F4.
The Power Down System (PWRDWNSYS) command prompt appears.
Chapter 3. Stopping the System Unit 3-3

4. Specify the options you want and then press Enter.

Note: Positioning the cursor on one of the input fields and pressing F4 dis-
plays the values that can be specified for that parameter. Pressing the
Help key or F1 provides additional information about that parameter.
Using the Power Pushbutton to Stop the System

If you cannot use option 3 (Power off the system immediately) or option 4 (Power
off the system immediately and then power on) on the Power On and Off Tasks
(POWER) menu or the PWRDWNSYS command to stop the system, you can turn
the power off using the Power pushbutton when the mode is set to Manual. Pow-
ering off this way causes the next IPL to be abnormal.
There are two ways to power off the system using the Power Pushbutton.
Normal sequence
Emergency sequence
Attention
Using the Power pushbutton to turn off the system may cause results that
cannot be predicted in your data files, and the next IPL will take longer to com-
plete.
Make sure that no media is left in the media devices and that the mode is set to
Manual.
Note: Do not turn the modem on or off when the system is turned off and is made
ready for remote IPL. Otherwise, the system may start unexpectedly, then
turn itself off in a few minutes.
Normal Sequence
1. Press the Power pushbutton. The Function/Data display blinks with O?. (the
international power off symbol).
Note: To cancel the power off operation, press any other pushbutton on the
control panel.
2. Press the Power pushbutton again. The Power On light blinks as the system is
being powered off. When power off is complete, the light goes off.
If the system does not turn the power off within 30 minutes or the System Attention
light does not come on, see the System Startup and Problem Handling book,
SC41-4206, for further directions.
Emergency Sequence
1. Set 08 (fast power off) in the Function/Data display.
2. Press the Enter Pushbutton.
A System Reference Code (SRC) of A1ðð 8ðð8 is shown in the Function/Data
display.
3. Press the Power Pushbutton. The Function/Data display blinks with O? (The
international power off symbol).
4. Press the Power Pushbutton again. The system will immediately power off.

OS/400 System Console
Chapter 4. The OS/400 System Console

The OS/400 system console is the workstation that allows you to control and
observe system operations. It is the workstation attached to the first input/output
processor capable of supporting workstations.
The system controls which display station is the OS/400 console. The system
moves the OS/400 console only if the display station at the first workstation I/O
processor, port 0, address 0 no longer works.
For more information in determining which workstation is the OS/400 console, see
the System Startup and Problem Handling book, SC41-4206.
Device Name of the System Console

To find out the device-name for the OS/400 console, type:
DSPSYSVAL QCONSOLE
QCONSOLE is the value that specifies the name of the display device that is the
console. You cannot change this system value.
How the System Console Display is Different from Other Displays

The console display is like any other display with the exception of system break
messages and commands. Unless the CHGMSGQ QSYSOPR *BREAK command
is issued, break messages are displayed only on the console. However, you can
view these system messages using the DSPMSG QSYSOPR command from an
OS/400 command line on any display station. For more information on messages,
see Chapter 5, “Handling OS/400 Messages.”
Most commands can be entered from any OS/400 display, the following commands
must be run from the OS/400 system console:
DST commands
ENDSBS command if the subsystem you are ending is the controlling sub-
system.

OS/400 System Console

Displaying Messages
Chapter 5. Handling OS/400 Messages

Note: The displays shown in this chapter are those you would see if you were
running at a basic assistance level. You would see different displays at
other assistance levels.
A message is any communication sent from one point to another point on the
AS/400 system. The communication may be between you and the system or
between you and another person using the system.
The system communicates with you by sending Informational and Inquiry mes-
sages.
Most Common Types of OS/400 Messages

Informational messages do not require a reply. These messages give you status
on what the system is doing, errors that you make, and responses that
you make to messages. Informational messages appear directly on the
workstation display in the message line. The message line is the
bottom line of the display.
Inquiry messages give you information about the system, but request a reply.
These messages are sent to either the system operator message queue
(QSYSOPR), a user message queue, or the workstation message
queue.
Displaying OS/400 Messages

A message sent to your message queue is not usually shown automatically. A
message interrupts you if:
Your message queue is set to interrupt you (break mode).
A message is sent with the Send Break Message (SNDBRKMSG) command.
If you are interrupted, the Display Messages display is shown automatically as in

Figure 5-1 on page 5-2.
Note: If you are interrupted, the Display Messages display is always shown. It
does not change based on the assistance level you are running with.

Displaying Messages
à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : SMITHS1 Program . . . . : \DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : ðð Delivery . . . : \NOTIFY
Type reply (if required), press Enter.

From . . . : QSYSOPR ð1/1ð/91 13:31:33
This system will go down in 1ð mins
Bottom
F3=Exit F11=Remove a message F12=Cancel
F13=Remove all F16=Remove all except unanswered F24=More keys
á ñ
Figure 5-1. Display Messages display
If your messages do not interrupt you whenever they are sent, you can see them
by:
Using the Display Messages (DSPMSG) command.
Using the Work with Messages (WRKMSG) command.
Selecting option 3 (Work with messages) on the Operational Assistant
(ASSIST) menu.
Figure 5-2 on page 5-3 shows the Work with Messages display.

Displaying Messages
à@ ð
Work with Messages
System: SYSTEMð1
Messages for: SMITH
Type options below, then press Enter.

4=Remove 5=Display details and reply
Opt Message
Messages needing a reply
_ Controller SYSTEMð1 contact not successful. Probable remote station
problem (C R)
Messages not needing a reply

_ System is scheduled to be powered off at 22:3ð:ð1 on ð5/17/92.
From . . : QPGMR ð5/17/92 22:15:ðð
_ System is scheduled to be powered off at 22:3ð:ð1 on ð5/16/92.
From . . : QPGMR ð5/16/92 22:15:ðð
_ System is scheduled to be powered off at 22:45:ð1 on ð5/15/92.
From . . : QPGMR ð5/15/92 22:3ð:ðð
From . . : QPGMR ð5/14/92 22:3ð:ðð
Bottom
F1=Help F3=Exit F5=Refresh F6=Display system operator messages
F16=Remove messages not needing a reply F17=Top F24=More keys
á ñ
Figure 5-2. Work with Messages display
Note: By displaying all of your message queues that are in break mode or notify
mode, you turn the message waiting light off.
To print the messages in a message queue if your assistance level is *BASIC, use
the Work with Messages (WRKMSG) command as follows:
WRKMSG MSGQ(msgqname) OUTPUT(\PRINT)
where msgqname is the name of the message queue that contains the messages you
want to print.
You can also print messages contained in a message file with the Display Message
Description (DSPMSGD) command and F4 (Prompt). Specify a range of message
identifiers and *PRINT for the Output (OUTPUT) parameter.
Finding Additional Information about Your Messages

To find out more information about messages on the Work with Messages display,
use option 5 (Display details and reply). When you use option 5 for a message
that does not need a reply, you receive the additional information about that
message. If the message requires a reply, you can type your reply in the field
provided at the bottom of the Additional Message Information display.
For example, Figure 5-3 on page 5-4 shows additional information about the first
inquiry message in Figure 5-2:
Chapter 5. Handling OS/400 Messages 5-3

Displaying Messages
à@ ð
Additional Message Information
Message ID . . . . . . : CPA57EF
Date sent . . . . . . : 11/18/91 Time sent . . . . . . : 15:43:ð2
Message . . . . : Controller SYSTEMð1 contact not successful. Probable remote

station problem. (C R)
Cause . . . . . : The system was trying to exchange identifiers with the

station when an error occurred. The probable causes are:
-- The controller description on the remote system is not varied on.
-- A configuration problem.
-- A remote hardware problem.
-- A local hardware problem or network problem if on an Ethernet network.
-- A timing or performance problem.
Recovery . . . : Do the following:
-- Contact the remote operator to verify the remote system is not
More...
Type reply below, then press Enter.
Reply . . . . _______________________________________________________
F1=Help F3=Exit F6=Print F9=Display message details F12=Cancel

F21=Select assistance level
á ñ
Figure 5-3. Additional Message Information Display – Basic Assistance Level
Press the Page Down key to see the rest of the information about the message.
When you have read the information, type a reply in the Reply field at the bottom of
the display and press Enter.
To see more details about the message, press F9 (Display message details).
Figure 5-4 shows the Display Message Details display.
à@ ð
Display Message Details
Message ID . . . . . . : CPA57EF Severity . . . . . . . : 99

Date sent . . . . . . : 11/18/91 Time sent . . . . . . : 15:43:ð2
Message type . . . . . : Inquiry
CCSID . . . . . . . . : 65535
From job . . . . . . . . . . . : QSYSARB

User . . . . . . . . . . . . : QSYS
Number . . . . . . . . . . . : ðð93ð2
From program . . . . . . . . . : QSWCDCR
To message queue . . . . . . . : QSYSOPR

Library . . . . . . . . . . : QSYS
Bottom
Press Enter to continue.
F1=Help F3=Exit F12=Cancel
á ñ
Figure 5-4. Display Message Details display

Displaying Messages
To print a single message, use F6 (Print) on the Additional Message Information

display. This prints all the information about the message shown on the display.
Identifying Messages from the System

On some message displays, the message is accompanied by a letter and number
code as shown in Figure 5-5.
CPF 0083
↑ ↑
.A/ .B/
Figure 5-5. Example of a Message ID
This is the message identifier (ID) that is used to distinguish a message from others
in the message file. The first three letters .A/ indicate the message category.
The following list shows some typical message categories:

CPA through CPZ Messages from the operating system
CBE through CBX COBOL messages
CSC COBOL language syntax checker messages
LBE through LSC COBOL messages
MCH Licensed Internal Code messages
QRG RPG language messages
RPG through RXT RPG language messages
SBX through SSC COBOL messages
SQL Structured Query Language (SQL) messages
The remaining four digits .B/ indicate the sequence number of the message. The
example message ID shown indicates this is a message from the operating system,
number 0083. A message ID is shown when you press the Help key for an error
message and additional message information is shown.
Message Severity Codes

Figure 5-6 shows the different severity codes of the messages and the types they
are associated with.
Figure 5-6 (Page 1 of 2). Message Severity Codes

Message Type Severity Code
Informational messages. For informational purposes only; no reply 00
is needed. The message can indicate that a function is in progress or
that a function has completed successfully.
Warning. A potential error condition exists. The program may have 10
taken a default, such as supplying missing data. The results of the
operation are assumed to be successful.

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

Message Type Severity Code
Error. An error has been found, but it is one for which automatic 20
recovery procedures probably were applied; processing has con-
tinued. A default may have been taken to replace the wrong data.
The results of the operation may not be correct. The function may
not have completed; for example, some items in a list ran correctly,
while other items did not.
Severe error. The error found is too severe for automatic recovery 30
procedures and no defaults are possible. If the error was in the
source data, the entire data record was skipped. If the error occurred
while a program was running, it leads to an abnormal end of program
(severity 40). The results of the operation are not correct.
Severe error: abnormal end of program or function. The opera- 40
tion has ended, possibly because the program was not able to handle
data that was not correct or because the user canceled it.
Abnormal end of job or program. The job was not started or failed 50
to start, a job-level function may not have been done as required, or
the job may have been canceled.
System status. Issued only to the system operator message queue. 60
It gives either the status of or a warning about a device, a subsystem,
or the system.
Device integrity. Issued only to the system operator message 70
queue, indicating that a device is not working correctly or is in some
way no longer operational.
System alert and user messages. A condition exists that, although 80
not severe enough to stop the system now, could become more
severe unless preventive measures are taken.
System integrity. Issued only to the system operator message 90
queue. Describes a condition where either a subsystem or system
cannot operate.
Action. Some manual action is required, such as entering a reply or 99
changing printer forms.

Displaying Messages
How to Handle Break Messages

The following is an example of the Display Messages display which appears when
a break message is sent.
à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : SMITHS1 Program . . . . : \DSPMSG
Severity . . . : ðð Delivery . . . : \NOTIFY

From . . . : QSYSOPR ð1/1ð/91 13:31:33
This system will go down in 1ð mins
Bottom
á ñ
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 and
press Enter. If you don’t want to reply to the break message, just press F12 to
cancel. 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 interruption
may be lost.
2. To display more information about a message, place the cursor under the
message and press Enter. The Additional Message Information display
appears.
Displaying OS/400 System Operator Messages

To display messages in the system operator message queue (QSYSOPR), do one
of the following:
Press F6 (Display system operator messages) on the Work with Messages
display.

Displaying Messages
Type DSPMSG QSYSOPR ASTLVL(*BASIC) on any command line and press

Enter.
Select option 1 (Display messages for system operator) on the Technical
Support Tasks (TECHHELP) menu.
Select option 3 (Work with system operator messages) on the Manage Your
System, Users, and Devices (MANAGESYS) menu.
Select option 6 (Display system operator messages) on the System Request
menu.
Figure 5-7 shows the Work with Messages display with system operator messages.
à@ ð
Work with Messages
System: SYSTEMð1
Messages for: System Operator

Opt Message
_ Device PRTð1 not available (C R)

_ 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 other
messages. See “Responding to OS/400 Messages” on page 5-9 for information on
how to reply or get additional information about these messages.
Your User Profile Message Queue

When signing on to the system, the message queue defined in your user profile is
put into the delivery mode specified in your user profile. For the system operator
(user profile QSYSOPR), this message queue is QSYSOPR, unless it has been
changed.
Whenever you transfer to an alternative job, your user profile message queue is set
to hold the messages. This allows your user profile message queue to move with
you 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 its
delivery mode set. At this time someone else can change the delivery mode of
your user profile message queue, so when you transfer back, your user profile

Displaying Messages
message queue will not be set back to the delivery mode it was set to when doing
the first transfer.
Responding to OS/400 Messages

The system sometimes sends you error messages that require you to choose a
response 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 system
operator message queue. However, under certain circumstances, they can also
appear on your own message queue.
You do not have to know or remember the meanings of the numbers or letters in
any response option code. The Additional Message Information display provides
information about these option codes. In addition, this display also provides a reply
line on which you can type your reply (if a reply is needed).
To get to the Additional Message Information display from the Work with Messages
display:
1. Position the cursor on the option line in front of the message you want to
respond 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.

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 Queues

A message queue is like a mail box for messages sent to a user. Each workstation
has a message queue with the same name as the device description name. Each
user has a message queue with the same name as the user profile name (or user
ID), and the system operator has a message queue named QSYSOPR. When a
user signs on the system for the first time, the system automatically creates a user
message queue. When a workstation is connected to the system for the first time,
the system automatically creates a workstation message queue. When the system
is configured for the first time, the system operator queue is created.
You can see the messages from your workstation and personal message queues
on 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 Details
display.

à@ ð
Display List Details
Message queue . . . . . : SMITHS1

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

Library . . . . . . . : 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 workstation
message queues:
Message Queue
This is the name of the message queue on which the messages are found.
Library
This is the library that contains the message queue.
Delivery
This is the method by which messages are delivered, whether they interrupt
you, sound an alarm, hold until answered, or automatically send a default reply.
Program
This is the name of the program called when a message arrives in a queue that
is set to interrupt and the severity of the message is equal to or greater than
the queue severity value.
Severity
Messages sent to the message queue with a severity level equal to or greater
than this severity level interrupt you or turn on the message waiting light
depending on how your message delivery is set.
Allow alerts
This value indicates whether messages sent to this message queue might also
generate an alert.
CCSID
This is the coded character set identifier associated with the message queue.
Description
This is the description of the message queue, usually the name and address of
the message queue owner.

Changing a Message Queue

You can change the way a message queue notifies you of messages, change the
message queue severity level, or the break-handling program. To change the infor-
mation shown on the Display List Details display:
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 Message
queue (MSGQ) parameter and the name of the library containing the message
queue 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 queue
is a workstation message queue, it is automatically changed to *NOTIFY by
the system at sign-on.
*BREAK: When you receive a message, your work is interrupted, and a
separate message display that contains the message is shown (unless you
have specified a program to handle the message).
*NOTIFY: When you receive a message, your work is not interrupted. You
are notified that a message has arrived by the workstation attention light
and an alarm (if your workstation has one) that sounds. You can use either
the Display Messages (DSPMSG) command or Work with Messages
(WRKMSG) command to see the message.
*HOLD: The message queue keeps or holds the messages until you
request them using the Display Messages (DSPMSG) or Work with Mes-
sages (WRKMSG) command. You are not notified when a new message
arrives.
*DFT: All messages are ignored, and any messages requiring a reply are
sent the default reply. For the system operator message queue
(QSYSOPR), the messages are kept in the queue and logged in the history
log, QHST; this is known as unattended operation. For any other user or
workstation 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 on
your Message Waiting light. For example, if you enter a message severity
code 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 message
with a severity code of 59 or greater sent to the same message queue causes
the Display Message display to be shown (unless you have specified a different
program to handle the message).
If you type a message severity code of 59, and the message queue is in notify
mode, the system notifies the user of any messages in the message queue that

have a severity code of 59 or greater. After you make this change, any
message with a severity code of 59 or greater sent to the same message
queue 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 for
more 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 queue
from being reset to the same status as new messages. Specify *YES to reset
messages you have displayed on the message queue to the same status as
new messages. Resetting old messages to new allows you to receive them
again.
10. For the Force to auxiliary storage (FORCE) parameter, specify one of the
following:
*SAME to use the value specified in the identified message queue.
*NO to specify that changes made to the message queue, including its
messages, are not immediately forced into auxiliary storage.
*YES to specify that all changes made to the message queue description
and to the messages in the queue are immediately forced into auxiliary
storage. If this field value is changed to *YES, the message queue is
forced into auxiliary storage each time it is changed. This is an important
recovery tool for message queues that provides communications between
programs, 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 generated
from 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 to
be determined from the message.
*JOB specifies that the CCSID of all messages on this message queue are
to be considered in the CCSID of the job.
Any valid job CCSID specifies that the CCSID of all messages on this
message queue are to be considered in this CCSID.
13. Press Enter to change the message queue.

Handling OS/400 Error Messages

You will receive a variety of system messages that indicate conditions ranging from
simple typing errors to problems with system devices or programs. The message
may be one of the following:
An error message on your current display.
A message regarding a system problem that is sent to the system operator
message queue and shown on a separate Work with Messages display.
A message regarding a system problem that is sent to the message queue
specified in a device description.
A message regarding a potential severe system condition that is sent to the
QSYSMSG message queue, the system operator message queue, and other
message queues specified by the users.
Handling Important System Messages in the QSYSMSG Message

Queue
The QSYSMSG message queue is an optional message queue that you create in
the QSYS library. The QSYSMSG message queue can be used to monitor specific
system 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 to
your system.
Creating the QSYSMSG Message Queue

To create the QSYSMSG message queue:
CRTMSGQ QSYS/QSYSMSG
TEXT ('optional MSGQ to receive specific system messages')
2. Press Enter.
Once the QSYSMSG message queue is created, certain specific system messages
are directed to it. For example, the following message would be sent to the
QSYSMSG message queue:
CPF0907 Serious storage condition may exist. Press HELP.
For a complete listing and description of these messages, see Chapter 8, “Working
With Messages” in the CL Programming book.
You can write a break-handling program that monitors messages sent to the
QSYSMSG 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.

Error Messages on Menus and Displays

If you request a task the system cannot run because of an error, an error message
appears at the bottom of the display. Depending on the workstation, the keyboard
may 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 message
queue, 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 Command

To run the Work with Problems (WRKPRB) command:
Intermediate Assistance Level
1. From the Display Messages display, move the cursor to the message that
has 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 with
problem) key. From the Work with Problem (WRKPRB) display, you can show the
details of the problem and work directly with the problem.
To run the Work with Problem (WRKPRB) command for critical messages, press
F15 (Work with critical problems) from the Additional Message Information display.
Problem analysis helps you resolve an error that you could not resolve from the
message or the Additional Message Information display. For more information
about handling problems, see Chapter 6 of the System Startup and Problem Han-
Understanding OS/400 Keyboard Error Messages

When you press the wrong keyboard keys by mistake, the computer simply stops
and tells you what is wrong. The computer has simply locked up the keyboard so
you cannot continue your task until you make the necessary correction.

Sending OS/400 Messages
If you make an error, you should get a flashing number in the lower left corner of
the display. In many cases, the number is ððð5. Some workstations show the
number briefly and then replace it with a statement. The statement is called an
error message.
To find out what the error message means, press the key marked Help. If your
keyboard does not have a Help key, press F1.
The number is replaced with text. For example, the text might read: Cursor in
protected area of display. The computer does not have a precise message for
every 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.

As the system operator, you can send Informational messages like System Being
Shut 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 Message

The 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 a
message 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's
message queue, to all currently active message queues or to the system history
log, QHST. The sender can also require a reply from the message receiver.
To send a message,
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 text
contains blanks or other special characters, the text must be enclosed in apos-
trophes.

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 the
message 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 of
each user profile with an interactive job currently running. *ALLACT
cannot be specified with inquiry messages.
5. Press Enter.
The message is sent.
Using the Send Break Message Command to Send a Message

The Send Break Message (SNDBRKMSG) command is used to send an immediate
message to one or more workstation message queues. This command temporarily
interrupts the tasks being done by those who receive the message.
To send a break message, do the following:

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 text
contains 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 as
follows:
To workstation message queue (TOMSGQ) Specifies the names of one or more
workstation message queues to which the break message is sent. Only
the 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 and
you 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 Personal
Computer message queues. *ALLWS cannot be specified for
an inquiry message.

message-queue-name Specify the name of the message queue to

which the break message is being sent. The possible library
values are:
*LIBL All libraries in the job's library list are searched
until the first match is found.
library-name Specifies the library where the message queue
is located.
Message type (MSGTYPE) Specifies the type of message that is sent in break
mode. 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 the
message is expected to reply to it. An inquiry message
cannot be sent to multiple queues with only one command.
Message queue to get reply (RPYMSGQ) Specifies, only if an inquiry message is
sent, the name of the message queue that the workstation user's reply
is sent to.
QSYSOPR Specifies the replies to the break message are sent to the
system operator's message queue, QSYSOPR.
message-queue-name Specifies the name of the message queue to
which a reply to the break message is sent. Only a user or
workstation message queue can be specified.
The possible library values are:
*LIBL All libraries in the job's library list are searched
until the first match is found.
library-name Specify the library where the message queue
is located.
Coded character set ID (CCSID) Specifies the coded character set identifier
(CCSID) that the specified message text is in. The text supplied in the
Message 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 job
running this command.
*HEX The message text is not converted. CCSID 65535 is used.
coded-character-set-identifier Specify a valid CCSID in which you
want your message text to be considered in. Valid values
range from 1 through 65535.

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

OS/400 CL commands are commands run from the OS/400 command line. These
commands allow you to give explicit instructions to the system without using
menus.
CL Commands — Overview
Except for special commands like GO, CL commands have a verb part and an
object part. The verb part is a three letter prefix. Some examples are as follows:
Figure 6-1. Verb Part of CL Command

Verb Abbreviated Command Example command
Prefix
Change CHG CHGPF
Create CRT CRTLIB
Display DSP DSPMSGQ
Start STR STRBGU
Work with WRK WRKJOBQE
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 are
working with. Some examples are as follows:
Figure 6-2. Object Part of CL Command

Object Abbreviated Command Example command
Suffix
Physical file PF CHGPF
Library LIB CRTLIB
Message Queue MSGQ DSPMSGQ
Business Graphics Utility BGU STRBGU
Job Queue Entry JOBQE WRKJOBQE
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 you

do not know which parameters can be specified for a specific command, type the
command 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 the
parameters, the center column is where you type the parameter values, and the
right 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 different
value, you can type that value over the default. If a value is required, the line is
highlighted and no default is filled in.

What are the Operational Assistant Displays?
If you do not know what a value means or what a parameter is, move your cursor
to the value or parameter and press F1. A new display overlays the existing one
with 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 the
required parameters. The defaults are known already to the system. You can also
type as many parameters on the command line as you remember and then prompt
using 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 the
cursor to a value or parameter and press F1.
Refer to CL Reference book, SC41-4722.
Using Operational Assistant Displays

The Operational Assistant* displays are a menu-driven interface that allow you to
do commonly performed system tasks quickly and easily. The Operational
Assistant displays:
Simplify everyday tasks such as controlling printer output, controlling jobs, and
handling messages
Allow you to set up a schedule for automatic power on and off, automatic
cleanup, and backup
Allow you to backup your system
Allow you to manage the devices attached to your system, users enrolled on
the system, signed-on users, and disk space storage
All of these tasks can be done by selecting options from the Operational Assistant
menu. 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.

Using Assistance Levels
Security Consideration
You must have at least a user class of system operator (*SYSOPR) to see all of
the 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 output

2. Work with jobs
3. Work with messages
4. Send messages
5. Change your password
1ð. Manage your system, users, and devices

11. 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 Profiles

You can choose the level of information you want when you interact with the
system. There are three levels of information called assistance levels:
1=Basic
Shows the displays that provide the most assistance. Basic assistance
level supports the more common operator tasks and user tasks, and
does not use computer terminology. Some less often used functions are
not shown.
2=Intermediate
Shows the displays that support all system tasks and uses computer ter-
minology. Complicated tasks can be done by using this level.
3=Advanced
Shows the displays that provide the same functions as the intermediate
assistance level. However, the displays contain as much information as
possible 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

Changing Assistance Level Displays

You can change from one assistance level to another on most Operational
Assistant displays. For example, to change assistance levels on the Work with
Messages (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) to
select the intermediate assistance level, or a 3 (Advanced) to select the
advanced assistance level (if available).
3. Press Enter.
4. The display you see on your system corresponds to the assistance level you
selected.
You can also change the assistance level by typing the command you want run
followed by astlvl(\xxxxx) where \xxxxx is \basic for basic assistance level,
\intermed for intermediate assistance level, and \advanced for advanced assistance
level. 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)

Work with Writers (WRKWTR)
Changing Assistance Levels Temporarily — Examples

Example 1
To change the assistance level for the Work with User Jobs (WRKUSRJOB)
command and reach the Work with Signed-On Users display:
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 and
then use the WRKUSRJOB command again, you return to the intermediate
assistance level.
Example 3
To see messages at the basic assistance level as shown in Figure 6-5 on

page 6-6:
1. Type
DSPMSG ASTLVL(\BASIC) MSGQ(QSYSOPR)
2. Press Enter.
OR
1. Type
DSPMSG MSGQ(QSYSOPR)
2. Press Enter.
4. Type
1
to select Basic.
5. Press Enter.

à@ ð
Work with Messages
System: SYSTEMð1
Messages in: QSYSOPR

Opt Message
_ 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)

_ 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 reply
F17=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 on

page 6-7:
1. Type
DSPMSG ASTLVL(\INTERMED) MSGQ(QSYSOPR)
2. Press Enter.
OR
1. Type
DSPMSG MSGQ(QSYSOPR)
2. Press Enter.
4. Type
2
to select Intermediate.
5. Press Enter.

à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : QSYSOPR Program . . . . : \DSPMSG
Severity . . . : 7ð Delivery . . . : \HOLD

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.
Controller KODO failed. Automatic recovery started.
Device KODOS4 no longer communicating.
Device KODOS3 no longer communicating.
Controller KODO contacted on line TRNLINE.
Bottom
á ñ
Figure 6-6. Display Messages Display—Intermediate Assistance Level
Changing Assistance Levels in Your User Profile

You 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 CL
command.
The Operational Assistant function keeps track of what assistance level you have
requested 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 assistance
level for some displays and the intermediate assistance level for other displays.
For each command, select the assistance level that you feel most comfortable
working 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 you
sign on again, your assistance level remains the same.

Using CL Commands with the Operational Assistant Displays

As you become an experienced AS/400 system user, you may prefer to do some
tasks 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 the
bottom of your display. You can type any control language (CL) command on this
command line.
Note: To control whether or not a user has use of a command line, type N (No) in
the Restrict command line use field on the Add User or Change User
display. You can add or change a user on the Work with User Enrollment
display. To find this display, type go setup and select option 10 (Work with
user enrollment) or use the command WRKUSRPRF *ALL
ASTLVL(*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 the
bottom of your display.
à@ ð
ASSIST AS/4ðð Operational Assistant (TM) Menu
System: SYSTEMð1

2. Work with jobs
4. Send messages

..............................................................................
: 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 on
the command line and press F4. A display is shown with all of the fields you need
to fill in for that command. Press the Help key or F1 while your cursor is on any
field to get an explanation of its function and a list of the possible values you can
type in the field.
If you do not know the name of the command you want, you can press F4 without
typing anything while your cursor is on the command line. The Major Command
Groups menu is shown where you can begin your search for the command you
want.

Doing Specific Tasks (GO)

To get to any menu on the AS/400 system quickly, type go plus the menu ID on
any command line, then press Enter. For example, if you want to run your daily
backup, you can get to the Run Backup menu by typing go runbckup on any
command line and press Enter. The menu ID is shown in the top left corner of the
display 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 Operations

The 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 display
having a command line. Just type GO plus a menu ID from the following list:
ASSIST The Operational Assistant (ASSIST) menu simplifies
some of the common user tasks, such as working with
printer output, jobs, messages, and changing your pass-
word.
In addition, users with proper authority can select options
to manage or customize the system, check the system
status, clean up objects, power the system on and off,
enroll users, change some system options, and collect
disk space information.
BACKUP The Backup Tasks (BACKUP) menu allows you to back
up (save) the system and initialize the tapes that are
used during backup.
CLEANUP The Cleanup (CLEANUP) menu allows you to start, end,
or change automatic cleanup. The cleanup function
deletes old job logs, history logs, messages, office cal-
endar items, and journal receivers that take up storage
space.
CMNCFG The Communications Configuration (CMNCFG) menu
can be used to configure communications to other
AS/400 systems, System/36s, or to remote work station
controllers and attached devices.

DEVICESTS The Device Status (DEVICESTS) menu allows you to

choose options for working with system devices, such as
display stations, printers, tape drives, and diskette
drives.
DISKETTE The Diskette (DISKETTE) menu allows you to work with
diskettes.
DISKTASKS The Disk Space Tasks (DISKTASKS) menu provides the
option for collecting disk space information to help show
how storage is being used on your system. After col-
lecting the information, you can specify what information
to include in a report and then print the report.
FILE The Files (FILE) menu allows you to work with files on
the system.
FOLDER The Folders (FOLDER) menu allows you to manage
folders. Folders can be used to store other folders and
documents.
INFO The Information Assistant* Options (INFO) menu allows
you to find out where to look for information about your
AS/400 system and how to comment on that information.
You can also use this menu to find out what is new in
this release of the AS/400 system and what new
enhancements and functions will be available in the next
release.
LIBRARY The Libraries (LIBRARY) menu allows you to work with
libraries.
MANAGESYS The Manage Your System, Users, and Devices
(MANAGESYS) menu allows you to display what activity
is going on in the system, run backup, and work with the
devices on the system.
POWER The Power On and Off Tasks (POWER) menu allows
you to display the power-on and off schedule. If you
have the correct authority, you can also change the
schedule or power off the system and then power it on
again.
PROBLEM The Problem Handling (PROBLEM) menu allows you to
work with problems, ask questions, and receive answers
using the question and answer database, display system
operator messages, display the history log, and start
system service tools (SST).
RESTORE The Restore (RESTORE) menu allows you to restore
saved information from tape, or save file (SAVF) on the
system.
RUNBCKUP On the Run a Backup (RUNBCKUP) menu you can
select a menu option to specify the type of backup you
want to run.

SETUP The Customize Your System, Users, and Devices

(SETUP) menu lets you customize automatic cleanup,
schedule when your system will power on and off, and
enroll users.
SETUPBCKUP The Set Up Backup (SETUPBCKUP) menu allows you to
change backup options, lists, and schedules.
STATUS The Status (STATUS) menu allows you to display the
status of jobs, devices, and system activities.
SYSTEM The General System Tasks (SYSTEM) menu allows you
to control system operations, devices, and all jobs on the
system.
TAPE The Tape (TAPE) menu allows you to use and control
tape 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 system
and is useful in attempting to resolve problems.
Figure 6-9 lists other commonly used AS/400 menu IDs.
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)
If you use the word GO followed by CMD and the verb part or object part of a CL
command, you go to a menu that lists all commands which contain that part. Verb
and object parts are explained in “CL Commands — Overview” on page 6-1.


Printing with OS/400
Chapter 7. Printing with OS/400

When you use OS/400, printing is handled differently than when you use SSP. You
do not need to know everything about printing. To work with your printer output
and printer output created by others, you need to know only the essentials.
Definitions
The key elements you need to know about are:
Spooled files
Printer writers
Output queues
Printers
Spooled Files
In OS/400, a spooled file is a file that holds output data that is waiting to print. It
is also 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)
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 the
operator. There is one spool file shared by everyone on the system. All printer
output goes to this spool file.
Printer Writers
In OS/400, the printer writer is a system program that writes spooled files to a
printer.
In SSP, the spool writer (printer writer) is the part of SSP that prints output saved in
spool file entries.
Output Queues
In 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 an

OS/400 output queue, see “Defining Whether SSP or OS/400 Controls SSP Printer
Output” on page 31-26.

Printing with OS/400
Printers
The operating systems can share the same printer. For directions on sharing
printers, 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 is
controlled by a subsystem named QSPL. If an SSP job tries to use a printer that
another SSP or OS/400 job is using, the job receives an error stating that the
printer is in use.
Additional reading: For detailed information about printing elements, printer

device support, printer spooling support, and Advanced Function Printing* (AFP*),
see the Printer Device Programming book, SC41-4713.

Finding OS/400 Printer Output
Getting to the Work with Printer Output Display Using Operational

Assistant
It is easy to check on a submitted print job when you use Operational Assistant.
To see your printer output:
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 with
Printer 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 Command

You could also reach the Work with Printer Output display, by using a CL
command.
WRKSPLF ASTLVL(\BASIC)
2. Press Enter.
Figure 7-1 on page 7-4 shows the Work with Printer Output display.
Chapter 7. Printing with OS/400 7-3

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 of
others if:
You have job control (*JOBCTL) authority and the output queue was created
with 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 for
everyone. 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 work
with in the User field.
Note: If you do not know the user ID, press F4. This shows the Select a User
display. This display allows you to select a user ID from a list of all
users 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 may
have a status of Not assigned to a printer. Printer output that is not
assigned to a printer appears last in the list on your display.

This display shows you information about your printer output. It shows the
Printer ID, the name of the output sent to that printer, and the status of the
output.
This display also allows you to release jobs, resume printing, hold jobs, delete
jobs, respond to messages about forms, and change the order in which jobs
print.
5. Press F11 (Dates/pages/forms) to see another view of this display that shows
when printer output was created, the number of pages, what forms types are
used, and how many copies print.
Understanding Printing Problems

Figure 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 respond
to the message.
Printer is not started. Use option 10 Start printing on the Work with Printer Output display.
Printer output is not assigned to a Use option 10 Start printing on the Work with Printer Output display.
printer.
Printer output has a forms type Stop the printer and start it for the desired forms type.
that has not been started for the
1. Press F22 on the Work with Printer Output display.
printer.
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 Use the Change Spooled File Attributes (CHGSPLFA) CL command to
*JOBEND in the Schedule field change the value in the Schedule field to *FILEEND.
and the job has not finished.
Printer output is held. Release the printer output using option 6 Release on the Work with Printer
Output display.
Nothing is printing on the system. Verify that the QSPL subsystem is started with the WRKSBS CL
command. If QSPL is not started, use the STRSBS CL command to start
it.
Check for messages sent to the QSYSOPR message queue in the QSPL
subsystem. Respond to the messages.
Printer status says Message See if the printer's message queue is too full to receive new messages. If
waiting or MSGW, but you cannot so, remove some messages from the message queue.
find the message.
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, see
the information on getting help with problems in Chapter 13 of the System Startup
and Problem Handling book, SC41-4206.

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

SSP OS/400
Printing Priorities Printing Priorities
5 3
4 4
3 5
2 6
1 7
0 7 and put in HELD status

Managing Printer Output
Managing Printed Output

To manage printer output, use the Work with Printer Output display.
Holding Printer Output

To 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 Output

To 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 Output

To 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 Printer
Output display.
Changing Printer Output

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

The Change Printer Output display appears. Figure 7-4 on page 7-8 shows
the 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-255
First page to print . . 1 Number
Last 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 printer
output is now \Status changed.
What to Do if the Printer Output Is Not Already Printing

If 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, type
the 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 display
to select a printer.
Change the Number of Copies to Print: To change the number of copies to

print, type the new number in the Number of copies field.
Specify the Page to Start On: To specify the page that this printer output should
begin 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 page
to print field. The First page to print and Last page to print fields can be used
together if part of your report was damaged by a paper jam or if you only want to
print part of a report.

Change the Form Type: To change the form type for a report, type the name of
the 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 on
ordinary paper.
Change when Printer Output Prints: To move printer output to the front of the
line for printing, type a Y in the Print this output next field.
Your user profile controls the highest priority you can use when changing printer
output. The printer output you select only prints next if your user profile has higher
priority than the printer output next in line.
Save Your Printer Output after It Prints: To save your printer output after it is
printed, type a Y in the Save printer output field. Normally, you would want printer
output deleted to avoid cluttering up your system. However, for output that prints
on special forms, you may want to save your printer output. If you discover an
alignment problem after the output has printed, you can reprint without having to
rerun the program.
If the printer output you want to change is currently printing, you can change only
the Number of copies and Save printer output fields. If you want to change the
other fields, hold the printer output, make your change, and then release the printer
output.
Assigning Printer Output to a Printer

To 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
1ð
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 all
the 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 the
printer.

Working with Printers

To work with printers, press F22 (Work with printers) on the Work with Printer
Output display or use the following command:
WRKWTR ASTLVL(\BASIC)
Figure 7-5 shows the Work with Printers display.
à@ ð
Work with Printers
User . . . . . : SMITH

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 Printer
To 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 the
type 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 to
start. This means the system has started finding the printer output assigned
to this printer.
6. Press F5.
The status usually changes to Message waiting which means there is a forms
alignment message waiting.
7. In the Opt field, type
7
to select Message
8. Press Enter.
After you respond to this message, printing begins.

You can also start a printer on the Work with Printer Output display by using option
10 (Start printing).
Stopping a Printer
To 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, or
press F12 (Cancel) to return to the Work with Printers display without stopping
the printer.
4. Press F5 to see which printers are stopped.
If you pressed Enter, the printer’s status is \Stopped.
Restarting a Printer
To 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 page
field.
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 you
respond to the message, printing starts on the page you requested.
You can also restart a printer on the Work with Printer Output display using option
11 (Restart printing).
Answering Printer Messages

To see a printer message and find out what action is needed, on the Work with
Printers 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 Output
display using option 7 (Messages).

For more information about responding to printer messages, see “Responding to

OS/400 Messages” on page 5-9.

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 or
CPA3395) 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 Printer

To 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 printer
field.
7. Press Enter.
Working with Spooled Files

The Work with Spooled Files (WRKSPLF) command lets you display or print all (or
a specified portion) of the spooled files that are currently on the system. This
command 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.

4. Press Enter.
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 Queues

The Work with Output Queue (WRKOUTQ) CL command shows you the overall
status 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 moving
output from one queue to another.
To use this command:

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

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 Commands

The following list shows the System/36 commands that are used for controlling
printers 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. There
is no AS/400 equivalent command.
BALPRINT You can balance printer output on AS/400 by using the
Start Printer Writer (STRPRTWTR) command to start
another printer writer to the same output queue.
CANCEL (C P) Option 4 (Delete) on either the Work with All Output
Queues display or the Work with Printer Output display.
Use the WRKOUTQ command or the WRKSPLF
command, respectively, to go to these displays.
You can also use the Clear Output Queue (CLROUTQ)
command to remove spooled files from a specified
output queue.
CHANGE (G) Option 2 (Change) on either the Work with All Output
HOLD (H P) Option 3 (Hold) on either the Work with All Output
RELEASE (L P) Option 6 (Release) on either the Work with All Output
RESTART (T P) The Restart printing field on the Change Spooled File
Attributes display lets you specify which page to restart
printing the spooled file. This display lets you change
many attributes of the spooled file, such as the number
of copies to print, the forms types, and print sequence.
Use the CHGSPLFA command to go to the Change
Spooled 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.

TEXTPRTQ Same as the Work with Documents to be Printed

(WRKDOCPRTQ) command.
For more information on working with printer output, refer to the System Operation
book, 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 find
your printer output.

OS/400 Subsystems
Chapter 8. Working with OS/400 Subsystems
Definitions
Just as the word master has more than one meaning, subsystem has more than
one meaning. Subsystem means something quite different to OS/400 than it does
to SSP.
OS/400 Subsystems
For 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 startup
program that is supplied by IBM. If you use the startup program and you use the
CHGSYSVAL 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 additional
subsystems 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 restricted
state to back it up.
All user jobs are run in a subsystem. A subsystem creates a suitable environment
for 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 subsystems
can be defined to manage those jobs. All interactive processing can occur in one
subsystem, all batch processing in another, system operator jobs in a third, and so
on.
This makes it easier to control the different jobs in the system because subsystems
can be started and ended individually.
SSP Subsystems
For SSP, a subsystem is the part of communications that handles the require-
ments of the remote system. It isolates most system-dependent considerations
from the application program.
The only SSP subsystems are:

SSP-ICF subsystems
APPC subsystems

OS/400 Subsystems
The SSP-ICF subsystem is required for running ICF sessions.
The APPC subsystem allows the System/36 to communicate with other systems
that have compatible support.
Working with a Subsystem

The Work with Subsystem (WRKSBS) command allows you to work with each
active subsystem in the system. Also, if you select one of the subsystems shown
on the display, you can see additional information on all the jobs that are active in
that subsystem.
To use the WRKSBS command:

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 display
appears. 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 Descriptions

The Work with Subsystem Description (WRKSBSD) command allows you to work
with a specific subsystem or all subsystems currently on the system.
To use the WRKSBSD command:

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.

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

OS/400 Subsystems

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 Security
The system administrator can use a combination of system values, user profile
parameters, and resource security to protect the information on your computer. For
example, a system value called the security level determines how much security is
enforced on your system.
The security level for your system is the same for all users on the system. When
the system is set up, your system Security Officer sets the security level as one of
the following:
10 This is the lowest level of security. When the system security is set at
level 10 and you sign on, the system checks for a user profile. If the
system does not find a user profile, it creates one.
20 At level 20, a user profile must already exist. The system verifies that
the 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 level
40 also apply to level 50. In addition, level 50 is designed to meet the
C2 security requirements defined by the United States Department of
Defense.
Changing the Security Level

The security level of the system is set in the QSECURITY system value. To
change 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 user
profile 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.

Changing Passwords
To 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

2. Work with jobs
4. Send messages

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.

à@ 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 New
password 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


Working with Batch Jobs
Chapter 10. Controlling OS/400 Jobs

The key element used by the AS/400 system to organize and manage work is the
job. A job usually includes all necessary programs, files, connections and
instructions to the Operating System/400 licensed program.
A job can be one very short and simple task such as printing a report. It can also
be 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.
SBMJOB Batch
Job
Writer Printer
Interactive
Job
Job Queue Subsystem Output Queue

Sign On
RSLP109-0
Figure 10-1. Overview of Job Processing
There are two basic types of jobs: batch jobs and interactive jobs. “Submitting
Batch Jobs” gives you information about how to display, end, hold, release and
schedule batch jobs as well as work with job queues. “Working with Signed-On
Users” 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 information
about 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 the
Work Management book, SC41-4306.
Submitting Batch Jobs

A batch job does not require constant interaction with the user. Once you have
submitted a batch job, you are free to do other work at your work station without
waiting for the job to run. Two examples of jobs that are commonly run in batch
are printing reports and doing month-end data summaries.

When you submit a batch job, it is placed on a job queue. Then, the subsystem to
which the job queue is assigned takes the jobs off the job queue in order and runs
them. 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 and
time.
Submitting a Batch Job to Run Immediately

To 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 the
command you want to run in a batch job.
If the job you want to submit is a program, type call and the name of the
program; for example, CALL PAYROLL. If the job you want to run is a
REXX procedure, use the Start REXX Procedure (STRREXPRC)
command.
If the job you want to run is a CL command, type the name of the
command. You can use prompting to assist you with the parameters for
the command. Type the name of the command and then press F4 while
your cursor is positioned in the Command to run field. If you want, you can
also 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 of
your display that tells you the qualified job name that the system has
assigned to your job and the name of the job queue to which it has been
submitted.
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 is
unique.
User ID The user profile under which the job is running, usually the profile of
the submitter.
Job name A short descriptive title of the job, such as PRTINV for “print
invoices.”
Scheduling a Batch Job to Run Later

To schedule a batch job using the Submit Job (SBMJOB) command, use the
Schedule date (SCDDATE) and Schedule time (SCDTIME) parameters.
Schedule date (SCDDATE) parameter: Specifies the day the job is released on
the job queue. The possible values are:
*CURRENT Today’s date
*MONTHSTR First day of the month

*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 value
QDATFMT)
Schedule time (SCDTIME) parameter: Specifies the time on the scheduled date
when the job will be marked released on the job queue. The actual time may vary
depending on the activity involved in releasing the job and the load on the system
when 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 current
time 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 it
is processed as a normal job on the job queue. If a scheduled job is held on the
job 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 the
subsystem.
Changing a Job Schedule to Run at a Different Date or Time

To change the date and time for a scheduled job or to change a non-scheduled job
to be scheduled, use the Schedule date (SCDDATE) and Schedule time
(SCDTIME) parameters on the Change Job (CHGJOB) command.
Scheduling a Job Using Job Schedule Entries

A job schedule entry contains the information needed to submit a batch job once
or 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 can
also change the information in the job schedule entries, or hold and release a job
schedule entry. Each entry has a unique job name and entry number.
This section contains an overview of the job scheduling function. See the Work
Management book, SC41-4306, for complete and detailed information about the job
scheduling 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

à@ ð
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 Submit
Opt 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 Entry

To schedule a job once, weekly, or monthly, use F6 (Add) on the Work with Job
Schedule 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 Entry

If 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 \yes
for the Save (SAVE) parameter on the Add Job Schedule Entry (ADDJOBSCDE)
command.
Removing a Job Schedule Entry

To 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 Job
Schedule Entry (RMVJOBSCDE) command. If a job from this entry has already
been 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.

Changing a Job Schedule Entry

To change a job schedule entry, use option 2 (Change) on the Work with Job
Schedule Entries display or use the Change Job Schedule Entry (CHGJOBSCDE)
command. This changes the entry in the job schedule but does not affect any jobs
already submitted for this entry.
Holding and Releasing a Job Schedule Entry

To hold a job schedule entry, use option 3 (Hold) on the Work with Job Schedule
Entries 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 Job
Schedule Entries display or use the Release Job Schedule Entry (RLSJOBSCDE)
command. If the time has not passed, the job is submitted as scheduled. If the
scheduled time has passed, a message is displayed indicating that jobs were
missed.
Scheduling a Batch Job to Start an AS/400 Advanced 36

Machine
Because 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 the
system, this type of function needs to be performed by OS/400. To schedule a
batch 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 on
starting an AS/400 Advanced 36 machine in other ways, see Chapter 15, “Starting
an AS/400 Advanced 36 Machine.”

You can hold, release, end, and check the status of batch jobs on the Work with
Jobs display. To find the Work with Jobs display:
go assist
2. Press Enter to display the Operational Assistant menu.
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:

WRKUSRJOB JOBTYPE(\BATCH) ASTLVL(\BASIC)
2. Press Enter.
Figure 10-3 on page 10-6 shows the Work with Jobs display.

à@ ð
Work with Jobs
System: SYSTEMð1
User . . . . . . SMITH_____ Name, \ALL, F4 for list

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)
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-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 until
the time they are scheduled to be submitted.
Displaying Batch Jobs of Other Users

You can select whose jobs to view on the Work with Jobs display.
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 whose
jobs 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 Jobs

To see all batch jobs, on the Work with Jobs display, type *all in the User field and
press Enter. You can enter a generic name, for example A\ shows you all of the
jobs for all users whose names start with an A. You can also press F14 to go to
the 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.

à@ ð
Work with Jobs
System: SYSTEMð1
User . . . . . . \ALL______ Name, \ALL, F4 for list

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 jobs
are grouped by status.
Performance Note
Whenever possible, select a user ID instead of typing *all in the User field of
the 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 Status

To find jobs based on status:
1. On the Work with Jobs display, press F14 (Select other jobs). Figure 10-5 on
page 10-8 shows the Select Other Jobs window.

à@ ð
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 your
display 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 have
the statuses you selected.
You can also see when jobs were started by pressing F11 (Display dates/times) on
the Work with Jobs display. To return to the status version of this display, press
F11 (Display statuses).
Holding a Batch Job

To 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 Printer
output, it has finished running. Any reports it has created are waiting to print or
are printing. If you do not want these reports to print, use option 8 (Work with
printer output) on the Work with Jobs display. On the Work with Job Printer Output
display, use option 3 (Hold).
Note: Printer output is not included unless you type a Y in the Printer output field
in the Select Other Jobs window.

Working with Job Queues
Releasing a Batch Job

To 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 Job

Attention: Use caution when ending a job. Ending a job may interrupt job or file
updates.
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 the
display if it has a status of Printer output. This status does not appear unless
Y 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 to
print. To cancel a report, use option 8 (Work with printer output). On the Work
with Job Printer Output display, select option 4 (Delete) for the printer output you
want to delete.

Before a batch job is run, it waits in line on the job queue of the subsystem that will
run 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 active
subsystem. 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 Queue
Figure 10-6. Overview of Job Queue Processing

Looking at Job Queues

If you submitted batch jobs, the Work with Jobs display gives you the status of
those 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 your
job. Or, as the system operator, you may want to monitor the activity on the job
queues. You can see this information on the Work with Job Queues display. To
find 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

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 job
queue).
The Work with Job Queues display appears again with the jobs included.
4. From either of these displays, press F11 (Display libraries/descriptions) to see
another version that shows descriptive information about the job queues.
Working with an Empty Job Queue and Displaying Job Priority: To view an
empty 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 submitted
to that job queue.

To find priorities of jobs on a job queue use option 5 (Work with). When you press
Enter, the Work with Job Queue display is shown for the queue you selected. The
Priority column contains the priority of each job in the job queue.
Holding a Job Queue

To 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 which
have 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 held
when you know that the job queue is empty and choose to hold it so you
can stop all future jobs from coming into the system.
Releasing a Job Queue

To 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 Queues

Jobs waiting on the job queue do not run if the job queue is not assigned to an
active 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 the
job queues that are ready to run jobs.
2. If you need additional information about which job queues are assigned to
which subsystems, use the Work with Job Queues (WRKJOBQ) command.
3. On the Work with All Job Queues display, look at the Subsystem column to
tell 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-17
for instructions on how to do this.
Start the subsystem to which the job queue is assigned using the STRSBS
command. 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 Problem
Handling book, SC41-4206 for information on how to display a sub-
system description.

Working with Signed-On Users
On the Display Subsystem Description display, select option 6 (Job

queue entries). The Display Job Queue Entries display is shown with
all of the job queues assigned to the subsystem.
Assign the job queue to a subsystem. If you have determined that none of the
subsystems have a job queue entry for this job queue, you can assign it to a
subsystem using the Add Job Queue Entry (ADDJOBQE) command.

When you are signed on the system, you type one request at a time (such as
selecting an option or typing a command). The system responds to each typed
request after Enter is pressed.
This session, sometimes called an interactive job, begins when you sign onto a
workstation and ends when you sign off. During the session, your interaction with
the system is similar to a conversation. The AS/400 system links together all of the
tasks you do from the time you sign on until you sign off. This makes it easier for
you to manage your work environment, find your output, and keep track of what
you have done.
Displaying Signed-On Users

To display all users signed on the system, select option 12 (Work with signed-on
users) on the Manage Your System, Users, and Devices (MANAGESYS) display
which can be reached using option 10 on the ASSIST menu.
You can also use the Work with User Jobs command as follows:
WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\INTERACT) ASTLVL(\BASIC)
2. Press Enter.
Creating a Customized Work with User Jobs Command

If you do not want to type the Work with User Jobs (WRKUSRJOB) command with
all the parameters to get to the Work with Signed-On Users display, you can create
your own copy of the Work with User Jobs (WRKUSRJOB) command in your
library, changing the defaults to show the Work with Signed-On Users display. To
do this:
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)


CHGCMDDFT
5. Press F4.
6. Type the following values for the parameters and press Enter:
Command (CMD) WRKSGNON (or the name of the new
command)
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

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
Bottom
F1=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 System

When you sign a user off the system, you interrupt the user's interactive job in the
middle 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 user
or 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 or
F12 (Cancel) to leave the users signed on to the system.

Displaying Job Information
The Work with Signed-On Users display is shown without the users you signed
off the system.
Finding Signed-On Users and Sorting the User List

To find a specific user signed on to the system, type the first few characters of the
user's name in the Find user field and press Enter. The list is positioned at the
first user matching the characters you typed.
The list is initially sorted by user name and shows the activities of each user. To
sort the list by user name or display station name, press F13 (Sort list). To select
other 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 field
on the Select Other Users and Display Stations window.
Finding Additional Information about Signed-On Users

There are two ways you can display additional information about the users currently
signed on to the system. For a single user listed on the Work with Signed-On
Users display, select option 5 (Display details). This shows the Display Details
display, which gives the user, display station description, and the current activity of
the user.
To get additional information for all users shown on the Work with Signed-On Users
display, press F11 (Display additional information). This displays a pop-up window
where you can select to see activities, workstation descriptions, or user descriptions
in 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 Users

From 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 each
user. To send a message to all signed-on users, press F10 (Send message to
all).
Type your message in the Message text field on the Send a Message display
and press F10 (Send).
Note: The Send a Message display is set up to interrupt the users signed on
the system. If you do not want to interrupt them, change the value in
the Interrupt user field to an N.
Displaying Detailed Job Information

The 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:

Displaying Job Information
1. Use the Work with User Jobs (WRKUSRJOB) command selecting all jobs (or
the 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 the
Work 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 the
Display Job (DSPJOB) command or the Work with Job menu. You can do the
same 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 Attributes

To 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 can
see 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 running
too long and might be in a loop.
Displaying Job Definition Attributes

To display the current job definition attributes, select option 2 (Display job definition
attributes) on the Work with Jobs display. This display provides information such
as 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 Attributes
display. See “Changing How a Job Is Run” on page 10-16 for information on how
to change a job.
Displaying Job Run Attributes

To 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 priority
is on this display.
Displaying the Call Stack

If an active job has stopped or seems to be in a loop, the call stack can help to
determine where the problem is. It shows what program line numbers the job is
currently trying to run. To display the call stack, select option 11 (Display call
stack, if active) on the Work with Job menu.
Displaying Open Files

You can see information about all of the files that the job is currently using by
selecting 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 F5
continually and look at the data in the Relative Record column to see if the job is
repeating the same relative record number.

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 can
check the I/O Count field for the input/output count in that file to find out how the
job is progressing.

Once you have used the options on the Work with Job menu to do research, you
might want to change some of the attributes of a job that is running or waiting to
run. 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) prompt
display. You can do any of the following by changing the value for the specified
parameter.
Changing a Job’s Priority on a Job Queue

Each job on a job queue has an assigned priority (position on the queue). To
change a job’s position on the queue, type a number (0 to 9) in the Job priority (on
JOBQ) 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 the
queue. Then the job begins running sooner than jobs with lower priority on that
queue.
The highest priority is 0. The lowest priority is 9. Jobs with a higher priority are
run before jobs with a lower priority. There may be a limit on how high you can set
the 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 is
reserved 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 to
run:

Priorities
0 1 2 3 4 9
To Processing
If a job that
has a priority
of 1 is added
to the queue, it
would go here.
RV2P721-4
Figure 10-9. Job Queue Priority
This change only affects the job once. If the same job is submitted to the job
queue again, it has its original priority. If you want to make a permanent change to
the job’s priority on the job queue, you need to change either the job description it
uses or the procedure that submits the job.
Moving a Job to a Different Job Queue

You may have more than one job queue on your AS/400 system. Sometimes
certain 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 system
is. Or, your system may have a job queue assigned to a subsystem that has less
system resources than the interactive subsystem.
If you have more than one job queue on your system, you can move a job from
one queue to another by typing the new job queue in the Job queue field. This
change only affects the job once. If the same job is submitted again in the same
way, it goes to the original job queue. If you want to make a permanent change to
the queue this job uses, you need to change either the job description it uses or the
procedure that submits the job.
Changing How an Active Job Is Run

To change how a job is run, change either the Run priority or Time slice fields on
the Change Job (CHGJOB) display. The control program decides which jobs to run
in 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 on
how long the processor works on one job before switching to another job.
Time slices are measured in milliseconds. The run priority determines which
job 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 might
send a new display to your display station. Then the system has to wait for
you to type another request and press Enter. This is known as a long
wait.

When one of the previous events occurs, the system has to decide which job to
run next.
It looks at a list of jobs that are ready to be run and chooses the highest priority
job.
You can see that both run priority and time slice can affect how a job is run. You
should use great care in changing either of these. If you give any job too high a
priority or too long a time slice, it can negatively affect everything else running on
the 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 you
want to make a permanent change to how the job runs, you need to change either
the characteristics of the class it uses or have it run using a different class. For
more information on class, see the Work Management book, SC41-4306.
Changing a Job’s Print Priority

Each printer output on an output queue has an assigned priority (position on the
queue that was obtained from the job’s print priority). To change this priority, type
a 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 output
closer to the top of the output queue. Then it begins printing sooner than printer
output with lower priority on that output queue. Output queue priorities work in the
same way as job queue priorities (see Figure 10-9 on page 10-17).
Changing print priority using the Change Job (CHGJOB) command only affects the
job once. If the same job runs again, it returns to the original output priority. If you
want to make a permanent change to the job’s output priority, you need to change
either the job description it uses or change the procedure for submitting the job.
Assigning a Job to a Different Output Queue

When a batch job that creates printed output is waiting to run, you can change the
output queue to which it is assigned by changing the Output queue field on the
Change Job (CHGJOB) display. Once the batch job starts to run, it begins creating
its spooled file in its assigned output queue. At that point, you would need to move
the spooled file to a different output queue.
For an interactive job, you may want to change the assigned output queue before
you 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 same
job runs again, it is assigned to the original output queue. If you want to make a
permanent change to a batch job’s output queue, you need to change either the job
description it uses or change the procedure for submitting the job. If you want to
make a permanent change to an interactive job’s output queue, you need to
change either the job description it uses, the user profile, or the work station device
description. For more information on the CHGJOB command, see the CL Refer-
ence book, SC41-4722.

Working with Job Logs

A 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 message
online 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 viewed
or printed. When an interactive job ends normally, the job log is usually not sent to
an output queue. When an interactive job ends abnormally, the job log output file
is sent to an output queue.
The job log is a useful tool in diagnosing problems with a job. However, when the
system creates and prints detailed job logs, it can slow the system down. It is a
good idea to balance how much information you need in your job logs against how
their creation affects system performance.
Displaying a Job Log

You 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 to
see.
2. On the Work with Job Spooled Files display, find the file called
QPJOBLOG.
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 Job
Log (DSPJOBLOG) command.
Printing a Job Log

When an interactive job is running, a job log is being created. If the interactive job
ends normally, for example, when you sign off without problems, this job log is not
sent to the output queue.
To print a log for your interactive job during sign-off:

signoff \list
2. Press Enter.
To print the job log for another job:


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 be
printed on the system, user is the name of the user of the job whose job log is
to be printed, and job-name is the name of the job whose job log is to be
printed.
2. Press Enter
Your job log output file is printed or placed in an output queue, depending on how
your system is set up.
Changing the Logging Level for a Job

To minimize the size of job logs on your system, use the log level to limit how
much 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 program
command fields.
4. Type in the changes and press Enter.
Note: If you change the logging level to 0, F9 (Retrieve) does not work for
command 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 description
under 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 Log

Filtering is the process of removing messages from the job log based on the
message logging level set for the job. Filtering occurs before each new request is
received by a request processing program. If you run a CL program interactively or
in batch and fill in the Message logging fields (on the Change Job command) as
shown:
Level 0
Severity 00
Text *NOLIST
filtering would be run only once after the program ends. Filtering does not occur
after every CL command is run within the program. After the program ends, all
messages are removed from the job log because the message level is 0. A job log
is not spooled if the job ended normally because *NOLIST is specified for the
message text level.
Note: When the job log is not spooled, system resource to remove messages
from the job log is wasted.

Sending Job Log Output Files to a Separate Output Queue

The Operational Assistant automatic cleanup function deletes old job logs by
assigning them to the QEZJOBLOG output queue in the QUSRSYS library. For
more information about automatic cleanup, see chapter 8 of the System Operation
book, SC41-4203.
All of the job logs are conveniently stored for you in one output queue. You can
view them when you need to. If you need a printed copy of a log, you can move it
to 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 file
to 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.


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

Communications
In operating the system, you sometimes have to change device status (making
devices 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 ready
to 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 a
user 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 a

local configuration, see the Local Device Configuration book, SC41-4121. For infor-
mation on how to do a remote configuration, see the Communications Configuration
book, SC41-3401.
Note: With the following tasks, make sure you are using the basic assistance level
of the Operational Assistant functions. Otherwise the displays you see will
not match the displays shown in this manual. For more information on
assistance levels, see “Using Assistance Levels and User Profiles” on
page 6-3.

To 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 status
tasks). To display the Work with Devices display where you can see different kinds
of 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 of
device (display, printer, tape, and diskette) whose status you want to see.
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 (Make
available) or 2 (Make unavailable) after selecting the corresponding option on the
Device Status Tasks menu. The status for all of the devices is shown in the Status
column.

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 (Display
system operator messages) on the Work with Messages display.
Before a printer can print, the printer’s power and ready lights must be on, and
the error light must be off. If the printer’s error light is on, you may need to
answer messages sent to the system operator. To do this, make the printer
available (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 you
reach the limit specified for the QAUTOVRT system value. To display the
QAUTOVRT system value, on an OS/400 command line, type
DSPSYSVAL QAUTOVRT and press Enter. To change the system value,
use the Work with System Value (WRKSYSVAL) command. You must
have *ALLOBJ authority to change this system value.
For information on activating communications lines and controllers, see “Activating

Communications Lines and Controllers” on page 11-4.
Renaming a Device
To 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 with
display 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 New
name field and press Enter. If necessary, the system tries to make the
selected device unavailable so it can be renamed, and then makes it available
again with the new name.
Considerations for Renaming Devices

If you rename a device, there are other places where you will need to change the
name.
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

Printing Local Device Addresses

Job descriptions that refer to this device by name
Display descriptions referring to this as an auxiliary printer
Tape device
Tape files
Diskette device
Diskette files
Displaying and Changing a Device Description

To see the text description (location and owner) of any device on the system, press
F11 (Display descriptions) on any of the device displays. The display remains the
same except the description is shown next to the device it describes. In addition to
the name of the person who operates the device, it is helpful to include the physical
location 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 the

Change Description display, type the new description over the current description in
the New description field and press Enter. The Work with Display Devices display
is shown with the new description in the Description column.

You can print a diagram that shows the device location, by port number and switch
setting, 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 the
display to make sure it is printing.
Chapter 11. Working with OS/400 Devices and Communications 11-3

Activating Communications Lines and Controllers

Figure 11-1 illustrates how communications lines and controllers are connected to
enable the devices to communicate with each other.
System 2
(or remote
System 1 controller)
Line
Description LIND LIND
Controller CTRL CTRL
Devices Devices
RV2P705-0
Figure 11-1. Relationship Between Controllers and Lines in Communications
To activate, change the text descriptions, or rename your communications lines and
controllers, 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 on
the 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 the
device 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 display
station, you would see the Work with Controller display because a local
display does not have a communications line.
à@ ð
Work with Controller and Line
System: SYSTEMð1
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 descriptions

F12=Cancel F17=Top F18=Bottom
á ñ
Figure 11-2. Work with Controller and Line Display

3. The Work with Controller and Line display shows the controller and line to
which 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 this
display, 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 the
Rename 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 the
new name.
Note: When you change the name of a line or controller, other objects on
the system need to be updated with the new name. If you change
the name of a line or controller, check to ensure that any control
language (CL) programs that refer to that line or controller are
updated 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 was
changed.
To change the text description of the line, controller, or device type, use
option 13 (Change description). On the Change Description display, type
the new description over the current description in the New description
field. For example, if a new remote display station were added, RMTDEV3,
you could change the description to include that display station.
Configuring Remote Communications

To configure remote communications, use option 20 (Communications configuration
tasks) on the Customize Your System, Users, and Devices (SETUP) menu or type
go 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.

Using a Switched Communications Line

You can establish a connection to a remote controller or another system by making
a telephone call to the remote location or by answering a telephone call from the
remote location. If you do not have an automatic dial modem, you must place the
call manually, using manual dial. If you do not have an automatic answer modem,
calls to you must be answered manually.
Using Manual Dial

Generally, a communications request is made to the system by an application
program. When the request is made, you manually connect the line by doing the
following:
1. A message is sent by the system to the system operator message queue. If
you are authorized as the system operator, a message light comes on at your
work station, and an alarm, if your work station has one, sounds to indicate that
a message has arrived.
2. Display the messages sent to the system operator:
a. On the Operational Assistant (ASSIST) menu, select option 3 (Work with
messages). The Work with Messages display is shown.
b. Press F6 (Display system operator messages). A message similar to the
following 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 example
message shown, the number is 123-4567 and the line is LINE02).
4. When the call is answered, type
5
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 do
this, see the appropriate modem instructions.
When you complete this manual dial sequence, another message is sent to the
system operator. Display the message using option 3 (Work with messages).
The system operator message queue is shown with a message indicating
whether the controller was contacted successfully or not. Sometimes the
remote 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 should
monitor the messages at a work station near the phone or modem.

Using Manual Answer

Connect the line by doing the following:
1. When the telephone connected to the data line rings, answer it, and make sure
the person calling is authorized, if possible. If it is a modem from another
system 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 Line
field.
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 message
queue. 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
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 or
modem in data mode.
For information about how to do this, see the appropriate modem
instructions.
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 to
the 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 that
the controller was contacted successfully.
Using Manual Answer for Countries Other Than the United States
For 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.

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 press
Enter. 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
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 communications
equipment, press the answer button within 60 seconds.
When you complete the manual answer sequence, another message is sent to
the system operator. Display the message using the Work with Messages
display. 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 are
trying to make a dial connection. Press F5 to see what is currently hap-
pening on the line and controller.

Saving and Restoring OS/400
Chapter 12. Saving and Restoring OS/400 and OS/400

Objects
This chapter contains an overview of how to save and restore OS/400 objects and
the OS/400 operating system.
You can save or restore an entire system or individual objects in the system. Use
the save and restore commands and functions to ensure that, following any type of
failure, information exists that allows you to recover your system or to re-create any
objects on your system that were damaged. The media that are used for saving or
restoring objects and information include tape, diskette, and optical storage.
You can use the save and restore functions by using specific commands or by
using 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 press
Enter.
Saving the Entire System

You should develop a disaster recovery plan:
To ensure that you can respond to a disaster or other emergency that might
affect your system
To minimize the effect on your business operations
Part of the disaster recovery plan should be saving your entire system. The entire
system 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 Machine
Information.”
To save the entire system:

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 the
System Startup and Problem Handling book, SC41-4206 or Chapter 7 of the
Operating 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 Save
menu. 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 and
restore objects and information and how to plan more advanced strategies for
backup and recovery.
Restoring the Entire System

To recover after a complete system loss, see “Recovering from a complete Loss” in
Chapter 9 in the Backup and Recovery – Basic book, SC41-4304.
To recover after a disk failure, see “Choosing the Recovery for a disk failure” in
Chapter 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/400
Advanced 36 machine data, restore that data.
If you did individual saves of your AS/400 Advanced 36 machine, restore the
AS/400 Advanced 36 machine. For directions, see Chapter 25, “Saving and
Restoring the AS/400 Advanced 36 Machine Information.”
Saving the OS/400 Operating System

The 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/400
system.
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” on
page 25-1.
Libraries other than QSYS
For directions on saving the entire system including the AS/400 Advanced 36
machine, see “Saving the Entire System” on page 12-1.

Restoring the OS/400 Operating System

Restoring the OS/400 operating system from SAVSYS media is made up of two
tasks:
Restoring the Licensed Internal Code
For directions, see “Recovering Licensed Internal Code” in the Backup and
Recovery – Basic book, SC41-4304.
Restoring the operating system
For directions, see “Restoring the Operating System” in the Backup and
For directions on restoring other libraries from SAVSYS media, the directions are
also included in the Backup and Recovery – Basic book, SC41-4304.
For directions on how to restore an AS/400 Advanced 36 machine that was saved
individually, see Chapter 25, “Saving and Restoring the AS/400 Advanced 36
Machine Information.”
Saving AS/400 Storage

The Save Storage (SAVSTG) CL command causes the Licensed Internal Code and
the contents of the auxiliary storage to be saved to tape. When you run the
SAVSTG command, the save function causes an IPL of the system. This function
is intended for disaster recovery backup. Individual libraries or objects cannot be
restored from a save storage tape. For more information on the SAVSTG
command, see the CL Reference book, SC41-4722.
Restoring AS/400 Storage

To 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 SAVSTG
command was used.
The restore storage process is started by using an option on the Dedicated Service
Tools (DST) menu. The restore storage operation can only be started when the
operating system is not active (before an IPL of the operating system). This func-
tion is intended for disaster recovery backup. The procedure does not restore
single objects or libraries.
Saving Individual OS/400 Objects

This section contains an overview of the CL commands that can be used to save
OS/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
Saving Objects in Directories

The Save (SAV) command saves a copy of one or more objects that can be used
in the integrated file system. For more information about the integrated file system,
see the Integrated File System Introduction book, SC41-4711.
Saving Calendar
The Save Calendar (SAVCAL) CL command saves of calendars and calendar
items.
Saving Configuration Objects

The Save Configuration (SAVCFG) command saves all configuration and system
resource management (SRM) objects without requiring a system in a restricted
state.
Saving Changed Objects

The Save Changed Objects (SAVCHGOBJ) command saves a copy of each
changed object (since a specified date and time). The SAVCHGOBJ command is
the same as the SAVOBJ command except that the SAVCHGOBJ command saves
only changed objects and members.
Saving Documents, Folders, and Mail

The 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. Mail
can 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 folders
created since the last complete save operation, and all mail.
Saving Libraries
The Save Library (SAVLIB) command allows you to save a copy of one or more
libraries.
An AS/400 Advanced 36 machine is stored as an object in a library. By saving that

library, you can save the entire AS/400 Advanced 36 machine. A library containing
an 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 the
library in which the AS/400 Advanced 36 machine is contained.
The SAVLIB command saves the entire library, including the library description, the
object descriptions, and the contents of the objects in the library. You can save 1 to

300 libraries using the SAVLIB command. If you specify multiple libraries, you
overlap processing, which can improve performance. All libraries, including all user
libraries, can be saved to diskette or tape using the SAVLIB command. User
libraries are defined as libraries that you create or IBM-supplied libraries that are
intended to contain user data.
The SAVLIB LIB(*NONSYS) command saves all user-created libraries, the QGPL
library, 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 which
libraries are IBM libraries and which libraries are user libraries, see the Backup and
Note: When you save this way, you cannot restore individual System/36 files or
programs. You must restore the entire library. You should continue to use
the directions in Chapter 25, “Saving and Restoring the AS/400 Advanced
36 Machine Information” to save specific files and program libraries.
Saving Licensed Programs

The Save Licensed Programs (SAVLICPGM) CL command saves a copy of the
objects that make up a licensed program.
Saving Specific Objects

The Save Object (SAVOBJ) CL command saves a copy of a single object or a
group of objects located in the same library.
Saving Security Data

The Save Security Data (SAVSECDTA) command saves all security information
without requiring a system in a restricted state.
Restoring Individual OS/400 Objects

This section contains an overview of the CL commands that can be used to restore
OS/400 objects. For more information about these CL commands, see the CL Ref-
erence book, SC41-4722.
Restoring Objects in Directories

The Restore (RST) command restores a copy of one or more objects that can be
used in the integrated file system. For more information about integrated file
system, see the Integrated File System Introduction book, SC41-4711.
Restoring Calendar
The Restore Calendar (RSTCAL) CL command allows you to restore calendars and
calendar items.
Restoring Configuration Data

The Restore Configuration (RSTCFG) command restores a device configuration
object to the system. The command restores any device configuration object that
was saved to tape by the Save System (SAVSYS) command or the Save Config-
uration (SAVCFG) command.
Restoring Changed Objects

The Restore Changed Objects (RSTCHGOBJ) CL command restores each
changed object (since a specified date and time). The RSTCHGOBJ command is
the same as the RSTOBJ command except that the RSTCHGOBJ command only
restores changed objects and members.
Restoring Documents, Folders, and Mail

The 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 the
folders (if any) from which they were saved.
Restoring Libraries
The Restore Library (RSTLIB) command restores a single saved library or a group
of libraries. The RSTLIB command restores the entire library, including the library
description, object descriptions, and the contents of the other objects. Any library
that was saved by the Save Library (SAVLIB) command can be restored by the
RSTLIB command.
The AS/400 Advanced 36 machine is stored as a library. If you have used the
SAVLIB command to save the library in which the AS/400 Advanced 36 machine is
stored, you can use the RSTLIB command to restore the entire AS/400 Advanced
36 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 which
libraries are IBM libraries and which libraries are user libraries.
The RSTLIB SAVLIB(*NONSYS) command restores to the system all libraries

saved by SAVLIB LIB(*NONSYS) command.
Restoring Licensed Programs

The Restore Licensed Program (RSTLICPGM) CL command restores a copy of the
objects that make up a licensed program.

Restoring Specific Objects

The Restore Object (RSTOBJ) command restores objects to a library. Objects can
only 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 same
library with the same name and object type.
Restoring User Profiles

The Restore User Profile (RSTUSRPRF) command restores the basic parts of a
user profile or a set of user profiles. The command restores any user profiles that
were saved by the Save System (SAVSYS) command or the Save Security Data
(SAVSECDTA) command.
Restoring Object Authority

The Restore Authority (RSTAUT) command restores object authorities. When you
restore objects and user profiles, you do not simultaneously restore the authority to
those objects. Authority is only restored by using the RSTAUT command.

Working with LIC and OS/400 PTFs
Chapter 13. Working with Licensed Internal Code and OS/400

Program Temporary Fixes
IBM periodically creates program temporary fixes (PTFs) to correct problems or
potential problems found within a particular IBM licensed program. PTFs may fix
problems 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 program

may 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 to

IBM AS/400 system service and delivery.
AS/400 Program Maintenance Strategy

The 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 the
start of the current release.
Cumulative PTF packages contain PTFs which have been ordered a specific
number of times. If a PTF provides a change for a limited set of users or requires
special handling, it may not be included in the package. Cumulative PTF package
application 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 are
always sent by mail on a CD-ROM or tape.
Cumulative PTF packages should be installed every three to four months if there is
no change to the equipment or programs on your system. Between releases of
cumulative PTF packages, IBM service support provides PTFs that may be impor-
tant to your system. You should periodically order preventive service planning
information and review the PTFs listed. If any of these PTFs are needed for your
system, you should order and install them.
Corrective Service
Corrective service corrects problems reported to IBM service support. If you have
a problem with an IBM licensed program, you can describe the problem using the
Analyze 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-

Ordering PTFs and PTF Information
Ordering LIC and OS/400 PTFs and PTF Information

For information on the following topics, see Chapter 5 of the System Startup and
Problem Handling book, SC41-4206.
Ordering PTFs and PTF Information
Installing PTFs
System Storage Areas A and B
Advanced PTF Topics

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/400
job to the specified AS/400 Advanced 36 machine. The display device that is
transferred 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. The
display 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/400
Advanced 36 machine where you can sign on as if your display station were
attached locally. The display device where STRPASTHR is run is the display
that 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 36

machine allows up to eight characters for the user ID. For this reason, when you
choose to automatically sign on to the AS/400 Advanced 36 machine, the first eight
characters of the OS/400 user ID are used. If two user IDs start with the same
eight characters, this could be a security problem. For example, the following user
IDs would all be shortened to MICHAELS:
MICHAELS
MICHAELSON
MICHAELSEN
MICHAELSRM
Restrictions on Transfers using the TFRM36 and STRM36PRC

Commands
The following restrictions apply when using the TFRM36 or the STRM36PRC CL
command to transfer to an AS/400 Advanced 36 machine:
The AS/400 Advanced 36 machine specified on the M36 parameter must be
STARTING or STARTED. If the STATUS of the machine is STARTED, the

Transferring to M36
transfer request proceeds immediately. If the machine STATUS changes to

STARTED before two minutes are up, the transfer proceeds. After two
minutes, if the machine STATUS is still STARTING, the transfer request ends
with an error. The STATUS of the AS/400 Advanced 36 machine can be found
by 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 Advanced
36 machine being transferred to must have AUTOSIGNON(*ENABLE) specified
or a message is issued. For TFRM36, the transfer continues and
AUTOSIGNON(*NO) is used.
When you set up your AS/400 Advanced 36 machine, you need to decide
whether to allow automatic sign-on or not. If you allow automatic signon, an
SSP signon display is not seen because the user ID is already signed on to
OS/400.
A user ID that is greater than eight characters is truncated to an eight-character
user ID when they transfer to an AS/400 Advanced 36 machine.
The STRM36PRC command cannot be sent to an AS/400 Advanced 36
machine display station that is configured as an AS/400 Advanced 36 machine
data display station. It must be sent to an AS/400 Advanced 36 machine
display 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 is
configured as a command display station. These parameters are not allowed
when you sign on to an AS/400 Advanced 36 machine data display station.
Problems can occur if the TFRM36 or STRM36PRC CL commands are used
while you are reloading SSP. The TFRM36 or STRM36PRC commands can be
discarded and there may be no record that the commands did not complete
successfully.
| 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.
| 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

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

The Transfer to AS/400 Advanced 36 Machine (TFRM36) command transfers
control of a display device from an OS/400 job to the specified AS/400 Advanced
36 machine. The display device that is transferred is the one on which the
command is run. Control returns to OS/400 when you sign off the SSP operating
system.
There are certain restrictions you should be aware of when using the TFRM36. For
information on the restrictions, see “Restrictions on Transfers using the TFRM36
and STRM36PRC Commands” on page 14-1. For more information on the
TFRM36 command, see the CL Reference book, SC41-4722.
Transferring to an AS/400 Advanced 36 Machine

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

Transferring to M36
Using the TFRM36 Command — Examples

Example 1
TFRM36 M36(MYM36)
This command transfers the display station, on which the command is run, to an
AS/400 Advanced 36 machine named MYM36. It is located through the library list of
the OS/400 job. If the machine allows automatic sign on, the user of the display
device is automatically signed on to the AS/400 Advanced 36 machine using the
default 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, and
address of the display station in the AS/400 Advanced 36 machine configuration is
used to determine the SSP logical display station. For example, if your display
station 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 address
4 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 display
stations that are defined in the SSP master configuration record that are not in the
AS/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/400

Advanced 36 machine named MYM36, located in the current library of the OS/400
job. 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 for
use by this display device. If it is not available, an error message is returned and
the transfer request is refused.
If the user can be automatically signed on to workstation W7, the library INVAPPL will
be 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 on
the user's display device. The user is not given an ideographic session. If the
requested library, procedure, or menu for the TFRM36 command cannot be found,
the System/36 signon display is shown and a message which identifies the error
also appears on the signon display. The user has the option of correcting the error
and signing on or pressing Cmd7 to return to OS/400.
Example 3
TFRM36 M36(JOG/ADV36) AUTOSIGNON(\NO)

Transferring to M36
This command transfers the display device, on which it is run, to an AS/400

Advanced 36 machine named ADV36, located in a library named JOG. The SSP
workstation identifier that is assigned to the display device, is based on whether the
display device is currently configured in the AS/400 Advanced 36 machine. The
user 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.
| 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

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.

STRM36PRC Command
The Start AS/400 Advanced 36 Procedure (STRM36PRC) CL command transfers
control from an OS/400 job to the specified AS/400 Advanced 36 machine and runs
the specified SSP procedure. Control returns to OS/400 when the SSP procedure
ends.
There are certain restrictions you should be aware of when using the STRM36PRC
command. For information on the restrictions, see “Restrictions on Transfers using
the 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 Command

1. On an OS/400 command line or in a CL source program, type
STRM36PRC
2. Press F4.
4. Press Enter.

Transferring to M36
Running an SSP Procedure from OS/400 — Examples

Example 1
The following example runs an SSP procedure named CATALOG on an AS/400

Advanced 36 machine named PARENTIS.
STRM36PRC M36(PARENTIS) PRC(CATALOG)
The AS/400 Advanced 36 machine first checks for the procedure in the default
session library identified in the user's SSP user profile. If the AS/400 Advanced 36
machine does not find the procedure in the default session library, SSP automat-
ically searches the AS/400 Advanced 36 machine system library (#LIBRARY). No
parameters 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 Advanced

36 machine named CLASSOF96, located in a library named JML. First, the AS/400
Advanced 36 machine checks for the procedure in a library named STUDENTS
because this was specified as the current library for the procedure. If the AS/400
Advanced 36 machine does not find the procedure in the specified library, SSP
automatically searches the AS/400 Advanced 36 machine system library
(#LIBRARY). If the PRC or CURLIB values are not found, an error message is
returned 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, type
the command on an OS/400 command line and press F1.
Transferring to an AS/400 Advanced 36 Machine using STRPASTHR

The Start Pass-Through (STRPASTHR) command allows you to pass through to an
AS/400 Advanced 36 machine where you can sign on as if you were attached
locally. 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 STRPASTHR
command:
The AS/400 Advanced 36 machine you are passing through to must be
STARTED. If the STATUS of the machine is STARTED, the transfer request
proceeds immediately. If the machine STATUS is something other than
STARTED, the transfer fails.
The STATUS of the AS/400 Advanced 36 machine can be found by using the
Work with AS/400 Advanced 36 Machine (WRKM36) CL command. For more
information on the WRKM36 CL command, see the CL Reference book,
SC41-4722.

Transferring to M36
ILAN communications must be set up. For directions on setting up ILAN, see
Chapter 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:

STRPASTHR
2. Press F4.
4. Press Enter.

STRPASTHR Command — Examples
Example 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 a

location 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 the
display device on which the STRPASTHR command was typed.
Example 2 — Pass Through and Automatically Sign on to an AS/400 Advanced 36

Machine
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 a

location of IBMM36ð1. A user ID of USER1 and password of X1T4 are passed to the
AS/400 Advanced 36 machine. The defaults for the other parameters are used. If
USER1 is authorized to the AS/400 Advanced 36 machine and has enabled the
AS/400 Advanced 36 machine for automatic sign on, an SSP command display
appears 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.

Chapter 15. Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . 15-1
Starting the AS/400 Advanced 36 Machine from the OS/400 Command line 15-1
Requirements for Using the Start AS/400 Advanced 36 Machine Command 15-1
Using the IPL Type (IPLTYPE) Parameter . . . . . . . . . . . . . . . . . . . 15-2
Using the User Profile (USRPRF) Parameter . . . . . . . . . . . . . . . . . 15-2
Using the Apply AS/400 Advanced 36 Machine Configuration
(APYM36CFG) Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Starting an AS/400 Advanced 36 Machine — Examples . . . . . . . . . . . 15-4
Starting the AS/400 Advanced 36 Machine Automatically . . . . . . . . . . . 15-5
How To Change a Configuration for an AS/400 Advanced 36 Machine That
Starts Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Creating a Customized IPL Start-Up Program . . . . . . . . . . . . . . . . . 15-5
Sample QSYS/QSTRUP Start-up Program . . . . . . . . . . . . . . . . . . 15-7
Chapter 16. Stopping an AS/400 Advanced 36 Machine . . . . . . . . . . 16-1

Putting the AS/400 Advanced 36 Machine In a Dedicated State . . . . . . . . 16-1
Stopping an AS/400 Advanced 36 Machine from the SSP System Console . 16-2
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Chapter 17. Operating the SSP Console and SSP Subconsoles . . . . . 17-1
The SSP Console: A Way of Controlling the AS/400 Advanced 36 Machine 17-1
The SSP Subconsole: A Way of Controlling SSP Printers . . . . . . . . . . . 17-1
Transferring the SSP Console Function to an Alternative SSP Console . . . 17-2
Transferring the SSP Console Function During an Attended IPL . . . . . . 17-2
Transferring the SSP Console Function When the SSP Console Is in
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Transferring the SSP Console Function to an Alternative SSP Console
When the Console Is in Operation . . . . . . . . . . . . . . . . . . . . . . 17-3
Making an Alternative SSP Console the SSP Console . . . . . . . . . . . . 17-3
Transferring the SSP Console Function When the SSP Console Is Not in
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Using the SSP Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Requesting a Help Menu from the SSP Console Display . . . . . . . . . . 17-5
Using the Subconsole Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Requesting a Help Menu from the Subconsole Display . . . . . . . . . . . 17-6
Chapter 18. Handling SSP Messages . . . . . . . . . . . . . . . . . . . . . 18-1

How You Know That You Have an SSP Message . . . . . . . . . . . . . . . . 18-1
Types of SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Messages That Instruct You to Perform an Action . . . . . . . . . . . . . . 18-2
Messages That Require a Response . . . . . . . . . . . . . . . . . . . . . . 18-2
Additional Information for a Message . . . . . . . . . . . . . . . . . . . . . . 18-5
Informational Messages at the SSP Console . . . . . . . . . . . . . . . . . 18-5
Specifying That Informational Messages Are Not to Be Displayed at the
SSP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Displaying SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-6
Replying to SSP Messages at the SSP Console or Subconsole . . . . . . . . 18-7
Replying to Messages - Example . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Sending SSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9

Using the MSG Control Command to Send an SSP Message . . . . . . . 18-9
Using the MSG OCL Statement to Send an SSP Message . . . . . . . . 18-10
Using the OFCMSG Procedure to Send a Message . . . . . . . . . . . . 18-10
SSP Keyboard Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Error Reset Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Displaying Keyboard Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Chapter 19. Using SSP Commands and Procedures to Do Tasks . . . . 19-1

Using Help for Commands and Procedures . . . . . . . . . . . . . . . . . . . 19-1
When You Know the Name of a Command or a Procedure . . . . . . . . . 19-1
When You Do Not Know the Name of a Command or a Procedure . . . . 19-4
Chapter 20. Printing with SSP . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Spooled Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Printer Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Finding SSP Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Using SSP Help Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Using the Work with Spool File (WRKSPL) Command . . . . . . . . . . . . 20-2
Managing Printer Output — Command Summary . . . . . . . . . . . . . . . . 20-3
Managing Printer Output — Complete Details . . . . . . . . . . . . . . . . . . 20-3
Changing Printer Output with a Control Command . . . . . . . . . . . . . . 20-4
Changing Printer Output with an Option from a Menu . . . . . . . . . . . . 20-4
Changing Printer Output with an Option from a Display . . . . . . . . . . . 20-4
Holding Printer Output Using a Control Command . . . . . . . . . . . . . . 20-4
Holding Printer Output Using an Option from a Menu . . . . . . . . . . . . 20-4
Holding Printer Output Using an Option from a Display . . . . . . . . . . . 20-4
Releasing Printer Output Using a Control Command . . . . . . . . . . . . . 20-4
Releasing Printer Output Using an Option from a Menu . . . . . . . . . . . 20-5
Releasing Printer Output Using an Option from a Display . . . . . . . . . . 20-5
Deleting Printer Output Using a Control Command . . . . . . . . . . . . . . 20-5
Deleting Printer Output Using an Option from a Menu . . . . . . . . . . . . 20-5
Deleting Printer Output Using an Option from a Display . . . . . . . . . . . 20-5
Copying 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-6
Working with Spool Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Starting a Spool Writer Using a Control Command . . . . . . . . . . . . . . 20-6
Starting a Spool Writer Using an Option from a Menu . . . . . . . . . . . . 20-7
Stopping a Spool Writer Using a Control Command . . . . . . . . . . . . . 20-7
Stopping a Spool Writer Using an Option from a Menu . . . . . . . . . . . 20-7
Restarting a Spool Writer Using a Control Command . . . . . . . . . . . . 20-7
Restarting a Spool Writer Using an Option from a Menu . . . . . . . . . . 20-7
Assign a Printer as the System Printer . . . . . . . . . . . . . . . . . . . . . 20-8
Creating Printed Output — Selected Examples . . . . . . . . . . . . . . . . . 20-8
Configuring Printer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Chapter 21. Working with SSP Subsystems . . . . . . . . . . . . . . . . . 21-1

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
SSP Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
OS/400 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Starting an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Ending an SSP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Displaying the Status of an SSP Subsystem . . . . . . . . . . . . . . . . . . . 21-2
Chapter 22. SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

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

Working With Current Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Working with the History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Chapter 24. Working with SSP Devices and Communications . . . . . . 24-1

Displaying Communications Lines and Controllers . . . . . . . . . . . . . . . . 24-1
Configuring Remote Communications Lines . . . . . . . . . . . . . . . . . . . 24-1
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine

Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
Saving and Restoring an AS/400 Advanced 36 Machine . . . . . . . . . . . . 25-1
Saving the AS/400 Advanced 36 Machine Library . . . . . . . . . . . . . . 25-1
Saving the AS/400 Advanced 36 Machine Object and Configuration Object 25-1
Restoring the AS/400 Advanced 36 Machine Library . . . . . . . . . . . . . 25-2
Restoring the AS/400 Advanced 36 Machine Object and Configuration
Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
Saving and Restoring the SSP Operating System, Licensed Programs, and
Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
Initializing Tapes to Save the SSP Operating System, Licensed Program
Product and Other SSP System Files . . . . . . . . . . . . . . . . . . . . . 25-2
Saving the SSP Operating System Using the SAVELIBR Procedure . . . 25-3
Saving the Licensed Program Products . . . . . . . . . . . . . . . . . . . . 25-3
Saving the Licensed Program Products Interactively . . . . . . . . . . . 25-5
Creating a Procedure to Save Licensed Program Products . . . . . . . 25-7
Saving the Licensed Program Products Using a Previously Created
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8
Saving Other SSP System Files . . . . . . . . . . . . . . . . . . . . . . . 25-12
Saving Other SSP System Files Interactively . . . . . . . . . . . . . . 25-13
Creating a Procedure to Save Other SSP System Files . . . . . . . . 25-16
Saving the Other SSP System Files Using a Previously Created
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-18
Restoring the SSP Operating System . . . . . . . . . . . . . . . . . . . . 25-18
Using the Restore Library Procedure to Restore the SSP Operating
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19
Restoring the SSP Operating System Using the Start AS/400
Advanced 36 Machine Command . . . . . . . . . . . . . . . . . . . . 25-21
Restoring the Licensed Program Products . . . . . . . . . . . . . . . . . . 25-24
Restoring the Licensed Program Products Interactively . . . . . . . . . 25-25
Creating a Procedure to Restore Licensed Program Products . . . . . 25-27
Restoring the Licensed Program Products from a Previously Created
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-29

Restoring the Other SSP System Files . . . . . . . . . . . . . . . . . . . . 25-32
Restoring the Other SSP System Files Interactively . . . . . . . . . . . 25-33
Creating a Procedure to Restore the Other Saved SSP System Files 25-35
Restoring the Other SSP System Files from a Previously Created
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-37
Chapter 26. Working with SSP Program Temporary Fixes . . . . . . . . 26-1

AS/400 Advanced 36 Program Maintenance Strategy . . . . . . . . . . . . . . 26-1
Preventative Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
Cumulative PTF Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
Corrective Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Corrective Service SSP PTFs . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Ordering SSP PTFs and PTF Information . . . . . . . . . . . . . . . . . . . . . 26-3
Displaying or Printing Cumulative PTF Information . . . . . . . . . . . . . . . 26-3
Installing Cumulative SSP PTF Packages . . . . . . . . . . . . . . . . . . . . 26-5
Corrective SSP PTFs (Patches) . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5
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-9
Installing SSP PTFs That Were Sent Electronically . . . . . . . . . . . . . 26-9
Installing a Saved PTF That Was Sent Electronically . . . . . . . . . . 26-13
Displaying or Printing Corrective SSP PTF Information . . . . . . . . . . 26-14
Removing Corrective SSP PTFs . . . . . . . . . . . . . . . . . . . . . . . 26-15
Mapping the TC Device ID to the CD-ROM Drive . . . . . . . . . . . . . . . 26-16
What to Do if the Mapping Failed . . . . . . . . . . . . . . . . . . . . . . . . 26-17
Changing the TC Device ID Back to a Tape Cartridge Drive . . . . . . . . . 26-17

Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1
Using Remote Work Station Support . . . . . . . . . . . . . . . . . . . . . . . 27-1
Establishing the Communications Link . . . . . . . . . . . . . . . . . . . . . 27-1
Ending the Communications Link . . . . . . . . . . . . . . . . . . . . . . . . 27-2

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 are
OS/400 commands, directions for starting your AS/400 Advanced 36 machines are
in this chapter since you cannot use SSP without starting the AS/400 Advanced 36
machine.
For directions on using SSP sign-on displays, see Chapter 2 of the Operating Your
Computer–SSP Operating System book, SC21-8297.
Starting the AS/400 Advanced 36 Machine from the OS/400 Command

line
You use the Start AS/400 Advanced 36 Machine (STRM36) command to start an
AS/400 Advanced 36 machine.
The STRM36 command starts an existing AS/400 Advanced 36 machine as a guest

of the OS/400 operating system. Essentially, an IPL of the AS/400 Advanced 36
machine is performed.
You can either type the command and the appropriate parameters on an OS/400
command 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 a
parameter and pressing F1.
The AS/400 Advanced 36 machine must already be created. The AS/400

Advanced 36 machine contains a copy of the last applied AS/400 Advanced 36
machine configuration.
If you want to create an AS/400 Advanced 36 machine configuration, use the

Create AS/400 Advanced 36 Machine Configuration (CRTM36CFG) command. For
more information on the CRTM36CFG command, see the CL Reference book,
SC41-4722.
Requirements for Using the Start AS/400 Advanced 36 Machine

Command
If the SSP needs to be loaded onto the AS/400 Advanced 36 machine, as
would be the case if the AS/400 Advanced 36 machine was just created, then
IPLTYPE is a required parameter. Specify the device in which media (a
diskette, 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 the
machine, and the machine was not created through a conversion of a 236/436
AS/400 Advanced 36 machine definition to an AS/400 Advanced 36 machine,
then APYM36CFG is a required parameter.

Using the IPL Type (IPLTYPE) Parameter

This parameter specifies the type of IPL to perform and the device from which it is
performed. You can specify any of the following keywords for the parameter:
*M36 This is the default. This specifies to use the type of IPL (attended
or unattended) defined in the AS/400 Advanced 36 machine.
*UNATTEND An unattended IPL is performed from the fixed disk of the AS/400
Advanced 36 machine. In an unattended IPL, the system operator
cannot sign on either to change the system date and time, or to
specify IPL overrides.
*ATTEND An attended IPL is performed from the fixed disk of the AS/400
Advanced 36 machine. In an attended IPL, the system operator
must sign on to the AS/400 Advanced 36 machine. The system
date and time of the AS/400 Advanced 36 machine can be
changed and IPL overrides can be specified.
*I1 An attended IPL is performed from the diskette drive. For
directions on defining a diskette drive, see “Defining a Diskette
Device” 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 or
CD-ROM Device” on page 31-10.
*T2 An attended IPL is performed from the media drive defined for T2.
*TC An attended IPL is performed from the media drive defined for TC.
device-name Specify the name of the OS/400 device description from which you
want to IPL. An attended IPL is performed from the drive by that
name.
For information on how the IPLTYPE parameter affects the starting of an AS/400
Advanced 36 machine, see Figure 15-1 on page 15-4.
Using the User Profile (USRPRF) Parameter

This parameter controls the OS/400 job attributes and the authority available to the
AS/400 Advanced 36 server job. For information on AS/400 Advanced 36 server
jobs, see “Understanding Server Jobs” on page C-1.
If you sign on to an SSP display station that was automatically acquired by the
AS/400 Advanced 36 machine or run an SSP batch job and:
You use the RUN400 OCL statement, the job runs under the USRPRF user
profile.
You send printed output to an OS/400 output queue, the printed output belongs
to 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 the

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/400
Advanced 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 the
Change AS/400 Advanced 36 Machine Configuration (CHGM36CFG)
command, you must use the APYM36CFG parameter on the STRM36
command to apply the changes to the AS/400 Advanced 36 machine. The
changes will not affect an AS/400 Advanced 36 machine until you do this.
For more information on using the CHGM36CFG command, see
Chapter 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 36
The name of the AS/400 Advanced 36 machine configuration can be
qualified by one of the following library values:
*LIBL All libraries in the job's library list are searched until the first
match is found.
*CURLIB The current library for the job is searched. If no library is
specified as the current library for the job, the QGPL library is
searched.
library-name Specify the name of the library to be searched.
For information on how the APYM36CFG parameter affects the starting of an

AS/400 Advanced 36 machine, see Figure 15-1.
Chapter 15. Starting an AS/400 Advanced 36 Machine 15-3

Advanced 36 Machine Object

STRM36 USRPRF
(user profile) Temporary
STRM36 IPLTYPE USRPRF IPLTYPE

(IPL type)
STRM36 USRPRF(*M36) IPLTYPE(*M36)
Applied Advanced 36
Advanced 36 Machine Machine Configuration
Configuration Object 1. Attributes
CRTM36CFG
or 1. Attributes: IPLTYPE 2. Display and printer devices
and USRPRF
CHGM36CFG STRM36 APLYM36CFG 3. Display and printer device
(config name) attributes
2. Display and printer devices 4. Tape and optical devices
3. Display and printer device 5. Diskette devices
attributes
4. Tape and optical devices 6. Communication lines
5. Diskette devices
6. Communication lines Overwrite at IPL
Temporary Advanced 36
Machine Configuration
1. Attributes
2. Display and printer devices
3. Display and printer device
attributes
CHGSYSVL 4. Tape and optical devices

DEVMAP 5. Diskette devices
(SSP procedure) 6. Communication lines
RV3P219-0
Figure 15-1. How the STRM36 Parameters Affect an AS/400 Advanced 36 Machine
Starting an AS/400 Advanced 36 Machine — Examples

Example 1
STRM36 M36(ADV36M)
This command performs an IPL of an AS/400 Advanced 36 machine named ADV36M

that is located through the library list of the OS/400's job in which the STRM36
command is run.
The IPL type and user profile are taken from the configuration last applied to the
AS/400 Advanced 36 machine. You can display the current IPL type and user
profile 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/400
Advanced 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 last
machine configuration object that was applied to the AS/400 Advanced
36 machine.
2. Stop the machine. For directions, see Chapter 16, “Stopping an AS/400
Advanced 36 Machine.”
3. Start the machine again using the APYM36CFG parameter on the STRM36
command to apply that machine configuration to the machine.
Example 2

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 changes
to the IPLTYPE parameter.
This command performs an IPL of an AS/400 Advanced 36 machine named ADVM36

that is located in the library named MYLIB. The IPL is performed from the media
drive 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 default
authority and job attributes of the AS/400 Advanced 36 machine. The AS/400
Advanced 36 machine configuration named MYM36CFG which is located in the library
named MYLIB is applied to the AS/400 Advanced 36 machine.
Starting the AS/400 Advanced 36 Machine Automatically

If you want your AS/400 Advanced 36 machines to start up automatically when you
IPL your AS/400 system, you need to create a customized start-up program. For
directions, see “Creating a Customized IPL Start-Up Program” on page 15-5.
How To Change a Configuration for an AS/400 Advanced 36 Machine

That 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 may
need 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 to
temporarily change the user profile or the type of IPL. The next time you do an IPL
of the AS/400 Advanced 36 machine without specifying these parameters, the
values in the machine configuration are used.
Creating a Customized IPL Start-Up Program

To change the IPL start-up program, complete the following steps from an OS/400
command prompt unless directed otherwise:
1. If you do not already have an editor installed with which you can edit a source
member, 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, create
one as follows:

a. Type
CRTLIB yourlib
where yourlib is the name of the library in which you want to store the
start-up program source member.
b. Press Enter.
3. If you do not already have a file in which to store your start-up program source
member, create one as follows:
a. Type
CRTSRCPF yourlib/yourfile
where yourlib is the name of the library in which you want to store the
start-up program source member and yourfile is the name of the file in
which 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 as
follows:
a. Type
RTVCLSRC PGM(QSYS/QSTRUP) SRCFILE(yourlib/yourfile)
Where yourlib is the name of the library in which you want to store the
start-up program source member and yourfile is the name of the file in
which 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-name
MONMSG MSGID(CPFðððð)
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 you want to start automatically.
Notes:
a. The number .1/, shown in reverse highlighting in Figure 15-2 on
page 15-8, indicates where to add the lines to the sample start-up program
to start the AS/400 Advanced 36 machine automatically.
b. Repeat step 5 on page 15-6 for each AS/400 Advanced 36 machine that
you 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.

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-up
program:
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 the
library where you stored your start-up program.
10. Press Enter.
Sample QSYS/QSTRUP Start-up Program

Figure 15-2 on page 15-8 shows the source for a CL program highlighted with the
changes you make. The changed start-up program resides on OS/400. You will
add two lines where .1/ is shown in reverse highlighting in Figure 15-2 on
page 15-8. You replace library-name with the name of the library in which the
AS/400 Advanced 36 machine resides, and you replace machine-name with the
name of the AS/400 Advanced 36 machine that you want to start. You can add
additional lines for your other AS/400 Advanced 36 machines.

Figure 15-2. Example of Modified QSYS/QSTRUP Startup Program. This example program starts a single AS/400
Advanced 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)
32ðð
33ðð QSYS/RLSJOBQ JOBQ(QGPL/QS36EVOKE)
35ðð
36ðð QSYS/STRCLNUP
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)
46ðð
47ðð QSYS/STRSBS SBSD(QBATCH)
49ðð
5ððð QSYS/STRSBS SBSD(QCMN)
52ðð
53ðð QSYS/STRSBS SBSD(QSERVER)
55ðð
56ðð
57ðð
58ðð
59ðð DONE:
6ððð .1/ QSYS/STRM36 library-name/machine-name
62ðð
63ðð QSYS/RTVSYSVAL SYSVAL(QSTRPRTWTR) RTNVAR(&STRWTRS)
64ðð IF (&STRWTRS = 'ð') GOTO NOWTRS
65ðð
66ðð CALL PGM(QSYS/QWCSWTRS)
68ðð
69ðð NOWTRS:
7ððð RETURN
71ðð CHGVAR VAR(&CPYR) VALUE(&CPYR)
72ðð /\ Needed to include CPYR variable in program. \/
73ðð ENDPGM

For information on automatically starting ILAN communications, see “Automatically

Starting ILAN Communications” on page 29-6.
For information on manually starting ILAN communications, see “Manually Starting

the ILAN” on page 29-3.


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 Advanced
36 machine. You should always use the SSP POWER OFF command to stop your
AS/400 Advanced 36 machines. If the AS/400 Advanced 36 machine is stopped in
any 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 might
be 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 under
normal circumstances.
Stop an AS/400 Advanced 36 machine from the OS/400 operating system only
when you cannot stop it normally from the SSP system console.
Putting the AS/400 Advanced 36 Machine In a Dedicated State

Certain operations, such as stopping an AS/400 Advanced 36 machine, require the
AS/400 Advanced 36 machine to be in a dedicated state.
Note: The following steps refer to the SSP command display and the SSP console
display. The SSP command display is the display where an operator can
display or send messages and use control commands and procedures to
start and control jobs. The SSP console display is a display that can only
be requested from the SSP system console. From this display, the operator
can control the operation of the AS/400 Advanced 36 machine. For more
information on the SSP command display and the SSP console display and
how to switch between the two, see “Using the SSP Console Display” on
page 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 SSP
system console.
a. Send a message to all users to inform them that you are going to put the
system 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 be
completed 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

Stopping SSP
Or,
D W
2) Press Enter.
c. If users are still signed on, you can send them another message or use
option 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 system
console:
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, and
perform 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 System

Console
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 SSP
console 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 you
power down or IPL the AS/400 system.

Stopping SSP

System
| 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/400
Advanced 36 machine from the SSP console using the POWER OFF command.
When you use the ENDM36 command to stop the AS/400 Advanced 36
machine:
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
might be in an unknown condition.
The ENDM36 command ends (stops) the AS/400 Advanced 36 machine imme-
diately.
To use the ENDM36 command:

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 that
you want to end.
4. In the Library field, type the name of the library that contains the AS/400
Advanced 36 machine, *LIBL if your library list is to be searched for the AS/400
Advanced 36 machine or *CURLIB if the current library is to be searched for
the 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/400
Advanced 36 machine, causes the OS/400 operating system to attempt to
dump the contents of the AS/400 Advanced 36 machine to disk. A message is
sent to the QSYSOPR message queue. The message indicates whether the
dump was successful. If the dump was created, the message tells you the type
of object the dump was written to, the name of the object and the library the
object is located in.
You can use either the OS/400 Dump Object (DMPOBJ) command or the
OS/400 Dump System Object (DMPSYSOBJ) command to copy the dump to a
spool 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, diskette
or a *SAVF.
If you call your service representative to report the problem, this dump will be
very 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

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 named

MYM36, located through the library list of the OS/400 job in which the command is
run. A main storage dump of the AS/400 Advanced 36 machine is not generated
because 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 Advanced
36 machine is generated while the AS/400 Advanced 36 machine is ending.

Using SSP Console, Subconsoles
Chapter 17. Operating the SSP Console and SSP

Subconsoles
This chapter describes how to use the SSP console and SSP subconsole after you
sign on. You can:
Transfer the SSP console function to an alternative SSP console (CONSOLE
GIVE 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 36

Machine
An SSP console, like other display stations, is made up of a keyboard and a
display. 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 SSP
console 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 command
display station or SSP subconsole, provided their display station was configured as
an 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 the
control of the SSP console to an alternative SSP console, refer to “Transferring the
SSP Console Function to an Alternative SSP Console” on page 17-2.
The SSP Subconsole: A Way of Controlling SSP Printers

During system configuration, you may have had one or more display stations con-
figured as an SSP subconsole. An SSP subconsole operator may then use the
SSP 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.

For more information about data display stations and command display stations,
refer to the Using Your Display Station – Advanced 36 book, SC21-0209.

The SSP console and the alternative SSP consoles are specified during system
configuration. You can transfer the SSP console function to an alternative SSP
console:
During an attended IPL.
If you are using the SSP console, and you find it necessary to leave the SSP
console (you may want another operator to control the system in your
absence).
If the SSP console does not work.
Transferring the SSP Console Function During an Attended IPL

Turn on the display station that was specified as an alternative SSP console and is
to 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.

Transferring the SSP Console Function When the SSP Console Is in

Operation
To transfer the SSP console function to an alternative SSP console, the CONSOLE
GIVE command must be entered at the SSP console and the CONSOLE TAKE (or
CONSOLE) command must be entered at an alternative SSP console.
Note: If the CONSOLE GIVE command is entered at the SSP console and then
the CONSOLE TAKE command is entered at the SSP console, the
CONSOLE GIVE command is canceled.

When 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 SSP
console and is to become the SSP console. The ID is shown in the WS-ID
column, and the alternative SSP console (Alt Console) is shown in the TYPE
column.
Note: If you do not type the ID, any display station that was defined as an
alternative SSP console during system configuration can become the
SSP console.
4. Press Enter.
Making an Alternative SSP Console the SSP Console

To have an alternative SSP console become the SSP console, use a command
display at the alternative SSP console. For this example, the Main System Help
menu 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 command
at the SSP console, only the alternative SSP console with that display
station ID can be used to enter the CONSOLE or CONSOLE TAKE
command.
If a display station ID was not entered with the CONSOLE GIVE command at
the SSP console, any alternative SSP console can be used to enter the
CONSOLE 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 at
the SSP console or if the SSP console is signed off, in error, or turned
off.
Chapter 17. Operating the SSP Console and SSP Subconsoles 17-3
Transferring the SSP Console Function When the SSP Console Is Not
in Operation
When the SSP console does not work, type CONSOLE or CONSOLE TAKE on the
command display at any alternative SSP console. The alternative SSP console can
then operate as the SSP console.
Note: If you have interrupted a job (Inquiry Options display), you cannot use the
CONSOLE command. For more information about the Inquiry Options
display, refer to the Using Your Display Station – Advanced 36 book,
SC21-0209.
Using the SSP Console Display

The SSP Console display can be displayed only at the display station designated
as 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 SSP
Console display is shown:
à@ SYSTEM CONSOLE W1
ð
á ñ
You can use the SSP Console display to receive and send messages, and to enter
all 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 word
CONSOLE in the upper-right corner or the lower-right corner, to enter procedure
commands. These commands must be entered on a Command display. To return
to a display after using the SSP Console display:
2. Press Enter with the input line blank.

You return to the original display.
Requesting a Help Menu from the SSP Console Display

To 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 help
menu.
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, press
Enter.
Using the Subconsole Display

The 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). To
request this display:
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 enter
control commands except JOBQ, MENU, MODE, and OFF. You cannot enter
control commands that are restricted to the system console, such as START
SYSTEM and STOP SYSTEM. You may want to use this display to monitor
system activity, respond to messages, or send messages when the SSP console is
being 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 procedure
commands. These commands must be entered on a command display.
Chapter 17. Operating the SSP Console and SSP Subconsoles 17-5
To return to a display after using the Subconsole display:

You return to the original display.
Requesting a Help Menu from the Subconsole Display

To 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 help
menu.
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, press
Enter.

SSP Messages
Chapter 18. Handling SSP Messages

A message is a way for SSP operating system to communicate with you and for
you 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 Message

The following summarizes how you know that SSP or another operator has sent
you a message:
A blinking 4-digit number appears in the lower-left corner of your display, and
the Input Inhibited light is on at your display station. You have a keyboard
message waiting to be displayed. For information on keyboard errors, see
“SSP Keyboard Error Messages” on page 18-10 or see “Displaying Keyboard
Messages” in the Using Your Display Station – Advanced 36 book, SC21-0209.
A message appears and an alarm may sound. A procedure that you are
running displayed the message. For information on keyboard errors, see “SSP
Keyboard Error Messages” on page 18-10 or see “Understanding the Kinds of
Messages that Are Displayed” in the Using Your Display Station – Advanced 36
book, 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 “Displaying
SSP Messages at the SSP Console or Subconsole” on page 18-6 in this book
or “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 “Sending
SSP Messages” on page 18-9.
When you want to display local or remote messages while in a Display Station
Pass-Through session, see “Displaying Messages While in a Display Station Pass-
Through Session” in the Using Your Display Station – Advanced 36 book,
SC21-0209.

SSP Messages
Types of SSP Messages

When an alarm sounds and a message appears, or if there is no alarm but a
message 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 Action

SSP 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 Response

SSP displays a message for various reasons. For example, you might use a
command or a procedure that requests SSP to perform an action that is not
allowed. When this happens, you need to enter a response to the message. The
message has an identifier, options that you can enter, and text that explains the
message. Following is an example of a message that requires a response:
A B
D E
F C RTSP033-0
You can have SSP respond to some messages for you. This is called automatic
response. For more information on automatic response, see “NOHALT Procedure”
in the S/36 System Reference book, SC21-9020.

SSP Messages
The message identifier .A/ is 3- or 4-alphabetic characters followed by a dash

and four numbers. Each message that has an identifier, other than USER, is
described 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 are
described:
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 Guide
book, 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 the
4-digit number. This number is called a message identification code.
The options .B/ you can use to respond to the message are shown within the
parentheses. Each message shows only the options that are allowed.
The following describes what generally happens when you select an option to
respond to a message. Because each message has a different description,
always refer to the Options part of each message description in the appropriate
messages book for specific details.
Chapter 18. Handling SSP Messages 18-3

SSP Messages
Option 0: When you select this option, generally the error is ignored and the
job continues.
Option 1: When you select this option, generally the operation that caused the
error is retried and you can continue the job.
Option 2: When you select this option, generally the job step is ended. If this
option 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, option
D is not displayed and is not described in the message description. When you
select option D, the contents of main storage and System/36 Emulator control
block storage are copied into the dump area on disk. SSP actions described
for option 3 occur.
Option H: This option is available when option 3 is displayed if you are using a
help display. When you select this option, the display where you made the
error 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 additional
information that you can display for the message. If you press Enter or the
Help key without typing an option number, the additional message information
display is shown.
Use the message identifier .A/ to refer to the message description in the
appropriate 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 an
8-character system reference code in the message text .C/. If you are unable
to solve the problem, refer to the appropriate system problem determination
book. 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 your
response on the entry line .F/ and press Enter.
If you are using the Console display, you must respond to the message with the
REPLY command, which is described later in this chapter.

SSP Messages
Additional Information for a Message

Following 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 appropriate
to 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 Console

An informational message could be displayed at your display station by an SSP
procedure 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 History
file.
The following messages are examples of informational messages because they do

not 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 was
written by a programmer).

SSP Messages
Specifying That Informational Messages Are Not to Be Displayed

at the SSP Console
If you are using the SSP console, enter the INFOMSG NO command on a
command display. Then, if you do not want to use the REPLY command to reply
to 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 that
are responses to a command, such as CANCEL command successful, are
displayed. An informational message such as Payroll procedure is
running is not displayed.
b. If an alarm sounds and no apparent message has been sent to the console
display, the job that sent the message has ended and the message was
removed. This happens if, during SSP configuration, the option to keep
informational 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 INFOMSG
command to indicate that most informational messages are to be displayed.
Displaying SSP Messages at the SSP Console or Subconsole

To display a message that was sent to the SSP Console display when you are
using a command display or when you are running a job, switch to the SSP
console display or a Subconsole display. To switch:
2. Press Enter with the input line left blank. A console or subconsole display is
shown 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 to
SSP Messages at the SSP Console or Subconsole” on page 18-7.
A job that is running may have displayed a message. Return to the command
display.

SSP Messages
Replying to SSP Messages at the SSP Console or Subconsole

The display you use when you reply to a message at the Console display and the
Subconsole 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 another
operator, and information that you have entered on the Console display. When
this area is full, the old (top) entries roll up and off the display and the new
entries appear at the bottom of the display.
Messages that require a reply, which you have not replied to, will not roll off the
display. A message is displayed if the display is full of messages that you
have not replied to. You must reply to some of the messages to get any new
messages. 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 to
messages.
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 side
of the display. After you reply to a message, the reply ID is replaced by two aster-
isks (**).

SSP Messages
Replying to Messages - Example

Following is an example of messages displayed on the Console display, and how to
reply 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. The

message has a reply ID of 01.
To reply to message 01, type one of the following:
– REPLY 01
– R1
– 1
To reply to all informational messages that have a reply ID, type one of the
following:
– REPLY I
– RI
If you do not want informational messages to be displayed, use the INFOMSG
NO command. See “Specifying That Informational Messages Are Not to Be
Displayed” 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 an
option (012) when you reply. The three periods (...) indicate there is additional
information 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

SSP Messages
4 (or ð4)
2. Press Enter.
Possible options that could be displayed for a message and their meanings are
explained in “Messages That Require a Response” on page 18-2.
These messages .C/ are responses to messages or messages that do not
require a response. To clear (remove from the display) these messages and
messages that have been replied to, type one of the following:
– REPLY C
– RC
This is the 8-character ID .D/ of the job that received this message. This field
shows SYSTEM if a message was issued by an SSP function.
Use the message identifier .E/ to refer to the message description in the
appropriate 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 an
8-character system reference code .F/ in the message text. If you are unable
to solve the problem, refer to the appropriate system problem determination
book. 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 Messages

There 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 Message

The 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 with
the AS/400 Advanced 36 machine
A user on another AS/400 Advanced 36 machine for which communications are
set 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 let
everyone 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

SSP Messages
This message was sent to all of the user IDs that were active on the AS/400
Advanced 36 machine.
Using the MSG OCL Statement to Send an SSP Message

The MSG OCL statement is similar to the MSG Control Command. The MSG OCL
Statement 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 with
A user on another AS/400 Advanced 36 machine for which communications are
set 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 everyone
know 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 any
of the display stations currently signed on to that AS/400 Advanced 36 machine.
Using the OFCMSG Procedure to Send a Message

The OFCMSG procedure allows you to send messages to more than one user or
display station in an office environment. The user or display station can be locally
attached or on another system. This is done interactively.
Note: The OFCMSG procedure can only be used if Personal Services/36 is
installed on your system.
SSP Keyboard Error Messages

When you press the wrong keyboard keys by mistake, the computer simply stops
and tells you what is wrong. The computer has locked up the keyboard so you
cannot continue your task until you make the necessary correction.
Error Reset Key

The Error Reset key (or Reset key) is used to unlock the keyboard from a keyboard
error or an invalid answer to a prompt. The Error Reset key is also used to unlock
the 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.

SSP Messages
Displaying Keyboard Messages

If you have a blinking 4-digit number in the lower left corner of the display and the
Input Inhibited light is on at your display station, you have a keyboard message
waiting to be displayed. If you know the cause of the error, press the Error Reset
key and enter the required data again.
If you do not know the cause of the error, press the Help key. A message appears
on the bottom line of the display. If you need an explanation of the message, refer
to the S/36 System Messages book, SC21-7938. Then, take the recommended
action to continue processing. Following is an example of a keyboard message:
COMMAND W4
Cmd3-Previous menu Cmd5-Main help menu Home-Sign on menu
Ready for command or procedure.
KBD-0009 This field requires numeric characters
RTSN017-0
Keyboard Message

SSP Messages

SSP Commands
Chapter 19. Using SSP Commands and Procedures to Do

Tasks
SSP Control Commands are used to control the AS/400 Advanced 36 machine, the
printers and the display stations. You can use the Help key or HELP procedure on
Control Commands to find out more information about the commands. The Control
Commands can be entered from the keyboard or selected by a menu option. They
cannot be coded in a procedure.
SSP Procedures are used to do various tasks on the AS/400 Advanced 36 machine
such as creating files, creating libraries, copying files and compiling programs. You
can 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 Procedures

When 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 the
command or procedure that does the task.
When You Know the Name of a Command or a Procedure

Use the following steps when you know the name of the command or procedure
that does the task.
1. Type the name of the command or procedure on the entry line of a command
display.
2. Press the Help key. A menu, a command, or a procedure display is shown at
your display station. This menu, command or procedure display enables you to
do the task.
Note: You can accomplish the same thing by typing HELP followed by the
name of the command or procedure on the entry line of a command
display and pressing Enter.
3. If a menu is shown, you can select an option to do a specific task. If there is
another menu for the option and you press Cmd11, the name of the next menu
for the option is shown on the right side of the menu options. To show that
menu, type the menu name of the command line and press the Help key. If
you press the Help key without typing anything, the help text for the menu that
is currently on your display station is shown.
4. If a command is shown, you can run that command by pressing Enter. If you
press the Help key again, the help text for the command that is on your display
station is shown.
If a procedure display is shown, you can type the necessary parameters on the
prompt lines. Then, press Enter to perform the task described at the top of the
procedure display. If you press the Help key again, the help text for the proce-
dure display is shown.

SSP Commands
Example 1
Type
HELP STATUS
When you press Enter, the following STATUS menu is shown at your display
station:
à@ ð
STATUS W1
Display general status information
Select one of the following:
1. Spool file entries (PRT) SPOOLJOB

2. Spool writer (WRT) SPOOL
3. Jobs on the job queue (JOBQ) JOBQUEUE
4. Currently running jobs (USERS) JOBS
5. Devices on the system (WORKSTN) DEVICES
6. System activity (SYSTASK) SYSACT
7. Session status (SESSION) JOBENVR
8. Message at subconsoles (MESSAGE) SUBCMSG
9. Communications COMMSTAT
1ð. 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 menu
option 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 to
the description of the specific status that can be displayed. If any of the listed
actions 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. The
help for the STATUS menu is displayed at your display station.

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. Help
for the POWER command is displayed at your display station.
Chapter 19. Using SSP Commands and Procedures to Do Tasks 19-3

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 first
prompt line and FILENEW on the second prompt line. Then press Enter.
To display additional help about the RENAME procedure, press the Help key. The
help for the RENAME procedure will be shown at your display station.
For more information about help support, see “Help for Commands and
Procedures” in the Using Your Display Station – Advanced 36 book, SC21-0209.
When You Do Not Know the Name of a Command or a Procedure

Use 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 Help
key.
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 next
menu 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 command
line and pressing the Help key.

SSP Commands
If you press the Help key without typing anything, the help text for the Main
menu 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 that
does the task is displayed.
5. Type the necessary parameters on the input lines of the procedure or
command 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 display
or 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
1. Display a user menu MENU

2. Perform general System activities SYSSESN
3. Use and control printers, diskettes, or tape USEDEV
4. Work with files, libraries, or folders LIBRFILE
5. Use programming languages and utilities PROGRAM
6. Communicate with another system or user SYSCOMM
7. Define the system and its users DEFSYS
8. Use problem determination and service PROBSERV
9. Use office products OFCPROD
1ð. Sign off the system OFF
Cmd3-Previous menu Cmd7-End Cmd12-How to use help Home-Signon menu
á ñ
The option that best describes what you were asked to do (put a job on the job
queue) is option 2 Perform general system activities.
2. Type a 2 on the command line and press Enter.

SSP Commands
The SYSSESN menu is shown at your display station.
à@ SYSSESN W1
ð
Perform general system activities
1. Control session environment SESNENVR

2. Handle messages MESSAGE
3. Control printing (spool file) SPOOLJOB
4. Control jobs and the job queue JOBS
5. Work with files, libraries, and folders LIBRFILE
6. List or work with history file HIST
7. Display general status information STATUS
8. Change or control the status of devices DEVICES
9. Stop or start system activity SYSACT
1ð. Help with system procedures and control commands COMMAND
Cmd3-Previous menu Cmd7-End Cmd12-How to use help Home-Signon menu
á ñ
queue) 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 display
station.
à@ 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 queue
1. Display a specific job 6. Change processing priority
2. Jobs on the job queue 7. Prevent jobs from starting
3. Stop a job 8. Allow jobs to start
4. Restart a stopped job 9. Prevent SSP-ICF jobs
5. Cancel a job 1ð. Allow SSP-ICH jobs to start
á ñ
queue) is option 2 Jobs on the job queue.

SSP Commands

2
to select Jobs on the job queue
6. Press Enter.
The JOB QUEUE STATUS display and the JOBQUEUE menu is shown at your
display station.
à@ Complete JOB QUEUE STATUS W1

ð
Jobs 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

--------------------------------------------------------------------
JOBQUEUE
Jobs on the job queue
1. Display specific job(s) 6. Start the job queue
2. Put a job on the queue 7. Stop the job queue
3. Cancel a job 8. Change position of a job
4. Hold a job 9. Change processing priority
5. Release a job 1ð. Change maximum active jobs
á ñ
queue) is option 2 Put a job on the queue.
2
to select Put a job on the queue.
8. Press Enter.
The JOBQ COMMAND display overlays the JOBQUEUE menu at your display
station.

SSP Commands
à@ Complete JOB QUEUE STATUS W1

ð
Jobs in Queue: o of 8ð JOBQ PRTY STOPPED : ð
SYS-5689 The job queue is empty now

--------------------------------------------------------------------
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 was
successfully 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 and
Procedures” 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.

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 printer
output and printer output created by others, you only need to know the essentials.
Spooled Files
In OS/400, a spooled file is a file that holds output data waiting for printing. It is
also 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) special
authorities 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 printer
output goes to this spool file.
Printer Writers
In OS/400, the printer writer is a system program that writes spooled files to a
printer.
In SSP, the equivalent to a printer writer is the Spool Writer. The spool writer is the
part of SSP that prints output saved in spooled file entries.
Output Queues
In 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 an

OS/400 output queue, see “Defining Whether SSP or OS/400 Controls SSP Printer
Output” on page 31-26.
Printers
For directions on specifying whether a printer is assigned to an AS/400 Advanced
36 machine or shared with OS/400, see Chapter 31, “Changing Your AS/400
Advanced 36 Machine Configuration” on page 31-1. For more information on
OS/400 printing, see Chapter 7, “Printing with OS/400” on page 7-1.
The operating systems can share the same printer. For directions on sharing
printers, 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 job
tries to use a printer that another SSP or OS/400 job is using, the job receives an

SSP Printing
error stating that the printer is in use. If an OS/400 job tries to use a printer that an
SSP 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 SSP
and OS/400. This prevents SSP and OS/400 from trying to acquire the same
printer. The output queue is specified either on the PRINTER OCL statement or in
the configuration of the Advanced 36 machine.
In order to use non-twinaxial printers, such as ASCII printers and LAN-attached

printers, the output must be directed to an output queue and then printed using the
OS/400 printer writers.
Additional reading: For detailed information about printing elements, printer

device support, printer spooling support, and Advanced Function Printing* (AFP*),
see the Printer Device Programming book, SC41-4713.
Finding SSP Printer Output

There are two ways of finding all the SSP printer output for which you are
authorized:
Using the SSP Help support
If you have the Value Added Software Package installed on your AS/400
Advanced 36 machine, you can use the WRKSPL command.
Using SSP Help Support

To 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) Command

To use the WRKSPL command, do as follows:
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.

SSP Printing
Managing Printer Output — Command Summary

The following commands can be used from your AS/400 Advanced 36 machine to
manage 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 of
printers.
| 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, also
contains information on printing concepts.
Managing Printer Output — Complete Details

To manage printer output you can use:
Control commands
Options selected from a menu
Options from a display
Chapter 20. Printing with SSP 20-3

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:

G
which is the abbreviation for the CHANGE command.
Changing Printer Output with an Option from a Menu

Select option 5 (Change entries) on the SPOOLJOB menu.
Changing Printer Output with an Option from a Display

Use 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:

HOLD PRT
Holding Printer Output Using an Option from a Menu

Select option 3 (Hold entries) on the SPOOLJOB menu.
Holding Printer Output Using an Option from a Display

Use 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.
RELEASE PRT

SSP Printing
Releasing Printer Output Using an Option from a Menu

Select option 4 (Release entries) on the SPOOLJOB menu.
Releasing Printer Output Using an Option from a Display

Use 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.
CANCEL PRT
Deleting Printer Output Using an Option from a Menu

Select option 2 (Cancel entries) on the SPOOLJOB menu.
Deleting Printer Output Using an Option from a Display

Use 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
COPYPRT
| Copying Printer Output Using an Option from a Display

Select option 6 (Copy or display entries) on the SPOOLJOB menu.
| Displaying Printer Output Using an Option from a Display

Select option 5 (Browse) on the WRKSPL display.

SSP Printing
Balancing Spooled Output Between Printers Using a Procedure

The BALPRINT procedure allows you to balance spooled output between printers in
a group.
BALPRINT
Note: You cannot balance spooled output between printers using an option from a
menu or using an option from a display.
Working with Spool Writers

There 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 spool
writers.
STATUS WRT
Or
D WRT
2. Press Enter.
The SPOOL WRITER STATUS display and the SPOOL menu are shown at
your display station.
Using a Menu to Work with Spool Writers
SPOOL
The SPOOL WRITER STATUS display and the SPOOL menu are shown at
your display station.
Starting a Spool Writer Using a Control Command

To 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

SSP Printing
Starting a Spool Writer Using an Option from a Menu

To 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 lower
half of your display station.
Stopping a Spool Writer Using a Control Command

If 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 of
the following:
STOP PRT
Or,
P P
Stopping a Spool Writer Using an Option from a Menu

To stop a spool writer using an option from a menu:
The STOP Command display overlays the SPOOL menu shown on the lower
half of your display station.
Restarting a Spool Writer Using a Control Command

You can use the RESTART command to restart printing in any of the following
places:
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 of
the following:
RESTART PRT
Or,
T P
Restarting a Spool Writer Using an Option from a Menu

To use an option from a menu to start a spool writer again:
The RESTART Command display overlays the SPOOL menu shown on the
lower half of your display station.

SSP Printing
Assign a Printer as the System Printer

To assign a printer as the system printer, do as follows:
HELP ASSIGN
2. Press Enter.
The STATUS WORK STATION display and the ASSIGN COMMAND menu is
shown at your workstation.
3. On the ASSIGN COMMAND menu, select option 2 (Assign a printer as the
system printer).
Creating Printed Output — Selected Examples

LISTDATA 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 on
disk, 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 Options

The following can be specified during system configuration using the CNFIGSSP
procedure:
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 Your
System Configuration–SSP book, SC21-8295

SSP Subsystems
Chapter 21. Working with SSP Subsystems
Definitions
SSP Subsystems
For SSP, a subsystem is the part of the operating system that handles commu-
nication requirements of the remote system or remote drives. It isolates most
system dependent considerations from the application program. The following are
examples 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 communicate

with other systems that have compatible support.
OS/400 Subsystems
For 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 default
subsystem 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 additional
subsystems 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 restricted
state to back it up.
All jobs are run in a subsystem. A subsystem creates a suitable environment for 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 subsystems
can be defined to manage those jobs. All interactive processing can occur in one
subsystem, all batch processing in another, system operator jobs in a third, and so
on.
This makes it easier to control the different jobs in the system because subsystems
can be started and ended individually.

SSP Subsystems
Starting an SSP Subsystem

To start an SSP subsystem,
1. On any SSP command line, type
ENABLE
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 Subsystem

To end an SSP subsystem:
DISABLE
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 Subsystem

To display the status of the Communications subsystems:
STATUS SUBSYS
Or,
D I
2. Press Enter.
The STATUS Information display and the CNTLLINE menu are shown at your
display station.
The status of the active subsystems are in the STATUS display. You can use
the CNTLLINE menu to control subsystems and communications lines.

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/400
Advanced 36 machine objects (*M36 and *M36CFG). OS/400 system security
does not provide password, menu, badge, communications or resource security for
the AS/400 Advanced 36 machine. This security must be provided by SSP secu-
rity.
Password Security
Password security helps prevent an unauthorized person from signing on to the
system. When password security is active, you have specified that password infor-
mation should be checked and verified. This requires that the password and the
user ID be entered when you sign on to the system. If the correct combination of
user ID and password is entered on the sign-on display, the person is allowed on
the system.
Note: If password security is active for SSP, Master Security Officer authority is
required to use certain commands such as the CHGSYSVL command. If
password security is not active, the CHGSYSVL command and other
system commands must be run from the SSP console.
A user ID can be any combination of up to 8 characters. The first character must

be 0 through 9, A through Z, #, @, or $. The remaining characters can be any
character 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 any
special character except a blank can be used.
When password security is not active, anyone can sign on to the system by
entering any user ID.
Note: The difference between four-character passwords for SSP and ten-character
passwords for OS/400 must be considered when you transfer to an AS/400
Advanced 36 machine with autosignon enabled.
The password prompt appears on the Sign-On display only if password security is
active.
Menu Security
Password security must be active to use menu security. Menu security allows you
to restrict a user to using a single menu or chain of menus. When menu security is
in effect, the menu that you specify in the user profile as the mandatory default
user menu appears after the user signs on. Unless an option on the mandatory
menu causes another option menu, help menu, or help prompt to appear, a user
cannot use another menu or the system help.

SSP Security
When menu security is in effect, the user does not have to enter a menu name in
the menu field on the Sign On display. Once the default menu is displayed, the
user can only:
Select the options on that menu
Enter the MSG and OFF control commands
Badge Security
If password security is active, you can use another type of security called badge
security. Badge security prevents unauthorized users from signing on to a display
station that has a magnetic stripe reader configured. When badge security is
active, the display station configured with a magnetic stripe reader has an Enter
badge prompt on the Sign On display.
The user must move a badge through the magnetic stripe reader as well as supply
the other information needed during sign-on. The badge has a magnetic stripe with
specially coded data. Consult your local IBM branch office for information about
obtaining badges and magnetic stripe readers, and about coding the information
needed 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 stations
with badge readers are identified during system configuration.
Not every display station needs a magnetic stripe reader. A person with a badge
can still sign on at a display station without a magnetic stripe reader. You might
decide to install magnetic stripe readers only at those display stations that are far
away from your central data processing center.
Communications Security
In order to use communications security, password security must be active for
APPC and ICF.
Communications security is only valid with the APPC (advanced program-to-

program communications) subsystem when password security is active. APPC is
the 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 you
allow it to run programs on your system. When communications security is in
effect, the local and remote locations must send and receive the same location
password to start an APPC session.
If both systems have communications security in effect, they verify each other's
identity, by exchanging location passwords, before an APPC session can be
started.
If neither system has communications security or password security, a user on one

system can access:

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 secured
system through the APPC subsystem. The secured system must create a user
profile with a user ID of *NULL. The user ID of *NULL and an access level should
be entered for the resources on your system that you will allow the system that is
not 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 the
SSP ICF BSCEL subsystem if you use Bisynchronous Communications. When the
AS/400 Advanced 36 machine is using BSCEL and is connected to a remote
system by a switched communications line. The DEFINEID procedure compares
the ID received from the remote system with the DEFINEID list. If the ID is in the
list, the communications line is connected successfully. If the ID is not found, the
remote system is disconnected.
The DEFINLOC procedure can be used for an asynchronous system using X.25
support to define remote locations that are allowed to call your system. When a
connect request is received, the location ID of the calling system is checked. If the
location ID and name are listed in the DEFINLOC list, the call is accepted. If the
location ID and name are not on the DEFINLOC list, the call is rejected.
Resource Security
Resource 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 can
use 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 have
authorized to use certain files, libraries, and folders can do so. You can, for
example, allow only the employees responsible for the payroll to update the per-
sonnel files and to run the payroll programs.
Working with SSP Security

To 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
Or,
Use the HELP SECURITY command.
Chapter 22. SSP Security 22-3

SSP Security

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.

Controlling SSP Jobs
Chapter 23. Controlling SSP Jobs

The STATUS JOBQ (D J) command can be used to control SSP JOBS. This
command 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 W1
Jobs in Queue: 4 of 8ð JOBQ PRTY STOPPED : ð
PRIORITY
1 W1ð75ðð6 JOB5 JOBLIB USER1 -- 5 N
2 W1ð75ðð1 JOB3 JOBLIB USER1 -- 3 N
3 W1ð75ð15 JOB2 JOBLIB USER1 -- 3 N
4 W1ð75ð25 JOB4 JOBLIB USER1 -- 3 N

---------------------------------------------------------------------------
JOB
Control jobs and the job queue
1. Display specific job 6. Start the job queue
2. Put a job on the job queue 7. Stop the job queue
3. Cancel a job 8. Change position of a job
4. Hold a job 9. Change processing priority
5. Release a job 1ð. Change maximum active jobs
á ñ
To perform any of the functions on the previous display, you type the option
number on the display and press Enter. The display will change to show the
command prompt for that function.

Working With Current Running Jobs

The STATUS USERS (D U) command and the WRKUSER command show all the
jobs currently running on the AS/400 Advanced 36 machine and allow the operator
to:
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 BUFF

W1ð74951 JOB1 -------- MSG-Wait ----------- Norm 24K ---- ----
W3113219 CATALOG $LABEL ACTIVE SRT Norm 24K 26K ----
W3113234 DSPSYS $VAPS ACTIVE SRT Norm 24K 18K ----

---------------------------------------------------------------------------
JOBQUEUE
Jobs on the job queue
1. Display specific job 6. Change processing priority
2. Jobs on the job queue 7. Prevent jobs from starting
3. Stop a job 8. Allow jobs to start
4. Restart a job 9. Prevent SSP-ICF jobs
5. Cancel a job 1ð. Allow SSP-ICF jobs to start
á ñ
To perform any of the functions on the previous display, type the option on the
display and press Enter. The display changes to show the command prompt for
that function.
Working with the History File

The 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

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
Use the HELP HIST command.
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


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 to
work with devices and communications from the SSP operating system. In those
cases where the information is limited, it is included in this chapter. For information
on doing these tasks from OS/400, see Chapter 11, “Working with OS/400 Devices
and Communications.”

You can use the following commands to display and change device status from the
SSP operating system:
STATUS LINE (D L)
The STATUS LINE command displays status and allows the operator to
change the communication line status.
STATUS WORKSTN (D W)
The STATUS WORKSTN command displays status and allows the operator to
change workstation, diskette, or tape status.

To print the addresses of the local workstations and printers, follow the directions in
Chapter 5 of the Changing Your System Configuration–SSP book, SC21-8295.
Displaying Communications Lines and Controllers

You can start or stop a subsystem that controls a communications line using the
STATUS LINE (D L) command to show the status of the line. You can show the
status 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 Lines

You can configure remote communications lines for your AS/400 Advanced 36
machine using the CNFIGICF procedure.

SSP Devices and Communications

Saving and Restoring SSP
Chapter 25. Saving and Restoring the AS/400 Advanced 36

Machine Information
This chapter contains information on how to save and restore the AS/400 Advanced
36 machine as an OS/400 object. It also contains information on how to save and
restore the SSP operating system, the licensed program products and other SSP
system files.
User data must also be backed up. User data is stored in files, folders and libraries
in an AS/400 Advanced 36 machine. There are 6 procedures that can be used to
save 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 user
data. For information on Backup and Recovery of your user data in the AS/400
Advanced 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 Library

The OS/400 Save Library (SAVLIB) command can be used to save the library that
contains the AS/400 Advanced 36 machine. The SAVLIB command saves the
entire 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 disaster
recovery. Individual files, folders or libraries in the AS/400 Advanced 36 machine
cannot be restored from this type of save. For more information on the SAVLIB
command, see “Saving Libraries” on page 12-4.
Saving the AS/400 Advanced 36 Machine Object and Configuration

Object
The OS/400 Save Object (SAVOBJ) CL command can be used to save an AS/400
Advanced 36 machine object and an AS/400 Advanced 36 machine configuration
object. This type of save is intended for disaster recovery. Individual files, folders
or libraries in the AS/400 Advanced 36 machine cannot be restored from this type
of save. For more information on the SAVOBJ command, see “Saving Specific
Objects” on page 12-5.

Restoring the AS/400 Advanced 36 Machine Library

The OS/400 Restore Library (RSTLIB) CL command can be used to restore a
saved library that contains the AS/400 Advanced 36 machine. This type of restore
is intended for disaster recovery. The entire library containing the AS/400
Advanced 36 machine must be restored. Individual files, folders or libraries in the
AS/400 Advanced 36 machine cannot be restored. For more information on the
RSTLIB command, see “Restoring Libraries” on page 12-6.
Restoring the AS/400 Advanced 36 Machine Object and Configuration

Object
The OS/400 Restore Object (RSTOBJ) CL command can be used to restore an
AS/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 entire
object containing the AS/400 Advanced 36 machine must be restored. Individual
files, 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, Licensed

Program Product and Other SSP System Files
Note: One 6150 tape initialized at QIC120 holds 120MB of data. This tape will
hold the SSP, all of your programming support, and the other SSP system
files that you want to save.
For information on using different kinds of tape from your AS/400 Advanced 36
machine, see Chapter 7 of the Operating Your Computer–SSP Operating System
book, 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 the
tape must by PPROD. Therefore, it is recommended that you use the
volume ID of PPROD.

3. Press Enter.
4. When the command entry display returns, remove the tape cartridge from the
tape drive and label it PPROD - BACKUP 1.
Saving the SSP Operating System Using the SAVELIBR Procedure

Use the Save Library (SAVELIBR) procedure to save the SSP operating system
library, #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. For
information on putting the system in dedicated state, see “Putting the
AS/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 the
tape 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) has
been saved to tape.
If you put the AS/400 Advanced 36 machine in a dedicated state and you are going
to save the licensed program products or other SSP system files, you can leave the
AS/400 Advanced 36 machine in dedicated state. If you are not going to perform
these tasks, remove the dedication as follows:
1. On the command line of the SSP System Console for the AS/400 Advanced 36
machine, type
START SYSTEM
2. Press Enter.
Saving the Licensed Program Products

Product libraries must be saved to tape using specific save commands for that
product (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 the
SAVE, SAVEFLDR, and SAVELIBR procedures.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-3
Before Your Begin...

1. You must specify PPROD for the volume ID when you save the product
libraries to tape.
2. It is recommended that you save the licensed program products to the
same tape where you saved the SSP operating system.
3. Make sure the tape cartridge you initialized with a volume ID of PPROD is
in the tape drive.
4. The session library must be set to #LIBRARY to use the procedures in this
section. Use the SLIB procedure to accomplish this.
a. On the command line of the SSP system console, type
SLIB ð
b. Press Enter.
icated state prior to saving the licensed program products. This will ensure
all parts of the licensed program products are saved. If you left the AS/400
Advanced 36 machine in dedicated state, you can proceed to save the
licensed program products. Otherwise, put the AS/400 Advanced 36
machine in dedicated state. For information on how to put the AS/400
Advanced 36 machine in dedicated state, see “Putting the AS/400
Advanced 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 system
console. Saving the licensed program products this way is very time con-
suming and the tape LEAVE option does not work properly. The advantage to
saving 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 you
would have keyed in if you were to save the licensed program products interac-
tively. Saving the licensed program products this way is less time consuming
and the tape LEAVE option does work properly. The disadvantage is that this
way requires previous preparation.
Note: During the saving of the licensed program products, if you receive
message SYS-2509, #######--Specified members not in this
library, record the name of the member shown in the message text.
Select option 1 for the message, this causes the save to continue. If
you are experiencing AS/400 Advanced 36 machine problems and have
reported these problems to your service representative, contact them
again. This time mention you received message SYS-2509 during a
save of your licensed program product and give them the name of the
module in the message text. If you are not experiencing any AS/400
Advanced 36 machine problems, ignore the error message.

Saving the Licensed Program Products Interactively

To save the licensed program products interactively:
1. Determine which programming support you have installed on your AS/400
2. Using Figure 25-1 on page 25-10, find the programming support functions you
have installed. If the procedure name for the programming support function is
not SAVE, SAVEFLDR, SAVELIBR or DICTSAVE:
a. Type that procedure name on the command line at the SSP system
console.
For example, if the programming support function was DFU, the procedure
name is DFUSAVE. DFUSAVE is not SAVE, SAVEFLDR, SAVELIBR or
DICTSAVE, so DFUSAVE would be typed on the command line at the SSP
system 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-1
on page 25-10 for the file name of the programming support that is to
be 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 the
SAVE procedure. The default values will work.
i. Press Enter.
If the procedure name is SAVEFLDR:
SAVEFLDR
The help display for the SAVEFLDR procedure appears.

c. In the Name of folder to save field, type the folder name. See
Figure 25-1 on page 25-10 for the folder name of the programming
support 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.
SAVEFLDR procedure. The default values will work.
g. Press Enter.
If the procedure name is SAVELIBR:
SAVELIBR
The help display for the SAVELIBR procedure appears.
c. In the Name of library to be saved field, type the library name. See
Figure 25-1 on page 25-10 for the library name of the programming
support that is to be saved.
d. In the Volume ID field, type
PPROD
TC
f. Press Enter.
SAVELIBR procedure. The default values will work.
If the procedure name is DICTSAVE:
DICTSAVE
The help display for the DICTSAVE procedure appears.
c. In the Dictionary to load field, type the dictionary ID. See Figure 25-1
on page 25-10 for the dictionary ID of the programming support that is
to be saved.
d. Press Enter.
3. Repeat step 2 on page 25-5 for each of the programming support functions
installed on your AS/400 Advanced 36 machine.
You have saved the Licensed Program Products interactively.

4. If you put the AS/400 Advanced 36 machine in a dedicated state, and you are
going to save the other SSP system files, leave the AS/400 Advanced 36
machine in dedicated state.
5. If you are not going to save the other SSP system files, remove the dedication
as follows.
START SYSTEM
b. Press Enter.
Creating a Procedure to Save Licensed Program Products

To create a procedure to save the licensed program products (features and
products):
1. Use DSU, FSEDIT or SEU to edit a new procedure library member. The name
of the procedure and the library you put the procedure in are your choice. You
might choose SAVELPP in #LIBRARY.
For more information on creating a procedure, see “Making Procedures” in the
S/36 System Reference book, SC21-9020.
2. Determine which programming support you have installed on your AS/400
have installed. If the procedure name for the programming support function is
not SAVE, SAVEFLDR, SAVELIBR or DICTSAVE, add that procedure name to
the 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 the
new 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 be
saved. 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 these
parameters.
If the procedure name is SAVEFLDR,
SAVEFLDR folder name,999,PPROD,TC,,,LEAVE
where folder name is the file name of the programming support that is to
be saved. See Figure 25-1 on page 25-10 for the folder name of the pro-
gramming support that is to be saved.
Note: On the SAVEFLDR procedure there are parameters that were not
specified (the null parameters ',,'). The default values are used for
these parameters.
If the procedure name is SAVELIBR,
SAVELIBR library name,999,PPROD,,,TC,LEAVE
where library name is the file name of the programming support that is to
be saved. See Figure 25-1 on page 25-10 for the library name of the pro-
Note: On the SAVELIBR procedure there are parameters that were not
these parameters.
If the procedure name is DICTSAVE,
DICTSAVE dictionary ID
where dictionary ID is the file name of the programming support that is to
be saved. See Figure 25-1 on page 25-10 for the dictionary ID of the pro-
you have installed on your AS/400 Advanced 36 machine.
5. After all the procedures used to save the program products are added to the
new procedure, end the edit session and replace the procedure member in the
library.
Saving the Licensed Program Products Using a Previously

Created Procedure
To save the licensed program products with a procedure you previously created:
1. If you have not created a procedure to save licensed program products, follow
the steps described in section “Creating a Procedure to Save Licensed
Program Products” on page 25-7.
2. Set the session library to the library that contains the procedure you created to
save the licensed program products.
SLIB library name
where library name is the name of the library that contains the procedure
you 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 to
it.
5. When the command entry display appears again, the procedure has ended and
you have completed the task of saving the licensed program products.

6. If you put the AS/400 Advanced 36 machine in a dedicated state and you are
going to save the other SSP system files, leave the AS/400 Advanced 36
machine in dedicated state.
7. If you are not going to save the other SSP system files, do as follows:
START SYSTEM
b. Press Enter.
Figure 25-1 (Page 1 of 2). Licensed Program Product Save Procedures

Programming Support to be Procedure Name File, Folder
Saved or Library Name
or Dictionary ID
Programmer and Operator POPSAVE
Productivity Aid
Value Added Software VASPSAVE
Package
Migration Analyzer ANLZSAVE
DFU DFUSAVE
WSU WSUSAVE
SEU SEUSAVE
SDA SDASAVE
RPG II RPGSAVE
COBOL COBSAVE
BASIC BASSAVE
FORTRAN FORTSAVE
Assembler ASMSAVE
DisplayWrite/36 TEXTSAVE
SAVEFLDR #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 Facility SAVEFLDR #OFCFLDR 1
DisplayWrite/36 SAVEFLDR #WPFLDR 2
SAVEFLDR WPDOCS
Personal Services/36 SAVEFLDR #OFCFLDR 1
SAVE $OUDRSMP
SAVELIBR #DQRYSMP
SAVEFLDR #DIRSMP
Document Library Services SAVEFLDR #DLSFLDR
Query/36 SAVEFLDR #QRYFLDR
IDDU SAVEFLDR #IDDFLDR
SAVEFLDR #IDDUSMP
SAVEFLDR #USERDCT
SAVE CUSTCDT
SAVE NAMEADDR
SAVE NAMEPHON
DSU SAVEFLDR #DSUFLDR
Shared Folders SAVEFLDR #WPFLDR 2

Figure 25-1 (Page 2 of 2). Licensed Program Product Save Procedures

or Dictionary ID
DisplayWrite/36
Language Dictionaries:
English DICTSAVE ENGLISH
French DICTSAVE FRENCH
French-Canadian DICTSAVE FRENCHCA
Spanish DICTSAVE SPANISH
Italian DICTSAVE ITALIAN
Danish DICTSAVE DANISH
German DICTSAVE GERMAN
Swedish DICTSAVE SWEDISH
Norwegian DICTSAVE NORWEGIAN
Dutch DICTSAVE DUTCH
Icelandic DICTSAVE ICELANDIC
Portuguese DICTSAVE PORTUGUESE
Development Support Utility DSUSAVE
Business Graphics Utility/36 BGUSAVE
PC Support/36, including: IWSAVE 3
Shared Folders
PC Support/36 Organizer
PC Support/36 Pass-Thru
PC Support/36 IBM Token- LRTRSAVE
Ring Network Support
PC Support/36 Work Station WSFSAVE
Feature
Multinational Character Set 4 MCSTSAVE
Conversion
Software Distribution Support SWDSAVE
LAN Communications Support LANSAVE
Character Generator Utility 4 CGUSAVE
IGC Sort 4 SRTXSAVE
Support for Printing/Reading DOCPSAVE
Online Information
3278 Device Emulation via SAVE #EPPCLD1
IBM Personal Computer
Table notes:
1 #OFCFLDR is used by both Personal Services/36 and Object Distribution Facility. If you
have both functions on your AS/400 Advanced 36 machine, it is only necessary to save the
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 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 the
base PC Support/36 procedure IWSAVE.
4 This programming support would only be supported on the Ideographic version of the SSP.
Saving Other SSP System Files

This 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 of
the SSP.
SSP Configuration Members
Although SSP configuration members are not really files, they are included in
this section because they should be saved when you backup your AS/400
Advanced 36 machine. Configuration members are used to change the SSP
master 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 tapes
that were used to save the licensed program products.
2. If you are going to save the password or resource security files, you must
determine the name of the tape file these SSP system files are to be saved
to (For example: USERIDFL and RESOURFL).
3. If you are going to save the extended character set files, you may want to
use a name other than #EXT1818 and #EXT2424. If you do, you should
determine these names before you start the save (For Example: EXT18FIL
and EXT24FIL).
4. Make sure the tape cartridge you initialized with a volume ID of PPROD is
in the tape drive.
SLIB ð
b. Press Enter.
icated state prior to saving the other SSP system files. This ensures the
files get saved correctly. You may have done this earlier when saving the
SSP operating system or the licensed program products. If you left the
AS/400 Advanced 36 machine in dedicated state, you can proceed. For
information on how to put the AS/400 Advanced 36 machine in dedicated
state, 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:

1. Interactively
You key each save procedure on the command line at the SSP system
console. Saving the other SSP system files this way is very time consuming
and the tape LEAVE option does not work properly. The advantage to saving
files this way is that no previous preparation is required.
2. Using a previously created procedure
This previously created procedure contains all procedures you would have
keyed 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 the
tape LEAVE option functions properly. The disadvantage to saving this way is
that some previous preparation is required.
Saving Other SSP System Files Interactively

To 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:
SECSAVE USERID
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 you
want to save the password security file.
d. In the Location of file field, type
TC
e. Press Enter.
f. In the Volume ID of tape 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
products, the volume ID is PPROD.
SECSAVE 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:
SECSAVE RESOURCE
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 you
want to save the resource security file.
TC
e. Press Enter.
f. In the Volume ID of tape field, type the volume ID of the tape used for the
SECSAVE 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 36
machine, complete the following steps to save the Network Resource Directory:
SAVENRD
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. If
this 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.
SAVENRD 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:
SAVEEXTN #EXT1818
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 to
save the #EXT1818 file. If you want the name to be #EXT1818, leave the
prompt blank.

SAVEEXTN procedure. The default values will work.
e. Press Enter.
The extended character set file #EXT1818 is saved to tape.
To save the #EXT2424 file,
SAVEEXTN #EXT2424
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 to
save the #EXT2424 file. If you want the name to be #EXT2424, leave the
prompt blank.
SAVEEXTN 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 Advanced
36 machine, complete the following steps:
SAVELIBR
The help display for the SAVELIBR procedure appears.
c. In the Name of library to be saved field, type the library name that contains
the 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.
TC
SAVELIBR procedure. The default values will work.
f. Press Enter.
The library containing your configuration members is saved to tape.
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 the
dedication:
START SYSTEM
b. Press Enter.
Creating a Procedure to Save Other SSP System Files

To create a procedure to save the other SSP system files such as password secu-
rity file and resource security file:
of the procedure and the library you put it in is your choice. It may be
SAVEOSF 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 remind
you 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 36
machine, 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 the
password security file and volume ID is the volume ID of the tape used for
the save. If this is the same tape that was used to save the licensed
program products, the volume ID is PPROD.
Note: On the SECSAVE procedure there are parameters that were not
these parameters.
b. If you have resource security activated on your AS/400 Advanced 36
SECSAVE RESOURCE,file name,TC,volume ID,999,,,LEAVE
resource security file and volume ID is the volume ID of the tape used for
the save. If this is the same tape that was used to save the licensed
program products, the volume ID is PPROD.
Note: On the SECSAVE procedure there are parameters that were not
these parameters.
c. If you have a Network Resource Directory (NRD) on your AS/400
Advanced 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 is
the same tape that was used to save the licensed program products, the
volume ID is PPROD.

Note: On the SAVENRD procedure there are parameters that were not
these parameters.
d. If you have the extended character set file #EXT1818 on your AS/400
SAVEEXTN #EXT1818,file name,volume ID,999,TC,,,,LEAVE
#EXT1818 file and volume ID is the volume ID of the tape used for the
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 not
these parameters.
e. If you have the extended character set file #EXT2424 on your AS/400
SAVEEXTN #EXT2424,file name,volume ID,999,TC,,,,LEAVE
#EXT2424 file and volume ID is the volume ID of the tape used for the
save. If you want the name to be #EXT2424, specify a null value (,,). If
Note: On the SAVEEXTN procedure there are parameters that were not
these parameters.
f. If you want to save the SSP configuration members on your AS/400
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 the
save.
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 to
save the licensed program products, the volume ID is PPROD.
Note: On the SAVELIBR procedure there are parameters that were not
these parameters.
g. After all the procedures used to save the other SSP system files are added
to the new procedure, end the edit session and replace the procedure
member in the library.
Saving the Other SSP System Files Using a Previously Created

Procedure
To save the other SSP system files using a procedure you created previously, do
as 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.
save the other SSP system files.
SLIB library name
you created to save the other SSP system files.
b. Press Enter.
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 to
it.
you 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 use
the START SYSTEM command to remove the dedication.
START SYSTEM
b. Press Enter.
Restoring the SSP Operating System

You may be directed by your software support personnel to restore the SSP oper-
ating system if the SSP operating system is experiencing problems. You can
restore 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 “Using
the Restore Library Procedure to Restore the SSP Operating System” on
page 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 the
Start AS/400 Advanced 36 Machine (STRM36) CL command to perform an IPL
(restore) of the SSP operating system from tape. Go to “Restoring the SSP
Operating System Using the Start AS/400 Advanced 36 Machine Command” on
page 25-21 to restore the SSP operating system.

Using the Restore Library Procedure to Restore the SSP

Operating System
Use the Restore Library (RESTLIBR) procedure to restore the SSP operating
system library if it is running but is experiencing problems, or when you want to go
back to the previous PTF level of SSP operating system.
Note: If Licensed program product libraries are to be restored, this must be done
after 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) in
the 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 SSP
GENERATION AND RELOAD - SIGN ON display.
à@ ð
SSP GENERATION AND RELOAD - SIGN ON
User ID . . . . . . . . . . . . . . . . . . . SYSSSP__
Password . . . . . . . . . . . . . . . . . . _________
4. Enter the information on the SSP GENERATION AND RELOAD - SIGN ON

display using the following instructions:
a. User ID: Type your user ID (SYSSSP is the default). If the Password
prompt is not displayed, the user ID could be your name or initials. If the
Password prompt is displayed, type the user ID assigned to you.
b. Password: Type your 4-character password. This password does not
appear 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 AND
RELOAD – SIGN ON display, press Enter.
An initial program load (IPL) begins from tape. The display clears and the SSP
GENERATION AND RELOAD – INPUT/OUTPUT display appears. If this
display does not appear, refer to the System Problem Determination–SSP
book, 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. If
you are asked to perform an action, perform the action that is requested and
press Enter.

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 machine
automatically starts an IPL from disk. When this happens, the display clears.
After a few minutes, the AS/400 Advanced 36 machine SIGN ON display
appears. If this display does not appear, refer to the System Problem
Determination–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/400

Advanced 36 Machine Command
If 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 to
restore the SSP operating system.

1. If the AS/400 Advanced 36 machine is still running, stop it.
For directions, see Chapter 16, “Stopping an AS/400 Advanced 36
Machine.”
2. Make sure the workstation designated as the SSP system console is turned
on.
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.
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 is
to be restored.
5. In the Library field, type the name of the OS/400 library that contains the
AS/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 you
specified.
After a few minutes, the display clears for the workstation designated as the
system console for the AS/400 Advanced 36 machine that you are restoring.
The next display should be the SSP GENERATION AND RELOAD - SIGN ON
display.
à@ ð
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, or
any 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 not
active, the Password field is not displayed.
c. Press Enter.
An initial program load (IPL) begins from tape. The display clears and the SSP
GENERATION AND RELOAD – INPUT/OUTPUT display appears. If this
display does not appear, refer to the System Problem Determination–SSP
book, SC21-8296.

à@ ð
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. If
you are asked to perform an action, perform the requested action and press
Enter.
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 machine
automatically starts an IPL from disk. When this happens, the display clears.
After a few minutes, the AS/400 Advanced 36 machine SIGN ON display
appears. If this display does not appear, refer to the System Problem
Determination–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 Products

Product libraries must be restored from tape using specific restore commands for
that product (for example, RPGLOAD for RPG and SEULOAD for SEU).
Other files, folders and libraries that are part of the program product must be
restored using the RESTORE, RESTFLDR and RESTLIBR procedures.

1. Insert the tape cartridge you used during the save of the licensed program
products in the tape drive. The tape has a volume ID of PPROD.
section. Use the SLIB procedure to set the session library as follows:
SLIB ð
b. Press Enter.

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 system
console. Restoring the licensed program products this way is very time con-
suming and the tape LEAVE option does not work properly. The advantage to
this way is that no previous preparation is required.
Using a previously created procedure.
This previously created procedure contains all of the procedures you would
have typed if you were to restore the licensed program products interactively.
Restoring the licensed program products this way is less time consuming and
the tape LEAVE option works properly. The disadvantage to this way of
restoring is that some previous preparation is required.
Restoring the Licensed Program Products Interactively

To restore the licensed program products interactively:
1. Determine which licensed program products you want to restore to your AS/400
want to restore. If the procedure name for the programming support function is
not RESTORE, RESTFLDR, RESTLIBR or DICTLOAD:
a. Type that procedure name on the command line at the SSP system
console.
b. Press Enter.
For example, if the programming support function was DFU, the procedure
name is DFULOAD. DFULOAD is not RESTORE, RESTFLDR, RESTLIBR
or DICTLOAD, so DFULOAD would be typed on the command line at the
SSP 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:
RESTORE
The help display for the RESTORE procedure appears.
c. In the Name of file to restore field, type the file name. See Figure 25-2
on page 25-30 for the file name of the programming support that is to
be restored.
d. Press Enter.
TC
f. Press Enter.
A third help display appears.

RESTORE procedure. The default values will work.
g. Press Enter.
If the procedure name is RESTFLDR:
RESTFLDR
The help display for the RESTFLDR procedure appears.
c. In the Name of folder containing folder to restore field, type the folder
name. See Figure 25-2 on page 25-30 for the folder name of the pro-
gramming support that is to be restored.
TC
e. Press Enter.
RESTFLDR procedure. The default values will work.
f. Press Enter.
If the procedure name is RESTLIBR:
RESTLIBR
The help display for the RESTLIBR procedure appears.
c. In the Name of library to be restored field, type the library name. See
Figure 25-2 on page 25-30 for the library name of the programming
support that is to be restored.
TC
e. Press Enter.
RESTLIBR procedure. The default values will work.
If the procedure name is DICTLOAD:
DICTLOAD
The help display for the DICTLOAD procedure appears.
c. In the Dictionary to load field, type the dictionary ID. See Figure 25-2
on page 25-30 for the dictionary ID of the programming support that is
to be restored.
d. Press Enter.


DICTLOAD procedure. The default values will work.
you 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 the
tape cartridge from the tape drive and return it to its protective container.
Creating a Procedure to Restore Licensed Program Products

Note: 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 were
saved to tape. This efficiency is achieved because the tape does not need
rewinding between restores. The procedure will work correctly even if the
order is the same.
To create a procedure to restore the licensed program products (features and pro-
ducts), do as follows:
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 use
the 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 the
copy.
b. Instead of adding the statements indicated in the other steps in this
topic, replace the save statements with the restore statements.
of the procedure and the library you put it in is your choice. You could choose
RESTLPP in #LIBRARY. For more information on creating a procedure, see
3. Determine which programming support you want to restore to your AS/400
4. Using the Figure 25-2 on page 25-30, find the programming support functions
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 was
DFU, the procedure name is DFULOAD. DFULOAD is not RESTORE,
RESTFLDR, RESTLIBR or DICTLOAD, so you would add DFULOAD to the
new 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.
If the procedure name is RESTORE:

RESTORE file name,,,,,,TC,,,,,,,,,,,LEAVE
where file name is the file name of the programming support that is to be
restored. 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 not
these parameters.
If the procedure name is RESTFLDR,
RESTFLDR folder name,,,TC,,,LEAVE
where folder name is the folder name of the programming support that is to
be restored. See Figure 25-2 on page 25-30 for the folder name of the
programming support that is to be restored.
Note: On the RESTFLDR procedure there are parameters that were not
these parameters.
If the procedure name is RESTLIBR,
RESTLIBR library name,,,,,,TC,LEAVE
where library name is the library name of the programming support that is
to be restored. See Figure 25-2 on page 25-30 for the library name of the
programming support that is to be restored.
Note: On the RESTLIBR procedure there are parameters that were not
these parameters.
If the procedure name is DICTLOAD,
DICTLOAD dictionary ID
where dictionary ID is the dictionary ID of the programming support that
is to be restored. See Figure 25-2 on page 25-30 for the dictionary ID of
the programming support that is to be restored.
Note: On the DICTLOAD procedure there are parameters that were not
these parameters.
8. After all the procedure names for the programming support you want to restore
are added to the new procedure, end the edit session and replace the member
in the library.

Restoring the Licensed Program Products from a Previously

Created Procedure
To restore the licensed program products using a procedure you created
previously:
“Creating a Procedure to Restore Licensed Program Products” on page 25-27
and then return here.
restore the licensed program products.
SLIB library name
you created to restore the licensed program products.
b. Press Enter.
dure you created to restore the licensed program products.
4. Press Enter.
you 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 tape
cartridge from the tape drive and return it to its protective container.
Figure 25-2 (Page 1 of 3). Licensed Program Product Restore Procedures

or Dictionary ID
Programmer and Operator POPLOAD
Productivity Aid
Value Added Software VASPLOAD
Package
Migration Analyzer ANLZLOAD
DFU DFULOAD
WSU WSULOAD
SEU SEULOAD
SDA SDALOAD
RPG II RPGLOAD
COBOL COBLOAD
BASIC BASLOAD
FORTRAN FORTLOAD
Assembler ASMLOAD
DisplayWrite/36 TEXTLOAD
RESTFLDR #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 Facility RESTFLDR #OFCFLDR 1
DisplayWrite/36 RESTFLDR #WPFLDR 2
RESTFLDR WPDOCS
Personal Services/36 RESTFLDR #OFCFLDR 1
RESTORE $OUDRSMP
RESTLIBR #DQRYSMP
RESTFLDR #DIRSMP
Document Library Services RESTFLDR #DLSFLDR
Query/36 RESTFLDR #QRYFLDR
IDDU RESTFLDR #IDDFLDR
RESTFLDR #IDDUSMP
RESTFLDR #USERDCT
RESTORE CUSTCDT
RESTORE NAMEADDR
RESTORE NAMEPHON
DSU RESTFLDR #DSUFLDR
Shared Folders RESTFLDR #WPFLDR 2


or Dictionary ID
DisplayWrite/36
Language Dictionaries:
English DICTLOAD ENGLISH
French DICTLOAD FRENCH
French-Canadian DICTLOAD FRENCHCA
Spanish DICTLOAD SPANISH
Italian DICTLOAD ITALIAN
Danish DICTLOAD DANISH
German DICTLOAD GERMAN
Swedish DICTLOAD SWEDISH
Norwegian DICTLOAD NORWEGIAN
Dutch DICTLOAD DUTCH
Icelandic DICTLOAD ICELANDIC
Portuguese DICTLOAD PORTUGUESE
Development Support Utility DSULOAD
Business Graphics Utility/36 BGULOAD
PC Support/36, including: IWLOAD 3 and 4
Shared Folders
PC Support/36 Organizer
PC Support/36 Pass-Thru
PC Support/36 IBM Token- LRTRLOAD
Ring Network Support
PC Support/36 Work Station WSFLOAD
Feature
Multinational Character Set 5 MCSTLOAD
Conversion
Software Distribution Support SWDLOAD
LAN Communications Support LANLOAD
Character Generator Utility 5 CGULOAD
IGC Sort 5 SRTXLOAD
Support for Printing/Reading DOCPLOAD
Online Information

or Dictionary ID
3278 Device Emulation via RESTORE #EPPCLD1 4
IBM Personal Computer
Table notes:
1 #OFCFLDR is used by both Personal Services/36 and Object Distribution Facility. If you
have both functions on your AS/400 Advanced 36 machine, it is only necessary to restore
the 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 the
base PC Support/36 procedure IWLOAD.
4 The virtual disk #EPPCLD1 is not a part of PC Support/36. The virtual disk #EPPCLD1
must be restored prior to restoring PC Support/36. The virtual disk is then activated when
the IWLOAD procedure is run.
5 This programming support would only be supported on the Ideographic version of the SSP.
Restoring the Other SSP System Files

This 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 system
files in the tape drive.
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 system
console. Restoring the other SSP system files this way is very time consuming
and the tape LEAVE option does not work properly. The advantage to
restoring this way is that no previous preparation is required.
2. Using a previously created procedure.

This previously created procedure contains all the procedures you would have
keyed 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 the
tape LEAVE option works properly. The disadvantage to restoring this way is
that some previous preparation is required.
Restoring the Other SSP System Files Interactively

To 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 36
machine:
SECREST USERID
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 you
saved the password security file.
TC
e. Press Enter.
SECREST 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 36
machine:
SECREST RESOURCE
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 you
saved the resource security file.
TC
e. Press Enter.
SECREST 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/400
Advanced 36 machine:

RESTNRD
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.
RESTNRD 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 the
extended character set file #EXT1818:
RESTEXTN
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 where
you saved the #EXT1818 file.
d. In the Name of the extended character file prompt, type
#EXT1818
RESTEXTN 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 the
extended character set file #EXT2424:
RESTEXTN
The help display for the RESTEXTN procedure appears.
c. In the Name of file to be restored prompt, type the name of the tape file
where you saved the #EXT2424 file.
d. In the Name of the extended character file field, type
#EXT2424
RESTEXTN procedure. The default values will work.

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/400
RESTLIBR
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.
TC
RESTLIBR 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 System

Files
Note: 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 were
saved to tape. This efficiency is achieved because the tape does not need
rewinding between restores. The procedure will work correctly even if the
order 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:
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 use
the 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 the
copy.
b. Instead of adding the statements indicated in the other steps in this
topic, replace the save statements with the restore statements.
of the procedure and the library you put it in is your choice. You might choose
RESTOSF in #LIBRARY. For more information on creating a procedure, see

“Creating a Procedure to Restore Licensed Program Products” on page 25-27
4. If you want to restore the password security file to your AS/400 Advanced 36
SECREST USERID,file name,,,TC,,,,LEAVE
where file name is the name of the tape file where the password security file
was saved.
Note: On the SECREST procedure there are parameters that were not speci-
parameters.
5. If you want to restore the resource security file to your AS/400 Advanced 36
SECREST RESOURCE,file name,,,TC,,,,LEAVE
where file name is the name of the tape file where the resource security file
was saved.
Note: On the SECREST procedure there are parameters that were not speci-
parameters.
6. If you want to restore the Network Resource Directory to your AS/400
RESTNRD #NRD.FLE,TC,,,LEAVE
Note: On the RESTNRD procedure there are parameters that were not speci-
parameters.
7. If you want to restore the extended character set file #EXT1818 to your AS/400
RESTEXTN file name,,#EXT1818,TC,,,,,LEAVE
where file name is the name of the tape file where the #EXT1818 extended
character 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 these
parameters.
8. If you want to restore the extended character set file #EXT2424 to your AS/400
RESTEXTN file name,,#EXT2424,TC,,,,,LEAVE
where file name is the name of the tape file where the #EXT2424 extended
character 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 these
parameters.
9. If you want to restore the SSP configuration members to your AS/400

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.
Note: On the RESTLIBR procedure there are parameters that were not speci-
parameters.
10. After all the procedures used to restore the other SSP system files are added
to the new procedure, end the edit session and replace the procedure member
in the library.
Restoring the Other SSP System Files from a Previously Created

Procedure
To restore the other SSP system files using a procedure you created previously:
“Creating a Procedure to Restore the Other Saved SSP System Files” on
page 25-35 and then return here.
restore the other SSP system files.
SLIB library name
you created to restore the other SSP system files.
b. Press Enter.
dure you created to restore the other SSP system files.
4. Press Enter.
you 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 protective
container.

SSP PTFs
Chapter 26. Working with SSP Program Temporary Fixes

An SSP program temporary fix (PTF) is a solution to a problem or a potential
problem 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 provide
new functions.
SSP PTFs are designed to replace the failing load module(s) or procedure(s) in a
product library. Generally, the failing load modules or procedures are incorporated
into a future release of the system.
The program maintenance strategy discussed in this chapter applies to the IBM
AS/400 system service and delivery, specifically the AS/400 Advanced 36 system.
AS/400 Advanced 36 Program Maintenance Strategy

The AS/400 program maintenance strategy consists of preventative service and
corrective service.
Preventative Service
Preventative service helps you avoid problems that have been found and fixed
since the start of the current release. Cumulative PTF Packages are used to
perform 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

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 Service
Corrective service corrects problems reported to IBM service support. If you have
a problem with the SSP, SSP features or LPPs, you use the System Problem
Determination–SSP book, SC21-8296, to help isolate the problem. This book might
direct you to contact your service representative for assistance. If there is a
problem with the IBM supplied software, a PTF is made available to fix the
problem.
Corrective Service SSP PTFs

There are three types of PTFs for corrective service:
Test PTFs
Development cannot adequately test the PTF, so the customer is asked to help
test the PTF.
Traps PTFs
Development cannot recreate the reported problem. They need additional
information to solve the problem. A trap is developed to get that additional
information 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.

SSP PTFs
On a corrective cumulative PTF package on a tape cartridge sent to you by

your service representative.
Electronically using Electronic Customer Support.
An electronically sent SSP PTF is sent to the OS/400 operating system using
Electronic Customer Support. For more information on Electronic Customer
Support see Appendix D, “Using Electronic Customer Support.”
Ordering SSP PTFs and PTF Information

Preventative cumulative PTF packages or Corrective PTFs can be ordered by:
Contacting your service provider and asking for the latest AS/400 Advanced 36
Cumulative PTF package.
Using the OS/400 Send PTF Order (SNDPTFORD) command and Electronic
Customer Support. For information on using SNDPTFORD and Electronic Cus-
tomer Support, see Appendix D, “Using Electronic Customer Support.”
Displaying or Printing Cumulative PTF Information

You can choose to either display or print information about IBM-supplied PTFs. To
do 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 reads
only 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 must
remap the device TC to be the CD-ROM drive. For directions, see “Mapping
the 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 the
appropriate drive.
Note: For information on using different kinds of media from your AS/400
Advanced 36 machine, see Chapter 7 of the Operating Your
Computer–SSP Operating System book, SC21-8297. For information
on using different kinds of media from OS/400, see Chapter 4 of the
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.
Chapter 26. Working with SSP Program Temporary Fixes 26-3

SSP PTFs
à@ ð
PTF PROCEDURE
Applies PTFs (program temporary fixes) and patches to
IBM-supplied and user programs that are found to be
in 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 PTFNEWS
library.
8. Press Enter.
à@ ð
PTF PROCEDURE
Applies PTFs (program temporary fixes) and patches to
IBM-supplied and user programs that are found to be
in 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 or
printed:

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 package
are 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 must
change it back to the tape cartridge tape drive.
To change it back, follow the directions in “Changing the TC Device ID Back to
a Tape Cartridge Drive” on page 26-17 and then return here.
Installing Cumulative SSP PTF Packages

The 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 PTF
Shipping Information Letter that comes with the Cumulative PTF package.
Note: It is important to remember, the SSP PTF procedure only installs PTFs from
a device that has a device ID of TC.
If you received a cumulative PTF package on CD-ROM, you must map the device
that has an ID of TC to be the CD-ROM drive. Before you copy the PTFs, follow
the 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 Tape

Before you begin...
Prior to installing your corrective SSP PTF, review the PTF Shipping Information
Letter that came with the corrective PTF. There might be special instructions
you must do when installing the PTF.

SSP PTFs
You use the AUTOPTCH procedure to install corrective SSP PTFs (patches) from
CD-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 the
CD-ROM drive. To do this, follow the steps in “Mapping the TC Device ID to
the 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/400
Advanced 36 machine, see Chapter 7 of the Operating Your
Computer–SSP Operating System book, SC21-8297. For information
on using different kinds of media from OS/400, see Chapter 4 of the
4. From the console for the AS/400 Advanced 36 machine, put the AS/400
Advanced 36 machine in a dedicated state. To do this, follow the directions in
After this is done, return here.
If you completed this step, the AS/400 Advanced 36 machine is in a dedicated
state.
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 is
always 8 characters long. The first 2 characters are TF, PT or
DT. 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 the
APAR 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, you
should change it back at this time. To do so, follow the directions in “Changing
the 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.

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:
DSPNETA
2. Press Enter.
3. Find the line titled Local control point name. This is the name of the AS/400
system 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 to
define an entry in the Network Resource Directory. To define that entry, do as
follows:
| 1. On a command line on the AS/400 Advanced 36 machine console, type
EDITNRD
2. Press Enter.

SSP PTFs
If the NRD already exists, the NETWORK RESOURCE DIRECTORY edit

display 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 DIRECTORY
create 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 to
access.
Note: If you are only going to use the DDM for electronically sent PTFs, 40
entries 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 point
name 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.

SSP PTFs
9. Press Cmd7 to end the edit session.

Other messages, such as COPYDATA is running, may roll up from the bottom of
the display. These are normal and should be ignored.
Electronic Installation Checklist

During 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 was
ILANSBS. This was also the recommended name for any additional AS/400
Advanced 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/400
Advanced 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 or
DT. 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 the
problem 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 Electronically

The SSP PTF is sent to your OS/400 operating system as a save file (SAVF). A
cover 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 Problem
Handling book, SC41-4206.
1. Make sure you have everything in the “Electronic Installation Checklist” on

page 26-9 and that you have read the cover letter for special instructions.

SSP PTFs

state. You need to start ILAN communications again on the dedicated AS/400
3. Start ILAN communications as follows:
a. On a command line on the AS/400 Advanced 36 machine console, type
ENABLE
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 the
ILAN Subsystem Configuration Member. If you do not know the name, see
the 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 “ILAN
Communications Verification” on page 29-10. If the ILAN subsystem is not
enabled, see the directions in the System Problem Determination–SSP book,
SC21-8296.
ECSAPTCH savfname,patchid
Where:
savfname Is the save file name that contains the corrective PTF (patch) that
you 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 the
display.
After a few seconds the following will rollup from the bottom of the display.
When the NETWORK RESOURCE DIRECTORY display comes up
find the LOCAL LABEL - LOCPTFFL. Modify the REMOTE
LABEL on this entry to be:
U57mnnn
When 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, it
refers to the Pause message SYS-3725.
7. Write down the number that is in the form U57mnnn.

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 be
used to page forward and backward through the entries.
11. In the REMOTE LABEL field for that entry, type the name that was shown
earlier 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 the
steps, the system is dedicated except for ILAN communications that were
needed 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 job

1. Request Command display
2. Cancel job and close files; new data is saved
3. Cancel job; new files are lost
4. Set inquiry condition for program
5. Display session status
6. Display messages sent to this display station
7.
Enter number to select option
á ñ
15. Type
1
16. Press Enter.
DISABLE
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” on
page 26-9.

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 a
dedicated state.
22. Press Cmd1 (Resume job) to resume the interrupted job. The following
message 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 which
you want to backup the corrective PTF. The volume ID
must 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 or
you can use the tape to install this PTF on another AS/400 Advanced 36
machine.
Note: The message identified in the above text might be SYS-3726. If so, it
refers to the Pause message SYS-3725.
27. If you do not have a tape cartridge with a volume ID of AUTOPT, do as
follows:
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 INQUIRY
command display appears again.
f. Press Cmd1 (Resume job) to resume the interrupted job.

SSP PTFs
28. Type
ð
29. Press Enter.
The library that contains the corrective PTF is saved to tape. When the
command entry display appears, the electronically sent PTF has been installed
and saved to tape. The save file that was sent to OS/400 and the LIBRFILE
that 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 next
time 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 Electronically

If you want to apply this PTF on another AS/400 Advanced 36 machine, you will
need to use the tape you saved this PTF to. You do this by following the directions
in this topic.
When you installed the electronically sent PTF, the library that contains the PTF
was 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, PT
or DT. The third character is the version of the patch (A, B, or C). The last 5
characters 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:

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

SSP PTFs
AUTOPTCH APPLY,patchid,F1
5. Press Enter.
6. When the command display is shown, type
DELETE patchid,F1,,,LIBR
7. Press Enter.
When the command display is shown, the installation of the corrective PTF is
complete. This completes the process of installing a saved electronically sent
PTF.
8. To remove system dedication, on a command line on the AS/400 Advanced 36
machine, type
START SYSTEM
9. Press Enter.
Displaying or Printing Corrective SSP PTF Information

After the corrective PTF is installed, you should review the information sent with the
PTF. During the install process, a PTF backup library was created. In this library
is a source member called README. This member contains any special informa-
tion about the corrective PTF. The name of the backup library is #Bmnnnnn, where
m is the version of the corrective PTF (for example, A, B or C) and nnnnn is the
last 5 digits of the APAR that reported the problem this corrective PTF is going to
fix.
| 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 backup
library name.
To display or print the corrective PTF information, you must display or print the
source 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 discussed
earlier in this topic.
2. Press Enter.
This LISTLIBR procedure lists the contents of the source member README in
library #Bmnnnnn on the current system list device. If the system list device is
CRT, 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 then
be printed or you can browse it using the WRKSPL procedure.
Using the LIBR function of the Programmer and Operator Productivity Aid
(POP):

SSP PTFs
LIBR #Bmnnnnn
where #Bmnnnnn is the name of the PTF back up library that was discussed
earlier in this topic.
2. Press Enter.
This LIBR procedure shows you the members in the library #Bmnnnnn. You can
use the B (Browse) or P (Print) options to display or print the README
member.
Removing Corrective SSP PTFs

You use the AUTOPTCH procedure to remove corrective PTFs (patches) from the
Note: You can only remove corrective PTFs if the PTF backup library is still be on
the system. If the PTF backup library is not on the system, it must be
restored before you try to remove a corrective PTF.
To remove a corrective PTF:
state.
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 is
always 8 characters long. The first 2 characters will be TF, PT or
DT. The second 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 the problem this corrective PTF is going
to 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 the
system 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.

SSP PTFs
Mapping the TC Device ID to the CD-ROM Drive

To 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 the
system list output is to be shown at your display station.
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 is
currently 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 device
name.
CHGSYSVL DEVMAP,TC
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 is
IPLed or device TC is remapped again, any reference to device ID TC actually
refers 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 the
CD-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.”

SSP PTFs
What to Do if the Mapping Failed

You are here because you received an error when you tried to map the device ID
TC to the CD-ROM drive. The following steps will help you determine the OS/400
device 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 the
OS/400 device name of the CD-ROM drive. This is the name you must use
when 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,” starting
with step 7. When you get to step 9, make sure you type the OS/400 device
name you determined.
Changing the TC Device ID Back to a Tape Cartridge Drive

After the operations that require you to use the CD-ROM drive are complete, the
TC device ID should be mapped back to the 1/4-inch tape drive. To change the
mapping of TC back to the tape cartridge drive:
CHGSYSVL DEVMAP,TC
3. In the OS/400 device name field, type the OS/400 device name you determined
in 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.

SSP PTFs

Remote Workstation Communications

Workstations
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, at
a display station or the system console, to establish the communications link
depends 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 establish
a communications link with the communications support that is on your system.
Forms establishing communications links for other communications support appear
in the appropriate communications reference books, with examples of how to fill in
the 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 in
by your programmer or system manager.
The steps you can take to determine the cause of a problem for communications
lines are described in the System Problem Determination–SSP book, SC21-8296.
Using Remote Work Station Support
Establishing the Communications Link

1. 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 be
varied 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 station
address.
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, and
you 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, and
you must answer a call from a remote location. Perform the following
steps:

Remote Workstation Communications
c. Other message
See the S/36 System Messages book, SC21-7938, for an explanation of
the message and the steps that you should follow.
Ending the Communications Link

If you have system operator authority or higher, enter the VARY OFF command at
a display station for each line, cluster controller, or for each device that is to be
varied 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 off
or if the spool writers for remote printers are not stopped.

AS/400 System Common Operator Tasks
Chapter 28. Problem Handling . . . . . . . . . . . . . . . . . . . . . . . . . 28-1
Hardware Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1
Hardware Problem Message Sent to SSP . . . . . . . . . . . . . . . . . . . 28-1
Hardware Problem Message Sent to OS/400 . . . . . . . . . . . . . . . . . 28-1
Using the Product Activity Log to Find out about Hardware Problems . . . 28-1
Determining 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-8
Using the Work with Configuration Status Command to Determine If
Devices are Varied Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-8
Handling AS/400 Advanced 36 Machine Error Codes . . . . . . . . . . . . . . 28-9
Determining What the Error Codes Mean . . . . . . . . . . . . . . . . . . . 28-9

Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1
Setting up ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . 29-3
Understanding Default Startup Settings . . . . . . . . . . . . . . . . . . . . . . 29-3
Manually Starting the ILAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3
Manually Starting the OS/400 Side of ILAN . . . . . . . . . . . . . . . . . . 29-3
Manually Starting the SSP Side of ILAN (All Connections) . . . . . . . . . 29-4
Manually Starting the SSP Side of ILAN (A Single Connection) . . . . . . 29-5
Automatically Starting ILAN Communications . . . . . . . . . . . . . . . . . . . 29-6
Automatically Starting ILAN Communications for SSP . . . . . . . . . . . . 29-6
Automatically Starting ILAN Communications for OS/400 . . . . . . . . . . 29-6
Disabling Automatic Startup of ILAN . . . . . . . . . . . . . . . . . . . . . . . . 29-7
Finding Out the OS/400 Control Point Name . . . . . . . . . . . . . . . . . . . 29-8
Stopping ILAN Communications . . . . . . . . . . . . . . . . . . . . . . . . . . 29-8
Stopping ILAN Communications on the OS/400 Side . . . . . . . . . . . . 29-8
Stopping ILAN Communications on the SSP Side (All Connections) . . . . 29-9
Stopping ILAN on the SSP Side (Single Connection) . . . . . . . . . . . . 29-9
ILAN Communications Verification . . . . . . . . . . . . . . . . . . . . . . . . 29-10
Verification for the First AS/400 Advanced 36 Machine . . . . . . . . . . 29-10
Verification for the Second AS/400 Advanced 36 Machine . . . . . . . . 29-10
Verification for the Third AS/400 Advanced 36 Machine . . . . . . . . . . 29-11
OS/400 Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-12
SSP 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-15
Running Display Station Pass-Through from OS/400 to SSP . . . . . . . 29-15
Changing the QAUTOVRT Value . . . . . . . . . . . . . . . . . . . . . . . 29-15
Running Pass-Through from SSP to OS/400 . . . . . . . . . . . . . . . . 29-16
Running Pass-Through from SSP to SSP . . . . . . . . . . . . . . . . . . 29-16

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36
Configurations and Machines . . . . . . . . . . . . . . . . . . . . . . . . . . 30-1
Using the Work with AS/400 Advanced 36 Machine Command . . . . . . . . 30-1
Creating An AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . 30-2
Changing Attributes for AS/400 Advanced 36 Machines . . . . . . . . . . . 30-3
Deleting an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . 30-4
Displaying Information about an AS/400 Advanced 36 Machine and Its
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-4
Printing Information about an AS/400 Advanced 36 Machine and Its
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-5
Renaming an AS/400 Advanced 36 machine . . . . . . . . . . . . . . . . . 30-5
Changing the Description for an AS/400 Advanced 36 Machine . . . . . . 30-6
Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . . 30-6
Ending an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . . . . . . 30-7
Transferring to an AS/400 Advanced 36 Machine . . . . . . . . . . . . . . 30-7
Using the Work with AS/400 Advanced 36 Machine Configuration Command 30-8
Creating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 30-9
Changing Attributes and Configuration Details for an AS/400 Advanced
36 Machine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 30-10
Deleting an AS/400 Advanced 36 Machine Configuration . . . . . . . . . 30-11
Displaying an AS/400 Advanced 36 Machine Configuration . . . . . . . . 30-11
Printing an AS/400 Advanced 36 Machine Configuration . . . . . . . . . 30-12
Renaming an AS/400 Advanced 36 Machine Configuration . . . . . . . . 30-12
Changing the Description for an AS/400 Advanced 36 Machine
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13
Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13

Configuration That Exists Immediately after Installation . . . . . . . . . . . . . 31-2
OS/400 Added to a System That Previously Was SSP Only . . . . . . . . 31-2
OS/400 and SSP Preloaded from IBM Manufacturing . . . . . . . . . . . . 31-3
Defining a Communications Line or a LAN . . . . . . . . . . . . . . . . . . . . 31-4
Defining a Diskette Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-8
Defining a Tape or CD-ROM Device . . . . . . . . . . . . . . . . . . . . . . . 31-10
Defining Printers and Display Stations Using Device Mapping . . . . . . . . 31-12
Defining Printers and Display Stations Using Controller Mapping . . . . . . 31-17
Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-22
Defining Whether SSP or OS/400 Controls SSP Printer Output . . . . . . . 31-26
Giving SSP Control of AS/400 Advanced 36 Machine Printer Output . . 31-26
Giving OS/400 Control of AS/400 Advanced 36 Machine Printer Output 31-30
Giving OS/400 Control of Printer Output When There Is No Physical
Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-32
Defining Whether SSP or OS/400 Controls the Display Station . . . . . . . 31-36
Validating an AS/400 Advanced 36 Machine Configuration . . . . . . . . . . 31-39
Chapter 32. Displaying Information About an AS/400 Advanced 36

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

Hardware Problem Isolation
Chapter 28. Problem Handling

When the system detects a hardware problem and you are running an AS/400
Advanced 36 machine, the system reports the hardware problem to either the SSP
operating system or the OS/400 operating system.
Hardware Problem Message Sent to SSP

If the system determines that the hardware problem is with a single specific device
that the SSP operating system is using, the system notifies the SSP operating
system 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 error
messages.
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 SSP
Messages.”
Hardware Problem Message Sent to OS/400

If the system cannot determine that the hardware problems is with a single specific
device, 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 can
use the Display Message (DSPMSG) CL command to display the QSYSOPR
message queue.
Note: For many of the hardware error messages, you can press Cmd14 to start
the Work with problem support to try and determine the cause of the error.
For more information on how to respond to OS/400 messages, see
Chapter 5, “Handling OS/400 Messages.”
Using the Product Activity Log to Find out about Hardware Problems
For many hardware problems, an entry is placed in the Product Activity Log. This
log is a list of errors that occurred on the various hardware devices. Examples of
hardware devices include: disks, tapes, diskettes, displays, printers, and commu-
nication lines.
You can use the Start System Service Tools (STRSST) CL command to access the
Product Activity Log. For more information about the Product Activity Log, see the
AS/400 Service Functions book, SY44-4902.
Determining Who Owns the Device

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

| 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 use
the Deallocate Object (DLCOBJ) CL command to release the device. If the
OS/400 user is using a CL command to access the device, the user can end
the job to release the device. Devices are also given up when the OS/400 user
signs 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.

| 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

| 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:

| 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

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

| 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.
| 18. Type
| 1
| to select Work with display stations and printers.
| 19. Press Enter.
| 20. Type
| 6
| to select Change display stations or printer workstation IDs.
| 21. Press Enter.
| 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.

| 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 Conflicts

There are a number of alternatives. If OS/400 and SSP printer conflicts frequently
arise, 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 writer
print SSP output along with OS/400 output. For directions, see “Giving SSP
Control of AS/400 Advanced 36 Machine Printer Output” on page 31-26.
Dedicate printers to SSP or OS/400. For directions, see “Defining Whether
SSP or OS/400 Controls the Display Station” on page 31-36.
Get an additional printer.
Using the Work with Configuration Status Command to Determine If

Devices are Varied Off
The Work with Configuration Status (WRKCFGSTS) command should only be used
after the WRKOBJLCK command.
When you use the WRKOBJLCK command, a display appears on which the owner
of the lock is identified. The user ID which owns the lock on the device has a
status of held in the Status field. Any other user IDs which have requested use of
the device have REQ in the Status field.
Note: A lock on a printer or a display station is an exclusive read (*EXCLRD) lock
held by a single job on the system.

What the Error Codes Mean
When a lock is given up by a display station, the lock request is satisfied and the
QBASE 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 a
printer 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 the
WRKCFGSTS 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 Mean

Errors that are generated because there are problems related to using OS/400 and
SSP on the same system, are included in this chapter.
If you were not referred to this book for recovery, move your cursor to the message
and press Cmd1 for more information.
If you were referred to this book for recovery, find the error code in the following
list. Then, read the Message and Recovery column. The following error codes can
be shown for CPFACE0 exceptions:
Error Code Message and Recovery
00010001 AS/400 Advanced 36 machine not started. The machine state
is 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.
00010003 The AS/400 Advanced 36 machine is still active because the
machine was not able to shutdown completely.
To recover, end each AS/400 Advanced 36 machine on the
system. Then, do another IPL of the AS/400 system.
00010004 The function code is not valid because an internal processing
error occurred.
00010005 The AS/400 Advanced 36 machine machine pointer is not valid
because an internal processing error occurred.
00010006 Migration is pending and the state of the AS/400 Advanced 36
machine is not valid.
01010002 Insufficient storage space exists to create the minimum size
To recover, free up disk storage or add another disk. The

minimum storage space required to create an AS/400

Advanced 36 machine is 80 megabytes.
01010003 User storage limit exceeded. The machine cannot be created
because it causes the user's storage limit to be exceeded.
Free up user storage or increase the storage limit specified in
the user profile for the user ID of the person creating the
03010001 Configuration template bytes provided less than 16 megabytes.
03010002 Configuration template device category mask is non-zero.
03010003 Configuration template reserve bytes are non-zero.
03010004 Invalid device category.
03010005 Resource not compatible with device category. A hardware
resource was renamed after the machine configuration was
applied.
To recover, start the machine again and apply the same config-
uration.
03010006 Resource name not valid. A hardware resource was renamed
after the machine configuration was applied.
To recover, start the AS/400 Advanced 36 machine again and
apply the same configuration.
03010007 Device code is not valid.
03010008 IPL device category is not valid.
03010009 IPL device code is not valid.
0301000A IPL resource name is not valid. A hardware resource was
renamed after the machine configuration was applied.
0301000B The resource is not an IPL-able device. A hardware resource
was renamed after the AS/400 Advanced 36 machine config-
uration was applied.
0301000C No configuration exists in the AS/400 Advanced 36 machine.
Apply a valid AS/400 Advanced 36 machine configuration using
the APYM36CFG parameter on the STRM36 command.

0301000D The AS/400 Advanced 36 machine configuration is no longer

valid. It is out of date.
0301000E The configuration template has a duplicate device code.
0301000F The configuration template has a duplicate resource name.
03010010 An IPL from media is required. There is no SSP/reload in
progress.
To recover, load the SSP from tape, CD-ROM, or diskette.
03010011 There is at least one workstation controller missing.
03010012 The AS/400 Advanced 36 machine configuration that is applied
is not capable of using a resource.
Restart the machine and apply the same configuration.
03010013 The AS/400 Advanced 36 machine cannot use the IPL
resource because a hardware resource was renamed after the
machine 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 Advanced
36 machine.
To recover, free up some disk storage or add another disk.
05010001 The STRM36PRC CL command was entered but the OS/400
user ID is not correct for the AS/400 Advanced 36 machine.
To recover, have the security officer add the OS/400 user ID to
the user ID file on the AS/400 Advanced 36 machine.
05010002 The STRM36PRC CL command was entered, but the default
menu is not correct for the specified user ID.
To recover, have the security officer for the AS/400 Advanced
36 machine correct the default user menu or help menu for the
user ID. More information about the cause of the error can be
found in the S/36 history file.
05010003 The STRM36PRC CL command was entered but the procedure
is not correct. The procedure might not exist. It is also possible
that you may not be authorized to use the procedure or your
user ID may be restricted to run only a specific procedure.
To recover, make sure the procedure you are trying to run
exists on the AS/400 Advanced 36 machine. Get authorization
to run the procedure. More information about the cause of the
error is in the S/36 history file.

05010004 The STRM36PRC CL command was entered but the library is

not correct. The library might not exist. You may not be
authorized to the library or your user ID may be restricted to
use only a specific library.
Ensure that the library you are trying to use exists on the
AS/400 Advanced 36 machine. Have the security officer
authorize you to this library. More information about the cause
of the error can be found in the S/36 history file.
05010005 The procedure was terminated abnormally. The STRM36PRC
CL 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 terminate
the procedure was selected.
More information about the cause of the error can be found in
the 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 in
the S/36 history file. Contact your service representative for
help.
05010011 The STRM36PRC or TFRM36 CL command was entered but
there were no SSP workstations available for the transfer.
To recover, do the following. Display the job log for your
OS/400 job. If message CPIAC82 is in the job log, your
OS/400 display is probably not defined to this AS/400
Advanced 36 machine. The CL command tried to find an
unused SSP display station. However, all the display stations
defined 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 be
reserved for this OS/400 display.
If there is no CPIAC82 message in the job log, your display is
configured in the AS/400 Advanced 36 machine for a specific
controller, port and workstation address. The specific address
is already in use so the CL command failed.
There may be a display station error message that the system
operator must respond to before this workstation address can
be used again.
Another reason for this error is another display station has
already signed on to this specific address.
05010012 The STRM36PRC or TFRM36 CL command was entered and a
workstation ID was specified. However, the workstation ID is
not defined to the AS/400 Advanced 36 machine at this time.

To recover, issue the CL command again specifying a valid

workstation ID.
If the system is be reloaded, no workstation IDs are defined by
the AS/400 Advanced 36 machine. If a display is defined in the
AS/400 Advanced 36 machine at controller 1 port 0 address 0,
only that display station is allowed to transfer into the AS/400
Advanced 36 machine
To recover, issue the CL command specifying *DFT for the
workstation ID.
05010013 The STRM36PRC or TFRM36 CL command was entered, and
a workstation ID was specified, but the workstation ID is
already in use or a display station error message is waiting for
a response from the system operator.
To recover, check to see if there is display station error
message that the system operator must respond to before this
workstation ID can be used again. Try the command again
after the system operator responds to the message. If that
doesn't work, try the command again with a different work-
station ID.
the address that was specified for the AS/400 Advanced 36
machine was not configured for the AS/400 Advanced 36
machine.
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 configuration
that includes the display station.
the address that was specified to the SSP was already in use
or a display station error message must be responded to by the
system operator.
To recover, have the system operator respond to any waiting
error messages or try the command again with a different
display station ID.
the S/36 display station was varied off.
To recover, vary on the display station from the AS/400
Advanced 36 machine console using the VARY command.
07010001 The configuration template provided less than sixteen bytes.
07010002 The Configuration template device category mask is not valid.
07010003 The configuration template reserved bytes that are nonzero

07010004 The AS/400 Advanced 36 machine has no configuration

because the AS/400 Advanced 36 machine has never been
started.
To recover, start the AS/400 Advanced 36 machine and apply a
configuration. 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 Advanced
36 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.
09010001 Unconverted AS/400 Advanced 36 machine does not exist
because an internal processing error occurred.
0B010000 There is a communication object processing error.
00FFnnnn Unexpected exception (nnnn)
00FE0001 Configuration is missing
00FE0002 Configuration has a resource name that is not valid.
00FE0003 Configuration has invalid device class
00FE0004 The configuration has a duplicate device code.
00FE0005 The configuration has a duplicate resource name.
00FE0006 The configuration has resource that the S/36 is not capable of
using.
00FE0007 The configuration has a new device code.

ILAN Communications

Communications
When multiple, different, operating systems exist on a single physical system, it is
often desirable for applications running on these operating systems to have a way
to communicate with each other. ILAN offers a way of doing this without physical
communication links. ILAN Communications are accomplished by defining a
network within the system. This network is linked by what is called an Internal
Local 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:
AS/400 AS/400
Other Token
Connections Ring
AS/400 AS/400 System/36

Advanced 36 Advanced 36
RV3D360-2

ILAN Communications
On an ILAN, you would find the following type of configuration:
Other Token
Connections Ring
OS/400
AS/400 AS/400 AS/400

Advanced 36 Advanced 36 Advanced 36
Machine Machine Machine
RV3D361-0
| 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 examples
are:
DDM
SNADS
| ODF
Display Station Pass-through
Customer-written APPC applications
Every physical LAN (such as Token-Ring or Ethernet) has the following three
unique 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.

ILAN Communications
To an external network, these coexisting operating systems or machines appear to

be independent systems. External networks are unaware that each of these oper-
ating systems actually reside on the same piece of equipment.
Setting up ILAN Communications

Instructions on how to set up ILAN communications for your AS/400 Advanced 36
machines are in chapter 4 of the Getting SSP and OS/400 Installed and Running
book, SC21-8377.
Understanding Default Startup Settings

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 need to decide whether you want to start ILAN manually or automatically and
make 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/400
Advanced 36 machine, you must go to OS/400 (and any AS/400 Advanced 36
machine connected to this AS/400 Advanced 36 machine) to stop and then
restart the ILAN connections with this AS/400 Advanced 36 machine.
Manually Starting the ILAN

In order for ILAN to establish a link between the OS/400 Operating System and the
SSP Operating System, ILAN communications must be started on both operating
systems.
On the OS/400 Operating System, the APPC Controller Description was created
with ONLINE(*YES) specified. This starts and varies on the Controller Description
objects 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 ILAN

You must make changes to the OS/400 side if you want ILAN communications to
manually start for OS/400.
Chapter 29. System-to-System Communications - ILAN Communications 29-3

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 each
AS/400 Advanced 36 machine. They must be completed each time you do either
of 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/400
Advanced 36 machine, you must vary your AS/400 controller
description *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 first
AS/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 36
machine, type
VRYCFG ILANM36ðx \CTL \ON
where x is the number of an AS/400 Advanced 36 machine that you want
to start. For the second AS/400 Advanced 36 machine, x is 2. For the
third AS/400 Advanced 36 machine, x is 3.
b. Press Enter.
ILAN communications are now started on the OS/400 side for either the
second or third AS/400 Advanced 36 machine.
Manually Starting the SSP Side of ILAN (All Connections)


ILAN Communications
On the SSP Operating System, communication line 15 is used for ILAN commu-
nications. To start the APPC subsystem:
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/400
Manually Starting the SSP Side of ILAN (A Single Connection)

On the SSP Operating System, communication line 15 is used for ILAN commu-
nications. To start the APPC subsystem:
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 36
machine.
IBMM3602 is the control point name of the second AS/400 Advanced 36
machine.
IBMM3603 is the control point name of the third AS/400 Advanced 36
machine.
Sxxxxxxx (S followed by the serial number of the AS/400 system) is the
IBM-supplied control point name for OS/400. For directions on finding out
what this name is see “Finding Out the OS/400 Control Point Name” on
page 29-8.
2. Press Enter.
ILAN communications are now started on the SSP side for the single con-
nection you specified.

ILAN Communications
Automatically Starting ILAN Communications

In order for ILAN to establish a link between the OS/400 operating system and an
SSP operating system or between two SSP operating systems, ILAN communica-
tions must be started.

You do not need to make changes to the OS/400 side unless ILAN communica-
tions were changed to manually start OS/400.
Automatically Starting ILAN Communications for SSP

To 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:
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 36
machine is started until you change the instructions to start ILAN communica-
tions manually.
Automatically Starting ILAN Communications for OS/400

Directions in this section allow you to automatically start ILAN communications on
the OS/400 side of the ILAN. For directions on automatically starting the SSP side
of ILAN communications, see “Automatically Starting ILAN Communications” on
page 29-6.

You do not need to make changes to the OS/400 side unless ILAN communica-
tions were changed to manually start OS/400.

ILAN Communications
To start ILAN communications for OS/400 automatically for your first AS/400
Advanced 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 for
the first AS/400 Advanced 36 machine.
2. Press Enter.
| Each time the system is IPLed, ILAN communications will automatically start for the
OS/400 operating system.
To start ILAN communications for OS/400 automatically for the second or third
AS/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 for
the third AS/400 Advanced 36 machine if you used the recommended names
for the AS/400 APPC controller description.
2. Press Enter.
Each time the AS/400 Advanced 36 system is IPLed, ILAN communications will
automatically start for the OS/400 operating system.
Disabling Automatic Startup of ILAN

If OS/400 or SSP or both are automatically started, and you want to start them
manually, 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 of
the 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 want
to start. For the second AS/400 Advanced 36 machine, x is 2. For the
third AS/400 Advanced 36 machine, x is 3.
b. Press Enter.
This change to manual startup takes effect the next time the AS/400
Advanced 36 machine is started.
Repeat steps 1a and 1b for each AS/400 Advanced 36 machine.

ILAN Communications
2. To disable ILAN communications on the SSP side, comment out or delete the
following statement from the #STRTUP2 procedure in the #LIBRARY:
This change to manual startup takes effect after the next IPL of OS/400 or after
the next startup of the AS/400 Advanced 36 machine.
Finding Out the OS/400 Control Point Name

To 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 point
name. 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 Communications

The directions in this topic tell you how to stop ILAN communications. You must
stop ILAN communications on the OS/400 side of the ILAN and on each AS/400
Advanced 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 Side

To 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
| 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 this
AS/400 system, continue with the next step.
VRYCFG ILANM36ðx \CTL \OFF

ILAN Communications
where x is a 2 for the second AS/400 Advanced 36 machine and x is a 3 for

the 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 for
that 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/400
1. From an SSP command prompt on the AS/400 Advanced 36 machine for which
you want to stop ILAN communications, type
DISABLE ILANSBS
2. Press Enter.
3. If you get a SYS-8003 message ILANSBS -- DISABLE tried but subsystem
active., 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 for
which you completed the steps in this section.
Note: If you do not stop ILAN communications before you power down the
AS/400 Advanced 36 machine, you must go to OS/400 (and any AS/400
Advanced 36 machine connected to this AS/400 Advanced 36 machine) to
stop and then restart the ILAN connections with this AS/400 Advanced 36
machine.
Stopping ILAN on the SSP Side (Single Connection)

To stop ILAN on the SSP side, do the following on the AS/400 Advanced 36
machine from which you want to disconnect another AS/400 Advanced 36 machine
or OS/400:
1. From an SSP command prompt on the AS/400 Advanced 36 machine for which
you want to stop a single ILAN connection, type
DISABLE ILANSBS,xxxxxxxx
where xxxxxxxx is the control point name.
machine.
machine.
machine.
Sxxxxxxx (S followed by the serial number of the AS/400 system) is the
IBM-supplied control point name for OS/400. For directions on finding out
this name, see “Finding Out the OS/400 Control Point Name” on
page 29-8.
2. Press Enter.

ILAN Communications
3. If you get a SYS-8003 message ILANSBS -- DISABLE tried but subsystem

active., 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/400
Advanced 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/400
Advanced 36 machine, you must go to OS/400 (and any AS/400 Advanced
36 machine connected to this AS/400 Advanced 36 machine) to stop and
then restart the ILAN connections with this AS/400 Advanced 36 machine.
ILAN Communications Verification

This section explains how to verify that your ILAN communications are started. You
must verify ILAN communications on both OS/400 and SSP. Directions for setting
up ILAN communications are in Chapter 4 of Getting SSP and OS/400 Installed
and Running book, SC21-8377.
Verification for the First AS/400 Advanced 36 Machine

1. 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 available
OS/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 Machine

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

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)” on
page 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.
| 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” on
page 29-13.
Verification for the Third AS/400 Advanced 36 Machine

2. Go to the OS/400 console and manually start the ILAN controller for the third
AS/400 Advanced 36 machine. For directions, see “Manually Starting the
OS/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)” on
page 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.

ILAN Communications
| 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.
OS/400 Verification
| To verify ILAN communications for the first AS/400 Advanced 36 machine, do as
| follows:
WRKCFGSTS \CTL QILANM36ð1
| where QILANM36ð1 is the OS/400 APPC controller description name for the first
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 Is
Not ACTIVE or VARIED ON” on page 29-13.
5. If the status is ACTIVE or VARIED ON, and you only installed one AS/400
Advanced 36 machine, go to “SSP Side Verification” on page 29-13 and verify
the 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:
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/400
Advanced 36 machine and ILANM36ð3 for the third AS/400 Advanced 36
machine.
2. Press Enter.

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 Is
Not ACTIVE or VARIED ON” on page 29-13.
5. If the status is ACTIVE or VARIED ON, and you have checked the OS/400
side for each of your AS/400 Advanced 36 machines, go to “SSP Side
Verification” on page 29-13 and verify the SSP Side.
6. If the status is ACTIVE or VARIED ON, and you installed a third AS/400
Advanced 36 machine repeat these steps.
SSP Side Verification

For 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/400
Advanced 36 machine, there is a Y in the communicating column for that
Location 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 to
use pass-through, go to “Using Display Station Pass-Through” on
page 29-15.
If there is an N in the communicating column, ILAN communications are not
started 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 for
further directions.
Finding Out Why ILAN Is Not ACTIVE or VARIED ON

If you verified that your ILAN communications are not started on either the OS/400
side or the SSP Side, do as follows:
1. Make sure the AS/400 Advanced 36 machines are started.
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 SSP
console.
5. Try setting up ILAN communications again for the AS/400 Advanced 36
machine for which ILAN communications are not started.

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 or
end each AS/400 Advanced 36 machine. The directions in this section tell you how
to get your ILAN up and running again if you forgot to disable communications or
were unable to disable communications before you powered down or ended each
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:
| 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 36
machine 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
d. Press Enter.

ILAN Communications
Using Display Station Pass-Through
Running Display Station Pass-Through from OS/400 to SSP

Note: 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:

STRPASTHR IBMM36ðx
where IBMM360x is the control point name of the AS/400 Advanced 36
machine that you want to pass through to.
If you set up your system as recommended:
machine.
machine.
machine.
2. Press Enter.
The Display Status Passthru display appears briefly. Then, an SSP signon
display appears.
3. After the signon display appears, sign-on and do the SSP operations you want
to 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 Value

If 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 as
follows:
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.

ILAN Communications
Running Pass-Through from SSP to OS/400

Note: 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 the
IBM-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.
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 SSP

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 another AS/400 Advanced 36

machine:
1. On an SSP command line, type
PASSTHRU IBMM36ðx
where IBMM360x is the control point name of the AS/400 Advanced 36
machine that you want to pass through to.
If you set up your system as recommended:
machine.
machine.
machine.
2. Press Enter.
An SSP signon display appears.
3. Sign on and do the SSP operations you want to do.
a. Type

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.

ILAN Communications

Managing Machines and Configurations
Chapter 30. Using CL Commands to Manage AS/400

Advanced 36 Configurations and Machines
There are fourteen CL commands that were developed specifically to help you
manage 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” on
page 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 Command

To use the WRKM36 command, do as follows:
WRKM36
2. Press F4.
A display similar to the following appears.
à@ ð
Work with Machines (WRKM36)
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.

à@ ð
Work with M36 Machines

1=Create 2=Change 4=Delete 5=Display 6=Print 7=Rename
13=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:
WRKM36 \ALL/\ALL
2. Press Enter.
Creating An AS/400 Advanced 36 Machine

You can use the WRKM36 CL command to create an AS/400 Advanced 36
machine.
Important Note
It is especially important that you make sure there is enough room on your
system for the AS/400 Advanced 36 machine before you try to create it. It is
highly recommended that you follow the directions in the Getting SSP and
OS/400 Installed and Running book, SC21-8377 when you create an AS/400
To use the Work with M36 Machines display to create an AS/400 Advanced 36
machine, you would:
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 the
field 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.

| 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 Machines

You can use the WRKM36 CL command to change the attributes of AS/400
Advanced 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/400
Advanced 36 machine, you would do as follows:
2
to select Change.
2. Press Enter.
The Change Machine (CHGM36) display appears.
field 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 the
TFRM36 command.
– Users are automatically signed on when they use the STRM36PRC
command.
| 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 36
machine. 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
Deleting an AS/400 Advanced 36 Machine

You can use the WRKM36 CL command to delete an AS/400 Advanced 36
machine 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 36
machine, you would do as follows:
1. In the Opt field beside the AS/400 Advanced 36 machine that you want to
delete, 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 Its

Configuration
You can use the WRKM36 CL command to display information about an AS/400
To use the Work with M36 Machines display to display information about an
AS/400 Advanced 36 machine, you would do as follows:
display, 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 the
option and press F1.
| 4. Press Enter to display information about the AS/400 Advanced 36 machine.

| 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 Its

Configuration
You can use the WRKM36 CL command to print information about an AS/400
Advanced 36 machine and its configuration.
To use the Work with M36 Machines display to print information about an AS/400
1. In the Opt field beside the AS/400 Advanced 36 machine that you want to print
information 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 and
library-name is the name of the library in which the AS/400 Advanced 36
machine (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 machine

You can use the WRKM36 CL command to change the name of an AS/400
To use the Work with M36 Machines display to change the name of an AS/400
rename, 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 for
object type *M36. If the AS/400 Advanced 36 machine being renamed is in
use when you press Enter, the command is not run and a message is sent.
To rename any object, you must have object management authority for the
object. You must also have update authority and execute authority for the
library 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.

You can use the WRKM36 CL command to change the description of an AS/400
To use the Work with M36 Machines display to change the description of an
AS/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 to
change 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.
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.

You 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 36
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 object
occurs 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.”

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 machine

without allowing any programs running in the AS/400 Advanced 36 machine to
perform any cleanup.
| To use the Work with M36 Machines display to abnormally end an AS/400
| 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 cursor
on 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 that
command, 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 Machine

You can use the WRKM36 CL command to transfer to an AS/400 Advanced 36
machine.
To use the Work with M36 Machines display to transfer to an AS/400 Advanced 36
1. In the Opt field beside the AS/400 Advanced 36 machine to which you want to
transfer this display station, type
16
to select Transfer.
2. Press F4.
The Transfer to Machine (TFRM36) display appears.
WRKM36CFG
field 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 Configuration

Command
To use the WRKM36CFG command, do as follows:
WRKM36CFG
2. Press F4.
à@ ð
Work with Machine Config (WRKM36CFG)
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.

WRKM36CFG
à@ ð
Work with AS/4ðð Advanced 36 Machine Configurations

1=Create 2=Change 4=Delete 5=Display 6=Print 7=Rename
13=Change description
M36
Opt 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:
WRKM36CFG \ALL/\ALL
2. Press Enter.
Creating an AS/400 Advanced 36 Machine Configuration

You can use the WRKM36CFG CL command to create an AS/400 Advanced 36
machine configuration. Up to three AS/400 Advanced 36 machines are supported
on 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 using
the APYM36CFG parameter on the STRM36 command before it affects an
To use the Work with Machine Config (WRKM36CFG) display to create an AS/400
Advanced 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) display
appears.
field 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 member

on 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
WRKM36CFG
| machine configuration whose configuration information should be copied. If you do

not 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 supply
configuration information. If you specified a from object, these displays show the
copied configuration information. You can change this configuration information or
leave it as it is.
The configuration defines the attributes to be used for an AS/400 Advanced 36

machine. When the configuration is applied to an AS/400 Advanced 36 machine, a
copy of those attributes are stored in the *M36 object. This is done using the
APYM36CFG parameter with the Start AS/400 Advanced 36 Machine (STRM36)
command.
It is acceptable to create an empty configuration. However, an AS/400 Advanced

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

36 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 you
want to change, type
2
to select Change.
2. Press Enter.
The Change Machine Configuration (CHGM36CFG) display appears.
field 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.

WRKM36CFG
Deleting an AS/400 Advanced 36 Machine Configuration

You can use the WRKM36CFG CL command to delete an AS/400 Advanced 36
To use the Work with Machine Config (WRKM36CFG) display to delete an AS/400
want 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 not
affect the AS/400 Advanced 36 machine to which it was applied. The AS/400
Advanced 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
Displaying an AS/400 Advanced 36 Machine Configuration

You can use the WRKM36CFG CL command to display information about an
To use the Work with Machine Config (WRKM36CFG) display to display information
about 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 to
display 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 the
option 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 .
WRKM36CFG
Printing an AS/400 Advanced 36 Machine Configuration

You can use the WRKM36CFG CL command to print the AS/400 Advanced 36
To use the Work with Machine Config (WRKM36CFG) display to print the AS/400
want to print, type
6
to select Print.
2. Press Enter.
When printing is complete, the following message appears at the bottom of
your display:
Object printed for configuration-name in library-name type \M36CFG.
where configuration-name is the name of the AS/400 Advanced 36 machine
configuration and library-name is the name of the library in which the AS/400
Advanced 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 Configuration

You can use the WRKM36CFG CL command to change the name of an AS/400
Advanced 36 machine configuration.
To use the Work with Machine Config (WRKM36CFG) display to change the name
of an AS/400 Advanced 36 machine configuration, you would do as follows:
want 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 field
must be unique in that library for AS/400 Advanced 36 machine configurations.
field 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 the
object. You must also have update authority and execute authority for the
library in which the object is located.

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

Configuration
You can use the WRKM36CFG CL command to change the description of an
To use the Work with Machine Config (WRKM36CFG) display to change the
description 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 you
want 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.
| 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.

Machines
The Figure 30-3 table includes the CL commands used only to manage AS/400
Advanced 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 you 14-5
to change attributes for a machine.
CHGM36CFG Change AS/400 Advanced 36 Machine Chapter 31,
Configuration: Allows you to change an AS/400 “Changing Your
Advanced 36 machine configuration. The config- AS/400
uration can be applied to an AS/400 Advanced 36 Advanced 36
machine. Once applied, the configuration of the Machine
AS/400 Advanced 36 machine is changed. Configuration”
CRTM36 Create AS/400 Advanced 36 Machine: Allows you CL Reference
to create an AS/400 Advanced 36 machine. book,
SC41-4722.

CRTM36CFG Create AS/400 Advanced 36 Machine CL Reference
Configuration: Allows you to create an AS/400 book,
Advanced 36 machine configuration. You can SC41-4722.
apply the configuration to any AS/400 Advanced 36
machine using the STRM36 command.
DLTM36 Delete an AS/400 Advanced 36 Machine: Allows CL Reference
you to delete an AS/400 Advanced 36 machine and book,
all of the libraries, files, and folders that exist on SC41-4722.
that machine.
DLTM36CFG Delete an AS/400 Advanced 36 Machine CL Reference
Configuration: Allows you to delete an AS/400 book,
Advanced 36 machine configuration. This does not SC41-4722.
affect any AS/400 Advanced 36 machine to which it
was applied.
DSPM36 Display AS/400 Advanced 36 Machine: Allows you “Displaying a
to display information about an AS/400 Advanced Machine” on
36 machine. page 32-2
DSPM36CFG Display AS/400 Advanced 36 Machine “Displaying a
Configuration: Allows you to display information Configuration”
about a configuration object that you can apply to on page 32-1
an AS/400 Advanced 36 machine.
ENDM36 End AS/400 Advanced 36 Machine: Used to stop “Stopping an
an AS/400 Advanced 36 machine when it cannot AS/400
be stopped by other means. Advanced 36
Machine from
the OS/400
Operating
System” on
page 16-3
STRM36 Start AS/400 Advanced 36 Machine: Allows you to Chapter 15,
start an AS/400 Advanced 36 machine. “Starting an
AS/400
Advanced 36
Machine”
STRM36PRC Start AS/400 Advanced 36 Machine Procedure: “Transferring to
Allows you to start an SSP procedure from an an AS/400
OS/400 command line for a specific AS/400 Advanced 36
Advanced 36 machine. If you want access to an Machine Using
AS/400 Advanced 36 machine to do more than run the
| a procedure, you should use the TFRM36 or STRM36PRC
| STRPASTHR commands. Command” on
page 14-6
| TFRM36 Transfer to AS/400 Advanced 36 Machine: Allows Chapter 14,
you to transfer from an OS/400 display station to “Transferring to
an SSP display station for a specific AS/400 an AS/400
Advanced 36 machine. If you want access to an Advanced 36
AS/400 Advanced 36 machine to just run a proce- Machine”
dure, you could use the STRM36PRC command.
WRKM36 Work with AS/400 Advanced 36 Machines: Allows This chapter
you to work with all of your AS/400 Advanced 36
machines at the same time.


WRKM36CFG Work with AS/400 Advanced 36 Machine This chapter
Configuration: Allows you to work with all the con-
figurations that can be applied to an AS/400
Note: For additional information on any of these commands, type the command
on an OS/400 command line and press F4, or see the CL Reference book,
SC41-4722.

Configuration
Chapter 31. Changing Your AS/400 Advanced 36 Machine

Configuration
You use the Change AS/400 Advanced 36 Machine Configuration (CHGM36CFG)
command to change the configuration of an AS/400 Advanced 36 machine. The
changes you make to the configuration only affect an AS/400 Advanced 36
machine 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 applies
the updated configuration information to the AS/400 Advanced 36 machine. The
changes 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 36

configuration. 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” on
page 31-17.
“Changing a Workstation Controller from Controller Mapping to Device
Mapping” on page 31-22.
“Defining Whether SSP or OS/400 Controls SSP Printer Output” on
page 31-26.
– “Giving SSP Control of AS/400 Advanced 36 Machine Printer Output” on
page 31-26.
– “Giving OS/400 Control of AS/400 Advanced 36 Machine Printer Output” on
page 31-30.
– “Giving OS/400 Control of Printer Output When There Is No Physical
Printer” on page 31-32.
“Defining Whether SSP or OS/400 Controls the Display Station” on
page 31-36.
Note: The configuration changes in the previous list require no additional changes
in 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. The
tasks 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.

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. All
commands must be entered from the console of the AS/400 Advanced 36
machine for which you want to make configuration changes.
Configuration That Exists Immediately after Installation
OS/400 Added to a System That Previously Was SSP Only

If 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 as
the configuration of your system before you added OS/400:
When the SSP refers to T1, T2, TC, I1, and communications lines 1-10, it will
refer 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 printers
attached to them, it will refer to the same physical workstation controllers and
the devices attached to them at the same physical ports and addresses as it
did before OS/400 was added.
There is one exception. It will normally be the case that the OS/400
system console display is attached to the same physical workstation con-
troller as appears to be workstation controller 1 to the AS/400 Advanced 36
machine. When this is the case, then to prevent both OS/400 and SSP
from trying to use the same display station as their system consoles, there
must 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 0
address 0. It is therefore the SSP system console. The display station
physically 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, it
would 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. This
means that entire physical workstation controllers are mapped to entire
logical workstation controllers on the AS/400 Advanced 36 machine. If you
cable new displays or printers to the workstation controller, those devices
will auto-configure into the master configuration record of the AS/400
– All display stations on mapped controllers will be automatically acquired by
the AS/400 Advanced 36 machine when it is started. The only exception to
this will be the display station which is the OS/400 console. That device
will 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 the
OUTQ parameter on the // PRINTER OCL statement.

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 Manufacturing

If your system was ordered with both OS/400 and SSP, the preloaded AS/400
Advanced 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. If
there is more than one such resource, it will refer to the one with the lowest
address on the system bus.
| Note: You can change the configuration to include the CD-ROM drive as a
tape drive.
When the SSP refers to T1 or T2, it will refer to the 1/2" tape cartridge or reel
devices. 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 in
the configuration. This would be true if they were added to your system after
the configuration was established in the manufacturing process. If this is the
case, you may change the configuration to add them yourself.
| Note: You can change the configuration to include the CD-ROM drive as a
tape drive.
When the SSP refers to I1, it will refer to the diskette drive which has the
lowest address on the system bus. It is possible that the diskette drive may not
be included in your configuration. This would be true if it was added after the
configuration 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 the
token ring port resources which have the lowest addresses on the system bus
respectively. You may need to change the configuration to associate different
SSP 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 and
addresses.
There is one exception. It will normally be the case that the OS/400
system console display is attached to the same physical workstation con-
troller as appears to be workstation controller 1 to the AS/400 Advanced 36

Configuration
machine. When this is the case, then to prevent both OS/400 and SSP
from trying to use the same display station as their system consoles, there
must 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, and
will be the SSP system console. The display station physically 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, it would 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. This
means that entire physical workstation controllers are mapped to entire
logical workstation controllers on the AS/400 Advanced 36 machine. If you
cable new displays or printers to the workstation controller, those devices
will auto-configure into the master configuration record of the AS/400
– All display stations on mapped controllers will be automatically acquired by
the AS/400 Advanced 36 machine when it is started. The only exception to
this will be the display station which is the OS/400 console. That device
will 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 the
OUTQ 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 the
Defining a Communications Line or a LAN

If you are connecting your AS/400 system to external communications you will need
to 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:
CHGM36CFG
2. Press F4.
3. In the Machine configuration field, type the name of the AS/400 Advanced 36
4. In the Library field, type the name of the library in which the AS/400 Advanced
36 machine configuration object is stored.

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 used
for any of the following communications methods: Async, Bisync, SDLC, X.21
Short 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 and
Frame Relay Support book, SC41-3404. You should follow the example for the
System/36 when setting-up the token-ring connection for an AS/400 Advanced
36 machine.
9. If you want to add or replace a communication line, type the Resource Name
of the desired AS/400 communication port in the AS/400 Communication
Resource 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 for
you. The ports selected will be the same ones that would be used by SSP
if OS/400 were not installed.
b. Use F4 to prompt, as follows:
1) Move the cursor to the entry in the AS/400 Communication Resource
column corresponding to the desired line number.
2) Press F4 to see a list of the Resource Names that can be used for that
communication 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 of
the 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 “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
then 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 this
chapter before exiting.
14. To save and exit,

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 not
be saved.
c. Press Enter.
The configuration changes are saved and the display with the OS/400
command line where you typed CHGM36CFG appears. The following
message appears:
Object changed for configuration object-name in library-name type \M36CFG.
where configuration_name is the name of the configuration you just
changed and library_name is the name of the library that contains the con-
figuration.
Note: Use the APYM36CFG (library-name/configuration-name) parameter
on the STRM36 command to apply the configuration changes to an
AS/400 Advanced 36 machine. The changes will not affect an
AS/400 Advanced 36 machine until you do this.
15. When you set up communications lines, follow the System/36 directions in the
appropriate books:
Communications Protocol SSP Book Reference
Async S/36 Using the Asynchronous Communications Support
book, 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) Guide
book, SC21-9471.
Some types of communications are allowed from OS/400 or from an AS/400

Advanced 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 up
APPN for all of these communications types except Apple Talk. These types of
communications 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.

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 and
OS/400 Installed and Running book, SC21-8377.
| The following type of communications can be done from OS/400 or from an AS/400
Advanced 36 machine. However, you must send the AS/400 Advanced 36
machine printer output to an OS/400 output queue to use the following type of
communications:
Communications Type Book References
Fax Local Device Configuration book, SC41-4121.

Configuration
Defining a Diskette Device

To add, change, or delete a diskette device, do as follows:
CHGM36CFG
2. Press F4.
5. Press Enter.
6. Press Enter.
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. That
device is known to the SSP operating system as I1. Any diskette device
description name can be specified for I1.
9. If you want to add a device or replace a device, type the name of the device in
the 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 device
it selects is the same device the SSP operating system would select if
OS/400 was not installed.
1) Press F4 to see a list of the diskette device names that can be used for
I1.
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 device
name.
11. Press Enter.

Configuration

then return here.
13. If you need to make any configuration changes, return to step 7 on page 31-8.
a. Press F3.
be saved.
c. Press Enter.
message appears:
figuration.

Configuration
Defining a Tape or CD-ROM Device

To add, change, or delete a tape or CD-ROM device, do as follows:
CHGM36CFG
2. Press F4.
5. Press Enter.
6. Press Enter.
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. These
are 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-name
in the AS/400 Tape or Optical Device column by the tape device-ID in the M36
Tape Device column. Or, do one of the following:
a. Press F10 to have the system select the tape drives for you. The devices
it selects are the same devices the SSP operating system would select if
the OS/400 operating system was not installed.
1) Move the cursor to the entry in the AS/400 Tape or Optical Device
column that corresponds to the device ID.
2) Press F4 to see a list of the tape and CD-ROM devices that can be
used 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 space
over the tape device-ID with blanks.
11. Press Enter.

Configuration

then return here.
13. If you need to make any configuration changes, return to step 7 on
page 31-10.
a. Press F3.
be saved.
c. Press Enter.
message appears:
figuration.

Configuration
Defining Printers and Display Stations Using Device Mapping

This section assumes you have physically connected the hardware and defined the
printers and display stations to OS/400.
SSP supports a maximum of four workstation controllers. For this reason, an

AS/400 Advanced 36 machine supports only four workstation controllers. However,
since the AS/400 Advanced 36 machine's workstation controllers are logical and
not physical, you can map any display station or printer on any physical controller
to any AS/400 Advanced 36 machine workstation controller using device mapping.
Note: You can also choose to map an entire physical controller (including all of
the printers and display stations attached to the physical controller) to a
specific workstation controller on an AS/400 Advanced 36 machine. This is
called controller mapping. For directions on controller mapping, see
“Defining Printers and Display Stations Using Controller Mapping” on
page 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 and
printers mapped to its logical ports and addresses. This is done without regard to
the 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 be
the SSP system console. Other than that, you can map devices to any ports and
addresses. All fifty-six port and address combinations of each logical workstation
controller may have a display station or printer mapped to them. All fifty-six can be
used 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 and
addresses you specify.
To add, replace or delete a printer or display station using device mapping, do as

follows:
CHGM36CFG
2. Press F4.
5. Press Enter.
6. Press Enter.
2
to select Change M36 display and printer devices.

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 filled
in already with *DEV.
b. Go to step 10.
To configure a new workstation controller with device mapping and add
workstation 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 device
mapping and map workstation devices to it:
Note: If the workstation controller is mapped with controller mapping,
the line is filled in with an OS/400 Workstation Controller
Description.
b. Type *DEV over the name.
After you have applied this configuration to your AS/400 Advanced 36
machine, you may want to use the CNFIGSSP procedure to remove
printers or display stations that are no longer part of the AS/400
Advanced 36 machine configuration from the master configuration
record.
Note: Before you type over the controller name, you may want to save
the attributes. For directions, see “Changing a Workstation
Controller from Controller Mapping to Device Mapping” on
page 31-22.
c. Go to step 10 to add the workstation devices.
To remove a workstation controller from the configuration:
b. Blank out the line.
After you have applied this configuration to your AS/400 Advanced 36
machine, you may want to use the CNFIGSSP procedure to remove
the display stations and printers associated with this workstation con-
troller from the master configuration record.
c. Go to step 12 on page 31-15.

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 of
a device description for the printer or display station that you want configured at
the 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 the
basis for the AS/400 Advanced 36 machine's workstation controller. If you
do this, all display stations and printers currently attached to that controller
will 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 M36
Display and Printer Dev display.
b. In the Opt field on the line with the name of the AS/400 workstation
controller that contains the devices you want automatically filled in for
the AS/400 Advanced 36 machine's workstation controller, type
1
Note: F11 works as a toggle to allow you to see the controller names
and their descriptions or to see just controller names. Selecting
just controller names allows you to see more choices on a
single display. If necessary, you can use Page Down to see
more controller names.
c. Press Enter.
The Select AS/400 Work Station Ctlr display is replaced by the Chg
M36 Display and Printer Dev display. This display is automatically filled
in with the devices that are physically connected to the controller you
chose.
If you are working with the AS/400 Advanced 36 machine's workstation
controller 1 and you auto-filled it from the AS/400 workstation controller
that contains the OS/400 system console, the devices at port 0
addresses 0 and 1 were switched when they were filled in.
Notes:
1) If the OS/400 system console is physically cabled to port 0 address
0, it will appear at port 0 address 1 in the display.
2) The device physically cabled to port 0 address 1 will appear in the
display 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 see
on the display instead of at the ports and addresses to which they
are 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.

Configuration
Technique 2
You can add or replace a device at a particular port and address by typing
the desired device description name at the desired port and address. You
can remove a device from a particular port and address by spacing over its
name with blanks.
Note the following considerations for device mapping:
– The display stations and printers you include in the configuration must
be locally attached twinax or ASCII devices.
Note: Locally attached ASCII printers may only be configured as
output queues. For information on how to configure these
printers, see “Giving OS/400 Control of AS/400 Advanced 36
Machine Printer Output” on page 31-30.
– The display stations and printers must be known to OS/400. They can
be cabled to any AS/400 workstation controller, at any port and
| address. The display stations can be any sessions of a multi-session
device.
For information on restrictions on using the multi-session devices, see
the 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 1
will be the SSP system console for the AS/400 Advanced 36 machine.
You should choose some device other than the OS/400 system console
to 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 have
applied 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 on
page 31-13. Otherwise, continue with step 13 on page 31-15.
13. Press Enter.
then return here.
page 31-12.

Configuration
a. Press F3.
be saved.
c. Press Enter.
message appears:
figuration.

Configuration
Defining Printers and Display Stations Using Controller Mapping

printers and display stations to OS/400.
SSP supports a maximum of four controllers. For this reason, an AS/400

Advanced 36 machine supports only four controllers. These controllers are logical
so you can map any physical AS/400 workstation controllers to them. Mapping a
physical workstation controller also maps all the display stations and printers that
are 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 is
called device mapping. You might choose to use device mapping to more
effectively assign display stations and printers to multiple AS/400 Advanced
36 machines. You would have to do this if you needed to include devices
that were cabled to more than four physical workstation controllers. For
directions on device mapping, see “Defining Printers and Display Stations
Using Device Mapping” on page 31-12.
Controller mapping maps an AS/400 Advanced 36 machine workstation controller to

a physical AS/400 workstation controller. When you do controller mapping, you do
| not map individual devices. The devices are mapped implicitly when the controller
is mapped. All of the devices attached to the physical workstation controller will
auto-configure into the corresponding mapped workstation controller of the AS/400
Advanced 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 of
the AS/400 workstation controller to which workstation controller 1 of the AS/400
Advanced 36 machine is mapped, unless that device is the OS/400 system
console. In that case, there must be a display station cabled at port 0 address 1 of
that 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 be
the SSP system console.
To add or replace a printer or display station, cable it to the physical workstation

controller 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:
WRKCFGSTS \DEV
b. Press Enter.
The Work with Configuration Status display appears.

Configuration
c. Find the name of the Device Description for the device you uncabled. You
may 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 from
the WRKCFGSTS command.
3. Use the CNFIGSSP procedure in the AS/400 Advanced 36 machine to remove
the device from the master configuration record.
To configure workstation controllers with controller mapping, do as follows:

CHGM36CFG
2. Press F4.
5. Press Enter.
6. Press Enter.
2
8. Press Enter.
9. To define display stations and printers using controller mapping, do one of the
following:
| To configure the same workstation controllers that would be configured for
the SSP operating system if the OS/400 operating system was not installed
on your system,
a. Press F10.

Configuration
The list of workstation controllers on this display is filled in with the

physical 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 workstation
controller number (1-4).
Note: If this controller is not configured for the AS/400 Advanced 36
machine, this line is blank.
b. If you know the name of the OS/400 Controller Description for the
AS/400 workstation controller you want to map, type the name on the
line.
c. Otherwise:
1) Press F4 to bring up a list of OS/400 Controller Description names
that 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 the
Chg M36 Display and Printer Dev display and the selected name is
filled in on the display.
d. Go to step 10 on page 31-20.
To change a workstation controller from device mapping to controller
mapping, or to change the mapping to a different AS/400 workstation
controller:
Note: If the workstation controller is device mapped, the line contains
the special value *DEV. If the workstation controller is already
mapped to an AS/400 workstation controller, the line contains
the 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 the
OS/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 to
the workstation controller, type
1
3) Press Enter.
The list of OS/400 controller description names is replaced by the
Chg M36 Display and Printer Dev display and the selected name is
filled in on the display.
d. Go to step 10.

Configuration
To remove a workstation controller from the configuration:

Note: If the workstation controller is defined in the AS/400 Advanced
36 machine configuration, the line contains either the special
value *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 the
configuration to your AS/400 Advanced 36 machine, you may want to use
the CNFIGSSP procedure to remove any printers or display stations that
are no longer in the machine configuration from the master configuration
record.
To see the OS/400 Device Description names for the display stations and
printers that are currently attached to an AS/400 workstation controller that
is mapped:
troller number.
b. Press F21.
A grid with rows of ports and columns of addresses is displayed, with
the 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.
then return here.
page 31-18.
a. Press F3.
be saved.
c. Press Enter.

Configuration
message appears:
figuration.

Configuration

Mapping
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 with
device mapping.
You want the display stations and printers you have chosen to have the same
configuration 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 System
Configuration–SSP book, SC21-8295.
To change the workstation controller to device mapping from controller mapping, do

the following:
CHGM36CFG
2. Press F4.
5. Press Enter.
6. Press Enter.
7. Determine whether there are any display stations or printers whose attributes
are something other than the default values and make note of any of these that
are different from the default values. To do this, do the following:
a. In the Opt field, type
3

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 the
following 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. You
may need to page down to reach the bottom of the display.
f. Press F12 twice to return to the Change M36 Configuration display.
2
to select Change M36 display and printer devices
9. Press Enter.
10. Move the cursor to the line that corresponds to the workstation controller
number. Write down the name of the workstation controller. You will need it
later.
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 of
addresses.
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 controller
you wrote down in step 10.
1
16. Press Enter.
The Chg M36 Display and Printer Dev display returns.

Configuration
The names of device descriptions for display stations and printers are now in
the port and address fields that correspond to how they are physically cabled.
17. Press Enter twice.
18. If you did not list any information in step 7e on page 31-23, go to step 25 on
page 31-24. Otherwise, go to step 19.
3
20. Press Enter.
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 workstation
controller. 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 the
list.
Note: You may need to page down to find it.
b. Change the Display M36 signon at IPL field or the Spooling Attribute on the
display 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.
then return here.
26. If you need to make any configuration changes, return to step 7 on page 31-22
or step 19 on page 31-24.
a. Press F3.

Configuration
be made.
c. Press Enter.
command line where you typed CHGM36CFG appears with the following
message at the bottom of the display:
Object changed for configuration_name in library_name type \M36CFG.
figuration.
Note: Use the APYM36CFG (library-name/Configuration_name) parameter

Configuration
Defining Whether SSP or OS/400 Controls SSP Printer Output

You can use the AS/400 Advanced 36 machine configuration object to give control
of your printer output either to SSP or to OS/400. The default is to give control to
SSP. You do this on an individual basis, for printers defined to the SSP. If you
give control of the printer output for a printer to:
SSP, then any printer output created within the AS/400 Advanced 36 machine
for 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 Device
Description is mapped to the SSP printer for which the output was created.
You can give control to SSP regardless of whether you use controller mapping
or 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 36
machine for that printer is placed in an OS/400 output queue and is only visible
through 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/400
Device Description for the printer to which the SSP operating system's
printer 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 name
and using it to override the OS/400 Device Description for the printer to
which the SSP's printer is mapped. You can do this regardless of whether
you used controller mapping or device mapping.
– If you used device mapping, you can also specify the fully qualified name of
any 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 configuring
an output queue as a printer without having to base it on a printer device
description.
You would use OS/400 print spooling to print any output which is placed in an
output queue regardless of whether the output came from an SSP program or
an OS/400 program.
Note: You can also use the OUTQ parameter on the // PRINTER OCL statement
to 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 or
printing it directly. For information on the // PRINTER OCL statement, see
the General Information for SSP Operating System book, SC21-8299.
Giving SSP Control of AS/400 Advanced 36 Machine Printer Output

printer to OS/400. It also assumes you have added the printer to the AS/400
To give the SSP operating system control of AS/400 Advanced 36 machine printer
output, do as follows:
1. Find out the controller number, port number, and address of the printer as
defined in the SSP configuration object using the CNFIGSSP procedure from
an SSP command line on the AS/400 Advanced 36 machine.

Configuration
For directions, see the Changing Your System Configuration–SSP book,

SC21-8295.
CHGM36CFG
3. Press F4.
6. Press Enter.
7. Press Enter.
3
9. Press Enter.
10. In the M36 Controller field, type the identification number of the AS/400
Advanced 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 of
the display stations and printers on the specified controller.
The following columns are displayed:
Port This column displays the logical AS/400
Advanced 36 machine port.
Addr This column displays the logical AS/400
Advanced 36 machine address.
AS/400 Device This column displays:
The AS/400 device name that is mapped
to the port and address listed on the
same line
*OUTQ if you are mapping an AS/400
Advanced 36 machine printer at this port
and address to an OS/400 output queue
but 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:

Configuration
Y Assigns the display station to the

The SSP Sign-On display is auto-
matically shown on the display
station when the AS/400 Advanced
36 machine is started.
Note: If someone is already
signed-on to OS/400 at the
display station before the
AS/400 Advanced 36
machine is started, the
SSP Sign-On display
appears after that person
signs off of OS/400.
N Causes the OS/400 Sign-On
display to remain on the display
station when the AS/400 Advanced
36 machine is started. Once you
sign on to the OS/400, you can
use the TFRM36 command to
transfer to the AS/400 Advanced
36 machine from this display
station.
Spooling Attributes This column only applies to printers. There
are three spooling options.
*S36 Specifies that no spooling is done
by the OS/400 operating system.
*S36 is the default.
If there is a printer device-name in
the AS/400 device column, and
*S36 is specified, the printer is
acquired by SSP when a request is
made to send output to this printer.
Printer output prints real time as it
is sent to the printer.
OS/400 can use the printer when
is no longer using the printer.
*DEV Specifies the AS/400 printer device
output queue that is in library
QUSRSYS. Anytime SSP prints to
that printer, the output goes to the
output queue in library QUSRSYS
that has the same name as the
printer in the AS/400 Device field.
qualified output queue name Specifies the
output queue name that is to be
used for spooled files. This must
be specified if the AS/400 Device
is specified as *OUTQ.

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 port
number 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 column
is *OUTQ. In this case, there is no printer mapped to that port and
address. See “Giving OS/400 Control of Printer Output When There Is
No Physical Printer” on page 31-32.
15. To change other printers on this workstation controller, return to step 12 on
page 31-29.
16. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display appears showing the M36 controller
field.
17. If you want to change the Spooling Attributes on other AS/400 Advanced 36
machine workstation controllers, return to step 10 on page 31-27.
18. Press Enter.
then return here.
page 31-27.
a. Press F3.
be made.
c. Press Enter.
figuration.

Configuration

Giving OS/400 Control of AS/400 Advanced 36 Machine Printer Output

To give the OS/400 operating system control of AS/400 Advanced 36 machine
printer output, do as follows:
SC21-8295.
CHGM36CFG
3. Press F4.
6. Press Enter.
7. Press Enter.
3
9. Press Enter.
Advanced 36 machine controller that the SSP printer is attached to.
11. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display changes to show the attributes of
the 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-27
12. Search through the list to find the entry corresponding to the printer's port
number 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:

Configuration
a. Type *DEV if you want to send the output to the output queue that has the
same name as the device description for the printer mapped at this port
and address.
Note: You cannot choose this option if the name in the AS/400 Device
column is *OUTQ. In this case, there is no printer mapped to the
port and address. See “Giving OS/400 Control of Printer Output
When There Is No Physical Printer” on page 31-32.
b. Type a fully qualified name of the output queue if you want to give control
of the printer output to OS/400 but override the printer device description
and 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.
page 31-30.
15. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display appears showing the M36 controller
field.
16. If you want to change the Spooling Attributes on other AS/400 Advanced 36
machine workstation controllers, return to step 10 on page 31-30.
17. Press Enter.
then return here.
page 31-30.
a. Press F3.
be made.
c. Press Enter.

Configuration

figuration.
| 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 Physical

Printer
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 36
machine printer output, do as follows:
SC21-8295.
CHGM36CFG
3. Press F4.
6. Press Enter.
7. Press Enter.
2
9. Press Enter.

Configuration
10. Position the cursor on the AS/400 Work Station Controller field of the controller
for which you want to define the output queue for your printer output.
Note: The controller you choose must use device mapping (*DEV) to define
display stations and printers.
11. Press F21.
The Chg M36 Display and Printer Dev display changes to show the devices
defined 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.
a. To configure an output queue at a particular port and address, type *OUTQ
in 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 configure
the printer at the desired port and address.
b. To remove an output queue from a particular port and address, space over
the *OUTQ at that port and address with blanks. You may later want to
use the CNFIGSSP procedure to remove the printer at that port and
| address from the SSP master configuration record.
page 31-33.
15. Press Enter.
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 is
associated 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
b. Press Enter.
c. In the M36 Controller field, type the identification number of the AS/400
Advanced 36 machine workstation controller where you defined the *OUTQ
special value.
d. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display changes to show the attributes
of the display stations and printers on the specified controller.

Configuration
You are only interested in the special value *OUTQ in the AS/400 Device
column. For information on which printer attributes you can specify, see
step 11 on page 31-27 and then return here.
e. Verify *OUTQ is specified for the correct port and address. You may need
to 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 of
the 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 Advanced
36 machine workstation controllers, return to step 18c on page 31-33.
Press Enter.
then return here.
20. If you need to make any configuration changes, return to step 8 on page 31-32
or step 18 on page 31-33.
21. To save and exit.
a. Press F3.
be made.
figuration.

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 automatically
removed from the master configuration record. If the changes you make
require 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.

Configuration
Defining Whether SSP or OS/400 Controls the Display Station

This 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 display
is blanked out. Then, the SSP sign-on display appears. If the OS/400 sign-on
display is not shown when the AS/400 Advanced 36 machine is started, when
the 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 to
transfer 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 station
as defined in the SSP configuration object using the CNFIGSSP procedure
from an SSP command line on the AS/400 Advanced 36 machine.
CHGM36CFG
3. Press F4.
6. Press Enter.
7. Press Enter.
3
9. Press Enter.
Advanced 36 machine controller.

Configuration

11. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display appears with different information
displayed.
| 12. Search the list and find the entry that corresponds to the port and address of
the 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 SSP
Sign-On display is automatically shown on the display station when the AS/400
Advanced 36 machine is started.
Note: If there is a Y in this field, it is ignored for the display station that is the
OS/400 console.
If there is an N in this field, the display station is controlled by OS/400. An
OS/400 sign-on display remains on this display station when the system is
started. 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 the
Display M36 signon at IPL column.
15. If you want SSP to control the display station, make sure there is a Y in the
Display M36 signon at IPL column.
16. If you want to change the attributes of other display stations, go back to step
12 on page 31-37.
17. Press Enter.
18. If you want to change display stations on other workstation controllers, return to
step 10 on page 31-36.
19. Press Enter.
then return here.
page 31-36.
a. Press F3.

Configuration
be saved.
c. Press Enter.
message appears:
figuration.

Configuration
Validating an AS/400 Advanced 36 Machine Configuration

To 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 when
you 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 when
you 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 be
started 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.

Configuration

Displaying Configuration and Machine
Chapter 32. Displaying Information About an AS/400

Advanced 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 machine
configuration. You use the Display AS/400 Advanced 36 Machine (DSPM36)
command to display information about the AS/400 Advanced 36 machine and the
configuration that was last applied to the AS/400 Advanced 36 machine. When you
use the DSPM36CFG and DSPM36 commands, you cannot make any changes to
the 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 Configuration
To display the configuration for an AS/400 Advanced 36 machine, do as follows:
DSPM36CFG
2. Press F4.
The Display Machine Configuration (DSPM36CFG) display appears.
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.

Displaying a Machine
You 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 or
changed the configuration object and you want to know what the configuration
object 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:

DSPM36
2. Press F4.
The Display Machine (DSPM36) display appears.
3. In the Machine field, type the name of the machine.
36 machine is stored.
5. Press Enter.
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 machine
resides.
Console check When there is an SSP console check, the Console check field
appears. If it appears, it always has a value of Y. The line that
contains this field does not appear if there is not an SSP console
check for this AS/400 Advanced 36 machine.
M36 status The status of the AS/400 Advanced 36 machine. The possible
status values are as follows:
Incomplete The machine has no configuration applied. This is an
empty machine.
Damaged The machine is damaged. If you know why the machine
is damaged, you can attempt to fix the machine. If you
cannot fix the machine, the machine should be deleted.
You would then restore the machine and its data from
your last backup.

Job Queue The AS/400 Advanced 36 machine is currently on a job

queue where it is waiting to start. When you start an
AS/400 Advanced 36 machine, the request is always
sent to the QSYSNOMAX batch queue in the QSYSWRK
subsystem.
Starting The AS/400 Advanced 36 machine is starting. An IPL is
in progress.
Started The AS/400 Advanced 36 machine is started and active.
Ending A request to power off the AS/400 Advanced 36 machine
is in progress. This can be requested using the SSP
POWER OFF command or by using the OS/400
ENDM36 command. This status also occurs if the
AS/400 Advanced 36 machine session is ending abnor-
mally.
Ended The AS/400 Advanced 36 machine is not started yet or is
no 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/400
Advanced 36 machine
M36 Id A three-character unique identification assigned by the system at the
time the AS/400 Advanced 36 machine was created.
M36 fixed disk size The size of the fixed disk reserved for the AS/400
Advanced 36 machine in megabytes. You can change the size of
the fixed disk using the SSP CHGSYSVL command.
M36 auto-signon Indicates whether the users can bypass the SSP Sign-On
display when they transfer to an AS/400 Advanced 36 machine.
Note: The OS/400 STRM36PRC CL command only works if this
value 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 and
yyyyyy is the batch job number. Both of these numbers are
assigned by the system. The number of the AS/400 Advanced 36
machine 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 36
machine is attended or unattended.
Chapter 32. Displaying Information About an AS/400 Advanced 36 Configuration and Machine 32-3
User profile The name of the default AS/400 user profile associated with this
AS/400 Advanced 36 machine. This is the user profile used by the
AS/400 Advanced 36 server job for handling AS/400 requests from
the AS/400 Advanced 36 machine.
Text description The specified user description for this AS/400 Advanced 36
machine.
Note: You cannot make changes to any of these displays.
8. Press Enter.
9. To display AS/400 Advanced 36 machine configuration information, type a
number (from 2 through 6) in the Opt field.
Note: These options are described in “Displaying a Configuration” on
page 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 to
step 9.
12. To exit, press F3.

Other Useful Information
Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1
System/36 Procedures to AS/400 Commands Cross-Reference . . . . . . . . A-1
System/36 Control Commands to AS/400 Commands Cross-Reference . . . A-27
System/36 OCL Statements to AS/400 Commands Cross-Reference . . . . . A-32
| Appendix B. Displaying and Setting the IPL Mode For a 9402 Model 436 B-1
Displaying the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Setting the IPL Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Appendix C. Performance Considerations . . . . . . . . . . . . . . . . . . C-1

Understanding Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Understanding Prestart Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Setting Attributes For the AS/400 Advanced 36 Server Job . . . . . . . . . . C-3
Changing the Priority of an AS/400 Advanced 36 Server Job — Example C-4
Setting attributes for the AS/400 Advanced 36 SLIC Tasks . . . . . . . . . . C-5
Setting Attributes for the AS/400 Advanced 36 Prestart Jobs . . . . . . . . . C-6
Changing the Priority and Storage Pool for an AS/400 Advanced 36
Prestart Job— Example . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Changing the AS/400 Advanced 36 Prestart Job to Immediately Use
Changed Values — Example . . . . . . . . . . . . . . . . . . . . . . . . C-7
Appendix D. Using Electronic Customer Support . . . . . . . . . . . . . . D-1

Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
System Detected Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Putting User-Detected Problems in the Problem Log . . . . . . . . . . . . . D-2
What Happens After Submitting a Problem Through Electronic Customer
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Reviewing Status of an Open Problem . . . . . . . . . . . . . . . . . . . . . . D-3
Ordering PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Appendix E. Preparing SSP for Dedicated State . . . . . . . . . . . . . . . E-1

Procedures
Appendix A. System/36 and AS/400 Commands

Cross-Reference
System/36 procedures, control commands, and OCL statements are listed alpha-
betically, with cross-references to AS/400* commands, beginning on the following
pages.
System/36 procedures Page A-1
System/36 control commands Page A-27
System/36 OCL statements Page A-32
System/36 Procedures to AS/400 Commands Cross-Reference

The first column lists the System/36 commands in alphabetic order. The second
column lists the AS/400 commands with the same (or similar) function followed by a
brief 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 and
STRSEU 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 subsystem
descriptions
#STRTUP2 ADDAJE Adds an autostart job entry to an existing sub-
system description
WRKSBSD Allows you to work with a list of subsystem
descriptions
ALERT CHGMSGD Changes an existing message description stored in
a specified message file
ALOCFLDR RGZDLO Allows a user to reorganize document library
objects
ALOCLIBR None Function not supported or no longer required on
the AS/400 system
ALTERCOM GO CFGCMN Shows the Configure Communications display
(more command mapping information can be found
in the System/36 Migration book)
APAR CRTAPAR Records data on tape, diskette, or a save file on
disk to submit with an authorized program analysis
report (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 on
the AS/400 system
 Copyright IBM Corp. 1995, 1996 A-1

Procedures

AUTOC CRTRPGPGM Creates (compiles) RPG with automatic report
specifications
AUTOPTCH GO CMDPTF Shows Program Temporary Fix (PTF) command
menu
BALPRINT None Function not supported or no longer required on
the AS/400 system
BASIC STRBAS Starts a BASIC session
BASICP STRBASPRC Starts running a BASIC procedure saved as a
source 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) licensed
program
BGUCHART DSPCHT Displays an existing chart defined by the Business
Graphics Utility (BGU) licensed program
DSPGDF Displays, prints, or plots a graphics data file
STRBGU Starts the Business Graphics Utility (BGU) licensed
program
BGUDATA STRBGU Starts the Business Graphics Utility (BGU) licensed
program
BGUGRAPH DSPGDF Displays, prints, or plots a graphics data file
DSPCHT Displays an existing chart defined by the Business
Graphics Utility (BGU) licensed program
program
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 format
and a data file
program
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 command
message file) from the user's source members
BUILD None Function not supported or no longer required on
the AS/400 system
A-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Procedures

CACHE 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 file
description of a database
DSPFFD Displays or prints field-level information for one or
more files in one library or all libraries that the user
can 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 specified
objects 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 on
the 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
CRTCTLxxxx Creates a controller description where xxxx is the
controller class or type
CRTDEVxxxx Creates a device description where xxxx is the
device class or type
CRTLINxxxx Creates a line description where xxxx is the line
class or type
CHGCTLxxxx Changes a controller description where xxxx is the
controller class or type
CHGDEVxxxx Changes a device description where xxxx is the
CHGLINxxxx Changes a line description where xxxx is the line
class 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

Procedures

DLTLIND Deletes a line description
CNFIGSSP CRTDEVxxxx Creates a device description where xxxx is the
CRTPRTF Creates a printer device file
CHGPRTF Changes one or more of the characteristics of the
specified 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
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 in
the AS/400 environment
COBOLONL STRPDM Calls the Programming Development Manager
(PDM) utility, which allows you to work with
libraries, objects, members, and user-defined
options
COBOLP STRPDM Calls the Programming Development Manager
options
COBSDA STRPDM Calls the Programming Development Manager
options
STRSDA Starts the screen design aid main menu and allows
users to create or change a display format interac-
tively
COBSEU STRPDM Calls the Programming Development Manager
options
STRSEU Calls the source entry utility (SEU) program and
displays the main menu
COMPRESS None Function not supported or no longer required on
the AS/400 system
CONDENSE None Function not supported or no longer required on
the AS/400 system (use RGZDLO to condense a
folder)

Procedures

COPYDATA CPYF Copies all or part of a file from the database or
external device to the database or another external
device
CRTDUPOBJ Copies one or a group of objects from one library
to another
RGZPFM Reorganizes a physical file member
COPYDIAG DUPDKT Duplicates the contents from one diskette onto one
or more other diskettes
COPYI1 DUPDKT Duplicates the contents from one diskette onto one
or more other diskettes
COPYPRT CPYSPLF Copies data records in a specified spooled output
file 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 specified
message file
CRTMSGF Creates a user-defined message file
CRTS36MSGF Creates a message file from the user's System/36
message source member
CSALL DSCJOB Disconnect all interactive jobs
DATE CHGJOB Changes the attributes of a job
DEFINEID GO CFGCMN Shows the Configure Communications display
DEFINEPN GO CFGCMN Shows the Configure Communications display
DEFINLOC GO CFGCMN Shows the Configure Communications display
DEFINX21 GO CFGCMN Shows the Configure Communications display
DEFINX25 GO CFGCMN Shows the Configure Communications display
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

Procedures

DLTLIB 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 to
change, delete, create, and do other work with
DDM files
DFA DMPCLPGM Dumps all variables declared in a CL program and
all messages in the program's message queue to a
spooled printer file
DMPDLO Dumps the contents and/or attributes, or both, of
folders, documents, or internal document library
system objects to a printer file
DMPJOB Dumps the basic data structures or specific calls of
the current job or the job being serviced
DMPJOBINT Dumps the machine internal data related to the
current job
DMPOBJ Dumps the contents and/or attributes of a specified
object stored in a library to a spooled printer file
DMPSYSOBJ Dumps the contents, attributes, or both, of any
object, a generic group of objects, or all objects to
a spooled printer file
DMPTAP Dumps label information, data blocks, or both, from
labeled or unlabeled tapes to a spooled printer file
DMPTRC Dumps the performance data from the trace table
to a database file
PRTINTDTA Prints the dump file copied from DMPJOBINT
command
STRSST Starts system service tools by showing the System
Service 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, and
optionally resets the IOP associated with the speci-
fied object
DOCCNV None Function not supported or no longer required on
the 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 (Work
with Licensed Information)

Procedures

WRKSYSSTS Work with information about status of system
DSPSYSVL DSPSYSVAL Display the current value of a system value
DSU STRPDM Calls the Programming Development Manager
options
WRKMBRPDM Allows you to work with lists of members
DUMP DMPCLPGM Dumps all variables declared in a CL program and
all messages in the program's message queue to a
spooled printer file
DMPDLO Dumps the contents and/or attributes, or both, of
folders, documents, or internal document library
system objects to a printer file
DMPJOB Dumps the basic data structures or specific calls of
the current job or the job being serviced
DMPJOBINT Dumps the machine internal data related to the
current job
DMPOBJ Dumps the contents and/or attributes of a specified
DMPTRC Dumps the performance data from the trace table
to a database file
PRTINTDTA Prints the dump file copied from DMPJOBINT
command
ECSAPTCH GO CMDPTF Shows the Program Temporary Fix (PTF)
command menu
EDITNRD CHGDDMF Changes one or more of the values in the specified
DDM file
CRTDDMF Creates a distributed data management file to
define 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

Procedures

STREML3270 Starts a 3270 device emulation session
STRPRTEML Starts 3270 printer emulation
ENABLE VRYCFG Varies lines, controllers, or devices on or off, and
optionally 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 existing
database file
EPDOWNL STREML3270 Starts a 3270 device emulation session
EPLMRG None Function not supported or no longer required on
the AS/400 system
EP3270 STREML3270 Starts a 3270 device emulation session
ERAP STRSST Starts system service tools by showing the System
ERR SNDBRKMSG Sends a message to one or more work station
message queues
SNDPGMMSG Sends a message from a program to a user,
system operator, user profile message queue, or
all active users
SNDUSRMSG Sends a message from a program to a message
queue 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 to
the system
CHGDSPF Changes (in the file description) one or more of the
attributes of the specified display device file
CRTS36DSPF Creates a display file from System/36 SFGR
source
FORTGO CALL Calls a specified program and passes control to it
FORTONL STRPDM Calls the Programming Development Manager
options
FORTP STRPDM Calls the Programming Development Manager
options
FORTRANC CRTFTNPGM Compiles a FORTRAN/400* source program into
an object program

Procedures

FORTSDA STRPDM Calls the Programming Development Manager
options
tively
FORTSEU STRPDM Calls the Programming Development Manager
options
FROMLIBR CPYF Copies all or part of a file from the database or
device
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 from
diskette in a specified block format
SAVOBJ The Save Object (SAVOBJ) command saves a
copy of a single object or a group of objects
located in the same library. For job queues, output
queues, data queues, message queues, and
logical 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 diskette
or tape
HELP Replaced Replaced by online help information for commands
and 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 job
that entered the command
ICVERIFY None Function not supported or no longer required on
the AS/400 system
IDDU STRIDD Starts IDDU
WRKDTADCT Allows a user to work with the contents of a data
dictionary
IDDUDCT CRTDTADCT Creates a data dictionary
WRKDTADCT Allows a user to work with the contents of a data
dictionary

Procedures

IDDUDFN STRIDD Starts IDDU
DSPDTADCT Displays or prints the contents of a field, record
format, or file definition
DSPDBR Displays or prints relational information about data-
base files, record formats, and libraries
can 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 display
where you can select an option to create physical
files or enter data into a file
IDDULINK STRIDD Starts IDDU
LNKDTADFN Links or unlinks file definitions in a dictionary and
program-described files
IDDUPRT STRIDD Starts IDDU
can access
DSPDBR Displays or prints relational information about data-
base files, record formats, and libraries
DSPDTADCT Displays or prints the contents of a field, record
format, or file definition
IDDURBLD None Function not supported or no longer required on
the AS/400 system
IDDUXLAT None Function not supported or no longer required on
the AS/400 system
INIT CLRDKT Clears all files from a diskette
INZDKT Initializes identification information and sets the
format on a diskette
RNMDKT Changes the volume identifier of a diskette or
changes the name of its owner
INITDIAG INZDKT Initializes identification information and sets the
format on a diskette
INIT9332 None Function not supported or no longer required on
the AS/400 system
INQUIRY DSPDTA Displays the contents of a database physical file
under control of a DFU program
IPL PWRDWNSYS Powers down the system

Procedures

ITF STRITF Starts sending and receiving data through different
applications
JOBSTR CPYF Copies all or part of a file from the database or
device
RSTS36LIBM Reads a file containing library members, creates
database source or data file members on the
AS/400 system, and copies the member data from
the file into each restored member
SBMJOB Allows a job that is running to submit another job
to a job queue to be run later as a batch job
CPYFRMDKT Copies one or more files from diskette to an output
file 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 on
the AS/400 system
LIBRLIBR CPYLIB Copies a library and all of its objects to another
library
CRTDUPOBJ Copies one or a group of objects from one library
to 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 and
certain 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 or
device
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 source
file
DSPPFM Displays a physical database file member
LISTFILE CPYF Copies all or part of a file from the database or
device

Procedures

CPYFRMTAP Copies records from a tape file to a physical file,
CPYSRCF Copies records from a tape file to a physical 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 or
device
DSPLIB Displays the contents of one or more libraries
DSPOBJD Displays the names and attributes of specified
objects in a specified library
STRPDM Calls the Programming Development Manager
options
LISTNRD DSPDDMF Displays or prints detailed information about the
specified DDM file
WRKDDMF Displays a list of DDM files, which allows you to
change, delete, create, and do other work with
DDM files
LOG CHGJOB Changes the attributes of a job
CHGSYSVAL Changes the current value of the specified system
value
CHGJOBD Changes the attributes specified for a job
description object
MAINTX25 None Function not supported or no longer required on
the AS/400 system
MCSCONV None Function not supported or no longer required on
the AS/400 system
MOVEFLDR None Function not supported or no longer required on
the AS/400 system
MSGFILE CRTMSGQ Creates a user-defined message queue
DLTMSGQ Deletes the specified message queue
DSPMSG Displays messages received at the specified
message queue
GO CMDMSG Displays a menu of commands relating to mes-
sages

Procedures

RMVMSG Removes the specified message or group of mes-
sages from the specified message queue
MSRJE ENDRJESSN Ends a remote job entry session for a specified
session
GO CMDRJE Displays a menu of commands relating to remote
job entry
SBMRJEJOB Submits a remote job entry input stream to the
host system as a batch job
STRRJESSN Starts a remote job entry session for a specified
session
WRKRJESSN Allows a user to work with information about an
active remote job entry (RJE) session
NOHALT ADDMSGD Describes a message and stores it in a specified
message file
CHGMSGD Changes an existing message description stored in
CHGRPYLE Changes the message ID, comparison data,
message, or dump attributes of the reply
message queue
DSPMSGD Displays detailed information about messages in a
message file
MONMSG Monitors the messages sent to the program
message queue
WRKRPYLE Allows a user to work with reply entries currently in
the system message reply list
OFCBPRT STROFC Starts OfficeVision/400* which allows the user to
do office functions interactively
OFCCAL STROFC Starts OfficeVision/400* which allows the user to
OFCCANCL ENDSBS Ends the processing in a specified subsystem or all
subsystems
OFCCOMM None Function not supported or no longer required on
the AS/400 system
CFGDSTSRV Changes the configuration of the distribution
network

Procedures

OFCDATA SAVOBJ The Save Object (SAVOBJ) command saves a
located in the same library. The system saves the
specified objects by writing a copy of each one on
diskettes, tapes, CD-ROM volumes or in a save
file. For job queues, output queues, data queues,
message queues, and logical files, only the object
descriptions are saved, and the contents of the
objects are not saved.
SAVLIB Saves libraries to tape, diskette, or a save file on
disk
SAVDLO Saves the specified documents or folders to tape,
OFCDFLT STROFC Starts OfficeVision/400* which allows the user to
OFCDIR WRKDIR Allows user to work interactively with a set of dis-
plays to view, add, change, and remove entries in
the system directory
OFCFILE WRKDOC Allows a user to work with the word processing
function
OFCGRP WRKDSTL Allows a user to work with distribution lists
OFCINSTL RSTLICPGM Restores an IBM licensed program from tape for
initial installation or new release installation
OFCLDF STROFC Starts OfficeVision/400* which allows the user to
OFCMAIL STROFC Starts OfficeVision/400* which allows the user to
OFCMAINT CFGDSTSRV Changes the configuration of the distribution
network
OFCMSG SNDMSG Sends a message from one user to one or more
message queues
STROFC Starts OfficeVision/400* which allows the user to
OFCQ WRKDSTQ Allows the user to work with distribution requests
on the distribution queues
WRKDOCPRTQ Allows the user to work with the word processing
function
OFCSRCH STROFC Starts OfficeVision/400* which allows the user to
OFCSTAT STROFC Starts OfficeVision/400* which allows the user to
OFCUSER STROFC Starts OfficeVision/400* which allows the user to

Procedures

OLINK 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 or
device
PASSTHRU STRPASTHR Starts a pass-through session and allows the user
to sign on a remote system as if the user were
locally attached
PASSWORD CHGDSTPWD Changes the password shipped with the system for
the 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 specified
PCEXCH None Function not supported or no longer required on
the AS/400 system
PCEXEC STRPCCMD Starts a single PC application or DOS command
on the personal computer
PCOPROF CHGPCOPRF Allows you to specify if you want to use
DisplayWrite* 4 or OfficeVision/400* as your text
editor
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 physical
database 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 the
CHGJOB Changes the attributes of a job
CRTPRTF Creates a printer device file

Procedures

OVRPRTF Overrides the file named, overrides certain param-
PRINTKEY CHGDEVxxxx Changes a device description where xxxx is the
PROBLEM ANZPRB Shows the Analyze Problems menu, and allows the
user to analyze or report problems not detected by
the system
DSPPRB Displays or prints service-related information for
hardware or programming
WRKPRB Allows a user to work with the problems that were
detected by the system or by the user
PRTGRAPH DSPGDF Displays, prints, or plots a graphics data file
program
PTF APYPTF Applies PTFs to a specified licensed program
DSPPTF Displays or prints the program temporary fixes for
a specified licensed program
LODPTF Loads program temporary fixes for a specified
licensed program from the service support system,
tape, diskette, or a save file on disk
RMVPTF Removes a program temporary fix from a specified
licensed program
QRY GO CMDQRY Displays a menu of commands relating to queries
STRQRY Starts the Query function by showing the Query
main menu
WRKQRY Allows you to work with a query definition and to
run a query
QRYDE STRDFU Starts the Data File Utility (DFU) program
main menu
UPDDTA Creates and runs a temporary data file utility (DFU)
program, which allows you to update a database
file
QRYRUN RUNQRY Runs an existing query or a default query if only
the file name is specified
main menu
WRKQRY Allows you to work with a query definition and to
run a query

Procedures

READINFO DSPDOC Allows the user to display a document using the
word processing function of the OfficeVision/400
program
REMOVE DLTF Deletes a specified database or device files
DLTMSGF Deletes the specified message file including
message descriptions stored in the file
DLTPGM Deletes a compiled program or group of programs
RMVM Removes the specified member from a specified
physical 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 on
the AS/400 system
RESPONSE ADDMSGD Describes a message and stores it in a specified
message file
ADDRPYLE Adds a message entry to the system-wide auto-
matic message reply list
CHGMSGD Changes an existing message description stored in
CHGRPYLE Changes the message ID, comparison data,
message, or dump attributes of the reply
MONMSG Monitors the messages sent to the program
message queue
RMVMSGD Removes a message description from a specified
message file
WRKRPYLE Allows a user to work with reply entries currently in
the system message reply list
RESTEXTN CPYIGCTBL Copies part or all of a double-byte character set
font 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 on
disk
RSTLIB Restores user libraries saved to tape, diskette, or a
save file on disk
RESTLIBR RSTLIB Restores user libraries saved to tape, diskette, or a
save file on disk
RESTNRD RSTLIB Restores user libraries saved to tape, diskette, or a
save file on disk

Procedures

RSTOBJ Restores objects to a single library saved from
RESTORE RSTOBJ Restores objects to a single library saved from
RSTS36F Reads a file, (optionally) creates a database phys-
ical or logical file (if it does not already exist), and
copies any data into the file
RETRIEVE RSTDLO Restores filed documents, distribution documents,
and folders from tape, diskette, or a save file on
disk
RJFILE CVTRJEDTA Converts compressed AS/400 system database
files to decompressed database files written either
to another database or to AS/400 system printer
device files
STRRJERDR Starts reading a remote job entry (RJE) file
RJTABLE ADDFCTE Adds a forms entry to an existing forms control
table
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
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 file
member
RPGC CRTRPGPGM Creates (compiles) an auto report RPG program
RPGONL STRPGMMNU Starts the programmer menu
STRPDM Calls the Programming Development Manager
options
RPGP STRPDM Calls the Programming Development Manager
options
RPGR STRPDM Calls the Programming Development Manager
options

Procedures

RPGSDA STRPDM Calls the Programming Development Manager
options
tively
RPGSEU STRPDM Calls the Programming Development Manager
options
RPGX CRTRPGPGM Creates (compiles) an auto report RPG program
SAVE SAVOBJ The Save Object (SAVOBJ) command saves a
SAVS36F Creates a copy of a database physical or logical
file to diskette or tape magnetic media that can be
restored on a System/36 or to a physical file that
can be sent to a System/36
SAVEEXTN CPYIGCTBL Copies part or all of a double-byte character set
font 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,
disk
SAVSECDTA Saves all security information to tape, diskette, or
save file on disk
SAVELIBR SAVLIB Saves libraries to tape, diskette, or a save file on
disk
SAVS36LIBM Saves a copy of source file members on diskette
or tape
SAVENRD SAVCHGOBJ Saves a changed object or group of objects
located in the same library to tape, diskette, or a
save file on disk
disk

Procedures

SAVOBJ The Save Object (SAVOBJ) command saves a
SAVSTG Saves the licensed internal code and the contents
of auxiliary storage to tape
SDA STRSDA Starts the screen design aid main menu and allows
tively
SECDEF CHGSYSVAL Changes the current value of the specified system
value
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 from
one user to another
CHGDSTPWD Changes the Dedicated Service Tools (DST) pass-
word
CHGOBJOWN Transfers ownership of an object from one user to
another
CHGPWD Changes a user's password
CHKPWD Checks the password associated with a user's
profile
CRTCFGL Creates a list of remote location names and remote
location identifiers for the specified communications
type
CRTUSRPRF Creates a user profile to describe a user to the
system
DLTAUTHLR Deletes an authority holder for an associated
resource
DLTCFGL Deletes a list of remote location names and remote
type
DLTUSRPRF Deletes an individual user profile or a group profile
from the system
DSPDLOAUT Displays a list of users and their authorities
assigned to a specified document or folder
GRTOBJAUT Grants specific authority for a named object, a
generic group of objects, or all objects

Procedures

RMVAUTLE Removes a user from an authorization list
RMVDLOAUT Removes a user's specific authority to a document
or 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 owned
by a specified user profile
WRKUSRPRF Allows a user to work with a description of an
existing user profile
SECLIST CHGCFGL Changes a configuration list
CRTCFGL Creates a list of remote location names and remote
type
CRTDEVxxxx Creates a device description where xxxx is the
DSPAUTHLR Displays all authority holders on the system
DSPAUTLDLO Displays a list of documents and folders whose
security is specified on the specified authorization
list
DSPAUTUSR Displays a list of users and information about those
users who are authorized to use the system
DSPDLOAUT Displays a list of users and their authorities
assigned to a specified document or folder
DSPOBJAUT Displays a list of users assigned to an object
DSPPGMADP Displays a list of programs that use the authority of
a specified (owner) user profile or group profile
DSPSYSVAL Displays the name and value of a specified system
value
DSPUSRPRF Displays the user profile information
SECREST RSTAUT Restores authorities that were specifically assigned
to a user profile
RSTUSRPRF Restores the basic parts of a user profile or a set
of user profiles
SECSAVE SAVSECDTA Saves all security information to tape, diskette, or
save file on disk
SERVICE ANZPRB Shows the Analyze Problems menu, and allows the
the system

Procedures

WRKPRB Work with problem System Service Tools main
menu
SERVLOG ANZPRB Shows the Analyze Problems menu, and allows the
the system
WRKPRB Allows a user to work with the problems that were
detected by the system or by the user
SET CHGDEVxxxx Changes a device description where xxxx is the
SETALERT CHGMSGD Changes an existing message description stored in
SETCOMM GO CFGCMN Shows the Configure Communications display
SETDUMP ADDBKP Adds breakpoints in a program being debugged
GO CMDDBG Displays a menu of commands relating to debug-
ging
GO CMDBKP Displays a menu of commands relating to break-
points
RMVBKP Removes one or more breakpoints from the
program being debugged
STRCBLDBG Starts the debugging statements from a COBOL
program
STRDBG Starts a job in debug mode
SEU STRSEU Calls the source entry utility (SEU) program and
SLIB ADDLIBLE Adds a library name to the library list
CHGCURLIB Changes the current library entry of the library list
SMF STRPFRT Starts the Performance Tools licensed program
main menu
SMFDATA DSPPFRDTA Displays performance data collected
ENDSAM Ends the running environment defined in the
STRSAM command
ENDSAMCOL Ends sampling data and writes the collected
sample data in a database file member

Procedures

STRPFRMON Starts a collection of performance statistics based
on specified values and writes the statistics to
system-supplied database files
STRSAM Periodically samples the machine interface instruc-
tion address while running specified programs
STRSAMCOL Starts sample address monitor data collection and
collects sample data defined by the STRSAM
command
SMFPRINT PRTRSCRPT Prints a usage report for devices from data col-
lected by the OS/400 performance monitor
PRTSAMDTA Prints a report of the sampled data collected by the
STRSAMCOL command and recorded by the
ENDSAMCOL command
STRPFRT Starts the Performance Tools licensed program
main menu
SMFSTART STRPFRMON Starts a collection of performance statistics based
on specified values and writes the statistics to
system-supplied database files
SMFSTOP ENDPFRMON Ends collection of performance statistics
SORT FMTDTA Formats sort file contents
SRTX FMTDTA Formats sort file contents
STARTM VRYCFG Varies lines, controllers, or devices on or off, and
optimally resets the IOP associated with the speci-
fied object
STATEST VFYCMN Shows the Verify a Communications Line display
STOPGRP ENDMOD Ends a single mode or all active modes for a spe-
cific advanced program-to-program communica-
tions (APPC) remote location
STOPM VRYCFG Varies lines, controllers, or devices on or off, and
fied object
STRTGRP STRMOD Starts a single mode or all modes currently in use
for an APPC remote location
VRYCFG Varies lines, controllers, or devices on or off, and
fied object
SWITCH CHGJOB Changes the attributes of a job
description object
SYSLIST None Function not supported or no longer required on
the AS/400 system
SYSTYPE None Function not supported or no longer required on
the AS/400 system

Procedures

TAPECOPY CPYFRMTAP Copies records from a tape file to a physical file,
CPYTOTAP Copies records to a tape file from a physical,
logical, or spooled inline file, from tape, or from
diskette in a specified block format
TAPEINIT INZTAP Initializes tapes for use on the system
TAPESTAT None Function not supported or no longer required on
the AS/400 system.
PRTERRLOG Places a formatted print file of the data in the
machine error log in a spooled printer device file
named QPCSMPRT and is used by IBM service
representatives
TEXTCONV None Function not supported or no longer required on
the AS/400 system
TEXTDCT CRTSPADCT Creates a user-defined dictionary
CHKDOC Checks spelling or performs grade-level analysis of
a document
TEXTDOC WRKDOC Allows a user to work with the word processing
function
CRTDOC Creates a document
DSPDOC Display a document
EDTDOC Edits a document using the word processing func-
tion of OfficeVision/400
CHKDOC Checks spelling or performs grade-level analysis of
a document
PRTDOC Prints a document using the word processing func-
tion of OfficeVision/400
MRGDOC Merge a document
PAGDOC Paginate a document
TEXTFLDR CRTFLR Creates a folder
DSPFLR Displays or prints a list of folders and documents,
or creates a database file containing the list
WRKFLR Allows a user to work with folders
TEXTOBJ WRKDOC Allows a user to work with the word processing
function
TEXTPROF WRKTXTPRF Allows a user to work with text profiles
TEXTPRTQ WRKOUTQ Allows a user to work with the overall status of all
output queues
WRKDOC Allows a user to work with the word processing
function
CHGOUTQ Changes the attributes of the output queue

Procedures

TEXTREL RLSOUTQ Releases the spooled files that were previously
held on the specified output queue
WRKOUTQ Allows a user to work with the overall status of all
output queues
TOLIBR RSTOBJ Restores objects to a single library saved from
TRACE DSPLOG Displays the contents of the history log
STRJOBTRC Starts the tracing function to collect performance
statistics for a specified job
TRCCSP Traces a CSP/AE application
TRCICF Traces all ICF functions that occur within the job
that entered the command
TRCINT Traces licensed internal code and writes the data
to a spooled printer file, to tape, or to diskette, or
holds data in internal storage
TRCJOB Traces program calls and returns that occur in the
current job or in the job being serviced by the Start
Service Job command
TRANSFER CPYFRMDKT Copies one or more files from diskette to an output
CPYTODKT Copies a database or device file to diskette
TRNMGR CRTLINxxxx Creates a line description where xxxx is the line
class or type
CHGLINxxxx Changes a line description where xxxx is the line
class or type
VRYCFG Varies lines, controllers, or devices on or off, and
fied object
UPDATE CHGDTA Changes, adds, or deletes records in an existing
database file
STRRMTSPT Creates and varies on all configuration objects
needed for remote support
ENDRMTSPT Ends remote support
WRKSPL WRKSPLF Displays a list of all spool files on the system
WRKUSER WRKACTJOB Work with all active jobs on the system

Procedures

WRKUSRJOB Work with a list of user jobs
WSU None Function not supported or no longer required on
the AS/400 system
WSUTXCR None Function not supported or no longer required on
the AS/400 system
WSUTXEX None Function not supported or no longer required on
the AS/400 system
WSUTXRV None Function not supported or no longer required on
the AS/400 system
WKSTYPE None Function not supported or no longer required on
the AS/400 system

Control Commands
System/36 Control Commands to AS/400 Commands Cross-Reference

ASSIGN(A) None Function not supported or no longer required on
the AS/400 system
CANCEL(C) job name ENDJOB Ends the specified job
CANCEL(C) JOBQ(J) ENDJOB Ends the specified job
CLRJOBQ Clears all batch jobs that are not active from the
specified job queue
WRKJOBQ Allows a user to work with the overall status of all
job queues
CANCEL(C) PRT(P) DLTSPLF Deletes a specified spooled file from the output
queue
CLROUTQ Clears spooled files from specified queue
CANCEL(C) ENDJOB Ends the specified job
SESSION(S)
WRKUSRJOB Allows a user to work with a list of all jobs and pro-
vides a release option to start a held job
CHANGE(G) COPIES CHGSPLFA Changes the characteristics of a spooled output file
while it is on the output queue
output queues
CHANGE(G) DEFER CHGSPLFA Changes the characteristics of a spooled output file
output queues
CHANGE(G) FORMS CHGSPLFA Changes the characteristics of a spooled output file
output queues
CHANGE(G) ID CHGSPLFA Changes the characteristics of a spooled output file
output queues
CHANGE(G) JOBQ(J) CHGJOB Changes the attributes of a job
job queues
CHANGE(G) JOBS CHGJOBQE Changes an existing job queue entry in the speci-
fied subsystem description
CHANGE(G) PRT(P) CHGSPLFA Changes the characteristics of a spooled output file
CHANGE(G) PRTY CHGJOB Changes the attributes of a job

Control Commands

CHANGE(G) SEP CHGSPLFA Changes the characteristics of a spooled output file
CHGWTR Changes the form type, number of file separators,
and output queue attributes of an active printer
writer
CONSOLE CHGMSGQ Changes the characteristics of a specified
message queue
message queue
WRKMSGQ Allows a user to work with message queues
INFOMSG CHGJOB Changes the attributes of a job
CHGMSGQ Changes the characteristics of a specified
message queue
HOLD JOBQ(J) HLDJOB Holds a job and prevents it from being processed
HOLD PRT(P) HLDSPLF Holds the specified output file from additional pro-
cessing by a spooling writer
HLDWTR Holds activity of the specified spooling writer at the
end of a record, a spooled file, or a printed page
JOBQ(J) SBMDBJOB Submits from a job that is currently running batch
jobs read from a database
SBMDKTJOB Submits from a job that is currently running batch
jobs read from diskette
SBMFNCJOB Submits a batch job to allow finance application
programs to communicate with 4701 or 4702 con-
troller application programs
SBMJOB Allows a job that is running to submit another job
SBMNETJOB Submits a batch job stream to a user on another
system in the network
SBMRJEJOB Submits a remote job entry input stream to the
host system as a batch job
MENU GO xxxx Immediately displays a menu showing a group of
commands (where xxxx is the name of a specific
group of commands; for example, GO CMDCRT
displays a menu of all create commands)
MODE None Function not supported or no longer required on
the AS/400 system
MSG DSPMSG Displays messages received at the specified
message queue
SNDMSG Sends a message from one user to one or more
message queues
SNDNETMSG Sends a message to a user on a remote system

Control Commands

all active users
RCVMSG Receives a message sent to a message queue
SNDBRKMSG Sends a message to one or more work station
message queues
OFF SIGNOFF Ends all interactive jobs or causes all jobs in a
group to end
POWER PWRDWNSYS Powers down the system
ENDSYS Ends all activity on the system and leaves only the
console active
PRTY CHGJOB Changes the attributes of a job
RELEASE(L) JOBQ(J) RLSJOB Releases a job for processing after the job was
held on the job queue or was submitted to the job
queue as a held job
job queues
RELEASE(L) PRT(P) RLSSPLF Releases a specified spooled file being held on an
output queue for processing by a spooling writer
output queues
WRKWTR Allows a user to work with the status of all printers,
all writers, or a specified writer
REPLY DSPMSG Displays messages received at the specified
message queue
RESTART STRPRTWTR Starts a spooling writer that sends output to a
specified printer
ENDWTR Ends the processing by the specified spooling
writer
START JOB RLSJOB Releases a job for processing after the job was
held on the job queue or was submitted to the job
queue as a held job
START JOBQ(J) CHGJOBQE Changes an existing job queue entry in the speci-

Control Commands

DSPSBSD Displays subsystem description information
RLSJOBQ Releases for processing the jobs previously held
START PRT(P) STRPRTWTR Starts a spooling writer that sends output to a
specified printer
RLSWTR Releases a spooling writer that was previously held
RLSOUTQ Releases the spooled files that were previously
START SERVICE GO CMDPRBMGT Displays a menu of commands relating to problem
management
START SESSION(N) RLSCMNDEV Releases the communications capability of a speci-
fied device that is being held
START SYSTEM(S) STRSBS Starts the subsystem activity
START WORKSTN(W) WRKCFGSTS Allows a user to work with line, controller, and
device configuration descriptions
STATUS(D) ALERT WRKALR Allows a user to work interactively with alerts
created by the local system or received from
another system
STATUS(D) APPC(A) DSPAPPNINFO Displays or prints APPN* network information
DSPMODSTS Displays the status of the APPC device
WRKCFGSTS Allows a user to work with line, controller, and
STATUS(D) COMM(C) WRKCFGSTS Allows a user to work with line, controller, and
STATUS(D) WRKCFGSTS Allows a user to work with line, controller, and
COMCNFIG(H) device configuration descriptions
STATUS(D) JOBQ(J) WRKJOBQ Allows a user to work with the overall status of all
job queues
WRKSBMJOB Allows a user to work with the status of all jobs
submitted at a work station
STATUS(D) LINE(L) WRKCFGSTS Allows a user to work with line, controller, and
STATUS(D) DSPMSG Displays messages received at the specified
MESSAGE(G) message queue
STATUS(D) MSRJE(M) GO CMDRJE Displays a menu of commands relating to remote
job entry
WRKRJESSN Allows a user to work with information about an
active remote job entry (RJE) session
STATUS(D) PRT(P) WRKOUTQ Allows a user to work with the overall status of all
output queues
STATUS(D) DSPJOB Displays information about job status
SESSION(S)

Control Commands

WRKJOB Allows you to work with or change information con-
cerning a job
SUBSESS(N) device configuration descriptions
WRKACTJOB Allows a user to work interactively with perfor-
mance and status information for active jobs in a
specified subsystem or all subsystems
STATUS(D) SUBSYS(I) WRKCFGSTS Allows a user to work with line, controller, and
STATUS(D) WRKACTJOB Allows a user to work interactively with perfor-
SYSTASK(T) mance and status information for active jobs in a
STATUS(D) USERS(U) WRKACTJOB Allows a user to work interactively with perfor-
mance and status information for active jobs in a
WORKSTN(W) device configuration descriptions
STATUS(D) WRT WRKWTR Allows a user to work with the status of all printers,
all writers, or a specified writer
STATUSF(DF) JOBQ(J) WRKJOBQ Allows a user to work with the overall status of all
job queues
WRKSBMJOB Allows a user to work with the status of all jobs
submitted at a work station
STATUSF(DF) PRT(P) WRKOUTQ Allows a user to work with the overall status of all
output queues
STATUSF(DF) WRKACTJOB Allows a user to work interactively with perfor-
USERS(U) mance and status information for active jobs in a
STATUSF(DF) WRKCFGSTS Allows a user to work with line, controller, and
WORKSTN(W) device configuration descriptions
STOP JOB NAME HLDJOB Holds a job and prevents it from being processed
STOP JOBQ(J) CHGJOBQE Changes an existing job queue entry in the speci-
DSPSBSD Displays subsystem description information
HLDJOBQ Holds processing of all jobs on the job queue or
added to the queue

OCL Statements

STOP PRT(P) ENDWTR Ends the processing by the specified spooling
writer
HLDOUTQ Holds all currently waiting spooled files and all
spooled files added to the queue from being pro-
cessed by a spooling writer
STOP SERVICE GO CMDPRBMGT Displays a menu of commands relating to problem
management
STOP SESSION(N) HLDCMNDEV Holds communications to a remote display station,
printer, or system
STOP SYSTEM(S) ENDSBS Ends the processing in a specified subsystem or all
subsystems
ENDSYS Ends all activity on the system and leaves only the
console active
ENDWTR Ends the processing by the specified spooling
writer
STOP WORKSTN(W) HLDCMNDEV Holds communications to a remote display station,
printer, or system
TIME DSPSYSVAL Displays the name and value of a specified system
value
VARY VRYCFG Varies lines, controllers, or devices on or off, and
fied object
System/36 OCL Statements to AS/400 Commands Cross-Reference

// ABEND None Function not supported or no longer required on
the AS/400 system
// ALLOCATE ALCOBJ Allocates an object or list of objects in a routing
step for later use in the routing step
// ATTR CHGJOB Changes the attributes of a job
// CHANGE CHGSPLFA Changes the characteristics of a spooled output file
// CANCEL DLTSPLF Deletes a specified spooled file from the output
queue

OCL Statements

// COMM OVRICFDEVE Temporarily adds the program device entry and the
remote location name to the ICF file, or overrides a
program device with the specified remote location
name and attributes for an ICF file
// COMPILE CRTxxxPGM Creates a program using the correct compiler
where xxx could be BAS (BASIC), CBL (COBOL),
FTN (FORTRAN), or RPG.
// DATE CHGJOB Changes the attributes of a job
CHGSYSVAL Changes the current value of the specified system
value
// DEALLOC DLCOBJ Releases the allocations of specified objects for the
specified lock status
// DEBUG STRDBG Starts a job in debug mode
// EVOKE SBMJOB Allows a job that is running to submit another job
// FILE (Disk) ALCOBJ Allocates an object or list of objects in a routing
step for later use in the routing step
OVRDBF Overrides the file named, overrides certain param-
// FILE Diskette OVRDKTF Overrides the file named, overrides certain param-
// FILE (Tape) OVRTAPF Overrides the file named, overrides certain param-
// FILELIB ADDLIBLE Adds a library name to the library list
CHGCURLIB Changes the current library entry of the library list
// FORMS CRTPRTF Creates a printer device file
// IMAGE None Function not supported or no longer required on
the AS/400 system
// INCLUDE None Function not supported or no longer required on
the AS/400 system
// INFOMSG CHGJOB Changes the attributes of a job
CHGMSGQ Changes the characteristics of a specified
message queue
// JOBQ SBMJOB Allows a job that is running to submit another job
// LIBRARY CHGCURLIB Changes the current library entry of the library list

OCL Statements

description object
CHGLIBL Changes the user portion of the current job's library
list by replacing it with the list of user-specified
libraries
// LOAD None Function not supported or no longer required on
the AS/400 system
// LOCAL CHGDTAARA Changes the value of the local data area, group
data area, or specified data area stored in a library
CHGVAR Changes the value of a CL variable
// LOG CHGJOB Changes the attributes of a job
description object
// MEMBER ADDMSGD Describes a message and stores it in a specified
message file
CRTMSGF Creates a user-defined message file
OVRMSGF Overrides a message file used in a program
all active users
// MENU xxxx GO xxxx Immediately displays a menu showing a group of
commands (where xxxx is the name of a specific
group of commands; for example, GO CMDCRT
displays a menu of all create commands)
// MSG SNDBRKMSG Sends a message to one or more work station
message queues
SNDMSG Sends a message from one user to one or more
message queues
SNDNETMSG Sends a message to a user on a remote system
all active users
// NOHALT MONMSG Monitors the messages sent to the program
message queue
// OFF SIGNOFF Ends all interactive jobs or causes all jobs in a
group to end
// POWER PWRDWNSYS Powers down the system

OCL Statements

// PRINTER OVRPRTF Overrides the file named, overrides certain param-
CHGPRTF Changes one or more of the characteristics of the
specified printer device files
// PROMPT DCLF Declares one file to a CL program
RCVF Used in a CL program to receive data from a
display device or database file
SNDF Used (in a CL program) to send a record to a
display device
SNDRCVF Used (in a CL program) to send and receive data
from a device being used interactively by a user
// REGION None Function not supported or no longer required on
the AS/400 system
// RESERVE None Function not supported or no longer required on
the AS/400 system
// RUN CALL xxxx Calls a specified program and passes control to it
// RUN400 None Function not needed on the AS/400 system.
// SESSION OVRICFDEVE Temporarily adds the program device entry and the
remote location name to the ICF file, or overrides a
program device with the specified remote location
name and attributes for an ICF file
// START PRT(P) STRPRTWTR Starts a spooling writer that sends output to a
specified printer
RLSWTR Releases a spooling writer that was previously held
RLSOUTQ Releases the spooled files that were previously
// STOP PRT(P) ENDWTR Ends the processing by the specified spooling
writer
HLDOUTQ Holds all currently waiting spooled files and all
spooled files added to the queue from being pro-
cessed by a spooling writer
// SWITCH CHGJOB Changes the attributes of a job
description object
// SYSLIST None Function not supported or no longer required on
the AS/400 system
// VARY VRYCFG Varies lines, controllers, or devices on or off, and
fied object

OCL Statements

// WAIT DLYJOB Allows your current job to wait for a specified
number of seconds, or until a specified time of day,
before running resumes
// WORKSTN OVRDSPF Overrides the file named in the program, overrides
certain parameters of a file used by the program,
or overrides the file named in the program and
certain parameters of the file processed

OCL Statements
| Appendix B. Displaying and Setting the IPL Mode For a 9402

| Model 436
| This appendix contains the instructions on how to display and set the IPL mode on
| the control panel of the 9402 Model 436. For directions on how to display and set
| the IPL mode for other models, see the System Startup and Problem Handling
| book, SC41-4206.
Displaying the IPL Mode

To display the IPL mode, do the following:
1. Open the control panel cover to access the control panel. If the control panel
cover has a Keylock feature, unlock and open the cover using the control panel
cover key.
2. Press the left or right Select pushbutton (F) until 01 is displayed in the
Function/Data display (E).
Function/Data
E
Enter G
F RTSP039-1
 Copyright IBM Corp. 1995, 1996 B-1

OCL Statements
3. Press the Enter pushbutton (G). A code similar to the following is shown:
Function/Data
E
Enter G
F RTSP040-2
Use the following to determine the meaning of each code:

B N–The mode is set to perform a normal IPL from the B side of the disk.
This mode is normally used to start the system by doing an unattended
IPL.
B M–The mode is set to perform a manual IPL from the B side of the disk.
This mode is normally used to start the system by doing an attended IPL.
D M–The mode is set to perform a manual IPL from tape or CD-ROM.
This mode is normally used to do an attended install of the Licensed
Internal Code and operating system and to restore the Licensed Internal
Code.
D N–The mode is set to perform a normal IPL from tape or CD-ROM. This
mode is used to do an unattended install of the Licensed Internal Code and
the operating system.
A M–The mode is set to perform a normal IPL from the A side of the disk.
This mode is used when applying PTFs. Use only under the direction of
your support personnel.
A N–The mode is set to perform a manual IPL from the A side of the disk.
This mode is used when an IPL from the B side cannot be performed. Use
only under the direction of your support personnel.
B-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

OCL Statements
Setting the IPL Mode

This section provides instructions for setting the IPL mode on the control panel.
Verify the current mode setting (see “Displaying the IPL Mode” on page B-1). If
the mode is not set to the desired mode, do the following:
1. If it is not already open, open the control panel cover to access the control
panel. If the control panel cover has a Keylock feature, unlock and open the
cover using the control panel cover key.
2. Press the left or right Select pushbutton (F) until 02 is displayed in the
Function/Data display (E).
A
B
D
C
Function/Data
E
Enter G
F RTSP032-1
3. Press the Enter pushbutton (G).
Appendix B. Displaying and Setting the IPL Mode For a 9402 Model 436 B-3
OCL Statements
4. Press the left or right Select pushbutton (F) to display the mode you want in the
Function/Data display (E) to select the IPL mode.
B B
Function/Data Function/Data
E E
Enter G Enter G
F F RTSP046-1
Figure B-1. Normal mode (Left) and Manual mode (Right)

6. Press the left Select pushbutton (F) until 01 is displayed in the Function/Data
display (E).
B-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Performance
Appendix C. Performance Considerations

This appendix provides helpful hints on improving performance for an installed
Notes:
1. Use the System Management Facilities (SMF) to find application problems.
SMF tracks such things as:
Locking conflicts,
OCL statements processed
File opens and closes
CPU usage rates
2. Avoid running batch jobs during high usage periods.
Consider moving batch jobs or some of your batch jobs out of peak periods.
You can use the DSPSYS command to dynamically view the three highest
CPU jobs currently running.
3. Consider performing keysorts before powering off the system.
This should only be done if IPLs are taking much longer than they did previ-
ously. If you are not running twenty-four hour operations, consider using the
stop system command with keysort. This should speed up the next IPL.
4. When you are running both OS/400 and SSP on the same AS/400 system, the
QPFRADJ parameter that you use on the CHGSYSVAL CL command should
be 3.
5. Add additional main storage or DASD.
For general system performance improvements, it may be necessary to add
additional main storage or DASD. This can be determined by using SMF.
When the system is running more slowly, use SMF to check CPU and DASD
use. If DASD use is high, more DASD will improve performance. If DASD use
is high and User Area Disk Activity (UADA) count is high, more main storage
(memory) will improve performance.
Understanding Server Jobs

When you start an AS/400 Advanced 36 machine with the STRM36 command,
OS/400 starts up what is known as an AS/400 Advanced 36 server job, which
runs as an OS/400 batch job under the user profile associated with the AS/400
Advanced 36 machine. A single server job is associated with each AS/400
Advanced 36 machine. When it is started, the server job performs an initial
program load (IPL) of the specified AS/400 Advanced 36 machine. After per-
forming the IPL, the server job handles requests for OS/400 functions coming from
SSP batch jobs and from display stations associated with the AS/400 Advanced 36
machine. (Those are the display stations acquired for use by SSP when the
machine is started.) Examples of functions handled by the server job are:
Processing IPL SSP procedure requests
A portion of DSPSYSVL SSP procedure requests
Processing CHGSYSVL DEVMAP SSP procedure requests
 Copyright IBM Corp. 1995, 1996 C-1

Performance
Creating and destroying OS/400 communication objects

Processing POWER OFF SSP control command requests
Understanding Prestart Jobs

Because the server job is responsible for responding to the requirements of all
acquired display stations and batch jobs on an AS/400 Advanced 36 machine, it
passes requests for functions that might take significant processor time to one of a
set of prestart jobs. The set of prestart jobs accept requests from any AS/400
Advanced 36 server job running on the system. Tasks run by a prestart job, run
under the user profile associated with the requesting server job. Examples of tasks
run by prestart jobs include:
Processing RUN400 OCL statement requests for display stations that are
assigned to an AS/400 Advanced 36 machine
Processing requests to open and put data into OS/400 spool files for display
stations that are assigned to an AS/400 Advanced 36 machine
| Allocating and deallocating AS/400 devices
Figure C-1 illustrates these concepts.
Interactive
OS/400 Job OS/400 Jobs
STRM36 CL command TFRM36 CL command

ENDM36 CL command STRM36PRC CL command
AS/400 AS/400
Advanced 36 Advanced 36
Server Prestart
Job Jobs
Machine Machine Machine

Interface Interface Interface
Queue Queue Queue
Machine
Interface
Boundary
IBM-supplied licensed internal code
RTSP077-0
Figure C-1. AS/400 Advanced 36 Server Jobs and Prestart Jobs. A server job handles requests for OS/400 func-
tions from display stations assigned to the AS/400 Advanced 36 machine. Requests for functions that might require
significant time are passed to prestart jobs.
C-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Performance
Setting Attributes For the AS/400 Advanced 36 Server Job

The server job runs in the QSYSWRK system-supplied subsystem and handles
requests from the AS/400 Advanced 36 machine to allocate devices, create printed
output, and so forth.
The Attribute display of the Display M36 Machine (DSPM36) command can be
used to find the OS/400 job name of the server job. You can use the Work with
Job (WRKJOB) or the Work with Active Jobs (WRKACTJOB) commands to display
information about the server job. Some of the things these commands display are
the:
Run priority of the job
Storage pool used by the job
Number of CPU seconds used by the job
You can use the Change Job (CHGJOB) CL command to make temporary changes
to the AS/400 Advanced 36 server job. The changes are lost when the AS/400
Advanced 36 server job ends or another CHGJOB command is used to change
these attributes.
When you start an AS/400 Advanced 36 machine, you can specify a user profile on
the STRM36 command or allow the AS/400 Advanced 36 machine to use the user
profile that was in the last AS/400 Advanced 36 machine configuration that was
applied to the machine. This user profile is used for the server job. In addition to
controlling object security, the user profile defines the job description (OS/400
*JOBD) that is used for the job. The job description defines attributes like:
Output queue for the job logs and for the server job
Message logging level for messages in the server's job log
Routing data for the server job
The value specified in the routing data is compared to the routing entries in the
QSYSWRK subsystem to choose the job class (OS/400 *CLS) that is used for the
job. The performance attributes like run priority and storage pool are defined within
the job class.
There are three routing entries defined in the QSYSWRK subsystem for the AS/400
Advanced 36 system:
QM36HIGH
This corresponds to an OS/400 run priority of 10. (High interactive job priority
level)
QM36MEDIUM
This corresponds to an OS/400 run priority of 20. (Normal interactive job pri-
ority level)
QM36LOW
This corresponds to an OS/400 run priority of 50. (Normal Batch priority level)
The IBM-supplied default for the run priority of the server job is 50. The default for
the storage pool for the server job is storage pool 1 as defined in the QSYSWRK
subsystem (*BASE pool).
Appendix C. Performance Considerations C-3

Performance
Changing the Priority of an AS/400 Advanced 36 Server Job —

Example
In this example, you change the priority of an AS/400 Advanced 36 machine named
M36ð1 in library M36 to run at priority 20:
1. Create a job description that will be used for the server job with routing data of
QM36MEDIUM as follows:
CRTJOBD JOBD(M36/M36ð1JOBD) RTGDTA(QM36MEDIUM) AUT(\USE)
b. Press Enter.
2. Create a new user profile for the AS/400 Advanced 36 machine to use for the
AS/400 Advanced 36 Server job. In this example, the default *USER is used
for the User Class (USRCLS keyword). *NONE is specified for the User Pass-
word because this prevents anyone from signing onto the system with this user
profile. The job description specified is M36ð1JOBD which is in library M36.
To create this user profile:
a. Type
CRTUSRPRF USRPRF(M36ð1USER) PASSWORD() JOBD(M36/M36ð1JOBD)
b. Press Enter.
Security Information
You need to be careful with the special authority and object access
authority that you give to this user profile. Users that have signed onto an
AS/400 Advanced 36 machine without signing on to OS/400 can submit
System/36 RUN400 OCL statements using this user profile's authority. You
may want to restrict access to certain functions from authorized System/36
users.
For example, if you define the new user profile to have *ALLOBJ special
authority, any authorized System/36 user can run any batch OS/400
command against any OS/400 system object.
3. Change the user profile for an AS/400 Advanced 36 machine.

In this example, the user profile for an AS/400 Advanced 36 machine is
changed to M36ð1USER for an AS/400 Advanced 36 machine named M36ð1 in
library M36L.
a. On an OS/400 command prompt, type
CHGM36CFG M36CFG(M36/M36ð1)
b. Press Enter.
Notes:
a. After the system is set up to run under a specific user profile, you only
need to change the routing data in the job description for the user profile to
select a new routing entry in the QSYSWRK subsystem.
b. You can use the Display AS/400 Advanced 36 Machine (DSPM36)
command to determine the name and the library of the last configuration
applied to the AS/400 Advanced 36 machine. For more information on
using the DSPM36 command, see “Displaying a Machine” on page 32-2.

Performance
c. If the AS/400 Advanced 36 machine configuration no longer exists, you can

create one using the Work with AS/400 Advanced 36 Machine Configura-
tion (WRKM36CFG) command. For more information on using the
WRKM36CFG command to create a new AS/400 Advanced 36 machine
configuration, see “Creating an AS/400 Advanced 36 Machine
Configuration” on page 30-9.
4. Apply the changes to the AS/400 Advanced 36 machine.
The changes are applied to an AS/400 Advanced 36 machine named M36ð1
that is in library M36. The configuration applied is also named M36ð1 and is also
stored in library M36.
Changes to an AS/400 Advanced 36 machine configuration, do not affect an
AS/400 Advanced 36 machine until the changes are applied to the AS/400
Note: If the AS/400 Advanced 36 machine is started, you must stop the
machine. To stop the AS/400 Advanced 36 machine, follow the
directions in Chapter 16, “Stopping an AS/400 Advanced 36 Machine”
on page 16-1.
To apply the configuration, after you stop the machine:
STRM36 M36(M36/M36ð1) APYM36CFG(M36/M36ð1)
b. Press Enter.
For more information about setting the attributes for OS/400 jobs, and job
descriptions, see the Work Management book, SC41-4306.
Setting attributes for the AS/400 Advanced 36 SLIC Tasks

When the AS/400 Advanced 36 Server job is started, it creates some System
Licensed Internal Code (SLIC) tasks that are used to emulate the System/36
instructions and to communicate with the various I/O devices (disks, workstations,
communications lines, tapes, CD-ROMs, and diskettes). Since these SLIC tasks
are not OS/400 jobs, the Work with Active Jobs (WRKACTJOB) command does not
display these tasks. However, the Work with System Activity (WRKSYSACT)
command, which is part of the Performance Tools/400 licensed program, can be
used to display the CPU usage and priority of SLIC tasks.
The priority of the SLIC task that is emulating the System/36 instructions and the
storage pool used by all AS/400 Advanced 36 SLIC tasks are set based on the
priority and storage pool of the AS/400 Advanced 36 Server job. If the server job is
defined to run at priority 20, the SLIC task emulating the System/36 instructions for
the AS/400 Advanced 36 machine will also run around priority 20. If the server job
is running in the *BASE storage pool, the SLIC tasks will bring data into the *BASE
storage pool.

Performance
Setting Attributes for the AS/400 Advanced 36 Prestart Jobs

The AS/400 Advanced 36 prestart jobs are used by an AS/400 Advanced 36
machine to run certain requests for the SSP operating system. For example, when
the RUN400 OCL statement is processed from a display that is assigned to SSP
(For example, the user does not have to sign on to OS/400 before signing on to the
SSP), the OS/400 request in the RUN400 OCL statement is run in an AS/400
Advanced 36 prestart job.
In the QSYSWRK subsystem there are three prestart job entries for AS/400
Advanced 36 processing:
QNURHHGH
QNURHMED
QNURHLOW
The priority of the request from the SSP job determines which routing entry is used
for the request. For example, if the priority of the SSP job is set to HIGH with the
ATTR OCL statement, the QNURHHGH entry will be used for the request.
QNURHMED is defined for normal SSP priority requests. QMHRHLOW is defined
for low priority requests.
You can use the Change Prestart Job Entry (CHGPJE) command to set the job
description, the storage pool and the class used for the request. The class defines
the priority for the request. Prestart job entry QNURHHGH defaults to class
QSYSCLS10 (priority 10). QNURHMED defaults to class QSYSCLS20 (priority 20).
QNURHLOW defaults to QSYSCLS50 (priority 50).
Changing the Priority and Storage Pool for an AS/400 Advanced

36 Prestart Job— Example
The following steps can be used to change the priority of the low priority jobs from
priority 50 and storage pool 1 to priority 40 storage pool 2.
1. Use the Create Class (CRTCLS) command to create a new class specifying
priority 40.
CRTCLS CLS(M36/NEWLOWPRTY) RUNPTY(4ð)
b. Press Enter.
2. Use the Change Prestart Job Entry (CHGPJE) command to change the
QNURHLOW prestart job entry specifying the new class and storage pool 2.
CHGPJE SBSD(QSYSWRK) PGM(QM36/QNURHLOW)
POOLID(2) CLS(M36/NEWLOWPRTY)
b. Press Enter.

Performance
Notes:
1. There is a user profile value on the prestart job entry. This is the default user
profile that is used if the request for the prestart job does not specify a user
profile. All SSP requests for the AS/400 Advanced 36 server job specify a user
profile so the value you specify in the prestart job entry is not used when deter-
mining if a job has the proper security authorization for a function.
2. In addition to changing the storage pool and class for a prestart job, you can
also use the Change Prestart Job Entry CL command to change the initial,
additional and total number of prestart job. For more information about
changing these parameters, see the Work Management book, SC41-4306.
3. The changes specified with the Change Prestart Job Entry command will be in
effect for any new prestarted jobs that are created. The Change Prestart Job
Entry command will not change any prestart jobs that are already active.
Changing the AS/400 Advanced 36 Prestart Job to Immediately

Use Changed Values — Example
You can use the following steps to cause all AS/400 Advanced 36 prestart jobs to
immediately use any changed values.
1. Stop all AS/400 Advanced 36 machines.
For directions, see Chapter 16, “Stopping an AS/400 Advanced 36 Machine”
on page 16-1.
2. Check to be sure the AS/400 Advanced 36 machines are all stopped.
WRKM36 \ALL/\ALL
b. Press Enter.
The Work with M36 Machines display appears. Wait until all machines are
inactive before proceeding with the next step. Inactive machines have a
status of Incomplete, Damaged, Ended or Abended.
Note: You will need to press F5 periodically to refresh the Status column.
c. End prestart jobs that run under the QSYSWRK subsystem for the benefit
of AS/400 Advanced 36 server jobs.
Note: These prestart jobs restart when any AS/400 Advanced 36 machine
is started.
1) On an OS/400 command line, type
ENDPJ SBS(QSYSWRK) PGM(QM36/QNURHHGH) OPTION(\IMMED)
2) Press Enter.
ENDPJ SBS(QSYSWRK) PGM(QM36/QNURHLOW) OPTION(\IMMED)
4) Press Enter.
ENDPJ SBS(QSYSWRK) PGM(QM36/QNURHMED) OPTION(\IMMED)
6) Press Enter.
As each set of prestart jobs (QNURHHGH, QNURHLOW and QNURHMED)
ends, a copy of the completion message CPC0905 will be logged in the

Performance
QSYSOPR message queue. For information on how to check messages in

the QSYSOPR message queue, see “Displaying OS/400 System Operator
Messages” on page 5-7.
Once these prestart jobs have ended, the new values for the prestarted
jobs will be used for any AS/400 Advanced 36 machines that you start.

Using Electronic Customer Support
Appendix D. Using Electronic Customer Support

OS/400 has an integrated set of functions that are designed to help service your
system. These functions are contained in what is referred to as Electronic Cus-
tomer Support. Electronic Customer Support allows you to:
Report problems
Review status of an open problem
Order PTFs
Your access to these functions is subject to the terms and conditions of service
contracts that you have with IBM (for example, warranty or maintenance agree-
ments).
| For hardware requirements and software setup directions, see Appendix D of the
Fastpath Installation of Your Advanced 36 book, SA41-4138.
Reporting a Problem
For hardware failures that do not disable system operations, Electronic Customer
Support provides a fast, electronic method for requesting the service of an IBM
service representative. Using Electronic Customer Support, you may report failures
on your system and selected input or output devices.
For software or Licensed Internal Code problems, notification of the failure and
related symptoms can be sent to the IBM service system. A file of known problems
is searched and, if available, a program temporary fix (PTF) is sent to your system
for installation.
If the reported problem is new, a problem management record (PMR) is created by

the IBM service system. The PMR number is returned to your system through
Electronic Customer Support. IBM service personnel, using the problem manage-
ment record, respond to your reported problem.
System Detected Problems

The system problem log allows you to display a list of the problems that were
recorded on your system. You can also display detailed information about a spe-
cific problem, such as:
The product type and serial number of the device that had the problem
The date and time of the problem
The hardware part or software program that failed
Where the hardware part is found
The problem status
To report a problem which has an entry created in the problem log:

WRKPRB
2. Press Enter.
 Copyright IBM Corp. 1995, 1996 D-1

3. In the OPT field beside the problem you want to work with, type
8
4. Press Enter.
2
to select Report problem.
6. Press Enter.
The Verify Contact Information display appears.
7. Make any changes you want to make (if any).
8. Press Enter to accept the information.
9. Select a problem severity level that closely relates to the severity of your
problem.
10. Select who should receive and process your service request.
11. Select when and how you want to send the service request.
12. Press Enter.
Note: If you want to permanently change the contact information, you would use
the WRKCNTINF command.
Putting User-Detected Problems in the Problem Log

A user-detected problem is one that has not automatically recorded in the problem
log. To analyze a user-detected problem:
ANZPRB
2. Press Enter.
3. Select the options that most closely describe your problem. As you progress
through problem analysis, a symptom string is being built based on your
responses.
4. When you complete problem analysis, the collected information is placed in the
problem log.
5. Go to step 1 on page D-1 and follow the same steps as you would to report a
system detected problem.
What Happens After Submitting a Problem Through Electronic

Customer Support
Reporting a problem to the IBM product support center results in a problem record
being opened in the IBM problem management system. Electronic Customer
Support, using information contained in this newly created problem record,
searches a database of known problems. Known problem fixes are either sent
electronically (if size permits) or an order for the PTF is placed. Unknown problems
or problems without a fix are routed to the product support center. The product
support center, using information contained within the problem record, investigates
the problem. If the problem is with the software, the center provides feedback
within the problem record. If the problem is with the hardware, the center responds
with a call or they dispatch a service representative.
D-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Reviewing Status of an Open Problem

To review text added to the problem record by the product support center during its
investigation of a software problem:
WRKPRB
2. Press Enter.
3. In the OPT field, beside the problem you want to work with, type
8
4. Press Enter.
The Work with Problems display appears.
5. Check the Problem Description column for the status of the problem you want
to check.
Note: Status of problems that have Fix request specified cannot be
obtained.
6. If the status of the problem is Answered or Sent, start the query as follows:
a. In the Option field next to the query problem status text, type
41
b. Press Enter.
Electronic Customer Support establishes a connection and the results are
displayed.
Ordering PTFs
One of the more popular functions of Electronic Customer Support is the electronic
ordering and delivery of PTFs.
Corrective PTFs
– Delivered electronically if size permits
– Delivered on CD-ROM if size is too big (In this case, Electronic Customer
Support places the order for you.)
Latest cumulative PTF preventive service package
– Electronic Customer Support places the order to deliver on CD-ROM
Preventive service information
– Delivered electronically
The following table shows how to use the SNDPTFORD command to order PTFs
and PTF information.
Figure D-1 (Page 1 of 2). How to Use the SNDPTFORD Command to Order PTFs and PTF Information
PTF Information Command
Specific PTFs and cover letters SNDPTFORD nnnnnnn .1/
PTF cover letter only SNDPTFORD nnnnnnn .1/
PTFPART(*CVRLTR)
Appendix D. Using Electronic Customer Support D-3

Figure D-1 (Page 2 of 2). How to Use the SNDPTFORD Command to Order PTFs and PTF Information
PTF Information Command
Cumulative PTF package SNDPTFORD SF99vrm .2/
PSP Information:
OS/400, SSP and LPPs SNDPTFORD SF98vrm .2/
Licensed Internal Code SNDPTFORD MF98vrm .2/
PTF Summary List SNDPTFORD SF97vrm .2/
Notes:
1. The nnnnnnn by the .1/ is the PTF identifier. You can order up to 20 PTFs at a
time.
2. The vrm by the .2/ is 360 for version 3 release 6. The v is for version. The r
is for release. The m is for the modification level of the system.
For more information about Electronic Customer Support, see the CL Reference
book, SC41-4722.
D-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Appendix E. Preparing SSP for Dedicated State

Note: While you are performing the following steps, you will be asked to switch
back and forth between the command display and the console display of the
display station designated as the SSP system console. The console display
has CONSOLE in the upper right corner. The command display has a line
that says Ready for option number or command.
For information on switching between the command display and the console
display, see “Using the Console display” in the Operating Your
By performing the following steps, you can ensure the AS/400 Advanced 36
machine can be put in a dedicated state.
1. Sending a message to all users
You should inform all users you are going to put the system in dedicated state
and ask them to sign off. This can be done using the MSG control command.
a. On the command display of the display station designated as the system
console, type
MSG ALL,SYSTEM BEING PLACED IN DEDICATED STATE, PLEASE SIGN OFF NOW
b. Press Enter.
c. Review any replies sent by the users. A critical job may need to be com-
pleted before you stop the system. After answering all replies, continue
with the preparation.
2. Verify all users have signed off.
console, type
STATUS WORKSTN (or D W)
b. Press Enter.
This control command allows you to see if anyone else is using the system.
If users are still signed on, you can use the MSG control command again to
send a message to the user. You can also use option 9 (Cancel a session)
on the DEVICES menu to sign off the user.
c. Press Cmd3 to end the display.
d. If you used option 9 to sign users off the system, press Cmd3 again.
3. Verify no jobs are running on the job queue.
console, type
STATUS JOBQ (or D J)
b. Press Enter.
This control command allows you to see if any batch jobs are running. If
the job queue is started, use option 7 (Stop the job queue) on the
JOBQUEUE menu to stop any more jobs from starting. If there are batch
jobs running, use the options on the JOBQUEUE menu to display, change
or cancel these jobs.
 Copyright IBM Corp. 1995, 1996 E-1


d. If you used any of the options on the JOBQUEUE menu, press Cmd3
again to return to the JOBQUEUE menu.
4. Verify no spool writers are active.
console, type
STATUS WRT (or D WRT)
b. Press Enter.
This control command allows you to see if any spool writers are active. If
there are spool writers active, use option 4 (Stop spool writer) on the
SPOOL menu to stop all spool writers.
d. If you used option 4 to stop all spool writers, press Cmd3 again.
5. Verify no communications subsystems are active.
console, type
STATUS SUBSYS (or D I)
b. Press Enter.
This control command allows you to see if any communications subsystems
are active. If there are communications subsystems active, use option 2
(Stop a subsystem) on the CNTLLINE menu to stop each active sub-
system.
d. If you used option 2 to stop each active subsystem, press Cmd3 again.
6. Verify Object Distribution Facility (ODF) tasks are not active.
a. On the command display of the display station designated as the SSP
system console, type
STATUS SYSTASK (or D T)
b. Press Enter.
This control command displays the active tasks. In the DESCRIPTION
field, look for any of the following tasks:
00AD-ODF LOGF
00A5-ODF LOCK
00A9-ODF QMGR
If none of these tasks were found, go to step 6e.
c. On the command line under the SYSACT menu, type
ODFCANCL
d. Press Enter.
This procedure cancels all the ODF tasks.
e. Press Cmd3 to end the display.
7. Verify Personal Services/36 jobs are not active.
E-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5


console, type
STATUS USERS (or D U)
b. Press Enter.
This control command displays the user jobs that are active. In the PROC
and PROGRAM fields, look for any of the following:
PROC PROGRAM
#cb003 #OUBR
#cb001 #OUSV
OSULOCK #OUXI
OFCC001 #ODQY
OFCSTART #OUQS
If none of these Personal Services/36 jobs were found, go to step 7f.
c. On the command line under the JOBS menu, type
OFCCANCL
d. Press Enter.
This procedure will cancel all the Personal Services/36 jobs.
e. If there are other user jobs active, use option 5 (Cancel a job) on the JOBS
menu to cancel each of these jobs.
f. Press Cmd3 to end the display.
g. If you used option 5 to cancel jobs, press Cmd3 again.
8. Reply to all messages on the system console.
a. On the console display of the display station designated as the SSP system
console, type
REPLY I (or R I)
b. Press Enter.
c. On the console display of the display station designated as the system
console, type
REPLY C (or R C)
d. Press Enter.
e. Reply to any remaining messages on the system console. See “Replying
to messages at the Console or Subconsole” in the Operating Your
9. Check for other activity on the system.
console, type
STATUS SYSTASK (or D T)
b. Press Enter.
This control command allows you to see if there is any other activity on
your system. The only tasks that should be active are:
Command Processor (Cmd Proc)
Error Recovery (Err Recov)
Appendix E. Preparing SSP for Dedicated State E-3

The following tasks may also be active:

– Autocall
– Gaiji
– Remote Work Station (RWS)
If there are tasks active other than those mentioned above, the task was
started after you started putting the system in dedicated state or you
skipped one of the previous steps. Perform step 9c and start over with
step 2 on page E-1.
10. Completing the dedication of the system.
a. On the console display of the display station designated as the SSP system
console, type
STOP SYSTEM (or P S)
b. 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 system
console:
SYS-5677 STOP SYSTEM command has completed
c. If the SYS-5677 message is not shown, type
START SYSTEM (or S S)
on the system console display.
d. Press Enter.
e. Go to step 2 on page E-1 and repeat all the steps again.
If Message SYS-5677 message is shown at this time, you have prepared
the system for being placed in dedicated state.
11. Return to the task that sent you here.
E-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Bibliography
You may need to refer to other IBM manuals for more S/36 3270 Device Emulation Guide, SC21-7912,
specific information about a particular topic. The fol- which has information about configuring and using
lowing IBM AS/400 manuals contain information that 3270 device emulation.
you may need.
For information about personal computers:
SSP Related Information S/36 PC Support/36 User’s Guide, SC21-9088,

which describes how to use PC Support/36 with an
For general information about SSP: IBM Personal Computer attached to an IBM AS/400
Advanced 36.
General Information for SSP Operating System,
SC21-8299, which includes the concepts you need S/36 PC Support/36 Technical Reference,
for using an AS/400 Advanced 36 machine. SC21-9097, which describes how to install PC
Support/36
Information Directory, SC21-8292, which includes a
list of the 9402 Model 236 publications. S/36 PC Support/36 Workstation Feature User’s
Guide, SC21-9695, which describes how to use the
Planning Information – Advanced 36, SA21-9638. work station feature.
This manual contains a planning guide and a set of
forms in addition to information on planning the S/36 PC Support/36 Workstation Feature Technical
installation of the 9402 Model 236. Reference, SC21-9569, which describes how to
tailor the work station feature.
Advanced 36 Installation, SA21-8290. This manual
describes the steps for setting up and checking out 3278 Emulation via IBM Personal Computer User's
9402 Model 236. Guide, SC09-1086, which describes how to con-
figure and use 3278/9 device emulation.
Performing the First System Configuration for Your
System–SSP, SC21-8298. This manual describes Enhanced 5250 Emulation Program Version 2.1
the steps for completing the first system configura- User's Guide, which describes how to use the emu-
tion for a 9402 Model 236. lation program with an IBM Personal Computer
attached to your AS/400 Advanced 36.
Using Your Display Station – Advanced 36,
SC21-0209, which describes how to use a 9402 Enhanced 5250 Emulation Program Version 2.1
Model 236 display station. Technical Reference Manual, which describes how
to customize the emulation program for an IBM Per-
Operating Your Computer–SSP Operating System, sonal Computer attached to your AS/400 Advanced
SC21-8297. This manual describes how to operate 36.
and manage a 9402 Model 236 after completing the
system configuration process. For information about programming:
S/36 System Security Guide, SC21-9042, which S/36 Data File Utility (DFU) Guide, SC21-7900,
describes system security procedures. which describes the Data File Utility of the utilities
S/36 System Reference, SC21-9020, which program product.
describes the procedures used for some of the S/36 Work Station Utility (WSU) Introduction,
tasks in this manual. SC21-7904, which introduces the Work Station
S/36 System Messages, SC21-7938, which Utility of the utilities program product.
describes the error messages that could occur while S/36 Source Entry Utility (SEU) Guide, SC21-7901,
doing some of the tasks. which describes the Source Entry Utility of the utili-
System Messages–SSP Addendum, SC21-8291, ties program product.
which describes the new error messages that could S/36 Business Graphic Utilities/36 User’s Guide,
occur while using the 9402 Model 236 SC21-7985, which describes how to use the Busi-
S/36 Procedures and Commands Summary, ness Graphics Utilities/36 to create business graphs
SC21-9024, which summarizes System/36 proce- and charts.
dures, control commands, operation control lan- S/36 Development Support Utility Guide,
guage statements, and procedure control SC09-1085, which describes the Development
expressions. Support Utility.
 Copyright IBM Corp. 1995, 1996 H-1

S/36 Creating Displays: Screen Design Aid (SDA) S/36 Advanced Peer-to-Peer Networking (APPN)
and SSP, SC21-7902, which describes the Screen Guide, SC21-9471, which describes the extended
Design Aid of the utilities program product. networking capabilities of APPC.
S/36 Character Graphic Utility Guide (Japan only),
For information about office support:
SC09-1055, which describes the ideographic Char-
acter Generator Utility (CGU). System/36 in the Office, GC21-8002, which gives
an overview of the capabilities of the OFFICE/36
S/36 Ideographic Sort Guide (Japan only),
program products and how they relate to each
SC09-1054, which describes the Ideographic (IGC)
other.
Sort Utility.
S/36 Getting Started with DisplayWrite/36,
For information about communications: SC21-8005, which describes DisplayWrite/36, an
OFFICE/36 Program Product.
S/36 Using System/36 Communications,
SC21-9082, which explains communications capa- S/36 Getting Started with Personal Services/36,
bilities. SC09-1061, which describes Personal Services/36,
an OFFICE/36 Program Product.
S/36 Distributed Data Management Guide,
SC21-8011, which describes DDM, a communica- S/36 Administering Personal Services/36 in the
tions feature of the SSP. Office, SC09-1062, which describes how to install
and tailor the Personal Services/36 program
S/36 Using the Asynchronous Communications
product.
Support, SC21-9143, which contains information
about the Asynchronous subsystem, the Interactive S/36 Getting Started with Query/36, SC21-8004,
Terminal Facility, and the file transfer subroutines. which describes Query/36, an OFFICE/36 Program
Product.
S/36 SSP-ICF Programming for Subsystems and
Intra Subsystem Reference, SC21-9533, which S/36 Getting Started with IDDU, SC21-8003, which
describes the Interactive Communications Feature describes IDDU, an option of the SSP.
(SSP-ICF), provides information for programming
SSP-ICF subsystems with Assembler, BASIC,
COBOL, and RPG II languages, and describes the OS/400 Related Information
subsystem.
For information not covered in this book on starting the
S/36 SSP-ICF Upline Subsystems Reference, system unit and handling problems:
SC21-9532, which describes the customer informa-
System Startup and Problem Handling, SC41-4206.
tion control system (CICS), information manage-
ment system (IMS), and SNA upline facility (SNUF)
For information about planning, installation, and
subsystems of the ICF.
migration:
S/36 SSP-ICF Finance Subsystems Reference,
Local Device Configuration, SC41-4121, provides
SC21-9531, which describes the finance subsystem information about how to do an initial configuration
of the ICF.
and how to change that configuration. It also con-
S/36 SSP-ICF Guide and Examples, SC21-7911, tains conceptual information about device configura-
which describes how to perform subsystem config- tion.
uration for the Interactive Communications Feature.
Software Installation, SC41-4120, provides step-by-
S/36 Multiple Session Remote Job Entry Guide, step procedures for initial install, installing licensed
SC21-7909, which describes MSRJE, a feature of programs, program temporary fixes (PTFs), and
the SSP. secondary languages from IBM.
S/36 3270 Device Emulation Guide, SC21-7912, ASCII Work Station Reference, SA41-3130, pro-
which describes BSC and SNA 3270 Device Emu- vides information on how to use ASCII work stations
lation, a feature of the SSP. attached to the AS/400 system. It describes how to
adjust the settings of ASCII work stations and pro-
S/36 Distributed Disk File Facility Reference
vides information on keyboard mappings and char-
Manual, SC21-7869, which describes DDFF, a
acter code mappings.
feature of the SSP.
This manual also describes the process of ASCII
S/36 Communications and Systems Management
device setup and provides examples about ASCII
Guide, SC21-8010, which describes the change
device setting adjustments. It also contains infor-
management, remote management, and alert func-
mation on special considerations for personal com-
tions of C & SM, a feature of the SSP.
puter setting adjustments, and auxiliary printer
setting adjustments.
H-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

For information about system use: gather data to determine who is using the system
and what resources are being used.
Getting Started with AS/400, SC41-4204, is for new
or novice AS/400 users to help them get started on System Manager Use, SC41-3321, provides infor-
the AS/400 system. The booklet shows how to mation about the commands and functions available
perform simple tasks on the system in a short time when the SystemView System Manager/400
(2 or 3 hours) and introduces them to key functions licensed program is installed on one or more
on the AS/400. AS/400 systems in a network. This manual also
provides setup procedures and information for main-
System Operation for New Users, SC41-3200, pro-
taining a network of AS/400 systems.
vides beginner information about how to sign on
and off; send and receive messages; respond to Performance Tools/400, SC41-4340, provides infor-
keyboard error messages; use function keys; use mation about what Performance Tools/400 are,
display, command, and help information; and control gives an overview of the tools, and tells how the
and manage jobs. tools can be used to help manage system perfor-
mance. The manual gives instructions on how to
System Operation, SC41-4203, provides information
approach the analysis of system performance and
about handling messages, working with jobs and
how to do system performance measurement,
printer output, devices communications, working
reporting, capacity planning, and application anal-
with support functions, cleaning up your system,
ysis. This manual also includes information about
and so on.
additional functions and related commands for
Managing OfficeVision/400, SH21-0699, provides further analysis. provides information on AS/400
information on how to manage the day-to-day activ- Performance Tools and how they can help manage
ities of OfficeVision. It also includes information on system performance.
maintaining office enrollment and creating and man-
aging office objects. For more information about communications and
connectivity:
Q & A Database Coordinator's Guide, SC41-8088,
describes how to use Question-and-Answer (Q & A) SNA Distribution Services, SC41-3410, provides
to search through questions and answers stored in information about administering data communica-
a Q & A database on the system. This manual also tions applications on an AS/400 system.
includes information about creating a Q & A data-
Communications Management, SC41-3406, pro-
base.
vides information on how to start, stop, verify, and
test communications, handle communications
For information about system management
errors, and work with communications status.
Security – Basic, SC41-4301, explains why security
Communications Configuration, SC41-3401, pro-
is necessary, defines major concepts, and provides
vides information on how to configure the commu-
information on planning, implementing, and moni-
nications functions available with the OS/400
toring basic security on the AS/400 system.
licensed program, including detailed descriptions of
Backup and Recovery – Basic, SC41-4304, con- network interface, line, controller, device, mode, and
tains information about planning a backup and class-of-service descriptions; configuration lists; and
recovery strategy, the different types of media avail- connection lists.
able to save and restore system data, save and
restore procedures, and disk recovery procedures. For information about program enablers
It also describes how to install the system again
Printer Device Programming, SC41-4713, provides
from backup.
information on printing elements and concepts of
Backup and Recovery – Advanced, SC41-4305, the AS/400 system, printer file and print spooling
describes how to plan for and set up user auxiliary support for printing operation, and printer
storage pools (ASPs), mirrored protection, and connectivity.
checksums, along with other availability recovery
System/36 Environment Programming, SC41-4730,
topics. It also provides information about journaling
provides information identifying the differences in
and save-while-active.
the applications process in the System/36 environ-
Work Management, SC41-4306, provides informa- ment on the AS/400 system. It helps the user
tion about how to create and change a work man- understand the functional and operational differ-
agement environment. Other topics include a ences (from a System/36 perspective) when pro-
description of tuning the system, collecting perfor- cessing in the System/36 environment on the
mance data including information on record formats AS/400 system. This includes an environment func-
and contents of the data being collected, working tional overview, considerations for migration, pro-
with system values to control or change the overall gramming, communications, security, and
operation of the system, and a description of how to coexistence.
Bibliography H-3
System/36 Environment Reference, SC41-4731, System API Reference, SC41-4801, provides infor-
provides information about using System/36 proce- mation on how to create, use, and delete objects
dure control expressions, procedures, operation that help manage system performance, use
control language (OCL) statements, control com- spooling efficiently, and maintain database files effi-
mands, and utilities on the AS/400 system. ciently. This manual also includes information on
creating and maintaining the programs for system
For information about program interfaces: objects and retrieving OS/400 information by
working with objects, database files, jobs, and
spooling.
H-4 AS/400 Operator Tasks – Multiple Operating Systems R7.5

Index
AFP (Advanced Function Printing)
Special Characters See Printer Device Programming
*NULL 22-3 ALCOBJ 28-1
user ID 22-3 ALRCTLD 11-5
*QUTQ special value alternative SSP console 17-1
to direct printer output to output queue 31-32 becomes SSP console 17-2
making into SSP console 17-3
transferring function to 17-3
A ANSLIN 11-7
abnormal end message
answering
definition 5-5
call
accessing
communications line 11-7
Operational Assistant 6-3
manually 11-7
activating
outside United States 11-7
ANZPRB 13-1
controller 11-4
APPC 22-2
device 11-1
APYM36CFG parameter
diskette device 11-1
using 15-3
display device 11-1
AS/400 Advanced 36
printer device 11-1
prestart jobs
tape device 11-1
setting attributes C-6
active job
server job C-1
changing 10-16, 10-17
activity log, product
SLIC Tasks
hardware problems 28-1
Add Job Queue Entry (ADDJOBQE)
AS/400 Advanced 36 machine
command 10-12
adding to configuration
adding
communications line or a LAN 31-4
by using controller mapping
printers 31-17
display station 31-12
workstations 31-17
printer 31-12
CD-ROM device 31-10
tape or CD-ROM device 31-10
workstation controller 31-17
changing
job queue entry 10-12
attributes 30-3, 30-10
job schedule entry 10-4
configuration description 30-13
local area network (LAN) 31-4
configuration details 30-10
tape 31-10
description of 30-6
using device mapping
changing configuration
printers 31-12
communications line or a LAN 31-4
workstations 31-12
ADDJOBQE (Add Job Queue Entry)
display station 31-12
command 10-12
printer 31-12
address
printing local device 11-3
Advanced 36 procedure
changing from
running
controller mapping to device mapping 31-22
example 14-7
configuration object
starting 14-6
saving 25-1
advanced assistance level 6-3
creating another 30-2, 30-9
Advanced Function Printing (AFP)
defining
See Printer Device Programming
whether SSP or OS/400 controls SSP printer
output 31-26
 Copyright IBM Corp. 1995, 1996 X-1

AS/400 Advanced 36 machine (continued) AS/400 and System/36 command
defining (continued) cross-reference A-1
whether SSP or OS/400 controls the display AS/400 system
station 31-36 See system
deleting 30-4 ASSIGN 20-8
configuration 30-11 assigning
display stations 31-36 job to a different output queue 10-18
displaying 30-4 printer output
configuration 30-11, 32-1 to a different printer 7-8
information 32-2 to a printer 7-9
dump 16-3 system printer 20-8
ending 30-7 assistance level
handling error codes 28-9 advanced 6-3
library basic 6-3
restoring 25-1, 25-2 changing 6-4
saving 25-1 changing in user profile 6-7
object changing temporarily 6-4
saving 25-1 definition 6-3
operations intermediate 6-3
management 30-1 using 6-3
printer output 31-26 attended IPL
printing changing B-3
AS/400 Advanced 36 machine configuration infor- setting B-3
mation 30-5 authority
configuration 30-12 working with other user jobs 10-6
putting in dedicated state 16-1 automatic
removing from configuration signon to an AS/400 Advanced 36 machine 14-5
communications line or a LAN 31-4 automatic startup, disabling 29-7
diskette device 31-8 automatically
display station 31-12 starting AS/400 Advanced 36 machine 15-5
printer 31-12 automatically starting ILAN subsystem 29-6
renaming 30-5 B
configuration 30-12 badge security 22-2
restoring 12-6, 25-1, 25-2 general description 22-2
library 25-2 magnetic stripe reader 22-2
saving 12-4, 25-1 balancing
starting 10-5, 15-1, 30-6 spooled output
automatically 15-5 using procedure 20-6
stopping 16-1 BALPRINT 20-6
from SSP system console 16-2 basic assistance level 6-3
summary of CL commands 30-13 batch job 10-9
transferring procedure to 14-6 definition 10-1
STRM36PRC 14-6 deleting printer output 10-9
transferring to 14-1, 14-3, 14-7, 30-7 displaying
transferring to with automatic sign-on 14-5 all 10-6
AS/400 Advanced 36 Program by status 10-7
corrective service SSP PTFs 26-2 other user 10-6
installing cumulative SSP PTF packages 26-5 ending 10-9
maintenance strategy holding
corrective service 26-1, 26-2 method 10-8
cumulative PTF package 26-1 printer output 10-8
preventative service 26-1, 26-2 printing a job log for 10-19
ordering releasing 10-9
SSP PTF information 26-3 scheduling 10-2, 10-4
SSP PTFs 26-3
X-2 AS/400 Operator Tasks – Multiple Operating Systems R7.5

batch job (continued) changing (continued)
scheduling to start an AS/400 Advanced 36 display device (continued)
machine 10-5 status 11-1
submit to run immediately 10-2 form type for printer output 7-9
viewing 10-6 IPL mode B-3
working with 10-1, 10-5 job
blinking 4-digit number 18-1, 18-11 how run 10-16
blinking 4-digit number and input inhibited light on print priority 10-18
keyboard message 18-11 priority on a job queue 10-16
break message job description
handling 5-7 caution notice 10-20
sending 5-17 job schedule entry 10-5
level, assistance 6-4
logging level for job 10-20
C message queue 5-12
calendar name
saving 12-4 diskette device 11-2
call stack display device 11-2
displaying 10-15 printer device 11-2
calling tape device 11-2
manual dial 11-6 password 9-2
CANCEL PRT 20-5 printer attributes 31-27
caution notice printer device
changing job description 10-20 forms 7-13
CD-ROM device name 11-2
adding 31-10 status 11-1
deleting 31-10 printer file 10-21
replacing 31-10 printer options 20-8
CD-ROM drive printer output
changing to tape cartridge drive 26-17 copies 7-8
installing corrective SSP PTFs 26-5 using Control Command 20-4
mapping devices to it 26-16 using display option 20-4
changed object using menu option 20-4
saving in a library 12-4 QAUTOVRT value 29-15
changed objects spooled file
restoring 12-6 priority 10-18
changing status
active job 10-17 device 10-18
AS/400 Advanced 36 machine display device 10-18
attributes 30-10 printer device 10-18
configuration 30-13 tape unit 10-18
configuration details 30-10 tape device
assistance level 6-4 name 11-2
assistance level temporarily 6-4 status 11-1
attributes for AS/400 Advanced 36 machine 30-3 temporary password 9-2
CD-ROM drive to tape cartridge drive 26-17 to a command display 17-4
configuration 31-1 workstation attributes 31-27
description of AS/400 Advanced 36 machine 30-6 changing configuration
device for an AS/400 Advanced 36 machine 15-5
description 11-3 that starts automatically 15-5
name 11-2 checklist
status 11-1 electronic PTF installation 26-9
diskette device CHGCTLAPPC 29-7
name 11-2 CHGJOB 10-15, 10-16
status 11-1 CHGJOBD 10-20
display device
name 11-2
Index X-3
CHGM36 14-5, 30-3, 30-13 CL command (continued)
CHGM36CFG 30-10, 30-13, 31-4, 31-8, 31-10, 31-12, STRREXPRC 10-2
31-18, 31-22, 31-27, 31-30, 31-32, 31-36, C-4 summary for managing AS/400 Advanced 36
CHGMSGQ 5-12 machines 30-13
CHGNETA 11-5 TFRM36 14-1, 14-3, 30-14
CHGPRTF 10-21 VRYCFG 29-4, 29-8, 29-9, 29-14
CHGSYSVAL 29-15 Work with AS/400 Advanced 36 Machine Configura-
CL command tion (WRKM36CFG) Command 30-15
ADDJOBQE 10-12 WRKCFGSTS 28-8
ALCOBJ 28-1 WRKJOBQ 10-10
ALRCTLD 11-5 WRKJOBSCDE 10-3
ANSLIN 11-7 WRKM36 30-1, 30-14
ANZPRB 13-1 WRKM36CFG 30-8
CHGCTLAPPC 29-7 WRKMSG 5-2
CHGJOB 10-15, 10-16 WRKOBJLCK 28-8
CHGJOBD 10-20 WRKPRB 5-15, 13-1, D-1, D-3
CHGM36 14-5, 30-3, 30-13 WRKSPLF 7-13
CHGM36CFG 30-10, 30-13, 31-4, 31-8, 31-10, WRKUSRJOB 10-5, 10-12, 10-13
31-12, 31-18, 31-22, 31-27, 31-30, 31-32, 31-36 WRKWTR 7-10
CHGMSGQ 5-12 clearing
CHGNETA 11-5 messages from a display
CHGPRTF 10-21 SSP console 18-6
CHGSYSVAL 29-15 subconsole 18-6
CRTDUPOBJ 10-12 code, system reference 18-4
CRTM36 30-2, 30-13 command 3-2
CRTM36CFG 30-9, 30-14 GO POWER 3-2
DLTM36 30-4, 30-14 PWRDWNSYS 3-3
DLTM36CFG 30-14 using help 19-1, 19-4
DSPJOBLOG 10-19 using the help key 19-1, 19-4
DSPM36 30-14, 32-1, 32-2 WRKOUTQ 7-14
DSPM36CFG 30-14, 32-1 command cross-reference
DSPMSG 5-2, 11-7, 29-13 System/36 and AS/400 A-1
DSPNETA 11-5, 26-7, 29-8 command display stations 17-1
ENDM36 16-3, 30-14 command display, returning to 17-4
GO 3-2, 6-2, 6-8, 6-9, 7-3, 9-2, 10-5, 11-3, 11-5, command summary
12-1 managing printer output 20-3
overview 6-1 communications
RSTAUT 12-7 answering from outside United States 11-7
RSTCFG 12-6 automatically starting
RSTCHGOBJ 12-6 ILAN 29-6
RSTDLO 12-6 ILAN for OS/400 29-6
RSTLIB 12-6, 25-2 ILAN for SSP 29-6
RSTOBJ 12-7, 25-2 controllers
RSTUSRPRF 12-7 activating 11-4
SAVCFG 12-2 determining
SAVCHGOBJ 12-4 why ILAN is inactive 29-13
SAVDLO 12-4 why ILAN is varied off 29-13
SAVLIB 12-4, 25-1 ILAN system-to-system 29-1
SAVOBJ 12-5 link
SAVSECDTA 12-2 establishing 27-1
SAVSTG 12-3 establishing for problem determination 27-1
SAVSYS 12-2 establishing for remote work station support 27-1
SBMJOB 10-2 manual
STRM36 15-1, 30-14 answer 11-7
STRM36PRC 14-1, 14-6, 14-7, 30-14 dial 11-6
STRPASTHR 29-15 manually starting ILAN 29-3, 29-4, 29-5
OS/400 side 29-3

communications (continued) control command
manually starting ILAN (continued) CONSOLE GIVE 17-3
SSP side, all connections 29-4 CONSOLE TAKE 17-3
SSP side, one connection 29-5 CONSOLE, SSP 17-2
problem determination 27-1 INFOMSG 18-5
setting up ILAN 29-3 REPLY 18-7
switched line 11-6 using
using 27-1 help 19-4
verifying ILAN 29-10 help key 19-1, 19-4
working with OS/400 11-1 to change printer output 20-4
Communications Configuration menu to hold printer output 20-4
displaying 11-5 to release printer output 20-4
communications line to restart spool writer 20-7
activating 11-4 to start spool writer 20-6
adding 31-4 VARY 27-1, 27-2
answering 11-7 control panel 1-2
deleting 31-4 opening cover 1-1
replacing 31-4 system unit 1-1
switched 11-6 control point name
communications security 22-2 determining 29-8
general description 22-2 finding 29-8
comparing controller
print commands 7-15 activating communications 11-4
System/36 to OS/400 7-15 controlling
configuration device 11-1
See also Local Device Configuration job 10-1
after installation 31-2 SSP jobs 23-1
after OS/400 added to SSP-only system 31-2 copies
changing 31-1 changing number of printer output 7-8
displaying 32-1 copying
error 31-39 printer output
for OS/400 and SSP preloaded system 31-3 using menu option 20-5
status 11-1 using procedure 20-5
warning 31-39 COPYPRT 20-5
configuration object corrective service
restoring definition 13-1
AS/400 Advanced 36 machine 25-2 CPFACE0 28-9
saving 12-4 creating
configuring another AS/400 Advanced 36 machine 30-2, 30-9
remote communications 11-5 customized 10-12
OS/400 11-5 WRKUSRJOB command 10-12
console 4-1 IPL start-up program 15-5
OS/400 4-1 procedure for restoring other SSP system
requesting help menu 17-5 files 25-35
SSP 17-1 procedure to restore licensed program
system 4-1 products 25-27
CONSOLE control command, SSP 17-2 QSYSMSG 5-14
console display CRTDUPOBJ 10-12
requesting 17-4 CRTM36 30-2, 30-13
requesting a help menu 17-4 CRTM36CFG 30-9, 30-14
SSP 17-4 cumulative PTF package
using 17-4 content 13-1
CONSOLE GIVE control command 17-3 definition 13-1
console roll area 18-7 ordering 13-1
CONSOLE TAKE control command 17-3 receiving 13-1
Index X-5
customer support deleting
electronic 26-7 AS/400 Advanced 36 machine 30-4
customizing configuration 30-11
WRKUSRJOB command 10-12 authority required 7-7
CD-ROM device 31-10
D diskette device 31-8
D I 21-2 job log 10-21
D J 23-1 local area network (LAN) 31-4
D L 24-1 printer output
D U 23-2 batch job 10-9
D W 24-1 using control command 20-5
D WRT 20-6 using display option 20-5
data using menu option 20-5
restoring 12-1 tape 31-10
overview 12-1 determination, problem
data display stations 17-1 communications 27-1
data security 22-1, 22-2, 22-3 determining
badge security 22-2 device name
communications security 22-2 system console 4-1
menu security 22-1 device owner 28-1
resource security 22-3 if message has been sent to you 18-1
SSP ILAN communications are inactive 29-13
password security 22-1 OS/400 control point name 29-8
DDM device
using for PTFs 26-7 See also diskette unit
sent electronically 26-7 See also display device
Dedicated Service Tools (DST) 12-3 See also printer device
dedicated state See also tape unit
putting AS/400 Advanced 36 machine in 16-1 controlling OS/400 11-1
default startup setting description
understanding 29-3 changing 11-3
defining displaying 11-3
remote communications 11-5 determining which SSP jobs owns it 28-5
OS/400 11-5 integrity message 5-5
whether SSP or OS/400 controls display printing address (local) 11-3
station 31-36 renaming 11-2
definition status
abnormal end message 5-5 changing 11-1
batch job 10-1 displaying 11-1
corrective service 13-1 varied off 28-8
cumulative PTF package 13-1 varied on 28-8
device integrity message 5-5 working with 11-1
error message 5-5 device owner
informational message 5-1, 5-5 finding 28-1
inquiry message 5-1 device status
interactive job 10-1, 10-12 restrictions 11-2
job 10-1 Device Status Tasks menu
long wait 10-17 displaying 11-3
preventive service 13-1 Work with diskette devices option 11-1
qualified job name 10-2 Work with display devices option 11-1
severe error message 5-5 Work with printer devices option 11-1
subsystem 8-1, 21-1 Work with tape devices option 11-1
system alert message 5-5 DICTLOAD 25-26, 25-28
system integrity message 5-5 DICTSAVE 25-6, 25-8
system status message 5-5

directions displaying (continued)
pass-through 29-15 job
DISABLE 21-2, 29-14 information 10-14
disabling ILAN after configuration 29-7 log 10-19
diskette device priority 10-10
adding 31-8 status characteristics 10-15
deleting 31-8 job log 10-19
replacing 31-8 job queue
diskette unit assignment 10-15
See also diskette device priority 10-15
changing name 11-2 submitted jobs 10-10
renaming 11-3 keyboard messages 18-11
status machine 32-1
changing 11-1 menu list 6-9
displaying 11-1 menus 6-9
display 17-1 message
error message 5-15 queue 5-1
subconsole 17-5 SSP console 18-6
display device subconsole 18-6
changing name 11-2 that are waiting 18-6
status Work with Messages display 5-2
changing 11-1 open file 10-15
displaying 11-1 Operational Assistant menu 6-2, 7-3, 9-2, 10-5,
display option 11-3
using OS/400 console messages 29-13
to change printer output 20-4 output queue
to delete printer output 20-5 assignment 10-15
to display printer output 20-5 priority 10-15
to hold printer output 20-4 Power On and Off Tasks (POWER) menu 3-2
to release printer output 20-5 printer output
display station using display option 20-5
See also display device printer status 11-1
changing priority 10-15
attributes 31-27 PTF information 26-3
renaming 11-2 qysopr message queue 11-7
whether SSP or OS/400 controls it 31-36, 32-1 Restore menu 12-1
display station pass-through 29-15 Save menu 12-1
virtual devices 11-2 signed-on users 10-12
displaying 18-11 SSP PTF information 26-14
additional information for a message 18-5 status
AS/400 Advanced 36 machine 30-4, 32-1 device 11-1
configuration 30-11 diskette device 11-1
information 32-2 display device 11-1
batch job system operator message 5-7
all 10-6 tape device
by status 10-7 status 11-1
other users 10-6 DLTM36 30-4, 30-14
call stack 10-15 DLTM36CFG 30-14
Communications Configuration menu 11-5 document
configuration restoring 12-6
configuration of AS/400 Advanced 36 machine 32-1 saving 12-4
cumulative PTF information 26-3 doing a task
device description 11-3 using help when you do not know the
Device Status Tasks menu 11-3 command 19-4
interactive jobs 10-12 procedure 19-4
IPL mode B-1 using help when you know the
command 19-1
Index X-7
doing a task (continued) example
using help when you know the (continued) calling 10-2
procedure 19-1 program 10-2
DSPJOBLOG 10-19 changing 6-5, 6-6, 15-5, 15-7, 17-3, 31-22, C-4,
DSPM36 30-14, 32-1, 32-2 C-6, C-7
DSPM36CFG 30-14, 32-1 AS/400 Advanced 36 prestart job to immediately
DSPMSG 5-2, 11-7, 29-13 use changed values C-7
DSPNETA 11-5, 26-7, 29-8 assistance levels temporarily 6-5, 6-6
DST (Dedicated Service Tools) 12-3 from controller mapping to device
dump 16-3 mapping 31-22
dumping error message information 18-3 priority and storage pool of AS/400 Advanced 36
prestart job C-6
priority of an AS/400 Advanced 36 server
E job C-4
Electronic Customer Support 26-7 startup program to automatically start AS/400
using D-1 Advanced 36 machine 15-5, 15-7
electronic PTF installation to an alternative SSP console 17-3
checklist 26-9 defining 31-4, 31-8, 31-10, 31-12, 31-17, 31-26,
installing 26-9 31-36
saved PTF 26-13 CD-ROM device 31-10
ENABLE 21-2, 29-5, 29-6, 29-8, 29-14 communications line 31-4
ending diskette device 31-8
See also stopping display stations using controller mapping 31-17
AS/400 Advanced 36 machine 30-7 display stations using device mapping 31-12
batch job 10-9 printers using controller mapping 31-17
interactive job 10-13 printers using device mapping 31-12
user job 10-9 tape device 31-10
ENDM36 16-3, 30-14 whether SSP or OS/400 controls display
Enter pushbutton (system unit) 1-4 stations 31-36
entry whether SSP or OS/400 controls SSP printer
working with job schedule 10-3 output 31-26
entry lines displaying 10-15
console display 18-7 job attributes 10-15
subconsole display 18-7 job status 10-15
error ending 16-4
keyboard 5-15, 18-10 AS/400 Advanced 36 machine 16-4
error codes informational messages 18-5
CPFACEO 28-9 job 19-5
what do they mean 28-9 putting on the job queue 19-5
error messages message 5-5, 5-15, 18-2, 18-5, 18-8, 18-9, 18-10
definition 5-5 additional information 18-5
description 18-3 ID 5-5
display 5-15 replying to 18-8
dump option 18-3 requiring a response 18-2
handling 5-14 running the Work with Problems command 5-15
help for errors messages 18-3 sending to everyone on AS/400 Advanced 36
help option 18-3 machine 18-9, 18-10
menu 5-15 renaming 11-2
options 18-3 device 11-2
that instruct you to perform an action 18-2 display station 11-2
that require a response 18-2 running
using SSP procedure from Operating System/400 14-7
the help key for an explanation 18-3 sending 16-1
using the help key 18-11 message to all users 16-1
Error Reset key SRC code 1-3
using to unlock keyboard 18-10 starting 15-4
AS/400 Advanced 36 machine 15-4

example (continued)
stopping 16-2 H
AS/400 Advanced 36 machine 16-2 handling
submitting 10-2 AS/400 Advanced 36 Machine error codes 28-9
job to run immediately 10-2 break messages 5-7
transferring 14-4, 14-8 error message 5-14
display station to an AS/400 Advanced 36 message 5-1
machine 14-4 hardware
using STRPASTHR 14-8 problem handling 28-1
using 19-2, 19-3, 19-4, 19-5 hardware problems
MAIN menu 19-5 product activity log 28-1
POWER command 19-3 help for
RENAME procedure 19-4 keyboard messages 18-11
STATUS command 19-2 Help key 5-16
validating 31-39 commands 19-1, 19-4
AS/400 Advanced 36 machine control command 19-1, 19-4
configuration 31-39 error messages 18-3
viewing 10-6 explanations 18-11
jobs 10-6 parameters 19-1
working with 11-4 procedures 19-1, 19-4
OS/400 workstation controllers and lines 11-4 Help menu 19-1, 19-4
displaying 19-4
requesting from SSP console display 17-4
F HIST menu 23-3
file history file
displaying open 10-15 working with 23-2
spooled 7-1, 20-1 HOLD PRT 20-4
See also spooled file holding
filtering batch job 10-8
messages job queue 10-11
from the job log 10-20 job schedule entry 10-5
finding printer output
additional information about signed-on users 10-14 batch job 7-7, 10-8
device owner 28-1 using control command 20-4
menus 6-9 using display option 20-4
message information 5-3 using menu option 20-4
OS/400 control point name 29-8
output 7-4
printer output 7-3 I
SSP printer output 20-2 ID, reply 18-7
users signed on to the system 10-14 identifier, message 18-2
folder identifying
restoring 12-6 message from the system 5-5
saving 12-4 ILAN communications
form automatically starting 29-6
changing on a printer 7-13 automatically starting for OS/400 29-6
function/data display 1-3 automatically starting for SSP 29-6
communications problems 29-13
determining
G why inactive 29-13
getting why varied off 29-13
to Work with Printer Output Display disabling after configuration 29-7
using Operational Assistant 7-3 manually starting 29-3, 29-4, 29-5
GO 3-2, 6-2, 6-8, 6-9, 7-3, 9-2, 11-3, 11-5, 12-1 OS/400 side 29-3
GO POWER 3-2 SSP side, all connections 29-4
SSP side, one connection 29-5
Index X-9
ILAN communications (continued) IPL mode (continued)
recovery if not disabled before stopping AS/400 code (continued)
Advanced 36 machine 29-14 B N B-2
setting up 29-3 D M B-2
stopping 29-8, 29-9 D N B-2
OS/400 side 29-8 displaying B-1
SSP side, all connections 29-9 setting B-3
SSP side, one connection 29-9 type
system-to-system 29-1 attended B-2
verifying 29-10, 29-11, 29-12, 29-13 attended from CD-ROM B-2
for first AS/400 Advanced 36 machine 29-10 attended from tape B-2
for second AS/400 Advanced 36 machine 29-10 manual B-2
for third AS/400 Advanced 36 machine 29-11 normal B-2
OS/400 29-12 unattended B-2
SSP 29-13 IPL modes 1-5
ILAN subsystem, automatically starting 29-6 IPL start-up program
individual object creating 15-5
restoring 12-7 IPL types 1-5
saving 12-5 IPLTYPE parameter
INFOMSG control command 18-5 using 15-2
information
displaying about job 10-14
finding about messages 5-3 J
OS/400 related H-2 job
printing 7-1 See also active job
restoring 12-1 See also batch job
saving 12-1 See also interactive job
SSP related H-1 See also job queue
informational message 5-1, 5-5 See also Work Management
example of 18-5 assigning to a different output queue 10-18
not to be displayed at the SSP console 18-6 authority to work with 10-6
initializing changing
system 2-1 attributes 10-16
tapes for saving files 25-2 definition attributes 10-15
input inhibited light on and blinking 4-digit number how run 10-16
keyboard message 18-11 print priority 10-18
inquiry message priority on a queue 10-16
definition 5-1 changing, active 10-17
installing controlling 10-1
corrective SSP PTFs definition 10-1
from CD-ROM or tape 26-5 displaying
sent electronically 26-7 batch 10-6, 10-7
interactive job information 10-14
definition 10-1, 10-12 open file 10-15
disconnecting 10-13 priority 10-15
displaying 10-12 status characteristics 10-15
ending 10-13 ending
printing a job log for 10-19 batch 10-9
working with 10-12 interactive 10-13
intermediate assistance level logging level 10-20
definition 6-3 moving to a different queue 10-17
IPL mode open file
changing B-3 displaying 10-15
code performance 10-7
A M B-2 printing a job log for 10-19
A N B-2 priority
B M B-2 changing job queue 10-16

job (continued) job schedule entry (continued)
priority (continued) holding 10-5
status 10-9 releasing 10-5
processing saving 10-4
overview 10-1 working with 10-3
qualified name 10-2
queue 10-9
scheduling 10-4 K
batch 10-2 key
using the Change Job (CHGJOB) Help
command 10-3 error message 5-16
job description keyboard 17-1
changing 10-20 blinking 4-digit number and input inhibited light
job log on 18-11
See also Work Management error 5-15, 18-10
assigning to a separate output queue 10-21 messages
definition 10-19 keystroke mistake 5-15, 18-10
deleting 10-21
displaying 10-19
filtering
L
LAN (local area network)
messages 10-20
adding 31-4
performance 10-21
deleting 31-4
printing 10-19
replacing 31-4
sending output file to a separate output
learning about messages 18-1
queue 10-21
level, assistance
viewing 10-19
changing 6-4
working with 10-19
library
Job priority (on JOBQ) field 10-16
restoring
job processing
AS/400 Advanced 36 machine 12-6, 25-2
overview 10-1
user 12-6, 25-2
job queue
saving
assigned 10-9
AS/400 Advanced 36 machine 12-4, 25-1
assigning to a subsystem 10-12
changed objects 12-4
changing priority on 10-16
licensed program products
displaying
creating procedure to restore
assignment 10-15
restoring 25-24
job priority within 10-10
from procedure 25-29
jobs 10-10
interactively 25-25
priority 10-15
saving 25-3
holding 10-11
creating procedure for 25-7
moving
interactively 25-5
job to a different 10-17
using procedure 25-8
jobs on 10-11
using the RESTLIBR procedure to restore 25-19
priority of a job 10-9
light 5-3
releasing
attention 5-12
while system running 10-11
error, printer 11-2
status 10-9
input inhibited 18-1
subsystem 10-11
keyboard message 18-1
viewing 10-10
message 11-6
working with 10-10
message waiting 5-3, 5-11, 5-12, 18-1, 18-11
empty 10-10
power 3-4
unassigned 10-11
power on 1-2
job schedule entry
power, printer 11-2
adding 10-4
processor active 1-3
canceling 10-4
ready, printer 11-2
changing 10-5
Index X-11
light (continued) manual initial program load (IPL) (continued)
system attention 1-3, 3-4 types 1-5
line manual IPL (initial program load)
entry 18-7 modes 1-5
message 18-7 types 1-5
line, communications Manual mode (system unit) 1-6
See communications line mapping
link, establishing a communications 27-1 device to CD-ROM drive 26-16
local area network (LAN) menu
adding 31-4 error message 5-15
deleting 31-4 finding 6-9
replacing 31-4 SSP security
local device address general description 22-1
printing 11-3 system operations 6-9
locating menu list
printer output 7-3 displaying 6-9
log menu option
See also job log using
job to change printer output 20-4
filtering messages from 10-20 to copy printer output 20-5
product activity 28-1 to delete printer output 20-5
hardware problems 28-1 to hold printer output 20-4
logging level to release printer output 20-5
changing for job 10-20 to restart spool writer 20-7
long wait 10-17 to start spool writer 20-7
loop to stop spool writer 20-7
See program loop menu, main Help 19-1, 19-4
menus
displaying 6-9
M message 5-3
machine (M36) See also error message
restoring 12-6, 25-2 additional information 5-3, 18-5
saving 12-4, 25-1 answering printer device 7-11
machine prestart jobs C-2 critical
machine server job C-1 QSYSMSG 5-14
magnetic stripe reader 22-2 determining if has been sent to you 18-1
mail display 5-1
restoring 12-6 displaying
saving 12-4 command 5-2
main Help menu 19-1, 19-4 keyboard message 18-11
main menu 19-4, 19-5 message queue 5-1
maintaining SSP console 18-6
licensed program subconsole 18-6
corrective service 13-1 system operator 5-7
preventive service 13-1 error 5-16
making handling 5-1
alternative SSP console the SSP console 17-3 identifier 5-5
managing identifier description 18-2
AS/400 Advanced 36 machine identifying 5-5
operation 30-1 informational 18-5
printer output definition 5-1
command summary 20-3 inquiry
details 20-3 definition 5-1
manual dial 11-6 job log
manual initial program load (IPL) filtering 10-20
modes 1-5 keyboard 18-11

message (continued) MSG 18-9
keyboard error 5-15, 18-10 MSG OCL statement 18-10
learning about 18-1
lines on
console display 18-7 N
subconsole display 18-7 normal initial program load (IPL)
MSG Control Command 18-9 electronic installation checklist 26-9
MSG OCL statement 18-10 from tape to restore the SSP Operating
OFCMSG procedure 18-10 System 25-21
option installing a saved electronically sent SSP
for responding to 18-3 PTF 26-13
OS/400 types 5-1 installing electronically sent SSP PTFs 26-9
printing 5-3 removing corrective SSP PTFs 26-15
replying to 18-7 transferring SSP console function during an
responding to 5-9 IPL 17-2
sending 5-16 normal IPL (initial program load)
break 5-17 electronic installation checklist 26-9
SSP 18-9 from tape to restore the SSP Operating
to signed-on users 10-14 System 25-21
sent to OS/400 28-1 installing a saved electronically sent SSP
hardware problem 28-1 PTF 26-13
sent to SSP 28-1 installing electronically sent SSP PTFs 26-9
hardware problem 28-1 removing corrective SSP PTFs 26-15
severity code 5-5 transferring SSP console function during an
that are waiting 18-6 IPL 17-2
that instruct you to perform an action 18-2 Normal mode (system unit) 1-5
that require a response 18-2
type
abnormal end 5-5
O
object
device integrity 5-5
restoring 12-1
error 5-5
individual 12-7
informational 5-5
saving 12-1
severe error 5-5
changed 12-4
system alert 5-5
individual 12-5
system integrity 5-5
objects in directories
system status 5-5
restoring 12-5
types 18-2
saving 12-4
SSP 18-2
OFCMSG procedure 18-10
understanding the types 18-11
OFF 29-15
validation 31-39
online help
waiting 5-3
commands 19-1, 19-4
working with 5-2
control command 19-1, 19-4
message queue
procedures 19-1, 19-4
changing 5-12
open file
defined in user profile 5-8
displaying 10-15
displaying message in 5-1
open, control panel cover 1-1
working with 5-10
operation
message waiting light 5-3
managing
mistake
AS/400 Advanced 36 machine 30-1
keystroke 5-15, 18-10
Operational Assistant
mode
accessing
Manual 1-6
methods 6-3
Normal 1-5
user 6-3
moving
introduction 6-2
job to different job queue 10-17
printer output to print sooner 7-9
Index X-13
Operational Assistant menu password
displaying 6-2, 7-3, 9-2, 10-5, 11-3 changing 9-2
operator tasks security 22-1
quick reference 1-7 SSP 22-1
option patches
for error messages 18-3 installing corrective SSP PTFs
for responding to messages 18-3 from CD-ROM or tape 26-5
ordering sent electronically 26-7
program temporary fix (PTF) performance
electronically 13-2 considerations
OS/400 sending job log output file to a separate
defining if it controls display station 31-36 queue 10-21
giving control to job 10-7
printer output 31-30 performing
message IPL from tape to restore the SSP Operating
types 5-1 System 25-21
related information H-2 Post Telephone and Telegraph Administration
restoring operating system 12-3 (PTT) 11-7
security 9-1 power 19-3
OS/400 console pushbutton 1-2
displaying messages 29-13 Power On and Off Tasks (POWER) menu
output file displaying 3-2
sending job log to separate output queue 10-21 Power On light 1-2
output queue 7-1, 20-1 Power pushbutton 3-4
assigning a job to a different 10-18 stopping the system 3-4
displaying power system 1-6
assignment 10-15 powering down the system 3-1
priority 10-15 powering off 3-1
sending job log output file to a separate 10-21 immediate 3-2
output, printer powering off system
See printer output See stopping
overview powering on system
CL commands 6-1 See starting system
job processing 10-1 prestart jobs C-2, C-6
Operational Assistant 6-2 preventative service 26-1
owner preventive service
communication line 28-8 definition 13-1
communication port 28-4 maintenance strategy 13-1
device 28-1, 28-3 PTF 13-1
determining 28-1 print, SSP 20-8
display station 28-6 file 20-8
media device 28-5 printer 7-2, 20-1
printer 28-6 See also printer device
See also printer output
See also printer writer
P adding using device mapping 31-12
P P 20-7 assigning
page as system printer 20-8
start printing on 7-8 output to a different 7-8
parameters, using the help key 19-1 changing
pass-through directions 29-15 attributes 31-27
Passing through handling OS/400 and SSP printer conflicts 28-8
from OS/400 to SSP 29-15 using controller mapping to add printers 31-17
from SSP to OS/400 29-16 printer device
PASSTHRU 29-16 assigning output to 7-9
changing
forms 7-13

printer device (continued) printer output (continued)
changing (continued) holding (continued)
name 11-2 using display option 20-4
message using menu option 20-4
answering 7-11 locating 7-3
renaming 11-2 managing 7-7
restarting 7-11 details 20-3
starting moving to print sooner 7-9
Work with Printer Output display 7-10 releasing 7-7
status using control command 20-4
changing 11-1 using display option 20-5
displaying 11-1 using menu option 20-5
stopping 7-11 saving 7-9
working with 7-10 specify page to start on 7-8
printer device support using
See Printer Device Programming *QUTQ to direct to output queue 31-32
printer elements printer spooling support
See Printer Device Programming See Printer Device Programming
printer file printer writer 7-1, 20-1
changing 10-21 printing
printer options AS/400 Advanced 36 machine configuration 30-5,
changing 20-8 30-12
printer output changing priority of a job 10-18
assigning contents of libraries on
to a different printer 7-8 disk 20-8
to a printer 7-9 diskette 20-8
authority required 7-7 tape 20-8
batch job 7-7 cumulative PTF information 26-3
changing files saved on
characteristics 7-7 tape 20-8
number of copies 7-8 information 7-1
using Control Command 20-4 about AS/400 Advanced 36 machine 30-5
using display option 20-4 about IBM-supplied PTFs 26-3
using menu option 20-4 job log 10-19
command summary 20-3 job priority 10-18
copying local device address 11-3
using menu option 20-5 message 5-3
using procedure 20-5 moving printer output to print sooner 7-9
defining names of files on
whether SSP or OS/400 controls 31-26 disk 20-8
deleting diskette 20-8
authority required 7-7 tape 20-8
batch job 10-9 names of libraries on
using control command 20-5 disk 20-8
using display option 20-5 diskette 20-8
using menu option 20-5 tape 20-8
displaying priorities 7-6
using display option 20-5 priority
form type 7-9 changing 10-18
giving control PTF information 26-3
OS/400 OUTQ 31-32 SSP PTF information 26-14
to the OS/400 operating system 31-30, 31-32 understanding problems 7-5
to the SSP operating system 31-26 using
when no printer 31-32 *QUTQ to direct to output queue 31-32
holding priorities
batch job 10-8 printing 7-6
using control command 20-4
Index X-15
priority program temporary fix (PTF) (continued)
changing working with SSP 26-1
job on queue 10-16 corrective service 26-2
job’s print 10-18 cumulative PTF package 26-1
description 10-9 program, sample QSYS/QSTRUP start-up 15-7
displaying job 10-15 PTF (program temporary fix)
job queue 10-9 cumulative package 13-1
problem information
ILAN communications 29-13 receiving 13-2
working with 5-15, 13-1, D-1, D-3 installing
problem analysis cumulative SSP PTF packages 26-5
running 5-15 maintenance strategy 13-1
problem determination for communications 27-1 ordering
problem handling electronically 13-2
hardware 28-1 SSP PTF information 26-3
Processor Active light 1-3 SSP PTFs 26-3
System Attention light 1-3 receiving
problems electronically 13-2
hardware 28-1 using 13-1
product activity log 28-1 working with SSP 26-1
procedure corrective service 26-2
restoring cumulative PTF package 26-1
SSP Operating System and licensed program pro- PTF cumulative package
ducts, using the RESTLIBR 25-19 content 13-1
using help 19-1, 19-4 ordering 13-1
processing receiving 13-1
changing job 10-16 PTF information, SSP
Processor Active light 1-3 displaying 26-14
product activity log printing 26-14
hardware problems 28-1 PTT (Post Telephone and Telegraph
program loop Administration) 11-7
detecting 10-15 PTYLMT (priority limit) parameter 10-16
program maintenance strategy 13-1 pushbutton 1-2
program products PWRDWNSYS 3-3
creating procedure to restore
restoring 25-24
from procedure 25-29 Q
interactively 25-25 QAUTOVRT value
saving 25-3 changing 29-15
creating procedure for 25-7 QIPLDATTIM system value 3-3
interactively 25-5 QSYS/QSTRUP start-up program, sample 15-7
using procedure 25-8 QSYSMSG
program temporary fix (PTF) creating 5-14
cumulative package 13-1 system message
information critical 5-14
receiving 13-2 qsysopr message queue
installing displaying 11-7
cumulative SSP PTF packages 26-5 qualified job name
maintenance strategy 13-1 definition 10-2
ordering queue
electronically 13-2 See also job queue
SSP PTF information 26-3 See also message queue
SSP PTFs 26-3 See also output queue
receiving job
electronically 13-2 displaying 10-10
using 13-1 working with unassigned 10-11

queue (continued) requesting
output 7-1, 20-1 console display, SSP 17-4
quick reference help menu
operator tasks 1-7 from console 17-5
from subconsole 17-6
subconsole display 17-5
R requirements
receiving for using STRM36 15-1
program temporary fix (PTF) resource security 22-3
information 13-2 general description 22-3
recovery responding
See also problem determination message 5-9, 18-3
communications not disabled 29-14 RESTART PRT 20-7
before stopping AS/400 Advanced 36 restarting
machine 29-14 printer device 7-11
reference spool writer
operator tasks 1-7 using control command 20-7
reference code, system 18-9 using menu option 20-7
related information RESTEXTN 25-34, 25-36
OS/400 H-2 RESTFLDR 25-26, 25-28
SSP H-1 RESTLIBR 25-19, 25-26, 25-28, 25-35, 25-36
RELEASE PRT 20-4 RESTLIBR procedure
releasing restore the SSP Operating System and licensed
job 10-9 program products, using 25-19
job queue 10-11 RESTNRD 25-34, 25-36
job schedule entry 10-5 RESTORE 25-25, 25-28
printer output 7-7 Restore menu
using control command 20-4 displaying 12-1
using display option 20-5 restoring
using menu option 20-5 AS/400 Advanced 36 machine 25-1
remote configuration object 25-2
work station library 25-2
signing on 27-1 object 25-2
removing changed objects 12-6
corrective SSP PTFs 26-15 documents 12-6
job schedule entry 10-4 folders 12-6
RENAME 19-4 individual objects 12-7
renaming information 12-1
AS/400 Advanced 36 machine 30-5 licensed program products 25-24
AS/400 Advanced 36 machine configuration 30-12 from procedure 25-29
devices 11-2 interactively 25-25
diskette device 11-3 mail 12-6
display station 11-2 object 12-1
printer device 11-2 in directories 12-5
tape device 11-3 Operating System/400 operating system 12-3
replacing other SSP system file
CD-ROM device 31-10 creating a procedure for 25-35
communications line 31-4 from created procedure 25-37
diskette device 31-8 other SSP system files 25-32, 25-33
local area network (LAN) 31-4 from procedure 25-37
tape 31-10 interactively 25-33
REPLY control command 18-7 SSP Operating System 25-21
reply ID of a message 18-7 storage 12-3
replying to messages at system 12-2
SSP console 18-7 user library 12-6, 25-2
subconsole 18-7
Index X-17
restoring (reloading) saving (continued)
SSP Operating System 25-18 objects in directories 12-4
restrictions printer output 7-9
device status 11-2 SSP Operating System using SAVELIBR
STRM36PRC 14-6 procedure 25-3
transfers 14-1 SSP system files 25-12
STRM36PRC 14-1 creating procedure to save 25-16
TFRM36 14-1 interactively 25-13
returning to a command display 17-4 using created procedure to save 25-18
roll area, console 18-7 system 12-1
RSTAUT 12-7 user library 12-4, 25-1
RSTCFG 12-6 SAVLIB 12-4, 25-1
RSTCHGOBJ 12-6 SAVOBJ 12-5
RSTDLO 12-6 SAVSECDTA 12-2
RSTLIB 12-6, 25-2 SAVSECDTA (Save Security Data) command 12-5
RSTOBJ 12-7, 25-2 SAVSTG 12-3
RSTUSRPRF 12-7 SAVSYS command 12-2
run priority 10-17 SBMJOB 10-2
running schedule
job adding job entries 10-4
See active job canceling job entry 10-4
changing job entries 10-5
holding job entries 10-5
S releasing job entries 10-5
S P 20-6 saving job entries 10-4
sample QSYS/QSTRUP start-up program 15-7 schedule entry
SAVCFG 12-2, 12-4 working with job 10-3
SAVCHGOBJ 12-4 scheduling
SAVDLO 12-4 batch job to start an AS/400 Advanced 36
SAVE 25-5, 25-7 machine 10-5
Save menu batch jobs 10-2
displaying 12-1 job
Save Security Data (SAVSECDTA) command 12-5 batch 10-4
SAVEEXTN 25-14, 25-15, 25-17 using job schedule entries 10-3
SAVEFDLR 25-7 using the Change Job (CHGJOB)
SAVEFLDR 25-5 command 10-3
SAVELIBR 25-3, 25-6, 25-8, 25-15, 25-17 SECREST 25-33, 25-36
SAVENRD 25-14, 25-16 SECSAVE 25-13, 25-16
saving security 22-1, 22-2, 22-3
AS/400 Advanced 36 machine 12-4, 25-1 badge 22-2
configuration object 25-1 changing levels 9-1
library 25-1 communications 22-2
object 25-1 level 9-1
calendar 12-4 definition 9-1
changed objects in a library 12-4 levels, OS/400 9-1
documents 12-4 menu 22-1
folders 12-4 on Operating System/400 9-1
individual objects 12-5 resource 22-3
information 12-1 SSP password 22-1
job schedule entry 10-4 user profile 9-1
licensed program products 25-3 select pushbutton 1-3
creating procedure to 25-7 selecting
interactively 25-5 option
using procedure 25-8 from error messages 18-3
mail 12-4 to respond to a message 18-3
object 12-1

sending SRC code
break message 5-17 example 1-3
job log output file to a separate output queue 10-21 SSP
message 5-16, 18-10 communications
signed-on users 10-14 working with 24-1
SSP 18-9 console
server job C-1, C-3 informational messages 18-5
service defining if it controls display station 31-36
corrective 13-1 devices
preventative 26-1 working with 24-1
preventive 13-1 giving control to
setting printer output 31-26
IPL mode B-3 help support
setting attributes using 20-2
prestart jobs C-6 installing SSP PTF packages 26-5
server job C-3 message
SLIC tasks C-5 determining if has been sent to you 18-1
setting up ordering SSP program temporary fixes (PTFs) 26-3
ILAN communications 29-3 related information H-1
severe error message security
definition 5-5 working with 22-3
Sign On display 22-2 subconsole 17-1
signed-on users system
displaying 10-12 preloaded configuration 31-3
finding additional information about 10-14 work with program temporary fixes (PTFs) 26-1
sending messages to 10-14 corrective service 26-2
sorting the list 10-14 cumulative PTF package 26-1
working with 10-12 SSP console
signing on displaying messages 18-6
OS/400 system 2-3 making alternative SSP console it 17-3
signing user off the system 10-13 method of operating the system 17-1
signon to an AS/400 Advanced 36 machine replying to messages 18-7
automatic 14-5 transferring to alternative SSP console 17-3
SLIB 25-4, 25-8, 25-12, 25-18, 25-24, 25-29, 25-32, when SSP console is in operation 17-3
25-37 when SSP console is not in operation 17-4
SLIC tasks C-5 SSP control command
sorting ASSIGN 20-8
sign-on user list 10-14 BALPRINT 20-6
SPOOL menu 19-2, 20-6 CANCEL PRT 20-5
spool writer CONSOLE 17-3
restarting CONSOLE TAKE 17-3
using control command 20-7 D I 21-2
using menu option 20-7 D J 23-1
starting D L 24-1
using menu option 20-7 D U 23-2
with control command 20-6 D W 24-1
stopping D WRT 20-6
using menu option 20-7 HOLD PRT 20-4
working with 20-6 OFF 29-15
spooled file 7-1, 20-1 P P 20-7
changing POWER 19-3
priority 10-18 RELEASE PRT 20-4
spooled output RESTART PRT 20-7
balancing 20-6 S P 20-6
SPOOLJOB menu 20-2 START PRT 20-6
START SYSTEM 25-3, 25-9, 25-16, 25-18
Index X-19
SSP control command (continued) SSP PTF (continued)
STATUS 19-2 installing a saved electronically sent PTF 26-13
STATUS JOBQ 23-1 removing corrective PTFs 26-15
STATUS LINE 24-1 SSP PTF information
STATUS SUBSYS 21-2 displaying 26-14
STATUS USERS 23-2 printing 26-14
STATUS WORKSTN 24-1 SSP subsystem
STATUS WRT 19-2, 20-6 starting 21-2
STOP PRT 20-7 SSP system file
T P 20-7 creating procedure for saving 25-16
SSP job restoring other files 25-32
controlling 23-1 saving 25-12
determining which job owns a device 28-5 interactively 25-13
working with 23-2 using created procedure for saving 25-18
SSP menu START PRT 20-6
HIST 23-3 START SYSTEM 25-3, 25-9, 25-16, 25-18
MAIN 19-5 start-up program, sample QSYS/QSTRUP 15-7
SECURITY 22-3 starting
SPOOL 19-2, 20-6 Advanced 36 procedure 14-6
SPOOLJOB 20-2 AS/400 Advanced 36 machine 15-1, 30-6
SSP Operating System AS/400 Advanced 36 Machine automatically 15-5
performing an IPL from tape to restore 25-21 automatically
restoring (reloading) 25-18 ILAN communications 29-6
saving using the SAVELIBR procedure 25-3 ILAN communications for OS/400 29-6
using the RESTLIBR procedure to restore 25-19 ILAN communications for SSP 29-6
SSP printer output ILAN subsystem 29-6
finding 20-2 manually
SSP procedure ILAN communications 29-3
COPYPRT 20-5 ILAN communications on OS/400 side 29-3
DICTLOAD 25-26, 25-28 ILAN communications on SSP side, all con-
DICTSAVE 25-6, 25-8 nections 29-4
DISABLE 21-2, 29-14 ILAN communications on SSP side, one con-
ENABLE 21-2, 29-5, 29-6, 29-8, 29-14 nection 29-5
PASSTHRU 29-16 printer device
RENAME 19-4 Work with Printer Output display 7-10
RESTEXTN 25-34, 25-36 spool writer
RESTFLDR 25-26, 25-28 using control command 20-6
RESTLIBR 25-19, 25-26, 25-28, 25-35, 25-36 using menu option 20-7
RESTNRD 25-34, 25-36 SSP subsystem 21-2
RESTORE 25-25, 25-28 system
SAVE 25-5, 25-7 methods 2-1
SAVEEXTN 25-14, 25-15, 25-17 Starting an SSP Procedure from OS/400
SAVEFDLR 25-7 STRM36PRC 14-1
SAVEFLDR 25-5 starting AS/400 Advanced 36 machine
SAVELIBR 25-3, 25-6, 25-8, 25-15, 25-17 automatically 15-5
SAVENRD 25-14, 25-16 statement
SECREST 25-33, 25-36 MSG OCL 18-10
SECSAVE 25-13, 25-16 status 19-2
SLIB 25-4, 25-8, 25-12, 25-18, 25-24, 25-29, 25-32, job
25-37 displaying 10-15
table 25-30 list 10-9
for licensed program product restores 25-30 job queue 10-9
TAPEINIT 25-2 selecting batch jobs according to 10-7
WRKSPL 20-2 STATUS JOBQ 23-1
SSP PTF STATUS LINE 24-1
installing
electronically sent 26-9

STATUS SUBSYS 21-2 system (continued)
STATUS USERS 23-2 identifying message from 5-5
STATUS WORKSTN 24-1 message
STATUS WRT 19-2, 20-6 alert 5-5
STOP PRT 20-7 critical 5-14
stopping integrity 5-5
AS/400 Advanced 36 machine 16-1 QSYSMSG 5-14
from system console 16-2 status 5-5
batch job 10-9 operations
ILAN communications 29-8, 29-9 menus 6-9
OS/400 side 29-8 power, uninterrupted 1-6
SSP side, all connections 29-9 reference code, description 18-4, 18-9
SSP side, one connection 29-9 restoring 12-2
interactive job 10-13 saving 12-1
printer device 7-11 signing on OS/400 2-3
spool writer signing users off 10-13
using menu option 20-7 starting 2-1
SSP subsystem 21-2 stopping 3-1
system using the SSP console 17-1
considerations 3-1 System Attention light 1-3
immediately 3-2 system console
methods 3-1 determining device name 4-1
power pushbutton 3-4 differences from other displays 4-1
PWRDWNSYS command 3-3 system operator
storage message
restore 12-3 displaying 5-7
STRM36 15-1, 30-14 system printer
requirements for using 15-1 assigning 20-8
STRM36PRC 14-1, 14-6, 14-7, 30-14 system value
restrictions 14-6 QIPLDATTIM 3-3
STRPASTHR 29-15 System/36 command and AS/400 command cross-
STRREXPRC 10-2 reference A-1
subconsole
display
using 17-5 T
displaying messages 18-6 T P 20-7
replying to messages 18-7 tape
requesting help menu 17-6 adding 31-10
SSP 17-1 deleting 31-10
submitting initializing for saving files 25-2
batch job 10-2 replacing 31-10
batch job that runs immediately 10-2 restore the SSP Operating System by doing an
job, batch 10-2 IPL 25-21
subsystem tape cartridge drive
automatically starting ILAN 29-6 changing to
description from CD-ROM drive 26-17
working with 8-2 installing corrective SSP PTFs 26-5
ending tape device
SSP 21-2 See also tape unit
SSP 8-1, 21-1 changing name 11-2
working with 8-1, 8-2, 21-1 displaying status 11-1
switched communications line 11-6 renaming 11-3
switching to a command display 17-4 status
system changing 11-1
console 4-1 displaying 11-1
finding who is signed on 10-14
Index X-21
TAPEINIT 25-2 user job
tasks ending 10-9, 10-13
using working with 10-5
commands to do 19-1 batch 10-5
procedures to do 19-1 user profile 14-5
temporary password changing assistance level in 6-7
changing 9-2 message queue defined in 5-8
TFRM36 14-1, 14-3, 30-14 user profile message queue 5-8
time using
slice 10-17 APYM36CFG parameter 15-3
transferring commands to do tasks 19-1
important information 14-1 communications 27-1
procedure to an AS/400 Advanced 36 console display, SSP 17-4
machine 14-6 Electronic Customer Support D-1
to an AS/400 Advanced 36 machine 14-3, 14-7 Help
to an AS/400 Advanced 36 machine with automatic for keyboard messages 18-11
sign-on 14-5 to do a task 19-1
to AS/400 Advanced 36 machine 30-7 Help key for error messages explanations 18-11
using 14-3, 14-6, 14-7 Help key for parameters 19-1
STRPASTHR 14-7 help when you do not know the
TFRM36 14-3 command 19-4
transferring SSP console function procedure 19-4
during IPL 17-2 help when you know the
to alternative SSP console 17-3 command 19-1
to an alternative SSP console 17-2 procedure 19-1
when SSP console is in operation 17-3 IPLTYPE parameter 15-2
when SSP console is not in operation 17-4 keyboard messages 18-11
transferring to pass-through 29-15
AS/400 Advanced 36 machine 14-1 procedures to do tasks 19-1
transfers RESTLIBR procedure to restore the SSP Operating
restrictions 14-1 System and licensed program products 25-19
STRM36PRC 14-1 SSP console 17-1
TFRM36 14-1 SSP help support 20-2
turning off system subconsole display 17-5
See stopping USRPRF parameter 15-2
WRKSPL command 20-2
USRPRF parameter
U using 15-2
unattended IPL
changing B-3
setting B-3 V
unit validating
See diskette unit configuration of AS/400 Advanced 36
See tape unit machine 31-39
unlocking keyboard validation message 31-39
Error Reset key 18-10 varied off
user device 28-8
finding those signed on to the system 10-14 varied on
library device 28-8
restoring 12-6, 25-2 VARY control command 27-1, 27-2
saving 12-4, 25-1 verifying
signed-on ILAN communications 29-10, 29-11, 29-12, 29-13
finding additional information about 10-14 for first AS/400 Advanced 36 machine 29-10
signing off the system 10-13 for second AS/400 Advanced 36 machine 29-10
working with signed-on 10-12 for third AS/400 Advanced 36 machine 29-11
OS/400 29-12
SSP 29-13

VRYCFG 29-4, 29-8, 29-9, 29-14 WRKSPL procedure 20-8
WRKSPLF 7-13
WRKUSRJOB 10-5, 10-12, 10-13
W WRKWTR 7-10
waiting messages 18-6
warning message
definition 5-5
Work with diskette devices option
Device Status Tasks menu 11-1
Work with display devices option
Work with jobs option
Operational Assistant menu 10-5
Work with Printer Output Display
using
CL command to get to 7-3
Operational Assistant to get to 7-3
to find output 7-4
Work with tape devices option
working with
history file 23-2
job queue 10-10
job schedule entry 10-3
messages 5-2
problem 5-15, 13-1, D-1, D-3
spool writers 20-6
SSP communications 24-1
SSP devices 24-1
SSP jobs 23-2
SSP program temporary fixes (PTFs) 26-1
SSP security 22-3
subsystem 8-2
subsystem description 8-2
user job 10-5, 10-13
writers 7-10
workstation
adding using device mapping 31-12
using
controller mapping to add workstations 31-17
remote support 27-1
writer
printer 7-1, 20-1
writers
working with 7-10
WRKCFGSTS 28-8
WRKJOBQ 10-10
WRKJOBSCDE 10-3
WRKM36 30-1, 30-14
WRKM36CFG 30-8
WRKMSG 5-2
WRKOBJLCK 28-8
WRKPRB 5-15, 13-1, D-1, D-3
WRKSPL 20-2
WRKSPL command
using 20-2
Index X-23
Reader Comments—We'd Like to Hear from You!
AS/400 Advanced Series
Operator Tasks –
Publication No. SC21-8384-01
Overall, how would you rate this manual?
Very
Very Dissatis-
Satisfied Dissatis-
Satisfied fied
fied
Overall satisfaction
How satisfied are you that the information in this manual is:
Accurate
Complete
Easy to find
Easy to understand
Well organized
Applicable to your tasks
THANK YOU!
Please tell us how we can improve this manual:
May we contact you to discuss your responses? __ Yes __ No

Phone: (____) ___________ Fax: (____) ___________ Internet: ___________
To return this form:

Mail it
Fax it
United States and Canada: 800+937-3430
Other countries: (+1)+507+253-5192
Hand it to your IBM representative.
Note that IBM may use or distribute the responses to this form without obligation.
Name Address
Company or Organization
Phone No.
Cut or Fold
Reader Comments—We'd Like to Hear from You! Along Line
SC21-8384-01
IBM 
Fold and Tape Please do not staple Fold and Tape
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
ATTN DEPT 542 IDCLERK

IBM CORPORATION
3605 HWY 52 N
ROCHESTER MN 55901-9986
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SC21-8384-01 Along Line
IBM 
Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.
SC21-8384-ð1
Spine information:
Operator Tasks –
IBM AS/400 Advanced Series Multiple Operating Systems

AS400 Operations Basic

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AS400 Operations Basic

Încărcat de

Drepturi de autor:

Formate disponibile

AS/400 Advanced Series IBM

Second Edition (November 1996)

or you can fax your comments to:

United States and Canada: 800+937-3430

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

AS/400 System Operation

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

OS/400 for the SSP Operator

Chapter 3. Stopping the System Unit . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter 4. The OS/400 System Console . . . . . . . . . . . . . . . . . . . . . 4-1

Chapter 5. Handling OS/400 Messages . . . . . . . . . . . . . . . . . . . . . 5-1

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

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

 Copyright IBM Corp. 1995, 1996 iii

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

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

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

Chapter 11. Working with OS/400 Devices and Communications . . . . 11-1

Chapter 14. Transferring to an AS/400 Advanced 36 Machine . . . . . . 14-1

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

Chapter 15. Starting an AS/400 Advanced 36 Machine . . . . . . . . . . . 15-1

Chapter 16. Stopping an AS/400 Advanced 36 Machine . . . . . . . . . . 16-1

Chapter 18. Handling SSP Messages . . . . . . . . . . . . . . . . . . . . . 18-1

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

Chapter 20. Printing with SSP . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Chapter 21. Working with SSP Subsystems . . . . . . . . . . . . . . . . . 21-1

Chapter 22. SSP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Chapter 24. Working with SSP Devices and Communications . . . . . . 24-1

Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine

Chapter 26. Working with SSP Program Temporary Fixes . . . . . . . . 26-1

Chapter 27. Establishing a Communications Link for Remote

AS/400 System Common Operator Tasks

Chapter 28. Problem Handling . . . . . . . . . . . . . . . . . . . . . . . . . 28-1

Chapter 29. System-to-System Communications - ILAN

Chapter 30. Using CL Commands to Manage AS/400 Advanced 36

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

Chapter 31. Changing Your AS/400 Advanced 36 Machine Configuration 31-1

Chapter 32. Displaying Information About an AS/400 Advanced 36

Other Useful Information

Appendix A. System/36 and AS/400 Commands Cross-Reference . . . . A-1

Appendix C. Performance Considerations . . . . . . . . . . . . . . . . . . C-1

Appendix D. Using Electronic Customer Support . . . . . . . . . . . . . . D-1

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

Address your questions to:

This publication could contain technical inaccuracies or typographical errors.

 Copyright IBM Corp. 1995, 1996 ix

C-bus is a trademark of Corollary, Inc.

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

Who Should Use This Book

 Copyright IBM Corp. 1995, 1996 xi

The book is divided into several parts:

What You Should Do Before You Use this Book

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

Where to Go for Other Information

For information about Advanced 36 publications, see the Advanced 36 Information

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

 Copyright IBM Corp. 1995, 1996

| Chapter 1. AS/400 System Operations Tasks

What You Need to Know about Your Control Panel

Figure 1-1. Control Panel with Cover Closed

When the control panel is closed, two lights are visible:

 Copyright IBM Corp. 1995, 1996 1-1

1. If you have a lock on your control panel, unlock the cover.

Power on is allowed in Manual or Normal mode. Power off is allowed in