Not all RM Library routines are available in Visual COBOL.

The one that you show is not on the list of supported routines which can be found here

Thanks for your response. Do Microfocus has any other modules that can be coded to replace these. If yes what are the modules for C$ and how the coding can be done . THanks.

Visual COBOL has an extensive list of library routines that can be accessed but you may have trouble calling them if you are using DIALECT"RM". DIALECT"RM" is mainly used to provide compatibility with existing RM programs and should not really be used if you are modernizing your application with Visual COBOL extensions.

The list of routines can be found here

The problem is that setting DIALECT"RM" also sets the directive DEFAULTCALLS = 1024 which is the default for RM library routines. The default for Visual COBOL library routines is 0. In order to call the VC library routines you will have to specify the call-convention on the call statement.

Example:

special-names.
   call-convention 0 is mfcall.

call mfcall "CBL_LIB_ROUTINE" using ...

Thanks For your reply.

So if I understand correctly RM cobol programs(with DIALECT"RM") can not call these Visual cobol Routines directly.

So In order to use these routines the RM cobol programs need to be compiled with Microfocus instead of DIALECT"RM".

could you please provide me the list of RM Routines VS the respective Microfocus routine so that i will try to use them.

And Also could you please share me the best practices/ Issue log for modernizing these RM to Microfocus Visual cobol So that i can try to modernize few programs and will let you know if any additional questions.

Thanks for your help.

Programs compiled with DIALECT"RM" can call the Visual COBOL library routines but you have to add the calling convention to the call statement as shown in my previous post. Sorry, but I do not have a list of corresponding RM->VC routines. I am not an expert in that area. If somebody else has experience with doing a conversion from RM to VC then maybe they can add their expertise here.

The documentation contains a compatibility guide that outlines many of the differences between the two products.

It can be found here.