From: Greg Shaull To: All
We have more than 200 users on our B70. We have a problem with a single user submitting many jobs to the job queue at one time ahead of other system users. The other users must then wait for all of the jobs of the first user before their job is started.
We need a job queue strategy that will allow the system to be more fairly shared among the users. We need to be able to limit the number of active jobs for a single user when there are jobs for other users waiting to start.
From: Tim Johnston To: Greg Shaull
I do not know if I can help you create a strategy, but I will help you try to learn the basics. Go to a command line and key in:
DSPSBSD QBATCH and take option #6, Job Queue Entries. I am at V2R1M1, so I see three entries, QBATCH, QS36-EVOKE and QTXTSRCH. Let's ignore for the time being the multiple entries and concentrate on one, QBATCH. As you will notice, there is a number of maximum active jobs. This is the total number of jobs that can run from the queue. QBATCH has 1, so it is considered a single- threaded job queue, one job at a time. Many jobs must be run one after the other, so you need this kind of queue. However, you can change the number of active jobs, or the number of jobs by each priority.
I wouldn't suggest monkeying with QBATCH. Leave it alone, like a honeymoon couple, and make your own subsystem and job queue. By letting more jobs run at a time from one job queue, system throughput will increase, but performance will degrade. Here is my strategy. I have a subsystem attached to its own pool in memory. I also have the system value QPRFADJ set to a 2, and the system will allocate and deallocate memory as it sees fit. The subsystem's sole purpose is for some of my batch jobs. I have attached a job queue to it with a maximum number of three active jobs out of the queue, with each priority letting one job run at a time.
Most of my jobs are compiles, and I have a data area which holds the priority used for the previous compile. I grab that and add one to it; if it is greater than 9, I reset it to 1, submit the job with that priority, and send the priority back to the data area for the next time. That way, I can have three compiles or any other jobs running at once. I have found that with more than three at a time, users start complaining about performance.
You might want to do something similar-but in your CL, route jobs to a certain priority, by the importance of the job. The highest priority is 1; the lowest is 9. Remember, the total number of jobs for the job queue will only let that number of jobs run simultaneously. Then the priorities take over.
I hope that I have whetted your whistle. If you are interested in a further discussion, let me know.
From: Carter Combs To: Greg Shaull
Greg, in the offending person's User Profile (or for all users if you like), change the maximum job queue priority to 5 (the system default) or lower (6- 9). This will put them on a FIFO (first-in, first-out) basis. Get them all on an equal footing, then let the system operator make changes as needed.
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