PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!

Lance, Carson and Larry -

Based upon a previous thread I posted regarding ASA and ASE environments for
our website DB and the issues we were having, I took your advice and did the
following:

1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
6.0.2
2.  Established an Open Client connection profile to the web DB instead of
using ODBC.
3.  Created an Open Client connection from the website to the ASE 11.9.2
primary database.

Here's is what is happening now!:( - Please see the attachment!

Summary:

PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
the do.
We have PD web pages that execute SQL and Stored Procedures against the ASE
11.9.2 database.  When accessing the PD web DB via ODBC, the pages executed
correctly and the data was retrieved as expected.  Now that we've switched
over to Open Client, we are experiencing failures with all of our stored
procedures executed by our PD web pages that use stored procedures. (Please
refer to the attachment for specifics!)

Further,  any stored procedures that use a 'Select Into' or 'Create' command
do not function under either ODBC or Open Client when the PD web DB is in
ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection, they
worked!!

Any ideas, insight, guidance would be appreciated.  As I said, I took all
your advice and this is where we are at now.  I have to have this
application, website and supporting database's ready for beta testing in 3
DAYS!!  HELP!!!

TIA

Brad McLeod
StoneHenge Partners


begin 666 Open Client-ASE Problem.doc
MT,\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````!
M````-0``````````$ ``-P````$```#^____`````#0```#_____________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M_______________________LI<$`<0`)! ```!*_````````$ ``````! ``
MP!H```X`8FIB:G0K="L````````````````````````)!!8`)3(``!9!`0`6
M00$`P!8```````````````````````````````````````#__P\`````````
M``#__P\```````````#__P\``````````````````````%T``````)(`````
M````D@```)(`````````D@````````"2`````````)(`````````D@```!0`
M`````````````*8`````````I@````````"F`````````*8`````````I@``
M``P```"R````+ ```*8`````````#@\``+8```#R`````````/(`````````
M\@````````#R`````````/(`````````\@````````#R`````````/(`````
M````TPX```(```#5#@```````-4.````````U0X```````#5#@```````-4.
M````````U0X``"0```#$#P``] $``+@1``!8````^0X``!4`````````````
M````````````D@````````#R``````````````````````````````#R````
M`````/(`````````\@````````#R`````````/D.````````$@T```````"2
M`````````)(`````````\@```````````````````/(`````````\@``````
M```2#0```````!(-````````$@T```````#R`````@@``)(`````````\@``
M``````"2`````````/(`````````TPX`````````````````````````````
MI@````````"F`````````)(`````````D@````````"2`````````)(`````
M````\@````````#3#@```````!(-``!.`0``$@T```````!@#@``'@```+,.
M```8````D@````````"2````````````````````````````````````````
M````````````````````````````````````````````TPX```````#R````
M`````-X````4````H(,3:O"8OP&F`````````*8`````````] @``!X$``#+
M#@``" ``````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````#0T-,2X@(%1H92!F;VQL;W=I;F<@2F%V87-C<FEP="!C86QL<R!A
M('-T;W)E9"!P<F]C961U<F4@9G)O;2!I;G-I9&4@82!01"!(5$U,('!A9V4N
M("!2=6YN:6YG('5N9&5R($]P96X@0VQI96YT+T%312 Q,2XY+C(L('1H:7,@
M9F%I;',N("!2=6YN:6YG('5N9&5R($]$0D,O05-%(#$Q+CDN,B @:70@=V]R
M:W,N(" -#0DN+BX-"79A<B!->4-O;FYE8W1I;VX@/2!S:71E+D=E=$-O;FYE
M8W1I;VXH(DEN=&5L:6UA=')I>"(I.PT)=F%R('-344P@/2 B15A%0R!S<%]R
M<'104F]L;$5X8V5P=&EO;B B("L@0VQI96YT240@*R B+"(@*R!3=&]R94E$
M("L@(BPG(B K(%5S97))1" K("(G+"<B("L@4W1A<G1$871E("L@(B<L)R(@
M*R!%;F1$871E("L@(B<B#0EV87(@37E1=65R>2 ]("!->4-O;FYE8W1I;VXN
M0W)E871E475E<GDH*3L-"4UY475E<GDN4V5T4U%,*'-344PI.PT)37E1=65R
M>2Y%>&5C=71E*"D[#0DN+BX-5&AE(&5R<F]R('1H870@:7,@<F5T=7)N960@
M:7,Z#0V14W1O<F5D('!R;V-E9'5R92"1<W!?<G!T4%)O;&Q%>&-E<'1I;VZ2
M(&UA>2!B92!R=6X@;VYL>2!I;B!U;F-H86EN960@=')A;G-A8W1I;VX@;6]D
M92X@(%1H92"14T54($-(04E.140@3T9&DB!C;VUM86YD('=I;&P@8V%U<V4@
M=&AE(&-U<G)E;G0@<V5S<VEO;B!T;R!U<V4@=6YC:&%I;F5D('1R86YS86-T
M:6]N(&UO9&62+@T-5&AI<R!I<R!T:&4@86-T=6%L('-T;W)E9"!P<F]C961U
M<F4@=&AA="P@87,@;65N=&EO;F5D+"!W;W)K<R!U;F1E<B!/1$)#+T%312 Q
M,2XY+C(@8G5T(&9A:6QS('5N9&5R($]P96X@0VQI96YT+T%312 Q,2XY+@T-
M0U)%051%(%!23T-%1%5212!S<%]R<'104F]L;$5X8V5P="A 05)?0TQ)14Y4
M7TE$($E.5"Q 05)?4U1/4D5?240@24Y4+$!54T52240@5D%20TA!4B@R,"DL
M0%-T87)T1&%T92!D871E=&EM92Q 16YD1&%T92!D871E=&EM92D@(" @(" @
M(" @( U!4R @(" @(" @(" @#4)%1TE.(" @(" @(" @(" -(" @($1%3$54
M12!&4D]-('1B;%]R<'1087ER;VQL17AC97!T:6]N<R!72$5212!54T527TE$
M/4!54T52240@(" @(" @(" @( T@(&EN<V5R="!I;G1O("!T8FQ?<G!T4&%Y
M<F]L;$5X8V5P=&EO;G,@*" @(" -(" @(" @(" @(" @16UP7TYO+" @(" -
M(" @(" @(" @(" @<W1R4$]32D]"3F\L(" @(" -(" @(" @(" @(" @<&%Y
M+" @(" -(" @(" @(" @(" @1&%Y7T-O=6YT+" @(" @(" -(" @(" @(" @
M(" @3F5W26Y$871E+" @#2 @(" @(" @(" @(&YE=VEN=&EM92P@( T@(" @
M(" @(" @("!.97=/=71$871E+" @(" -(" @(" @(" @(" @;F5W;W5T=&EM
M92P@( T@(" @(" @(" @("!4;W1?5&EM92P@( T@(" @(" @(" @("!A9&I?
M:6XL(" @( T@(" @(" @(" @("!A9&I?;W5T+" @#2 @(" @(" @(" @(')A
M=&4L(" -(" @(" @(" @(" @8W5R<VAI9G1T:7 L(" @( T@(" @(" @(" @
M("!E;7!N86UE+" @#2 @(" @(" @(" @('-S;BP@( T@(" @(" @(" @("!F
M;W)C96)R96%K+" @(" -(" @(" @(" @(" @<F5G=6QA<FAO=7)S+" @(" @
M(" @( T@(" @(" @(" @("!O=F5R=&EM96AO=7)S+" @(" @(" @(" @(" @
M(" @#2 @(" @(" @(" @(&-U<G-H:69T<V%L97,L(" @( T@(" @(" @(" @
M("!J;V)?9&5S8RP@(" @(" @(" @(" @(" -(" @(" @(" @(" @8VAA<F=E
M9'1I<',L(" @(" @(" @(" @(" @( T@(" @(" @(" @("!A:6Y?:60L(" @
M( T@(" @(" @(" @("!A;W5T7VED+" @(" @(" @(" @(" @(" @( T@(" @
M(" @(" @("!A:6Y?;FYA;64L(" @(" @(" @(" @(" @(" @(" @( T@(" @
M(" @(" @("!A;W5T7VYN86UE+" @(" -(" @(" @(" @(" @=7-E<E]I9"P@
M(" @(" @(" @(" @(" @(" -(" @(" @(" @(" @8W5R8VAA<F=E<V%L97,I
M(" @( T@('-E;&5C=" @("!S=')03U-%;7!.;RP@( T@(" @(" @(" @("!S
M=')03U-*3T).;RP@(" @(" @(" -(" @(" @(" @(" @*&1B;%)E9W5L87)0
M87D@*R!D8FQ/=F5R5&EM95!A>2DL(" @(" @(" @#2 @(" @(" @(" @(# P
M,"P@(" @(" @(" -(" @(" @(" @(" @8V]N=F5R="AD871E=&EM92QC;VYV
M97)T*&-H87(H,3 I+"A#87-E(%=H96X@>6Y!9&IU<W1E9$EN(#T@)UDG(%1H
M96X@9&%T94%D:G5S=&5D26X@16QS92!D871E26X@16YD*2PQ,#$I("L@)R G
M("L@*$-A<V4@5VAE;B!Y;D%D:G5S=&5D26X@/2 G62<@5&AE;B!T:6UE061J
M=7-T961);B!%;'-E('1I;65);B!%;F0I+#$P,2DL(" -(" @(" @(" @(" @
M*$-A<V4@5VAE;B!Y;D%D:G5S=&5D26X@/2 G62<@5&AE;B!T:6UE061J=7-T
M961);B!%;'-E('1I;65);B!%;F0I+" @(" @(" @( T@(" @(" @(" @("!C
M;VYV97)T*&1A=&5T:6UE+&-O;G9E<G0H8VAA<B@Q,"DL*$-A<V4@5VAE;B!Y
M;D%D:G5S=&5D3W5T(#T@)UDG(%1H96X@9&%T94%D:G5S=&5D3W5T($5L<V4@
M9&%T94]U="!%;F0I+#$P,2D@*R G("<@*R H0V%S92!7:&5N('EN061J=7-T
M961/=70@/2 G62<@5&AE;B!T:6UE061J=7-T961/=70@16QS92!T:6UE3W5T
M($5N9"DL,3 Q*2P@(" @(" @( T@(" @(" @(" @(" H0V%S92!7:&5N('EN
M061J=7-T961/=70@/2 G62<@5&AE;B!T:6UE061J=7-T961/=70@16QS92!T
M:6UE3W5T($5N9"DL(" @(" @(" @#2 @(" @(" @(" @(# P,# N,# L(" @
M(" @(" -(" @(" @(" @(" @>6Y!9&IU<W1E9$EN+" @(" @(" @( T@(" @
M(" @(" @("!Y;D%D:G5S=&5D3W5T+" @(" @(" @( T@(" @(" @(" @("!D
M8FQ2871E+" @(" @(" @( T@(" @(" @(" @("!C=7)3:&EF=%1I<"P@(" @
M(" @(" -(" @(" @(" @(" @4G1R:6TH<W1R3&%S=$YA;64I("L@)RP@)R K
M(%)T<FEM*'-T<D9I<G-T3F%M92DL(" @(" @(" @#2 @(" @(" @(" @('-T
M<E-33BP@(" @(" @(" -(" @(" @(" @(" @>6Y&;W)C94)R96%K+" @(" @
M(" @( T@(" @(" @(" @("!D8FQ296=U;&%R2&]U<G,L(" @(" @(" @#2 @
M(" @(" @(" @(&1B;$]V97)4:6UE2&]U<G,L(" @(" @(" @#2 @(" @(" @
M(" @(&-U<E-H:69T4V%L97,L(" @(" @(" @#2 @(" @(" @(" @('-P86-E
M*#,P*2P@(" @(" @(" -(" @(" @(" @(" @9&)L0VAA<F=E9%1I<',L(" @
M(" @(" @#2 @(" @(" @(" @('-T<D%D:G5S=&5R26Y)1"P@(" @(" @(" -
M(" @(" @(" @(" @<W1R061J=7-T97)/=71)1"P@(" @(" @(" -(" @(" @
M(" @(" @<W!A8V4H,S I+" @(" @(" @( T@(" @(" @(" @("!S<&%C92@S
M,"DL(" @(" @(" @#2 @(" @(" @(" @($!5<V5R240L(" @(" @(" @#2 @
M(" @(" @(" @(&1B;$-H87)G95-A;&5S(" @(" @(" @#2 @("!&<F]M(" @
M('1B;%]#;&]C:TAI<W1O<GD@(" @(" @(" -(" @(%=H97)E(" @*&1A=&5I
M;B!B971W965N($!3=&%R=$1A=&4@86YD($!%;F1$871E(&]R(&1A=&5!9&IU
M<W1E9$EN(&)E='=E96X@0%-T87)T1&%T92!A;F0@0$5N9$1A=&4I(&%N9"!D
M871E0G5S:6YE<W-$87D@:7,@;F]T(&YU;&P@(" @(" @(" -(" @(" @("!A
M;F0@87)?0VQI96YT7VED(#T@0$%R7T-L:65N=%])1" @(" @(" @( T@(" @
M(" @(&%N9"!A<E]3=&]R96ED(#T@0&%R7U-T;W)E7VED(" @(" @(" -(" @
M( T@(" @(" @(" @#2 @("!5<&1A=&4@('1B;%]R<'1087ER;VQL17AC97!T
M:6]N<R @#2 @("!3970@(" @(%1O=%]4:6UE(#T@4F]U;F0H9&%T961I9F8H
M36EN=71E+"!.97=);D1A=&4L3F5W3W5T1&%T92D@+R V,"XP+" R*2 @(" @
M(" @#2 @("!7:&5R92 @(%5S97)?240@/2! 57-E<DE$(" -(" @(" @(" @
M(" @(" -(" @(%5P9&%T92 @=&)L7W)P=%!A>7)O;&Q%>&-E<'1I;VYS(" @
M(" @(" @(" -(" @(%-E=" @(" @2F]B7T1E<V,@/2!*;V(N2F]B7T1E<V,@
M(" @(" @(" @#2 @("!&<F]M(" @('1B;%]R<'1087ER;VQL17AC97!T:6]N
M<RP@2F]B(" @(" @(" @( T@(" @5VAE<F4@("!S=')03U-*3T).;R ]($IO
M8BY*;V)?3F\@(" @(" @(" @( T@(" @(" @(&%N9"!*;V(N0VQI96YT7TE$
M(#T@0&%R7T-L:65N=%])1" @(" @(" @(" @#2 @(" @(" @86YD($IO8BY3
M=&]R95])1" ]($!A<E]3=&]R95])1" @(" @(" @(" -(" @(" @("!A;F0@
M=&)L7W)P=%!A>7)O;&Q%>&-E<'1I;VYS+E5S97)?240@/2! 57-E<DE$(" -
M(" @(" @(" @( T@(" @57!D871E("!T8FQ?<G!T4&%Y<F]L;$5X8V5P=&EO
M;G,@( T@(" @4V5T(" @("!!:6Y?;DYA;64@/2!T8FQ?16UP;&]Y964N<W1R
M3FEC:TYA;64@(" @(" @(" @#2 @("!&<F]M(" @('1B;%]R<'1087ER;VQL
M17AC97!T:6]N<RP@=&)L7T5M<&QO>65E(" @(" @(" @( T@(" @5VAE<F4@
M("!T8FQ?<G!T4&%Y<F]L;$5X8V5P=&EO;G,N06EN7TE$(#T@=&)L7T5M<&QO
M>65E+FEN=%!/4U)E8V]R9$YU;6)E<B @(" @(" @(" -(" @(" @("!A;F0@
M=&)L7T5M<&QO>65E+F%R7T-L:65N=%])1" ]($!A<E]#;&EE;G1?240@(" -
M(" @(" @("!A;F0@=&)L7T5M<&QO>65E+F%R7U-T;W)E240@/2! 87)?4W1O
M<F5?240@(" @(" @(" @#2 @(" @(" @86YD('1B;%]R<'1087ER;VQL17AC
M97!T:6]N<RY5<V5R7TE$(#T@0%5S97))1" @#2 @#2 @("!5<&1A=&4@('1B
M;%]R<'1087ER;VQL17AC97!T:6]N<R @#2 @("!3970@(" @($%I;E]N3F%M
M92 ]("AC87-E('=H96X@061J7TEN(&ES(&YU;&P@5&AE;B G)R!%;'-E("AC
M87-E('=H96X@06EN7TE$(#T@)TE3041*)R!O<B!!:6Y?240@/2 G0TU/550G
M('1H96X@)TEN=&5L:6UA=')I>"<@16YD*2!%;F0I(" @(" @(" @( T@(" @
M5VAE<F4@("!5<V5R7TE$(#T@0%5S97))1" @#2 @(" @( T@(" @57!D871E
M("!T8FQ?<G!T4&%Y<F]L;$5X8V5P=&EO;G,@( T@(" @4V5T(" @("!!;W5T
M7VY.86UE(#T@=&)L7T5M<&QO>65E+G-T<DYI8VM.86UE(" @(" @(" @( T@
M(" @1G)O;2 @("!T8FQ?<G!T4&%Y<F]L;$5X8V5P=&EO;G,L('1B;%]%;7!L
M;WEE92 @(" @(" @(" -(" @(%=H97)E(" @=&)L7W)P=%!A>7)O;&Q%>&-E
M<'1I;VYS+D%O=71?240@/2!T8FQ?16UP;&]Y964N:6YT4$]34F5C;W)D3G5M
M8F5R(" @(" @(" @( T@(" @(" @(&%N9"!T8FQ?16UP;&]Y964N87)?0VQI
M96YT7TE$(#T@0&%R7T-L:65N=%])1" @( T@(" @(" @(&%N9"!T8FQ?16UP
M;&]Y964N87)?4W1O<F5)1" ]($!A<E]3=&]R95])1" @(" @(" @(" -(" @
M(" @("!A;F0@=&)L7W)P=%!A>7)O;&Q%>&-E<'1I;VYS+E5S97)?240@/2! 
M57-E<DE$(" -(" -(" @(%5P9&%T92!T8FQ?<G!T4&%Y<F]L;$5X8V5P=&EO
M;G,@( T@(" @4V5T($%O=71?;DYA;64@/2 H8V%S92!W:&5N($%D:E]);B!I
M<R!N=6QL(%1H96X@)R<@16QS92 H8V%S92!W:&5N($%O=71?240@/2 G25-!
M1$HG(&]R($%O=71?240@/2 G0TU/550G('1H96X@)TEN=&5L:6UA=')I>"<@
M16YD*2!%;F0I(" @(" @(" @( T@(" @5VAE<F4@("!5<V5R7VED(#T@0%5S
M97))1" @#2 @#2 @("!$96QE=&4@9G)O;2!T8FQ?<G!T4&%Y<F]L;$5X8V5P
M=&EO;G,@( T@(" @5VAE<F4@;F]T("@H(%1/5%]424U%/CTQ,B!/4B!43U1?
M5$E-13P]+C R($]2($%$2E])3CTG62<@3U(@041*7T]55#TG62<@3U(@0U52
M4TA)1E1304Q%4R J("XP." ^($-54E-(24945$E0("D@04Y$(%!!62 ^(# N
M,"D@( T@(" @(" @(" @86YD(%5S97)?:60@/2! 57-E<DE$(" -(" -14Y$
M(" @(" @#0T-#0U5;F1E<B!/1$)#+T%312 Q,2XY+C(@86YY('-T;W)E9"!P
M<F]C961U<F5S(&AA=FEN9R!314Q%0U0@24Y43R!O<B!#<F5A=&4@8V]M;6%N
M9',@9F%I;"X@(%1H97D@=V]R:V5D('5N9&5R($]$0D,O05-!(#8N,"XR(%!O
M=V5R1'EN86UO(&-O;F9I9W5R871I;VXN#0``````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``````````````````````````````````````````````````0```0$``"Q
M! ``[P4``*8&```D!P``*!H``"D:``# &@``]N[VX_;N`/8`````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M`````````````````````````````````````````````````````!4U"(%"
M*@9/2@(`44H"`&@(`&Y("00/3TH"`%%*`@!H" !N2 D$$C4(@4]*`@!12@(`
M: @`;D@)! @`! ```00```($```#! ``M 0``+4$``"Z! ``\@0``'(%``">
M!0``M04``,D%``#.!0``[04``.X%``"H!@``J08``",'```D!P``L <``+X'
M``#/!P``&0@``$<(``!?" ``?0@``)((``"P" ``R0@``.((``#]````````
M````````_0```````````````/T```````````````#]````````````````
M_0```````````````/T```````````````#]````````````````_0``````
M`````````/T```````````````#]````````````````_0``````````````
M`/T```````````````#]````````````````_0```````````````/T`````
M``````````#]````````````````_0```````````````/T`````````````
M``#]````````````````_0```````````````/T```````````````#]````
M````````````_0```````````````/T```````````````#]````````````
M````_0```````````````/T```````````````#]````````````````_0``
M```````````````````````````!````'0`$```!! ```@0```,$``"T! ``
MM00``+H$``#R! ``<@4``)X%``"U!0``R04``,X%``#M!0``[@4``*@&``"I
M!@``(P<``"0'``"P!P``O@<``,\'```9" ``1P@``%\(``!]" ``D@@``+ (
M``#)" ``X@@``/X(```8"0``, D``$@)``!?"0``<PD``) )``"G"0``N@D`
M`-8)``#Y"0``)0H``$0*``!I"@``D@H``*H*``#1"@``_@H``!H+``!!"P``
M80L``'P+``">"P``U0L``.\+``"X# ``$0T``.8-``!"#@``7PX``((.``"F
M#@``Q X``.8.```L#P``20\``&P/``"2#P``N0\``-T/``#]#P``(A ``$@0
M``!O$ ``CQ ``*\0``#-$ ``\1 ``!<1``"G$0``V1$```<2```,$@``%Q(`
M`#X2``"5$@``M1(``,02``#T$@``(A,``%83``"&$P``NQ,``.T3```F% ``
M,10``%@4``"3% ``T!0``"@5``!A%0``````````````````````````````
M````````````````````````````````````````````````````````````
M``````````````````````````````````````#^_OX````````"#0%DX@@`
M`/X(```8"0``, D``$@)``!?"0``<PD``) )``"G"0``N@D``-8)``#Y"0``
M)0H``$0*``!I"@``D@H``*H*``#1"@``_@H``!H+``!!"P``80L``'P+``">
M"P``U0L``.\+``"X# ``$0T``.8-``!"#@``_0```````````````/T`````
M``````````#]````````````````_0```````````````/T`````````````
M``#]````````````````_0```````````````/T```````````````#]````
M````````````_0```````````````/T```````````````#]````````````
M````_0```````````````/T```````````````#]````````````````_0``
M`````````````/T```````````````#]````````````````_0``````````
M`````/T```````````````#]````````````````_0```````````````/T`
M``````````````#]````````````````_0```````````````/T`````````
M``````#]````````````````_0```````````````/T`````````````````
M`````````````0```!U"#@``7PX``((.``"F#@``Q X``.8.```L#P``20\`
M`&P/``"2#P``N0\``-T/``#]#P``(A ``$@0``!O$ ``CQ ``*\0``#-$ ``
M\1 ``!<1``"G$0``V1$```<2```,$@``%Q(``#X2``"5$@``M1(``,02``#]
M````````````````_0```````````````/T```````````````#]````````
M````````_0```````````````/T```````````````#]````````````````
M_0```````````````/T```````````````#]````````````````_0``````
M`````````/T```````````````#]````````````````_0``````````````
M`/T```````````````#]````````````````_0```````````````/T`````
M``````````#]````````````````_0```````````````/T`````````````
M``#]````````````````_0```````````````/T```````````````#]````
M````````````_0```````````````/T```````````````#]````````````
M````_0`````````````````````````````!````'<02``#T$@``(A,``%83
M``"&$P``NQ,``.T3```F% ``,10``%@4``"3% ``T!0``"@5``!A%0``GA4`
M`-<5``#:%0```18``)@6``"X%@``OQ8``.86```B%P``7Q<``+@7``#Q%P``
M+A@``&<8``!J& ``D!@``/T```````````````#]````````````````_0``
M`````````````/T```````````````#]````````````````_0``````````
M`````/T```````````````#]````````````````_0```````````````/T`
M``````````````#]````````````````_0```````````````/T`````````
M``````#]````````````````_0```````````````/T```````````````#]
M````````````````_0```````````````/T```````````````#]````````
M````````_0```````````````/T```````````````#]````````````````
M_0```````````````/T```````````````#]````````````````_0``````
M`````````/T```````````````#]``````````````````````````````$`
M```=814``)X5``#7%0``VA4```$6``"8%@``N!8``+\6``#F%@``(A<``%\7
M``"X%P``\1<``"X8``!G& ``:A@``) 8```F&0``1AD``$D9``!T&0``^!D`
M`!H:```=&@``)QH``"@:```I&@``*AH``"L:``# &@``````````````````
M`````````````````````/P`````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````!0@!``D!`!V0& ``)AD``$89``!)&0``=!D``/@9```:
M&@``'1H``"<:```H&@``*1H``"H:```K&@``P!H``/T```````````````#]
M````````````````_0```````````````/T```````````````#]````````
M````````_0```````````````/T```````````````#]````````````````
M_0```````````````/T```````````````#]````````````````_0``````
M`````````/@`````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````!0``"B8`"T8!```!````#2,`$C `'% !
M`!^PT"\@L. ](; (!R*P" <CD* %))"@!26P````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````$@`/``H``0!;``\``@`````````D``! \?\"`"0````&`$X`
M;P!R`&T`80!L`````@````0`;4@)! ```````````````````````#P`04#R
M_Z$`/ ```!8`1 !E`&8`80!U`&P`= `@`% `80!R`&$`9P!R`&$`< !H`" `
M1@!O`&X`= ``````````````````````P!8```@``#(```<`_____P`$``# 
M&@``$0`````$``#B" ``0@X``,02``"0& ``P!H``!(````4````%0```!8`
M```8``````0``&$5``# &@``$P```!<`````````%0```!\```"[````O@``
M`+\```#+````S@```. ```#B````[@```/,```#V````]P```/L````$`0``
M& $``!T!```E`0``+@$``#4!```_`0``10$``% !``!9`0``9 $``&L!``!S
M`0``=@$``'<!``!^`0``@@$``)H!``"?`0``K0$``*X!``"R`0``M@$``,4!
M```!`@``%0(``#4#``!&`P``?P,``(@#``")`P``F@,``)L#``"C`P``WP,`
M`/<#```H! ``0 0``%,$``!9! ``:P0``'8$``">! ``IP0``+P$``#%! ``
MU00``-X$``#N! ``^ 0```H%```4!0``) 4``"P%```\!0``0@4``%0%``!;
M!0``?P4``(H%``"<!0``HP4``+,%``"V!0``Q@4``- %``#B!0``[@4```4&
M```2!@``,08``#X&``!0!@``6 8``'4&``" !@``G@8``*0&``"V!@``O08`
M`-T&``#F!@``"@<``!0'```F!P``+0<``$T'``!;!P``;0<``'@'``"(!P``
MDP<``*L'``"X!P``NP<``,D'```#" ``$P@``"@(```T" ``0 @``$X(``!4
M" ``6@@``&D(``!J" ``> @``(0(``"0" ``G@@``*0(``"J" ``SP@``-L(
M``#G" ``]0@``/L(```!"0``)0D``#4)``!*"0``5PD``&,)``!R"0``> D`
M`'\)``"."0``CPD``)T)``"J"0``M@D``,4)``#+"0``T@D``/T)```*"@``
M%@H``"4*```K"@``,@H``&L*``!W"@``C@H``)L*``"R"@``N0H``- *``#;
M"@``\@H``/<*``#X"@```PL```X+```3"P``% L``" +```X"P``/@L``%4+
M``!A"P``> L``(<+``">"P``K@L``,4+``#2"P``"0P``!<,```N# ``/0P`
M`%0,``!D# ``O P``,(,``#9# ``YPP``/T,```-#0``) T``"H-```T#0``
M/0T``$,-``!*#0``3@T``%P-``!F#0``;PT``'4-``!\#0``@@T``)$-``"S
M#0``OPT``,,-``#/#0``Y0T``.\-``#S#0``_@T``",.```[#@``2@X``%(.
M``!;#@``8PX``&P.``" #@``H0X``*@.``"L#@``L@X``- .``#H#@````\`
M``@/```+#P``%P\``"X/``!&#P``8@\``&T/``!P#P``>@\``)(/``"?#P``
MHP\``*\/``#'#P``TP\``-</``#B#P``^0\``!D0```=$ ``(Q ``#T0``!5
M$ ``9! ``&T0``!P$ ``B! ``)\0``"W$ ``N1 ``,40``#<$ ``^Q ``/X0
M```=$0``-!$``$T1``!1$0``71$``&T1``"$$0``B!$``),1``"J$0``RA$`
M`,X1``#4$0``YA$``/X1```-$@``%A(``"02```J$@``2Q(``%$2``!?$@``
M91(``'82``""$@``I!(``*L2``"O$@``M1(``,L2``#C$@``\A(``/P2``#_
M$@``%Q,``"X3``!&$P``2!,``%03``!K$P``BQ,``(X3``"M$P``Q!,``-T3
M``#A$P``[1,``/T3```4% ``&!0``",4```Z% ``6A0``%X4``!D% ``=10`
M`(T4``"8% ``HA0``+ 4``"V% ``UQ0``-X4``#L% ``\Q0```05```0%0``
M,A4``#D5```]%0``0Q4``%D5``!Q%0``!A8```T6```1%@``%Q8``,(6```'
M`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`
M' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<
M``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`
M!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'
M`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`
M' `'`!P`!P`<``<`&P`'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<
M``<`' `'`!P`!P`;``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`
M!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'
M`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`
M' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<
M``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`
M!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'
M`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`
M' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<
M``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`!P`<``<`' `'`!P`
M!P`<``<``````* ```"J````NP```+X```#S````]@```',!``!V`0``GP$`
M`*X!``"V`0``Q@$``-T!``#H`0``%P(``"$"```X`P``1P,``!L$```A! ``
M:P0``'8$``")! ``C 0``-4$``#>! ``"@4``!0%```\!0``/P4``%0%``!7
M!0``:P4``&\%``!_!0``B@4``)P%``"C!0``LP4``+8%``#&!0``T 4``.(%
M``#N!0``!08``!(&```Q!@``/@8``% &``!3!@``=08``( &``">!@``H08`
M`+8&``"Z!@``W08``. &```*!P``#@<``"8'```J!P``30<``%L'``!C!P``
M:0<``(@'``"3!P``JP<``+@'``#[!P```@@``!T)```D"0``:PH``'<*``".
M"@``FPH``+(*``"Y"@``T H``-L*``#R"@``^ H``#@+```^"P``50L``&$+
M``!X"P``APL``)X+``"N"P``Q0L``-(+``#I"P``[@L```D,```7# ``+@P`
M`#T,``!4# ``9 P``'L,``" # ``FPP``* ,``#9# ``YPP``/4,````#0``
MKPT``+(-``#A#0``Y T``!L.```F#@``0@X``$T.``"9#@``I0X``,@.``#3
M#@``^ X```,/```F#P``,0\``%H/``!M#P``C@\``)$/``###P``Q@\``/4/
M``#X#P``-1 ``$ 0``!<$ ``9Q ``)<0``"B$ ``U! ``-\0```P$0``,Q$`
M`&D1``!L$0``IA$``*D1``#>$0``Z1$```42```0$@``G!(``*@2``##$@``
MSA(``.H2``#V$@``)A,``#$3``!C$P``;A,``, 3``##$P``^1,``/P3```V
M% ``.10``"H5```V%0``@Q4``(@5```"%@``!18``,(6```'`!H`!P`:``<`
M&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:
M``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`
M!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'
M`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`
M&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:
M``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`
M!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'
M`!H`!P`:``<`&@`'`!H`!P`:``<`&@`'`/__! ````L`0@!R`&$`9 `@`$T`
M8P!,`&4`;P!D`#(`0P`Z`%P`=P!I`&X`9 !O`'<`<P!<`%0`10!-`% `7 !!
M`'4`= !O`%(`90!C`&\`=@!E`'(`>0`@`',`80!V`&4`( !O`&8`( !$`&\`
M8P!U`&T`90!N`'0`,0`N`&$`<P!D``L`0@!R`&$`9 `@`$T`8P!,`&4`;P!D
M`%@`0P`Z`%P`00!L`'0`;P!C`" `4 !R`&\`:@!E`&,`= !<`% `<@!O`&H`
M90!C`'0`( !$`&\`8P!U`&T`90!N`'0`80!T`&D`;P!N`%P`5 !E`',`= !I
M`&X`9P`@`$0`;P!C`'4`;0!E`&X`= !A`'0`:0!O`&X`7 !/`' `90!N`" `
M0P!L`&D`90!N`'0`+0!!`%,`10`@`% `<@!O`&(`; !E`&T`+@!D`&\`8P`!
M`)XIH7X/``D$_P__#_\/_P__#_\/_P__#_\/`0`"```````!````````````
M```````````#$ ``#X1H`1&$F/X5Q@4``6@!!F\H``(````N``$```">*:%^
M````````````````________`0``````_T !@ $`OQ8``+\6``"$LVD!(P(C
M`K\6````````OQ8````````"$ ````````# %@``@ ``" ! ```#````1Q:0
M`0```@(&`P4$!0(#! ,````````````````````!`````````%0`:0!M`&4`
M<P`@`$X`90!W`" `4@!O`&T`80!N````-1:0`0(`!04!`@$'!@(%!P``````
M```0``````````````" `````%,`>0!M`&(`;P!L````,R:0`0```@L&! ("
M`@("! ,````````````````````!`````````$$`<@!I`&$`; ```"(`! !Q
M"(@8``#0`@``: $`````:>-#1H'C0T8``````0`3````2@,``,(2```!``D`
M```$``,0* ```````````````0`!`````0`````````A`P``````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``````````````````````````````````````````````"E!L 'M "T`( `
M,C ```````````````````D7````````````````````````````````````
M`````````````````````````````````````````````````````@``````
M__\2``````````$`,0`````````+`$(`<@!A`&0`( !-`&,`3 !E`&\`9 `+
M`$(`<@!A`&0`( !-`&,`3 !E`&\`9 ``````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``````````````````````````````````````````````````````````#^
M_P``! H"```````````````````````!````X(6?\OE/:!"KD0@`*R>SV3 `
M``!L`0``$0````$```"0`````@```)@````#````I ````0```"P````!0``
M`,0````&````T ````<```#<````" ```.P````)``````$``!(````,`0``
M"@```"@!```,````- $```T```! `0``#@```$P!```/````5 $``! ```!<
M`0``$P```&0!```"````Y 0``!X````"````,0!S`!X````!``````!S`!X`
M```,````0G)A9"!-8TQE;V0`'@````$`````<F%D'@````$`````<F%D'@``
M``<```!.;W)M86P`3!X````,````0G)A9"!-8TQE;V0`'@````(````Q`&%D
M'@```!,```!-:6-R;W-O9G0@5V]R9" X+C ``$ `````,GZG`@```$ `````
M;C>+[9B_`4 `````YGA6\)B_`0,````!`````P```$H#```#````PA(```,`
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M_O\```0*`@```````````````````````@````+5S=6<+AL0DY<(`"LL^:Y$
M````!=7-U9PN&Q"3EP@`*RSYKCP!``#X````# ````$```!H````#P```' `
M```%````C ````8```"4````$0```)P````7````I ````L```"L````$ ``
M`+0````3````O ```!8```#$````#0```,P````,````V@````(```#D! ``
M'@```!0```!3=&]N96AE;F=E(%!A<G1N97)S``,````H`````P````D````#
M````"1<```,````Q%0@`"P`````````+``````````L`````````"P``````
M```>$ ```0````(````Q``P0```"````'@````8```!4:71L90`#`````0``
M`)@````#`````````" ````!````-@````(````^`````0````(````*````
M7U!)1%]'54E$``(```#D! ``00```$X```![`#@`1@`R`#@`-P`Q`#@`0@`M
M`# `- !!`$4`+0`Q`#$`1 `T`"T`. !%`#(`, `M`# `, `Q`# `- !"`$8`
M-0!%`$4`. `W`'T`````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``$````"`````P````0````%````!@````<````(````"0````H````+````
M# ````T````.````#P```! ````1````$@```!,````4````%0```!8````7
M````& ```!D```#^____&P```!P````=````'@```!\````@````(0```"(`
M```C````_O___R4````F````)P```"@````I````*@```"L```#^____+0``
M`"X````O````, ```#$````R````,P```/[____]____-@```/[____^____
M_O__________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M________________________4@!O`&\`= `@`$4`;@!T`'(`>0``````````
M`````````````````````````````````````````````````!8`!0'_____
M_____P,````&"0(``````, ```````!&`````,!0ZFGPF+\!8*L<:O"8OP$X
M````@ `````````Q`%0`80!B`&P`90``````````````````````````````
M````````````````````````````````````````#@`"`/______________
M_P```````````````````````````````````````````````!H````0$@``
M`````%<`;P!R`&0`1 !O`&,`=0!M`&4`;@!T````````````````````````
M```````````````````````````````:``(!!0```/__________````````
M`````````````````````````````````````````````"4R````````!0!3
M`'4`;0!M`&$`<@!Y`$D`;@!F`&\`<@!M`&$`= !I`&\`;@``````````````
M`````````````````````"@``@$"````! ```/____\`````````````````
M```````````````````````````````D`````! ````````%`$0`;P!C`'4`
M;0!E`&X`= !3`'4`;0!M`&$`<@!Y`$D`;@!F`&\`<@!M`&$`= !I`&\`;@``
M````````````. `"`?_______________P``````````````````````````
M`````````````````````"P`````$ ````````$`0P!O`&T`< !/`&(`:@``
M````````````````````````````````````````````````````````````
M```2``(!`0````8```#_____````````````````````````````````````
M`````````````````&H`````````3P!B`&H`90!C`'0`4 !O`&\`; ``````
M`````````````````````````````````````````````````````!8``0#_
M______________\``````````````````````````&"K'&KPF+\!8*L<:O"8
MOP$`````````````````````````````````````````````````````````
M`````````````````````````````````````````````````/__________
M_____P```````````````````````````````````````````````&"B1P`Z
M`0#P!P````$```#^____________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M________________________________`0#^_P,*``#_____!@D"``````# 
M````````1A@```!-:6-R;W-O9G0@5V]R9"!$;V-U;65N= `*````35-7;W)D
M1&]C`! ```!7;W)D+D1O8W5M96YT+C@`]#FR<0``````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
I````````````````````````````````````````````````````````
`
end

0
Brad
3/28/2000 8:11:40 PM
sybase.easerver 11371 articles. 0 followers. Follow

21 Replies
714 Views

Similar Articles

[PageSpeed] 31

Is your sp is trying to do ddl ??
Here is what you could try ? Make sure that before you call the stored
procedure you are in autocommit mode (I'm not sure whether you can 'tell'
Dynamo to set the autocommit mode for you or not)

"Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
news:wlbGKKPm$GA.52@forums.sybase.com...
> Lance, Carson and Larry -
>
> Based upon a previous thread I posted regarding ASA and ASE environments
for
> our website DB and the issues we were having, I took your advice and did
the
> following:
>
> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
> 6.0.2
> 2.  Established an Open Client connection profile to the web DB instead of
> using ODBC.
> 3.  Created an Open Client connection from the website to the ASE 11.9.2
> primary database.
>
> Here's is what is happening now!:( - Please see the attachment!
>
> Summary:
>
> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
> the do.
> We have PD web pages that execute SQL and Stored Procedures against the
ASE
> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
executed
> correctly and the data was retrieved as expected.  Now that we've switched
> over to Open Client, we are experiencing failures with all of our stored
> procedures executed by our PD web pages that use stored procedures.
(Please
> refer to the attachment for specifics!)
>
> Further,  any stored procedures that use a 'Select Into' or 'Create'
command
> do not function under either ODBC or Open Client when the PD web DB is in
> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
they
> worked!!
>
> Any ideas, insight, guidance would be appreciated.  As I said, I took all
> your advice and this is where we are at now.  I have to have this
> application, website and supporting database's ready for beta testing in 3
> DAYS!!  HELP!!!
>
> TIA
>
> Brad McLeod
> StoneHenge Partners
>
>
>


0
Ashish
3/28/2000 9:17:39 PM
Ashish -

Did you check out the attachment to this thread that contains the actual sp?

Ashish Mahajan wrote in message ...
>Is your sp is trying to do ddl ??
>Here is what you could try ? Make sure that before you call the stored
>procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>Dynamo to set the autocommit mode for you or not)
>
>"Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>news:wlbGKKPm$GA.52@forums.sybase.com...
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
>for
>> our website DB and the issues we were having, I took your advice and did
>the
>> following:
>>
>> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2.  Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3.  Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
>ASE
>> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
>executed
>> correctly and the data was retrieved as expected.  Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
>(Please
>> refer to the attachment for specifics!)
>>
>> Further,  any stored procedures that use a 'Select Into' or 'Create'
>command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
>they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated.  As I said, I took all
>> your advice and this is where we are at now.  I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!!  HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>>
>>
>
>


0
Brad
3/28/2000 10:40:59 PM
  PowerDynamo runs in chained mode (autoCommit = FALSE) for
performance reasons. We explicitly change to autoCommit=FALSE and the
difference between the ODBC driver and Dynamo's OpenClient driver lies
in
each drivers implementation of AutoCommit. Dynamo's OpenClient driver
toggles chained mode. The ODBC driver does not and probably accomplishes
its AutoCommit support in a very complicated way.

You can change this via the Connection.autoCommit property. You can also
use sp_procxmode but please read the docs on transaction handling first
(tsql guide I believe)


As far as select into, make sure you have 'select into' enabled for the
database.  See the docs for sp_dboption.

Lance

Brad McLeod wrote:
> 
> Lance, Carson and Larry -
> 
> Based upon a previous thread I posted regarding ASA and ASE environments for
> our website DB and the issues we were having, I took your advice and did the
> following:
> 
> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
> 6.0.2
> 2.  Established an Open Client connection profile to the web DB instead of
> using ODBC.
> 3.  Created an Open Client connection from the website to the ASE 11.9.2
> primary database.
> 
> Here's is what is happening now!:( - Please see the attachment!
> 
> Summary:
> 
> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
> the do.
> We have PD web pages that execute SQL and Stored Procedures against the ASE
> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages executed
> correctly and the data was retrieved as expected.  Now that we've switched
> over to Open Client, we are experiencing failures with all of our stored
> procedures executed by our PD web pages that use stored procedures. (Please
> refer to the attachment for specifics!)
> 
> Further,  any stored procedures that use a 'Select Into' or 'Create' command
> do not function under either ODBC or Open Client when the PD web DB is in
> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection, they
> worked!!
> 
> Any ideas, insight, guidance would be appreciated.  As I said, I took all
> your advice and this is where we are at now.  I have to have this
> application, website and supporting database's ready for beta testing in 3
> DAYS!!  HELP!!!
> 
> TIA
> 
> Brad McLeod
> StoneHenge Partners
> 
>                                   Name: Open Client-ASE Problem.doc
>    Open Client-ASE Problem.doc    Type: Microsoft Word Document (application/msword)
>                               Encoding: x-uuencode

-- 
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
3/29/2000 2:19:38 PM
Open Client connections are automatically set to CHAINED = on.  The
autoCommit property in PowerDynamo may be used to set the chained mode to
off.

To set chained mode off, you can do:
<!--SCRIPT
    connection.autoCommit = true;
-->

Another way to do it is to change your SP to anymode.  So, it depends on how
you created your SP.  The SP can be executed in Chained, Unchained, and
Anymode.  To convert a SP to Anymode, you can do it in any isql session:

sp_procxmode [procname [, tranmode]]

tranmode values are: "chained", "unchained", "anymode"

Hope it helps.


"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
news:XV73nuPm$GA.298@forums.sybase.com...
> Is your sp is trying to do ddl ??
> Here is what you could try ? Make sure that before you call the stored
> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
> Dynamo to set the autocommit mode for you or not)
>
> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> news:wlbGKKPm$GA.52@forums.sybase.com...
> > Lance, Carson and Larry -
> >
> > Based upon a previous thread I posted regarding ASA and ASE environments
> for
> > our website DB and the issues we were having, I took your advice and did
> the
> > following:
> >
> > 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
> > 6.0.2
> > 2.  Established an Open Client connection profile to the web DB instead
of
> > using ODBC.
> > 3.  Created an Open Client connection from the website to the ASE 11.9.2
> > primary database.
> >
> > Here's is what is happening now!:( - Please see the attachment!
> >
> > Summary:
> >
> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> > configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
configuration
> > the do.
> > We have PD web pages that execute SQL and Stored Procedures against the
> ASE
> > 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
> executed
> > correctly and the data was retrieved as expected.  Now that we've
switched
> > over to Open Client, we are experiencing failures with all of our stored
> > procedures executed by our PD web pages that use stored procedures.
> (Please
> > refer to the attachment for specifics!)
> >
> > Further,  any stored procedures that use a 'Select Into' or 'Create'
> command
> > do not function under either ODBC or Open Client when the PD web DB is
in
> > ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
> they
> > worked!!
> >
> > Any ideas, insight, guidance would be appreciated.  As I said, I took
all
> > your advice and this is where we are at now.  I have to have this
> > application, website and supporting database's ready for beta testing in
3
> > DAYS!!  HELP!!!
> >
> > TIA
> >
> > Brad McLeod
> > StoneHenge Partners
> >
> >
> >
>
>


0
Bill
3/29/2000 4:17:30 PM
Lance -

Thanks!  I'll let you know how it goes!!

Brad McLeod

Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
>  PowerDynamo runs in chained mode (autoCommit = FALSE) for
>performance reasons. We explicitly change to autoCommit=FALSE and the
>difference between the ODBC driver and Dynamo's OpenClient driver lies
>in
>each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>toggles chained mode. The ODBC driver does not and probably accomplishes
>its AutoCommit support in a very complicated way.
>
>You can change this via the Connection.autoCommit property. You can also
>use sp_procxmode but please read the docs on transaction handling first
>(tsql guide I believe)
>
>
>As far as select into, make sure you have 'select into' enabled for the
>database.  See the docs for sp_dboption.
>
>Lance
>
>Brad McLeod wrote:
>>
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
for
>> our website DB and the issues we were having, I took your advice and did
the
>> following:
>>
>> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2.  Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3.  Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
ASE
>> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
executed
>> correctly and the data was retrieved as expected.  Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
(Please
>> refer to the attachment for specifics!)
>>
>> Further,  any stored procedures that use a 'Select Into' or 'Create'
command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated.  As I said, I took all
>> your advice and this is where we are at now.  I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!!  HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>>                                   Name: Open Client-ASE Problem.doc
>>    Open Client-ASE Problem.doc    Type: Microsoft Word Document
(application/msword)
>>                               Encoding: x-uuencode
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax:  (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!!              Let's Go Penguins!!!
>===========================================================================
====


0
Brad
3/30/2000 4:11:42 PM
Bill -

Between you and Lance, I should be able to get this puppy to work correctly.
I appreciate your advice and I'll let you know what happens!:)

TIA

Brad McLeod

Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
>Open Client connections are automatically set to CHAINED = on.  The
>autoCommit property in PowerDynamo may be used to set the chained mode to
>off.
>
>To set chained mode off, you can do:
><!--SCRIPT
>    connection.autoCommit = true;
>-->
>
>Another way to do it is to change your SP to anymode.  So, it depends on
how
>you created your SP.  The SP can be executed in Chained, Unchained, and
>Anymode.  To convert a SP to Anymode, you can do it in any isql session:
>
>sp_procxmode [procname [, tranmode]]
>
>tranmode values are: "chained", "unchained", "anymode"
>
>Hope it helps.
>
>
>"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
>news:XV73nuPm$GA.298@forums.sybase.com...
>> Is your sp is trying to do ddl ??
>> Here is what you could try ? Make sure that before you call the stored
>> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>> Dynamo to set the autocommit mode for you or not)
>>
>> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>> news:wlbGKKPm$GA.52@forums.sybase.com...
>> > Lance, Carson and Larry -
>> >
>> > Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> > our website DB and the issues we were having, I took your advice and
did
>> the
>> > following:
>> >
>> > 1.  Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> > 6.0.2
>> > 2.  Established an Open Client connection profile to the web DB instead
>of
>> > using ODBC.
>> > 3.  Created an Open Client connection from the website to the ASE
11.9.2
>> > primary database.
>> >
>> > Here's is what is happening now!:( - Please see the attachment!
>> >
>> > Summary:
>> >
>> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> > configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
>configuration
>> > the do.
>> > We have PD web pages that execute SQL and Stored Procedures against the
>> ASE
>> > 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
>> executed
>> > correctly and the data was retrieved as expected.  Now that we've
>switched
>> > over to Open Client, we are experiencing failures with all of our
stored
>> > procedures executed by our PD web pages that use stored procedures.
>> (Please
>> > refer to the attachment for specifics!)
>> >
>> > Further,  any stored procedures that use a 'Select Into' or 'Create'
>> command
>> > do not function under either ODBC or Open Client when the PD web DB is
>in
>> > ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
>> they
>> > worked!!
>> >
>> > Any ideas, insight, guidance would be appreciated.  As I said, I took
>all
>> > your advice and this is where we are at now.  I have to have this
>> > application, website and supporting database's ready for beta testing
in
>3
>> > DAYS!!  HELP!!!
>> >
>> > TIA
>> >
>> > Brad McLeod
>> > StoneHenge Partners
>> >
>> >
>> >
>>
>>
>
>


0
Brad
3/30/2000 4:13:01 PM
Lance -

In a previous thread you had mentioned configuring PowerDynamo document
cache.  Is the intent here to load all of the current website db documents
into cache (memory) or just allocate a certain amount of cache based upon
the size of our website db?

TIA

Bad McLeod

Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
>  PowerDynamo runs in chained mode (autoCommit = FALSE) for
>performance reasons. We explicitly change to autoCommit=FALSE and the
>difference between the ODBC driver and Dynamo's OpenClient driver lies
>in
>each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>toggles chained mode. The ODBC driver does not and probably accomplishes
>its AutoCommit support in a very complicated way.
>
>You can change this via the Connection.autoCommit property. You can also
>use sp_procxmode but please read the docs on transaction handling first
>(tsql guide I believe)
>
>
>As far as select into, make sure you have 'select into' enabled for the
>database.  See the docs for sp_dboption.
>
>Lance
>
>Brad McLeod wrote:
>>
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
for
>> our website DB and the issues we were having, I took your advice and did
the
>> following:
>>
>> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2.  Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3.  Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
ASE
>> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
executed
>> correctly and the data was retrieved as expected.  Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
(Please
>> refer to the attachment for specifics!)
>>
>> Further,  any stored procedures that use a 'Select Into' or 'Create'
command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated.  As I said, I took all
>> your advice and this is where we are at now.  I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!!  HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>>                                   Name: Open Client-ASE Problem.doc
>>    Open Client-ASE Problem.doc    Type: Microsoft Word Document
(application/msword)
>>                               Encoding: x-uuencode
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax:  (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!!              Let's Go Penguins!!!
>===========================================================================
====


0
Brad
3/30/2000 4:47:23 PM
The goal is to cut down as much work that needs to be done by PD.  So
what you are trying to do is minimize access by PD to the backend as
well as the generation of the output from a PD template/script.

Two items get placed into the cache, the source of the document and
optionally the generated output.

You control which document has output stored in the cache by using the
cachedOutputTimeOut tag or property.

for the most optimal performance you want to try and cache as much
output as you possibly can as this saves PD from having to process the
documents on each request.


Brad McLeod wrote:
> 
> Lance -
> 
> In a previous thread you had mentioned configuring PowerDynamo document
> cache.  Is the intent here to load all of the current website db documents
> into cache (memory) or just allocate a certain amount of cache based upon
> the size of our website db?
> 
> TIA
> 
> Bad McLeod
> 
> Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
> >  PowerDynamo runs in chained mode (autoCommit = FALSE) for
> >performance reasons. We explicitly change to autoCommit=FALSE and the
> >difference between the ODBC driver and Dynamo's OpenClient driver lies
> >in
> >each drivers implementation of AutoCommit. Dynamo's OpenClient driver
> >toggles chained mode. The ODBC driver does not and probably accomplishes
> >its AutoCommit support in a very complicated way.
> >
> >You can change this via the Connection.autoCommit property. You can also
> >use sp_procxmode but please read the docs on transaction handling first
> >(tsql guide I believe)
> >
> >
> >As far as select into, make sure you have 'select into' enabled for the
> >database.  See the docs for sp_dboption.
> >
> >Lance
> >
> >Brad McLeod wrote:
> >>
> >> Lance, Carson and Larry -
> >>
> >> Based upon a previous thread I posted regarding ASA and ASE environments
> for
> >> our website DB and the issues we were having, I took your advice and did
> the
> >> following:
> >>
> >> 1.  Generated our website DB in an ASE 11.9.2 environment instead of ASA
> >> 6.0.2
> >> 2.  Established an Open Client connection profile to the web DB instead
> of
> >> using ODBC.
> >> 3.  Created an Open Client connection from the website to the ASE 11.9.2
> >> primary database.
> >>
> >> Here's is what is happening now!:( - Please see the attachment!
> >>
> >> Summary:
> >>
> >> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> >> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD configuration
> >> the do.
> >> We have PD web pages that execute SQL and Stored Procedures against the
> ASE
> >> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
> executed
> >> correctly and the data was retrieved as expected.  Now that we've
> switched
> >> over to Open Client, we are experiencing failures with all of our stored
> >> procedures executed by our PD web pages that use stored procedures.
> (Please
> >> refer to the attachment for specifics!)
> >>
> >> Further,  any stored procedures that use a 'Select Into' or 'Create'
> command
> >> do not function under either ODBC or Open Client when the PD web DB is in
> >> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
> they
> >> worked!!
> >>
> >> Any ideas, insight, guidance would be appreciated.  As I said, I took all
> >> your advice and this is where we are at now.  I have to have this
> >> application, website and supporting database's ready for beta testing in
> 3
> >> DAYS!!  HELP!!!
> >>
> >> TIA
> >>
> >> Brad McLeod
> >> StoneHenge Partners
> >>
> >>                                   Name: Open Client-ASE Problem.doc
> >>    Open Client-ASE Problem.doc    Type: Microsoft Word Document
> (application/msword)
> >>                               Encoding: x-uuencode
> >
> >--
> >===========================================================================
> ====
> >Lance J. Andersen Email: lancea@sybase.com
> >Sybase Product Support Engineering Phone:(781) 564-6336
> >77 South Bedford Street Fax:  (781) 564-7001
> >Burlington, MA 01803
> >
> >The Dark Knight Returns!!!              Let's Go Penguins!!!
> >===========================================================================
> ====

-- 
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
3/30/2000 5:37:22 PM
Lance -

Understand your last and thanks.  Back to the original problem.  I modified
the the stored procedure to use 'anymode' and the database to allow for
'select into'.  Although we no longer get the original error message, we now
get this:

EXEC sp_rptTEST 1,1,'level1','1999-3-1 0:00:00','1999-12-31 0:00:00'-1 --
SELECT INTO command not allowed within multi-statement transaction.

As mentioned earlier, we are running this via an Open Client connection to
ASE 11.9.2.  Any other ideas?  We've got just under 24 hours till
howtime:( and everything we've tried doesn't seem to work!!

TIA

Brad McLeod
StoneHenge Partners

Lance Andersen wrote in message <38E390D2.8688C179@sybase.com>...
>The goal is to cut down as much work that needs to be done by PD.  So
>what you are trying to do is minimize access by PD to the backend as
>well as the generation of the output from a PD template/script.
>
>Two items get placed into the cache, the source of the document and
>optionally the generated output.
>
>You control which document has output stored in the cache by using the
>cachedOutputTimeOut tag or property.
>
>for the most optimal performance you want to try and cache as much
>output as you possibly can as this saves PD from having to process the
>documents on each request.
>
>
>Brad McLeod wrote:
>>
>> Lance -
>>
>> In a previous thread you had mentioned configuring PowerDynamo document
>> cache.  Is the intent here to load all of the current website db
documents
>> into cache (memory) or just allocate a certain amount of cache based upon
>> the size of our website db?
>>
>> TIA
>>
>> Bad McLeod
>>
>> Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
>> >  PowerDynamo runs in chained mode (autoCommit = FALSE) for
>> >performance reasons. We explicitly change to autoCommit=FALSE and the
>> >difference between the ODBC driver and Dynamo's OpenClient driver lies
>> >in
>> >each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>> >toggles chained mode. The ODBC driver does not and probably accomplishes
>> >its AutoCommit support in a very complicated way.
>> >
>> >You can change this via the Connection.autoCommit property. You can also
>> >use sp_procxmode but please read the docs on transaction handling first
>> >(tsql guide I believe)
>> >
>> >
>> >As far as select into, make sure you have 'select into' enabled for the
>> >database.  See the docs for sp_dboption.
>> >
>> >Lance
>> >
>> >Brad McLeod wrote:
>> >>
>> >> Lance, Carson and Larry -
>> >>
>> >> Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> >> our website DB and the issues we were having, I took your advice and
did
>> the
>> >> following:
>> >>
>> >> 1.  Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> >> 6.0.2
>> >> 2.  Established an Open Client connection profile to the web DB
instead
>> of
>> >> using ODBC.
>> >> 3.  Created an Open Client connection from the website to the ASE
11.9.2
>> >> primary database.
>> >>
>> >> Here's is what is happening now!:( - Please see the attachment!
>> >>
>> >> Summary:
>> >>
>> >> PD pages executing stored procedures under an Open Client/ASE 11.9.2
PD
>> >> configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
configuration
>> >> the do.
>> >> We have PD web pages that execute SQL and Stored Procedures against
the
>> ASE
>> >> 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
>> executed
>> >> correctly and the data was retrieved as expected.  Now that we've
>> switched
>> >> over to Open Client, we are experiencing failures with all of our
stored
>> >> procedures executed by our PD web pages that use stored procedures.
>> (Please
>> >> refer to the attachment for specifics!)
>> >>
>> >> Further,  any stored procedures that use a 'Select Into' or 'Create'
>> command
>> >> do not function under either ODBC or Open Client when the PD web DB is
in
>> >> ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC
connection,
>> they
>> >> worked!!
>> >>
>> >> Any ideas, insight, guidance would be appreciated.  As I said, I took
all
>> >> your advice and this is where we are at now.  I have to have this
>> >> application, website and supporting database's ready for beta testing
in
>> 3
>> >> DAYS!!  HELP!!!
>> >>
>> >> TIA
>> >>
>> >> Brad McLeod
>> >> StoneHenge Partners
>> >>
>> >>                                   Name: Open Client-ASE Problem.doc
>> >>    Open Client-ASE Problem.doc    Type: Microsoft Word Document
>> (application/msword)
>> >>                               Encoding: x-uuencode
>> >
>> >--
>>
>===========================================================================
>> ====
>> >Lance J. Andersen Email: lancea@sybase.com
>> >Sybase Product Support Engineering Phone:(781) 564-6336
>> >77 South Bedford Street Fax:  (781) 564-7001
>> >Burlington, MA 01803
>> >
>> >The Dark Knight Returns!!!              Let's Go Penguins!!!
>>
>===========================================================================
>> ====
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax:  (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!!              Let's Go Penguins!!!
>===========================================================================
====


0
Brad
3/30/2000 8:27:58 PM
Brad McLeod wrote:
> 
> Lance -
> 
> Understand your last and thanks.  Back to the original problem.  I modified
> the the stored procedure to use 'anymode' and the database to allow for
> 'select into'.  Although we no longer get the original error message, we now
> get this:
> 
> EXEC sp_rptTEST 1,1,'level1','1999-3-1 0:00:00','1999-12-31 0:00:00'-1 --
> SELECT INTO command not allowed within multi-statement transaction.
> 
> As mentioned earlier, we are running this via an Open Client connection to
> ASE 11.9.2.  Any other ideas?  We've got just under 24 hours till
> howtime:( and everything we've tried doesn't seem to work!!


Well your answer is in the error as you cannot issue SELECT INTO in
chained mode so your choice is to take the PD connection out of chained
mode (see the previous post) or rework your sprocs.


===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
3/30/2000 8:35:03 PM
Bill -

Herein lies the problem!!  We need for the connection to run in 'unchained'
mode so that we can execute 'select into' statements.  The 'autocommit'
needs to be set to false as well.  Based upon your thread, how do we
accomplish this?  Set the sp's mode to 'unchained' and leave the PD Open
Client connection as is?

TIA

Brad McLeod
StoneHenge Partners

Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
>Open Client connections are automatically set to CHAINED = on.  The
>autoCommit property in PowerDynamo may be used to set the chained mode to
>off.
>
>To set chained mode off, you can do:
><!--SCRIPT
>    connection.autoCommit = true;
>-->
>
>Another way to do it is to change your SP to anymode.  So, it depends on
how
>you created your SP.  The SP can be executed in Chained, Unchained, and
>Anymode.  To convert a SP to Anymode, you can do it in any isql session:
>
>sp_procxmode [procname [, tranmode]]
>
>tranmode values are: "chained", "unchained", "anymode"
>
>Hope it helps.
>
>
>"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
>news:XV73nuPm$GA.298@forums.sybase.com...
>> Is your sp is trying to do ddl ??
>> Here is what you could try ? Make sure that before you call the stored
>> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>> Dynamo to set the autocommit mode for you or not)
>>
>> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>> news:wlbGKKPm$GA.52@forums.sybase.com...
>> > Lance, Carson and Larry -
>> >
>> > Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> > our website DB and the issues we were having, I took your advice and
did
>> the
>> > following:
>> >
>> > 1.  Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> > 6.0.2
>> > 2.  Established an Open Client connection profile to the web DB instead
>of
>> > using ODBC.
>> > 3.  Created an Open Client connection from the website to the ASE
11.9.2
>> > primary database.
>> >
>> > Here's is what is happening now!:( - Please see the attachment!
>> >
>> > Summary:
>> >
>> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> > configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
>configuration
>> > the do.
>> > We have PD web pages that execute SQL and Stored Procedures against the
>> ASE
>> > 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
>> executed
>> > correctly and the data was retrieved as expected.  Now that we've
>switched
>> > over to Open Client, we are experiencing failures with all of our
stored
>> > procedures executed by our PD web pages that use stored procedures.
>> (Please
>> > refer to the attachment for specifics!)
>> >
>> > Further,  any stored procedures that use a 'Select Into' or 'Create'
>> command
>> > do not function under either ODBC or Open Client when the PD web DB is
>in
>> > ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
>> they
>> > worked!!
>> >
>> > Any ideas, insight, guidance would be appreciated.  As I said, I took
>all
>> > your advice and this is where we are at now.  I have to have this
>> > application, website and supporting database's ready for beta testing
in
>3
>> > DAYS!!  HELP!!!
>> >
>> > TIA
>> >
>> > Brad McLeod
>> > StoneHenge Partners
>> >
>> >
>> >
>>
>>
>
>


0
Brad
3/31/2000 6:29:15 PM
Brad,

I thought I answered your question via email...

let me know...

Lance

Brad McLeod wrote:
> 
> Bill -
> 
> Herein lies the problem!!  We need for the connection to run in 'unchained'
> mode so that we can execute 'select into' statements.  The 'autocommit'
> needs to be set to false as well.  Based upon your thread, how do we
> accomplish this?  Set the sp's mode to 'unchained' and leave the PD Open
> Client connection as is?
> 
> TIA
> 
> Brad McLeod
> StoneHenge Partners
> 
> Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
> >Open Client connections are automatically set to CHAINED = on.  The
> >autoCommit property in PowerDynamo may be used to set the chained mode to
> >off.
> >
> >To set chained mode off, you can do:
> ><!--SCRIPT
> >    connection.autoCommit = true;
> >-->
> >
> >Another way to do it is to change your SP to anymode.  So, it depends on
> how
> >you created your SP.  The SP can be executed in Chained, Unchained, and
> >Anymode.  To convert a SP to Anymode, you can do it in any isql session:
> >
> >sp_procxmode [procname [, tranmode]]
> >
> >tranmode values are: "chained", "unchained", "anymode"
> >
> >Hope it helps.
> >
> >
> >"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
> >news:XV73nuPm$GA.298@forums.sybase.com...
> >> Is your sp is trying to do ddl ??
> >> Here is what you could try ? Make sure that before you call the stored
> >> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
> >> Dynamo to set the autocommit mode for you or not)
> >>
> >> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> >> news:wlbGKKPm$GA.52@forums.sybase.com...
> >> > Lance, Carson and Larry -
> >> >
> >> > Based upon a previous thread I posted regarding ASA and ASE
> environments
> >> for
> >> > our website DB and the issues we were having, I took your advice and
> did
> >> the
> >> > following:
> >> >
> >> > 1.  Generated our website DB in an ASE 11.9.2 environment instead of
> ASA
> >> > 6.0.2
> >> > 2.  Established an Open Client connection profile to the web DB instead
> >of
> >> > using ODBC.
> >> > 3.  Created an Open Client connection from the website to the ASE
> 11.9.2
> >> > primary database.
> >> >
> >> > Here's is what is happening now!:( - Please see the attachment!
> >> >
> >> > Summary:
> >> >
> >> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> >> > configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
> >configuration
> >> > the do.
> >> > We have PD web pages that execute SQL and Stored Procedures against the
> >> ASE
> >> > 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
> >> executed
> >> > correctly and the data was retrieved as expected.  Now that we've
> >switched
> >> > over to Open Client, we are experiencing failures with all of our
> stored
> >> > procedures executed by our PD web pages that use stored procedures.
> >> (Please
> >> > refer to the attachment for specifics!)
> >> >
> >> > Further,  any stored procedures that use a 'Select Into' or 'Create'
> >> command
> >> > do not function under either ODBC or Open Client when the PD web DB is
> >in
> >> > ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC connection,
> >> they
> >> > worked!!
> >> >
> >> > Any ideas, insight, guidance would be appreciated.  As I said, I took
> >all
> >> > your advice and this is where we are at now.  I have to have this
> >> > application, website and supporting database's ready for beta testing
> in
> >3
> >> > DAYS!!  HELP!!!
> >> >
> >> > TIA
> >> >
> >> > Brad McLeod
> >> > StoneHenge Partners
> >> >
> >> >
> >> >
> >>
> >>
> >
> >

-- 
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
3/31/2000 8:57:55 PM
We set autoCommit = true; in PD script. Unfortunately, it corrupted our
database. Set SP to Anymode  did not work for SP having "Select Into"
command. We got an message "Stored procedure ... may be run only in
unchained transaction mode. The 'SET CHAINED OFF' command will cause the
current session to use unchained transaction mode".  Even we changed the SP
to Unchained by sp_procxmode, we still got the same error message.
It looks like stored proc works only under the Chained mode in PD. I hope I
am wrong. Any thought to solve the problem?

Thanks

Bill Zhang <bill.zhang@sybase.com> wrote in message
news:$9TIDKcm$GA.52@forums.sybase.com...
> Open Client connections are automatically set to CHAINED = on.  The
> autoCommit property in PowerDynamo may be used to set the chained mode to
> off.
>
> To set chained mode off, you can do:
> <!--SCRIPT
>     connection.autoCommit = true;
> -->
>
> Another way to do it is to change your SP to anymode.  So, it depends on
how
> you created your SP.  The SP can be executed in Chained, Unchained, and
> Anymode.  To convert a SP to Anymode, you can do it in any isql session:
>
> sp_procxmode [procname [, tranmode]]
>
> tranmode values are: "chained", "unchained", "anymode"
>
> Hope it helps.
>
>
> "Ashish Mahajan" <ash@NOSPAM.com> wrote in message
> news:XV73nuPm$GA.298@forums.sybase.com...
> > Is your sp is trying to do ddl ??
> > Here is what you could try ? Make sure that before you call the stored
> > procedure you are in autocommit mode (I'm not sure whether you can
'tell'
> > Dynamo to set the autocommit mode for you or not)
> >
> > "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> > news:wlbGKKPm$GA.52@forums.sybase.com...
> > > Lance, Carson and Larry -
> > >
> > > Based upon a previous thread I posted regarding ASA and ASE
environments
> > for
> > > our website DB and the issues we were having, I took your advice and
did
> > the
> > > following:
> > >
> > > 1.  Generated our website DB in an ASE 11.9.2 environment instead of
ASA
> > > 6.0.2
> > > 2.  Established an Open Client connection profile to the web DB
instead
> of
> > > using ODBC.
> > > 3.  Created an Open Client connection from the website to the ASE
11.9.2
> > > primary database.
> > >
> > > Here's is what is happening now!:( - Please see the attachment!
> > >
> > > Summary:
> > >
> > > PD pages executing stored procedures under an Open Client/ASE 11.9.2
PD
> > > configuration, do not execute.  Under an ODBC/ASE 11.9.2 PD
> configuration
> > > the do.
> > > We have PD web pages that execute SQL and Stored Procedures against
the
> > ASE
> > > 11.9.2 database.  When accessing the PD web DB via ODBC, the pages
> > executed
> > > correctly and the data was retrieved as expected.  Now that we've
> switched
> > > over to Open Client, we are experiencing failures with all of our
stored
> > > procedures executed by our PD web pages that use stored procedures.
> > (Please
> > > refer to the attachment for specifics!)
> > >
> > > Further,  any stored procedures that use a 'Select Into' or 'Create'
> > command
> > > do not function under either ODBC or Open Client when the PD web DB is
> in
> > > ASE 11.9.2.  When the PD web DB was in ASA and used an ODBC
connection,
> > they
> > > worked!!
> > >
> > > Any ideas, insight, guidance would be appreciated.  As I said, I took
> all
> > > your advice and this is where we are at now.  I have to have this
> > > application, website and supporting database's ready for beta testing
in
> 3
> > > DAYS!!  HELP!!!
> > >
> > > TIA
> > >
> > > Brad McLeod
> > > StoneHenge Partners
> > >
> > >
> > >
> >
> >
>
>


0
Yong
3/31/2000 9:25:32 PM
Yong Song wrote:
> 
> We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> database. Set SP to Anymode  did not work for SP having "Select Into"
> command. We got an message "Stored procedure ... may be run only in
> unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> current session to use unchained transaction mode".  Even we changed the SP
> to Unchained by sp_procxmode, we still got the same error message.
> It looks like stored proc works only under the Chained mode in PD. I hope I
> am wrong. Any thought to solve the problem?
>

All this does is disable chained mode. Sounds like an ASE issue now.

Try running the sproc via tsql
and see if you encounter the error.  Ribo can show you the TDS that is
being sent to ASE from PD.

Lance
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
3/31/2000 9:59:48 PM
Lance Andersen <lancea@sybase.com> wrote in message
news:38E51FD4.8F16EBE9@sybase.com...
> Yong Song wrote:
> >
> > We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> > database. Set SP to Anymode  did not work for SP having "Select Into"
> > command. We got an message "Stored procedure ... may be run only in
> > unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> > current session to use unchained transaction mode".  Even we changed the
SP
> > to Unchained by sp_procxmode, we still got the same error message.
> > It looks like stored proc works only under the Chained mode in PD. I
hope I
> > am wrong. Any thought to solve the problem?
> >
>
> All this does is disable chained mode. Sounds like an ASE issue now.
>
> Try running the sproc via tsql
> and see if you encounter the error.  Ribo can show you the TDS that is
> being sent to ASE from PD.
>
> Lance
>
============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax:  (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!!              Let's Go Penguins!!!
>
============================================================================
===

Yes, the proc works via tsql. I also tried sproc having only one query( with
or without Select into). The same thing happened.
By the way, could you tell me what TDS means?

Thanks

Yong


0
Yong
3/31/2000 10:54:27 PM
TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc

I would suggest next to download Ribo from the jConnect HOme page,
point your PD app to it which in turn will point to ASE.  This will
let us see the TDS (queries, token types) being sent to ASE.

Please if you can zip up your proc and bcp dump of the data along with
the schema for the table and we will try and take a look.  At the
same time, please open a case with Tech Support.

thanks
Lance

Yong Song wrote:
> 
> Lance Andersen <lancea@sybase.com> wrote in message
> news:38E51FD4.8F16EBE9@sybase.com...
> > Yong Song wrote:
> > >
> > > We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> > > database. Set SP to Anymode  did not work for SP having "Select Into"
> > > command. We got an message "Stored procedure ... may be run only in
> > > unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> > > current session to use unchained transaction mode".  Even we changed the
> SP
> > > to Unchained by sp_procxmode, we still got the same error message.
> > > It looks like stored proc works only under the Chained mode in PD. I
> hope I
> > > am wrong. Any thought to solve the problem?
> > >
> >
> > All this does is disable chained mode. Sounds like an ASE issue now.
> >
> > Try running the sproc via tsql
> > and see if you encounter the error.  Ribo can show you the TDS that is
> > being sent to ASE from PD.
> >
> > Lance
> >
> ============================================================================
> ===
> > Lance J. Andersen Email: lancea@sybase.com
> > Sybase Product Support Engineering Phone:(781) 564-6336
> > 77 South Bedford Street Fax:  (781) 564-7001
> > Burlington, MA 01803
> >
> > The Dark Knight Returns!!!              Let's Go Penguins!!!
> >
> ============================================================================
> ===
> 
> Yes, the proc works via tsql. I also tried sproc having only one query( with
> or without Select into). The same thing happened.
> By the way, could you tell me what TDS means?
> 
> Thanks
> 
> Yong
0
Andersen
4/1/2000 4:17:56 PM
Hi, Lance,

Glad to hear from you.

I also doubt that is an ASE issue because it happens on every proc having
select into, even a proc only has "Select * into #MyTemp from ar_store"
command. It seems to be a generic problem. I am not a ASE DBA. Could you
point me to somewhere I may find the solution?

I downloaded Ribo but I don't know how to point my PD app to Ribo then to
ASE. What computer should I run Ribo on, client PC or Server?
Is the PD port assigned to the listen_port? I tried command Ribo -l 9000 -s
localhost -gui. Ribo gave an error message "The port is in use". 9000 is our
PD port.

Thanks for your help.

Yong

Andersen, Lance / Tonya <lta@tiac.net> wrote in message
news:38E62134.19DFF796@tiac.net...
> TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
>
> I would suggest next to download Ribo from the jConnect HOme page,
> point your PD app to it which in turn will point to ASE.  This will
> let us see the TDS (queries, token types) being sent to ASE.
>
> Please if you can zip up your proc and bcp dump of the data along with
> the schema for the table and we will try and take a look.  At the
> same time, please open a case with Tech Support.
>
> thanks
> Lance
>
> Yong Song wrote:
> >
> > Lance Andersen <lancea@sybase.com> wrote in message
> > news:38E51FD4.8F16EBE9@sybase.com...
> > > Yong Song wrote:
> > > >
> > > > We set autoCommit = true; in PD script. Unfortunately, it corrupted
our
> > > > database. Set SP to Anymode  did not work for SP having "Select
Into"
> > > > command. We got an message "Stored procedure ... may be run only in
> > > > unchained transaction mode. The 'SET CHAINED OFF' command will cause
the
> > > > current session to use unchained transaction mode".  Even we changed
the
> > SP
> > > > to Unchained by sp_procxmode, we still got the same error message.
> > > > It looks like stored proc works only under the Chained mode in PD. I
> > hope I
> > > > am wrong. Any thought to solve the problem?
> > > >
> > >
> > > All this does is disable chained mode. Sounds like an ASE issue now.
> > >
> > > Try running the sproc via tsql
> > > and see if you encounter the error.  Ribo can show you the TDS that is
> > > being sent to ASE from PD.
> > >
> > > Lance
> > >
> >
============================================================================
> > ===
> > > Lance J. Andersen Email: lancea@sybase.com
> > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > 77 South Bedford Street Fax:  (781) 564-7001
> > > Burlington, MA 01803
> > >
> > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > >
> >
============================================================================
> > ===
> >
> > Yes, the proc works via tsql. I also tried sproc having only one
uery( with
> > or without Select into). The same thing happened.
> > By the way, could you tell me what TDS means?
> >
> > Thanks
> >
> > Yong


0
Yong
4/3/2000 10:01:09 PM
Yong,

What is the exact error you get when you run the sproc?

Ribo can run anywhere you like.

Port 9000 is usually used by Jaguar.  What you do is this:

Point PD connections to use port 5005 (the default listener port for
Ribo), Start Ribo specifying the host and port that that your ASE server
is running on.

Run your query and then when complete, use Ribo to translate the binary
stream to an ascii human readable file.

This will show you the resultsets, queries and errors that have gone
back and forth between your PD client and ASE.


I have just tried a sproc which was

create proc procTest as
select * into #foo from pubs2..authors
select * from #foo
go


My PD script:
<html>
<title>test</title>
<body>
<h1>xxx</h1>
<!--Script
  connection.autoCommit=true;
  qu= connection.createQuery("test..procTest");
  if(qu.GetErrorCode())
  {
     document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
      "<p>");
  }
  while(qu.MoveNext())
  {
    document.writeln(qu.GetValue(1) +"<br>");
  }
-->
</body>
</html>

this works fine.

Regards,
Lance

Yong Song wrote:
> 
> Hi, Lance,
> 
> Glad to hear from you.
> 
> I also doubt that is an ASE issue because it happens on every proc having
> select into, even a proc only has "Select * into #MyTemp from ar_store"
> command. It seems to be a generic problem. I am not a ASE DBA. Could you
> point me to somewhere I may find the solution?
> 
> I downloaded Ribo but I don't know how to point my PD app to Ribo then to
> ASE. What computer should I run Ribo on, client PC or Server?
> Is the PD port assigned to the listen_port? I tried command Ribo -l 9000 -s
> localhost -gui. Ribo gave an error message "The port is in use". 9000 is our
> PD port.
> 
> Thanks for your help.
> 
> Yong
> 
> Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> news:38E62134.19DFF796@tiac.net...
> > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> >
> > I would suggest next to download Ribo from the jConnect HOme page,
> > point your PD app to it which in turn will point to ASE.  This will
> > let us see the TDS (queries, token types) being sent to ASE.
> >
> > Please if you can zip up your proc and bcp dump of the data along with
> > the schema for the table and we will try and take a look.  At the
> > same time, please open a case with Tech Support.
> >
> > thanks
> > Lance
> >
> > Yong Song wrote:
> > >
> > > Lance Andersen <lancea@sybase.com> wrote in message
> > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > Yong Song wrote:
> > > > >
> > > > > We set autoCommit = true; in PD script. Unfortunately, it corrupted
> our
> > > > > database. Set SP to Anymode  did not work for SP having "Select
> Into"
> > > > > command. We got an message "Stored procedure ... may be run only in
> > > > > unchained transaction mode. The 'SET CHAINED OFF' command will cause
> the
> > > > > current session to use unchained transaction mode".  Even we changed
> the
> > > SP
> > > > > to Unchained by sp_procxmode, we still got the same error message.
> > > > > It looks like stored proc works only under the Chained mode in PD. I
> > > hope I
> > > > > am wrong. Any thought to solve the problem?
> > > > >
> > > >
> > > > All this does is disable chained mode. Sounds like an ASE issue now.
> > > >
> > > > Try running the sproc via tsql
> > > > and see if you encounter the error.  Ribo can show you the TDS that is
> > > > being sent to ASE from PD.
> > > >
> > > > Lance
> > > >
> > >
> ============================================================================
> > > ===
> > > > Lance J. Andersen Email: lancea@sybase.com
> > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > 77 South Bedford Street Fax:  (781) 564-7001
> > > > Burlington, MA 01803
> > > >
> > > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > > >
> > >
> ============================================================================
> > > ===
> > >
> > > Yes, the proc works via tsql. I also tried sproc having only one
> uery( with
> > > or without Select into). The same thing happened.
> > > By the way, could you tell me what TDS means?
> > >
> > > Thanks
> > >
> > > Yong

-- 
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
4/4/2000 11:46:04 AM
Thanks, Lance.

The error message is:
Stored procedure 'sp_TEST' may be run only in unchained transaction mode.
The 'SET CHAINED OFF' command will cause the current session to use
unchained transaction mode.

The error code I got from PD is -1.

The test script is:
<%@ LANGUAGE=JavaScript %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
    <META NAME=SERVERLANGUAGE CONTENT=JavaScript HTTP-EQUIV=PowerSiteData>
</HEAD>
<BODY>
<%
      var MyConnection = site.GetConnection("Intelimatrix");
      var sSQL = "";
      var MyQuery = MyConnection.CreateQuery();
      sSQL = "EXEC sp_TEST";
      document.writeln(sSQL);
      MyQuery.SetSQL(sSQL);
      MyQuery.Execute();
      if (MyQuery.GetErrorCode())
      {
        document.write(MyQuery.GetErrorCode() + " -- " +
MyQuery.GetErrorInfo());
        return;
      }
      else
        document.writeln("Success!");
%>
</BODY>
</HTML>

sproc:
 CREATE PROCEDURE dbo.sp_test;1
AS
    BEGIN
        select * into #tempTB
        from ar_store where ar_client_id = 1
    END

I didn't put MyConnection.autoCommit = true in the script. Our database
corrupted just after I tested another sproc having select into. It could be
an occincidence but I don't want to take the risk.

I will follow your instruction to use Ribo and let you know the result.

Thanks again.

Yong

Lance Andersen <lancea@sybase.com> wrote in message
news:38E9D5FC.E3DB4B93@sybase.com...
> Yong,
>
> What is the exact error you get when you run the sproc?
>
> Ribo can run anywhere you like.
>
> Port 9000 is usually used by Jaguar.  What you do is this:
>
> Point PD connections to use port 5005 (the default listener port for
> Ribo), Start Ribo specifying the host and port that that your ASE server
> is running on.
>
> Run your query and then when complete, use Ribo to translate the binary
> stream to an ascii human readable file.
>
> This will show you the resultsets, queries and errors that have gone
> back and forth between your PD client and ASE.
>
>
> I have just tried a sproc which was
>
> create proc procTest as
> select * into #foo from pubs2..authors
> select * from #foo
> go
>
>
> My PD script:
> <html>
> <title>test</title>
> <body>
> <h1>xxx</h1>
> <!--Script
>   connection.autoCommit=true;
>   qu= connection.createQuery("test..procTest");
>   if(qu.GetErrorCode())
>   {
>      document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
>       "<p>");
>   }
>   while(qu.MoveNext())
>   {
>     document.writeln(qu.GetValue(1) +"<br>");
>   }
> -->
> </body>
> </html>
>
> this works fine.
>
> Regards,
> Lance
>
> Yong Song wrote:
> >
> > Hi, Lance,
> >
> > Glad to hear from you.
> >
> > I also doubt that is an ASE issue because it happens on every proc
having
> > select into, even a proc only has "Select * into #MyTemp from ar_store"
> > command. It seems to be a generic problem. I am not a ASE DBA. Could you
> > point me to somewhere I may find the solution?
> >
> > I downloaded Ribo but I don't know how to point my PD app to Ribo then
to
> > ASE. What computer should I run Ribo on, client PC or Server?
> > Is the PD port assigned to the listen_port? I tried command Ribo -l
9000 -s
> > localhost -gui. Ribo gave an error message "The port is in use". 9000 is
our
> > PD port.
> >
> > Thanks for your help.
> >
> > Yong
> >
> > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > news:38E62134.19DFF796@tiac.net...
> > > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> > >
> > > I would suggest next to download Ribo from the jConnect HOme page,
> > > point your PD app to it which in turn will point to ASE.  This will
> > > let us see the TDS (queries, token types) being sent to ASE.
> > >
> > > Please if you can zip up your proc and bcp dump of the data along with
> > > the schema for the table and we will try and take a look.  At the
> > > same time, please open a case with Tech Support.
> > >
> > > thanks
> > > Lance
> > >
> > > Yong Song wrote:
> > > >
> > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > Yong Song wrote:
> > > > > >
> > > > > > We set autoCommit = true; in PD script. Unfortunately, it
corrupted
> > our
> > > > > > database. Set SP to Anymode  did not work for SP having "Select
> > Into"
> > > > > > command. We got an message "Stored procedure ... may be run only
in
> > > > > > unchained transaction mode. The 'SET CHAINED OFF' command will
cause
> > the
> > > > > > current session to use unchained transaction mode".  Even we
changed
> > the
> > > > SP
> > > > > > to Unchained by sp_procxmode, we still got the same error
message.
> > > > > > It looks like stored proc works only under the Chained mode in
PD. I
> > > > hope I
> > > > > > am wrong. Any thought to solve the problem?
> > > > > >
> > > > >
> > > > > All this does is disable chained mode. Sounds like an ASE issue
now.
> > > > >
> > > > > Try running the sproc via tsql
> > > > > and see if you encounter the error.  Ribo can show you the TDS
that is
> > > > > being sent to ASE from PD.
> > > > >
> > > > > Lance
> > > > >
> > > >
> >
============================================================================
> > > > ===
> > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > 77 South Bedford Street Fax:  (781) 564-7001
> > > > > Burlington, MA 01803
> > > > >
> > > > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > > > >
> > > >
> >
============================================================================
> > > > ===
> > > >
> > > > Yes, the proc works via tsql. I also tried sproc having only one
> > uery( with
> > > > or without Select into). The same thing happened.
> > > > By the way, could you tell me what TDS means?
> > > >
> > > > Thanks
> > > >
> > > > Yong
>
> --
>
============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax:  (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!!              Let's Go Penguins!!!
>
============================================================================
===


0
Yong
4/4/2000 3:32:58 PM
You are going to want to run with autoCommit as in my example.

There are restrictions with what you can do in chained mode.

Yong Song wrote:
> 
> Thanks, Lance.
> 
> The error message is:
> Stored procedure 'sp_TEST' may be run only in unchained transaction mode.
> The 'SET CHAINED OFF' command will cause the current session to use
> unchained transaction mode.
> 
> The error code I got from PD is -1.
> 
> The test script is:
> <%@ LANGUAGE=JavaScript %>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> <HTML>
> <HEAD>
>     <META NAME=SERVERLANGUAGE CONTENT=JavaScript HTTP-EQUIV=PowerSiteData>
> </HEAD>
> <BODY>
> <%
>       var MyConnection = site.GetConnection("Intelimatrix");
>       var sSQL = "";
>       var MyQuery = MyConnection.CreateQuery();
>       sSQL = "EXEC sp_TEST";
>       document.writeln(sSQL);
>       MyQuery.SetSQL(sSQL);
>       MyQuery.Execute();
>       if (MyQuery.GetErrorCode())
>       {
>         document.write(MyQuery.GetErrorCode() + " -- " +
> MyQuery.GetErrorInfo());
>         return;
>       }
>       else
>         document.writeln("Success!");
> %>
> </BODY>
> </HTML>
> 
> sproc:
>  CREATE PROCEDURE dbo.sp_test;1
> AS
>     BEGIN
>         select * into #tempTB
>         from ar_store where ar_client_id = 1
>     END
> 
> I didn't put MyConnection.autoCommit = true in the script. Our database
> corrupted just after I tested another sproc having select into. It could be
> an occincidence but I don't want to take the risk.
> 
> I will follow your instruction to use Ribo and let you know the result.
> 
> Thanks again.
> 
> Yong
> 
> Lance Andersen <lancea@sybase.com> wrote in message
> news:38E9D5FC.E3DB4B93@sybase.com...
> > Yong,
> >
> > What is the exact error you get when you run the sproc?
> >
> > Ribo can run anywhere you like.
> >
> > Port 9000 is usually used by Jaguar.  What you do is this:
> >
> > Point PD connections to use port 5005 (the default listener port for
> > Ribo), Start Ribo specifying the host and port that that your ASE server
> > is running on.
> >
> > Run your query and then when complete, use Ribo to translate the binary
> > stream to an ascii human readable file.
> >
> > This will show you the resultsets, queries and errors that have gone
> > back and forth between your PD client and ASE.
> >
> >
> > I have just tried a sproc which was
> >
> > create proc procTest as
> > select * into #foo from pubs2..authors
> > select * from #foo
> > go
> >
> >
> > My PD script:
> > <html>
> > <title>test</title>
> > <body>
> > <h1>xxx</h1>
> > <!--Script
> >   connection.autoCommit=true;
> >   qu= connection.createQuery("test..procTest");
> >   if(qu.GetErrorCode())
> >   {
> >      document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
> >       "<p>");
> >   }
> >   while(qu.MoveNext())
> >   {
> >     document.writeln(qu.GetValue(1) +"<br>");
> >   }
> > -->
> > </body>
> > </html>
> >
> > this works fine.
> >
> > Regards,
> > Lance
> >
> > Yong Song wrote:
> > >
> > > Hi, Lance,
> > >
> > > Glad to hear from you.
> > >
> > > I also doubt that is an ASE issue because it happens on every proc
> having
> > > select into, even a proc only has "Select * into #MyTemp from ar_store"
> > > command. It seems to be a generic problem. I am not a ASE DBA. Could you
> > > point me to somewhere I may find the solution?
> > >
> > > I downloaded Ribo but I don't know how to point my PD app to Ribo then
> to
> > > ASE. What computer should I run Ribo on, client PC or Server?
> > > Is the PD port assigned to the listen_port? I tried command Ribo -l
> 9000 -s
> > > localhost -gui. Ribo gave an error message "The port is in use". 9000 is
> our
> > > PD port.
> > >
> > > Thanks for your help.
> > >
> > > Yong
> > >
> > > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > > news:38E62134.19DFF796@tiac.net...
> > > > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> > > >
> > > > I would suggest next to download Ribo from the jConnect HOme page,
> > > > point your PD app to it which in turn will point to ASE.  This will
> > > > let us see the TDS (queries, token types) being sent to ASE.
> > > >
> > > > Please if you can zip up your proc and bcp dump of the data along with
> > > > the schema for the table and we will try and take a look.  At the
> > > > same time, please open a case with Tech Support.
> > > >
> > > > thanks
> > > > Lance
> > > >
> > > > Yong Song wrote:
> > > > >
> > > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > > Yong Song wrote:
> > > > > > >
> > > > > > > We set autoCommit = true; in PD script. Unfortunately, it
> corrupted
> > > our
> > > > > > > database. Set SP to Anymode  did not work for SP having "Select
> > > Into"
> > > > > > > command. We got an message "Stored procedure ... may be run only
> in
> > > > > > > unchained transaction mode. The 'SET CHAINED OFF' command will
> cause
> > > the
> > > > > > > current session to use unchained transaction mode".  Even we
> changed
> > > the
> > > > > SP
> > > > > > > to Unchained by sp_procxmode, we still got the same error
> message.
> > > > > > > It looks like stored proc works only under the Chained mode in
> PD. I
> > > > > hope I
> > > > > > > am wrong. Any thought to solve the problem?
> > > > > > >
> > > > > >
> > > > > > All this does is disable chained mode. Sounds like an ASE issue
> now.
> > > > > >
> > > > > > Try running the sproc via tsql
> > > > > > and see if you encounter the error.  Ribo can show you the TDS
> that is
> > > > > > being sent to ASE from PD.
> > > > > >
> > > > > > Lance
> > > > > >
> > > > >
> > >
> ============================================================================
> > > > > ===
> > > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > > 77 South Bedford Street Fax:  (781) 564-7001
> > > > > > Burlington, MA 01803
> > > > > >
> > > > > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > > > > >
> > > > >
> > >
> ============================================================================
> > > > > ===
> > > > >
> > > > > Yes, the proc works via tsql. I also tried sproc having only one
> > > uery( with
> > > > > or without Select into). The same thing happened.
> > > > > By the way, could you tell me what TDS means?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Yong
> >
> > --
> >
> ============================================================================
> ===
> > Lance J. Andersen Email: lancea@sybase.com
> > Sybase Product Support Engineering Phone:(781) 564-6336
> > 77 South Bedford Street Fax:  (781) 564-7001
> > Burlington, MA 01803
> >
> > The Dark Knight Returns!!!              Let's Go Penguins!!!
> >
> ============================================================================
> ===

-- 
===============================================================================
Lance J. Andersen			Email: lancea@sybase.com 
Sybase Product Support Engineering	Phone:(781) 564-6336 
77 South Bedford Street			Fax:  (781) 564-7001
Burlington, MA 01803                    

The Dark Knight Returns!!!              Let's Go Penguins!!!
===============================================================================
0
Lance
4/4/2000 3:48:19 PM
Hi, Lance,

I took your advice adding connection.autoCommit = true in the script. It
worked!
So it meant the setting autoCommit = true might not be a piece of  the
database corruption puzzle.

Thank you very much. You gave us a hugh help.

Best regards,

Yong

Lance Andersen <lancea@sybase.com> wrote in message
news:38EA0EC3.1AA0524A@sybase.com...
> You are going to want to run with autoCommit as in my example.
>
> There are restrictions with what you can do in chained mode.
>
> Yong Song wrote:
> >
> > Thanks, Lance.
> >
> > The error message is:
> > Stored procedure 'sp_TEST' may be run only in unchained transaction
mode.
> > The 'SET CHAINED OFF' command will cause the current session to use
> > unchained transaction mode.
> >
> > The error code I got from PD is -1.
> >
> > The test script is:
> > <%@ LANGUAGE=JavaScript %>
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> > <HTML>
> > <HEAD>
> >     <META NAME=SERVERLANGUAGE CONTENT=JavaScript
HTTP-EQUIV=PowerSiteData>
> > </HEAD>
> > <BODY>
> > <%
> >       var MyConnection = site.GetConnection("Intelimatrix");
> >       var sSQL = "";
> >       var MyQuery = MyConnection.CreateQuery();
> >       sSQL = "EXEC sp_TEST";
> >       document.writeln(sSQL);
> >       MyQuery.SetSQL(sSQL);
> >       MyQuery.Execute();
> >       if (MyQuery.GetErrorCode())
> >       {
> >         document.write(MyQuery.GetErrorCode() + " -- " +
> > MyQuery.GetErrorInfo());
> >         return;
> >       }
> >       else
> >         document.writeln("Success!");
> > %>
> > </BODY>
> > </HTML>
> >
> > sproc:
> >  CREATE PROCEDURE dbo.sp_test;1
> > AS
> >     BEGIN
> >         select * into #tempTB
> >         from ar_store where ar_client_id = 1
> >     END
> >
> > I didn't put MyConnection.autoCommit = true in the script. Our database
> > corrupted just after I tested another sproc having select into. It could
be
> > an occincidence but I don't want to take the risk.
> >
> > I will follow your instruction to use Ribo and let you know the result.
> >
> > Thanks again.
> >
> > Yong
> >
> > Lance Andersen <lancea@sybase.com> wrote in message
> > news:38E9D5FC.E3DB4B93@sybase.com...
> > > Yong,
> > >
> > > What is the exact error you get when you run the sproc?
> > >
> > > Ribo can run anywhere you like.
> > >
> > > Port 9000 is usually used by Jaguar.  What you do is this:
> > >
> > > Point PD connections to use port 5005 (the default listener port for
> > > Ribo), Start Ribo specifying the host and port that that your ASE
server
> > > is running on.
> > >
> > > Run your query and then when complete, use Ribo to translate the
binary
> > > stream to an ascii human readable file.
> > >
> > > This will show you the resultsets, queries and errors that have gone
> > > back and forth between your PD client and ASE.
> > >
> > >
> > > I have just tried a sproc which was
> > >
> > > create proc procTest as
> > > select * into #foo from pubs2..authors
> > > select * from #foo
> > > go
> > >
> > >
> > > My PD script:
> > > <html>
> > > <title>test</title>
> > > <body>
> > > <h1>xxx</h1>
> > > <!--Script
> > >   connection.autoCommit=true;
> > >   qu= connection.createQuery("test..procTest");
> > >   if(qu.GetErrorCode())
> > >   {
> > >      document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
> > >       "<p>");
> > >   }
> > >   while(qu.MoveNext())
> > >   {
> > >     document.writeln(qu.GetValue(1) +"<br>");
> > >   }
> > > -->
> > > </body>
> > > </html>
> > >
> > > this works fine.
> > >
> > > Regards,
> > > Lance
> > >
> > > Yong Song wrote:
> > > >
> > > > Hi, Lance,
> > > >
> > > > Glad to hear from you.
> > > >
> > > > I also doubt that is an ASE issue because it happens on every proc
> > having
> > > > select into, even a proc only has "Select * into #MyTemp from
ar_store"
> > > > command. It seems to be a generic problem. I am not a ASE DBA. Could
you
> > > > point me to somewhere I may find the solution?
> > > >
> > > > I downloaded Ribo but I don't know how to point my PD app to Ribo
then
> > to
> > > > ASE. What computer should I run Ribo on, client PC or Server?
> > > > Is the PD port assigned to the listen_port? I tried command Ribo -l
> > 9000 -s
> > > > localhost -gui. Ribo gave an error message "The port is in use".
9000 is
> > our
> > > > PD port.
> > > >
> > > > Thanks for your help.
> > > >
> > > > Yong
> > > >
> > > > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > > > news:38E62134.19DFF796@tiac.net...
> > > > > TDS is the protocol used to speak to ASE, RepServer,
OPenSErver..etc
> > > > >
> > > > > I would suggest next to download Ribo from the jConnect HOme page,
> > > > > point your PD app to it which in turn will point to ASE.  This
will
> > > > > let us see the TDS (queries, token types) being sent to ASE.
> > > > >
> > > > > Please if you can zip up your proc and bcp dump of the data along
with
> > > > > the schema for the table and we will try and take a look.  At the
> > > > > same time, please open a case with Tech Support.
> > > > >
> > > > > thanks
> > > > > Lance
> > > > >
> > > > > Yong Song wrote:
> > > > > >
> > > > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > > > Yong Song wrote:
> > > > > > > >
> > > > > > > > We set autoCommit = true; in PD script. Unfortunately, it
> > corrupted
> > > > our
> > > > > > > > database. Set SP to Anymode  did not work for SP having
"Select
> > > > Into"
> > > > > > > > command. We got an message "Stored procedure ... may be run
only
> > in
> > > > > > > > unchained transaction mode. The 'SET CHAINED OFF' command
will
> > cause
> > > > the
> > > > > > > > current session to use unchained transaction mode".  Even we
> > changed
> > > > the
> > > > > > SP
> > > > > > > > to Unchained by sp_procxmode, we still got the same error
> > message.
> > > > > > > > It looks like stored proc works only under the Chained mode
in
> > PD. I
> > > > > > hope I
> > > > > > > > am wrong. Any thought to solve the problem?
> > > > > > > >
> > > > > > >
> > > > > > > All this does is disable chained mode. Sounds like an ASE
issue
> > now.
> > > > > > >
> > > > > > > Try running the sproc via tsql
> > > > > > > and see if you encounter the error.  Ribo can show you the TDS
> > that is
> > > > > > > being sent to ASE from PD.
> > > > > > >
> > > > > > > Lance
> > > > > > >
> > > > > >
> > > >
> >
============================================================================
> > > > > > ===
> > > > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > > > 77 South Bedford Street Fax:  (781) 564-7001
> > > > > > > Burlington, MA 01803
> > > > > > >
> > > > > > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > > > > > >
> > > > > >
> > > >
> >
============================================================================
> > > > > > ===
> > > > > >
> > > > > > Yes, the proc works via tsql. I also tried sproc having only one
> > > > uery( with
> > > > > > or without Select into). The same thing happened.
> > > > > > By the way, could you tell me what TDS means?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Yong
> > >
> > > --
> > >
> >
============================================================================
> > ===
> > > Lance J. Andersen Email: lancea@sybase.com
> > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > 77 South Bedford Street Fax:  (781) 564-7001
> > > Burlington, MA 01803
> > >
> > > The Dark Knight Returns!!!              Let's Go Penguins!!!
> > >
> >
============================================================================
> > ===
>
> --
>
============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax:  (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!!              Let's Go Penguins!!!
>
============================================================================
===


0
Yong
4/4/2000 8:36:39 PM
Reply:

Similar Artilces:

Dates using ODBC vs. Open Client connection
My HTML Datawindow retrieve works using an ODBC connection string to ASE 11.5, but fails to return data with a SYJ Open Client connection. The date parameter passed to RetrieveEx is the same format ( "1999-10-27" ). The same Datawindow retrieval works in PowerBuilder using SYC Open Client connection with same format date argument. Why should the Open Client connection in PD behave differently? Thanks. Helen Seabrook wrote: > My HTML Datawindow retrieve works using an ODBC connection string to ASE > 11.5, but fails to return data with a SYJ Open Client conn...

Single open connection vs connection pool (opening and closing each time)
I see that log4net use single open connection instead of connection pool. They don't open and close the connection each time they just do it once in the beginning.  What are the risks of such approach in a multythreaded environment?  What can happen if two threads want to use the connection at the same time?  Is there a risk associated with that?  The fact is that if using just a single connection there is a performance benefit, then what is the down side? Or we are just wrong by doint this? using(var c = new SqlConnection(str)){   // use connection ......

The connection is already open and the connection state is connecting.
Hello, I am getting this error time to time randomly. My web application is built on asp.net 3.5 which uses ODBC 5.1 driver to connect to mysql database. I have a separate database class which handles the connection, execute, fetching and all. The application runs fine for sometime then suddenly the users start getting this error after which the application fails to insert select from database. I have posted in this forum couple of times now and no one is really contributing or helping me. Please..Any help will be highly appreciated.. Many thanks, Viv The database abstract loo...

Open/Close connection VS. Connection pool?
My site have very heavy traffic and many users reach the database at the sametime. I wonder witch it is the best strategy to connect to the database: open/close the connections as soon as possible OR use a connection pool? If a connection pool it is a better strategy please submit some code in C# about a connection pool. ASP.NET does connection pooling all by itself, presuming connection strings are identical. It will do a better job than you are likely to do, so open as late as possible, close as early as possible, and ASP.NET will handle connection pooling for you.Starting with ASP.NET ...

Opened connection vs connection string perfomance
Is there a performance hit by using a connection string to open a connection, execute and then close it vs having the connection open as soon as the app initializes. Need to insert a million rows over the course of the day. Thanks If you use Connection pooling (which is enabled by default), then the underlying connection to db is kept open... So generally speaking the only overhead is to pull the connection out from the pool... -Ashish <GG> wrote in message news:41990eed.490.1681692777@sybase.com... > Is there a performance hit by using a connection string to > ...

PowerDynamo open client connection
Hi, I'm trying to create an connection profile using open client source.but each time i enter the necessary values it gives an error saying some [odbc][error]. what can be the problem Jyothi ---== Posted via the PFCGuide Web Newsreader ==--- http://www.pfcguide.com/_newsgroups/group_list.asp ...

test for open connection before connection.open command
Hi I am trying to work together a peice of code that will basically state: If MyCon.Open Then 'do nothing Else MyCon.Open() End If This is because occasionally the SQL.ExecuteReader() occasionally times out and when the user trys again the page errors and states that the MyCon is already open. Has anyone had to deal with this before? Thanks for any help, Skippy. Try this - If MyCon.state = ConnectionState.open Then 'do nothing else ... In fact, if you require only to check connection is open and if not open the connection then fo...

not connected when I am connected
What do I need to change on my 'puter when the icon in the toolbar shows and tells me I am connected and the error message tells me I am not and I can not go to web pages, get or send emails. I have to close down and restart to get connected again. This only happens if I am on line and leave the 'puter for an hour or so. As long as I am using it I don't have a problem. This just started about a month ago. I am on very slow dialup, DSL and Cable not in my area, thanks you SBC/ATT tks Elaine wrote: > What do I need to change on my 'puter when the icon in ...

odbc/ open client connection question ?
I am connrecting to a sybase 11 server from nt network. currently I use opne client 11.1. I want to switch to odbc. Using the odbc administrator in setting up the connection it appears that there is no place to address the server, unless I am refrring to an exisiting datasource defined in open client dsedit. Do I still need open client to use odbc ????? Hello Richard, yes you still need open client to use sybase ODBC driver! Sybase implemented the ODBC driver as an wrapper around the open client. Bye Wolfgang Kunk RTL Television "R. SEIGLEMAN" schrieb: &g...

jdbc connection cache vs client library connection cache
I see options for Client Library to encrypt data by passing the information to the DBMS. But I don't see similar options for JDBC. Are the Sybase 11.0 encryption options only available through the Client Library driver? TIA, Tim The encryption you see of OpenClient is only to encrypt the password. The rest of the stream is i the clear. jConnect can go inside of SSL but you need to tunell, and detunnel etc etc. Dave Wolf Internet Applications Division Tim Nesham <tim.nesham@born.com> wrote in message news:38ac2dbf@news.qgraph.com... > I see options f...

Open Client Connection to PowerDynamo destroys data
I have created a small Project with Powersite, connected to SQL Any 5.5 and deployed it to Power Dynamo 2.0.2 using an ODBC Profile. All worked fine. To Deploy the Project to an Internetserver, with Openserver Gateway listening to a free Port, I established a Powerdynamo connection with open client. The first connection was successful, but I did not have all templates and tools but the createt Folders and fhe html - files Deployed with Powersite could not be opened. The second try to open the Open Client Connection to PD failed with an massage, that this is are files from an ol...

Oracle connectivity through ODBC vs Oracle client
Hai all I m facing problem , regarding retreiving data from a datawindow having date columns in 4 digit format. By using Oracle client connection report retrived without errors but by using ODBC it gives " NO rows found". Version Details are : PB Ver 7.0.3 Build 10135 Oracle 8i Can anyone tell the solution. Regards Shweta ---== Posted via the PFCGuide Web Newsreader ==--- http://www.pfcguide.com/_newsgroups/group_list.asp Does your data order match the date order for the database. i.e.,the client may use mm/dd/yyyy on the client side and the database may use IS...

EAServer 6.0 connect to MS SQL SERVER using ODBC Connection
I am currently migrating from EAServer 4.2 to 6.0. I am trying to connect a SQL Server database through an ODBC connection in EAServer 6.0. When I set up the data source and tried to ping the database server, it gives me an error saying it cannot connect to the database. I have tried to change the database type from SQL SERVER to JCM_ODBC and other multiple things to try to connect, but it still fails. The odbc connection is properly set up but I can't seem to connect through EAServer. Any help would be appreciated. Could you please give the log of EAServer6 which is under ...

connection pooling and open connections
Hi Dmitry, I have connection pooling enabled and I'm connecting to MySQL with 2 AdConnection at the same time. Is it normal that I see 2 active connections on MySQL management and not just one? I thought that when using connection pooling they would share the same one. Thanks, Lorenzo Hello Lorenzo > Is it normal that I see 2 active connections on MySQL management and not > just one? FireDAC does not open the pooled connections before they will be really needed. Instead FireDAC returns open connections back to pool instead of closing them, when they are no l...

Client Connections and PowerBuilder connections
What do I need to do to my NT box to be able to run a browser from a client machine to run the demo database/tutorial? I am able to run the demo from the NT server itself, but would like to test client connectivity. My client has browser capability. Furthermore, I am anticipating on using Jaguar as a middle tier for accepting communications from PowerBuilder. Jaguar would then take the SQL and pass the information onto a SYBASE SQL Server. I am not even concerned with any of the business logic that may be involved but am more interested in getting Jaguar to be a middle tier while...

Web resources about - PowerDynamo and Open Client connections vs ODBC connections - HELP!!!! - sybase.easerver

Sybase fights to stay in tool game
The company will lay out a plan for bringing its flagship PowerBuilder development tool more fully into the era of distributed application building. ...

Product Data Sheets - Sybase Inc
switch to mobile view Worldwide [change] Argentina Australia Austria Belgium Brazil Canada China Czech Republic Denmark Finland France Germany ...

Sybase debuts Web tools
Sybase is continuing its comeback in the database and development tool market, debuting packages for building intranet and Internet applications. ...

Sybase Software Downloads and Code Samples - Database and Mobility Software - Sybase Inc
The business intelligence and database management software download center offers various Sybase software downloads and code samples. For more ...

Resources last updated: 2/4/2016 9:13:22 PM