AS400 Operations Basic
AS400 Operations Basic
AS400 Operations Basic
Operator Tasks –
Multiple Operating Systems
SC21-8384-01
AS/400 Advanced Series IBM
Operator Tasks –
Multiple Operating Systems
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.
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
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
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 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 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
Contents v
Chapter 23. Controlling SSP Jobs . . . . . . . . . . . . . . . . . . . . . . . 23-1
Working With Current Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Working with the History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
| 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
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.
IBM Corporation
Software Interoperability Coordinator
3605 Highway 52 N
Rochester, MN 55901-7829 USA
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:
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.
Other company, product, and service names, which may be denoted by a double asterisk (**), may be
trademarks or service marks of others.
| 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.
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 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
| 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
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:
| 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
The table in Figure 1-3 on page 1-6 summarizes what operations you can do in
the Manual (M) or Normal (N) IPL modes:
Note: You can display the kind of IPL the system is set to do when the system is
in any mode.
If you want to stop the system when the mode is set to Normal, use the Power
Down System (PWRDWNSYS) command at any display station after you stop the
AS/400 Advanced 36 machines. You must have QSYSOPR authority to use the
Power Down System (PWRDWNSYS) command.
Figure 1-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)
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.
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
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
| 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.
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.
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
à@ ð
Sign On
System . . . . . : SYSTEMð1
Subsystem . . . . : QBASE
Display . . . . . : DSPð1
User . . . . . . . . . . . . . . __________
Password . . . . . . . . . . . .
Program/procedure . . . . . . . . __________
Menu . . . . . . . . . . . . . . __________
Current library . . . . . . . . . __________
Chapter 2. Starting the System Unit and OS/400 Operating System 2-3
Starting System Unit
The system cleanup functions are automatically started with default values.
For more information about customizing the cleanup function, see chapter 8
of the System Operation book, SC41-4203.
The Attention key program defaults to display the Operational Assistant
(ASSIST) menu.
For more information on signon displays, see the System Startup and Problem
Handling book, SC41-4206.
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.
à@ ð
Confirm Power Off of System
System: SYSTEMð1
Next scheduled power on:
Date . . . . . . . . . . . : ð5/19/95
Time . . . . . . . . . . . : ð5:4ð:ðð
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)
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.
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.
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.
QCONSOLE is the value that specifies the name of the display device that is the
console. You cannot change this system value.
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.
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.
à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : SMITHS1 Program . . . . : \DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : ðð Delivery . . . : \NOTIFY
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.
à@ ð
Work with Messages
System: SYSTEMð1
Messages for: SMITH
Opt Message
Messages needing a reply
_ Controller SYSTEMð1 contact not successful. Probable remote station
problem (C R)
á ñ
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.
For example, Figure 5-3 on page 5-4 shows additional information about the first
inquiry message in Figure 5-2:
à@ ð
Additional Message Information
Message ID . . . . . . : CPA57EF
Date sent . . . . . . : 11/18/91 Time sent . . . . . . : 15:43:ð2
á ñ
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
Bottom
Press Enter to continue.
á ñ
Figure 5-4. Display Message Details display
CPF 0083
↑ ↑
.A/ .B/
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.
à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : SMITHS1 Program . . . . : \DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : ðð Delivery . . . : \NOTIFY
Bottom
F3=Exit F11=Remove a message F12=Cancel
F13=Remove all F16=Remove all except unanswered F24=More keys
á ñ
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.
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
Messages needing a reply
_ Device PRTð1 not available (C R)
á ñ
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.
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
message queue will not be set back to the delivery mode it was set to when doing
the first transfer.
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.
à@ ð
Additional Message Information
Message ID . . . . . . : CPA5335
Date sent . . . . . . . : 11/27/95 Time sent . . . . . . : ð8:31:42
More...
Type reply below, then press Enter.
Reply . . . ____________________________________________________________
á ñ
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
á ñ
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.
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.
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.
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).
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-
dling book, SC41-4206.
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.
The keyboard is now back to normal and you can continue with your task.
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,
1. On an OS/400 command line, type
SNDMSG
2. Press F4.
3. Type a message in the Message text field.
The message you type can contain a maximum of 512 characters. If the text
contains blanks or other special characters, the text must be enclosed in apos-
trophes.
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.
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:
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:
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.
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.
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.
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:
á ñ
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.
à@ ð
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)
To change the assistance level for the Work with User Jobs (WRKUSRJOB)
command and reach the Work with Signed-On Users display:
1. On an OS/400 command line, type
WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\INTERACT) ASTLVL(\BASIC)
2. Press Enter.
Example 2
To change the assistance level for the Work with Users Jobs (WRKUSRJOB)
command and reach the Work with Jobs display :
1. Type
WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\BATCH) ASTLVL(\BASIC)
2. Press Enter.
Note: If you follow the directions in examples 1 and 2, you only change the assist-
ance level for one use of the command. If you issue another command and
then use the WRKUSRJOB command again, you return to the intermediate
assistance level.
Example 3
OR
1. Type
DSPMSG MSGQ(QSYSOPR)
2. Press Enter.
3. Press F21 (Select assistance level).
4. Type
1
to select Basic.
5. Press Enter.
à@ ð
Work with Messages
System: SYSTEMð1
Messages in: QSYSOPR
Opt Message
Messages needing a reply
_ Device RMTPRTðð13 not available. (C R)
_ Device RMTPRTðð12 not available. (C R)
_ Device RMTPRTððð9 not available. (C R)
_ Device RMTPRTðððð not available. (C R)
_ Load form type '\STD' device PRTð1 writer PRTð1. (H C G I R)
_ Device KOLUMDEV not available. (C R)
á ñ
Figure 6-5. Work with Messages Display—Basic Assistance Level
Example 4
OR
1. Type
DSPMSG MSGQ(QSYSOPR)
2. Press Enter.
3. Press F21 (Select assistance level).
4. Type
2
to select Intermediate.
5. Press Enter.
à@ ð
Display Messages
System: SYSTEMð1
Queue . . . . . : QSYSOPR Program . . . . : \DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : 7ð Delivery . . . : \HOLD
á ñ
Figure 6-6. Display Messages Display—Intermediate Assistance Level
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.
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
To select one of the following, type its number below and press Enter:
..............................................................................
: 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.
à
RUNBCKUP
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.
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.
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.
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.
Figure 7-1 on page 7-4 shows the Work with Printer Output display.
à@ ð
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.
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
Figure 7-3 maps OS/400 and SSP printing priorities.
The Change Printer Output display appears. Figure 7-4 on page 7-8 shows
the Change Printer Output display.
à@ ð
Change Printer Output
á ñ
Figure 7-4. Change Printer Output Display
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.
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.
à@ ð
Work with Printers
User . . . . . : SMITH
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).
4. Press Enter.
The Work with Printer Output display appears.
From the Work with Printer Output display you can:
Change the attributes of a spooled file
Hold a spooled file
Delete a spooled file
Display the contents of a spooled file
Release a held spooled file
Answer a printer message
Work with printing status
Start printing
Restart printing
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.
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
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.
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 APPC subsystem allows the System/36 to communicate with other systems
that have compatible support.
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
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.
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.
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.
á ñ
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
Current password . . . . . . . . . . . .
New password . . . . . . . . . . . . . .
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.
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
SBMJOB Batch
Job
Writer Printer
Interactive
Job
RSLP109-0
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.
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.
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.”
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
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.
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.
à@ ð
Work with Job Schedule Entries RCH3836ð
ð3/25/91 ð8:15:ð4
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
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.
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
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.
Security Consideration
To view and manage the jobs of other users, you must have job control
(*JOBCTL) authority in your user profile.
If you want to see all of the jobs for a user, type the user ID of the person whose
jobs you want to see in the User field and press Enter.
The Work with Jobs display appears for the user you selected.
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
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.
à@ ð
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 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.
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.
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
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
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.
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.
You can also use the Work with User Jobs command as follows:
1. On an OS/400 command line, type
WRKUSRJOB USER(\ALL) STATUS(\ACTIVE) JOBTYPE(\INTERACT) ASTLVL(\BASIC)
2. Press Enter.
à@ ð
Work with Signed-On Users
System: SYSTEMð1
Find user . . . . . . . . . . . . . _________ Starting characters
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
Attention: Use caution when signing a user off the system. Ending a user’s inter-
active job may interrupt job or file updates.
The Work with Signed-On Users display is shown without the users you signed
off the system.
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.
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.”
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:
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.
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.
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.
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.
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.
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
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.
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.
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 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.
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.
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.
Your job log output file is printed or placed in an output queue, depending on how
your system is set up.
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.
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.
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.
Security Consideration
Only the devices for which you have object operational authority are displayed.
On all of the device displays, the device status can be changed with option 1 (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
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.
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
Tape device
Tape files
CL programs referring to this device
Diskette device
Diskette files
CL programs referring to this device
This printout can help you know where to attach new devices.
System 2
(or remote
System 1 controller)
Line
Description LIND LIND
Devices Devices
RV2P705-0
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
Type options below, then press Enter.
1=Make available 2=Make unavailable 5=Display details
7=Display message 9=Rename 13=Change description
Line/
Controller/
Opt Device Type Status
__ LINð2 \SDLC Active
__ RMTCTLð3 5394 Active
__ RMTDEV1 318ð Sign-on display
__ RMTDEV2 318ð Powered off or not yet available
á ñ
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.
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.
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.
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:
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.”
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.”
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.
Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-3
Saving and Restoring OS/400
Saving Calendar
The Save Calendar (SAVCAL) CL command saves of calendars and calendar
items.
Distribution objects (mail) cannot be saved or restored for individual users. Mail
can only be saved for all users.
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.
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(*ALLUSR) command saves all user libraries. To determine which
libraries are IBM libraries and which libraries are user libraries, see the Backup and
Recovery – Basic book, SC41-4304.
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.
Restoring Calendar
The Restore Calendar (RSTCAL) CL command allows you to restore calendars and
calendar items.
Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-5
Saving and Restoring OS/400
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.
Attention: When you restore an object, it replaces any existing object in the same
library with the same name and object type.
Chapter 12. Saving and Restoring OS/400 and OS/400 Objects 12-7
Saving and Restoring OS/400
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.
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-
dling book, SC41-4206.
| 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.
MICHAELS
MICHAELSON
MICHAELSEN
MICHAELSRM
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.
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 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)
| 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)
| 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.
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.
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)
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.
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.
When the pass-through has completed, an SSP sign-on display will appear at the
display device on which the STRPASTHR command was typed.
For more information on using STRPASTHR, see “Using Display Station Pass-
Through” on page 29-15.
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
For directions on using SSP sign-on displays, see Chapter 2 of the Operating Your
Computer–SSP Operating System book, SC21-8297.
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.
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.
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
AS/400 Advanced 36 machine.
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.
The possible values you can specify for the APYM36CFG parameter are:
configuration-object-name Specify the name of an existing AS/400 Advanced 36
machine configuration.
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.
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
RV3P219-0
Figure 15-1. How the STRM36 Parameters Affect an AS/400 Advanced 36 Machine
STRM36 M36(ADV36M)
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
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.
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.
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)
31ðð MONMSG MSGID(CPFðððð)
32ðð
33ðð QSYS/RLSJOBQ JOBQ(QGPL/QS36EVOKE)
34ðð MONMSG MSGID(CPFðððð)
35ðð
36ðð QSYS/STRCLNUP
37ðð MONMSG MSGID(CPFðððð)
38ðð
39ðð
4ððð QSYS/RTVSYSVAL SYSVAL(QCTLSBSD) RTNVAR(&CTLSBSD)
41ðð IF ((&CTLSBSD \NE 'QCTL QSYS ') +
42ðð \AND (&CTLSBSD \NE 'QCTL QGPL ')) GOTO DONE
43ðð
44ðð QSYS/STRSBS SBSD(QINTER)
45ðð MONMSG MSGID(CPFðððð)
46ðð
47ðð QSYS/STRSBS SBSD(QBATCH)
48ðð MONMSG MSGID(CPFðððð)
49ðð
5ððð QSYS/STRSBS SBSD(QCMN)
51ðð MONMSG MSGID(CPFðððð)
52ðð
53ðð QSYS/STRSBS SBSD(QSERVER)
54ðð MONMSG MSGID(CPFðððð)
55ðð
56ðð
57ðð
58ðð
59ðð DONE:
6ððð .1/ QSYS/STRM36 library-name/machine-name
61ðð MONMSG MSGID(CPFðððð)
62ðð
63ðð QSYS/RTVSYSVAL SYSVAL(QSTRPRTWTR) RTNVAR(&STRWTRS)
64ðð IF (&STRWTRS = 'ð') GOTO NOWTRS
65ðð
66ðð CALL PGM(QSYS/QWCSWTRS)
67ðð MONMSG MSGID(CPFðððð)
68ðð
69ðð NOWTRS:
7ððð RETURN
71ðð CHGVAR VAR(&CPYR) VALUE(&CPYR)
72ðð /\ Needed to include CPYR variable in program. \/
73ðð ENDPGM
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.
Each AS/400 Advanced 36 machine should be stopped in this way before you
power down or IPL the AS/400 system.
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.
7. Press Enter.
The AS/400 Advanced 36 machine is ended.
Example 1
ENDM36 M36(MYM36)
Example 2
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.
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.
For more information about data display stations and command display stations,
refer to the Using Your Display Station – Advanced 36 book, SC21-0209.
à@ ð
IPL
á ñ
Chapter 17. Operating the SSP Console and SSP Subconsoles 17-3
Using SSP Console, Subconsoles
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.
à@ 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:
1. Press the System Request key documented in the user's guide for your work-
station. A blank line is shown at the bottom of the display.
2. Press Enter with the input line blank.
á ñ
You 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
Using SSP Console, Subconsoles
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.
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.
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.
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.
à@ ð
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.
───┘
á ñ
Note: See Figure 18-1 on page 18-3 for information on which book is appropriate
to use for information on the messages.
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.
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.
à@ ð
SYSTEM CONSOLE W1
__ .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.
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 (**).
à@ ð
SYSTEM CONSOLE W1
á ñ
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.
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
This message was sent to all of the user IDs that were active on the AS/400
Advanced 36 machine.
For example, you can use the MSG OCL Statement when you want to let everyone
know you are taking the system down.
Example
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.
The keyboard is now back to normal and you can continue with your task.
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
RTSN017-0
Keyboard Message
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.
Example 1
Type
HELP STATUS
When you press Enter, the following STATUS menu is shown at your display
station:
à@ ð
STATUS W1
á ñ
Note: If you press Cmd11, the menu names are shown to the right of each menu
option as they appear on this display.
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.
Example 2
Type
HELP POWER
à@ ð
POWER OFF COMMAND
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.
Example 3
Type
HELP RENAME
and press Enter.
à@ ð
RENAME PROCEDURE Optional-\
á ñ
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.
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
à@ MAIN W1
ð
Main System/36 help 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.
à@ SYSSESN W1
ð
Perform general system activities
á ñ
The option that best describes what you were asked to do (put a job on the job
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
--------------------------------------------------------------------
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
Ready for option number or command
á ñ
The option that best describes what you were asked to do (put a job on the job
queue) is option 2 Jobs on the job queue.
á ñ
The option that best describes what you were asked to do (put a job on the job
queue) is option 2 Put a job on the queue.
7. On the command line, type
2
to select Put a job on the queue.
8. Press Enter.
The JOBQ COMMAND display overlays the JOBQUEUE menu at your 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.
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.
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.
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
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.
| 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.
| 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.
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.
If you want to change any of the items in the previous list, see the Changing Your
System Configuration–SSP book, SC21-8295
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
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.
A message is displayed indicating that the system has started to end the sub-
system. Another message is sent when the subsystem has ended.
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 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.
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 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 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.
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.
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 : ð
Max Active Jobs: 1 Max for PRTY 5:5ð 4:5ð 3:5ð 2:5ð 1:5ð ð:5ð
PRIORITY
POS JOBNAME PROC/DOC LIBR/FLDR USER STATUS JOBQ PROC
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
á ñ
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.
When the STATUS USER or D U command is run, the following display appears:
à@ ð
Complete STATUS USERS W1
á ñ
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.
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
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.
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.
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-3
Saving and Restoring SSP
Note: It is recommended that you place the AS/400 Advanced 36 machine in ded-
icated state prior to saving the licensed program products. This will 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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-5
Saving and Restoring SSP
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.
a. On the command line at the SSP system console, type
START SYSTEM
b. Press Enter.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-7
Saving and Restoring SSP
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,
add the following to the new procedure:
SAVELIBR library name,999,PPROD,,,TC,LEAVE
where library name is the file name of the programming support that is to
be saved. See Figure 25-1 on page 25-10 for the library name of the pro-
gramming support that is to be saved.
Note: On the SAVELIBR procedure there are parameters that were not
specified (the null parameters ',,'). The default values are used for
these parameters.
If the procedure name is DICTSAVE,
add the following to the new procedure:
DICTSAVE dictionary ID
where dictionary ID is the file name of the programming support that is to
be saved. See Figure 25-1 on page 25-10 for the dictionary ID of the pro-
gramming support that is to be saved.
4. Repeat step 3 on page 25-7 for each of the programming support functions
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.
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:
a. On the command line at the SSP system console, type
START SYSTEM
b. Press Enter.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-9
Saving and Restoring SSP
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-11
Saving and Restoring SSP
Note: It is recommended that you place the AS/400 Advanced 36 machine in ded-
icated state prior to saving the other SSP system files. This ensures 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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-13
Saving and Restoring SSP
TC
e. Press Enter.
A second help display appears.
f. In the Volume ID of tape field, type the volume ID of the tape used for the
save. If this is the same tape that was used to save the licensed program
products, the volume ID is PPROD.
Note: No values need to be specified for the other parameters on 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:
a. On the command line at the SSP system console, type
SAVENRD
b. Press the Help key.
The help display for the SAVENRD procedure appears.
c. In the Name of directory to be saved field, type
#NRD.FLE
d. In the Volume ID field, type the volume ID of the tape used for the save. 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.
A second help display appears.
Note: No values need to be specified for the other parameters on the
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:
a. On the command line at the SSP system console, type
SAVEEXTN #EXT1818
b. Press the Help key.
The help display for the SAVEEXTN procedure appears.
c. In the Name of file field, type the name of the tape file where you want to
save the #EXT1818 file. If you want the name to be #EXT1818, leave the
prompt blank.
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.
Note: No values need to be specified for the other parameters on the
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,
a. On the command line at the SSP system console, type
SAVEEXTN #EXT2424
b. Press the Help key.
The help display for the SAVEEXTN procedure appears.
c. In the Name of file field, type the name of the tape file where you want to
save the #EXT2424 file. If you want the name to be #EXT2424, leave the
prompt blank.
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.
Note: No values need to be specified for the other parameters on the
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:
a. On the command line at the SSP system console, type
SAVELIBR
b. Press the Help key.
The help display for the SAVELIBR procedure appears.
c. In the Name of library to be saved field, type the library name that 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.
e. In the Location of file field, type
TC
Note: No values need to be specified for the other parameters on the
SAVELIBR procedure. The default values will work.
f. Press Enter.
The library containing your configuration members is saved to tape.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-15
Saving and Restoring SSP
You have completed the task of saving the other SSP system files interactively.
If you put the AS/400 Advanced 36 machine in a dedicated state, remove the
dedication:
a. On the command line at the SSP system console, type
START SYSTEM
b. Press Enter.
Note: On the SAVENRD procedure there are parameters that were not
specified (the null parameters ',,'). The default values are used for
these parameters.
d. If you have the extended character set file #EXT1818 on your AS/400
Advanced 36 machine, add the following to the new procedure:
SAVEEXTN #EXT1818,file name,volume ID,999,TC,,,,LEAVE
where file name is the name of the tape file where you want to save the
#EXT1818 file and volume ID is the volume ID of the tape used for the
save. If this is the same tape that was used to save the licensed program
products, the volume ID is PPROD.
If you want the file name to be #EXT1818, you could specify a null value
(,,) for file name.
Note: On the SAVEEXTN procedure there are parameters that were not
specified (the null parameters ',,'). The default values are used for
these parameters.
e. If you have the extended character set file #EXT2424 on your AS/400
Advanced 36 machine, add the following to the new procedure:
SAVEEXTN #EXT2424,file name,volume ID,999,TC,,,,LEAVE
where file name is the name of the tape file where you want to save the
#EXT2424 file and volume ID is the volume ID of the tape used for the
save. If you want the name to be #EXT2424, specify a null value (,,). If
this is the same tape that was used to save the licensed program products,
the volume ID is PPROD.
Note: On the SAVEEXTN procedure there are parameters that were not
specified (the null parameters ',,'). The default values are used for
these parameters.
f. If you want to save the SSP configuration members on your AS/400
Advanced 36 machine, add the following to the new procedure:
SAVELIBR library name,999,volume ID,,,TC,LEAVE
where library name is the name of the library that contains the SSP config-
uration members and volume ID is the volume ID of the tape used for 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
specified (the null parameters ',,'). The default values are used for
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-17
Saving and Restoring SSP
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-19
Saving and Restoring SSP
à@ ð
SSP GENERATION AND RELOAD - SIGN ON
User ID . . . . . . . . . . . . . . . . . . . SYSSSP__
Password . . . . . . . . . . . . . . . . . . _________
à@ ð
SSP GENERATION AND RELOAD - INPUT/OUTPUT
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.
à@ ð
SSP GENERATION AND RELOAD - MESSAGES
á ñ
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-21
Saving and Restoring SSP
à@ ð
SSP GENERATION AND RELOAD - SIGN ON
User ID . . . . . . . . . . . . . . . . . . . SYSSSP__
Password . . . . . . . . . . . . . . . . . . _________
à@ ð
SSP GENERATION AND RELOAD - INPUT/OUTPUT
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-23
Saving and Restoring SSP
à@ ð
SSP GENERATION AND RELOAD - MESSAGES
á ñ
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.
Other files, folders and libraries that are part of the program product must be
restored using the RESTORE, RESTFLDR and RESTLIBR procedures.
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-25
Saving and Restoring SSP
To create a procedure to restore the licensed program products (features and pro-
ducts), do as follows:
1. Do one of the following:
Method 1
a. Use the print option P of the LIBR function to print a copy of the proce-
dure you created to save the licensed program products. You can 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.
2. Use DSU, FSEDIT or SEU to edit a new procedure library member. The name
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
“Making Procedures” in the S/36 System Reference book, SC21-9020.
3. Determine which programming support you want to restore to your AS/400
Advanced 36 machine.
4. Using the Figure 25-2 on page 25-30, find the programming support functions
you want to restore.
5. If the procedure name for the programming support function is not RESTORE,
RESTFLDR, RESTLIBR or DICTLOAD, add that procedure name to the proce-
dure you are editing. For example, if the programming support function 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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-27
Saving and Restoring SSP
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-29
Saving and Restoring SSP
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-31
Saving and Restoring SSP
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.
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-33
Saving and Restoring SSP
e. Press Enter.
The extended character set file #EXT2424 is restored from tape.
6. If you want to restore the SSP configuration members on your AS/400
Advanced 36 machine:
a. On the command line at the SSP system console, type
RESTLIBR
b. Press the Help key.
The help display for the RESTLIBR procedure appears.
c. In the Name of library to be restored field, type the library name that con-
tained the SSP configuration members when the save was done.
Normally, these members are stored in a library named #CNFGLIB.
d. In the Location of file field, type
TC
Note: No values need to be specified for the other parameters on the
RESTLIBR procedure. The default values will work.
e. Press Enter.
The library containing your configuration members is restored from tape.
To create a procedure to restore the other saved SSP system files such as pass-
word security file and resource security file:
1. Do one of the following:
Method 1
a. Use the print option P of the LIBR function to print a copy of the proce-
dure you created to save the licensed program products. You can 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.
2. Use DSU, FSEDIT or SEU to edit a new procedure library member. The name
of the procedure and the library you put it in is your choice. You might choose
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-35
Saving and Restoring SSP
Chapter 25. Saving and Restoring the AS/400 Advanced 36 Machine Information 25-37
Saving and Restoring SSP
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.
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.
| 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
| VRM Is the version, release and modification level of the software running on
| the system.
| 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 could be sent to you in the following ways:
On a corrective cumulative PTF package on a CD-ROM sent by IBM.
à@ ð
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.
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.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
\ 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.
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.
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.
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
System Startup and Problem Handling book, SC41-4206.
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
“Putting the AS/400 Advanced 36 Machine In a Dedicated State” on page 16-1.
After this is done, return here.
If you completed this step, the AS/400 Advanced 36 machine is in a 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.
| The NRD:
| Contains information about each remote file that can be accessed using DDM
| Reflects the DDM network as seen from the AS/400 Advanced 36 machine's
| viewpoint
| Identifies the remote files that can be accessed by the AS/400 Advanced 36
| machine
| Identifies the remote system where the files are located.
| If you have not previously installed an electronically sent PTF, you need the Local
| control point name of the AS/400 system. If you do not know the name, do the
| following:
| 1. On an OS/400 command line, type
DSPNETA
2. Press Enter.
3. Find the line titled Local control point name. This is the name of the AS/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.
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.
---------------------------------------------------------------------------
á ñ
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.
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.
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.
á ñ
15. Type
1
16. Press Enter.
17. On the command line, type
DISABLE
18. Press the Help key.
The DISABLE PROCEDURE help display appears.
19. In the Subsystem configuration name field, type the ILAN Subsystem Config-
uration Member name.
If you do not know the name, see the “Electronic Installation Checklist” on
page 26-9.
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.
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.
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.
AUTOPTCH APPLY,patchid,F1
where patchid is the patch ID of the corrective PTF you determined earlier.
5. Press Enter.
6. When the command display is shown, type
DELETE patchid,F1,,,LIBR
where patchid is the patch ID of the corrective PTF you determined earlier.
7. Press Enter.
When the command display is shown, the installation of the corrective PTF 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.
| 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):
1. On a command line on the AS/400 Advanced 36 machine, type
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.
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.
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.
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.
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.
| 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.
| 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.
| 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.
| 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.
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.
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.
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.
Contact your service representative for help.
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.
Contact your service representative for help.
00010005 The AS/400 Advanced 36 machine machine pointer is not valid
because an internal processing error occurred.
Contact your service representative for help.
00010006 Migration is pending and the state of the AS/400 Advanced 36
machine is not valid.
Contact your service representative for help.
01010002 Insufficient storage space exists to create the minimum size
AS/400 Advanced 36 machine.
To recover, free up disk storage or add another disk. The
| Any operating system running on the system can communicate with any other oper-
| ating system running on the system.
AS/400 AS/400
Other Token
Connections Ring
Other Token
Connections Ring
OS/400
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
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.
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.
You must make changes to the OS/400 side if you want ILAN communications to
manually start for OS/400.
Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN
| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-
| ically starts during the next IPL of OS/400. If you want to use ILAN com-
munications before the next IPL, you must manually start the OS/400 side.
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.
| ically starts during the next IPL of OS/400. If you want to use ILAN com-
munications before the next IPL, you must manually start the OS/400 side.
On the SSP Operating System, communication line 15 is used for ILAN commu-
nications. To start the APPC subsystem:
1. On the command line, type
ENABLE ILANSBS,#CNFGLIB,15
2. Press Enter.
ILAN communications are now started on the SSP side.
Note: These steps must be completed each time you start an AS/400
Advanced 36 machine.
On the SSP Operating System, communication line 15 is used for ILAN commu-
nications. To start the APPC subsystem:
1. On the command line, type
ENABLE ILANSBS,#CNFGLIB,15,NOSHOW,xxxxxxxx
where xxxxxxxx is the control point name.
IBMM3601 is the control point name of the first AS/400 Advanced 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.
You do not need to make changes to the OS/400 side unless ILAN communica-
tions were changed to manually start OS/400.
Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN
| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-
| ically starts during the next IPL of OS/400. If you want to use ILAN com-
munications before the next IPL, you must manually start the OS/400 side.
You do not need to make changes to the OS/400 side unless ILAN communica-
tions were changed to manually start OS/400.
Note: If you create additional AS/400 Advanced 36 machines and you set up ILAN
| for those AS/400 Advanced 36 machines, the OS/400 side of ILAN automat-
| ically starts during the next IPL of OS/400. If you want to use ILAN com-
munications before the next IPL, you must manually start the OS/400 side.
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.
2. To disable ILAN communications on the SSP side, comment out or delete the
following statement from the #STRTUP2 procedure in the #LIBRARY:
ENABLE ILANSBS,#CNFGLIB,15
This change to manual startup takes effect after the next IPL of OS/400 or after
the next startup of the AS/400 Advanced 36 machine.
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.
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.
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.
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.
| 6. Go to the console for the first AS/400 Advanced 36 machine and verify ILAN
| communications for the second AS/400 Advanced 36 machine. For directions,
see “SSP Side Verification” on page 29-13.
| 7. Go to the console for the second AS/400 Advanced 36 machine and verify
| ILAN communications for connections for OS/400 and the first AS/400
Advanced 36 machine. For directions, see “SSP Side Verification” on
page 29-13.
| Note: If you do not stop ILAN communications before you power off the AS/400
| Advanced 36 machine, when you start the AS/400 Advanced 36 machine
| again, you might need to stop and restart all of the ILAN connections to the
| AS/400 Advanced 36 machine. For information on how to do this, see
| “Recovery When Communications Were Not Disabled Before Stopping an
| AS/400 Advanced 36 Machine” on page 29-14.
| 7. Go to the console for the first AS/400 Advanced 36 machine and verify ILAN
| communications for the third AS/400 Advanced 36 machine. For directions,
see “SSP Side Verification” on page 29-13.
| 8. Go to the console for the second AS/400 Advanced 36 machine and verify
| ILAN communications for the third AS/400 Advanced 36 machine. For
directions, see “SSP Side Verification” on page 29-13.
| 9. Go to the console for the third AS/400 Advanced 36 machine and verify ILAN
| communications for all connections for OS/400, the first AS/400 Advanced 36
machine and the second AS/400 Advanced 36 machine. For directions, see
“OS/400 Verification” and “SSP Side Verification” on page 29-13.
| Note: If you do not stop ILAN communications before you power off the AS/400
| Advanced 36 machine, when you start the AS/400 Advanced 36 machine
| again, you might need to stop and restart all of the ILAN connections to the
| AS/400 Advanced 36 machine. For information on how to do this, see
| “Recovery When Communications Were Not Disabled Before Stopping an
| AS/400 Advanced 36 Machine” on page 29-14.
OS/400 Verification
| To verify ILAN communications for the first AS/400 Advanced 36 machine, do as
| follows:
1. On an OS/400 command prompt, type
WRKCFGSTS \CTL QILANM36ð1
| where QILANM36ð1 is the OS/400 APPC controller description name for the first
| AS/400 Advanced 36 machine.
2. Press Enter.
3. Check the Status column.
Communications are started properly if the status is ACTIVE or VARIED ON.
4. If the status is not ACTIVE or VARIED ON, go to “Finding Out Why ILAN 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 recover,
1. Make sure all your AS/400 Advanced 36 machines are started.
2. Vary off each AS/400 APPC Controller Description as follows:
a. On an OS/400 command line, type
| VRYCFG QILANM36ðx \CTL \OFF
| where x is 1 for the first AS/400 Advanced 36 machine, 2 for the second
| AS/400 Advanced 36 machine and 3 for the third AS/400 Advanced 36
| machine.
| b. Press Enter to vary off the controller for the first AS/400 Advanced 36
| machine on which you are doing recovery.
c. On an OS/400 command line, type
| VRYCFG QILANM36ðx \CTL \ON
| where x is 1 for the first AS/400 Advanced 36 machine, 2 for the second
| AS/400 Advanced 36 machine and 3 for the third AS/400 Advanced 36
| machine.
| d. Press Enter to vary on the controller for each AS/400 Advanced 36
| machine on which you are doing recovery.
3. Disable and Enable ILAN communications for each AS/400 Advanced 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
ENABLE ILANSBS,#CNFGLIB,15
d. Press Enter.
For complete directions on using pass-through, see S/36 Using System/36 Commu-
nications book, SC21-9082.
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.
à@ ð
Work with Machines (WRKM36)
à@ ð
Work with M36 Machines
If you prefer, instead of doing step 1 on page 30-1 through step 5 on page 30-1,
you could do as follows:
1. On an OS/400 command line, type
WRKM36 \ALL/\ALL
2. Press Enter.
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
Advanced 36 machine.
To use the Work with M36 Machines display to create an AS/400 Advanced 36
machine, you would:
1. In the Opt field, type
1
to select Create.
2. Press F4.
The Create Machine (CRTM36) display appears.
3. Type the necessary values.
If you are unsure what a field is used for, you can position the cursor on 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.
To use the Work with M36 Machines display to change the attributes of an AS/400
Advanced 36 machine, you would do as follows:
1. In the Opt field, type
2
to select Change.
2. Press Enter.
The Change Machine (CHGM36) display appears.
3. Type the necessary values.
If you are unsure what a field is used for, you can position the cursor on the
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.
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-3
Managing Machines and Configurations
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.
To use the Work with M36 Machines display to display information about 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
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 .
To use the Work with M36 Machines display to print information about 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 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.
To use the Work with M36 Machines display to change the name of 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
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.
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-5
Managing Machines and Configurations
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.
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.
The description can contain up to 50 characters.
4. Press Enter to rename the AS/400 Advanced 36 machine.
| You can also use the CHGOBJD and the CHGM36 CL commands to change the
| description of an AS/400 Advanced 36 machine. For more information on how to
| use these commands, see the CL Reference book, SC41-4722.
To use the Work with M36 Machines display to start 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 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.”
Important Note
| To use the Work with M36 Machines display to abnormally end 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
| 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.
To use the Work with M36 Machines display to transfer to an AS/400 Advanced 36
machine, you would do as follows:
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.
3. Type the necessary values.
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-7
WRKM36CFG
If you are unsure what a field is used for, you can position the cursor on the
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.”
à@ ð
Work with Machine Config (WRKM36CFG)
à@ ð
Work with AS/4ðð Advanced 36 Machine Configurations
M36
Opt Configuration Library Text
If you prefer, instead of doing step 1 through step 5, you could do as follows:
1. On an OS/400 command line, type
WRKM36CFG \ALL/\ALL
2. Press Enter.
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.
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 configuration.
| When creating a new AS/400 Advanced 36 machine configuration, you can specify
| an existing AS/400 Advanced 36 machine or an existing AS/400 Advanced 36
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-9
WRKM36CFG
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.
| 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.
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.
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 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.
To use the Work with Machine Config (WRKM36CFG) display to delete 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 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
| command, see the CL Reference book, SC41-4722.
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 .
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-11
WRKM36CFG
To use the Work with Machine Config (WRKM36CFG) display to print the 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 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.
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:
1. In the Opt field beside the AS/400 Advanced 36 machine configuration that you
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.
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 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.
| You can also use the RNMOBJ command to rename an AS/400 Advanced 36
| machine configuration. For more information on how to use the RNMOBJ
| command, see the CL Reference book, SC41-4722.
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.
The description can contain up to 50 characters.
| You can also use the CHGOBJD and CHGM36CFG commands to change the
| description of the AS/400 Advanced 36 machine configuration. For more informa-
| tion on how to use these commands, see the CL Reference book, SC41-4722.
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-13
CL Command Summary Table
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.
Chapter 30. Using CL Commands to Manage AS/400 Advanced 36 Configurations and Machines 30-15
CL Command Summary Table
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.
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
Advanced 36 machine.
– 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
AS/400 Advanced 36 machine.
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,
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.
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.
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.
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:
a. Move the cursor to the line that corresponds to the workstation con-
troller number (1-4).
Note: If the workstation controller is mapped with controller mapping,
the line is filled in with an OS/400 Workstation 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:
a. Move the cursor to the line that corresponds to the workstation con-
troller number (1-4).
b. Blank out the line.
After you have applied this configuration to your AS/400 Advanced 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.
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.
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.
The Change M36 Configuration display appears.
14. Press F19 to validate your changes.
Note: For information on how to handle warnings and errors, go to “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
then return here.
15. If you need to make any configuration changes, return to step 7 on
page 31-12.
You may choose to make other changes as described in other sections of this
chapter before exiting.
16. To save and exit,
a. Press F3.
The Exit M36 Configuration display appears.
b. Make sure a 1 is in the Option field.
Note: If a 2 is in the Option field, and you proceed, the changes will 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.
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.
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.
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.
| 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.
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.
The Change M36 Configuration display appears.
18. If you did not list any information in step 7e on page 31-23, go to step 25 on
page 31-24. Otherwise, go to step 19.
19. In the Opt field, type
3
to select Change M36 display and printer device attributes.
20. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display appears.
21. In the M36 Controller field, type the workstation controller number.
22. Press Enter.
The display changes to show you a list of devices defined on the 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.
The Change M36 Configuration display appears.
25. Press F19 to validate your changes.
Note: For information on how to handle warnings and errors, go to “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
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.
You may choose to make other changes as described in other sections of this
chapter before exiting.
27. To save and exit,
a. Press F3.
The Exit M36 Configuration display appears.
b. Make sure a 1 is in the Option field.
Note: If a 2 is in the Option field, and you proceed, the changes will not
be made.
c. Press Enter.
The configuration changes are saved and the display with the OS/400
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.
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.
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.
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.
The Change M36 Configuration display appears.
19. Press F19 to validate your changes.
Note: For information on how to handle warnings and errors, go to “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
then return here.
20. If you need to make any configuration changes, return to step 8 on
page 31-27.
You may choose to make other changes as described in other sections of this
chapter before exiting.
21. To save and exit,
a. Press F3.
The Exit M36 Configuration display appears.
b. Make sure a 1 is in the Option field.
Note: If a 2 is in the Option field, and you proceed, the changes will not
be made.
c. Press Enter.
The configuration changes are saved and the display with the OS/400
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.
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.
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.
14. To change other printers on this workstation controller, return to step 12 on
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.
The Change M36 Configuration display appears.
18. Press F19 to validate your changes.
Note: For information on how to handle warnings and errors, go to “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
then return here.
19. If you need to make any configuration changes, return to step 8 on
page 31-30.
You may choose to make other changes as described in other sections of this
chapter before exiting.
20. To save and exit,
a. Press F3.
The Exit M36 Configuration display appears.
b. Make sure a 1 is in the Option field.
Note: If a 2 is in the Option field, and you proceed, the changes will not
be made.
c. Press Enter.
The configuration changes are saved and the display with the OS/400
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.
To specify which OS/400 output queue will receive the 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.
For directions, see the Changing Your System Configuration–SSP book,
SC21-8295.
2. On an OS/400 command line, type
CHGM36CFG
3. Press F4.
The Change Machine Configuration (CHGM36CFG) display appears.
4. In the Machine configuration field, type the name of the AS/400 Advanced 36
machine configuration.
5. In the Library field, type the name of the library in which the AS/400 Advanced
36 machine configuration object is stored.
6. Press Enter.
The rest of the parameters for the command appear on the display.
7. Press Enter.
The Change M36 Configuration display appears.
8. In the Selection field, type
2
to select Change M36 display and printer devices.
9. Press Enter.
The Chg M36 Display and Printer Dev display appears.
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.
13. Do one of the following:
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.
14. To change other printers on this workstation controller, return to step 12 on
page 31-33.
15. Press Enter.
The Chg M36 Display and Printer Dev display appears.
16. If you want to change another controller, return to step 10.
17. Press Enter.
The Change M36 Configuration display appears. Each *OUTQ you added 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
to select Change M36 display and printer device attributes.
b. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display appears.
c. In the M36 Controller field, type the identification number of the AS/400
Advanced 36 machine workstation controller where you defined the *OUTQ
special value.
The identification number can only be: 1, 2, 3, or 4.
d. Press Enter.
The Chg M36 Dsp and Prt Dev Attr display changes to show the attributes
of the display stations and printers on the specified controller.
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.
The Change M36 Configuration display appears.
19. Press F19 to validate your changes.
Note: For information on how to handle warnings and errors, go to “Validating
an AS/400 Advanced 36 Machine Configuration” on page 31-39 and
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.
You may choose to make other changes as described in other sections of this
chapter before exiting.
21. To save and exit.
a. Press F3.
The Exit M36 Configuration display appears.
b. Make sure a 1 is in the Option field.
Note: If a 2 is in the Option field, and you proceed, the changes will not
be made.
The configuration changes are saved and the display with the OS/400
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.
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: 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.
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.
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:
1. On an OS/400 command line, type
DSPM36CFG
2. Press F4.
The Display Machine Configuration (DSPM36CFG) display appears.
3. In the Machine configuration field, type the name of the AS/400 Advanced 36
machine configuration.
4. In the Library field, type the name of the library in which the AS/400 Advanced
36 machine configuration object is stored.
5. Press Enter.
The Display M36 Configuration display appears.
6. Type the number of the option that you want to display.
7. Press Enter.
The displays that appear are quite similar to the Change displays.
Note: You cannot make changes to any of these displays.
8. To display other options:
a. Press Enter.
The Display M36 Configuration display appears again
b. Repeat steps 6 and 7.
9. To exit, press F3.
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.
Chapter 32. Displaying Information About an AS/400 Advanced 36 Configuration and Machine 32-3
Displaying Configuration and Machine
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.
The Display M36 Machine display appears.
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.
| 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
Function/Data
E
Enter G
F RTSP039-1
3. Press the Enter pushbutton (G). A code similar to the following is shown:
Function/Data
E
Enter G
F RTSP040-2
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
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
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.
Interactive
OS/400 Job OS/400 Jobs
AS/400 AS/400
Advanced 36 Advanced 36
Server Prestart
Job Jobs
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.
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).
For more information about setting the attributes for OS/400 jobs, and job
descriptions, see the Work Management book, SC41-4306.
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.
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).
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.
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.
3. In the OPT field beside the problem you want to work with, type
8
4. Press Enter.
5. In the Selection field, type
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.
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)
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.
For information on switching between the command display and the console
display, see “Using the Console display” in the Operating Your
Computer–SSP Operating System book, SC21-8297.
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.
a. On the command display of the display station designated as the system
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.
a. On the command display of the display station designated as the system
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.
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.
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
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
communications line 31-4
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
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
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
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
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
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
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
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
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
Index X-23
Reader Comments—We'd Like to Hear from You!
AS/400 Advanced Series
Operator Tasks –
Multiple Operating Systems
Publication No. SC21-8384-01
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!
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
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
Cut or Fold
SC21-8384-01 Along Line
IBM
SC21-8384-ð1
Spine information:
Operator Tasks –
IBM AS/400 Advanced Series Multiple Operating Systems