RE: [sqr-users] Re: Formal parameter '@P83' was defined as OUTPUT butthe actual parameter not declared OUTPUT.

["Joe Johnson" <joejohnson@ernesthealth.com>]

Thanks, Nathan

Yes, I definitely have the ODBC version - thanks for the info.

PeopleSoft Customer Support reported that the ODBC driver we have from our
PeopleTools 8.47 upgrade is a 'new' driver and should be OK.

I looked at previous logs, and we actually had this same error on the 'old'
version of PeopleTools, although the cut-off on rows processed without
errors was around 75.

This is one of the few Interfaces that I run outside of PeopleSoft.  I
wonder if I set up a Run Control within PeopleSoft and ran it if it would
make a difference.  I know that we have other processes that hit the
database harder than the problem program, but they are all run from within
PS using Run Controls.

I'll keep poking around.

Thanks,

Joe 

Direct: (505) 798-6480 
email: joejohnson@ernesthealth.com


-----Original Message-----
From: sqr-users-bounces+joejohnson=ernesthealth.com@sqrug.org
[mailto:sqr-users-bounces+joejohnson=ernesthealth.com@sqrug.org] On Behalf
Of Nathan Stratton Treadway
Sent: Monday, April 10, 2006 10:10 AM
To: This list is for discussion about the SQR database reporting language
from Hyperion Solutions.
Subject: [sqr-users] Re: Formal parameter '@P83' was defined as OUTPUT
buttheactual parameter not declared OUTPUT.

On Fri, Apr 07, 2006 at 09:59:44AM -0500, Knapp, Richard wrote:
> 
> It's not just the driver.  There is something about the SQR executable
> that limits its use to the database you specified when you bought (SQR
> or PeopleSoft).  If you bought PS for SQL Server and all SQL Server
> supports is ODBC access, then you have an ODBC version of SQR.  Of
> course, you also need the correct driver.
> 
> My Oracle SQRW will not work with an ODBC database like MYSQL even if I
> specify an ODBC driver.
> 
> Maybe Nathan or Ray could jump in here and flesh out our understanding.

The issue that Richard is referring to is that SQR comes in specific
"flavors" to support specific database connection libraries.  Richard
has "SQR for Oracle"; other flavors include "SQR for DB2" and "SQR for
Sybase", and "SQR for Informix".  Each flavor is compiled against an API
providied by that particular database and thus can't be used to connect
to other database products.  (For example, generally speaking "SQR for
Oracle" uses SQL*Net to connect to remote databases, and can't connect
to databases that don't support that protocol.)

As far as SQR is concerned, "SQR for ODBC" is a flavor similar to the
database-specific ones mentioned above.  In this case, you can connect
to various database products, but that's because ODBC inherently lets
you do that -- SQR is still "fixed" on using one particular database
API, namely ODBC.

The error message that Joe gave on Apr 6 shows he is running the ODBC
version of SQR, but he can check for sure by hitting the "About" button
on the SQRW dialog box (the one where you enter the report name and
login information) and looking at the first line of the resulting
information box (assuming PeopleSoft's SQRW still follows the same
convention as Hyperion's SQR does).  Or he could run the 1-line program
listed at:
  http://www.sqrug.org/sqr-users/sqr-users-hints.html#ss4.2
to get the version information.  (The SQR for ODBC version string will
include "ODBC" in the second-to-last section, just before the compile
date.)


Unfortunately I'm not familar enough with ODBC and SQL Server to guess
what's causing the error in question....  However, you (Joe) mention
that you've recently upgraded to a new version of PeopleSoft; if you can
still find an earlier version of SQR and/or the ODBC Driver manager and
SQL Server ODBC Driver (e.g. from an earlier version of PeopleSoft), it
might be worth trying a few combinations of new and older versions of
each piece to see if you find a combination that doesn't trigger this
particular bug....  If you were able to narrow down the problem to the
latest version of one specific piece, then at least you know you need to
contact whoever provided that piece.


                                                        Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway  -  nathanst@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users



_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users