Re: syntax issue -- MIDRANGE-L

I see that Crystalreports is asking all kinds of basic questions - he/she really needs to read the SQL Reference or Pence's SQL book or something - yeah, we've been nice about answering all this, but it is getting ridiculous - and I hope I'm not being just a curmudgeon here - there's stuff that can go pretty wrong without a broader, more comprehensive understanding, I think.

I just hope this person, of whom we know very little, is not in a department outside of IT at some company and trying to muck with data outside of channels.

Did CR say who they are? I get nervous around these "anonymous" posts. Maybe I'm just too used to this being a very open community, where we actually think we might meet face to face someday.

Vern

On 5/24/2013 5:25 PM, Gary Thompson wrote:

In the Run SQL Scripts menu, open "Connection", then select "JDBC Settings",
then click on the "Format" tab.

Naming convention can be either:

System (*SY) mylib/myfile
SQL(*SQL) mylib.myfile

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crystal Reports
Sent: Friday, May 24, 2013 4:15 PM
To: midrange-l@xxxxxxxxxxxx
Subject: syntax issue

I did run finally the sql query but had some errors why is it using my name as the library/

Connected to relational database S9090abc on 1nn.1nn.n.n as crystalcleardecisions - 644367/Quser/Qzdasoinit

SELECT NOTEH6.UARIDC , NOTEH6.UANOTL , NOTEP1.UCCMT ,
OEORH41.OHORD# , OEORH41.OHOSTC , OEORH41.OHORDT ,

OEORH41.OHORDD , OEORH41.OHPO# , OEORH41.OHSHTC , OEORH41.OHSLR# , OETRA95.OTTRNC , REFER1.RFCAT , REFER1.RFDAT FROM OEORH41 INNER JOIN REFER1 ON OEORH41.OHSHTC = REFER1.RFSLC INNER JOIN OETRA95 ON OEORH41.OHCOM# = OETRA95.OTCOM# AND OEORH41.OHORD# = OETRA95.OTORD# INNER JOIN NOTEH6 ON OEORH41.OHENT# = NOTEH6.UAENT# AND OEORH41.OHSFX# = NOTEH6.UASFX# INNER JOIN NOTEP1 ON NOTEH6.UANOTT = NOTEP1.UCNOTT AND NOTEH6.UANTK = NOTEP1.UCNTK AND NOTEH6.UANOT# = NOTEP1.UCNOT# WHERE NOTEH6.UARIDC = 'UA' and OETRA95.OTTRNC = '001' and OEORH41.OHORDD = CURRENT DATE and OEORH41.OHORDT IN ('COC', 'COE', 'COF', 'COR', 'COS') AND OEORH41.OHOSTC <> 'CN' and REFER1.RFCAT = '0023'

SQL State: 42704
Vendor Code: -204
Message: [SQL0204] OEORH41 in crystalcleardecisions type *FILE not found.
Cause . . . . . : OEORH41 in crystalcleardecisions type *FILE was not found.
If the member name is *ALL, the table is not partitioned.
If this is an ALTER TABLE statement and the type is *N, a constraint or partition was not found.
If this is not an ALTER TABLE statement and the type is *N, a function, procedure, trigger or sequence object was not found. If a function was not found, OEORH41 is the service program that contains the function. The function will not be found unless the external name and usage name match exactly. Examine the job log for a message that gives more details on which function name is being searched for and the name that did not match.
Recovery . . . : Change the name and try the request again. If the object is a node group, ensure that the
DB2 Multisystem product is installed on your system and create a nodegroup with the CRTNODGRP CL command.
If an external function was not found, be sure that the case of the EXTERNAL NAME on the CREATE FUNCTION statement exactly matches the case of the name exported by the service program.

Processing ended because the highlighted statement did not complete successfully
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.