The Work File Label Definition tool is an easy-to-use interface for DBAs to use to set up the Job Control Language (JCL) label definition statements needed by Control Center for the DBSPACE Reorganization and Analysis utilities. The JCL is stored in the SQMWORK file and is used during job submission to create the JCL for the batch job.
Note that work files are not actually defined until the first time they are used in a Control Center job. If another application uses an area first, the Control Center job will be cancelled.
When Option 4 is chosen from the Control Center main menu, the screen shown in Figure 13 is displayed. This is also the screen that is presented when the CICS transaction SQFM is entered directly.
Figure 13. Work File Label Definition Screen
|
|+--------------------------------------------------------------------------------+ || mm/dd/yyyy CONTROL CENTER hh:mm:ss | ||*----------------------- WORK FILE LABEL DEFINITION -----------------------* | ||| | | ||| OPTION => 1 (DEFINE WORK FILE ) | | ||| | | ||| ************************************************************************** | | ||| | | ||| FILE TYPE => (1=DATA 2=DDL ) | | ||| (3=PACKAGES 4=MESSAGES ) | | ||| | | ||| FILE/PARTITION => FILE TYPE 1 - 2 : FILE SIZE NUMBER | | ||| NUMBER FILE TYPE 3 : PARTITION NUMBER | | ||| FILE TYPE 4 : NOT USED | | ||| | | ||| TLBL FILE-ID => | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||*----------------------------------------------------------------- SQC03 ----* | || | ||PRESS ENTER TO PROCESS | ||ENTER F1=HELP F3=EXIT | |+--------------------------------------------------------------------------------+
This screen allows you to enter the parameters that identify the work file labels you want to define or update. There is one option available - Define Work File.
There are 2 types of work files that may be defined:
Data work files are used by the |DBSPACE Reorganization, DBSPACE Analysis, and Table |Reorganization tools to hold data unloaded from the DBSPACE using the DBSU UNLOAD DBSPACE command. Data work files may be defined as either:
DDL work files are used by the DBSPACE Reorganization and DBSPACE Analysis tools to hold DDL generated from the database by SQB01, the Control Center batch DDL generation program. DDL work files are always stored on disk.
To define a tape work file label, leave FILE TYPE and FILE NUMBER BLANK and only enter a 1 to 17 character FILE ID and press ENTER. The TAPE WORK FILE LABEL DEFINITION will be displayed; |see Figure 13. Remember that tape may only be used for data work files.
|Defining disk files is more involved. Because disks do not |have the same capacity as tapes, file size becomes important. The |FILE/PARTITION NUMBER field is used to identify small (1), medium (2), and |large (3) DDL and DATA work files. If you define only one set of disk |work files, we suggest you choose file number 2 because that is the default |value on the screens.
When defining a package work file, the field is used to enter a partition number (job class) in which the View Package job stream will run; valid values are 0-9 and A-Z. These two types of values share the same inut field on the screen.
|As an example, if the user wants to define a medium-size disk DATA |work file, the FILE TYPE would be 1 (DATA) and the FILE NUMBER would be 2 |(medium). The file name (and JCL) will be generated as file name |SQMDAT2 with file identifier as SQLMSTR.DATA.FILE2. The |actual size of the files defined is entered on the next screen and depends on |the DBA's estimates of the needed space. (See Chapter 4, DBSPACE Reorganization Tool for an explanation of how you can combine a disk dataset for |the DDL and a tape dataset for the DATA.)