Ideas on how to spot problems of table conflicts -- MIDRANGE-L

Subject: Ideas on how to spot problems of table conflicts
From: Thomas Burrows <thomas.burrows.1957@xxxxxxxxx>
Date: Tue, 24 Apr 2018 13:55:18 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We have a mainframe that is sending data over. We are getting some SQL
errors 911 and 913's.

Any ideas how to spot these issues on the iSeries?

Would help if we had the job names that are running on the iSeries.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Ideas on how to spot problems of table conflicts , Justin Taylor
Re: Ideas on how to spot problems of table conflicts , Paul Roy

This mailing list archive is Copyright 1997-2025 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.