Conference orarep::nomahs::rdb_60

~%RDB-E-CONVERT_ERROR, invalid or unsupported data conversion.
~-RDMS-E-CSETBADASSIGN, incompatible character sets prohibit the requested assignment.

The error describes a CHARACTER SET error, so this would be CHAR, VARCHAR or
NCHAR data types.

~%CC-I-UNSUPPTYPE, The CDD description for x_time speciciese data type not supported in C.
~#dictionary "DD$DEFAULT.xxx.RDB$RELATIONS.xxxx"

Please show the definition for this CDD record

Ian

-.1>~%RDB-E-CONVERT_ERROR, invalid or unsupported data conversion.
-.1>~-RDMS-E-CSETBADASSIGN, incompatible character sets prohibit the requested assignment.
-.1>
-.1>The error describes a CHARACTER SET error, so this would be CHAR, VARCHAR or
-.1>NCHAR data types.

Do you mean "RDMS-E-CSETBADASSIGN" cause of "%CC-I-UNSUPPTYPE"?

-.2>The target table has VMS DATE type columns. Is "CONVERT_ERROR" cause of it?
-.2>I test about another table which has not VMS DATE type column, or try to select 
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.2>instead of create & open cursor, but it still has same error.

Does "%CC-I-UNSUPPTYPE" point out CHAR, VARCHAR or NCHAR types? not VMS DATE type?

-.1>Please show the definition for this CDD record

Here is the "%CC-I-UNSUPPTYPE"'s full message and CDD record. 

%CC-I-UNSUPPTYPE, The CDD description for station_delete_time speciciese data type not supported in C.
#dictionary "DD$DEFAULT.EQUIPMENT_MANAGEMENT.RDB$RELATIONS.STATION_MAIN"

Welcome to CDO V6.1
The CDD/Repository V6.1 User Interface
Type HELP for help
Definition of record STATION_MAIN
|   Contains field           STATION_NUMBER
|   |   Based on                 SQL$SML
|   |   |   Datatype                 signed word
|   Contains field           STATION_DISTRICT
|   |   Based on                 SQL$BYT
|   |   |   Datatype                 signed byte
|   Contains field           STATION_NAME
|   |   Based on                 SQL$20CHR
|   |   |   Datatype                 text size is 20 characters
|   Contains field           STATION_POSITION
|   |   Based on                 SQL$INT
|   |   |   Datatype                 signed longword
|   Contains field           STATION_NAME_POSITION
|   |   Based on                 SQL$INT
|   |   |   Datatype                 signed longword
|   Contains field           STATION_START
|   |   Based on                 SQL$INT
|   |   |   Datatype                 signed longword
|   Contains field           STATION_END
|   |   Based on                 SQL$INT
|   |   |   Datatype                 signed longword
|   Contains field           STATION_TIME_STAMP
|   |   Based on                 SQL$ADT
|   |   |   Datatype                 date
|   Contains field           STATION_DELETE_TIME
|   |   Based on                 SQL$ADT
|   |   |   Datatype                 date
                         
Regards.
Naoko

~-.1>~%RDB-E-CONVERT_ERROR, invalid or unsupported data conversion.
~-.1>~-RDMS-E-CSETBADASSIGN, incompatible character sets prohibit the requested assignment.
~-.1>
~-.1>The error describes a CHARACTER SET error, so this would be CHAR, VARCHAR or
~-.1>NCHAR data types.
~
~Do you mean "RDMS-E-CSETBADASSIGN" cause of "%CC-I-UNSUPPTYPE"?

Did I say that?  Please do not confuse the two messages.  I do not think they
are related.

The "RDMS-E-CSETBADASSIGN" message says that the character set for a CHAR,
VARCHAR or NCHAR is being assigned a value from an incompatible character set. 

Is the logical RDB$CHARACTER_SET defined?  If so what as?
Do you use CHARACTER SET?  Maybe at the database level?  I expect you do in
Japan. 

