I've found a way to identify what jobs are running from a job queue and what is holding others up from running.
I use the Work with User Jobs (WRKUSRJOB) command.
WRKUSRJOB USER(*ALL) STATUS(*ALL) +
JOBTYPE(*BATCH) ASTLVL(*BASIC)
You can see what is displayed with this command in 10.
You can see what is displayed with this command in Figure 10.
You could use the Work with Active Jobs (WRKACTJOB) and Work with Job Queues (WRKJOBQ) command to get this same information, but I've found this method much more concise.
What Job is Holding Mine Up?
Figure 10 WRKUSRJOB Display
UNABLE TO REPRODUCE GRAPHICS
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