RE: SQL

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