Highlighted
Absent Member.
Absent Member.
1448 views

RM 2 Visual Cobol

Dear Chris,

We just migrate an Application from RM Cobol to Visual Cobol for Eclipse and we noted that our Files are very diferent in Size. Could you please give a reason for that ??.

Regards

 
 
TAMAÑO EN RMCOBOL = 514490368
 

TAMAÑO EN VISUAL COBOL = 1241272408      ( como tuvimos problema con comp-6 , lo eliminamos y dejamos con comp-3, tiene las mismas clave principal y segundarias)

Pedro Juan Montero Bernales

PJM Informatica Soluciones Globales

Santiago - Chile

0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

RE: RM 2 Visual Cobol

Dear Sirs,

Any answer about this question...????

Pedro Juan Montero Bernales

PJM Informatica Soluciones Globales

Santiago - Chile

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

RE: RM 2 Visual Cobol

You state that you are using Eclipse.  However, Eclipse is a development environment for both Linux/Unix and Windows.  Which operating system are you using?  

Also, an output from RMMAPINX (see RM Users Guide for use) would be helpful in understanding the file's characteristics.  Simply looking at size does not tell us much.  But RMMAPINX will tell how much space is used for storing the index trees versus the data records, and the amount of compression that is achieved.  


Tom Morrison
Consultant

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: RM 2 Visual Cobol

Dear Sir,

We usThere are several differences:




1. The size of the log with the previous definition (RM and COMP-6) occupies 133 bytes, while the current (VC and COMP-3) occupies 183 bytes.




2. The size of the indices; before the primary key occupies 23 bytes and with duplicate keys occupy 4, 2, 13 and 1 bytes; now the primary key occupies 30 bytes and with duplicate keys occupy 5, 3, 16 and 1 bytes.




3. RM indexed files have the indication in the configuration file that uses both data compression and indices


                RUN-FILES INDEX-data-compression = yes force-force-closed = no data = no force-disk = no

                RUN-FILES INDEX-force-index = no key-compression = yes

     While now no compression is required.




Does it justify why the deal triple space ?, I can not tell; but obviously now the same data take up more space.e Linux for Fevelopment and Unix AIX for Deployment.

Pedro Juan Montero Bernales

PJM Informatica Soluciones Globales

Santiago - Chile

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: RM 2 Visual Cobol

Sorry Sir,

We USE Linux for Development and we Use UNIX AIX for Deployment...And I sent others Differents..

Pedro Juan Montero Bernales

PJM Informatica Soluciones Globales

Santiago - Chile

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: RM 2 Visual Cobol

Hi Pedro,

If you are now using COMP-3 instead of COMP-6 then your fields will be larger. COMP-6 in RM is unsigned PACKED-DECIMAL and COMP-3 in VC is signed PACKED-DECIMAL so an extra byte of storage may be required to hold the sign.

You can emulate the RM COMP-6 behavior by using the RM dialect directive which will set the COMP-6"2" directive on. Then if you define your data as COMP-6 and it has no sign in the PIC then the extra byte will not be used.

You can also specify data and key compression on your files using the DATACOMPRESS or KEYCOMPRESS directives or by setting this on in a file handler configuration file.

Thanks

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.