~-.2>The target table has VMS DATE type columns. Is "CONVERT_ERROR" cause of it?
~-.2>I test about another table which has not VMS DATE type column, or try to select 
~                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
~-.2>instead of create & open cursor, but it still has same error.
~
~Does "%CC-I-UNSUPPTYPE" point out CHAR, VARCHAR or NCHAR types? not VMS DATE type?

Well this is not an ERROR, it is in information message.  It is saying that C
doesn't understand DATE types, but that is nothing new.  CDD will just
generate a C char[] variable of the correct size.

Ian

~Now I try to port an application from Rdb V6.0 on VMS/VAX V5.5-2 to Rdb V6.1 on
~VMS/AXP V6.2. But, it fail in this error when it try to create & open cursor.
~
~%RDB-E-CONVERT_ERROR, invalid or unsupported data conversion.
~-RDMS-E-CSETBADASSIGN, incompatible character sets prohibit the requested assignment.

So now show us the code which declares and opens the cursor.

Ian

RDB$CHARACTER_SET is DEC_KANJI in system logical name.

>So now show us the code which declares and opens the cursor.

I do compile & link by these commands.
SCC/DEB/NOOP/STAND=VAXC/nomember_align SUZUKI.SC
LINK/DEB/EXEC=SUZUKI.EXE SUZUKI.OBJ,sys$library:sql$user/lib

The source file, SUZUKI.SC, is below. Thank you!
/****/
#include <stdio.h>                                      
#include descrip.h

short int	rdb_err_len;               
char		rdb_err_msg[400];
$DESCRIPTOR( rdb_err_msg_dsc , rdb_err_msg );

EXEC SQL INCLUDE SQLCA;
EXEC SQL INCLUDE FROM DICTIONARY 'CDD$DEFAULT.EQUIPMENT_MANAGEMENT.RDB$RELATIONS.STATION_MAIN' FIXED;

EXEC SQL DECLARE ALIAS
COMPILETIME PATHNAME 'JRTOUKAI$CDD:EQUIPMENT_MANAGEMENT'
RUNTIME  FILENAME 'JRTOUKAI$RDB:EQUIPMENT_MANAGEMENT';

/****/
main()
{
	int 	  status;
	short int number;
	short int init_ind[10];
	struct 	station_main	station_main;
                                                   
	printf("\n... START ...\n");

	    EXEC SQL DECLARE GET_STATION_CUR CURSOR FOR
		SELECT *
		FROM STATION_MAIN
		ORDER BY STATION_DISTRICT,STATION_POSITION,STATION_START;
                                         
	    EXEC SQL OPEN GET_STATION_CUR;

	    if( SQLCA.SQLCODE != 0 ){
		SQL$GET_ERROR_TEXT( &rdb_err_msg_dsc,&rdb_err_len );
	    	printf("*** Error at CURSOR ***\n%s", rdb_err_msg);
	    }

	EXEC SQL DISCONNECT DEFAULT;
	if( SQLCA.SQLCODE != 0 ) {
	    SQL$GET_ERROR_TEXT( &rdb_err_msg_dsc,&rdb_err_len );
	    printf("*** Error at DISCONNRCT ***\n%s", rdb_err_msg);
	}

	printf("\n... END ...\n");
} 
/****/

Please enter a BUG report for Rdb.  Someone will need to investigate further.

Ian

>Please enter a BUG report for Rdb.  Someone will need to investigate further.

Now I try to find and get patch kits for Rdb V6.1. 
And I'm looking about for how and to whome I should enter this bug report.

Thank you very much.
Naoko

>>Please enter a BUG report for Rdb.  Someone will need to investigate further.
>
>Now I try to find and get patch kits for Rdb V6.1. 
>And I'm looking about for how and to whome I should enter this bug report.

And, that error still be on Rdb V6.1-04.
I enterd this bug report to our support channel.

Thanks again.
Naoko