View source for Obtaining User 0 output (CCAPRINT)

==Overview==
<p>
The output from CCAPRINT can help in problem determination by showing parameter or other initialization errors.</p>
<p>
This page explains how to store and print User 0 output using the CCAPRINT system file. </p>

==CCAPRINT data set==
<p>
CCAPRINT defines a sequential output data set (usually <code>SYSOUT=*</code> in z/OS) that contains User 0 output, such as:</p>
<ul>
<li>Summary of the execute parameters, such as <var>SYSOPT</var></li>

<li>Version running</li>

<li>User 0 parameter settings</li>

<li>Number of users and servers</li>

<li>Terminal output, if the commands are issued from the User 0 input stream </li>
</ul>

===Initialization information about Early Warnings===
<p>
At <var class="product">Model&nbsp;204</var> initialization, a listing of all Early Warnings that have been applied to the module is produced. It is comparable to the output of the following command:</p>
<p class="code">DISPLAY EW ALL
</p>
<p>
The output is directed to CCAPRINT in Online, Batch204, IFAM1 (if CCAPRINT has been defined), and IFAM4 jobs. A listing of all maintenance currently applied to the active load module or phase is displayed. Messages of the following type are produced in CCAPRINT, depending on the maintenance history at your site.</p>

====Examples====
<p class="code">NO EARLY WARNINGS HAVE BEEN APPLIED
EARLY WARNING 1 TO 4 APPLIED
EARLY WARNING 6 APPLIED
EARLY WARNINGS 9 TO 12 APPLIED
</p>
<p>
This listing helps [[Contacting Rocket Software Technical Support|Rocket Software Technical Support]] reduce the time required for problem resolution. You should have both CCAPRINT and CCAAUDIT available when you report problems to Rocket Software Technical Support.</p>

===z/OS considerations===
<p>
In a z/OS environment, the JCL must contain a DD statement for CCAPRINT. CCAPRINT is normally defined as a SYSOUT data set. Records written to CCAPRINT go to the system spool. For example:</p>
<p class="code">//CCAPRINT DD SYSOUT=* 
</p>
<p>
If CCAOUT, which is used for problem analysis, is allocated in your UTILJ JCL, journal records are written to CCAOUT, not CCAPRINT. See [[System and media recovery#Using UTILJ to analyze problems|Using UTILJ to analyze problems]] for more details.</p>

===z/VSE considerations===
<p>
In a z/VSE environment, the output from CCAPRINT is printed in the order generated on the logical unit SYSLST. The unit SYSLST must be assigned.</p>

===z/VM considerations===
<p>In a z/VM environment, CCAPRINT can be defined as one of the following:</p>
<ul>
<li>CMS file:
<p class="code">FILEDEF CCAPRINT DISK WORK CCAPRINT A </p></li>

<li>Service machine virtual printer:
<p class="code">FILEDEF CCAPRINT PRINTER </p></li>
</ul>
<p>
Information about unusual <var class="product">Model&nbsp;204</var> activity is displayed on the service virtual machine console. Spooling this console and ensuring that the file is closed and examined on a regular basis may be helpful. </p>
<p class="note"><b>Note:</b>
Do not define a terminal as the output device for CCAPRINT.</p>
<p>
If CCAOUT, which is used for problem analysis, is allocated in your UTILJ JCL, journal records are written to CCAOUT, not CCAPRINT. See [[System and media recovery#Using UTILJ to analyze problems|Using UTILJ to analyze problems]] for more details.</p>

[[Category:System Manager]]
[[Category:Auditing and problem determination]]