Iseries file monitor pci software#

We monitored for the following error message: Inside MessengerPlus, we set up a QSYSOPR message queue monitor to look for a specific error message that occurred whenever a job crashed because it was unable to obtain a locked record. We recently set up a system to do this by using BytwareвЂ™s MessengerPlus.

Iseries file monitor pci software#

If you have the programming knowledge or third-party software that can detect and react to job messages when they occur, you can also configure your system to automatically answer your file or record allocation errors whenever they appear. You can then make a decision on how best to proceed. This will display a screen that shows which jobs are currently locking the object your job is trying to access. Right-click on the object and select Lock Holders from the pop-up menu that appears. Look for the object that has a Lock Status of Requested. Like its green-screen counterpart, the OpsNav Locked Objects screen will also show you the list of objects that the job is either currently holding or requesting. Right-click on the job thatвЂ™s waiting for a lock and select Detailsв†’Locked Objects from the pop-up menu that appears. YouвЂ™ll see a screen that looks something like this. To perform the same process in OpsNav V5R4M x, open the Work Managementв†’Active Jobs node under your target partition. In that case, you just have to wait for the job to resolve the lock or try to locate the locked object by using OpsNav. It just hangs and I canвЂ™t get any information. There have been times when IвЂ™ve run WRKOBJLCK and it doesnвЂ™t let me see the name of the locking job. However, WRKOBJLCK doesnвЂ™t always provide the name of the locking job. WRKOBJLCK OBJ( library/object_name) OBJTYPE(*FILE)ДЄnd this should tell you the name of the job that is locking your file. You can then run the following Work with Object Lock (WRKOBJLCK) command to determine who is holding the lock. In this case, my job is waiting for the SOURCE file in library JOEHTST. Look for any entry that has a status of REQ (Request) with a member lock that says WAIT. On the Work with Job screen that appears, select option 12 (Work with Locks) to see all the file locks the job is currently holding or requesting. On the green screen, use the Work with Job (WRKJOB) command to view the job that is waiting on a record or file lock. HereвЂ™s the drill for locating your locked object or record using either technique. One way to locate it is by using i5/OS green screen commands the other is by using iSeries Navigator (OpsNav). There are two ways to figure out which locked object a job is waiting for.

How can I tell which object the job is waiting for before it crashes and which user has that object locked? IвЂ™m running i5/OS V5R4M5. I have a recurring problem with file locks on my system, where critical jobs are stuck in lock waiting status (LCKW) waiting for an object before crashing on a file allocation error. Discovering Which Locked Object is Holding Up Your Job