Documents stored in a CA View repository must be self-contained. A self‑contained document is a document that has no external dependencies. For example, if a Word document contains links to an Excel spreadsheet, that document contains external dependencies and is not self-contained. To maintain integrity when the file is viewed after storage, remove any external links or transfer them with the source document in a zip format.
After the files are transferred to the CA View repository, the report ID is determined by the source file name or by the LPDDEST FNAME parameter specification, or both.
No validation is performed on the distributed files, specifically the file names that are being sent and stored on the CA View database. The standards that are currently implemented at your site regarding security and report retention may not be easily enforced with the storage of distributed files. To ensure that your existing CA View environment is not impacted by the implementation of this solution, we recommend that you store the distributed files in a separate database. It may also be necessary to develop new site standards regarding file-naming conventions to enforce the security rules that limit file access for each group of users that stores distributed file types in the CA View database.
Distributed files stored in the CA View database cannot be indexed, viewed, or printed from a 3270 terminal.
The creation date for a distributed file stored in the CA View database is its archive date, not the original date of the file.
Distributed files cannot be bundled or processed through CA Deliver.
There is no concept of pages and lines with these files. CA View displays the file size in place of the page and line counts. Page indexing is not available.
After the distributed file types are stored in the CA View database, they are treated the same as all other report files in terms of back up utilities, security, ERO retention, and EAS processing.
