{"id":1945,"date":"2017-08-10T11:16:18","date_gmt":"2017-08-10T10:16:18","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=1945"},"modified":"2022-10-07T16:31:33","modified_gmt":"2022-10-07T15:31:33","slug":"exporting-single-item-frame-getframe-c_io-exe","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/exporting-single-item-frame-getframe-c_io-exe\/","title":{"rendered":"Exporting a Single Item Frame using ‘getframe’ with c_io"},"content":{"rendered":"

Exporting<\/h2>\n

A user can export a single item’s text<\/em> or binary<\/em> frame and place it in a file using getframe<\/em>. A batch file is great for this as a user can use copy and paste the same command line numerous times,\u00a0 replacing the identity for each line. Then when run, all the frames will be quickly exported.<\/p>\n

The start of this command line is the same as for all main options, using the path<\/em> and login<\/em> details.<\/p>\n

The -getframe<\/strong> options are as follows:<\/p>\n

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

-getframe<\/strong> option sets the frame name to be output for the first item that matches the query or identity (if used).<\/p>\n

-file<\/strong> sets the name and location of the file to be output<\/p>\n

-query<\/strong> option sets the query to be used<\/p>\n

-qloc<\/strong> sets the location of the -query<\/strong> option
\n<\/strong><\/p>\n

-identity<\/strong> over rides any set within the used query<\/p>\n

c_io.exe Batch File GetFrame Examples<\/h3>\n
\"%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe\" -login admin,ADMIN,demo -getframe NOTES -file \"C:\\Temp\\notes.txt\" -query \"Req - All\" -qloc automatic<\/pre>\n
Using -identity<\/h3>\n
\"%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe\" -login admin,ADMIN,demo -getframe TEXT -file \"C:\\Temp\\REQ-2_TEXT.txt\" -query \"Req - All\" -qloc automatic\u00a0 -identity \"REQ-2\"\r\n\r\n\"%CRADLEHOME%\\bin\\exe\\windows\\c_io.exe\" -login admin,ADMIN,demo -getframe PICTURE -file \"C:\\Temp\\REQ-9_PIC.jpg\" -query \"Req - All\" -qloc automatic\u00a0 -identity \"REQ-9\"<\/pre>\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
\"%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\"\r\n\r\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\" -verbose<\/pre>\n
Options not used within a batch file<\/h2>\n
There are a couple of options that are not used in a batch file. The reason is that they are only useful in a command line, in a command prompt as they show pop ups with information on them.<\/p>\n
-ver<\/strong> lets the user see what the version number, date and time of the build they are using.
\n-help<\/strong> option allows a user to see the command line options.<\/p>\n
Links to Other Batch File Options<\/h2>\n
Read Publishing a Formal Document Using a Batch File<\/a> article for information of formal documentation.<\/p>\n
Details of importing can be read in Importing Using c_io in a Batch File<\/a><\/p>\n
 <\/p>\n