IBM i (AS/400) Daily Operations Manual
AS/400 Basic Operation Guide
I Manual Startup of AS/400
1 Select Machine Startup Mode
AS/400 startup (IPL) mainly has two modes: Manual or Normal. The selection between these two modes is achieved via the control panel.
For models with an electronic key, this process is very easy. After inserting the electronic key into the keyhole, press the mode selection key continuously; the mode indicator lights will cycle one by one. Simply leave the light for the desired mode illuminated to complete the transition between manual and normal modes.
For models without an electronic key, mode switching requires using function 02 on the control panel. The steps are as follows.
A. Under normal conditions, the control panel displays '01 B N', indicating Normal mode.
B. Press the data display up button once; the panel will display '02'.
C. After pressing the execute key, the panel displays '02 B N'.
D. Press the data display up or down button repeatedly until '02 B M' is displayed.
E. Press the execute key once; the panel displays '02'.
F. Press the data display down button so that the panel displays '01'.
G. Press the execute key once; the panel then displays '01 B M', completing the transition from Normal mode to Manual mode.
If you wish to switch back from Manual mode to Normal mode, simply select '02 B N' at step D.
2 AS/400 Manual Startup Process
The startup of an AS/400 is called Initial Program Load, abbreviated as IPL (Initial Program Load). The IPL in Normal mode is simple: after confirming the correct mode selection, just press the start key. For Manual mode, after pressing the start key, you must answer some questions on the master terminal before the system becomes available. The specific process is as follows.
The first menu the system waits for a response to is 'IPL or Install the System', displayed as follows.
1. Perform an IPL
2. Install the operating system
3. Use Dedicated Service Tools (DST)
4. Perform automatic installation of the operating system
5. Save Licensed Internal Code
After determining no other operations are required, select '1 (Perform an IPL)' to start the AS/400.
After the login screen appears, log in with a user having Security Officer authority. It is recommended to use the QSECOFR user. After the 'Select Products to Work with PTFs' menu appears, display as follows; then press the F3 key.
Opt Product Option Release
5769999 *BASE V4R2M0
5769SS1 *BASE V4R2M0The 'IPL Options' menu appears, displayed as follows.
System date . . . . . . . . . . . . . . 04 / 21 / 00 MM / DD / YY System time . . . . . . . . . . . . . . 17 : 44 : 25 HH : MM : SS Clear job queues . . . . . . . . . . . . N Y=Yes, N=No Clear output queues . . . . . . . . . N Y=Yes, N=No Clear incomplete job logs . . . . . N Y=Yes, N=No Start print writers . . . . . . . . . . Y Y=Yes, N=No Start system to restricted state . . N Y=Yes, N=No Run #STRTUP1 procedure . . . Y Y=Yes, N=No Run #STRTUP2 procedure . . . Y Y=Yes, N=No Set major system options . . . . . . N Y=Yes, N=No Define or change system at IPL . N Y=Yes, N=No
Here you can change the system date and time. There are several points to note in this menu.
The third, fourth, and fifth lines shown—'Clear job queues', 'Clear output queues', and 'Clear incomplete job logs'—refer to clearing the job queue, clearing the print queue, and clearing the logs of all unfinished jobs in the system prior to the last shutdown, respectively. By default, the system does not clear these items. However, for special cases, you may set the necessary options to 'Y' to allow the system to clear them during the IPL process. IBM recommends not clearing logs of unfinished jobs because if the system encounters issues, job logs are the best tool for diagnosing problems.
The last two lines determine whether to define the system's runtime environment and change system parameters during startup. Once an AS/400 system is configured and put into operation, its runtime environment rarely changes, and these parameters can be modified while the system is running normally. Therefore, under general circumstances, it is recommended to select 'No' for both items when starting the AS/400.
If 'Set Major System Options' in the IPL Option menu is selected as 'Y', the system displays.
Enable automatic configuration . . . . . . . Y Y=Yes, N=No
Device configuration naming . . . . . . . . *NORMAL *NORMAL, *S36,
*DEVAD
Default special environment . . . . . . . . *NONE *NONE, *S36If 'Define or change system at IPL' in the IPL Option menu is selected as 'Y', the system displays.
1. Configuration commands
2. Change user profile
3. System value commands
4. Network attribute commands
5. General object commands
6. Work with shared pools
After the IPL Option menu, the system will occasionally pop up information; simply press the execute key. Unless there are special circumstances, the AS/400 main menu will appear shortly thereafter, indicating that the IPL is complete.
II AS/400 Shutdown
There are several methods to shut down an AS/400, described below.
Method One First, ensure that user applications have terminated. Then use 'ENDSBS *ALL *IMMED' to shut down all subsystems. When all subsystems are shut down, the system prompts 'The system is in a restricted state'. At this point, enter the command 'PWRDWNSYS', then press the F4 key to enter the 'Power Down System (PWRDWNSYS)' menu, displayed as follows.
How to end . . . . . . . . . . . *IMMED *CNTRLD, *IMMED Delay time, if *CNTRLD . . . . . 3600 Seconds, *NOLIMIT Restart options: Restart after power down . . . *NO *NO, *YES Restart type . . . . . . . . . *IPLA, *SYS, *FULL IPL source . . . . . . . . . . . *PANEL *PANEL, A, B, D
In the 'How to end' line, input '*IMMED'. If you intend to restart the system, input '*YES' in the 'Restart after power down' line, then press the execute key.
Method Two When the system is available, enter the command 'GO POWER'. This will display the 'Power On and Off Tasks' menu, shown as follows.
1. Display power on and off schedule
2. Change power on and off schedule
3. Power off the system immediately
4. Power off the system immediately and then power on
If only shutting down, select '3'. If restarting is also required, select '4'. After entering the option, press the execute key, then press the F16 key to confirm.
Method Three Shutdown via the control panel.
First, switch the machine's startup mode to Manual. Press the power switch once; the function display will show '0'. Press the power switch again to confirm the shutdown operation.
Shortly after confirming the shutdown operation, the function display will show 'DXXX XXXX', indicating that the system is shutting down. No further action is required at this point.
III Viewing System Jobs
AS/400 provides a powerful command, WRKACTJOB. This command allows users to view all active jobs currently running in the system, enabling users to assess system performance by observing metrics such as CPU utilization and response time.
After entering this command, the system displays the following:
Work with Active Jobs IBMCHINA
00/04/19 10:08:33
CPU %: .0 Elapsed time: 00:00:00 Active jobs: 123
Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Opt Subsystem/Job User Type CPU % Function Status
QBATCH QSYS SBS .0 DEQW
QCMN QSYS SBS .0 DEQW
QCTL QSYS SBS .0 DEQW
QPFRCOL QPGMR ASJ .0 PGM-QPMLWAIT EVTW
QSYSSCD QPGMR BCH.0 PGM-QEZSCNEP EVTW
QDOMINOHT QSYS SBS .0 DEQW
QHTTPSVR QSYS SBS .0 DEQW
DEFAULT QTMHHTTP BCH.0 PGM-QZHBHTTP TIMW
DEFAULT QTMHHTTP BCI .0 TIMWWhen this command is first run, the CPU usage for all jobs is 0%. Press F5 to refresh the display. The 'Elapsed time' at the top of the screen indicates the duration during which the WRKACTJOB command has been observing running jobs in the system. The 'CPU%' in the upper-left corner represents the average CPU utilization during that period. Therefore, to view the current moment's CPU utilization using this command, press F10 to restart the statistics.
When the command is first run as shown above, six columns are displayed. Below is an explanation of each:
- Subsystem/Job: Subsystem name or job name. By default, entries are arranged by subsystem name. All jobs within the same subsystem are displayed indented beneath that subsystem.
- User: The username that started the subsystem/job.
- Type: Type of subsystem/job. The subsystem type will always be SBS. Job types vary; the two common types are BCH and INT, representing batch jobs and interactive jobs, respectively.
- Function: The command submitted by the current job or the program name. This item applies only to jobs.
- Status: Current status of the subsystem/job.
After running the WRKACTJOB command, you can press F11 to display the system resource usage of the job during the statistical period. After pressing F11, the display appears as follows:
--------Elapsed---------
Opt Subsystem/Job Type Pool Pty CPU Int Rsp AuxIO CPU %
QINTER SBS 2 0 .7 0 .0
QPADEV0011 INT 4 20 .3 7 .0 7 .0
QPADEV0013 INT 4 20 .8 41 .0 47 .0
QSERVER SBS 2 0 .3 0 .0
QPWFSERVSD BCH 2 20 .1 0 .0
QSERVER ASJ 2 20 .1 0 .0- pool: Number of the memory pool where the subsystem/job is running.
- Pty: Job priority. The range is 0-99, where 0 is the highest priority and 99 is the lowest.
- CPU: CPU processing time consumed within the statistical period, measured in seconds.
- Int: Number of times user intervention was required for an interactive job within the statistical period. This item is displayed only for interactive jobs.
- Rsp: Average response time for interactive jobs. This field is blank for non-interactive jobs.
- AuxIO: Number of disk input/output operations performed by the job during the statistical period.
- CPU%: Percentage of CPU utilized during the statistical period.
If you notice a significant slowdown in system response during daily operations, use the WRKACTJOB command to check the jobs in the system. If you find an unnecessary job consuming excessive CPU, first determine the job's status to confirm if this is normal. For example, immediately after system IPL, it is normal for the system job SCPF to consume a large amount of CPU. If you determine the job is abnormal or decide to terminate it, enter 4 in the Opt column on the left of the job and press F4. The End Job menu will then appear, displaying the following:
Job name . . . . . . . . . . . . > QPADEV0011 Name User . . . . . . . . . . . . . > IBM Name Number . . . . . . . . . . . . > 035604 000000-999999 How to end . . . . . . . . . . . *IMMED *CNTRLD, *IMMED Delay time, if *CNTRLD . . . . . 30 Seconds Delete spooled files . . . . . . *NO *NO, *YES Maximum log entries . . . . . . *SAME Number, *SAME, *NOMAX Additional interactive jobs . . *NONE *NONE, *GRPJOB, *ALL
In the 'How to end' row, enter *IMMED and then press the Execute key to terminate the job.
Additionally, the WRKACTJOB command consumes significant system resources. Unless necessary, do not run this command when system utilization is high.
Finally, note that terminating a job to improve system response speed applies only to cases where the job is consuming excessive CPU. However, sometimes the system may exhibit near-zero CPU utilization while still responding slowly. In such cases, check for LOCKs in the system causing most jobs to wait. If this occurs, the LOCKs must be resolved; otherwise, the system may only be recoverable via manual IPL.
IV. Viewing Disk Status
1 WRKSYSSTS
AS/400 provides the WRKSYSSTS command for users to view system status. After running this command, the system displays the following:
% CPU used . . . . . . . : 25.8 Auxiliary storage: Elapsed time . . . . . . : 00:00:00 System ASP . . . . . . : 10252 M Jobs in system . . . . . : 118 % system ASP used . . : 45.9193 % addresses used: Total . . . . . . . . : 10252 M Permanent . . . . . . : 3.316 Current unprotect used : 409 M Temporary . . . . . . : .308 Maximum unprotect . . : 415 M
Type changes (if allowed), press Enter.
System Pool Reserved Max -----DB----- ---Non-DB--- Pool Size (K) Size (K) Active Fault Pages Fault Pages 1 20292 11225 +++ .0 .0 .0 .0 2 100251 0 8 .0 .0 .0 .0 3 1310 0 4 .0 .0 .0 .0 4 9219 0 8 .0 .0 .0 .0
The first six lines of the display show the current system status. The subsequent lines relate to system performance and are not elaborated here.
The upper-right section of the screen displays Auxiliary Storage. The five rows in that column are related to disks.
- System ASP: Disk capacity of the system operating system partition. For most users, there is only one partition in the system, the operating system partition. Therefore, under normal circumstances, this value refers to the available capacity of all disks in the system.
- %system ASP used: Current disk utilization rate.
- Total: Total capacity of all disks in the system. If the system contains user partitions, this value should be greater than the System ASP size. If there are no user partitions, it should equal the System ASP.
- Current unprotect used and Maxium unprotect: For RISC-based machines, these refer to the current and maximum allowed space for storing temporary files. After each IPL, the system automatically clears temporary files. However, since system jobs also generate temporary files, the space occupied by current temporary files will never be zero. Regarding maximum temporary file space, the system automatically allocates a region for temporary file usage upon each startup, so this value will also not be zero. For CISC-based machines, these values are valid only if disk checking and protection are enabled.
2 WRKDSKSTS
The WRKDSKSTS command allows viewing the working status of all disks. The display appears as follows:
Size % I/O Request Read Write Read Write % Unit Type (M) Used Rqs Size (K) Rqs Rqs (K) (K) Busy 1 6713 7516 41.7 .0 .0 .0 .0 .0 .0 0 2 6713 7516 41.7 .0 .0 .0 .0 .0 .0 0 3 6713 7516 41.7 .4 4.0 .4 .0 4.0 .0 0 4 6713 7516 41.7 .8 4.0 .8 .0 4.0 .0 0
Using this command, you can view the working status of each disk, including disk model, capacity, current utilization, I/O request count, average data volume per I/O request, read request count, write request count, average data volume per read request, average data volume per write request, and disk busy level. After pressing F11, the display appears as follows:
--Protection-- Unit ASP Type Status Compression 1 1 DPY ACTIVE 2 1 DPY ACTIVE 3 1 DPY ACTIVE 4 1 DPY ACTIVE
At this point, you can view the status of each disk. If the status is ACTIVE, the disk is functioning normally. If it is FAILED, the disk is damaged and needs replacement. In this case, please call the IBM service hotline 8008106677 to seek IBM technical support.
V. Viewing System Logs
AS/400 has a comprehensive security mechanism that logs many activities in the system. On AS/400, there are primarily three types of logs: Current Job Log, History Log, and Error Log.
1. Current Job Log and System Log
The Current Job Log records only the work of the current job. For interactive jobs, this log records all commands submitted and their results from login until logout. Generally, after a user logs out, AS/400 does not retain this user's Current Job Log. If a user wishes to retain the log, they should enter the command SIGNOFF *LIST upon logout. At this point, the Current Job Log will be retained as a spooled file in the output queue.
To display the Current Job Log, enter the command DSPJOBLOG. The system displays the following:
Display Job Log
System: XXXXXXXX
Job . . : QPADEV0017 User . . : WQ Number . . . : 0364953> DSPJOBLOG
At this point, only the most recently entered command (DSPJOBLOG) is displayed. To view previous logs, press F10 once. The display then changes as shown below:
Display All Messages
System: XXXXXXXX
Job . . : QPADEV0017 User . . : WQ Number . . . : 0364953> DSPJOBLOG
Then press the Page Up/Page Down keys to view all logs.
Additionally, using the CALL QCMD command allows users to view all commands entered since the current login. Upon first entering this command, the system displays (No previous commands or messages). Pressing F10 once thereafter lists all commands entered since login.
The History Log records all events that have occurred in the system. Through the History Log, users can view events that happened several hours or days ago. The command to view the History Log is DSPLOG. If this command is entered directly, the system displays all logs available for the current day. To selectively display logs within a specific time period, press F4 after entering the command. There, you can input the start and end dates and times. After completion, press the Execute key.
All records in the log are equivalent to messages (Message) and can be viewed using the method for viewing messages.
2 Error Log
The error log is a feature of System Service Tools (SST) in AS/400. It records all system errors. The method to view logs in SST is as follows:
Enter the command STRSST in the AS/400 command line to start SST.
Select 1. Start a service tool
Select 1. Product activity log
Select 1. Analyze log
In the Log option, select 1. All logs, then enter appropriate dates in the start and end date fields, and press the Execute key. In the Select Analysis Report Options option, do not change any default settings; press the Execute key directly. At this point, you can see the error codes in the log. If you want to view the specific content, enter 5 in the Opt column and press the Execute key.
Not all records in the error log represent true system errors. Some are caused by improper operation, while others are caused by external environmental factors, such as communication line signal distortion. Therefore, when you see many errors in the system, do not panic; analyze each problem specifically. If there are unclear points, call the IBM service hotline at 800-810-6677 to seek IBM technical support.
AS/400 Basic Fault Diagnosis
I. General Faults
1. Unable to access the LAN
Generally, inability to access AS/400 from the LAN or from AS/400 to the LAN is caused by incorrect configuration.
First, enter the command WRKCFGSTS *LIN, then find the line description configured for the LAN. The system default line description is ETHLINE; for Token Ring networks, it is TRNLINE, as shown below:
__ QESLINE VARIED OFF __ QTILINE VARIED OFF __ Q1PLIN VARIED OFF __ ETHLINE ACTIVE __ ETHLINET ACTIVE __ ETHLITCP ACTIVE QTCPIP QTCP 026752
Opt Description Status -------------Job--------------
Generally, each normally functioning line will display three indented lines similar to the one above. From top to bottom, these three lines represent the Communication Line (Line), the Controller on the line (Controller), and the device controlled by the controller (Device). Each line will have various states such as ACTIVE, VARY OFF, VARY ON, PENDING, etc. Furthermore, when the state is ACTIVE, jobs from devices currently using that line will appear in the Job column. Normally, this job is the QTCPIP job submitted by the QTCP user, as shown above.
If the line and controller states are ACTIVE or VARIED ON, but the device state is VARIED ON, it indicates that the TCP/IP network protocol stack has not started. At this time, enter the command STRTCP. If the line state is VARIED OFF, it indicates that the line is disabled; you need to select option 1 next to the line to enable it.
If the line state is RCYPND, generally there is a problem with the network cable or the HUB/switch port that needs to be checked. After checking, first select option 2 next to the line; wait until the state becomes VARIED OFF, then select option 1.
Note: Some network cards have two indicator lights. When one light is yellow, it does not indicate a network card failure. The system uses the blinking of the two lights to indicate the current working status: Full Duplex/Half Duplex, 10M/100M.
2. Control Panel No Display
Control panel no display is usually a power issue. First, check if the power cord is plugged in properly, and verify that the input voltage at the AS/400 power input terminal is 220V AC at 50Hz. For the four models 270, 820, 830, and 840, the control panel will only display after approximately 5 seconds after the power cord is plugged in. Therefore, when the machine is first powered on, the control panel may still have no backlight. If the input voltage is normal but there is still no display, the AS/400 power supply or control panel may be faulty. Please call the IBM hotline at 800-810-6677 to request IBM engineer support.
II. System Fault Light On
Both software and hardware faults on AS/400 can cause the system fault light to turn on. When the fault light is on, an 8-digit code will appear on the function display of the control panel. First, record this code, then perform the following operations on the control panel:
Press the Up Data Display key; the control panel will show 12-2 (or 12-3). Press the Execute key once; an 8-digit code will appear on the function display. Record this code. Press the Up Data Display key again; the control panel will show 13-2 (or 13-3). Press the Execute key once more; another 8-digit code will appear on the function display. Record this code. Repeat step B until you record the code obtained after pressing the Execute key when the control panel displays 20. (From 12 to 19, the control panel will show XX-X format, but at 20, only 20 will appear.)
Note: For the four models 270, 820, 830, and 840, when the fault light is on, a 32-digit code may sometimes appear on the control panel, consisting of only four parts: 11, 12, 13, and 20.
After obtaining the above codes, please call the IBM hotline at 800-810-6677 to request IBM engineer support.
III. Summary
| Fault Phenomenon | Possible Fault Causes | Solution |
| Unable to access the LAN | Network adapter line description setting abnormal | Check line description, change line status |
| Network cable or HUB/Switch port setting | Replace network cable, check switch port settings, check HUB port status | |
| Control panel no display | No power input | Check power cord, input voltage |
| Machine performing internal startup | Wait at least 5 seconds | |
| System fault light on | Hardware failure | Call the IBM hotline for technical support |
AS/400 data backup
I. Backup Object or Library
Use the SAVOBJ command to backup objects. After entering the command, press F4. The screen displays as follows:
Objects . . . . . . . . . . . . Name, generic*, *ALL
+ for more values
Library . . . . . . . . . . . . Name, generic*
+ for more values
Device . . . . . . . . . . . . . Name, *SAVF
+ for more values
Object types . . . . . . . . . . *ALL *ALL, *ALRTBL, *BNDDIR...
+ for more valuesThe command to backup a library is SAVLIB. After entering the command and pressing F4, the screen displays as follows:
Library . . . . . . . . . . . . Name, generic*, *NONSYS...
+ for more values
Device . . . . . . . . . . . . . Name, *SAVF
+ for more valuesIn the Objects, Library, Device, and Object types rows, enter the name of the object to be backed up, the name of the library containing the object (or the name of the library to be backed up in the case of backing up a library), the device name of the tape drive, and the type of object to be backed up. If multiple values need to be entered, type a plus sign (+) on the row below and press Enter. A screen will pop up to facilitate entering multiple values. After all entries are complete, press Enter to return. Once all content has been entered, press Enter again. If a tape drive name is entered in the Device row, the following additional rows will appear on the screen.
Volume identifier . . . . . . . *MOUNTED
+ for more values
Sequence number . . . . . . . . *END 1-16777215, *END
Label . . . . . . . . . . . . . *LIB
File expiration date . . . . . . *PERM Date, *PERM
End of tape option . . . . . . . *REWIND *REWIND, *LEAVE, *UNLOAD
Use optimum block . . . . . . . *YES *YES, *NOThe Volume identifier parameter in this section is very important. This parameter refers to the volume label of the tape used during backup. By default, the system uses the tape currently inserted in the tape drive. To ensure the system confirms the correct tape is used for each backup, you can enter the tape's volume label in this row. Typically, pressing Enter once more will submit the backup operation.
If *SAVF (backup to file) is entered, only two additional rows will appear on the screen.
Save file . . . . . . . . . . . Name Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
At this point, enter the backup file name and the library where it resides in these two rows respectively, then press Enter to submit.
II. Full System Backup
Full system backup must be submitted from the system primary console. Enter the GO SAVE command in the command line and press Enter to access the SAVE menu. Select option 21. A Save the Entire System screen will appear, listing the tasks required for a full system backup. The display is as follows:
What this option will do
- End all subsystems
- Save the Licensed Internal Code
- Save the operating system
- Save the security data
- Save the device configuration objects
- Save all user libraries (including libraries for licensed programs)
- Save all documents and folders
- Save all distribution and mail objects
- Save all directories
- Start the controlling subsystem
What this option will not do
- Save the contents of job queues, output queues, or data queues that
- exist on the system
After pressing Enter, the Specify Command Defaults screen will appear as shown below:
Prompt for commands . . . . . N Y=Yes, N=No
Check for active files . . . . Y Y=Yes, N=No
Message queue delivery . . . . *BREAK *BREAK, *NOTIFY
Start time . . . . . . . . . . *CURRENT *CURRENT, time
Vary off network servers . . . *NONE *NONE, *ALL, *LANSERVER,
*NETWARE, *BASE, *AIX,Tape devices . . . . . . . . . TAP01 Names
In the Tape devices field, enter the tape drive device name (up to four tape drive names can be entered). In the Prompt for commands field, enter N to avoid confirmation prompts for each step. In the Check for active files row, enter N so the system does not check if the tape contains content. Use default values for the remaining fields. Once you confirm the tape is inserted into the tape drive, press Enter to start the full system backup.