SirAud invocation: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (combine two pages)
 
m (1 revision: SirAud pages)
(No difference)

Revision as of 23:00, 10 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, you should 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 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.

See also