How Consequential are Pages and Faults?
Q: The Work with System Status (WRKSYSSTS) screen shows the database and nondatabase faults plus the database and nondatabase pages. What exactly are the pages? What kind of number should I look for when monitoring the system in these values? I've been told that I shouldn't worry too much about the pages. Is this correct?
A: The database and nondatabase pages on the WRKSYSSTS screen show the rate at which data is being brought in from the disk system into that pool of memory. Each page consists of 16KB of data. You don't need to worry about this number much. Use it to help monitor faults by comparing the page values to the fault values. For instance, if you show a paging rate and a fault rate of 200 each, it usually means that none of the data that the job is trying to access is in memory. If you are performing a job such as a backup, this does not represent a problem. Under this circumstance, you don't need to worry about the fault rate, either, because it is non-normal workload processing.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online