Re: SQL Problem in upgrading to V4R3 from V4R2

This is possibly worth a try, although I am just venturing a guess, do you have 
a
WRKRDBDIRE (Work Relational Database Directory Entry) for *LOCAL defined?  I 
know
this gave us a problem with ODBC.

    HTH

        Pete Massiello

Murali Bhaavan wrote:

> Hi friends,
>
> We recently moved from V4R2 to V4R3 after having an initial hitch-up
> with the first set of CDs. Now the new version (V4R3) is installed properly
> on our system (S20). We are facing some problems after we moved to the
> new release. One of the problems we are facing is as follows......
>
>  In SQL If we take  <F4> On "SELECT fields  . . . . . . ." of SELECT
> statement to get the column descriptions, its giving the following error :
>
>    "No fields available in chosen file or files". When I pressed <F1> on
> this error message, It says the following :
>
>   Cause . . . . . :   There are no fields that are available in the file or
>          files that were selected from the file list.  One of the following
>          conditions has occurred:
>
>       -- The file has been deleted.
>       -- Authorization to the file or files has changed.
>       -- The file or files has been damaged.
>       -- The session is not connected to a relational database.
>       -- The current relational database manager does not support the
>          DESCRIBE  TABLE statement.
>       -- More information may be available in messages by pressing F10
>          (Display messages in job log) on this display.
>
>    Recovery  . . . :   If connected to the local relational database manager
>         and the field list is needed, press F18 (Select fields) again.
> Before
>         the field list is shown, a request to select a file or files from
> the file
>         list will be shown on the display. If not connected to the local
> relational
>         database manager, connect to a relational database manager that
> supports the
>         DESCRIBE TABLE statement and request a field list again.
>
> Does V4R3 supports DESCRIBE TABLE or not ?
>
>          I have tried with different options here and found the following:
>          If the File Object name is in quotes (" "), then its giving the
>          above error.
>
> For Ex. If the Object name is F.ILE1 (say), the SQL SELECT statement is
>
>    FROM files . . . . . . . . . .  LIB1/"F.ILE1"
>    SELECT fields  . . . . . . .  press <F4> here
>
> then its giving the above error.
>
> Now change the above object name to FILE1. Now the SQL SELECT statement is
>
>   FROM files . . . . . . . . . .  LIB1/FILE1
>   SELECT fields  . . . . . . .  press <F4> here
>
> its showing the fields.
>
> Please mail me the solutions as soon as possible.
>
> Regards,
> Murali Bhaavan.
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

--
Pete Massiello
OS Solutions International
Phone: (203)-744-7854  Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---