RE: TeraScript-Talk: First time doing Direct_DBMS

2019-07-26 Thread Robert Shubert
Wayne,



Please try out the 7.1.5 pre-release I just posted.



Preferably on a non-production system.



Robert



From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Thursday, July 25, 2019 4:03 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS



Ok, so in theory should this work?





What am I missing?



Wayne



On 26 Jul 2019, at 1:40 am, Robert Shubert mailto:rshub...@tronics.com> > wrote:



The alias t1 is set in the query by having it follow the table name, so yes, 
"FROM test t1" is creating the alias t1



@BOUNDVALS should work normally, in the query below there are none, so nothing 
should've been reported.



From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Wednesday, July 24, 2019 6:43 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS



<@SQL> just gives the same string as the DEBUG information.





It gives no information on how the t1 alias is set up (unless ‘FROM testtable 
t1’ is how it is done). Either way, this statement used in the Direct_DBMS 
action results in an error still.



<@BOUNDVALS> is pink in Terascribe and ignored by Terascript.



Wayne



On 24 Jul 2019, at 12:01 am, Robert Shubert mailto:rshub...@tronics.com> > wrote:



You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
immediately after the query.

-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS

Well no luck so far on the Direct_DBMS action.

Tried with a fresh new table and very simple SQL statement and got the same 
error.

I would really love a way to actually log the SQL statement generated and sent 
by the Search Action. The one in the Debug uses aliases and you can’t see the 
steps beforehand to test it out.

Wayne





On 12 Jul 2019, at 10:23 am, Wayne Irvine mailto:wa...@byteserve.com.au> > wrote:

This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.

What i would like to be able to log is the call the Search action makes to the 
JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify from 
there.

One thing that has got me thinking is the actions next to Direct_DBMS. 
Begin_Transaction and End_Transaction. Do these need to be before and after the 
Direct_DBMS action? I’ve never seen documentation for how these work.

Wayne





On 12 Jul 2019, at 9:12 am, ubslab mailto:ubs...@uw.edu> > 
wrote:

Wayne,

Am I correct assume this is all on a MacOS server?

If so, which version of OS and FileMaker are you using?

- Steve K

On 7/10/2019 7:18 PM, ubs...@uw.edu <mailto:ubs...@uw.edu>  wrote:




Wayne,

I recall needing to adjust datatype(s) in FM databases to work
correctly with Wtango and JDBC/ODBC.

Perhaps a test FM db with only integer columns.

- Steve K


On 7/10/19 7:06 PM, ubslab wrote:




Wayne,

Are you able to connect to FM table.columns in the Terascribe
editor JDBC/ODBC panel?

- Steve K

On 7/10/19 6:45 PM, Wayne Irvine wrote:




On 11 Jul 2019, at 12:38 am, Robert Shubert
mailto:rshub...@tronics.com> >
wrote:

Wayne,

First do a simple query like "SELECT 1" just to double check the DBMS.

I tried:
SELECT 1
SELECT 1 FROM Packages

both gave an error.




Then try grabbing just one row "SELECT packagename FROM Packages
WHERE packagename = '{known name}’"

SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’

Error




If that works, then we may be looking for a bug dealing with
non-value. Try "SELECT packagename FROM Packages WHERE
packagename IS NOT NULL”

SELECT packagename FROM Packages WHERE packagename IS NOT NULL

Error




What version of TS are you running? There was a JDBC fix in 7.1.1
and I have another fix (which may be your problem) coming in 7.1.5.

7.1.3.1

Wayne

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.




To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.





To unsubscribe from this list, please send an email to lists...@terascript.com 
<mailto:lists...@terascript.com>  with "unsubscribe terascript-talk" in the 
body.


Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <

Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-26 Thread Dale Graham
Our group routinely communicates with an FM server via DirectDBMS, so let me 
offer some dumb questions/advice

1] are you sure you using the right JDBC driver for the version of the server 
you are talking to
Is the JDBC driver located where TS can use it?

2] can you run a simple query in TS and get an answer

select * from Packages

Use  TS to limit the response to 1 row

If you get a response, ask for the zero row!

@@request$resultset[0,*]

The column names may have some surprises for you (they certainly did 
for us when we set this up)

If you cannot get a response from the select *, it has to be a driver/url 
problem

Your JDBC for filmmaker should look like this.

 
databasename

com.filemaker.jdbc.Driver

jdbc:filemaker://111.11.11.111/databasename 


databasename



3] If you CAN connect, be sure to reference all actual column names (as found 
in your select statement) within double quotes. We found that to be a failsafe 
for us.

Like this

SELECT p."last", p."first", p."middle", p."ned", p."current_ic", 
p."current_prof_design", p."current_Lab",p."Current_PD_Affective_Date"
FROM PersonnelFile p
where p."ned" = '<@ARG NEDID>'
order by p."last",p."first" asc




Dale Graham
dale.gra...@gmail.com



