RE: Datalinks

Vern, Good Guess.  
I copied this one Insert statement into in interactive SQL session and
added the file://localhost prefix and ran the statement.  It added the
record.  Kewl.  

Then I went to the source file changed all the records to include the
prefix.  Received error.  

Performed a CLRPFM on EMPLOYEE.  Copied next statement to STRSQL, reran-
error.  

Error 25 occurred using DataLink data type.
-- Error type 25 is file already linked.   

Now I have to try and figure out how to remove the link and try again.  

I'm not positive this is the best approach to my problem, but so far all
I have come up with is either the Datalink or a BLOB.  Initial thought
was to access these images from a green screen session, however I'm
fairly confident I can't do that(although not positive)

The request is to link images that relate to a particular service card
and have a user be able to see this image. 
When the record is accessed.  



Michael Smith
iSeries.mySeries.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Monday, October 16, 2006 12:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Datalinks


Just a wild guess, Mike - the first parameter of DLVALUE is supposed 
to be a URL, I believe - the docs at V5R2 says it needs to have a 
scheme and server - try adding file://localhost in front maybe. I've 
not done this, had no need to work with data links yet.

At 11:18 AM 10/16/2006, you wrote:

Vern,
First here is one of the sql statements.
INSERT INTO EMPLOYEE VALUES
  ( 104681, 'BARB', 'L', 'GIBBENS ', 898613,
     DLVALUE( '/MYDATALINKS/EMPNOTES/BARBGIBBENS.TXT' ) );

Here is some of the text from the joblog.
 Message . . . . :  -RUNSQLSTM SRCFILE(DATALINK/QCLSRC)
SRCMBR(POPEMPSQL)
   COMMIT(*NONE)

    10/16/06  08:37:54.881360  QDBSIGEX     QSYS        0D70

QSQRUN3

QS
 To module . . . . . . . . . :   QSQINS

 To procedure  . . . . . . . :   SQL_Insert

 Statement . . . . . . . . . :   9897

 Message . . . . :   Data mapping error on member QSQPTABL.

 Cause . . . . . :   A data mapping error occurred on field *N in

record

number
   1, record format QSQPTABL, member number 1, in member QSQPTABL file

QSQPTABL
   in library QSYS2, because of error code 28. The error codes and 
their

   meanings follow: 26 -- For the CAST operation, a source character 
was found
   that is not valid. 27 -- For the CAST operation, the character 
destination
   field is too short to hold all the significant digits of the 
source. 28 --
   User-defined function DLVALUE returned a mapping error. 29 -- Java


   10/16/06  08:37:54.902880  QDBSIGEX     QSYS        01D6

QDBSIGEX

QS
Message . . . . :   Data mapping error on member QSQPTABL.

Cause . . . . . :   A data mapping error occurred on member QSQPTABL
file
  QSQPTABL in library QSYS2, because the data fields in record number 
1,

  record format FORMAT0002, member number 1 are in error. Recovery  . 
. . :
   If the record number is zero, the error occurred on an attempt to 
put or
   update a record through a logical file, or the error occurred on a 
group by
   operation, or the error was caused by a default value, or the error

was
   caused by a null value in the record.  See previously listed 
message CPF5035
   or CPD5036 to determine which fields are in error.  Change the 
fields that
   are in error and try the operation again. If the record number is 
not zero,
   the error occurred on an attempt to read an existing record from a 
file.
   See previously listed message CPF5035 or CPD5036 to determine which

physical
   file fields are in error. Then either delete the record from the 
file or
   change the data in the fields that are in error. Then try your 
request
   again. Possible choices for replying to message . . . . . . . . . .

. . . .

 Message . . . . :   Error 21 occurred using DataLink data type.

 Cause . . . . . :   An error occurred while using a DataLink.

Possible

errors
   are: -- Error type 21 is format of DataLink value not valid. -- 
Error type
   22 is the DataLink File Manager (DLFM) is not properly configured 
on the
   server. -- Error type 23 is link type not valid. -- Error type 24 
is file
   does not exist. -- Error type 25 is file already linked. -- Error 
type 26 is
   file not available. -- Error type 27 is length of comment or URL 
not valid.


There are 0 records in file Employee

Michael Smith
iSeries.mySeries.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Monday, October 16, 2006 9:10 AM
To: Midrange Systems Technical Discussion
Subject: Re: Datalinks


There should be more information at second level - please post it. 
Easiest way to get it might be DSPJOBLOG OUTPUT(*PRINT) and copy-paste 
the relevant section.

At 07:55 AM 10/16/2006, you wrote:

I'm trying to make use of Datalinks.  I am working through an article

in the IseriesNetwork from Jan of 01. " RPG IV "Crib Sheet" for SQL 
DataLinks" I've gone through all the steps, however, when I run the 
sql

statement to populate the datalinks I get the following error.
 Data mapping error on member QSQPTABL.
 Data mapping error on member QSQPTABL.
 Data mapping error on member QSQPTABL.
 Error 21 occurred using DataLink data type.
 RUNSQLSTM command failed.
 RUNSQLSTM command failed.
Error type 21 is format of DataLink value not valid.

I have searched the archives and found some references to this, but I

haven't come across a solution.

Anybody have an idea what is causing this and how to correct it?

Thanks.


Michael Smith
iSeries.mySeries.

--
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.

--
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.


--
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.