Shared Pools vs. Nonshared Pools
From: David Baxter To: All
My operations manager loves shared pools. In my experience, shared pools did not work well with ad hoc or query type reports. Everything is going through pool 2 (*BASE) and the communications jobs have their own pool, also in *BASE.
1. If you wish your interactive users to have better response, shouldn't you keep the batch jobs in their own nonshared pool?
2. Should the devices on the communications line be given their own nonshared pool?
I came from a S/36 shop four years ago and do not believe that shared pools are the best thing since sliced bread (my own prejudice). I know what all the disk makers are saying-cache, cache, and more cache. Yet, it seems to me that since batch jobs (queries and the like) eat up all available processing power, you should keep them in their own nonshared pool and separate your communications and noncommunications interactive users in nonshared pools. Any thoughts?
From: Gregory Leister To: David Baxter
I'll address your first question. If your run priority for interactive jobs is at 20 and batch jobs are at 50, then the interactive jobs will process first. Then interactive jobs should take whatever CPU it needs and batch gets what's left. We have separated our batch jobs into their own nonshared pool and it works fine.
What you don't want to do is give a nonshared pool more memory than it needs because of course it would be wasted. There are exceptions to the priorities. Try setting your time slices for your interactive jobs around 250 or 300. If you find too many jobs timing out, you will need to increase the time slice.
From: Michael Catalani To: David Baxter
You can use shared pools, but use one shared pool for interactive, one for batch, one for communications and one for spool. The idea behind using shared pools is so that multiple subsystems can use the same pool of memory. You would want to do this, for example, if you have a tremendous number of interactive users attempting to sign on at one time.
The subsystem monitor only allows one sign-on at a time per subsystem. So you can create multiple interactive subsystems pointing to the same shared pool. This allows several concurrent sign-ons, but all interactive jobs run out of the same pool of memory. But you are correct in saying that you do not want your batch and interactive jobs running out of the same shared pool. This can cause you a lot of grief.
For your second question, it is usually a good idea to separate your communication jobs into their own pool and subsystem. I have three remote sites. They all have their own subsystem but point to the same shared pool. This way, I can keep one remote site down so that I can perform maintenance on it without affecting the other sites. This allows me to add job queue entries to my California subsystem without having to affect users across town on remote.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
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