> On Jul 26, 2019, at 10:53 AM, Robert Shubert  wrote:
>
> Yes that should work. I suspect it's a bug in TS.
>
> From: Wayne Irvine [mailto:wa...@byteserve.com.au 
> <mailto:wa...@byteserve.com.au>]
> Sent: Thursday, July 25, 2019 4:03 PM
> To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
> Ok, so in theory should this work?
> 
>
> What am I missing?
>
> Wayne
>
>> On 26 Jul 2019, at 1:40 am, Robert Shubert > <mailto:rshub...@tronics.com>> wrote:
>>
>> The alias t1 is set in the query by having it follow the table name, so yes, 
>> "FROM test t1" is creating the alias t1
>>
>> @BOUNDVALS should work normally, in the query below there are none, so 
>> nothing should've been reported.
>>
>> From: Wayne Irvine [mailto:wa...@byteserve.com.au 
>> <mailto:wa...@byteserve.com.au>]
>> Sent: Wednesday, July 24, 2019 6:43 PM
>> To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
>> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>>
>> <@SQL> just gives the same string as the DEBUG information.
>> 
>>
>> It gives no information on how the t1 alias is set up (unless ‘FROM 
>> testtable t1’ is how it is done). Either way, this statement used in the 
>> Direct_DBMS action results in an error still.
>>
>> <@BOUNDVALS> is pink in Terascribe and ignored by Terascript.
>>
>> Wayne
>>
>>> On 24 Jul 2019, at 12:01 am, Robert Shubert >> <mailto:rshub...@tronics.com>> wrote:
>>>
>>> You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
>>> immediately after the query.
>>>
>>> -Original Message-
>>> From: Wayne Irvine [mailto:wa...@byteserve.com.au 
>>> <mailto:wa...@byteserve.com.au>]
>>> Sent: Monday, July 22, 2019 7:03 PM
>>> To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
>>> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>>>
>>> Well no luck so far on the Direct_DBMS action.
>>>
>>> Tried with a fresh new table and very simple SQL statement and got the same 
>>> error.
>>>
>>> I would really love a way to actually log the SQL statement generated and 
>>> sent by the Search Action. The one in the Debug uses aliases and you can’t 
>>> see the steps beforehand to test it out.
>>>
>>> Wayne
>>>
>>>
>>>
>>>> On 12 Jul 2019, at 10:23 am, Wayne Irvine >>> <mailto:wa...@byteserve.com.au>> wrote:
>>>>
>>>> This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.
>>>>
>>>> What i would like to be able to log is the call the Search action makes to 
>>>> the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and 
>>>> modify from there.
>>>>
>>>> One thing tha

RE: TeraScript-Talk: First time doing Direct_DBMS

2019-07-26 Thread Robert Shubert
Yes that should work. I suspect it's a bug in TS.



From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Thursday, July 25, 2019 4:03 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS



Ok, so in theory should this work?





What am I missing?



Wayne



On 26 Jul 2019, at 1:40 am, Robert Shubert mailto:rshub...@tronics.com> > wrote:



The alias t1 is set in the query by having it follow the table name, so yes, 
"FROM test t1" is creating the alias t1



@BOUNDVALS should work normally, in the query below there are none, so nothing 
should've been reported.



From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Wednesday, July 24, 2019 6:43 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS



<@SQL> just gives the same string as the DEBUG information.





It gives no information on how the t1 alias is set up (unless ‘FROM testtable 
t1’ is how it is done). Either way, this statement used in the Direct_DBMS 
action results in an error still.



<@BOUNDVALS> is pink in Terascribe and ignored by Terascript.



Wayne



On 24 Jul 2019, at 12:01 am, Robert Shubert mailto:rshub...@tronics.com> > wrote:



You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
immediately after the query.

-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS

Well no luck so far on the Direct_DBMS action.

Tried with a fresh new table and very simple SQL statement and got the same 
error.

I would really love a way to actually log the SQL statement generated and sent 
by the Search Action. The one in the Debug uses aliases and you can’t see the 
steps beforehand to test it out.

Wayne





On 12 Jul 2019, at 10:23 am, Wayne Irvine mailto:wa...@byteserve.com.au> > wrote:

This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.

What i would like to be able to log is the call the Search action makes to the 
JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify from 
there.

One thing that has got me thinking is the actions next to Direct_DBMS. 
Begin_Transaction and End_Transaction. Do these need to be before and after the 
Direct_DBMS action? I’ve never seen documentation for how these work.

Wayne





On 12 Jul 2019, at 9:12 am, ubslab mailto:ubs...@uw.edu> > 
wrote:

Wayne,

Am I correct assume this is all on a MacOS server?

If so, which version of OS and FileMaker are you using?

- Steve K

On 7/10/2019 7:18 PM, ubs...@uw.edu <mailto:ubs...@uw.edu>  wrote:




Wayne,

I recall needing to adjust datatype(s) in FM databases to work
correctly with Wtango and JDBC/ODBC.

Perhaps a test FM db with only integer columns.

- Steve K


On 7/10/19 7:06 PM, ubslab wrote:




Wayne,

Are you able to connect to FM table.columns in the Terascribe
editor JDBC/ODBC panel?

- Steve K

On 7/10/19 6:45 PM, Wayne Irvine wrote:




On 11 Jul 2019, at 12:38 am, Robert Shubert
mailto:rshub...@tronics.com> >
wrote:

Wayne,

First do a simple query like "SELECT 1" just to double check the DBMS.

I tried:
SELECT 1
SELECT 1 FROM Packages

both gave an error.




Then try grabbing just one row "SELECT packagename FROM Packages
WHERE packagename = '{known name}’"

SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’

Error




If that works, then we may be looking for a bug dealing with
non-value. Try "SELECT packagename FROM Packages WHERE
packagename IS NOT NULL”

SELECT packagename FROM Packages WHERE packagename IS NOT NULL

Error




What version of TS are you running? There was a JDBC fix in 7.1.1
and I have another fix (which may be your problem) coming in 7.1.5.

7.1.3.1

Wayne

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.




To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.





To unsubscribe from this list, please send an email to lists...@terascript.com 
<mailto:lists...@terascript.com>  with "unsubscribe terascript-talk" in the 
body.


Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 04

Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-25 Thread Wayne Irvine
Ok, so in theory should this work?


