RE: [sqr-users] Formal parameter '@P83' was defined as OUTPUT but theactual parameter not declared OUTPUT.

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

Thanks - I tried the show thing, all of the data (successful and bombed)
looks exactly the same.

I'll try the Commit approach.

What's weird is that the data being inserted is very lite - it should be
able to insert 90 rows of data without errors.

I've also posted this with Microsoft - a Google search shows similar errors
with other apps accessing SQL Server.

I'll post my final findings to this group.

Joe 

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 Jim Womeldorf
Sent: Wednesday, April 05, 2006 3:47 PM
To: This list is for discussion about the SQR database reporting language
from Hyperion Solutions.
Subject: RE: [sqr-users] Formal parameter '@P83' was defined as OUTPUT
buttheactual parameter not declared OUTPUT.

This is a real stab in the dark, but I'd try 'show'ing the values before
the insert to see if anything jumps out at you.
Perhaps a COMMIT every so often would help?
Like I said, stabbing in the dark :) 
I'm totally unfamiliar with the 'Formal parameter '@P83' was defined as
OUTPUT but the actual parameter not declared OUTPUT.' error.
Jim

-----Original Message-----
From: sqr-users-bounces+jwomeldo=fastenal.com@sqrug.org
[mailto:sqr-users-bounces+jwomeldo=fastenal.com@sqrug.org] On Behalf Of
Joe Johnson
Sent: Wednesday, April 05, 2006 3:16 PM
To: 'This list is for discussion about the SQR database reporting
language from Hyperion Solutions.'
Subject: RE: [sqr-users] Formal parameter '@P83' was defined as OUTPUT
but theactual parameter not declared OUTPUT.

Yes - the file looks just as it should.

Plus, I just successfully loaded the data, but not before I split the
input file into 4 files and did each one separately.  Equally strange -
I would cut down each file until it ran successfully, saving off what I
cut into an 'error' file.  Then, without making any changes to the data,
I ran the 'error' file, and it loaded successfully as well!

That tells me the data is fine, but there must be something squirrelly
in SQL Server, PeopleSoft ODBC, SQR.

Thanks,

Joe Johnson
Software Developer
Ernest Health, Inc.
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 Jim Womeldorf
Sent: Wednesday, April 05, 2006 2:09 PM
To: This list is for discussion about the SQR database reporting
language from Hyperion Solutions.
Subject: RE: [sqr-users] Formal parameter '@P83' was defined as OUTPUT
buttheactual parameter not declared OUTPUT.

I assume you have examined the csv file closely to be certain it does
not contain any strange characters like form feeds?
Jim 

-----Original Message-----
From: sqr-users-bounces+jwomeldo=fastenal.com@sqrug.org
[mailto:sqr-users-bounces+jwomeldo=fastenal.com@sqrug.org] On Behalf Of
Joe Johnson
Sent: Wednesday, April 05, 2006 2:06 PM
To: 'This list is for discussion about the SQR database reporting
language from Hyperion Solutions.'
Subject: [sqr-users] Formal parameter '@P83' was defined as OUTPUT but
theactual parameter not declared OUTPUT.

Greetings Group,

I have seen this error posted in the history for SQRUG, but none of the
posts seem to fit my error here.

We are using SQR for Peoplesoft 8.47 and MS SQL Server 2000.

I have a straightforward program that inserts Merit and Accomplishment
data from a csv file into 4 tables.  The majority of the fields that are
inserted for each table are obtained by doing a select on that table.

What I have run into is this:

If the CSV file has more than 50 rows in it, it bombs with the following
error:

Formal parameter '@P83' was defined as OUTPUT but the actual parameter
not declared OUTPUT.

The insert for '@P83' is this:

Begin-sql
insert into PS_JOB_JR
(Columns listed .....)
Values
......
......
,&JOBJR.FP_PT_END_DT
......

Etc.

The value &JOBJR.FP_PT_END_DT is selected from PS_JOB_JR in a previous
step.

Here's the part that gets me -- if I cut the input csv file to 40 rows,
there is no error.  If I run the rest of the file, as long as it is less
than 50 rows, there is no error.

My file parameters being set are:

#define RecLength  1500        
#define RecType    Vary

What gives?

There is no temp table involved, nor is there a stored procedure.  

Any help will be appreciated.

Thanks,

Joe Johnson
Software Developer
Ernest Health, Inc.
joejohnson@ernesthealth.com



_______________________________________________
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



_______________________________________________
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



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