× 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.



The file QADBERAP is Q=System, A=Database File, DB=Database component, E=Edit, R=Rebuild, A=Access, P=Path. The file QADBERAP is the implementation object for the graphical OpsNav interface to the "Edit Rebuild Access Paths"; i.e. effectively, EDTRBDAP command.

I infer from the errors that either of the following:

- The program SA010R attempts to perform some update activity on a file which apparently effected an error [e.g. CPF5090] that suggested there was an invalid access path of the data being accessed. The response to the error included the "verify file" routine of the query engine attempting to delete the record which recorded\represented the invalid access path, presumably because the access path had since been rebuilt; i.e. CPF3145 or similar was logged. If that is the case, then likely the code has a defect for failing to adopt the necessary authority to effect the DELETE FROM QRECOVERY/QADBERAP WHERE.

- The program SA010R attempts delete activity on a file, the CPF5090 prevents opening the file, some query component activity attempts to access the QADBERAP file in QRECOVERY with regard to the restriction\error, that code does not properly adopt authority to do so, and the default error handling for "not authorized" is manifest; that the origin for the condition was not directly related to the SQL request, but is reported as the object named in the -550 SQL code details is merely a side effect of the defect... and the SQL DELETE may or may not have completed without error without said defect [e.g. perhaps cpf5090 is manifest as sql0901 or similar].

Regards, Chuck

Charles Wilt wrote:

Our box went down hard last night due to a failed power supply.

We noticed this morning during our End of Day process, the following
messages in the job log..

*NONE Command 12/16/09 06:24:21.051840
QCLCLCPR QSYS 04CB FS001C HLTHPRDPGM 037D
Message: 48400 - CALL PGM(SA010R) /* parameters */
CPF4269 Escape 40 12/16/09 06:24:21.227928
QQQSRVV1 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . : QQQVFILE
From procedure . . : QQQSNDPMSG
Statement . . . . . : 6291
To module . . . . . : QSQOPEN
To procedure . . . : FULL_OPEN
Statement . . . . . : 23166
Message: Not authorized to object QADBERAP in QRECOVERY type *FILE.
Cause . : You do not have the necessary authority to perform the
function that you requested. If you are not authorized to a logical file, you may need authority to the based-on files of the
logical file. Recovery . . . : Get the necessary authority from
either your security officer or from the owner of the object. Then try your request again.
SQL0551 Diagnostic 30 12/16/09 06:24:21.228648
QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . : QSQDELET
From procedure . . : CLEANUP
Statement . . . . . : 13437
To module . . . . . : QSQDELET
To procedure . . . : CLEANUP
Statement . . . . . : 13437
Message: Not authorized to object QADBERAP in QRECOVERY type *FILE.
Cause . : An operation was attempted on object QADBERAP in
QRECOVERY type *FILE. This operation cannot be performed without
the required authority. Recovery . . . : Obtain the required authority from either the security officer or the object owner. If you are not authorized to a logical file, obtain the authority
to the based-on files of the logical file. Try the operation
again.

I've googled the file, but don't see anything telling me what it is.

Does anywhere here know anything about it, or should we call IBM?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.