Building EXTRACT, INDEXFILE, and WORKFILE control statements

• The EXTRACT Control Statement panel (EXTRACT CONTROL STATEMENT PANEL) builds control statements to allocate an extract file. Log Analyzer writes all log records that are associated with LUOWs of interest to this file.
• The INDEXFILE Control Statement panel (which is similar to (EXTRACT CONTROL STATEMENT PANEL) to builds control statements to allocate an index file. The Log Analyzer ISPF interface uses this file during interactive analysis of LUOWs.
• The WORKFILE Control Statement panel (which is similar to (EXTRACT CONTROL STATEMENT PANEL) builds control statements to allocate a work file. Log Analyzer uses this file to sort log records that it reads from an input extract file.

For more information, see Specifying-EXTRACT-INDEXFILE-and-WORKFILE-control-statements

To access and work with fileType Control Statement panels

1. Access the Build JCL panel.For instructions, see Accessing-JCL-functions.

2. In the Control Statements field to the left of the EXTRACT, INDEXFILE, or WORKFILE label, enter S.One of the following panels is displayed, depending on which label you selected:

   • EXTRACT Control Statement panel (see (EXTRACT CONTROL STATEMENT PANEL))
   • INDEXFILE Control Statement panel
   • WORKFILE Control Statement panel

   These panels are similar to each other but contain different fields and generate different control statements (based on your entries).

   EXTRACT Control Statement panel

    File  Options  Help                                                          
   -------------------------------------------------------------------------------
   Log Analyzer              EXTRACT Control Statement                           
   Command ===> _________________________________________________________________
                                                                                
   Extract file data set name  . . _____________________________________________  
                                                                                 
   Enter allocation information.                                                  
     SMS Management class  . . . . ________ (For SMS managed data set)            
     SMS Storage class . . . . . . ________ (For SMS managed data set)            
     SMS Data class  . . . . . . . ________ (For SMS managed data set)            
     Volume serial(s)  . . . . . . _______________________________________________
     Generic unit  . . . . . . . . ________                                       
     Space units . . . . . . . . . ___      (TRK or CYL)                          
     Primary quantity  . . . . . . _____    (in above units)                      
     Secondary quantity  . . . . . _____    (in above units)                      
                                                                                 
   The following fields may be specified to model the allocation after            
   an existing data set. They are mutually exclusive.                             
     LIKE data set name (SMS)  . . _____________________________________________  
     DCB data set name (non-SMS) . _____________________________________________

3. In the fileType file data set name field, enter the data set name of the data set to be allocated.This information is used to generate the DSN keyword on the fileType control statement. For more information, see DSN-keyword.

   Note

   This field is not displayed on the WORKFILE Control Statement panel.

4. Provide values in the following data entry fields as required:

    

   Field	Specification
   SMS Management class	Specify the name of the SMS management class to use for the data set to be allocated. This keyword is used to produce the MGMTCLASS keyword on the fileType control statement. For more information, see MGMTCLASS-keyword.
   SMS Storage class	Specify the name of the SMS storage class to use for the data set to be allocated. This keyword is used to produce the STORCLASS keyword on the fileType control statement. For more information, see STORCLASS-keyword.
   SMS Data class	Specify the name of the SMS data class to use for the data set to be allocated. This keyword is used to produce the DATACLASS keyword on the filetype control statement. For more information, see DATACLASS-keyword.
   Volume serial(s)	Specify the name of the volume serial number to use for the data set to be allocated. This keyword is used to produce the VOLSER keyword on the fileType control statement. For more information, see VOLSER-keyword.
   Generic unit	Specify the unit type to use for the data set to be allocated. This keyword is used to produce the UNIT keyword on the EXTRACT control statement. For more information, see UNIT-keyword. This field is not valid for the INDEXFILE control statement.
   Space units	Specify whether to allocate space in cylinders or tracks. This keyword is used to produce the SPACEUNITS keyword on the fileType control statement. For more information, see SPACEUNITS-keyword.
   Primary quantity	Specify the amount of primary space to use for the data set to be allocated. This keyword is used to produce the PRISPACE keyword on the fileType control statement. For more information, see PRISPACE-keyword.
   Secondary quantity	Specify the amount of secondary space to use for the data set to be allocated. This keyword is used to produce the SECSPACE keyword on the fileType control statement. For more information, see SECSPACE-keyword.
   LIKE data set name (SMS)	Specify the data set name of a data set to use as a model for allocation of a new extract data set as an SMS-managed data set. This keyword is used to produce the LIKE keyword on the EXTRACT control statement. For more information, see LIKE-keyword. This field is not valid for the INDEXFILE control statement.
   DCB data set name (non-SMS)	Specify the data set name of a data set to use as a model for allocation of a new extract data set as a non-SMS-managed data set. This keyword is used to produce the DCB keyword on the EXTRACT control statement. For more information, see DCB-keyword. This field is not valid for the INDEXFILE control statement.