What am I missing?

Wayne

> On 26 Jul 2019, at 1:40 am, Robert Shubert  wrote:
>
> The alias t1 is set in the query by having it follow the table name, so yes, 
> "FROM test t1" is creating the alias t1
>
> @BOUNDVALS should work normally, in the query below there are none, so 
> nothing should've been reported.
>
> From: Wayne Irvine [mailto:wa...@byteserve.com.au]
> Sent: Wednesday, July 24, 2019 6:43 PM
> To: TeraScript-Talk@terascript.com
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
> <@SQL> just gives the same string as the DEBUG information.
> 
>
> It gives no information on how the t1 alias is set up (unless ‘FROM testtable 
> t1’ is how it is done). Either way, this statement used in the Direct_DBMS 
> action results in an error still.
>
> <@BOUNDVALS> is pink in Terascribe and ignored by Terascript.
>
> Wayne
>
>> On 24 Jul 2019, at 12:01 am, Robert Shubert > <mailto:rshub...@tronics.com>> wrote:
>>
>> You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
>> immediately after the query.
>>
>> -Original Message-
>> From: Wayne Irvine [mailto:wa...@byteserve.com.au 
>> <mailto:wa...@byteserve.com.au>]
>> Sent: Monday, July 22, 2019 7:03 PM
>> To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
>> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>>
>> Well no luck so far on the Direct_DBMS action.
>>
>> Tried with a fresh new table and very simple SQL statement and got the same 
>> error.
>>
>> I would really love a way to actually log the SQL statement generated and 
>> sent by the Search Action. The one in the Debug uses aliases and you can’t 
>> see the steps beforehand to test it out.
>>
>> Wayne
>>
>>
>>> On 12 Jul 2019, at 10:23 am, Wayne Irvine >> <mailto:wa...@byteserve.com.au>> wrote:
>>>
>>> This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.
>>>
>>> What i would like to be able to log is the call the Search action makes to 
>>> the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and 
>>> modify from there.
>>>
>>> One thing that has got me thinking is the actions next to Direct_DBMS. 
>>> Begin_Transaction and End_Transaction. Do these need to be before and after 
>>> the Direct_DBMS action? I’ve never seen documentation for how these work.
>>>
>>> Wayne
>>>
>>>
>>>> On 12 Jul 2019, at 9:12 am, ubslab mailto:ubs...@uw.edu>> 
>>>> wrote:
>>>>
>>>> Wayne,
>>>>
>>>> Am I correct assume this is all on a MacOS server?
>>>>
>>>> If so, which version of OS and FileMaker are you using?
>>>>
>>>> - Steve K
>>>>
>>>> On 7/10/2019 7:18 PM, ubs...@uw.edu <mailto:ubs...@uw.edu> wrote:
>>>>
>>>>> Wayne,
>>>>>
>>>>> I recall needing to adjust datatype(s) in FM databases to work
>>>>> correctly with Wtango and JDBC/ODBC.
>>>>>
>>>>> Perhaps a test FM db with only integer columns.
>>>>>
>>>>> - Steve K
>>>>>
>>>>>
>>>>> On 7/10/19 7:06 PM, ubslab wrote:
>>>>>
>>>>>> Wayne,
>>>>>>
>>>>>> Are you able to connect to FM table.columns in the Terascribe
>>>>>> editor JDBC/ODBC panel?
>>>>>>
>>>>>> - Steve K
>>>>>>
>>>>>> On 7/10/19 6:45 PM, Wayne Irvine wrote:
>>>>>>
>>>>>>>> On 11 Jul 2019, at 12:38 am, Robert Shubert
>>>>>>>> mailto:rshub...@tronics.com>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Wayne,
>>>>>>>>
>>>>>>>> First do a simple query like "SELECT 1" just to double check the DBMS.
>>>>>>> I tried:
>>>>>>> SELECT 1
>>>>>>> SELECT 1 FROM Packages
>>>>>>>
>>>>>>> both gave an error.
>>>>>>>
>>>>>>>> Then try grabbing just one row "SELECT packagename FROM Packages
>>>>>>>> WHERE packagename = '{known name}’"
>>>>>>> SELECT packagename

RE: TeraScript-Talk: First time doing Direct_DBMS

2019-07-25 Thread Robert Shubert
The alias t1 is set in the query by having it follow the table name, so yes, 
"FROM test t1" is creating the alias t1



@BOUNDVALS should work normally, in the query below there are none, so nothing 
should've been reported.



From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Wednesday, July 24, 2019 6:43 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS



<@SQL> just gives the same string as the DEBUG information.





It gives no information on how the t1 alias is set up (unless ‘FROM testtable 
t1’ is how it is done). Either way, this statement used in the Direct_DBMS 
action results in an error still.



<@BOUNDVALS> is pink in Terascribe and ignored by Terascript.



Wayne



On 24 Jul 2019, at 12:01 am, Robert Shubert mailto:rshub...@tronics.com> > wrote:



You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
immediately after the query.

-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS

Well no luck so far on the Direct_DBMS action.

Tried with a fresh new table and very simple SQL statement and got the same 
error.

I would really love a way to actually log the SQL statement generated and sent 
by the Search Action. The one in the Debug uses aliases and you can’t see the 
steps beforehand to test it out.

Wayne




On 12 Jul 2019, at 10:23 am, Wayne Irvine mailto:wa...@byteserve.com.au> > wrote:

This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.

What i would like to be able to log is the call the Search action makes to the 
JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify from 
there.

One thing that has got me thinking is the actions next to Direct_DBMS. 
Begin_Transaction and End_Transaction. Do these need to be before and after the 
Direct_DBMS action? I’ve never seen documentation for how these work.

