In this section: |
Reference: |
In FOCUS, you always reference files by ddname rather than by their fully qualified data set names. Data set names are arbitrary but must conform to your installation's naming standards.
Note: FOCUS supports up to 380 DDNAMEs and a total of 5000 members.
The following is a list of the major files that you will use in FOCUS. These will be discussed in detail in subsequent sections. The files are referenced by ddname and divided into categories:
Required DDNAMEs |
Description |
---|---|
ERRORS |
Contains error messages, help information, National Language error messages, README information, and FOCUS configuration parameters. |
SYSPRINT |
Specifies the normal destination of the run log, messages, and reports. |
SYSIN |
Is the source of the FOCUS command. |
OFFLINE |
Specifies alternate destination for printed reports. |
Application Files |
Description |
---|---|
MASTER |
Master Files. |
ACCESS |
Access Files (Optional except for intelligent partitioning. For information, see the Describing Data manual). |
FOCEXEC |
Stored procedures. |
ddname |
FOCUS data sources and external indices. |
USERLIB |
Library of user programs. |
FOCSTYLE |
FOCUS StyleSheet files. |
FOCCOMP |
Compiled procedures. |
ddname |
Non-FOCUS data sources. |
TTEDIT |
TableTalk sessions. |
FMU |
Window files. |
TRF |
Documentation for window files or window transfer files. |
HOLDSTAT Files |
Documentation and DBA information for extract files. |
WINFORMS |
Winforms used in a MAINTAIN procedure. |
Extract DDNAMEs |
Description |
---|---|
*HOLD |
Contains data saved using the HOLD command. |
*SAVB |
Contains data saved using the SAVB command. |
*SAVE |
Contains data saved using the SAVE command. |
HOLDMAST |
Temporary Master File for FOCUS HOLD files. |
Note: There are also extract files that you must allocate if used: LET, LOG, POST, and Dialogue Manager output files.
Work Files |
Description |
---|---|
STACK |
Used by Dialogue Manager to store FOCUS commands. |
FOCSORT |
Used during sorting. |
FOCSML |
A work area used by the Financial Modeling Language. |
*FOCPOST |
Sequential output file saved using the POST or PICKUP commands. |
REBUILD |
Used by the REBUILD utility. |
TABLTALK |
Used by TableTalk as a procedure. |
*The AS phrase renames asterisk-marked files to allow more than one file of that type in a single session.
You can explicitly allocate files using JCL in your logon procedure or with TSO ALLOCATE commands. Additionally, FOCUS will dynamically allocate certain work and permanent files during a FOCUS session, if they conform to the standard naming conventions (see Dynamically Allocating Files and DYNAM Command).
The JCL needed to operate FOCUS is usually the same and varies only because of local installation conventions. Generally, file allocations are the same for all users and vary only for the particular data files referenced. FOCUS uses a standard set of ddnames that perform specific functions. Their appearance is required in most runs.
The following is an example of JCL for a typical batch run:
//FOCUS EXEC PGM=FOCUS //STEPLIB DD DSN=FOCUS.FOCLIB.LOAD,DISP=SHR //ERRORS DD DSN=FOCUS.ERRORS.DATA,DISP=SHR //SYSPRINT DD SYSOUT=* //OFFLINE DD SYSOUT=* //MASTER DD DSN=MASTER.DATA,DISP=SHR //FOCEXEC DD DSN=FOCEXEC.DATA,DISP=SHR //* FOCUS CAR DATABASE //CAR DD DSN=CAR.FOCUS,DISP=SHR //SYSIN DD * . . FOCUS commands . FIN /*
The JCL shown below is a typical TSO logon procedure for a FOCUS session:
//TSOLOGON EXEC PGM=IKJEFT01,DYNAMNBR=50 //* FOCUS DATASETS //STEPLIB DD DSN=FOCUS.FOCLIB.LOAD,DISP=SHR //ERRORS DD DSN=FOCUS.ERRORS.DATA,DISP=SHR //OFFLINE DD SYSOUT=A //* USUAL TSO LOGON DATASETS FOLLOW
The following is an example of a TSO allocation CLIST:
ALLOC F(MASTER) DA(MASTER.DATA) SHR REUSE ALLOC F(FOCEXEC) DA(FOCEXEC.DATA) SHR REUSE ALLOC F(WINFORMS) DA(WINFORMS.DATA SHR ALLOC F(CAR) DA(CAR.FOCUS) SHR REUSE
Note: These allocation procedures are discussed in more detail in Calling FOCUS Under TSO.
You do not have to explicitly allocate all of your files prior to using them in a FOCUS session. FOCUS will dynamically allocate certain files.
FOCUS will allocate some or all of the following output or work files as temporary data sets during a FOCUS session:
FOCUS automatically allocates many permanent files on an as needed basis as long as they follow the data set naming conventions.
The permanent files that may be dynamically allocated are:
Note:Required Files through Work Files contain summaries of the files used in FOCUS sessions, with descriptions of their functions and information about allocations. Review them carefully, keeping in mind the space requirements of your application. If the amount of space allocated automatically is insufficient, you must make your own allocation before attempting to use the file.
The following files are required by FOCUS:
(FOC000) UNABLE TO LOCATE ERRORS FILE, FOCUS PROCESSING IS UNPREDICTABLE ERROR READING FOCPARM INSTALL FILE.
//SYSPRINT DD SYSOUT=A ALLOC F(SYSPRINT) DA(SYSPRINT.DATA) ALLOC F(SYSPRINT) DA(*)
//SYSIN DD * //SYSIN DD DSN=SYSIN.DATA,DISP=SHR ALLOC F(SYSIN) DA(*)
Once you enter FOCUS, you should not reallocate SYSIN in the foreground.
You do not have to explicitly allocate SYSIN, SYSPRINT, and OFFLINE by means of JCL, ALLOCATE, or DYNAM ALLOCATE commands. However, for the OFFLINE file (OFFLINE default is the terminal), user allocation is normally specified.
Whether or not SYSPRINT or OFFLINE are allocated to the terminal, the active output width is controlled by the LINESIZE or SCRSIZE parameter of the TERMINAL command that is in effect at entry into FOCUS.
Caution: The characteristics of files SYSIN and SYSPRINT are tested only once, at entry into FOCUS. ALLOCATE, DYNAM ALLOCATE, or FREE commands affecting these files must not be issued from within FOCUS. Likewise, altering the terminal LINESIZE or SCRSIZE setting from within FOCUS is not recommended.
|
Information Builders |