What compile options should I use for a program written for RM/COBOL?

Question ID : 208
Created on 2013-07-19 at 10:30 AM
Author : Veryant Support [support@veryant.com]

Online URL : http://support.veryant.com/support/phpkb/question.php?ID=208


When compiling source files of a RM/COBOL application, the following options should always be used: 

   -cr -ce=cbl -crko -crlk -dcii -dvext=32 -pt0 -va
Many RM/COBOL applications imply the SIGN IS TRAILING SEPARATE clause for signed data items.RM/COBOL version 1.6 behaved this way.

RM/COBOL version 2.x can optionally behave this way. If the application was written originally with version 2.0 or later, then it might not behave this way.

You will need to examine the source to see if the "S" picture element counts in the size of an item or not.
It is important to determine whether or not the sign counts in the size, particularly if you plan to convert existing data files, otherwise records loaded from RM/COBOL files may not match the record layout described in the program. To imply the SIGN IS TRAILING SEPARATE clause with isCOBOL, use the following compiler option: 
   -ds
With RM/COBOL, the default intensity during ACCEPT for UNIX machines is high intensity and for MS-DOS machines is low intensity.
With isCOBOL every ACCEPT uses low intensity by default. If you need to force a default high intensity on ACCEPT, use the following compiler option: 
   -vh
Many RM/COBOL applications use a specific mode of memory management. In this mode, all of the currently active programs must fit in 64K bytes, but programs that are not currently active do not.
This has the effect of dynamically canceling inactive subprograms as needed to gain memory. To obtain a similar behavior with isCOBOL, use the following compiler option: 
   -zi
For more information on compile options and other concerns when transitioning from RM/COBOL to isCOBOL, consult the transition guide specific to RM/COBOL in isCOBOL's documentation set.


Back to Original Question