Wayne




On 12 Jul 2019, at 9:12 am, ubslab mailto:ubs...@uw.edu> > 
wrote:

Wayne,

Am I correct assume this is all on a MacOS server?

If so, which version of OS and FileMaker are you using?

- Steve K

On 7/10/2019 7:18 PM, ubs...@uw.edu <mailto:ubs...@uw.edu>  wrote:



Wayne,

I recall needing to adjust datatype(s) in FM databases to work
correctly with Wtango and JDBC/ODBC.

Perhaps a test FM db with only integer columns.

- Steve K


On 7/10/19 7:06 PM, ubslab wrote:



Wayne,

Are you able to connect to FM table.columns in the Terascribe
editor JDBC/ODBC panel?

- Steve K

On 7/10/19 6:45 PM, Wayne Irvine wrote:



On 11 Jul 2019, at 12:38 am, Robert Shubert
mailto:rshub...@tronics.com> >
wrote:

Wayne,

First do a simple query like "SELECT 1" just to double check the DBMS.

I tried:
SELECT 1
SELECT 1 FROM Packages

both gave an error.



Then try grabbing just one row "SELECT packagename FROM Packages
WHERE packagename = '{known name}’"

SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’

Error



If that works, then we may be looking for a bug dealing with
non-value. Try "SELECT packagename FROM Packages WHERE
packagename IS NOT NULL”

SELECT packagename FROM Packages WHERE packagename IS NOT NULL

Error



What version of TS are you running? There was a JDBC fix in 7.1.1
and I have another fix (which may be your problem) coming in 7.1.5.

7.1.3.1

Wayne

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.




To unsubscribe from this list, please send an email to
lists...@terascript.com <mailto:lists...@terascript.com>  with "unsubscribe 
terascript-talk" in the body.





To unsubscribe from this list, please send an email to lists...@terascript.com 
<mailto:lists...@terascript.com>  with "unsubscribe terascript-talk" in the 
body.


Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
<mailto:lists...@terascript.com>  with "unsubscribe terascript-talk" in the 
body.


Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au <mailto:i...@byteserve.com.au>
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088





Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-24 Thread Wayne Irvine
<@SQL> just gives the same string as the DEBUG information.


It gives no information on how the t1 alias is set up (unless ‘FROM testtable 
t1’ is how it is done). Either way, this statement used in the Direct_DBMS 
action results in an error still.

<@BOUNDVALS> is pink in Terascribe and ignored by Terascript.

Wayne

> On 24 Jul 2019, at 12:01 am, Robert Shubert  wrote:
>
> You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
> immediately after the query.
>
> -Original Message-
> From: Wayne Irvine [mailto:wa...@byteserve.com.au]
> Sent: Monday, July 22, 2019 7:03 PM
> To: TeraScript-Talk@terascript.com
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
> Well no luck so far on the Direct_DBMS action.
>
> Tried with a fresh new table and very simple SQL statement and got the same 
> error.
>
> I would really love a way to actually log the SQL statement generated and 
> sent by the Search Action. The one in the Debug uses aliases and you can’t 
> see the steps beforehand to test it out.
>
> Wayne
>
>> On 12 Jul 2019, at 10:23 am, Wayne Irvine  wrote:
>>
>> This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.
>>
>> What i would like to be able to log is the call the Search action makes to 
>> the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify 
>> from there.
>>
>> One thing that has got me thinking is the actions next to Direct_DBMS. 
>> Begin_Transaction and End_Transaction. Do these need to be before and after 
>> the Direct_DBMS action? I’ve never seen documentation for how these work.
>>
>> Wayne
>>
>>> On 12 Jul 2019, at 9:12 am, ubslab  wrote:
>>>
>>> Wayne,
>>>
>>> Am I correct assume this is all on a MacOS server?
>>>
>>> If so, which version of OS and FileMaker are you using?
>>>
>>> - Steve K
>>>
>>> On 7/10/2019 7:18 PM, ubs...@uw.edu wrote:
>>>> Wayne,
>>>>
>>>> I recall needing to adjust datatype(s) in FM databases to work
>>>> correctly with Wtango and JDBC/ODBC.
>>>>
>>>> Perhaps a test FM db with only integer columns.
>>>>
>>>> - Steve K
>>>>
>>>>
>>>> On 7/10/19 7:06 PM, ubslab wrote:
>>>>> Wayne,
>>>>>
>>>>> Are you able to connect to FM table.columns in the Terascribe
>>>>> editor JDBC/ODBC panel?
>>>>>
>>>>> - Steve K
>>>>>
>>>>> On 7/10/19 6:45 PM, Wayne Irvine wrote:
>>>>>>> On 11 Jul 2019, at 12:38 am, Robert Shubert
>>>>>>> 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Wayne,
>>>>>>>
>>>>>>> First do a simple query like "SELECT 1" just to double check the DBMS.
>>>>>> I tried:
>>>>>> SELECT 1
>>>>>> SELECT 1 FROM Packages
>>>>>>
>>>>>> both gave an error.
>>>>>>> Then try grabbing just one row "SELECT packagename FROM Packages
>>>>>>> WHERE packagename = '{known name}’"
>>>>>> SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’
>>>>>>
>>>>>> Error
>>>>>>> If that works, then we may be looking for a bug dealing with
>>>>>>> non-value. Try "SELECT packagename FROM Packages WHERE
>>>>>>> packagename IS NOT NULL”
>>>>>> SELECT packagename FROM Packages WHERE packagename IS NOT NULL
>>>>>>
>>>>>> Error
>>>>>>> What version of TS are you running? There was a JDBC fix in 7.1.1
>>>>>>> and I have another fix (which may be your problem) coming in 7.1.5.
>>>>>> 7.1.3.1
>>>>>>
>>>>>> Wayne
>>>>>>
>>>>>> Byteserve Pty Ltd
>>>>>> w: http://www.byteserve.com.au/
>>>>>> e: i...@byteserve.com.au
>>>>>> p: +61 02 9960 6099
>>>>>> m: 0409 960 609
>>>>>> f: +61 02 9960 6088
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 
>>>>>>
>>>>>> To unsubscribe from this list, please send an email to
>>>>>> lists...@terascript.com with "unsubscribe

