I've often wanted to find out which job is holding up a single-threaded job queue. The Work with Active Jobs (WRKACTJOB) command shows which jobs are running in a subsystem, but it doesn't identify the job queue name. If you have more than one single-threaded job queue assigned to the subsystem, you can't determine which job queue originated a job.
After a little research, I was surprised to find a command that does list all job queues and their associated active jobs. It is the Work with User Jobs (WRKUSRJOB) command executed in the following form:
WRKUSRJOB USER(*ALL) + STATUS(*ACTIVE) + JOBTYPE(*BATCH) + ASTLVL(*BASIC)
The trick to making this work is to use the basic assistance level. In this case, the Work with Jobs panel lists each job queue; and below the job queue name, a list of the jobs running from the queue.
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