SirAud invocation: Difference between revisions
m (1 revision: SirAud pages) |
m (misc cleanup) |
||
| Line 15: | Line 15: | ||
// | // | ||
</nowiki></p> | </nowiki></p> | ||
<p class="note"><b>Note:</b> If you use any of the report selection parameters, | <p class="note"><b>Note:</b> If you use any of the report selection parameters, omit the various report DD statements, excepting <code>SYSPRINT</code>. | ||
See [[SirAud parameters#allpr|ALLPR and NOPR]] for a discussion of the report selection parameters. | See [[SirAud parameters#allpr|ALLPR and NOPR]] for a discussion of the report selection parameters. | ||
</p> | </p> | ||
==Running SirAud under CMS== | ==Running SirAud under CMS== | ||
A simple SIRAUD EXEC is provided to run <var class="product">SirAud</var>. | A simple <code>SIRAUD</code> EXEC is provided to run <var class="product">SirAud</var>. | ||
You must first issue a FILEDEF command for the JOURNAL file. | You must first issue a FILEDEF command for the <code>JOURNAL</code> file. | ||
You may want to insert a JOURNAL FILEDEF to identify the <var class="product">Model 204</var> journal file, or you | You may want to insert a <code>JOURNAL FILEDEF</code> to identify the <var class="product">Model 204</var> journal file, or you | ||
may want to issue EXEC SIRAUD from a "wrapper" that contains the FILEDEF command for JOURNAL. | may want to issue <code>EXEC SIRAUD</code> from a "wrapper" that contains the FILEDEF command for <code>JOURNAL</code>. | ||
<var class="product">SirAud</var> parameters are specified as options to SIRAUD EXEC | <var class="product">SirAud</var> parameters are specified as options to the <code>SIRAUD</code> EXEC or as SYSIN file records (see [[SirAud#sysin|SYSIN]]). | ||
or as SYSIN file records (see [[ | Unlike the MVS JCL <code>PARM=</code> field, you do not specify an | ||
Unlike the MVS JCL PARM= field, you do not specify an | equal sign (<tt>=</tt>) between a parameter and the value you are specifying. | ||
equal sign (=) between a parameter and the value you are specifying. | |||
For example: | For example: | ||
<p class="code" | <p class="code">SIRAUD (NFILES 10 NOSUBREPT | ||
</p> | |||
If you do not want to use the SIRAUD EXEC that is distributed with the product, | If you do not want to use the <code>SIRAUD</code> EXEC that is distributed with the product, <var class="product">SirAud</var> must be invoked by the <var class="product">Model 204</var> CMS interface, because | ||
<var class="product">SirAud</var> must be invoked by the <var class="product">Model 204</var> CMS interface, because | |||
it uses the CMS interface's QSAM/BSAM simulation. | it uses the CMS interface's QSAM/BSAM simulation. | ||
The program name of <var class="product">SirAud</var> as distributed is <code>SIRAUD</code>. | The program name of <var class="product">SirAud</var> as distributed is <code>SIRAUD</code>. | ||
<p class="note"><b>Note:</b> Because <var class="product">SirAud</var> uses the <var class="product">Model 204</var> CMS interface, any file | <p class="note"><b>Note:</b> Because <var class="product">SirAud</var> uses the <var class="product">Model 204</var> CMS interface, any file | ||
can be on an OS format minidisk. | can be on an OS format minidisk. | ||
</p> | </p> | ||
Revision as of 19:18, 12 October 2016
Running SirAud under MVS
The following JCL will run SirAud under MVS:
//SIRAUDJ JOB (0),MSGCLASS=A,CLASS=A,NOTIFY=ME //SIRAUD EXEC PGM=SIRAUD,PARM='NFILES=10' //STEPLIB DD DSN=SIRAUD.LOAD,DISP=SHR //JOURNAL DD DSN=M204.CCAJRNL,DISP=SHR //SYSPRINT DD SYSOUT=A //* Omit following if reports selected by PARM: //PERFREPT DD SYSOUT=A //FILEREPT DD SYSOUT=A //PROCREPT DD SYSOUT=A //SUBREPT DD SYSOUT=A //UTBLREPT DD SYSOUT=A //UTBLSUMM DD SYSOUT=A //
Note: If you use any of the report selection parameters, omit the various report DD statements, excepting SYSPRINT.
See ALLPR and NOPR for a discussion of the report selection parameters.
Running SirAud under CMS
A simple SIRAUD EXEC is provided to run SirAud.
You must first issue a FILEDEF command for the JOURNAL file.
You may want to insert a JOURNAL FILEDEF to identify the Model 204 journal file, or you
may want to issue EXEC SIRAUD from a "wrapper" that contains the FILEDEF command for JOURNAL.
SirAud parameters are specified as options to the SIRAUD EXEC or as SYSIN file records (see SYSIN).
Unlike the MVS JCL PARM= field, you do not specify an
equal sign (=) between a parameter and the value you are specifying.
For example:
SIRAUD (NFILES 10 NOSUBREPT
If you do not want to use the SIRAUD EXEC that is distributed with the product, SirAud must be invoked by the Model 204 CMS interface, because
it uses the CMS interface's QSAM/BSAM simulation.
The program name of SirAud as distributed is SIRAUD.
Note: Because SirAud uses the Model 204 CMS interface, any file can be on an OS format minidisk.