RE: TeraScript-Talk: First time doing Direct_DBMS

2019-07-23 Thread Robert Shubert
You can see generated SQL with @SQL and @BOUNDVALS, just output those tags 
immediately after the query.

-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS

Well no luck so far on the Direct_DBMS action.

Tried with a fresh new table and very simple SQL statement and got the same 
error.

I would really love a way to actually log the SQL statement generated and sent 
by the Search Action. The one in the Debug uses aliases and you can’t see the 
steps beforehand to test it out.

Wayne

> On 12 Jul 2019, at 10:23 am, Wayne Irvine  wrote:
>
> This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.
>
> What i would like to be able to log is the call the Search action makes to 
> the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify 
> from there.
>
> One thing that has got me thinking is the actions next to Direct_DBMS. 
> Begin_Transaction and End_Transaction. Do these need to be before and after 
> the Direct_DBMS action? I’ve never seen documentation for how these work.
>
> Wayne
>
>> On 12 Jul 2019, at 9:12 am, ubslab  wrote:
>>
>> Wayne,
>>
>> Am I correct assume this is all on a MacOS server?
>>
>> If so, which version of OS and FileMaker are you using?
>>
>> - Steve K
>>
>> On 7/10/2019 7:18 PM, ubs...@uw.edu wrote:
>>> Wayne,
>>>
>>> I recall needing to adjust datatype(s) in FM databases to work
>>> correctly with Wtango and JDBC/ODBC.
>>>
>>> Perhaps a test FM db with only integer columns.
>>>
>>> - Steve K
>>>
>>>
>>> On 7/10/19 7:06 PM, ubslab wrote:
>>>> Wayne,
>>>>
>>>> Are you able to connect to FM table.columns in the Terascribe
>>>> editor JDBC/ODBC panel?
>>>>
>>>> - Steve K
>>>>
>>>> On 7/10/19 6:45 PM, Wayne Irvine wrote:
>>>>>> On 11 Jul 2019, at 12:38 am, Robert Shubert
>>>>>> 
>>>>>> wrote:
>>>>>>
>>>>>> Wayne,
>>>>>>
>>>>>> First do a simple query like "SELECT 1" just to double check the DBMS.
>>>>> I tried:
>>>>> SELECT 1
>>>>> SELECT 1 FROM Packages
>>>>>
>>>>> both gave an error.
>>>>>> Then try grabbing just one row "SELECT packagename FROM Packages
>>>>>> WHERE packagename = '{known name}’"
>>>>> SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’
>>>>>
>>>>> Error
>>>>>> If that works, then we may be looking for a bug dealing with
>>>>>> non-value. Try "SELECT packagename FROM Packages WHERE
>>>>>> packagename IS NOT NULL”
>>>>> SELECT packagename FROM Packages WHERE packagename IS NOT NULL
>>>>>
>>>>> Error
>>>>>> What version of TS are you running? There was a JDBC fix in 7.1.1
>>>>>> and I have another fix (which may be your problem) coming in 7.1.5.
>>>>> 7.1.3.1
>>>>>
>>>>> Wayne
>>>>>
>>>>> Byteserve Pty Ltd
>>>>> w: http://www.byteserve.com.au/
>>>>> e: i...@byteserve.com.au
>>>>> p: +61 02 9960 6099
>>>>> m: 0409 960 609
>>>>> f: +61 02 9960 6088
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>> To unsubscribe from this list, please send an email to
>>>>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>>>>
>>>>
>>>> 
>>>>
>>>> To unsubscribe from this list, please send an email to
>>>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>>>
>>
>>
>> 
>>
>> To unsubscribe from this list, please send an email to 
>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>
>
> Byteserve Pty Ltd
> w: http://www.byteserve.com.au/
> e: i...@byteserve.com.au
> p: +61 02 9960 6099
> m: 0409 960 609
> f: +61 02 9960 6088
>
>
>
>
> 
>
> To unsubscribe from this list, please send an email to 
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-22 Thread Wayne Irvine
Well no luck so far on the Direct_DBMS action.

Tried with a fresh new table and very simple SQL statement and got the same 
error.

I would really love a way to actually log the SQL statement generated and sent 
by the Search Action. The one in the Debug uses aliases and you can’t see the 
steps beforehand to test it out.

Wayne

