|
I didn't think so. I just wanted to be sure. I've been bitten by that a few time. No offense intended. Rick Chevalier AmeriCredit AITS (817) 525-7178 rick.chevalier@xxxxxxxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CWilt@xxxxxxxxxxxx Sent: Tuesday, December 23, 2003 2:37 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: using STRSQL statement fails but works with Ops-Nav Rick, It is set to display. I guess I should have been specific when I said it "returns no records". What I meant was that the screen displays output with the "*****End of Data******" as the first line and the "no data selected for output" message at the bottom of the screen. Thanks for the replies, but just so you know. I've been using STRSQL for 7 years...the problem is not the result of something basic being set wrong. Charles > -----Original Message----- > From: Chevalier, Rick [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx] > Sent: Tuesday, December 23, 2003 3:17 PM > To: Midrange Systems Technical Discussion > Subject: RE: using STRSQL statement fails but works with Ops-Nav > > > What about the output option? > > Rick Chevalier > AmeriCredit AITS > > (817) 525-7178 > rick.chevalier@xxxxxxxxxxxxxxx > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > CWilt@xxxxxxxxxxxx > Sent: Tuesday, December 23, 2003 1:01 PM > To: midrange-l@xxxxxxxxxxxx > Subject: RE: using STRSQL statement fails but works with Ops-Nav > > Rick, > > It is set at *RUN. > > Charles > > > > -----Original Message----- > > From: Chevalier, Rick [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx] > > Sent: Tuesday, December 23, 2003 1:35 PM > > To: Midrange Systems Technical Discussion > > Subject: RE: using STRSQL statement fails but works with Ops-Nav > > > > > > Charles, > > > > Before we start digging into the statement have you checked > > you options on STRSQL? In particular F13 -> option 1 (Change > > session attributes) -> Statement processing and SELECT > > output. If you have anything other than *RUN for processing > > and 1 for output you won't see the result set. All you see > > is a message telling you the statement completed > > successfully. Take a look and let us know. > > > > HTH, > > > > Rick Chevalier > > AmeriCredit AITS > > > > (817) 525-7178 > > rick.chevalier@xxxxxxxxxxxxxxx > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > > CWilt@xxxxxxxxxxxx > > Sent: Tuesday, December 23, 2003 12:28 PM > > To: midrange-l@xxxxxxxxxxxx > > Subject: using STRSQL statement fails but works with Ops-Nav > > > > The following SQL statement works fine from the Ops-Nav "Run > > SQl Statements" > > and as a Query Manager SQL query. But when run from the > > STRSQL screen, it > > returns no records yet it doesn't give any error message either. > > > > Note that the QM query and the STRSQL are done interactively > > from the same > > job, so it isn't a problem with different files being used. > > > > I'm guessing STRSQL has a problem with the common-table > > expression or the > > correlated sub-query. > > > > Has anyone seen this before? > > > > Thanks, > > Charles > > > > > > with tbl as (select pimodl, piiall, dochdt > > from mason/mppriv, mason/tpdocu > > where pimodl = domelc and dochdt >= 20031223 > > group by pimodl, piiall, dochdt > > order by pimodl, dochdt asc) > > > > select tbl.pimodl, tbl.piiall, tbl.dochdt, (piiall - > > (select sum(b.doqty) > > from mason/tpdocu b > > where b.domelc = tbl.pimodl > > and b.dochdt between 20031223 and tbl.dochdt > > )) as EndingQty > > from tbl > > order by 1, 3 asc > > _______________________________________________ > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.