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)

Parents
  • 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.

Reply
  • 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.

Children
No Data