> On 12 Jul 2019, at 10:23 am, Wayne Irvine  wrote:
>
> This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12.
>
> What i would like to be able to log is the call the Search action makes to 
> the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify 
> from there.
>
> One thing that has got me thinking is the actions next to Direct_DBMS. 
> Begin_Transaction and End_Transaction. Do these need to be before and after 
> the Direct_DBMS action? I’ve never seen documentation for how these work.
>
> Wayne
>
>> On 12 Jul 2019, at 9:12 am, ubslab  wrote:
>>
>> Wayne,
>>
>> Am I correct assume this is all on a MacOS server?
>>
>> If so, which version of OS and FileMaker are you using?
>>
>> - Steve K
>>
>> On 7/10/2019 7:18 PM, ubs...@uw.edu wrote:
>>> Wayne,
>>>
>>> I recall needing to adjust datatype(s) in FM databases to work
>>> correctly with Wtango and JDBC/ODBC.
>>>
>>> Perhaps a test FM db with only integer columns.
>>>
>>> - Steve K
>>>
>>>
>>> On 7/10/19 7:06 PM, ubslab wrote:
 Wayne,

 Are you able to connect to FM table.columns in the Terascribe editor
 JDBC/ODBC panel?

 - Steve K

 On 7/10/19 6:45 PM, Wayne Irvine wrote:
>> On 11 Jul 2019, at 12:38 am, Robert Shubert 
>> wrote:
>>
>> Wayne,
>>
>> First do a simple query like "SELECT 1" just to double check the DBMS.
> I tried:
> SELECT 1
> SELECT 1 FROM Packages
>
> both gave an error.
>> Then try grabbing just one row "SELECT packagename FROM Packages
>> WHERE packagename = '{known name}’"
> SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’
>
> Error
>> If that works, then we may be looking for a bug dealing with
>> non-value. Try "SELECT packagename FROM Packages WHERE packagename
>> IS NOT NULL”
> SELECT packagename FROM Packages WHERE packagename IS NOT NULL
>
> Error
>> What version of TS are you running? There was a JDBC fix in 7.1.1
>> and I have another fix (which may be your problem) coming in 7.1.5.
> 7.1.3.1
>
> Wayne
>
> Byteserve Pty Ltd
> w: http://www.byteserve.com.au/
> e: i...@byteserve.com.au
> p: +61 02 9960 6099
> m: 0409 960 609
> f: +61 02 9960 6088
>
>
>
>
> 
>
> To unsubscribe from this list, please send an email to
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>

 

 To unsubscribe from this list, please send an email to
 lists...@terascript.com with "unsubscribe terascript-talk" in the body.

>>
>>
>> 
>>
>> To unsubscribe from this list, please send an email to 
>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>
>
> Byteserve Pty Ltd
> w: http://www.byteserve.com.au/
> e: i...@byteserve.com.au
> p: +61 02 9960 6099
> m: 0409 960 609
> f: +61 02 9960 6088
>
>
>
>
> 
>
> To unsubscribe from this list, please send an email to 
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread ubslab
Wayne,

I recall needing to adjust datatype(s) in FM databases to work correctly
with Wtango and JDBC/ODBC.

Perhaps a test FM db with only integer columns.

- Steve K


On 7/10/19 7:06 PM, ubslab wrote:
> Wayne,
>
> Are you able to connect to FM table.columns in the Terascribe editor
> JDBC/ODBC panel?
>
> - Steve K
>
> On 7/10/19 6:45 PM, Wayne Irvine wrote:
>>> On 11 Jul 2019, at 12:38 am, Robert Shubert  wrote:
>>>
>>> Wayne,
>>>
>>> First do a simple query like "SELECT 1" just to double check the DBMS.
>> I tried:
>> SELECT 1
>> SELECT 1 FROM Packages
>>
>> both gave an error.
>>> Then try grabbing just one row "SELECT packagename FROM Packages WHERE 
>>> packagename = '{known name}’"
>> SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’
>>
>> Error
>>> If that works, then we may be looking for a bug dealing with non-value. Try 
>>> "SELECT packagename FROM Packages WHERE packagename IS NOT NULL”
>> SELECT packagename FROM Packages WHERE packagename IS NOT NULL
>>
>> Error
>>> What version of TS are you running? There was a JDBC fix in 7.1.1 and I 
>>> have another fix (which may be your problem) coming in 7.1.5.
>> 7.1.3.1
>>
>> Wayne
>>
>> Byteserve Pty Ltd
>> w: http://www.byteserve.com.au/
>> e: i...@byteserve.com.au
>> p: +61 02 9960 6099
>> m: 0409 960 609
>> f: +61 02 9960 6088
>>
>>
>>
>>
>> 
>>
>> To unsubscribe from this list, please send an email to 
>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>
>
> 
>
> To unsubscribe from this list, please send an email to 
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>




To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread Wayne Irvine


> On 11 Jul 2019, at 12:38 am, Robert Shubert  wrote:
>
> Wayne,
>
> First do a simple query like "SELECT 1" just to double check the DBMS.

I tried:
SELECT 1
SELECT 1 FROM Packages

both gave an error.
>
> Then try grabbing just one row "SELECT packagename FROM Packages WHERE 
> packagename = '{known name}’"

SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’

Error
>
> If that works, then we may be looking for a bug dealing with non-value. Try 
> "SELECT packagename FROM Packages WHERE packagename IS NOT NULL”

SELECT packagename FROM Packages WHERE packagename IS NOT NULL

Error
>
> What version of TS are you running? There was a JDBC fix in 7.1.1 and I have 
> another fix (which may be your problem) coming in 7.1.5.


7.1.3.1

Wayne

Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread Wayne Irvine
I hadn’t noticed the user vars previously. They are left over from previous 
searches with the Search action. I added a Purge as the first action and they 
no longer appear.

I also changed the Select to retrieve a field that is not user generated, so 
more predictable and alphanumeric.

Still gives an error.

Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[Results Action][2] Results1
[Direct DBMS Action][2] Direct_DBMS : over60_db
[Datasource][286]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2636]  SELECT PackageUID FROM Packages
[Error] [4900]  -101 General error during data source operation.
[request$ Vars] [4900]  variableTimeout=30;













