Re: RUNSQLSTM 80 byte limit question -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: RUNSQLSTM 80 byte limit question
From: "Buck Calabro" <buck.calabro@xxxxxxxxxxxx>
Date: Tue, 22 Jun 2004 10:14:27 -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>

Hi Mark,

> Does anyone know how to make RUNSQLSTM
> recognize more than 80 bytes per line or another
> command to use (perhaps within STRSQL) to
> read a longer source command record.

The FAQ has an example of a command line SQL front end that uses 1280
bytes for any SQL statement.  It uses STRQMQRY and a little CL.
Perhaps it can be modified for your use?  http://faq.midrange.com
  --buck

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.