{"id":1898,"date":"2017-07-11T08:24:28","date_gmt":"2017-07-11T07:24:28","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=1898"},"modified":"2022-12-07T12:59:38","modified_gmt":"2022-12-07T12:59:38","slug":"c_io-exe-batch-file","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/c_io-exe-batch-file\/","title":{"rendered":"How to Use c_io.exe in a Batch File"},"content":{"rendered":"

Why use c_io.exe?<\/h2>\n

Using c_io.exe<\/samp> allows a user to do many things within a project without using the interface and is usually faster.<\/p>\n

Using c_io.exe<\/samp> in a batch file means you can do many things while you are actually away from your desk or in the background. You can then add this batch file to be run by a task<\/a> application during times you are away from you desk or work. This can be handy when needing to do backups of a single or many large databases.<\/p>\n

The executable can import and export everything in a project from single items to the whole project. It can use queries or different options to whittle down the required export. So a user can export all items of a specific type or just one to several items based on a query and or other set options.<\/p>\n

The user can use also use the import to update or create a new Project schema, items, cross references and definitions.<\/p>\n

Import and Export can use the Format Types already saved into the database.<\/p>\n

It can also export just a single frame from a single item into a file of the right type and print diagrams to specific print types.<\/p>\n

How to use c_io.exe<\/h2>\n

The only real difference between using a command prompt and a batch file is the user will need to have a path for the executable. At the beginning of each command line the user will need \u201c%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe\u201d<\/p>\n

As in commandline code, a user will require the correct login information and the project being logged into.
\n-login <username>,<password>,<projectcode><\/p>\n

For example:<\/p>\n

-login admin.ADMIN.demo<\/samp><\/p>\n

As long as the -login user has the correct privileges, they can use c_io.<\/p>\n

Different Options in c_io.exe<\/h2>\n

Required options are:<\/p>\n

-export<\/samp><\/p>\n

\"Export
Export Options for c_io.exe<\/figcaption><\/figure>\n

-import<\/samp><\/p>\n

\"c_io
Import options for c_io.exe<\/figcaption><\/figure>\n

-getframe<\/samp><\/p>\n

\"Options
The options for getframe in c_io.exe<\/figcaption><\/figure>\n

-printdiag<\/samp><\/p>\n

\"printdiag
The printdiag options in c_io.exe<\/figcaption><\/figure>\n

Without any of the previous options, c_io.exe will put up the Information page or an error.<\/p>\n

Helpful other c_io options<\/h2>\n

There are several helpful options especially when using in a batch file.<\/p>\n

-log<\/strong> allows a user to specify a name for a log. This is the log that will have the details of the actions performed during the\u00a0 import.<\/p>\n

-noldap<\/strong> allows users to bypass using LDAP when running a command line or batch file.
\n-errorstack<\/strong> option is for logging any issues with the import<\/p>\n

 <\/p>\n

“%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe” -login admin,ADMIN,demo -export “C:\\Temp\\all3.exp” -type all -noldap -errorstack -log “C:\\Temp\\all4_log.log”
\n“%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe” -login admin,ADMIN,demo -export “C:\\Temp\\pdb3.exp” -type pdb -noldap -errorstack -log “C:\\Temp\\pdb3_log.log”<\/p>\n

Options not used within a batch file<\/h2>\n

A few of the options are not used in a batch file but are in a command prompt. The reason is that they are only used in a command prompt is that they show pop ups with information on them.<\/p>\n

-verbose<\/strong> lets the user know that c_io.exe has finished
\n-ver<\/strong> lets the user see what the version number, date and time of the build they are using.
\n-help<\/strong> is used to see all the command line options.<\/p>\n

Batch Files from Project Phase<\/h2>\n

Batch files can be added into the Project Phases, this is done by going to “Project Setup”, and in Options selecting “Project Phases”. Inside here if you create a new Process and change the type to command, in Command navigate to your .bat file.<\/p>\n

\"A
Command phase node to run batch filesArticle Updated 04\/02\/2019 – Added infor on running batch file from phase sidebar<\/figcaption><\/figure>\n