> On 10 Jul 2019, at 10:33 pm, ubslab  wrote:
>
> If the expected result set is in the range of "[Array:553x36]" I would
> suspect characters that the ODBC/JDBC connector can't pass or parse.
>
> Is it reasonable to refill the database with values not containing
> special, symbol, or punctuation characters to diagnose?
>
> Had a similar issue with a FM Witango configuration years ago; Can't
> recall specifics, but involved filtering/substitution to solve.
>
> - Steve K
>
> On 7/9/19 11:33 PM, Wayne Irvine wrote:
>>> On 10 Jul 2019, at 4:26 pm, ubslab  wrote:
>>>
>>> Wayne,
>>> So none the following forms will work in the action?
>>>
>>> SELECT packagename FROM Packages
>>>
>> Error
>>
>> An error occurred while processing your request:
>>
>> File: SQLfindpkgs.taf
>> Position: Direct_DBMS
>> Class: Internal
>> Main Error Number: -101
>>
>> General error during data source operation.
>>
>>
>>
>> [Application File]   [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
>> Server 7
>> [user$ Vars] [2] variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [Direct DBMS Action] [2] Direct_DBMS : over60_db
>> [Datasource] [288]   No existing connection to the data source found, 
>> creating a new connection. DSN: jdbc.over60_db; User: witango;
>> [Query]  [2580]  SELECT packagename FROM Packages
>> [Error]  [4965]  -101 General error during data source operation.
>> [user$ Vars] [4965]  variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [request$ Vars]  [4965]  variableTimeout=30;
>>
>>> SELECT P1.packagename FROM Packages P1
>>>
>> Error
>>
>> An error occurred while processing your request:
>>
>> File: SQLfindpkgs.taf
>> Position: Direct_DBMS
>> Class: Internal
>> Main Error Number: -101
>>
>> General error during data source operation.
>>
>>
>>
>> [Application File]   [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
>> Server 7
>> [user$ Vars] [2] variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [Direct DBMS Action] [2] Direct_DBMS : over60_db
>> [Datasource] [289]   No existing connection to the data source found, 
>> creating a new connection. DSN: jdbc.over60_db; User: witango;
>> [Query]  [2635]  SELECT P1.packagename FROM Packages P1
>> [Error]  [5055]  -101 General error during data source operation.
>> [user$ Vars] [5055]  variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [request$ Vars]  [5055]  variableTimeout=30;
>>
>>> SELECT P1.packagename FROM Packages AS P1
>>>
>> Error
>>
>> An error occurred while processing your request:
>>
>> File: SQLfindpkgs.taf
>> Position: Direct_DBMS
>> Class: Internal
>> Main Error Number: -101
>>
>> General error during data source operation.
>>
>>
>>
>> [Application File]   [1] START /sandbox/SQLfindpkgs.taf  TeraScript 
>> Server 7
>> [user$ Vars] [1] variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [Direct DBMS Action] [1] Direct_DBMS : over60_db
>> [Datasource] [304]   No existing connection to the data source found, 
>> creating a new connection. DSN: jdbc.over60_db; User: witango;
>> [Query]  [2608]  SELECT P1.packagename FROM Packages AS P1
>> [Error]  [5006]  -101 General error during data source operation.
>> [user$ Vars] [5007]  variableTimeout=30; foundset=[Array:553x36]; 
>> elcount=20; endpoint=20;
>> [request$ Vars]  [5007]  variableTimeout=30;
>>
>>
>>
>>
>>
>>
>> Byteserve Pty Ltd
>> w: http://www.byteserve.com.au/
>> e: i...@byteserve.com.au
>> p: +61 02 9960 6099
>> m: 0409 960 609
>> f: +61 02 9960 6088
>>
>>
>>
>>
>> 
>>
>> To unsubscribe from this list, please send an email to 
>> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>>
>
>
> 
>
> To unsubscribe from this list, please send an email to 
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>

Byteserve 

RE: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread Robert Shubert
Wayne,

First do a simple query like "SELECT 1" just to double check the DBMS.

Then try grabbing just one row "SELECT packagename FROM Packages WHERE 
packagename = '{known name}'"

If that works, then we may be looking for a bug dealing with non-value. Try 
"SELECT packagename FROM Packages WHERE packagename IS NOT NULL"

What version of TS are you running? There was a JDBC fix in 7.1.1 and I have 
another fix (which may be your problem) coming in 7.1.5.

Robert

-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Tuesday, July 09, 2019 11:34 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS


> On 10 Jul 2019, at 4:26 pm, ubslab  wrote:
>
> Wayne,
> So none the following forms will work in the action?
>
> SELECT packagename FROM Packages
>

Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][2] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][2] Direct_DBMS : over60_db
[Datasource][288]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2580]  SELECT packagename FROM Packages
[Error] [4965]  -101 General error during data source operation.
[user$ Vars][4965]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [4965]  variableTimeout=30;

>
> SELECT P1.packagename FROM Packages P1
>

Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][2] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][2] Direct_DBMS : over60_db
[Datasource][289]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2635]  SELECT P1.packagename FROM Packages P1
[Error] [5055]  -101 General error during data source operation.
[user$ Vars][5055]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [5055]  variableTimeout=30;

> SELECT P1.packagename FROM Packages AS P1
>
Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [1] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][1] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][1] Direct_DBMS : over60_db
[Datasource][304]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2608]  SELECT P1.packagename FROM Packages AS P1
[Error] [5006]  -101 General error during data source operation.
[user$ Vars][5007]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [5007]  variableTimeout=30;






Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread ubslab
If the expected result set is in the range of "[Array:553x36]" I would
suspect characters that the ODBC/JDBC connector can't pass or parse.

