RE: Foreign key constraint problem -- MIDRANGE-L

Subject: RE: Foreign key constraint problem
From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
Date: Thu, 31 May 2007 16:22:38 -0400
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

In STRSQL it was set to *LANGIDSHR, I changed to *HEX.

I was actually using RUNSQLSTM. It says SRTSEQ(*JOB), which came from the
job description, which in turn came from system value QSRTSEQ, which is
*LANGIDSHR.

Looks like I'm going to be reading up on what changing this will to for (or
to) me.

Follow-Ups:

RE: Foreign key constraint problem , Jeff Crosby

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