iSeries
Getting started with iSeries
iSeries
Getting started with iSeries
Contents
Chapter 1. Getting started with iSeries 400 . . . 1
Completing EZ-Setup: do these tasks first . . . 1
Chapter 2. Configuring your LAN console . . . 3
Chapter 3. Backing up your system . . . 5
Chapter 4. Microsoft’s Data Access Components (MDAC) . . . 7
How MDAC works on your system . . . 7
How to get MDAC. . . 7
Saving changes after installing software . . . 7
Adding electronic customer support to your system . . . 7
Chapter 5. Making your system operational . . . 9
Before you start . . . 9
Turning on the system . . . 9
Powering on the system . . . 9
Performing an Initial Program Load (IPL) . . . 10
Configuring your LAN console . . . 10
System interfaces . . . 10
Operations Navigator . . . 10
Command line interface . . . 11
Installing Management Central . . . 12
Backing up your system . . . 12
Initializing the tape for a system backup . . . 12
Performing a system backup . . . 13
Installing software . . . 14
Saving changes after installing software . . . 15
Adding electronic customer support to your system . . . 15
Configuring Universal Connection . . . 16
Configure service provider information . . . 18
Testing your connection to electronic customer support . . . 18
Configuring SNA connection to electronic customer support . . . 18
Chapter 6. System configuration concepts . . . 21
Chapter 7. System operations concepts . . . 23
Messages . . . 23
Jobs . . . 24
Objects . . . 24
Logs and journals . . . 24
Logs . . . 24
Journals . . . 25
System authorities . . . 25
Files and file systems . . . 26
Control language commands . . . 26
Command syntax . . . 26
Entering commands . . . 27
User profiles . . . 28
Printing on iSeries . . . 28
Fixes . . . 29
Installed and permanently installed fixes . . . 29
Chapter 8. Managing system operations . . . 31
Controlling jobs . . . 31
To get information about a job on your system: . . . 31
Handling messages. . . 32
To send a message. . . 32
To delete a message . . . 32
To get more information about a message . . . 32
To reply to a message. . . 32
Your system status . . . 33
User profile tasks . . . 33
Perform common user profile tasks . . . 34
Managing user profiles . . . 35
Adding and removing users from groups . . . 36
Entering personal information into a user profile . . . 37
Setting security parameters for users . . . 37
Job-related information for users . . . 38
Setting system security . . . 38
System security classes . . . 39
Setting security policies . . . 39
Setting up auditing . . . 40
Defining authorization lists . . . 41
Using the security wizard . . . 42
Starting and stopping the iSeries . . . 42
Setting up an automatic power on and off schedule . . . 43
Starting the System. . . 44
Starting the iSeries: signing on . . . 46
Starting a remote system . . . 46
Changing your system IPL from the system control panel . . . 47
System Values That Control IPL . . . 47
Changing the system during IPL (attended IPL) . . . 50
Tips for Improving IPL Performance . . . 53
Cleaning up your system to improve performance . . . 57
Changing the system password . . . 61
Working with subsystems . . . 62
Stopping the system . . . 63
Powering off the system immediately . . . 64
Using the power pushbutton . . . 64
System reference codes and primary partitions . . . 65
System reference codes and secondary partitions . . . 67
What causes an abnormal IPL? . . . 69
Managing fixes . . . 69
Common fix management tasks . . . 69
Advanced fix management tasks . . . 70
Ordering individual fixes and cover letters . . . 70
Sample cover letter and description of fields . . . 73
Ordering fixes . . . 76
Using the SNDPTFORD command to order fixes . . . 78
Preparing to install fixes . . . 79
Choosing a storage area before applying a fix . . . 79
Installing a cumulative fix pack . . . 80
Installing licensed internal code fixes . . . 82
Installing licensed program (LP) fixes . . . 83
Verifying the fix installation . . . 84
Displaying fix status . . . 85
Displaying fix information. . . 85
Removing fixes . . . 92
Loading fixes . . . 94
Applying fixes: advanced procedure. . . 95
Working with devices . . . 98
System requirements for device configurations. . . 98
Working with printer output . . . 99
ASCII LAN printing . . . 99
IPDS LAN printing. . . 100
Twinax printing . . . 100
Using Line Printer Requester/Line Printer Daemon (LPR/LPD) printing . . . 100
Setting up a remote printer . . . 101
Setting up a remote printer from the command line . . . 101
Preparing to print . . . 102
Starting printer output . . . 104
Changing a format to ASCII before printing . . . 104
How spooled files are named . . . 105
Ownership of spooled files. . . 106
Deleting printers that are no longer needed on the system . . . 106
Setting up Telnet printer pass-through . . . 106
Setting the number of virtual devices . . . 107
Virtual controllers and devices created by the system . . . 108
Activating the QSYSWRK subsystem. . . 108
Printer security considerations . . . 109
Using removeable media . . . 109
Using tapes and tape units . . . 110
General Tape Usage Information . . . 111
Storage Device Ready Conditions . . . 114
Using CD-ROM Storage . . . 116
Using Optical Media Libraries . . . 118
Tape Drive Environment and Use . . . 118
Using 1/2-Inch and Magstar MP Tape Cartridges . . . 119
Using 1/4-Inch Cartridges . . . 120
Using 8-Millimeter Tape Cartridges. . . 133
Using 1/2-Inch tape reels . . . 135
Chapter 9. Handling system problems and getting help through electronic customer support 141 Troubleshooting printer problems . . . 141
Solving problems with sending jobs . . . 141
LPR command considerations . . . 141
Common error messages . . . 142
Materials required for reporting LPR problems . . . 142
Solving problems with receiving jobs . . . 142
Materials Required for Reporting LPD Problems. . . 143
Finding a job that did not print . . . 144
On the server . . . 144
On the client . . . 144
Resolving problems with the Universal Connection wizard . . . 144
AT&T customers: . . . 146
Contacting electronic customer support . . . 146
Wait! Before You Access the Internet... . . 146
Viewing system configuration lists . . . 146
Hardware . . . 147
Software . . . 147
Troubleshooting your system . . . 147
Before you call . . . 147
Begin troubleshooting now. . . 148
Troubleshooting your system: Step 2 . . . 148
Troubleshooting your system: Step 3 . . . 148
Troubleshooting your system: Step 4 . . . 148
Troubleshooting your system: Step 5 . . . 148
Troubleshooting your system: Step 6 . . . 148
Troubleshooting your system: Step 7 . . . 149
Troubleshooting your system: Step 8 . . . 149
Troubleshooting your system: Step 9 . . . 149
Troubleshooting your system: Step 10 . . . 149
Troubleshooting your system: Step 11 . . . 149
Troubleshooting your system: Step 12 . . . 149
Troubleshooting your system: Step 13 . . . 149
Troubleshooting your system: Step 14 . . . 150
Troubleshooting your system: Step 15 . . . 150
Troubleshooting your system: Step 16 . . . 150
Troubleshooting your system: Step 17 . . . 150
Troubleshooting your system: Step 18 . . . 151
Troubleshooting your system: Step 19 . . . 151
Analyzing problems with a symptom . . . 152
Procedure 1: Recovering from system power problem . . . 153
Procedure 2: Recovering when attention light is on or the System Reference Code (SRC) is displayed . . . 153
Procedure 2A: Recovering when Operations Console Remote Control Panel feature is not working properly. . . 156
Procedure 3: Recovering when control panel pushbuttons or lights are not working properly . . . 156
Procedure 4: Recovering from IPL or system failure . . . 156
Procedure 5: Recovering from workstation failure . . . 157
Procedure 6: Recovering from tape or optical device problem . . . 158
Procedure 7: Recovering from disk or diskette drive problem . . . 158
Procedure 8: Recovering from communication problem . . . 158
Procedure 9: Recovering from system hang or loop condition . . . 158
Procedure 10: Recovering from intermittent problem . . . 159
Procedure 11: Recovering when system console did not vary on . . . 159
Problem summary forms . . . 160
Problem summary form for systems with a single partition (except Model 270 and 8xx) . . . 160
Problem summary form for systems with multiple partitions (except Model 8xx) . . . 161
Problem summary form for Model 270 and 8xx systems with a single partition . . . 162
Problem summary form for Model 8xx systems with multiple partitions . . . 163
Accessing panel functions on a secondary partition . . . 164
Analyzing a new problem . . . 165
Reporting hardware and software problems . . . 165
Replacing Battery Power Unit on Models 5xx, and Tower FC507x and FC508X . . . 170
Performing a main storage dump . . . 171
Determining the primary or alternate consoles . . . 174
Chapter 1. Getting started with iSeries 400
Whether you are new to the iSeries or an experienced professional, this topic is a useful starting point for all kinds of information for handling simple and complex tasks on your system.
Use this information to get to know your system—how it works, how the pieces interact, and how you can customize it to better meet your needs. Learn the terminology, and see how this platform is different from others you may have worked on. Explore system concepts and learn to manage the day-to-day business of your system. Identify some of your common administrative tasks, and how you can accomplish them. If you run into problems, use the troubleshooting guide to get back on track.
Making your system operational Complete these tasks when you are ready to start your system for the first time. System configuration concepts Your system configuration includes the hardware (system and any devices) and
the software (operating system). Discover what is under the″hood″of your new system.
System operations concepts Focus on some of the most important concepts you need to know to operate your system. See how your new system compares to the competition.
Managing system operations Perform a system performance check or set up user profiles. Understand the security features incorporated into your system and how you can take full advantage of them.
Handling system problems and getting help
If you’ve lost a print job, or want to know what those cryptic error messages mean, and why your system is acting weird, you need troubleshooting. When a problem arises, you can either solve it yourself or get assistance, depending on the nature of the problem.
Print this topic for future reference.
Completing EZ-Setup: do these tasks first
Now that you have successfully completed EZ-Setup, you need to complete the following tasks to bring your system online for the first time. Once completed, your system will be configured, backed up, and connected to IBM support services.
1. Configure your LAN console
If you did not configure your local area network when prompted in EZ-Setup, do so now. 2. Back up your system
Perform an immediate system backup to save your new configuration and create a regular backup schedule.
3. Install MDAC
Add this component to enhance your database functionality. 4. Save changes to your system
Save the changes you have just made to your system. 5. Add electronic customer support
Run the wizard to set up a support connection to IBM.
Additional information on this topic can be found in these sources:
Chapter 2. Configuring your LAN console
Operations Console allows you to use your PC as the system console, perform control panel functions, or both. With Operations Console, you can administer iSeries servers that are on your local area network (LAN). You can also remotely administer several iSeries servers at different locations, including other LANs.
Chapter 3. Backing up your system
When you create a system backup, you create a snapshot of your system information at a particular point in time. The system backup preserves all of the system configuration information that you have made so far. You can expect to spend between 30 minutes and several hours performing this backup, but it is time well spent.
Backing up a system is not a difficult process, but it is one that can easily be forgotten as you attend to more pressing tasks. Scheduling backups can not only ease your system maintenance workload by automating a commonly performed function, but help you address problems with data corruption, power outages, and other unforseen situations that may damage your system data. The backup schedule you create plays an important part of that strategy.
Backup, Recovery and Media Services (BRMS) will help you structure your backup tasks, and manage your backup media. You can use BRMS to restore data, recover an entire system, and perform
maintenance tasks. BRMS is not intended to replace your backup and recovery strategy, but it can be a useful tool for implementing that strategy.
Backing up your system initially involves these steps: 1. Initializing the tape
2. Performing the backup
Additional information on this topic can be found in these sources:
Backing up your system
Planning a backup and recovery strategy Backup, Recovery, and Media Services
Chapter 4. Microsoft’s Data Access Components (MDAC)
One of your system’s key roles is as a database server. The DB2 database that is integrated into your system plays a vital role in managing client information, key business data, and historical archives.
How MDAC works on your system
MDAC adds important functionality to clients on your system. MDAC enables the universal data access required in client/server environments, and includes a number of Microsoft data components.
Some database components, such as OLE DB which provides a connection between relational and non-relational information sources, including traditional databases, require MDAC to be installed on clients on the system. The minimum level required for this release is MDAC version 2.5.
How to get MDAC
Download and install the most recent version of MDAC on your clients to ensure that all database
components function effectively. You can obtain the most current version of MDAC at no additional charge
from the Microsoft site .
Additional information on this topic can be found in these sources:
DB2 Database information
Saving changes after installing software
After finishing the Checklist for completing installation in the Software Installation manual , you must save the changes you have made to your system to make them permanent. Follow these steps:
1. On the command line, type: PWRDWNSYS *IMMED.
2. Once the machine is powered off and01 BNis on the remote control display on the system, press the white button on the front of the system to power on the machine. The system takes approximately 5 to 10 minutes to power on and completely restart.
3. Once the Function/Data display readsA900 2000or 01 BN, the system has completed the restart and you are finished installing additional software.
4. Back up your system to save the installed programs.
Adding electronic customer support to your system
From time to time, your system may experience problems that need attention from IBM’s support services. Electronic customer support is available to help you keep your system operating efficiently. If there is a system hardware or software problem,
IBM Customer Engineers can access your system directly to rapidly diagnose and solve the problem.á
Electronic customer support lets you:
v Order and install fixes
v Access the question-and-answer (Q & A) database
v Access local service and IBM product information
v Access problem analysis reporting and management
You can access electronic customer support in one of these ways: 1. Using Universal Connection.
Universal Connection is TCP/IP-based, and is configured using a graphical interface that allows you to choose how you connect to IBM: direct dial-up via the AT&T Global Network Service, through an existing Internet service provider (ISP), or via a virtual private network (VPN). This flexibility lets you choose the most convenient solution for your organization, while still providing a secure connection. For the majority of users, this option is the fastest, most convenient method of accessing electronic customer support.
2. Using the traditional connection.
This route is available to users who use Systems Network Architecture (SNA) and a Synchronous Data Link Control (SDLC) capable modem.
Additional information on this topic can be found in these sources:
Installing Fixes Extreme Support
Chapter 5. Making your system operational
Your system is ready to go—or is it? You’re ready to bring your system online. Once you have completed these tasks, your system will be configured, backed up, and connected to IBM support services.
Depending on the state of your system (is it powered on, are you upgrading from a previous release), you may need to complete some or all or of the tasks below to make your system operational.
Before you start
Do you want to start and configure the system yourself? If you prefer to use a wizard, obtain Client Access Express. Client Access Express’s EZ-Setup simplifies the process of setting up a new server.
Working from Operations Console? Get information on setting it up now.
Turn on the system Your system is more complicated to start and stop than a PC. Get the information you need to power it on safely.
Configure your LAN console
Configure your local area network to allow a PC to act as a console. Install the interfaces You need a way to communicate with your system. IBM gives you two. Install Management Central Plan now to simplify future administrative tasks.
Back up your system Perform an immediate system backup to save your new configuration and create a regular backup schedule.
Install software Add new licensed programs to your new system. Add electronic customer
support
Run the wizard to set up a support connection to IBM
Turning on the system
If you have just completed the cabling process, you are ready to turn the system on for the first time. These are the primary tasks to complete: turning the power on and performing an Initial Program Load.
Powering on the system
These are the steps you need to complete to power on your system for the first time.
1. Locate andáidentify some of the primary components on your control panel. The key components are:
v Power on light:áindicates when power has become available to the unit.
v Character display: displays the SPCN address, power status, or an SPCN reference code. v Power switch:ácontrols the power for everything installed in the unit.
v Mode button: allows you to scroll through different operating modes.
2. Turn on the power of any display stations, tape devices, and controllers you will need to operate. 3. Set the mode to Normal.
4. Turn the unit on using the Power Switch.áConfirm that the unit has power by noting theáblinking of the Power on light. If the unit is functioning properly, the Character display will display its normal running message:*rruwhererris the rack address (an integer from 01 to 63) andu indicates the SPCN port the unit is connected, and ranges from 1 to A (1 through 10).
If the Power on light does not blink to indicate that power is being received by the unit, and there is no data displayed in the Character display, verify that your system power cables are properly connected to electrical outlet and that all cables are properly connected to the system before trying again.
If the Character display contains a message that does not conform to the standard, go to the Getting Help section immediately. Do not attempt to rebootáthe systemáuntil you have determined the cause of the problem!
Now that the iSeries is powered on correctly, you are ready to begin your Initial Program Load
Performing an Initial Program Load (IPL)
Once your iSeries has powered on successfully, you are ready to perform an Initial Program Load (IPL). During an IPL, the system programs load from the system auxiliary storage and the system hardware is checked. If you have not correctly cabled your system, it will not recognize some of the installed hardware, and you will need to re-IPL in order for that hardware to be recognized on the system.
Your system is now ready to perform a normal, unattended IPL. In other words, the system will complete this IPL automatically because you set the mode to Normal. Once it is complete, a signon display will appear on your station.
1. Enter your user ID and press Enter.
You should now be taken to the main menu display. 2. Install the interfaces necessary to interact with the system.
Additional information on this topic can be found in these sources:
Starting and stopping the system
Changing operating modes and IPL types
Configuring your LAN console
Operations Console allows you to use your PC as the system console, perform control panel functions, or both. With Operations Console, you can administer iSeries servers that are on your local area network (LAN). You can also remotely administer several iSeries servers at different locations, including other LANs.
Follow the instructions in Client Access Express -> Operations Console.
System interfaces
You have a system made up of hardware and software. But how do you interact with that system? How do you get things to work? How do you monitor what is happening across the system? How do you check job performance?
The answer is simple: you need an interface. Even better, have two interfaces.
Operations Navigator
Operations Navigator is a graphical user interface that provides a connection to your system that looks and feels familiar to those experienced with Microsoft Windows platforms. You get point and click
functionality without sacrificing speed and power. If you are comfortable in Windows, you will feel right at home with Operations Navigator.
This example demonstrates the ease with which you can visualize and manage files, jobs, and security, among other components. Operations Navigator will soon become a familiar part of your PC desktop.
Command line interface
The command line interface (also known as a character-based display or emulation), offers another connection to your system. This interface takes longer to fully master, but may be preferred by those who are more comfortable typing commands rather than pointing and clicking.
+---+ | Sign On | | System . . . : SYSTEM01 | | Subsystem . . . . : QBASE | | Display . . . : DSP01 | | | | User . . . __________ | | Password . . . | | Program/procedure . . . __________ | | Menu . . . __________ | | Current library . . . __________ | | | | | | | +---+
Like Operations Navigator, the command line interface emulation is installed as a part of Client Access Express.
Both Operations Navigator and the command line interface can operate together on the same desktop, the same way that Windows and the DOS command prompt do. For many functions, Operations Navigator is all you need to accomplish tasks; for some others, the command line interface will be required. Experience will help you decide which to use in every situation.
Additional information on this topic can be found in these sources:
Operations Navigator home page Operations Console
Installing Management Central
Some functions of Management Central are optionally installable components of Operations Navigator, the graphical user interface (GUI) for iSeries 400. When you install Operations Navigator, be sure to choose to install Operations Navigator Base Support (which includes most of the Management Central functions), plus Commands, Packages and Products, and Monitors.
Follow the instructions in Operations Navigator -> Management Central.
Backing up your system
When you create a system backup, you create a snapshot of your system information at a particular point in time. The system backup preserves all of the system configuration information that you have made so far. You can expect to spend between 30 minutes and several hours performing this backup, but it is time well spent.
Backing up a system is not a difficult process, but it is one that can easily be forgotten as you attend to more pressing tasks. Scheduling backups can not only ease your system maintenance workload by automating a commonly performed function, but help you address problems with data corruption, power outages, and other unforseen situations that may damage your system data. The backup schedule you create plays an important part of that strategy.
Backup, Recovery and Media Services (BRMS) will help you structure your backup tasks, and manage your backup media. You can use BRMS to restore data, recover an entire system, and perform
maintenance tasks. BRMS is not intended to replace your backup and recovery strategy, but it can be a useful tool for implementing that strategy.
Backing up your system initially involves these steps: 1. Initializing the tape
2. Performing the backup
Additional information on this topic can be found in these sources:
Backing up your system
Planning a backup and recovery strategy Backup, Recovery, and Media Services
Initializing the tape for a system backup
Before beginning the backup, have your backup media ready. You will need blank tape cartridges to perform the backup. You may need several tapes, depending on the type of tape device you have and the size of your system.
Prepare the tape for backup
1. Label the blank tape cartridges that you use for saving the system information (for example: SAVT01,
SAVT02).
2. Insert the tape into the iSeries and closeáthe tape unit door.
The tape unit may wind and rewind the tape to set the tension. This takes approximately three minutes. You do not need to wait for the tape unit to stop to proceed to the next step.
Locate the initialize tape display
1. Open the command line interface.2. On the command line Main Menu, type 3.
Press Enter. The General System Tasks display appears. 3. On the command line, type 8.
Press Enter. The Device Operations display appears. 4. On the command line, type 4.
Press Enter. The Tape display appears. 5. On the command line, type 2.
Press Enter. The Initialize Tape display appears.
Set the tape initialization parameters
1. Type the recommended value for the following parameters:
v Tape device:TAP01(the name of the device you are using)
v New volume identifier:savt01(the same as the label on the tape)
v Check for active files:*no
2. Leave all other values as they appear in the display.
Complete the tape initialization
1. Press Enter. The tape unit rewinds the tape which takes approximately one minute. The light on the tape unit goes off.
2. The Tape menu appears with the following message:Volume SAVT01 prepared for operation with
owner ID*BLANK
3. Repeat these steps to initialize additional tapes, then perform the backup.
Performing a system backup
Periodically, and always after installing software, you should back up your system to preserve important data and configuration information. Consider the impact to your business operations if you lose all of the information contained on your system through fire, flood, or vandalism. A backup of vital information might save your business from ruin with only relatively minor disruption in service. Backups should play a key role in any business’s disaster recovery plan.
Beginning the backup
1. From the main command line, type GO TAPE. 2. At the Tape display, type 4.
3. Press Enter.
4. At the Save display, type 2. 5. Press Enter.
The Save the Entire System display explains what happens during the save process. Read it carefully before proceeding.
Configuring the backup
From the Specify Command Defaults display, complete the following tasks: 1. Type the recommended value for the following parameters:
Parameter Recommended Value
Tape devices TAP01
Prompt for commands N
Check for active files N
Message queue delivery *BREAK
Start time *CURRENT
2. Press Enter two times. If any display appears, follow the instruction on that display. The Save display appears with the following message:Save or restore option completed
successfully
3. Remove the tape when the light on the tape unit goes off. 4. Press F3 to return to the Main Menu.
You have now created a system backup. Ensure that all of your tapes are marked and stored in a safe, accessible place. Create a duplicate set of tapes and store them at a secure location off-site. To
streamline the backup procedure, establish a backup schedule. This schedule should be part of a larger backup and recovery strategy.
Consider your backup and recovery strategy
What would happen to your business if a security breach allowed a malicious user to corrupt client files? Would you be able to recover that information or would your business collapse in chaos? What would happen if a power failure or flood damaged your system? How would you respond?
An effective backup and recovery strategy takes all kinds of scenarios into account, and plans a response to each. This strategy should be tailored to your business’s needs and particular circumstances. A good strategy can’t be thrown together in a few minutes. It might require input from a variety of people at all levels of your organization, and be a time-consuming venture. However, the alternative is even more time-consuming: responding to a major catastrophe without any planning or strategy to guide you!
Create your own backup and recovery strategy now.
Additional information can be found in these sources:
Planning a backup and recovery strategy
Backup and Recovery Guide Backing up your system
Installing software
From time to time, you may choose to install a licensed program that did not come pre-loaded onto your system. Software installation takes careful planning to minimize downtime and maximize efficiency.á
The steps required for planning and installing software are the same for your first installation as they are for your hundredth.
1. Preparing for the installation
2. Performing the installation
Once you have completely planned the installation, you are ready to actually install the software. 3. Saving changes after the installation
Save the changes you have just made to your system.
Additional information on this topic can be found in these sources:
Managing software and licensed programs
Saving changes after installing software
After finishing the Checklist for completing installation in the Software Installation manual , you must save the changes you have made to your system to make them permanent. Follow these steps:
1. On the command line, type: PWRDWNSYS *IMMED.
2. Once the machine is powered off and01 BNis on the remote control display on the system, press the white button on the front of the system to power on the machine. The system takes approximately 5 to 10 minutes to power on and completely restart.
3. Once the Function/Data display readsA900 2000or 01 BN, the system has completed the restart and you are finished installing additional software.
4. Back up your system to save the installed programs.
Adding electronic customer support to your system
From time to time, your system may experience problems that need attention from IBM’s support services. Electronic customer support is available to help you keep your system operating efficiently. If there is a system hardware or software problem,
IBM Customer Engineers can access your system directly to rapidly diagnose and solve the problem.á
Electronic customer support lets you:
v Order and install fixes
v Access the question-and-answer (Q & A) database
v Access local service and IBM product information
v Access technology forums
v Access problem analysis reporting and management
You can access electronic customer support in one of these ways: 1. Using Universal Connection.
Universal Connection is TCP/IP-based, and is configured using a graphical interface that allows you to choose how you connect to IBM: direct dial-up via the AT&T Global Network Service, through an existing Internet service provider (ISP), or via a virtual private network (VPN). This flexibility lets you choose the most convenient solution for your organization, while still providing a secure connection. For the majority of users, this option is the fastest, most convenient method of accessing electronic customer support.
2. Using the traditional connection.
This route is available to users who use Systems Network Architecture (SNA) and a Synchronous Data Link Control (SDLC) capable modem.
Installing Fixes Extreme Support
Configuring Universal Connection
Unlike the traditional method, Universal Connectionáallows you to control how your business will connect to IBM’s support services. Once connected, you can access a variety of customer support options as you need them.
You can also run the Extreme Support wizard to configure Universal Connection. Extreme support also allows you to use the Electronic Service Agent, and it will collect and send data to IBM when problems are encountered.
Before you start
There are some decisions you need to make prior to running the Universal Connection wizard. During the configuration process, you will be asked to choose the type of connection you want to use for electronic customer support. That decision will depend upon your network and accessibility to the Internet from your iSeries.
v If your iSeries currently has direct (broadband with a fixed IP address or LAN with a globally routable IP address) access to the Internet (without an intervening firewall), you may want to select the Direct
connection to the Internet option. This option will allow for the fastest secure access to IBM services
and support.
v If you already have an Internet Service Provider (ISP) which your iSeries dials into, you may want to select the Dial up connection using an Internet Service Provider option. This option will support a secure connection to IBM services and support at the same time and over the same dial-up connection currently used by your iSeries to access the Internet.
v If your iSeries is not on a network, or is only on a private network, you may want to select the Dial-up
connection using the AT&T Global Network Services option. This option will provide you with a
secure dial-up connection to IBM services and support only, with no access to the Internet.
Note: In order to run the wizard, you must have installed both
Client Access Express and the optional Network component. You must also have *ALLOBJ and *IOSYSCFG authorities to run the wizard.
If you would like to configure your service provider information, do so now.
Prepare to configure Universal Connection
The tasks below will prepare you to begin configuring your connection. 1. From Operations Navigator, select the system you want to work with. 2. Expand Network.
3. Click Remote Access Services.
4. Right-click Originator Connection Profiles.
5. Select Universal Connection Wizard and begin the configuration process.
Note: If you encounter any problems while running the wizard,
go to the problem resolution section for advice, and then re-run the wizard.
Start the configuration process
The tasks below will configure your connection to Electronic Customer Support. 1. At the welcome window, click Next to start configuring.
2. Enter your service contact information in the spaces provided and click Next to continue. 3. Enter your company’s address information in the spaces provided and click Next to continue.
4. Identify the country where your system is located and click Next to continue. 5. Select the Electronic Customer Support connection and click Next to continue.
Note: If you want to configure a connection for Service Agent,
the steps below remain the same. 6. Select the type of connection that you want to use for Electronic Customer Support.
v If you have chosen to use a dial-up connection to AT&T Global Network Services, select it now and click Next to continue.
a. Select your hardware resource and click Next to continue.
b. Identify the line description to use (this may take you through several wizard panels). After completing every panel, click Next to continue.
– If multiple PPP lines already exist for that resource, you will be asked to select an existing one or to create a new one.
– If only one already exists, it will be used.
c. Select the appropriate AT&T location to dial. Modify the telephone number as appropriate (remember to add any required prefixes to the phone number once it has been selected) and click Next to continue.
d. Choose a backup phone number from the available list and click Next to continue.
e. (optional) Select the modem you would like to use from the available list. If you selected an internal modem as your hardware resource, the wizard will not display this screen. Click Next to continue.
v If you have chosen to use a Dial up connection using an Internet Service Provider, select that option now and click Next to continue.
a. Select new or existing dialup connection and click Next to continue.
– If you select an existing connection, the wizard will take you to the steps described below in
″Complete the configuration″.
– If you select a new connection, the wizard takes you to step b. b. Enter a name for the new Profile and click Next to continue. c. Select your hardware resource and click Next to continue.
d. Identify the line description to use (this may take you through several wizard panels). After completing each panel, click Next to continue.
– If multiple PPP lines already exist for that resource, you will be asked to select an existing one or to create a new one.
– If only one already exists, it will be used.
e. Enter the telephone number used to connect to your ISP (remember to add any required prefixes to the phone number) and click Next to continue.
f. Enter the account information provided by your ISP and click Next to continue.
g. (optional) Select the modem you would like to use from the available list. If you selected an internal modem as your hardware resource, the wizard will not display this screen. Click Next to continue.
v If you have chosen to use a Direct connection to the Internet, select that option now and click
Next to continue.
a. Select the TCP/IP interface (address) that you will use. b. Click Next to continue.
Complete the configuration
The tasks below allow you to confirm the choices you have made during the configuration process, and then test the resulting connection.
1. The next dialog summarizes the choices you have made during the configuration process. Verify that the information is correct. If it is not, click Back to make the necessary corrections.
2. Click Finish when you are satisfied that the information is accurate.
3. Test your connection now to verify that the configuration has been successfully completed. 4. Test your electronic customer support connection.
Configure service provider information
Occasionally, you may need to contact a service provider directly, over the telephone, for assistance. Complete the steps below to configure voice contacts for service and support:
1. On the command line of the main menu, type: WRKCNTINF and press Enter. The Work with Support Contact Information display appears.
2. On the command line, type 6 (Work with service providers), and press Enter. 3. Select option 2 to change the *IBMSRV Control Point Entry, and press Enter. 4. The Change Service Provider display appears.
If you are installing this system in the United States, type the following on the Change Service Provider display:
Hardware service: 1-800-426-7378 Software service: 1-800-237-5511
If you are not installing this system in the United States, call your service representative for the service telephone numbers.
5. Press Enter.
6. Press F3 (Exit) to return to the Work with Support Contact Information display.
Testing your connection to electronic customer support
To ensure your connection to Electronic Customer Support is functioning properly, complete the test described below. Upon receiving your request, an IBM service representative will telephone you.
Connection/Registration Test
1. The Send Test Request display should be before you.
If this screen does not appear, or you have previously set up Electronic Customer Support, follow this procedure:
a. Go to the main menu.
b. On the command line, type SNDSVRQS *TEST. c. Press Enter.
2. Press Enter to submit the test.
3. Test request completeappears at the bottom of the screen. If your test does not work, then note the error message and contact your service representative.
Congratulations! You have added and tested your electronic customer support connection.
Configuring SNA connection to electronic customer support
If you intend to access electronic customer support using SNA and a synchronous (SDLC) capable modem, then complete these tasks to establish your connection to IBM’s support services.
Warning: Temporary Level 5 Header
1. Obtain primary and alternate numbers and connection information. If you do not know your service
numbers and are not in the United States, contact IBM’s Service and Support Center for more information.
2. Power on the modem that is connected to the electronic customer support cable. 3. (optional) You may choose to configure your service provider information now.
Get ready to begin configuration:
1. On your PC desktop, open Client Access. 2. Expand Operations Console.
Note: If you have not worked with Operations Console, you
need to configure a new connection to your system. A wizard takes you through the configuration process. If no wizard appears, select Connection on the tool bar and select New Connection. If you do not have Client Access Express installed, you can use telnet or a 5250 emulation session.
3. In Operations Console window, select your system. 4. From the file menu, select Connection.
5. If prompted for the DST user ID and password, type in QSECOFR for both values. 6. Select Console. The system signon screen appears.
7. Enter your QSECOFR user ID and password.
8. On the command line of the main menu, type: Call QESPHONE and press Enter.á
Configure primary telephone information: If you are installing this system in the United States, the
Change Data Area (CHGDTAARA) display may have one of these IBM service support numbers in the New Value field. If you are not in the United States, call your IBM service support telephone number.
v East of the Mississippi River: SST:18002378804
v West of the Mississippi River: SST:18005252834
The ’SST’ value is a modem command. If you receive an error after entering these values, delete ’SST’, or add the required prefix (for example, ’SST9’), and try again.
1. Type in the primary telephone number in the New Value field.
2. Fill in the telephone/connection information outlined below and press Enter.
v Ensure that the telephone number you enter follows this format:
'1234567890 '
Do not add or delete any spaces after the last digit of the telephone number. Adding or deleting characters or spaces will cause an error.
Configure alternate telephone information: The Change Data Area (CHGDTAARA) display appears
again to allow you to enter the alternate support number (if it is available in your area). To determine whether you are on the display for the primary support number or the alternate support number (if it is available in your area), check the value of the substring starting position. For the primary support number, the value is 001. For the alternate support number, the value is 051.
1. Type the alternate support telephone number (the support number you did not use as primary) in the
New Value field and press Enter.
2. Press F3 (Exit) to return to the main menu.
Configure contact information:
2. Type 2 (Work with local service information) and press Enter. 3. The Work with Local Service Information display appears.
Type 2 (Change service contact information), and press Enter. 4. The Change Service Contact Information display appears.
Type the customer information. 5. Page down to the next display.
6. Enter the correct information in the National language version and Media for mailing fixes fields. Press F4 for a list of national language versions. Press the Help key for more information about the Media for mailing fixes field.
7. Press Enter.
8. The Work with Local Service Information display appears with the following message: Data area QSSF created in library QUSRSYS.
If the contact information has been created and you change it, the following message appears: Support contact information updated.
9. Press F3 (Exit).
Test your electronic customer support connection.
Additional information on this topic can be found in these sources:
Chapter 6. System configuration concepts
Your system is up and running, but what is in the box? What kind of software was pre-installed on the system? These are the questions that new users often have about their system configuration. If someone else purchased the system, you might not even know what they ordered, or how to tell if you received everything.
You need to know more about your system’s hardware and software—fast!
Hardware Software
The hardware side of your system can be as straightforward as a single iSeries and workstation in a single room, or as complex as an iSeries in one location linked together with others across cities, countries, and continents, spanning numerous workstations and connected to local area networks and wide area networks that support a variety of platforms.
Your system, regardless of its size, is comprised of many components that work seamlessly together to meet the needs of your business. You can view your hardware configuration“Hardware” on page 147 here.
Your system is shipped with the operating system pre-installed. Additionally, it may contain optional programs that were selected prior to purchasing. You also have the choice of installing programs contained within the media distribution set. You may also have additional software packages, such as Facsimile Support for iSeries 400, iSeries 400 Toolbox for Java, NetFinity, HTTP Server for iSeries 400 MQ Series, or any of a list of programs that can be found on the IBM site . To determine which programs are currently installed on your system, follow these instructions“Software” on page 147.
Additional information on this topic can be found in these sources:
Software Installation book
Chapter 7. System operations concepts
IFS? CL? APAR? Ever feel like you are learning an entirely new language in addition to a new operating system? Relax. The terminology used by the iSeries 400 will soon become second nature, and you will be using acronyms with the best of them!
The iSeries uses some of the same operating system concepts and terminology as other platforms. Others are unique. These topics introduce you to some of the most commonly used terminology:
Go here ... For information like this ...
Messages Users communicate with each other, and your system
communicates with you, using messages.
Jobs Every unit of work performed by your system is called a
job.
Objects If it takes up memory and can be used to perform a task,
it is an object.
Logs and journals A log is a viewable history of backup, archive, recovery, and media management operations. A journal is an object that contains a record of system activity.
Authorities (security) You control access to objects, and what users can do with them.
Files and file systems Files can be easily organized and managed with Operations Navigator.
OS/400 commands Familiarize yourself with the ways commands can be entered, and in what form.
User profiles Manage user activity with profiles.
Printing See how printing works on your system.
Fixes Discover fixes and the role they play on your system.
Additional reference information can be found in the IBM glossary.
Messages
Messages are communications that are sent from one person or program to another. Your system sends
informational messages that allow you to track system activity, jobs, users, and errors, and inquiry
messages that require you to respond to system activity.
Messages that are immediate or impromptu are sent between users, and are not permanently stored on the system. Predefined messages, on the other hand, are created by the system and are stored.
Predefined messages have these components:
v a message ID, which serves as a storage identifier
v the text of the message
v a message key, which contains a queue identifier indicating the queue to which it belongs You can use these componentsáto track messages.
Additional information on this topic can be found in these sources:
Handling messages Working with messages Create a message monitor
Jobs
A job is a unit of work on your system, and may be either interactive or batch. Users who enter commands are creating interactive jobs, while batch jobs run in the background without user interaction.
The system initially places a new job in a job queue. The queue defines how many jobs that it contains may be active and running at the same time. Subsystems manage the queues and determine the queue that each job is assigned to. The subsystem also decides when each job runs. Once the job begins to run, the subsystem selectsáthe area of memory (pool) that the job will use. The overall performance of the job depends on the amount of resources available in that pool.
Jobs may be filtered in Operations Navigator by name, user, type, and so on, at the user’s convenience. Users may also choose the information that is displayed about a job. For instance, a user may choose to view the job name, type, queue, priority, and subsystem.á Or, the user may only want to view job name and status.á This flexibility enables users to view the information that is important to them as they perform jobs on the system.
Additional information on this topic can be found in these sources:
Create a job monitor
Objects
The OS/400 is an object-based operating system. An object is anything that has a name and takes up space on the system. An object can be a data file, a directory, a user, or a printer. Each has an identifying name and holds space on your system.
Objects are not limited to individual entities on your system. They can also be categorized by type. An object’s type defines its purpose and how it is used on the system. Some examples of object types:
*USRPRF User Profile
*LIB Library
Objects on this system are encapsulated. Encapsulation means that they are protected by an interface that defines the operations that can be done to that specific object.
Additional information on this topic can be found in these sources:
Commands operating on OS/400 objects Management Central and commands OS/400 objects
Logs and journals
Record keeping is an important management function. Accurate records can provide clues in the case of system failure or attempted security breach. Two key types of records on your system are logs and
journals.
Logs
A log is a database file that contains the history of backup, archive, recovery, and media management operations that may be displayed online or printed for future reference.á Logs are usedáin backup and recovery situations.á Logs can also contain information about jobs and problems
Journals
A journal is a system object that contains information about changes made to another system object, such as a database or a security-related object.á The journal can be used to recover a database.á Regular journaling speeds up database management tasks such as saves.
Additional information on this topic can be found in these sources:
Logs Journals
Job logs Database journals
History logs Backup, Recovery, and Availability
Problem logs á
Event logs á
System authorities
Protecting confidential information is the most important function of security on any system. Your system integrates security features into every component, from the hardware to the interface that users see. The
authorities that you grant to users on the system determine what they can and cannot access, change,
and delete. The system does not recognize an absence of authority. Instead, users must be specifically
excluded from accessing objects.
Example: Granting Miranda the special authority All Object gives
her access to the entire system. Miranda can now access to every object on the system, and you have no way to deny her access to specific objects, such as payroll. Similarly, granting Job Control to Dennis gives him the ability the control, change, or cancel any job on the system—his and everyone else’s.
You need to carefully consider who is given these kinds of global special authorities to minimize who has superuser access to your system. Generally speaking, users only need to be granted the privileges necessary to perform their tasks.
Authority can be granted at the object level (the container that holds objects) or at the object data level (the actual data within a container). Object level authority gives a specific user specific access to specific objects.
Example: Ophelia needs authorization to delete data in a database,
but does not need to delete tables or the database itself. She would be granted object level authority, rather than object data level authority.
Users can be granted public authority, granting them default access to objects. Users can also be added to an authorization list which gives them access to objects defined within that list. They can also receive
adopted authority when the object they have access to calls another object to complete its tasks.
Users with similar kinds of access needs can be assigned individual profiles; these profiles can then be grouped to simplify security management. See creating and managing user profiles for more details.
Files and file systems
A fileáis another kind of object on your system. Each file has a description that describes its
characteristics and how the data associated with the file is organized into records, and, in many cases, the fields in the records. Whenever a file is processed, the operating system uses this description.
Operations Navigator provides access to the integrated file system. In the integrated file system, files are sorted in a familiar, Microsoft Windows-like hierarchical structure. Viewed with Operations Navigator, files are instantly accessible, whether they are stored locally or remotely. This transparency eases management of files across a large network, because users can view the file system, select files or folders to work with, and send them instantly to multiple systems if they choose. Files can be renamed or relocated with only a few clicks of the mouse.
The integrated file system combines a Windows-like hierarchical structure with a Unix-like ability to handle file pointers, effectively merging the strengths of these two operating systems. The integrated file system has real security advantages, too. In a Unix environment, a directory is the smallest object that can be owned by a user. In the integrated file system, however, users have object-level ownership, which allows for a more granular level of security. Users can have access rights to individual files, rather than to entire directories, which eliminates some security risks, while at the same time, increasing flexibility for the administrator.
Additional information on this topic can be found in these sources:
File systems and management Integrated file system tasks Integrated file system concepts
Control language commands
By now, you have probably run across the first signs of iSeries Command language, also known as CL. Those unfamiliar with typing commands may be a bit intimidated by the seemingly-incomprehensible string of characters that you need to know in order to complete tasks on the system.
Relax—working with CL syntax“Command syntax” is not as difficult as it appears at first glance. Once you learn the trick to decoding CL, you may find yourself using it as shorthand in other situations.
Commands may be entered into source files and compiled into programs. They can be entered from the command line“Entering commands” on page 27 or run from Management Central.
Command syntax
Control language syntax follows this structure:á <command name> <parameter> <parameter> ....
CL is used to interact with and get work done on your system. Commands usually take the form of verb/noun combinations (that is, what the action is followed by what is being acted on). Examples of commands include:
Command Verb Noun
DSPMSG Display Message
CPYF Copy File
SBMJOB Submit Job
Some commands require a modifier. Examples of this kind of command include:
Command Verb Modifier Noun
Command Verb Modifier Noun
CRTCLPGM Create CL Program
EDTLIBL Edit Library List
Entering commands
As you can imagine, the possible permutations that you might need to know to be fully fluent on your system is mind-boggling! Fortunately, you do not need to memorize commands that you seldom use to complete daily tasks. The system is designed to help you find just the information you are looking for.
To enter a command, use one of these methods:
v Command prompt from Operations Navigator 1. Select Run command.
2. Enter a command and click Prompt. – Press F10 to show additional parameters. – Press F9 to show all parameters.
– Press F1 on a parameter to get specific information. – Drag the ? into the field to see possible values.
You may also be prompted to enter commands in Operations Navigator. Create and save common commands as definitions that can be used over again without retyping.
v Command prompt from a command line
1. Enter a command and press F4. A short description is given for each parameter. 2. Press F10 to show additional parameters.
3. Press F9 to show all parameters.
4. Press F1 on a parameter to get specific information. 5. Drag the ? into the field to see possible values.
v Keyword notation
– Each parameter has a name. This is a keyword.
– From the command prompt screen, press F24 (more keys), then F11 (show keywords). – You can enter a command from the command line using keyword notation. For example,
<command> <keyword>(value)<keyword>(value) ...
– The order of <keyword>(value) combinations does not matter.
v Positional Notation
– Syntax:á <command> value value ...
– The order of values is important.á They must be entered in the order they are listed on the command prompt screen.
– Each command has a limit as to how many positional parameters it can accept. For example, CRTLIB payroll *PROD ’Production Library’ produces an error.á DSPCMD <command name> displays (among other information) how many parameters it can accept.
You do not need to use all of the parameters available for a command. The system has many predefined default values, and not all of them need to be entered for every command.
Additional information on this topic can be found in these sources:
Commands operating on OS/400 objects How commands are named
User profiles
When someone asks you to prove your identity, you have the tools to do that. You can show them a birth certificate, a driving license, and other forms of identification that verify that you are indeed the person you claim to be.
Similarly, you need proper identification on your system to prove that you have access to the confidential information you need to do your job. One way this is handled is through a system of user profiles.
A user profile defines a user to your system. It includes:
v A system user profile name
v The user’s privileges and limitations
v A list of objects the user owns or is authorized to use
v A message queue
v An output queue
v Information about which groups the user is a member of (up to 16)
v Information on the user’s last signon
v Job attributes, such as description and priority, the initial program to call, and the initial library list
v National language settings
v UNIX-like attributes, such as the userid (UID), group ID (GID), and home directory, similar to those found in UNIX systems
User profiles may be linked to group profiles. In this way, all group members share common attributes, common access to specific objects, and common ownership of objects. Group profiles simplify user administration tasks.
Administrators can also use Operations Navigator’s Management Central functions to create large users and groups that allow them to create, edit, and delete both users and groups across systems.
Additional information on this topic can be found in these sources:
User profile tasks
Printing on iSeries
If you are used to printing in a Microsoft Windows environment, you will notice differences when you print on your iSeries. Rather than just initiating a print job and picking up the output, printing on your system takes an extra step and gives you increased flexibility.
The two-step printing process means that files you want to print are first spooled . During the spooling process, formatting occurs,áchanging what appears on your screen by adding line and page breaks, fonts, and so on, to create a more visually appealing end product. The spooled file then waits in an output
queue until you have decided to move it to a printer. This allows you to manage printing jobs and
resources more effectively. Spooled files may be printed locally or remotely, immediately or at a later time, putting control over print jobs entirely in your hands.áThat control is enhanced by Operations Navigator’s print functioning.áYou can easilyáview spooled information, sortáthe output queue, as well as work with those spooled files (open, hold, release, print, and send).á
Once your spooled file has been moved from the output queue to a printer, printing begins. Your formatted data is collected and printed on the printer you have specified.
Operations Navigator also streamlines the printing process by combining print writers, printer devices, and output queues intoáa logical printer.á This is equivalent toáthe WRKWTR (Work with all printers)
command.á Through either interface, printers can be started, held, taken offline, and brought online.
For more information on printing, see Working with printers.
Additional information on this topic can be found in these sources:
IBM AS/400 Printing V
IBM AS/400 Printing IV
IBM AS/400 Printing III
Physical security for printers and printer output
Fixes
Periodically, bugs are discovered in iSeries programs. IBM issues a fix (formerly called a PTF, or program temporary fix) once corrections are made and the affected programs are recompiled. Multiple fixes are bundled together to form a cumulative pack, which contains certain recommended fixes. Cumulative fix packs should be installed quarterly in dynamic environments, and less frequently in stable ones.
Cumulative fix packs should also be considered prior to making major hardware or software changes to your environment.
Fixes play an important part in your system’s maintenance strategy . They give you a chance to fine-tune your system’s operation, add additional functionality, or improve performance.
Management Central wizards simplify fix management: they allow you to make a fix available on the system immediately—or delay the installation if you choose. You can also use the compare and update wizard to compare a model system to multiple target systems to find missing or extra fixes throughout the system.
Installed and permanently installed fixes
When a fix is installed to a system, both the original and new objects are kept on the system. Logically, two copies of the code are in residence on the machine. This allows you to restart the system using either the original objects or the new objects. Installing a fix to your system gives you a secure backup while you test the new code. If the system functions incorrectly using the new code, you simply restart your system using the original code and remove the defective code.
When a fix is permanently installed on your system, only the new objects exist on the system. A fix can be permanently installed when it has been in use for a period of time and you feel confident that the chances of it being defective are small.
Available and delayed fixes
Once a fix is loaded on your system, you can choose to apply it right away or wait for a period of time before applying it. A fix can be made available if the system cannot run the old and new code at the same time. Alternatively, you can choose to delay applying a fix. The fix is then applied the next time the system is restarted.
Manage fixes with Management Central
Fix maintenance strategy Fixes and logical partitions Managing fixes
Chapter 8. Managing system operations
Okay, your system is up and running. But how do you make stuff happen? How do you transform the box from a paperweight to an effective, useful aspect of your business?
There are a number of system operations that you need to perform on a daily basis. The topics below are a great starting point to get your system working the way it needs to work.
If you want to ... Go here ...
Monitor your system Control jobs to enhance system performance, send, track and handle messages, and monitor your system’s performance.
Manage users on the system Create and manage user profiles, and set security and authorities.
Perform system tasks Discover how to start and stop your system safely. Order, install and manage fixes to keep your system running at peak levels.
Manage hardware-related activities Work with devices, set up and manage printing tasks, and use removeable media (tapes, CDs, reels, and cartridges) effectively.
Controlling jobs
Controlling how jobs are handled is one of the most common tasks you perform on your system. You can control a job’s attributes, change its priority, determine its status, and view its output using Operations Navigator’s work management functions.
Why would you need to control a job on the system? Good question. If one of your users has just initiated
an enormous job (printing War and Peace, for instance) that is really slowing down the system, you need to be able to change that job’s priority, or cancel it altogether. Otherwise, every other user needing to print business-related material on that printer would have to wait.
To get information about a job on your system:
1. Select the system you want to work with.2. Expand Work Management. 3. Expand Job Queues. 4. Expand Active Job Queues.
When the information appears in the right window, you can view the job queue, library, status, jobs on queue, subsystem, and description.á
5. Right-click a job queue and select Properties.á Use the information displayed on the tabs to determine the number of jobs waiting in a job queue.á Select Advanced on the Activity tab to view the priority of jobs contained within a queue.
Operations Navigator’s Management Central allows you to manipulate jobs on your system in numerous ways. Create a monitor, manage job queues—Management Central gives you the flexibility you need to work with jobs
Additional information on this topic can be found in these sources:
Jobs and job queues Managing jobs Create a job monitor