Is it reasonable to refill the database with values not containing
special, symbol, or punctuation characters to diagnose?

Had a similar issue with a FM Witango configuration years ago; Can't
recall specifics, but involved filtering/substitution to solve.

- Steve K

On 7/9/19 11:33 PM, Wayne Irvine wrote:
>> On 10 Jul 2019, at 4:26 pm, ubslab  wrote:
>>
>> Wayne,
>> So none the following forms will work in the action?
>>
>> SELECT packagename FROM Packages
>>
> Error
>
> An error occurred while processing your request:
>
> File: SQLfindpkgs.taf
> Position: Direct_DBMS
> Class: Internal
> Main Error Number: -101
>
> General error during data source operation.
>
>
>
> [Application File][2] START /sandbox/SQLfindpkgs.taf  TeraScript 
> Server 7
> [user$ Vars]  [2] variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [Direct DBMS Action]  [2] Direct_DBMS : over60_db
> [Datasource]  [288]   No existing connection to the data source found, 
> creating a new connection. DSN: jdbc.over60_db; User: witango;
> [Query]   [2580]  SELECT packagename FROM Packages
> [Error]   [4965]  -101 General error during data source operation.
> [user$ Vars]  [4965]  variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [request$ Vars]   [4965]  variableTimeout=30;
>
>> SELECT P1.packagename FROM Packages P1
>>
> Error
>
> An error occurred while processing your request:
>
> File: SQLfindpkgs.taf
> Position: Direct_DBMS
> Class: Internal
> Main Error Number: -101
>
> General error during data source operation.
>
>
>
> [Application File][2] START /sandbox/SQLfindpkgs.taf  TeraScript 
> Server 7
> [user$ Vars]  [2] variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [Direct DBMS Action]  [2] Direct_DBMS : over60_db
> [Datasource]  [289]   No existing connection to the data source found, 
> creating a new connection. DSN: jdbc.over60_db; User: witango;
> [Query]   [2635]  SELECT P1.packagename FROM Packages P1
> [Error]   [5055]  -101 General error during data source operation.
> [user$ Vars]  [5055]  variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [request$ Vars]   [5055]  variableTimeout=30;
>
>> SELECT P1.packagename FROM Packages AS P1
>>
> Error
>
> An error occurred while processing your request:
>
> File: SQLfindpkgs.taf
> Position: Direct_DBMS
> Class: Internal
> Main Error Number: -101
>
> General error during data source operation.
>
>
>
> [Application File][1] START /sandbox/SQLfindpkgs.taf  TeraScript 
> Server 7
> [user$ Vars]  [1] variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [Direct DBMS Action]  [1] Direct_DBMS : over60_db
> [Datasource]  [304]   No existing connection to the data source found, 
> creating a new connection. DSN: jdbc.over60_db; User: witango;
> [Query]   [2608]  SELECT P1.packagename FROM Packages AS P1
> [Error]   [5006]  -101 General error during data source operation.
> [user$ Vars]  [5007]  variableTimeout=30; foundset=[Array:553x36]; 
> elcount=20; endpoint=20;
> [request$ Vars]   [5007]  variableTimeout=30;
>
>
>
>
>
>
> Byteserve Pty Ltd
> w: http://www.byteserve.com.au/
> e: i...@byteserve.com.au
> p: +61 02 9960 6099
> m: 0409 960 609
> f: +61 02 9960 6088
>
>
>
>
> 
>
> To unsubscribe from this list, please send an email to 
> lists...@terascript.com with "unsubscribe terascript-talk" in the body.
>




To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.



Re: TeraScript-Talk: First time doing Direct_DBMS

2019-07-10 Thread Wayne Irvine


> On 10 Jul 2019, at 4:26 pm, ubslab  wrote:
>
> Wayne,
> So none the following forms will work in the action?
>
> SELECT packagename FROM Packages
>

Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][2] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][2] Direct_DBMS : over60_db
[Datasource][288]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2580]  SELECT packagename FROM Packages
[Error] [4965]  -101 General error during data source operation.
[user$ Vars][4965]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [4965]  variableTimeout=30;

>
> SELECT P1.packagename FROM Packages P1
>

Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [2] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][2] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][2] Direct_DBMS : over60_db
[Datasource][289]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2635]  SELECT P1.packagename FROM Packages P1
[Error] [5055]  -101 General error during data source operation.
[user$ Vars][5055]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [5055]  variableTimeout=30;

> SELECT P1.packagename FROM Packages AS P1
>
Error

An error occurred while processing your request:

File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101

General error during data source operation.



[Application File]  [1] START /sandbox/SQLfindpkgs.taf  TeraScript 
Server 7
[user$ Vars][1] variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[Direct DBMS Action][1] Direct_DBMS : over60_db
[Datasource][304]   No existing connection to the data source found, 
creating a new connection. DSN: jdbc.over60_db; User: witango;
[Query] [2608]  SELECT P1.packagename FROM Packages AS P1
[Error] [5006]  -101 General error during data source operation.
[user$ Vars][5007]  variableTimeout=30; foundset=[Array:553x36]; 
elcount=20; endpoint=20;
[request$ Vars] [5007]  variableTimeout=30;






Byteserve Pty Ltd
w: http://www.byteserve.com.au/
e: i...@byteserve.com.au
p: +61 02 9960 6099
m: 0409 960 609
f: +61 02 9960 6088






To unsubscribe from this list, please send an email to lists...@terascript.com 
with "unsubscribe terascript-talk" in the body.