× 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.



Is the "naming" field in RUNSQLSTM set to *SYS or *SQL? What about in
interactive SQL?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
Sent: Thursday, January 18, 2007 4:24 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL

The log is saying 
SQL7008 position 1 "file in library not valid for operation" but like I
said,  I can do it interactively

-----Original Message-----
From: midrange-l-bounces+jacandidi=rutgersinsurance.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+jacandidi=rutgersinsurance.com@xxxxxxxxxxxx]
On
Behalf Of Elvis Budimlic
Sent: Thursday, January 18, 2007 4:17 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL

You're not qualifying library so that could be a problem.  Either
qualify
the file (i.e. LIB/FILEA) or have it as current library in your library
list
or specify DFTRDBCOL(LIB) on RUNSQLSTM command itself.

Also, check the resulting spooled file.  It'll tell you exactly what the
error is.

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: RE: SQL

It's simple statement 
Update filea
Set fielda = 'xx'  where fieldb ='yy'

When I run this interactively, it runs fine.I created the source file
and
enter these commands into it then do a RUNSQLSTM using the source file x
in
lib y using member z, it errors out




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.