4. Operation › 4.8 CA MICS Documentation Conversion › 4.8.6 Exporting DocWebVu › 4.8.6.6 CA MICS Documentation Export Trouble Shooting

4.8.6.6 CA MICS Documentation Export Trouble Shooting

o "I used exportdoc to create a tar file and transmitted it
  to another platform, but the explode utilities can't read
  it."

  Make sure that the utility used to transmit the file sent
  it as binary, with no character translation.  FTP, for
  example, uses a text translation as its default transfer
  mode.

  Additionally, the utility you are using may not support
  the compression used by exportdoc.


o "I used exportdoc to create a tar file, successfully
  transmitted it to another platform, exploded it, then
  hooked it into my web server.  However when I try to view
  the pages, they are really confusing. I get a lot of Z's,
  boxes, and other strange characters, but nothing readable."

  The HTML pages created by DOC2HTML are in EBCDIC character
  set, rather than ASCII that other platforms use.
  Therefore, if the exportdoc file is being moved to a
  platform using ASCII, any text file must first be converted
  from EBCDIC to ASCII before it can be used.

  exportdoc provides an option (-a) that will perform this
  necessary conversion.  See section 4.8.6.3.

o "The graphical portions of the Web page show as a box with
  a red 'x' in it. What is going on?"

  The CA MICS Document Web Viewer requires directory
  $MICSROOT/documents/images. If this does not exist it can
  be copied using the job in sharedprefix.MICS.CNTL(DOCHFSU).

o "I keep running exportdoc and it keeps failing due to lack
  of space."

  There is no solution here except to increase the space
  available.


  Note:  The DIC=N will not include CA MICS Data Dictionary
  in converted documentation.  This can significantly reduce
  the amount of space required for converted guides.