Skip to main content

Hi! 

I am playing around with the software, trying to update our conversion programs to no longer use Database Connectors.  

In my program I have an input file that is an RM\\COBOL ISAM file, and when I run the program, it is giving me a 9+,00 error code. 

I have tried adding the  $SET  DIALECT(RM)  FILETYPE(21) command to the beginning of the program to let the program know that I am using an RM\\COBOL file, BUT, when I do that, the embedded SQL commands are no longer recognized by the compiler, and I can't get the program to compile.  Is there a way to do this, or am I stuck using Database Connectors for my conversion programs? 

Hi! 

I am playing around with the software, trying to update our conversion programs to no longer use Database Connectors.  

In my program I have an input file that is an RM\\COBOL ISAM file, and when I run the program, it is giving me a 9+,00 error code. 

I have tried adding the  $SET  DIALECT(RM)  FILETYPE(21) command to the beginning of the program to let the program know that I am using an RM\\COBOL file, BUT, when I do that, the embedded SQL commands are no longer recognized by the compiler, and I can't get the program to compile.  Is there a way to do this, or am I stuck using Database Connectors for my conversion programs? 

Try removing DIALECT"RM" and keeping FILETYPE"21"


Try removing DIALECT"RM" and keeping FILETYPE"21"

That did it! Thanks for your help 🙂


That did it! Thanks for your help 🙂

I have another question.  When using the $SET FILETYPE"21" with programs that print reports, the program freezes, and does not print out the report.  Is there another command I would use for that?  


I have another question.  When using the $SET FILETYPE"21" with programs that print reports, the program freezes, and does not print out the report.  Is there another command I would use for that?  

Hi Amy,

Can you please provide more details?

What do you mean by "prints reports", assigning to PRINTER, using PC_PRINTER routines, something else?

What statement does it "freeze" on?


Hi Amy,

Can you please provide more details?

What do you mean by "prints reports", assigning to PRINTER, using PC_PRINTER routines, something else?

What statement does it "freeze" on?

I have a report that has a select statement that assigns to printer, and after I choose the printer, the program stops working on this line

WRITE PRINT-RECORD FROM PRINT-LINE
AFTER ADVANCING ADVANCE-NUM.


I have a report that has a select statement that assigns to printer, and after I choose the printer, the program stops working on this line

WRITE PRINT-RECORD FROM PRINT-LINE
AFTER ADVANCING ADVANCE-NUM.

Try setting the directive $SET FILETYPE"0" before the SELECT statement for the printer or set FILETYPE"21" at the file level instead of at the program level.

$SET FILETYPE"21"

           select 21-file ...

           select another-21-file...

$SET FILETYPE"0"

           select print-file...

$SET FILETYPE"21"


Try setting the directive $SET FILETYPE"0" before the SELECT statement for the printer or set FILETYPE"21" at the file level instead of at the program level.

$SET FILETYPE"21"

           select 21-file ...

           select another-21-file...

$SET FILETYPE"0"

           select print-file...

$SET FILETYPE"21"

Yep! That was it! Thanks!!