× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thank Birgitta. That is what I was looking for. Now my next issue.

After I have inserted the rows with the GUIDs, I then use CPYTOIMPF to
export this table. The CPYTOIMPF completes normally but I have a few recs
where the GUID column now has extra characters (in the csv file). This
causes an issue when someone on the PC side uses the IMPORT DB2 command. I
believe this is due to the fact that the GUID column has a double quote in
it. I have tried different combinations of the STRDLM and STRESCCHR parm
on the CPYTOIMPF with no luck.

Does anyone have any suggestions on what STRDLM and STRESCCHR combination
to use, or is this is even the issue? Thanks.

rpg400-l-bounces@xxxxxxxxxxxx wrote on 06/19/2008 10:15:47 PM:

Hi,

Too fast last time!

I assume the column was defined with CHAR(13) FOR BIT DATA, because the
column must be filled with an unique value where the timestamp is
encrypted.

Since V5R4 SQL provides a scalar function GENERATE_UNIQUE(): The
GENERATE_UNIQUE function returns a bit data character string 13 bytes
long
(CHAR(13) FOR BIT DATA) that is unique compared to any other execution
of
the same function.

The result of the function is a unique value that includes the internal
form
of the Universal Time, Coordinated (UTC) and the system serial number.
The
result cannot be null.

This function differs from using the special register CURRENT TIMESTAMP
in
that a unique value is generated for each instance of the function in an
SQL
statement and each row of a multiple row insert statement or an insert
statement with a fullselect. The timestamp value that is part of the
result
of this function can be determined using the TIMESTAMP function with the
result of GENERATE_UNIQUE as an argument.

Example:
INSERT INTO MYTABLE (FLD1, FLD2, FLD3)
VALUES(Generate_Unique(),'ABC', 123);

SELECT Timestamp(Fld1), Fld1
From MyTable;

May be that's what you are looking for!

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars."
(Les
Brown)

"If you think education is expensive, try ignorance." (Derek Bok)

"What is worse than training your staff and losing them? Not training
them
and keeping them!"



-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von MKirkpatrick@xxxxxxxxxxxxxxxxx
Gesendet: Thursday, June 19, 2008 20:46
An: RPG400-L@xxxxxxxxxxxx
Betreff: CHAR for BIT DATA fld


I have a column defined as CHAR FOR BIT DATA or CHAR(13) CCSID 65535 NOT

NULL. Why? Because this is the way it is defined in another table from

DB2 (Windows) that I am trying to duplicate/populate. W/in my RPG pgm,
the following stmt generates the correct data: CREDGUID =
x'20080618090909123456202020';

My problem is I need to use a variable (TIMESTAMP + 3 chars) part of
the
value used to populate the CREDGUID column. I have tried stringing
together using the '+' char but when the data gets into the column it is

truncated because the working variable is larger than the result
(CREDGUID). I also tried using the HEX SQL BIF without success.

Any ideas or suggestions would be greatly appreciated. Thanks.





This email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
Unless you are the addressee (or authorized to receive for the
addressee),
you may not use, copy or disclose to anyone this email or any
information
contained in this email. If you have received this email in error,
please
advise the sender by replying to this email, and delete this email
immediately. Please note that any views or opinions presented in this
email
are solely those of the author and do not necessarily represent those of
Western Dental Services, Inc. Finally, the recipient should check this
email and any attachments for the presence of viruses. Western Dental
Services, Inc. accepts no liability for any damage caused by any virus
transmitted by this email.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.






This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone this email or any information contained in this email. If you have received this email in error, please advise the sender by replying to this email, and delete this email immediately. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Western Dental Services, Inc. Finally, the recipient should check this email and any attachments for the presence of viruses. Western Dental Services, Inc. accepts no liability for any damage caused by any virus transmitted by this email.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.