Knowledge Article

Article Number

000404677

Old Article Number

Article Type

FAQ/Procedural

Title

ISPW - Documentation Types

Summary

Included within are just some examples of Documentation Types that may be requested by Support and/or Engineering, to help solve your issue.

Product

BMC Compuware ISPW Base System

Component

BMC Compuware ISPW Base System

Applies to

All end users and / or ISPW Administrators that are trying to collect logs, outputs, inputs, etc... to try and diagnose or solve an ISPW Base issue.

Question

Which are some ISPW - Documentation Types might be used to assist in collecting ISPW Documentation files, in an efficient and accurate way?

Answer

ISPW - Documentation Types

Further below are just some examples of Documentation Types that may be requested by Support and/or Development, to help solve your issue. For this article, we will only be outlining z/OS Documentation Types. Non-mainframe types, like *.txt, *.mp4, *.log, *.jpg, *.png, *.docx, etc… are fairly self-explanatory, and can easily be attached right from your PC to a case.

First, a good practice is to determine where a particular type resides or is derived from. For example, the CM started task and its log, reside and are derived from z/OS (the mainframe). This can be important when deciding later how to capture the documentation in the best way. A good practice when dealing with z/OS (mainframe) documentation, is that… if it derives from z/OS, then capture it in a way that it can be easily restored on z/OS. In some cases, there is no other choice but to provide the documentation in a format that can be restored on z/OS. However, when this is ‘optional’, it is still a better to capture files in a way that they can easily be restored and viewed in the same environment that they came from. An example of something that is ‘optional’ is a text log, being downloaded to the PC as ASCII, and then named with a *.txt naming. There are other examples as well. In this set of articles, we show how they can be collected in ways that retain their original formats, as they were written to z/OS and in a way that ensures the integrity of the documentation when it is restored.

Attachment(s):