Hi experts... 

Does anyone know what the .vc file versions of ODM actually do ? (CuAt and CuAt.vc, por example) 

What I've researched about them (besides "don't touch them or you'll be fired") is that these files are named according to their "variable character" or vchar content, and every time we use odmadd, odmcreate, odmdelete, and other ODM commands, information is entered into those files.

The ODM odmget command doesn't recognize them as part of ODM, and they could not be queried or reviewed.

You may notice that many of these files are not empty for example, when listing SMIT ODM files:

server /usr/lib/objrepos $ ls -l sm*
-rw-rw-r--    1 root     system       368640 Jun 28 2024  sm_cmd_hdr
-rw-rw-r--    1 root     system       999424 Jun 28 2024  sm_cmd_hdr.vc
-rw-rw-r--    1 root     system      2113536 Jun 28 2024  sm_cmd_opt
-rw-rw-r--    1 root     system      1146880 Jun 28 2024  sm_cmd_opt.vc
-rw-rw-r--    1 root     system       585728 Jun 28 2024  sm_menu_opt
-rw-rw-r--    1 root     system       143360 Jun 28 2024  sm_menu_opt.vc
-rw-rw-r--    1 root     system       143360 Jun 28 2024  sm_name_hdr
-rw-rw-r--    1 root     system       188416 Jun 28 2024  sm_name_hdr.vc

Is there critical info on those .vc files? is it important to consider their information as part of ODM? 

Are they just temporary files?  

Regards 

Luis A. Rojas Kramer 

Hi Luis

The .vc files are critical and store the variable length fields (vchar) of the ODM class. 

You can run "strings CuAt" and "strings CuAt.vc" for example to see what each contains.

> The ODM odmget command doesn't recognize them as part of ODM, and they could not be queried or reviewed.

odmget reads the .vc file behind the scenes.

# truss odmget CuAt 2>&1 | grep open
kopen("/etc/objrepos/CuAt", O_RDONLY)           = 3
kopen("/etc/objrepos/CuAt.vc", O_RDONLY)        = 3
kopen("/etc/objrepos/CuAt", O_RDONLY)           = 3
kopen("/etc/objrepos/CuAt.vc", O_RDONLY)        = 4

HTH

Chris

Hi experts... 

Does anyone know what the .vc file versions of ODM actually do ? (CuAt and CuAt.vc, por example) 

What I've researched about them (besides "don't touch them or you'll be fired") is that these files are named according to their "variable character" or vchar content, and every time we use odmadd, odmcreate, odmdelete, and other ODM commands, information is entered into those files.

The ODM odmget command doesn't recognize them as part of ODM, and they could not be queried or reviewed.

You may notice that many of these files are not empty for example, when listing SMIT ODM files:

server /usr/lib/objrepos $ ls -l sm*
-rw-rw-r--    1 root     system       368640 Jun 28 2024  sm_cmd_hdr
-rw-rw-r--    1 root     system       999424 Jun 28 2024  sm_cmd_hdr.vc
-rw-rw-r--    1 root     system      2113536 Jun 28 2024  sm_cmd_opt
-rw-rw-r--    1 root     system      1146880 Jun 28 2024  sm_cmd_opt.vc
-rw-rw-r--    1 root     system       585728 Jun 28 2024  sm_menu_opt
-rw-rw-r--    1 root     system       143360 Jun 28 2024  sm_menu_opt.vc
-rw-rw-r--    1 root     system       143360 Jun 28 2024  sm_name_hdr
-rw-rw-r--    1 root     system       188416 Jun 28 2024  sm_name_hdr.vc

Is there critical info on those .vc files? is it important to consider their information as part of ODM? 

Are they just temporary files?  

Regards 

Luis A. Rojas Kramer