OPSLOG WebView stores several types of files in your HFS or zFS in compatibility mode. Some of these files are distributed in binary format, and some are distributed in EBCDIC. Some examples are:
|
File type |
Code |
|
.html |
EBCDIC |
|
.jpg |
binary |
|
.png |
binary |
|
.gif |
binary |
|
.js |
EBCDIC |
|
.css |
EBCDIC |
By default, HTTPD treats files as ASCII. However, by using the Addtype configuration statement in the HTTPD configuration file, you can override the ASCII default. Many sites configure .html files to be EBCDIC coded. You can explicitly associate a file type to ASCII too, and although it is not necessary to do so, the explicit assignment serves to inform other maintainers of the configuration file that the file type is already in use.
It is possible that the character sets we have used to define WebView-related files could differ from the file formats used by other software that is already installed at your site. The .js (Java Scrip) and .css (Style Sheet) are the most vulnerable. If any of the OPSLOG WebView help files are in a different format than that already in use by other software, the most convenient fix is to translate the new OPSLOG WebView help files from EBCDIC to ASCII. You can do this by using FTP to transfer the file to a PC with conversion from EBCDIC to ASCII, then resending the file to the host as a binary format file. This establishes an ASCII instance of the file on your mainframe system. We recommend renaming and saving the EBCDIC version of the file for easy reference to its contents. You may have other ways to convert files to ASCII.
Files that are binary in nature, such as .png files, are neither ASCII nor EBCDIC. They are binary, and should be transmitted as such.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|