My operating system was upgraded from V5R3 to V5R4

Tags:
Application development
AS/400
CLP
DataCenter
DB2 Universal Database
Project management
RPG
RPGLE
my operating system was just upgraded from V5R3 to V5R4. All my cobol programs are compiled with *none commitment control and a target release of V5R3M0. However after upgrading the operating system while executing the programs -913 errors are being encountered. The same programs are getting executed fine on a separate box which still is on V5R3. Could anyone provide me with some help?

Answer Wiki

Thanks. We'll let you know when a new response is added.

what is a “-913 error” ?

=====================================================

The previous answer wasn’t much help. On the other hand, the question didn’t give much to go on and what was given was contradictory — tags included “RPG” and “RPGLE” but the question asked about COBOL programs. It also referenced “-913 errors” even though the errors have essentially nothing to do with COBOL (nor RPG).

Because there was also a reference to “*none commitment control”, it seems likely that the error is actually the old SQLCODE -913.

That should translate to SQLSTATE 57033 and also should show message SQL0913. The message text should be “The requested object &1 in &2 type *&3 is either in use by another application process or a row in the object is in use by either another application process or another cursor in this application process.”

2nd-level text:

Look at the previously listed messages in the job log (DSPJOBLOG command) or from interactive SQL press F10 (Display messages in job log) on this display to determine if this is an object or record lock wait time out. Do one of the following:<ul>
<li>If the object is locked by another application process, try the SQL statement again when the object is not in use. Use the Work with Object Locks (WRKOBJLCK) command to determine who is currently using the object.</li><li>If the object is a schema and an attempt was made to create a table, view, or index into this schema under commitment control, a save-while-active operation may be in progress on the same schema by another job in the system. Try the request again when the save-while-active processing is complete.</li><li>If a record is locked by another application process, try the SQL statement again when the record is not in use. The Display Record Locks (DSPRCDLCK) command will determine who is currently using the record.</li><li>If this is a record lock held by another cursor in the same application process, you must issue a COMMIT, ROLLBACK, or another FETCH statement on the cursor that is holding the lock before issuing this SQL statement. If this error occurs frequently, use the Change Physical File (CHGPF), Change Logical File (CHGLF), or Override Data Base File (OVRDBF) command to change the object or record wait time out.</li>
</ul>

Without knowing at least a little more about the definition of the tables, there’s not much more that can be said here.

Tom

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following