IBM AS400/iSeries find which job is blocking a job queue

ibm-midrangequeue

I'm working on an iSeries with system version 6.1. Some job is keeping other jobs in its queue to process. I know the queue name (PUR1) and see it has an abnormally amount of jobs in it. My understanding is that when a job runs, it moves from it original job queue. So how can I find which job is keeping the others from being processed?

Best Answer

A job is removed from the job queue as part of starting it. If you have multiple job queues attached to the subsystem, and multiple jobs running in the subsystem, then you have a bit of a challenge. Take a look at the job queue for each job currently running in the subsystem. One of the first few messages should mention the name of the job queue.

Related Solutions

Windows Network Drive Map for AS400 IFS (IBM iSeries)

To map to an IFS folder from a Windows machine on the network, you must first share it using iSeries Navigator. Ask your AS/400 server admin, or someone with enough authority to create the share. Here are instructions for creating a share:

Open iSeries Navigator
Connect to your AS/400 system.
Expand Network->Servers
Click TCP/IP to see a list of servers.
Right-click on iSeries NetServer and click Open
Right-click on shared objects and then click New and then File.

You also need to have the netserver job running on the AS/400. You can start it from iSeries Navigator or using the following AS/400 command if it isn't running:

STRTCPSVR SERVER(*NETSVR)

After that, you map just like any Windows server. You can use the NET USE command, right-click on my computer and map a drive, or type the address in your explorer window like \\NetServerName\

A big issue to consider is the name of your net server does not have to be the same as the name of your AS/400. Many systems like to put a Q in front of the name as the netserver name. You'll find this in the NetServer properties screen in iSeries Navigator. You may have to add this system name to your local hosts file or your DNS server, if you have access to that.

QNTC and Windows Server 2008 R2

Our programmers have managed to find a solution to the problem!

The solution comes in the form of an iSeries PTF (SI38554). Note: This requires an IPL to apply the fix.

We have a tested this PTF on our test/dev machine and we can see the shares on the 2008 R2 server and also read/write to them as well.

Since we can't just IPL the live machine at will, they have come up with an ingenious solution to get us by in the mean time. What they've done is set up a share on the test machine (which has had the PTF and been IPL'ed) which basically passes through to the Server 2008 machine - i.e on the live system, doing a WRKLNK '/QNTC/QDEVSYS/SVR01' will show the share contents of the 2008 R2 server.

I hope this helps anybody else having this problem - hopefully it will save someone else a lot of time and effort.

Best Answer

Related Solutions

Windows Network Drive Map for AS400 IFS (IBM iSeries)

QNTC and Windows Server 2008 R2

Related Topic