× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What would cause a MCH5802 - Lock operation for object TRACE TRACE not satisfied.
I had two occurrences last night.
Both were following RSTLIBBRM(s) of test environment.
One job 811697 opened the same file 63 seconds earlier with no issue.
According to the message details, the first job, 811697, which was successful, was the lock holder.

Checking the joblog for the first job, 811697, I see it took 4 minutes, 32 seconds for the program to open its 4 files.
Normally this is 1 second.
Date sent . . . . . . : 03/23/16 Time sent . . . . . . : 02:29:56
Date sent . . . . . . : 03/23/16 Time sent . . . . . . : 02:34:28

I'm thinking it could be related to an access path being rebuilt following the RSTLIBBRM.
What is puzzling is I don't see a CPF3145 Access path built for member for the file in question.
I do see many other CPF3145.

The TRACE file in question only has 1 access path.
The file is quite large.
Member List
Source Creation Last Change Deleted
Member Size Type Date Date Time Records Records
TRACE 7329742848 02/05/05 03/23/16 08:33:24 5,246,938 18,248,817

Subsystem class - Default wait time in seconds . . . . . . . . . . : 30

Access path maintenance . . . . . . . . . . : MAINT *IMMED
Access path recovery . . . . . . . . . . . : RECOVER *NO
Maximum file wait time . . . . . . . . . . : WAITFILE *IMMED
Maximum record wait time . . . . . . . . . : WAITRCD *NOMAX

I have a few unanswered questions.
1) What changed, we've never seen this MCH5802 error following a RSTLIBBRM?
2) Why was the first job successful and 2nd job failed?
3) If TRACE01 access path was rebuilt, why did the system not log a CPF3145?

I read many threads related to MCH5802, discuss increasing the 30 second class default wait time.


MCH5802 Escape 20 03/23/16 02:30:59.863601 < ckMiObject 001368 QDBOPEN QSYS *STMT
From Program . . . . . . . : RmslLockMiObject
To module . . . . . . . . . : QDBOPEN
To procedure . . . . . . . : QDBOPEN
Statement . . . . . . . . . : 19483
Message . . . . : Lock operation for object TRACE TRACE not satisfied.
Cause . . . . . : The lock operation was not satisfied for object TRACE
TRACE in the specified time interval of 63 seconds. The lock holder type is
1. The lock holder name is CURBSTONE MISSLICE 811697. The lock holder
thread identifier is X'000000000000007F'. The lock holder type has the
following meaning: 0 - The lock holder is a Licensed Internal Code (LIC)
task. The lock holder name and thread identifier do not apply. 1 - The lock
holder is a job. 2 - The lock holder is a transaction control structure.
The lock holder name and thread identifier do not apply.
CPF4126 Escape 50 03/23/16 02:30:59.864023 QDBSIGEX QSYS 05A4 AICURB IC08XXCHGP *STMT
To module . . . . . . . . . : AICURB
To procedure . . . . . . . : AICURB
Statement . . . . . . . . . : 1000001
Message . . . . : Object not available for file TRACE.
Cause . . . . . : Cannot allocate object for file TRACE in library MSPENWORK
because object not available. The object is specified in reason code 1 as
follows: 1 -- Access path for Member TRACE 2 -- Format *N for File *N in
Library *N 3 -- Member TRACE for File *N in Library *N 4 -- Trigger
program *N in Library *N Recovery . . . : Use the Work with Object Lock
(WRKOBJLCK) command to see which job or thread within your job has the
object locked. Try your request again when the object is available.
RNX1216 Escape 99 03/23/16 02:31:00.712231 QRNXIE QSYS *STMT AICURB IC08XXCHGP *STMT
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : SignalException
Statement . . . . . . . . . : 26
To module . . . . . . . . . : AICURB
To procedure . . . . . . . : AICURB
Statement . . . . . . . . . : 1000001
Message . . . . : Error message CPF4126 appeared during OPEN for file TRACE.
Cause . . . . . : RPG procedure AICURB in program IC08XXCHGP/AICURB received
the message CPF4126 while performing an implicit OPEN operation on file
TRACE. The actual file is TRACE. Recovery . . . : Check the job log for a
complete description of message CPF4126, and contact the person responsible
for program maintenance. If the file has a device type of SPECIAL, there may
be no message in the job log.
RNQ1216 Sender copy 99 03/23/16 02:31:01.045936 QRNXIE QSYS *STMT QRNXIE QSYS *STMT
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : InqMsg
Statement . . . . . . . . . : 15
To module . . . . . . . . . : QRNXMSG
To procedure . . . . . . . : InqMsg
Statement . . . . . . . . . : 15
Message . . . . : Error message CPF4126 appeared during OPEN for file TRACE
(C S D F).
Cause . . . . . : RPG procedure AICURB in program IC08XXCHGP/AICURB received
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.