Re: SQL Misbehaving

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

Did you F10 and look at messages that precede this one?

At 01:52 PM 3/19/02 -0500, you wrote:
>Message ID . . . . . . :   QRY2293       Severity . . . . . . . :   30
>  Message type . . . . . :   Information
>
>  Message . . . . :   Query cannot be run.  See lower level messages.
>  Cause . . . . . :   An error occurred when the query to be run was opened
>or
>    while output was being created.  Either a cancel reply was received to an
>    inquiry message about the problem, or the request was ended abruptly
>without
>    use of an inquiry message.  In most cases the problem involves data that
>is
>    not correct or data that is not being used correctly.
>  Recovery  . . . :   To determine the cause of the problem, press F10 or use
>    the Display Job Log (DSPJOBLOG) command to view the messages that were
>    logged immediately before this message.  (If you are in a Work With
>Queries
>    session, the diagnostic information will not be left in the job queue
>unless
>    you cancel the session when you return to the display on which you are
>    working.)  Inspect any partially completed printer output before
>discarding
>    it.  Correct the problem, then repeat your request.
>
>Bottom
>  Press Enter to continue.
>
>----- Original Message -----
>From: <rob@dekko.com>
>To: <midrange-l@midrange.com>
>Sent: Tuesday, March 19, 2002 1:45 PM
>Subject: Re: SQL Misbehaving
>
>
> >
> > Now, can we see the detail between:
> >  SELECT ODOBNM, ODOBTP, ODOBAT, ODOBTX, ODCTIM, ODOBOW, ODCRTU,
> >       ODUCNT FROM ogunmadewa/as400usr WHERE ODUCNT >0 and odobnm like 'Q%'
> >
> > and
> >
> >
> >       Query cannot be run.  See lower level messages.
> >
> >
> > Rob Berendt
> > --
> > "They that can give up essential liberty to obtain a little temporary
> > safety deserve neither liberty nor safety."
> > Benjamin Franklin
> >
> >
> >
> >                     "Dare @ Work"
> >                     <oludare                  To:
><midrange-l@midrange.com>
> >                     Sent by:                  cc:
> >                     midrange-l-admin@mi       Fax to:
> >                     drange.com                Subject:     Re: SQL
>Misbehaving
> >
> >
> >                     03/19/2002 01:39 PM
> >                     Please respond to
> >                     midrange-l
> >
> >
> >
> >
> >
> >
> >  I don't understand " Can you copy/paste from the last SQL looking entry
>to
> > the first device
> >  looking entry?"
> >
> >   > SELECT ODOBNM, ODOBTP, ODOBAT, ODOBTX, ODCTIM, ODOBOW, ODCRTU,
> >       ODUCNT FROM ogunmadewa/as400usr WHERE ODUCNT >0 and odobnm like 'Q%'
> >       Query cannot be run.  See lower level messages.
> >       Session ended abnormally. It has been recovered.
> >       Current connection is to relational database REDX.
> >       Session was saved and started again.
> >       Current connection is to relational database REDX.
> >    > SELECT ODOBNM, ODOBTP, ODOBAT, ODOBTX, ODCTIM, ODOBOW, ODCRTU,
> >       ODUCNT FROM ogunmadewa/as400usr WHERE ODUCNT >0 and odobnm like 'Q%'
> >       Session ended abnormally. It has been recovered.
> >       Current connection is to relational database REDX.
> >
> > ----- Original Message -----
> > From: <rob@dekko.com>
> > To: <midrange-l@midrange.com>
> > Sent: Tuesday, March 19, 2002 1:32 PM
> > Subject: Re: SQL Misbehaving
> >
> >
> > >
> > > Is there anything further up on your joblog?  All of that pointed to an
> > > error with your device description.  Which doesn't make sense unless the
> > > SQL had a problem creating the output.
> > >
> > > Can you copy/paste from the last SQL looking entry to the first device
> > > looking entry?
> > >
> > > Rob Berendt
> > > --
> > > "They that can give up essential liberty to obtain a little temporary
> > > safety deserve neither liberty nor safety."
> > > Benjamin Franklin
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.