Systems management Work management

Size: px
Start display at page:

Download "Systems management Work management"

Transcription

1 System i Systems management Work management Version 5 Release 4

2

3 System i Systems management Work management Version 5 Release 4

4 Note Before using this information and the product it supports, read the information in Notices, on page 271. Fifth Edition (February 2006) This edition applies to version 5, release 4, modification 0 of IBM i5/os (product number 5722-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. Copyright International Business Machines Corporation 2004, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Work management What s new for V5R Printable PDF Introduction to work management Your system as a business A job s life How work gets done Concepts The structure of your system Subsystems Memory pools Jobs Job scheduling options Job queues Output queues Job logs Job accounting Managing work Changing the IPL start-up program Calling a special IPL recovery program Monitoring system activity Managing jobs Managing job scheduling Managing subsystems Managing memory pools Managing job queues Managing output queues Managing job logs Managing job accounting Reference Group jobs Troubleshooting for work management My job is hung My job is experiencing poor performance Prestart job investigation Related information for work management Chapter 2. Advanced Job Scheduler 247 Advanced Job Scheduler for Wireless Scheduling jobs with Advanced Job Scheduler What s new in Advanced Job Scheduler for V5R Installing the Advanced Job Scheduler Setting up the Advanced Job Scheduler Managing the Advanced Job Scheduler Working with Advanced Job Scheduler for Wireless Troubleshooting the Advanced Job Scheduler 269 Appendix. Notices Trademarks Terms and conditions Copyright IBM Corp. 2004, 2006 iii

6 iv System i: Systems management Work management

7 Chapter 1. Work management Work management is an important building block within the i5/os operating system. Its functions are the foundation through which all work enters the system, is processed, run, and completed on System i products. Whether you run a simple batch job once a week or you call an application daily (like Lotus Notes ), work management helps manage the jobs and objects that run on your system. It also supports the commands and internal functions necessary to control system operations and allocate resources to applications when needed. The System i product is set up and ready to use. Most users will not need to change the default settings. However, if you need to tailor the work management piece to fit your company, you will need to understand the terms and concepts associated with it and how they integrate with each other to provide you with the best performance from your system. Whether you are an experienced System i user or just learning, this topic collection gives you an easy-to-understand view of work management. This topic contains different entry points, so that you choose where you want to start learning about work management. Note: In addition, you can work with work management using iseries Navigator tasks on the Web. This allows you to work with work management functions using a Web browser. For more information, see iseries Navigator tasks on the Web. What s new for V5R4 This release brings some exciting changes not only to the work management functions, but also to the Work management topic in the Information Center. You now have more control over producing job logs. The job log pending state has been available for many years. When a job log is in a job log pending state, no job log is produced. With the release of V5R4 the iseries Navigator Job Properties - Job Log window has been enhanced so that you can now control how and under what circumstances the job log for a specific job will be produced. If you prefer the character-based interface, the Work with Job Logs (WRKJOBLOG) command is a new command that you can use to manage job logs. When this command is run, the Work with Job Logs screen is displayed. From this screen you can display job logs, delete job logs, work with spooled files, and work with the job that is associated with the job log. In the job description, the new attribute LOGOUTPUT specifies whether the job log is produced by the job log server, by the job itself, or not produced at all. If the job description specifies *SYSVAL for the LOGOUTPUT value, then the new Job log output (QLOGOUTPUT) system value is used to control how a job log is produced. Additional information for call stacks is now available. As of V5R4, the call stack has changed on both the iseries Navigator and the character-based interface to add support for i5/os PASE, Java, and LIC applications. Many existing fields have been renamed, reorganized, or overloaded to display a greater variety of data. Copyright IBM Corp. 2004,

8 The Change Job (CHGJOB) and End Job (ENDJOB) commands can now operate on any current or completed jobs. In earlier releases, the commands did not work for special jobs such as system jobs, subsystem monitor jobs, spool readers, and spool writers. This change unifies the way the system handles output (spooled) files. The Work with Active Jobs (WRKACTJOB) screen has been enhanced. You can now view the Current user profile on the Work with Active Jobs screen. This attribute is already available in the Active Jobs list of iseries Navigator. Several enhancements have been made to the Advanced Job Scheduler. v The Work Flow Manager is a new tool that lets you define units of work that can consist of a combination of automated and manual steps. The units of work can then be scheduled or started manually. v You can add multiple commands to a scheduled task. v You have more control over the notification banner. v You can use Advanced Job Scheduler to send an . v You can distribute reports via the Basic Operations container. The entire Work management topic has been reorganized and updated for the IBM i5/os Information Center Version 5 Release 4 (V5R4). The new Work management topic replaces the V4R5 work management manual that was available in the IBM i5/os Information Center Version 5 Release 3 (V5R3). This manual provided information about how to effectively manage the system workload by changing work management objects to meet your needs. It also provided guidelines for performance tuning, description of system values, information about collecting performance data, gathering system use data, using work entries, and scheduling batch jobs. What s new as of January 2006 Group jobs This is a new topic collection that is included as reference material for the maintenance of older environments. Prestart jobs for batch applications This is a new topic that discusses the unique situation that server jobs that use prestart jobs presents. Prestart communications jobs and job accounting A section has been added to this topic that further discusses prestart jobs for batch applications. Experience reports The experience report, Reducing iseries IPL time has been updated. Additionally, the Subsystem configuration experience report now consists of a three part series designed to provide useful information about working with subsystems. v Subsystem Configuration v Subsystem Configuration: Managing Server Jobs v Subsystem Configuration: Interactive Subsystem Configuration How to see what s new or changed To help you see where technical changes have been made, this information uses: v The image to mark where new or changed information begins. 2 System i: Systems management Work management

9 v The image to mark where new or changed information ends. To find other information about what s new or changed this release, see the Memo to users. Printable PDF Use this to view and print a PDF of this information. v To view or download the PDF version of this document, select Work management (about 3300 KB). v To view or download the PDF version of just the Advanced Job Scheduler portion of Work management, select Advanced job scheduler (about 390 KB). You can view or download these related topics: v Performance (2000 KB) contains the following topics: Planning for performance Managing system performance Applications for performance management v Management Central (2500 KB) contains the information that helps you perform system management tasks across one or more systems simultaneously. Saving PDF files To save a PDF on your workstation for viewing or printing: 1. Right-click the PDF in your browser (right-click the link above). 2. Click the option that saves the PDF locally. 3. Navigate to the directory in which you want to save the PDF. 4. Click Save. Downloading Adobe Reader You need Adobe Reader installed on your system to view or print these PDFs. You can download a free copy from the Adobe Web site ( Introduction to work management Work management supports the commands and internal functions necessary to control system operation and the daily workload on the system. In addition, work management contains the functions that you need to distribute resources for your applications so that your system can handle your applications. The purpose of your system is to perform work. Work enters, work is processed, and work leaves the system. If you think of work management in these three terms, work management will be easier to understand. Work management describes where work enters the system, where and with what resources work is processed, and where output from work goes. Are you new to work management? The topic collection under the subject Introduction to work management is designed to provide you with several different overall perspectives of work management. In this way, you should be able to get a solid foundation in the underlying principles of work management, regardless of your systems background. Your system as a business To make grasping the overall concept of work management easier, try comparing your system with a business. Chapter 1. Work management 3

10 A simple system can be compared to a small business, and a complex system can be compared to a shopping mall. Assume there is a small store in the business of building hand-crafted wood furniture. Work enters, such as orders for small tables, chairs, and bookshelves. Work is processed, the carpenter calls the customers to confirm the order, and they are consulted on design points including style, size, and color. The carpenter designs each piece of furniture, gathers the necessary materials, and then builds the furniture. After the furniture is completed, it is delivered: work leaves. Since a complex system is a combination of many simple systems, a comparable example of a complex system is a shopping mall, many small and large businesses in one area. Maybe the carpenter has a business in the Northwest corner of the mall and a baker has a business along the East strip. The baker and the carpenter have different input and different output, that is, their orders and their products are very different. In addition, the time it takes each business to process their work is quite different, and their users know and understand that. Work management terms A complex system (shopping mall) is a compilation of many simple systems (stores). These simple systems are called subsystems. Any piece of work within the business is considered a job. An example of a piece of work might be a customer letter, a telephone call, an order, or nightly cleanup. The same can be said about the System i product. On the system, each job has a unique name. A job description describes how to handle the work coming into the subsystem. Job descriptions contain pieces of information such as user IDs, job queues, and routing data. Information in the job description might compare to descriptions of jobs in a small business. What does the business look like? Every store has blueprints or store plans. These plans are really just descriptions, in varying detail, of the physical makeup of the business. Maybe the business has a store with: 2 floors, 5 doors, 3 mailboxes, and 2 telephones. On your system, a subsystem description contains all the information about the subsystem. Where does the work come from? For the carpenter, the work comes from customer calls, from references, and from people that stop in. On your system, the work can come from many places. Examples include job queues, workstations, communications, autostart jobs, and prestart jobs. Where do they find the space? Within the mall, each business (subsystem) has a certain amount of floor space. On the system, memory pools allow you to control the main storage (or floor space) each subsystem (business) gets to do its work. The more floor space a store (subsystem) has, the more customers, or jobs, can fit in the store. How does the work come in? Customers that cannot find the store they need may find an information booth to help send them in the right direction. The same is true on your system. Routing entries are similar to store directories or an information booth. After the routing entry is found, it guides the job to its correct place. The routing entry needs to be found first, however. That is done through routing data. Routing data is what the job uses to find the right routing entry. How is the work treated? A carpenter needs to place a priority on each job. The chair due at the end of the week should be done before the bookshelf due at the end of the month. On your system, classes provide information about how the job is handled while in the subsystem. This information includes priority while running, maximum storage, maximum CPU time, and time slice. Each of these attributes contribute to how and when a job is processed. Just as there are rules that affect all the stores in the mall, there are rules that affect all the subsystems on your system. An example of these rules is a system value. System values are pieces of information that 4 System i: Systems management Work management

11 apply to the whole system. System values include information such as, date and time, configuration information, signon information, system security and, storage handling. Customers in a mall each have information specific to them. On your system, the user profile holds information specific to a particular user. Similar to a customer s credit card, a user profile gives that user specific authorities and assigns the user attributes for that user s jobs. These job attributes provide information that includes, but is not limited to, the job description, the output queue or printer device, the message queue, the accounting code, and the scheduling priority. A job s life To understand the basics of System i work management, follow a simple batch job as it moves through the system. The life of a simple batch job begins when you submit it to the system. The job is then sent to a job queue where it waits to enter a subsystem where it can run. After the job moves to the subsystem it is allocated memory in which to run. The printer output file (also called spooled files) is then sent to the output queue to await further instruction on what to do (for example, printing). While not every job follows this exact path, you can better understand how other work is completed on the system by learning more about this typical job life cycle. Submit the job Job enters the job queue Job enters the subsystem The memory pool allocates memory to the subsystem The job finishes and moves to the output queue Submitting a job When a job is submitted, it is created and enters the system. At this time, the attributes are given to the job. The job description holds attributes that the job will use to go through the work management life cycle. These attributes include the user profile the job will start to run under, the request data (which tells the job what it will do), and the initial user portion of the library list, and so on. The job description also holds information that tells the job which job queue to enter and the routing data. The routing data is later used by the subsystem to find the routing entry that contains information needed for the job to start running. The output queue is also defined within the job description. It tells where printer output (also called spooled files) from a job will go. After the job receives its values (initialization, customization) for its job attributes, it moves to the job queue where it waits to enter the subsystem. The job enters the job queue Job queues are work entry points for batch jobs to enter the system. They can be thought of as waiting rooms for a subsystem. A number of factors affect when the job is pulled off the job queue into the subsystem, such as the job priority on the job queue, the sequence number of the job queue, and the maximum active jobs. When all of these factors work together, the job will be pulled off the job queue to start running in the subsystem. When the job enters the job queue, it is available to a subsystem that has the job queue allocated to it. Because subsystems can have more than one job queue feeding into them (however, job queues cannot feed into more than one subsystem), a sequence number in the subsystem determines when the subsystem processes a job queue. The subsystem looks at the sequence number of the job queue before the job priority of the jobs in the job queue. The subsystem uses the priority on the job queue to determine when a job can enter relative to other jobs on the job queue. The job priority and the maximum active jobs determine when a job enters the subsystem. Chapter 1. Work management 5

12 The job enters the subsystem Subsystems are operating environments where the system manages the resources that jobs use and controls the jobs that run within them. After jobs are running in the subsystem, the subsystem job carries out user requests on a job such as holding, releasing, and ending a job. When the job enters the subsystem it becomes active. Like jobs, subsystems have descriptions that carry important information needed to complete the work. In the subsystem description is the routing entry. The routing entry references the class object, which contains the attributes that control the run-time environment. However, before the job can get its routing entry, the routing data must make a match with a compare value in the routing entry. If this association is not made, the job will not run. After the association between the routing data and the routing entry is made, the class object the job will use is determined. Some of the attributes that control the run-time environment include the run priority, the time slice, the maximum wait time, the maximum processing time, the maximum temporary storage, and the maximum number of threads. The subsystem description defines the memory pools that will be allocated to the subsystem. The subsystem description also contains the maximum active jobs, which is the maximum number of active jobs at one time in the subsystem. Until a job gets its activity level and is assigned a memory pool, it cannot run. The subsystem description, like the job description, carries information, such as the memory pool to use, the routing entry, the maximum active jobs, and the number of active jobs currently in the subsystem. The subsystem uses memory from the memory pool to run the job Memory is a resource from the memory pool that the subsystem uses to run the job. The amount of memory in a memory pool, as well as how many other jobs are competing for memory, affect how efficiently a job runs. Memory pools provide jobs with memory in which to run. Many factors affect how the job runs in the memory pool, such as the size of the memory pool, the activity level in the memory pool, and paging and faulting. The activity level in memory pools directly relates to the number of threads that are allowed to run in the memory pool at one time. Remember, every job has at least one active thread, but some can have multiple threads. Threads give a job the ability to do more than one thing at a time. For example, one thread can go out and do calculations while another thread waits for more data to process. Paging is the movement of data in and out of memory, both synchronously and asynchronously. Pages can be written out to storage or removed from memory without being written if they have not been changed. Faulting causes paging to occur on the server. Faulting occurs when a referenced page, or piece of data, is not in memory. This causes programs to stop because they must wait for the data to be paged in. Subsystems use different memory pools to support different types of jobs that run within them. The job finishes and moves to the output queue A job s printer output (also called spooled files) is sent to an output queue where it waits to be sent to a printer or file. The output queue is similar to the job queue in that it controls how the output is made available to the printer. The output queue allows the user to control what files are printed first. Output queues are areas where printer output files wait to be processed and sent to the printer. Printer output is created either by the system or by the user using a print file. A print file is similar to a template or a guideline where the default values for the attributes of printer output are set. It is the beginning of the printer output life cycle. 6 System i: Systems management Work management

13 The print file contains the output queue (OUTQ) and print device (DEV) attributes, which dictate how the printer output is to be directed. The default settings are typically *JOB, meaning that the job attributes of the output queue and printer device determine how the printer output is directed. The job attributes of the output queue and printer device settings are based on information obtained when the job is created. This is based on information from the user profile that the job is running under, the job description, the workstation device description, and the Default printer (QPRTDEV) system value. When the printer output is ready to be created, the system checks the print file and the job attributes (in this order) to see what output queue will process the printer output and which printer device the system will use. If a specified output queue cannot be found, the printer output will be directed to QGPL/QPRINT. After the printer output file is ready to be printed, a writer job, a job that processes the printer output from the output queue to the printer device, takes data from the printer output file and sends it to the designated printer. How work gets done This topic explains what work is, what needs to be set up before work begins, how work travels through the system, and what happens to work after it is done running. What work is On your System i product, work is always being done, whether you initiate it or the system initiates it. Any action done on the system has some type of work being performed to complete it. Work is done when you turn on your system, when you open a file, or when you query a database. Each piece of work on the system is performed by a job. A job can be as simple as an application that waits for a user to call it or it can be as complex as a constantly running system query that monitors the number of users on the system every hour. Some jobs, specifically batch and interactive jobs, have job descriptions associated with them that tell when and where the job will run. Jobs are made up of programs that perform certain functions. There is no limit to the amount of functions a job performs. A job contains the step-by-step instructions that must be completed for work to be done. The programs that make up the job run in a specific order. (For example, program A needs to run before program B can begin.) Threads help a job complete its work. An active job contains at least one thread. When a job contains multiple threads, it has the ability to do more than one thing at once. For example, one thread can go out and do calculations while another thread waits for more data to process. What happens before work enters the system All jobs, with the exception of system jobs, run within subsystems. For work to start in an active subsystem, memory pools and at least one source of work entry point need to be established. Job queues are an example of a source of work. The System i product includes a default set of job queues, subsystems, and memory pools, which can allow work to begin as soon as the system is powered on. You can tailor the subsystem and memory pool configurations to optimize the capabilities and performance of your System i product. For example, if batch jobs are critical to the success of your business, you may want to allocate more memory for them to run. Or, you may determine that the number of jobs running at one time in your Qbatch subsystem should be lower so that those jobs can use the maximum amount of resources to run. Also, you can create job queues, subsystems, and memory pools specifically designed to complete specific types of work. For example, you can create a job queue called Nightreps, where nightly batch reports are sent to a subsystem called Nightrep that allocates memory exclusively for running these batch jobs. Chapter 1. Work management 7

14 How work enters the system Work entries identify the sources where jobs enter a subsystem to become available to run. Each type of job has different types of work entries that it uses. For example, most batch jobs use job queues to enter the subsystem. Job queue entries are the mechanism through which a job queue is defined as a source of work to a subsystem. Work entries are kept in the subsystem description. If a subsystem description does not have a work entry for the type of work being done, the job cannot run in that subsystem. The IBM-shipped subsystems have default work entries in the subsystem descriptions. Keep in mind, some of the default work entries that ship with the subsystems are already allocated to run specific jobs. How work gets processed When the system is started, a subsystem monitor job begins running. The subsystem monitor job controls the jobs within subsystems. It also starts and ends work, as well as manages the resources for work in the subsystem. Work (or jobs) enters a subsystem through work entries where it becomes active and eligible to run. Work can only be completed when the subsystem has allocated memory to run. Memory is allocated to the subsystem by a memory pool. How the subsystem description helps process work Like a job, a subsystem has a description, called a subsystem description. The subsystem description contains important information that tells how, where, how much work can be active in a subsystem at one time, and which resources it can use to perform the work. Routing entry A routing entry exists within the subsystem description and tells the subsystem what program to run for the job, what memory pool to run the job in, and which class object to use to run the job. Class Object The Class object defines the run priority, default wait time, time slice, and other attributes. The run priority is important because it determines when a job will get processor time in order to run. The run priority scale goes from 0 to 99, with 0 being the highest priority. (Only system jobs are given priority of 0 because they are the jobs that run the system.) When a job enters the subsystem, the subsystem tries to match the routing data with the compare value in the routing entry. If the routing data and the compare value in a routing entry match, the routing entry is assigned to the job. If a match is not made in any routing entry, the job ends. Another factor that affects when a job runs in the subsystem is the number of jobs that are allowed to be active in the subsystem at one time (also known as maximum active jobs in the subsystem). When the maximum number of active jobs in a subsystem has been met, no more jobs can enter the subsystem until existing active jobs complete running. Memory has to be allocated to the subsystem for a job to run. Memory pool activity levels tell the system how many threads can be active within a memory pool. Remember, an active job contains at least one thread. When the memory pool activity level has been reached, the job has to wait for another thread to give up its use of the activity level. Thus, a job can be active in a subsystem and not be running. Note: Do not confuse the subsystem maximum active jobs with the memory pool activity level. How work leaves the system The output queue works similarly to a job queue in that it schedules output to be printed. Both the printer output and the output queue carry attributes that are used to print the information. 8 System i: Systems management Work management

15 Printer output holds output data that is waiting to be processed, such as information waiting to be printed. Printer output also holds important information that is used to schedule when it will be printed. Printer output attributes include the output queue in which the printer output will reside, the priority, the status and the schedule of the printer output. The output queue contains attributes of its own that determine the order in which the printer output files are processed. It also contains the authority that is needed to make changes to the printer output and the output queue. When the printer output is ready to be sent to the printer it is picked up by a writer job. The writer job takes the data from the printer output and prepares it to be printed. Concepts Whether you are new to work management or have been using work management tools for years, these work management concepts might be useful for you. The structure of your system After receiving your System i product, you might want to know what subsystems are included with the system, whether you need to change any start-up programs, and what kind of user interface you will work with. Subsystems shipped with the system Two complete subsystem configurations are supplied by IBM and can be used without being changed. The configuration the system uses when the system is started is controlled by the Controlling subsystem/library (QCTLSBSD) system value. The default configuration consists of the following subsystem descriptions: Subsystem Description Qbase (controlling subsystem) Qbase supports interactive, batch, and communications jobs. It has an autostart job, which automatically starts the Qusrwrk, Qserver, and Qspl subsystems. Qserver This is the file server subsystem. Qspl This is the spool subsystem that supports reader and writer jobs. Qsyswrk This is the system work subsystem. It contains jobs that support system functions that are started automatically at system startup and when the system comes out of restricted state. Qusrwrk This is the user work subsystem. It contains jobs that are started by servers to do work on behalf of a user. The other configuration, which is supplied by IBM, consists of the following subsystem descriptions: Subsystem Description Qctl (controlling subsystem) Qctl has an autostart job, which automatically starts the Qinter, Qbatch, Qcmn, Qusrwrk, Qserver and Qspl subsystems. Qinter This is the subsystem that supports interactive jobs, except those at the console. Qbatch This is the subsystem that supports batch jobs. Qcmn This is the subsystem that supports communications jobs, excluding TCP/IP communications jobs. These communications jobs are necessary for various communications protocols that the i5/os system supports. Qserver This is the file server subsystem. Qspl This is the spool subsystem that supports reader and writer jobs. Chapter 1. Work management 9

16 Qsyswrk This is the system work subsystem. It contains jobs that support system functions that are started automatically at system startup and when the system comes out of restricted state. Qusrwrk This is the user work subsystem. It contains jobs that are started by servers to do work on behalf of a user. The Qbase configuration gives the ability to run all of the same functions that you can run with the Qctl configuration and is easier to manage because it consists of fewer subsystems. The Qctl default configuration allows for more individualized control over your system operations by dividing the system activity into different subsystems based on the type of activity. For example, if you want to run batch jobs over the weekend, but do not want anyone to be able to sign on (except at the console), you can easily do that with the Qctl configuration by ending the Qinter subsystem. If you are considering creating your own subsystem configuration, you might also find that it is easier to use the Qctl configuration as a starting point than the Qbase configuration. Start-up programs QSTRUPPGM is the start-up program. This is a system value which specifies the name of the program called from an autostart job when the controlling subsystem is started. This program performs setup functions, such as starting subsystems and printers. This system value can only be changed by the security officer or by someone with security officer authority. A change to this system value takes effect the next time an IPL is performed. QSTRUPPGM can have these values: v QSTRUP QSYS: The program specified is run as a result of a transfer of control to it from the autostart job in the controlling subsystem. v *NONE: The autostart job ends normally without calling a program. Related information System values that control IPL What happens during the IPL: The default startup program QSYS/QSTRUP does the following: v Starts the QSPL subsystem for spooled work. v Releases the QS36MRT and QS36EVOKE job queues if they were held (these are used by the System/36 environment). v Starts Operational Assistant cleanup, if allowed. v Starts all print writers unless user specified not to on the IPL Options display. v Starts the QSERVER and QUSRWRK subsystems. v If the controlling subsystem is QCTL, it starts the QINTER, QBATCH, and QCMN subsystems. Types of start-ups During an initial program load (IPL), system programs load from the designated load source device in the system auxiliary storage. The system hardware is also checked. The i5/os control panel displays a series of system reference codes that indicate its current status and warn you of any problems. When the IPL is finished, the character-based interface presents the signon display, and users are able to sign on with iseries Navigator. There are several options for starting your system. You can: v Start the system without making configuration changes. This is referred to as an unattended IPL. v Change your system configuration during an IPL. This is referred to as an attended IPL. Attended IPL s display various additional screens depending upon the options that you select on the IPL options display. These can include displays that allow you to change system values and other 10 System i: Systems management Work management

17 system attributes during the IPL, reconstruct access paths, verify the status of physical file restrictions, configure and name new devices, and specify options for the operating environment. v Change the type of IPL from your system control panel. v Schedule a system shut down and restart. General problems during an IPL is referred to as an abnormal IPL. For more information about IPL and system shut down, see information about starting and stopping the system. Related information Starting and stopping the system Powering down your system You must be cautious when turning off your system. If you turn off the system without completing certain tasks, you can cause damage to data or cause the system to behave in unpredictable ways. The following information center topics contain more information about safely powering down your system. v How to safely shut down your system when integrated Windows servers are present v Power down a system with logical partitions v Power down System Exit Program v Exit Program for Tailoring Power Off Related information How to safely shutdown your iseries when integrated Windows servers are present Power down a system with logical partitions Power Down System Exit Program Exit Program for Tailoring Power Off iseries Navigator iseries Navigator is a powerful graphical interface for Windows clients. With iseries Navigator, you can manage and administer your systems from your Windows desktop. You can use Navigator to accomplish most of the tasks associated with work management. This interface has been designed to make you more productive. Therefore, it is recommended that you use Navigator, which has online help to guide you. While this interface is being developed, you might still need to use a traditional emulator such as PC5250 to do some of your tasks. If a topic discusses such a task, you will be directed to use the character-based interface within the instructional steps of the topic. Related information Getting to know iseries Navigator Subsystems The subsystem is where work is processed on the system. A subsystem is a single, predefined operating environment through which the system coordinates the work flow and resource use. The system can contain several subsystems, all operating independently of each other. Subsystems manage resources. All jobs, with the exception of system jobs, run within subsystems. Each subsystem can run unique operations. For instance, one subsystem may be set up to handle only interactive jobs, while another subsystem handles only batch jobs. Subsystems can also be designed to handle many types of work. The system allows you to decide the number of subsystems and what types of work each subsystem will handle. Chapter 1. Work management 11

18 The run-time characteristics of a subsystem are defined in an object called a subsystem description. For example, if you want to permanently change the amount of work (number of jobs) coming from a job queue into a subsystem you only need to change the job queue entry in the subsystem description. Related tasks Common subsystem tasks on page 186 This information discuss the most common tasks that you can perform on a subsystem. Creating a subsystem description on page 189 You can create a subsystem description in two ways. You can copy an existing subsystem description and change it, or you can create an entirely new description. Related information Experience Report: Subsystem Configuration The controlling subsystem The controlling subsystem is the interactive subsystem that starts automatically when the system starts, and it is the subsystem through which the system operator controls the system via the system console. It is identified in the Controlling subsystem/library (QCTLSBSD) system value. IBM supplies two complete controlling subsystem descriptions: QBASE (the default controlling subsystem) and QCTL. Only one controlling subsystem can be active on the system at any time. When the system is in the restricted condition, most of the activity on the system has ended, and only one workstation is active. The system must be in this condition for commands such as Save System (SAVSYS) or Reclaim Storage (RCLSTG) to run. Some programs for diagnosing equipment problems also require the system to be in a restricted condition. To end this condition, you must start the controlling subsystem again. Note: There is also a batch restricted state in which one batch job can be active. When all of the subsystems, including the controlling subsystem are ended, a restricted condition is created. You can end each subsystem individually or you can use the ENDSBS SBS(*ALL) OPTION(*IMMED). Important: The system cannot reach the restricted state until there is only one job remaining in the controlling subsystem. Sometimes it may appear as though there is a single job remaining, but the system does not go into the restricted state. In this case you need to verify that there are no suspended system request jobs, suspended group jobs, or disconnected jobs on the remaining active display. Use the Work with Active Jobs (WRKACTJOB) command and press F14=Include to display any suspended or disconnected jobs. If these jobs exist, you need to end them in order for the system to reach the restricted state. The ENDSYS and ENDSBS functions will send a CPI091C information message to the command issuer when this condition is detected. Related tasks Creating a controlling subsystem on page 203 IBM supplies two complete controlling subsystem configurations: QBASE (the default controlling subsystem), and QCTL. Only one controlling subsystem can be active on the system at one time. Typically, the IBM supplied subsystem configurations should be sufficient for most business needs. However, you can create your own version of a controlling subsystem and configure it to more closely meet your company s unique needs. Placing the system in restricted state on page 204 If all of the subsystems, including the controlling subsystem are ended, the system goes into a restricted condition. You can place the system in a restricted condition by using one of two commands from an interactive workstation. Related information Experience Report: Restricted State 12 System i: Systems management Work management

19 Why consider multiple subsystems As the number of users on the system increases, a single subsystem for a set of work is often insufficient. By dividing your users into multiple subsystems you gain several advantages. Improved manageability of work You get better control over what work is running in each subsystem. For example, for server jobs, you might want to isolate all of the database server jobs to one subsystem, the remote command server jobs to a different subsystem, the DDM server jobs to yet a different subsystem and so on. Additionally, by using multiple subsystems you can isolate groups of jobs with their own memory pools. In this way, one group does not adversely impact other jobs. Reduced downtime impact for users For example, if every Friday afternoon you must bring the system to the restricted state for backup purposes, you can gradually take users offline by ending one subsystem at a time. Improved scalability and availability By having a single subsystem do work for fewer users, the subsystem is less busy and can be more responsive to the work requests it handles. Improved error tolerance in interactive subsystems By spreading the work across multiple subsystems, should a network failure occur, multiple subsystems can manage the device recovery processing. Improved interactive subsystem startup time You can keep the subsystem startup times shorter by subdividing the work across multiple subsystems. Additional options for performance tuning By using multiple subsystems you can set up the subsystems with a small number of routing entries. Related information Experience Report: Subsystem Configuration Subsystem description A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. The system-recognized identifier for the object type is *SBSD. A subsystem description defines how, where, and how much work enters a subsystem, and which resources the subsystem uses to perform the work. An active subsystem takes on the simple name of the subsystem description. Like a set of detailed blueprints, each subsystem description is unique, containing the specific characteristics that describe the subsystem. The description includes where work can enter the subsystem, how much work the subsystem can handle, how much main storage (memory) will be used, and how quickly jobs in the subsystem can run. You can use a subsystem description supplied with your system (with or without making changes to it), or you can create your own. Related tasks Changing a subsystem description on page 193 The Change Subsystem Description (CHGSBSD) command changes the operational attributes of the specified subsystem description. You can change the subsystem description while the subsystem is active. To change a subsystem description, use the character based interface. Creating a subsystem description on page 189 You can create a subsystem description in two ways. You can copy an existing subsystem description and change it, or you can create an entirely new description. Subsystem description attributes: Chapter 1. Work management 13

20 Subsystem description attributes are common overall system attributes. When you create a subsystem, the first step is to define the subsystem attributes. Subsystem attributes include: v The name of the subsystem description and the library where it is stored v All of the memory pool definitions that this subsystem uses A subsystem definition can have a maximum of 10 memory pool definitions specified. Included in the subsystem definition are: Pool definition identifier: This is the identifier inside the subsystem description, of the storage pool definition. Size: This is the size of the storage pool expressed in KB (1K=1024 bytes) multiples and is the amount of main storage that the pool can use. Activity level: This is the maximum number of threads that can run at the same time in the pool. v The maximum number of jobs that can be active in the subsystem at the same time v A text description of the subsystem description v The name and library of the signon display file that is used to show signon displays at work stations that are allocated to the subsystem v A subsystem library name that you can use if you want to specify a library that should be entered ahead of other libraries in the system portion of the library list (This parameter allows you to use a secondary language library.) Also included in the subsystem description is information about authority levels to the subsystem. This information is kept by Security and is not stored with the other attributes of the subsystem description. You can view the subsystem description authority by using the Display Object Authority (DSPOBJAUT) command. Work entries: Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem description. The following information describes the different types of work entries and how to manage them. There are five types of work entries; autostart job entries, communication entries, job queue entries, prestart job entries, and workstation entries. Autostart job entries: Autostart job entries identify the autostart jobs to start as soon as the subsystem starts. When a subsystem starts, the system allocates several items and starts autostart and prestart jobs before it is ready for work. The autostart jobs associated with a subsystem are automatically started each time the subsystem is started. An autostart job in the controlling subsystem can be used to start other subsystems (as does the IBM-supplied controlling subsystem). An autostart job is a batch job doing repetitive work. For example: To call a special recovery program if the IPL senses that the previous system ending was abnormal, you can add an autostart job entry to the subsystem description for the controlling subsystem. This program checks the Previous system ending status (QABNORMSW) system value. For a normal system ending, the value of QABNORMSW is 0, and for an abnormal system ending, the value of QABNORMSW is 1. Related tasks Adding autostart job entries on page 189 You use the character-based interface to add an autostart job entry. An autostart job starts 14 System i: Systems management Work management

21 automatically when the associated subsystem starts. These jobs generally perform initialization work that is associated with a particular subsystem. Autostart jobs can also perform repetitive work or provide centralized service functions for other jobs in the same subsystem. Changing autostart job entries on page 194 You can specify a different job description for a previously defined autostart job entry. To change an autostart job entry, use the character-based interface Removing autostart job entries on page 197 You can remove an autostart job entry from a subsystem description by using the character-based interface. Communications entries: The communications work entry identifies to the subsystem the sources for the communications job it will process. The job processing begins when the subsystem receives a communications program start request from a remote system and an appropriate routing entry is found for the request. For performance reasons, instead of starting a communications job each time a program start request is received, you can configure a prestart job to handle a program start request from a remote system. For a communications batch job to run on system, a subsystem description containing a work entry for communications work must exist on the system. Related tasks Adding communications entries on page 190 Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface. Changing communication entries on page 194 You can change the attributes of an existing communications entry in an existing subsystem description by using the character-based interface. Removing communication entries on page 198 You can remove communication entries from the subsystem description by using the character-based interface. All jobs that are active through the communications entry being removed must be ended before this command can be run. Job queue entries: Job queue entries in a subsystem description specify from which job queues a subsystem is to receive jobs. When the subsystem is started, the subsystem tries to allocate each job queue defined in the subsystem job queue entries. For example, a job queue entry in the subsystem description QSYS/QBASE specifies that jobs can be started using the job queue QGPL/QBATCH. Jobs can be placed on a job queue even if the subsystem has not been started. When the subsystem QBASE is started, it processes the jobs on the queue. A subsystem description can specify the maximum number of jobs (batch or interactive) that can be processed at the same time. The number of jobs that can be active from any job queue is specified in the job queue entry. Related tasks Adding job queue entries on page 190 A job queue entry identifies a job queue from which jobs are selected for running in the subsystem. Jobs started from a job queue are batch jobs. You add a job queue entry using the character-based interface. Chapter 1. Work management 15

iseries Restricted State

iseries Restricted State iseries Restricted State iseries Restricted State Copyright International Business Machines Corporation 2004. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure

More information

IBM. Availability Implementing high availability. IBM i 7.1

IBM. Availability Implementing high availability. IBM i 7.1 IBM IBM i Availability Implementing high availability 7.1 IBM IBM i Availability Implementing high availability 7.1 Note Before using this information and the product it supports, read the information

More information

Security Service tools user IDs and passwords

Security Service tools user IDs and passwords IBM Systems - iseries Security Service tools user IDs and passwords Version 5 Release 4 IBM Systems - iseries Security Service tools user IDs and passwords Version 5 Release 4 Note Before using this information

More information

IBM i Version 7.3. Systems management Disk management IBM

IBM i Version 7.3. Systems management Disk management IBM IBM i Version 7.3 Systems management Disk management IBM IBM i Version 7.3 Systems management Disk management IBM Note Before using this information and the product it supports, read the information in

More information

Systems Management Working with Management Central monitors

Systems Management Working with Management Central monitors System i Systems Management Working with Management Central monitors Version 6 Release 1 System i Systems Management Working with Management Central monitors Version 6 Release 1 Note Before using this

More information

Availability Implementing High Availability with the solution-based approach Operator's guide

Availability Implementing High Availability with the solution-based approach Operator's guide System i Availability Implementing High Availability with the solution-based approach Operator's guide Version 6 Release 1 System i Availability Implementing High Availability with the solution-based

More information

IBM. Systems management Disk management. IBM i 7.1

IBM. Systems management Disk management. IBM i 7.1 IBM IBM i Systems management Disk management 7.1 IBM IBM i Systems management Disk management 7.1 Note Before using this information and the product it supports, read the information in Notices, on page

More information

Systems Management Advanced job scheduler

Systems Management Advanced job scheduler System i Systems Management Advanced job scheduler Version 6 Release 1 System i Systems Management Advanced job scheduler Version 6 Release 1 Note Before using this information and the product it supports,

More information

Understanding Advanced Workflow

Understanding Advanced Workflow IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 Note Before

More information

Hardware installation and use Control panel

Hardware installation and use Control panel System i Hardware installation and use Control panel Version 5 Release 4 System i Hardware installation and use Control panel Version 5 Release 4 Note Before using this information and the product it

More information

System i and System p. Creating a virtual computing environment

System i and System p. Creating a virtual computing environment System i and System p Creating a virtual computing environment System i and System p Creating a virtual computing environment Note Before using this information and the product it supports, read the information

More information

Availability Implementing high availability

Availability Implementing high availability System i Availability Implementing high availability Version 6 Release 1 System i Availability Implementing high availability Version 6 Release 1 Note Before using this information and the product it

More information

Networking TCP/IP troubleshooting

Networking TCP/IP troubleshooting System i Networking TCP/IP troubleshooting Version 6 Release 1 System i Networking TCP/IP troubleshooting Version 6 Release 1 Note Before using this information and the product it supports, read the information

More information

ERserver. Service provider information Service functions

ERserver. Service provider information Service functions ERserver Service provider information Service functions ERserver Service provider information Service functions Note Before using this information and the product it supports, be sure to read the information

More information

iseries Job Attributes

iseries Job Attributes iseries Job Attributes iseries Job Attributes Copyright ternational Business Machines Corporation 5. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted

More information

IBM. Basic system operations. System i. Version 6 Release 1

IBM. Basic system operations. System i. Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 Note Before using this information and the product it supports, read the information in

More information

System p. Partitioning with the Integrated Virtualization Manager

System p. Partitioning with the Integrated Virtualization Manager System p Partitioning with the Integrated Virtualization Manager System p Partitioning with the Integrated Virtualization Manager Note Before using this information and the product it supports, read the

More information

Security Enterprise Identity Mapping

Security Enterprise Identity Mapping System i Security Enterprise Identity Mapping Version 6 Release 1 System i Security Enterprise Identity Mapping Version 6 Release 1 Note Before using this information and the product it supports, be sure

More information

IBM i Version 7.2. Connecting to your system Connecting to Your system with IBM Navigator for i IBM

IBM i Version 7.2. Connecting to your system Connecting to Your system with IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to Your system with IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to Your system with IBM Navigator for i IBM Note

More information

Programming Advanced Job Scheduler for i5/os commands

Programming Advanced Job Scheduler for i5/os commands System i Programming Advanced Job Scheduler for i5/os commands Version 6 Release 1 System i Programming Advanced Job Scheduler for i5/os commands Version 6 Release 1 Note Before using this information

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation and User's Guide SC27-2809-03 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation

More information

Agenda. Jim Oberholtzer Senior Technical Architect

Agenda. Jim Oberholtzer Senior Technical Architect iseries Performance Configuration and Tools September 13, 2005 Jim Oberholtzer Senior Technical Architect INFORMATION S O L U T I O N S THAT WORK FOR BUSINESS GREEN BAY MILWAUKEE MINNEAPOLIS Agenda Work

More information

i5/os and related software Installing, upgrading, or deleting i5/os and related software

i5/os and related software Installing, upgrading, or deleting i5/os and related software i5/os i5/os and related software Installing, upgrading, or deleting i5/os and related software Version 6 Release 1 SC41-5120-10 i5/os i5/os and related software Installing, upgrading, or deleting i5/os

More information

IBM i Version 7.2. Security Object signing and signature verification IBM

IBM i Version 7.2. Security Object signing and signature verification IBM IBM i Version 7.2 Security Object signing and signature verification IBM IBM i Version 7.2 Security Object signing and signature verification IBM Note Before using this information and the product it

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation and User's Guide SC27-2809-04 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation

More information

IBM i and related software Installing, upgrading, or deleting IBM i and related software

IBM i and related software Installing, upgrading, or deleting IBM i and related software IBM i IBM i and related software Installing, upgrading, or deleting IBM i and related software 7.1 SC41-5120-11 IBM i IBM i and related software Installing, upgrading, or deleting IBM i and related software

More information

IBM i Version 7.3. IBM i and related software Maintaining and managing IBM i and related software IBM

IBM i Version 7.3. IBM i and related software Maintaining and managing IBM i and related software IBM IBM i Version 7.3 IBM i and related software Maintaining and managing IBM i and related software IBM IBM i Version 7.3 IBM i and related software Maintaining and managing IBM i and related software IBM

More information

System i and System p. Managing the Integrated Virtualization Manager

System i and System p. Managing the Integrated Virtualization Manager System i and System p Managing the Integrated Virtualization Manager System i and System p Managing the Integrated Virtualization Manager Note Before using this information and the product it supports,

More information

IBM i Version 7.2. Files and file systems Spooled files IBM

IBM i Version 7.2. Files and file systems Spooled files IBM IBM i Version 7.2 Files and file systems Spooled files IBM IBM i Version 7.2 Files and file systems Spooled files IBM Note Before using this information and the product it supports, read the information

More information

i5/os and related software Maintaining and managing i5/os and related software

i5/os and related software Maintaining and managing i5/os and related software i5/os i5/os and related software Maintaining and managing i5/os and related software Version 6 Release 1 i5/os i5/os and related software Maintaining and managing i5/os and related software Version 6

More information

Networking i5/os NetServer

Networking i5/os NetServer System i Networking i5/os NetServer Version 6 Release 1 System i Networking i5/os NetServer Version 6 Release 1 Note Before using this information and the product it supports, read the information in

More information

About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software

About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0 Windows

More information

IBM. IBM i and related software Maintaining and managing IBM i and related software. IBM i 7.1

IBM. IBM i and related software Maintaining and managing IBM i and related software. IBM i 7.1 IBM IBM i IBM i and related software Maintaining and managing IBM i and related software 7.1 IBM IBM i IBM i and related software Maintaining and managing IBM i and related software 7.1 Note Before using

More information

IBM Personal Computer. About Your Software Windows NT Workstation 4.0, Applications, and Support Software

IBM Personal Computer. About Your Software Windows NT Workstation 4.0, Applications, and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0, Applications, and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0, Applications, and Support

More information

IBM. Database Commitment control. IBM i 7.1

IBM. Database Commitment control. IBM i 7.1 IBM IBM i Database Commitment control 7.1 IBM IBM i Database Commitment control 7.1 Note Before using this information and the product it supports, read the information in Notices, on page 113. This edition

More information

IBM. Database Database overview. IBM i 7.1

IBM. Database Database overview. IBM i 7.1 IBM IBM i Database Database overview 7.1 IBM IBM i Database Database overview 7.1 Note Before using this information and the product it supports, read the information in Notices, on page 39. This edition

More information

IBM Personal Computer. About Your Software Windows 95, Applications, and Support Software

IBM Personal Computer. About Your Software Windows 95, Applications, and Support Software IBM Personal Computer About Your Software Windows 95, Applications, and Support Software IBM Personal Computer About Your Software Windows 95, Applications, and Support Software IBM Note Before using

More information

Development tools System i5 Debugger

Development tools System i5 Debugger System i Development tools System i5 Debugger Version 6 Release 1 System i Development tools System i5 Debugger Version 6 Release 1 Note Before using this information and the product it supports, read

More information

IBM. Documentation. IBM Sterling Connect:Direct Process Language. Version 5.3

IBM. Documentation. IBM Sterling Connect:Direct Process Language. Version 5.3 IBM Sterling Connect:Direct Process Language IBM Documentation Version 5.3 IBM Sterling Connect:Direct Process Language IBM Documentation Version 5.3 This edition applies to Version 5 Release 3 of IBM

More information

IBM Tivoli Storage Manager for HP-UX Version Installation Guide IBM

IBM Tivoli Storage Manager for HP-UX Version Installation Guide IBM IBM Tivoli Storage Manager for HP-UX Version 7.1.4 Installation Guide IBM IBM Tivoli Storage Manager for HP-UX Version 7.1.4 Installation Guide IBM Note: Before you use this information and the product

More information

Networking Bootstrap Protocol

Networking Bootstrap Protocol System i Networking Bootstrap Protocol Version 5 Release 4 System i Networking Bootstrap Protocol Version 5 Release 4 Note Before using this information and the product it supports, read the information

More information

Microsoft SQL Server Fix Pack 15. Reference IBM

Microsoft SQL Server Fix Pack 15. Reference IBM Microsoft SQL Server 6.3.1 Fix Pack 15 Reference IBM Microsoft SQL Server 6.3.1 Fix Pack 15 Reference IBM Note Before using this information and the product it supports, read the information in Notices

More information

Systems Management Management Central

Systems Management Management Central System i Systems Management Management Central Version 6 Release 1 System i Systems Management Management Central Version 6 Release 1 Note Before using this information and the product it supports, read

More information

MIMIX. Version 7.0 MIMIX Global Operations 5250

MIMIX. Version 7.0 MIMIX Global Operations 5250 MIMIX Version 7.0 MIMIX Global Operations 5250 Published: September 2010 level 7.0.01.00 Copyrights, Trademarks, and tices Contents Version 7.0 MIMIX Global Operations 5250 Who this book is for... 5 What

More information

About Your Software IBM

About Your Software IBM About Your Software About Your Software Note Before using this information and the product it supports, be sure to read Appendix. Viewing the license agreement on page 19 and Notices on page 21. First

More information

IBM i Version 7.2. Networking IBM i NetServer IBM

IBM i Version 7.2. Networking IBM i NetServer IBM IBM i Version 7.2 Networking IBM i NetServer IBM IBM i Version 7.2 Networking IBM i NetServer IBM Note Before using this information and the product it supports, read the information in Notices on page

More information

Security Digital Certificate Manager

Security Digital Certificate Manager System i Security Digital Certificate Manager Version 6 Release 1 System i Security Digital Certificate Manager Version 6 Release 1 Note Before using this information and the product it supports, be sure

More information

Central Administration Console Installation and User's Guide

Central Administration Console Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Central Administration Console Installation and User's Guide SC27-2808-03 IBM Tivoli Storage Manager FastBack for Workstations Version

More information

Systems management Backup, Recovery, and Media Services (BRMS)

Systems management Backup, Recovery, and Media Services (BRMS) System i Systems management Backup, Recovery, and Media Services (BRMS) Version 6 Release 1 System i Systems management Backup, Recovery, and Media Services (BRMS) Version 6 Release 1 Note Before using

More information

IBM. Security Digital Certificate Manager. IBM i 7.1

IBM. Security Digital Certificate Manager. IBM i 7.1 IBM IBM i Security Digital Certificate Manager 7.1 IBM IBM i Security Digital Certificate Manager 7.1 Note Before using this information and the product it supports, be sure to read the information in

More information

- - - ) _ I BM System/38. IBM System/3S Control Program Facility Concepts Manual GC Ie No Program Number

- - - ) _ I BM System/38. IBM System/3S Control Program Facility Concepts Manual GC Ie No Program Number - - - - GC21-7729-0 ) - - - - _.- Fi - --- - Ie No. 538-36 I BM System/38 IBM System/3S Control Program Facility Concepts Manual Program Number 5714-881 ( \ First Edition (October 1978) Changes are periodically

More information

System i and System p. Capacity on Demand

System i and System p. Capacity on Demand System i and System p Capacity on Demand System i and System p Capacity on Demand Note Before using this information and the product it supports, read the information in Notices on page 65 and the IBM

More information

IBM Content Manager OnDemand for i5/os Common Server Planning and Installation Guide

IBM Content Manager OnDemand for i5/os Common Server Planning and Installation Guide System i IBM Content Manager OnDemand for i5/os Common Server Planning and Installation Guide Version 6 Release 1 SC27-1158-04 System i IBM Content Manager OnDemand for i5/os Common Server Planning and

More information

IBM. Connecting to System i IBM Navigator for i. System i. Version 7Release 1

IBM. Connecting to System i IBM Navigator for i. System i. Version 7Release 1 IBM System i Connecting to System i IBM Navigator for i Version 7Release 1 IBM System i Connecting to System i IBM Navigator for i Version 7Release 1 Note Before using this information and the product

More information

iseries Managing disk units

iseries Managing disk units iseries Managing disk units iseries Managing disk units Copyright International Business Machines Corporation 2001. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure

More information

IBM Tivoli OMEGAMON XE for Storage on z/os Version Tuning Guide SC

IBM Tivoli OMEGAMON XE for Storage on z/os Version Tuning Guide SC IBM Tivoli OMEGAMON XE for Storage on z/os Version 5.1.0 Tuning Guide SC27-4380-00 IBM Tivoli OMEGAMON XE for Storage on z/os Version 5.1.0 Tuning Guide SC27-4380-00 Note Before using this information

More information

i5/os and related software Data migrations

i5/os and related software Data migrations System i i5/os and related software Data migrations Version 6 Release 1 System i i5/os and related software Data migrations Version 6 Release 1 Note Before using this information and the product it supports,

More information

Controlling IBM i startup and shutdown

Controlling IBM i startup and shutdown Controlling IBM i startup and shutdown OCEAN Users Group Larry DrFranken Bolhuis Chief i-entist Frankeni Technology Consulting, LLC Middleville, MI. OCEAN Users Group 2018 2 Why are we here? Back in the

More information

IBM VisualAge for Java,Version3.5. Distributed Debugger for Workstations

IBM VisualAge for Java,Version3.5. Distributed Debugger for Workstations IBM VisualAge for Java,Version3.5 Distributed Debugger for Workstations Note! Before using this information and the product it supports, be sure to read the general information under Notices. Edition notice

More information

IBM i Version 7.3. Database Administration IBM

IBM i Version 7.3. Database Administration IBM IBM i Version 7.3 Database Administration IBM IBM i Version 7.3 Database Administration IBM Note Before using this information and the product it supports, read the information in Notices on page 45.

More information

Networking Quality of service

Networking Quality of service System i Networking Quality of service Version 6 Release 1 System i Networking Quality of service Version 6 Release 1 Note Before using this information and the product it supports, read the information

More information

IBM i Version 7.2. Systems management Logical partitions IBM

IBM i Version 7.2. Systems management Logical partitions IBM IBM i Version 7.2 Systems management Logical partitions IBM IBM i Version 7.2 Systems management Logical partitions IBM Note Before using this information and the product it supports, read the information

More information

IBM Tivoli Storage Manager for AIX Version Installation Guide IBM

IBM Tivoli Storage Manager for AIX Version Installation Guide IBM IBM Tivoli Storage Manager for AIX Version 7.1.3 Installation Guide IBM IBM Tivoli Storage Manager for AIX Version 7.1.3 Installation Guide IBM Note: Before you use this information and the product it

More information

System Administration Guide

System Administration Guide IBM Content Manager for iseries System Administration Guide Version 5 Release 1 SC27-1136-00 IBM Content Manager for iseries System Administration Guide Version 5 Release 1 SC27-1136-00 Note Before using

More information

ERserver. User Interface Manager APIs. iseries. Version 5 Release 3

ERserver. User Interface Manager APIs. iseries. Version 5 Release 3 ERserver iseries User Interface Manager APIs Version 5 Release 3 ERserver iseries User Interface Manager APIs Version 5 Release 3 Note Before using this information and the product it supports, be sure

More information

MIMIX. Version 7.0 Using License Manager. Installation and Security Information for MIMIX Products

MIMIX. Version 7.0 Using License Manager. Installation and Security Information for MIMIX Products MIMIX Version 7.0 Using License Manager Installation and Security Information for MIMIX Products Published: September 2010 level 7.0.01.00 Copyrights, Trademarks, and Notices Contents Who this book is

More information

Outlook Integration Guide

Outlook Integration Guide PracticeMaster Outlook Integration Guide Copyright 2012-2015 Software Technology, Inc. 1621 Cushman Drive Lincoln, NE 68512 (402) 423-1440 Tabs3.com Tabs3, PracticeMaster, and the "pinwheel" symbol ( )

More information

Exam : Title : Iseries system administration v5r2. Version : Demo

Exam : Title : Iseries system administration v5r2. Version : Demo Exam : 000-355 Title : Iseries system administration v5r2 Version : Demo 1. Users are reporting long response time delays in transactions that previously would run with sunscald response. The system administrator

More information

IBM. Systems management Management Central. IBM i 7.1

IBM. Systems management Management Central. IBM i 7.1 IBM IBM i Systems management Management Central 7.1 IBM IBM i Systems management Management Central 7.1 Note Before using this information and the product it supports, read the information in Notices,

More information

Connecting to System i System i Access for Web

Connecting to System i System i Access for Web System i Connecting to System i System i Access for Web Version 6 Release 1 System i Connecting to System i System i Access for Web Version 6 Release 1 Note Before using this information and the product

More information

SAFENET/400 REFERENCE GUIDE Version MP Associates of Westchester, Inc.

SAFENET/400 REFERENCE GUIDE Version MP Associates of Westchester, Inc. SAFENET/400 REFERENCE GUIDE Version 8.0 2007 MP Associates of Westchester, Inc. How to contact us Direct all inquiries to: Kisco Information Systems 89 Church Street Saranac Lake, New York 12983 Phone:

More information

Networking IP filtering and network address translation

Networking IP filtering and network address translation System i Networking IP filtering and network address translation Version 6 Release 1 System i Networking IP filtering and network address translation Version 6 Release 1 Note Before using this information

More information

Extended Search Administration

Extended Search Administration IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 Note! Before using

More information

TANDBERG Management Suite - Redundancy Configuration and Overview

TANDBERG Management Suite - Redundancy Configuration and Overview Management Suite - Redundancy Configuration and Overview TMS Software version 11.7 TANDBERG D50396 Rev 2.1.1 This document is not to be reproduced in whole or in part without the permission in writing

More information

IBM i Version 7.2. Connecting to your system Connecting to IBM Navigator for i IBM

IBM i Version 7.2. Connecting to your system Connecting to IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to IBM Navigator for i IBM Note Before using this information and

More information

IBM i Version 7.2. Database DB2 Multisystem IBM

IBM i Version 7.2. Database DB2 Multisystem IBM IBM i Version 7.2 Database DB2 Multisystem IBM IBM i Version 7.2 Database DB2 Multisystem IBM Note Before using this information and the product it supports, read the information in Notices on page 59.

More information

IBM. Systems management Logical partitions. System i. Version 6 Release 1

IBM. Systems management Logical partitions. System i. Version 6 Release 1 IBM System i Systems management Logical partitions Version 6 Release 1 IBM System i Systems management Logical partitions Version 6 Release 1 Note Before using this information and the product it supports,

More information

Security Single sign-on

Security Single sign-on System i Security Single sign-on Version 6 Release 1 System i Security Single sign-on Version 6 Release 1 Note Before using this information and the product it supports, read the information in Notices,

More information

Migrating to the P8 5.2 Component Manager Framework

Migrating to the P8 5.2 Component Manager Framework Migrating to the P8 5.2 Component Manager Framework Contents Migrating to the P8 5.2 Component Manager Framework... 1 Introduction... 1 Revision History:... 2 Comparing the Two Component Manager Frameworks...

More information

Introduction and Planning Guide

Introduction and Planning Guide Content Manager OnDemand for Multiplatforms Introduction and Planning Guide Version 7.1 GC27-0839-00 Content Manager OnDemand for Multiplatforms Introduction and Planning Guide Version 7.1 GC27-0839-00

More information

Outlook Integration Guide

Outlook Integration Guide Tabs3 Billing PracticeMaster General Ledger Accounts Payable Trust Accounting TA BS3.COM PracticeMaster Outlook Integration Guide Copyright 2012-2018 Software Technology, LLC 1621 Cushman Drive Lincoln,

More information

Connecting to System i Getting to know System i Navigator

Connecting to System i Getting to know System i Navigator System i Connecting to System i Getting to know System i Navigator Version 6 Release 1 System i Connecting to System i Getting to know System i Navigator Version 6 Release 1 Note Before using this information

More information

Printing Basic printing

Printing Basic printing System i Printing Basic printing Version 6 Release 1 System i Printing Basic printing Version 6 Release 1 Note Before using this information and the product it supports, read the information in Notices,

More information

Chapter 2 CommVault Data Management Concepts

Chapter 2 CommVault Data Management Concepts Chapter 2 CommVault Data Management Concepts 10 - CommVault Data Management Concepts The Simpana product suite offers a wide range of features and options to provide great flexibility in configuring and

More information

BrightStor ARCserve Backup for Windows

BrightStor ARCserve Backup for Windows BrightStor ARCserve Backup for Windows Volume Shadow Copy Service Guide r11.5 D01191-2E This documentation and related computer software program (hereinafter referred to as the "Documentation") is for

More information

2012 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Excel, Lync, Outlook, SharePoint, Silverlight, SQL Server, Windows,

2012 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Excel, Lync, Outlook, SharePoint, Silverlight, SQL Server, Windows, 2012 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Excel, Lync, Outlook, SharePoint, Silverlight, SQL Server, Windows, Windows Server, and other product names are or may be registered

More information

IBM. Mailbox. Sterling B2B Integrator. Version 5.2

IBM. Mailbox. Sterling B2B Integrator. Version 5.2 Sterling B2B Integrator IBM Version 5.2 Sterling B2B Integrator IBM Version 5.2 Note Before using this information and the product it supports, read the information in Notices on page 37. Copyright This

More information

IBM DB2 Query Patroller. Administration Guide. Version 7 SC

IBM DB2 Query Patroller. Administration Guide. Version 7 SC IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 Before using this information and the product it supports, be sure

More information

System i. Networking REXEC. Version 5 Release 4

System i. Networking REXEC. Version 5 Release 4 System i Networking REXEC Version 5 Release 4 System i Networking REXEC Version 5 Release 4 Note Before using this information and the product it supports, read the information in Notices, on page 11.

More information

Lotus esuite Workplace for IBM Network Station Manager for AS/400 Date: December 8, 1998

Lotus esuite Workplace for IBM Network Station Manager for AS/400 Date: December 8, 1998 Lotus esuite Workplace for IBM Network Station Manager for AS/400 Date: December 8, 1998 TABLE OF CONTENTS ----------------- ----------------- -Prerequisites -Installation -Migration -Auto-configuration

More information

Networking TCP/IP routing and workload balancing

Networking TCP/IP routing and workload balancing System i Networking TCP/IP routing and workload balancing Version 6 Release 1 System i Networking TCP/IP routing and workload balancing Version 6 Release 1 Note Before using this information and the product

More information

IBM i Version 7.2. Connecting to your system Connecting to IBM Navigator for i IBM

IBM i Version 7.2. Connecting to your system Connecting to IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to IBM Navigator for i IBM Note Before using this information and

More information

Programming Virtual Terminal APIs

Programming Virtual Terminal APIs System i Programming Virtual Terminal APIs Version 6 Release 1 System i Programming Virtual Terminal APIs Version 6 Release 1 Note Before using this information and the product it supports, read the information

More information

System i. Networking RouteD. Version 5 Release 4

System i. Networking RouteD. Version 5 Release 4 System i Networking RouteD Version 5 Release 4 System i Networking RouteD Version 5 Release 4 Note Before using this information and the product it supports, read the information in Notices, on page 9.

More information

IBM. Connecting to System i Getting to know System i Navigator. System i. Version 7 Release 1

IBM. Connecting to System i Getting to know System i Navigator. System i. Version 7 Release 1 IBM System i Connecting to System i Getting to know System i Navigator Version 7 Release 1 IBM System i Connecting to System i Getting to know System i Navigator Version 7 Release 1 Note Before using

More information

Accelerated Library Framework for Hybrid-x86

Accelerated Library Framework for Hybrid-x86 Software Development Kit for Multicore Acceleration Version 3.0 Accelerated Library Framework for Hybrid-x86 Programmer s Guide and API Reference Version 1.0 DRAFT SC33-8406-00 Software Development Kit

More information

SAFENET/400 FOR THE IBM SYSTEM i5 IMPLEMENTATION GUIDE Version MP Associates of Westchester, Inc.

SAFENET/400 FOR THE IBM SYSTEM i5 IMPLEMENTATION GUIDE Version MP Associates of Westchester, Inc. SAFENET/400 FOR THE IBM SYSTEM i5 IMPLEMENTATION GUIDE Version 8.0 2007 MP Associates of Westchester, Inc. How to contact us Direct all inquiries to: Kisco Information Systems 89 Church Street Saranac

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations 6.1.2.0 Client Installation and User's Guide SC27-2809-01 IBM Tivoli Storage Manager FastBack for Workstations 6.1.2.0 Client Installation and User's

More information

Guide to Vision itera Availability templates

Guide to Vision itera Availability templates Guide to Vision itera Availability templates Copyright Copyright Halcyon - A Division of HelpSystems. All rights reserved. This document is intended as a guide to the Vision itera Availability monitoring

More information

IBM IMS Database Solution Pack for z/os Version 2 Release 1. Overview and Customization IBM SC

IBM IMS Database Solution Pack for z/os Version 2 Release 1. Overview and Customization IBM SC IBM IMS Database Solution Pack for z/os Version 2 Release 1 Overview and Customization IBM SC19-4007-04 IBM IMS Database Solution Pack for z/os Version 2 Release 1 Overview and Customization IBM SC19-4007-04

More information