Master Files have the file type MASTER and consist of parameter lists that describe data sources to FOCUS. The description of a FOCUS data source and all data sources it cross-references must be available whenever you refer to the data source. Generally, the description and the data source both reside on the A disk, although descriptions do not have to be on the same disk as the data. In this way, many users may share the same set of Master Files, yet use different data sources.

The Master File and the data source it is describing usually have the same file name. The maximum LRECL for a variable length file is 32756 bytes; for a fixed length file, the maximum length is 32760 bytes. The record format can be fixed or variable. TED can only work with Master Files that consist of fixed or variable-length records up to 160 bytes long.

Note: All disks are searched when a Master File is needed. That is, the standard CMS search order is used (A then B, and so on) until the Master File is found or no more disks exist to be searched.

Access Files for FOCUS data sources have the file type ACCESS. They are optional except for intelligent partitioning of FOCUS data sources. For information, see the Describing Data manual. The maximum LRECL for a variable length file is 32756 bytes; for a fixed length file, the maximum length is 32760 bytes. The record format can be fixed or variable.

Note: All disks are searched when an Access File is needed. That is, the standard CMS search order is used (A then B, and so on) until the Access File is found or no more disks exist to be searched.

Stored procedures can be saved under any CMS file name and file type. They are most conveniently filed under the file type FOCEXEC. Maintain procedures can conveniently have FILETYPE MAINTAIN. For details, see the Maintaining Databases manual. The maximum LRECL for a variable length file is 32756 bytes and for a fixed length file the maximum is 32760. The record format can be fixed or variable. TED can only work with FOCEXECs that consist of fixed or variable-length records up to 160 bytes long.

EXEC procedurename

EX procedurename

EXEC 'procname proctype procmode' 

EX 'procname proctype procmode' 

EX 'filename filetype filemode'

SALES REPORT A

EX 'SALES REPORT'

In CMS, the PROFILE procedure must be named

PROFILE FOCEXEC A

unless the PROFILE option of the EX FOCUS command is used. (See How to Enter FOCUS for more information.) Only the A disk or read-only extensions of the A disk (for example C/A) will be searched. The PROFILE will be executed before control is passed to the terminal.

StyleSheet files can be saved under any CMS file name and have file type FOCSTYLE. The record format is fixed length with LRECL=80. For details, see the Creating Reports manual.

FOCUS data sources contain data written in FOCUS format. FOCUS data sources have a record length of 4096 and a fixed-length record format. XFOCUS data sources have a record length of 16384 and a fixed-length record format. See the Describing Data manual for information about maximum file size and partitioning. Each data source has a file name that matches the name of its Master File, and has a file type of FOCUS. For example, if the data source's Master File is LEDGER MASTER, then the FOCUS data source is LEDGER FOCUS. You can override these defaults with the USE command, a DATASET attribute in the Master File, or an Access File. These techniques are explained in the Describing Data manual.

An external index is a FOCUS file that contains index, field, and segment information for one or more specified FOCUS data sources. The external index is independent of its associated FOCUS data source and is used to improve retrieval performance. In CMS, the external index is automatically defined as a permanent file when it is created using REBUILD.

An MDI is a separate multi-field index file for one or more FOCUS databases. The MDI is independent of its associated FOCUS database and is used to improve retrieval performance. In CMS, the MDI is automatically allocated as a permanent file when it is created using REBUILD.

Since the restriction information for a FOCUS data source is stored in its Master File, you will want to encrypt the Master File in order to prevent users from examining the restriction rules. Only the Database Administrator can encrypt a Master File. If you wish to change restrictions, the process can be reversed using the DECRYPT command to restore the Master File to a readable form. You can add security limitations to existing data sources using the RESTRICT command.

ENCRYPT FILE filename [filetype [filemode]]

ENCRYPT FILE EMPLOYEE

DECRYPT FILE filename [filetype [filemode]]

RESTRICT 
filename [filetype [filemode]] 
filename [filetype [filemode]]
.
.
.
END

RESTRICT
EMPLOYEE
SALES
PROD FOCUS C
END

The FOCUS User-Written Subroutine Library, FUSELIB, contains additional calculation and utility routines.

GLOBAL TXTLIB FUSELIB

The FOCCOMP file contains the output from the COMPILE command. The FOCCOMP file is used to run the compiled MODIFY procedure:

RUN focexecname

filename FOCCOMP

Window files contain the windows, menus, and related information created by Window Painter. There are three types of window files:

• Compiled window files are created automatically when a Window Painter user chooses the Create a new file option, or invokes Window Painter and specifies a window file which does not yet exist. Compiled window files are also created when a window transfer file is compiled by the WINDOW COMPILE command. Compiled window files can be executed by a Dialogue Manager -WINDOW statement, and can be edited using Window Painter.

  Compiled window files are created on the A disk. Once they are created, they can be moved to any other disk. They have a 4096-byte record length and a fixed-length record format.

• Window transfer files are created by selecting the Create a transfer file option from the Window Painter Utilities Menu. Transfer files are uncompiled source code versions of compiled window files; they can be transferred from FOCUS running in one operating environment (for example, CMS) to FOCUS running in another operating environment (for example, UNIX), and then edited to remove or fine tune window features not fully supported in the new environment. Transfer files can be edited using TED or IEDIT. Before they can be executed efficiently by a -WINDOW statement or edited by Window Painter, they must be compiled using the WINDOW COMPILE command.

  When window transfer files are created by mainframe FOCUS Window Painter, they are created on the A disk. When they are transferred from PC/FOCUS, they are transferred to the disk specified in the prior CMS FILEDEF command. Once they are created or transferred, they can moved to any disk. Transfer files have an 80-byte record length and a fixed-length record format.

  The Document the file option of the Window Painter Utilities Menu also creates a file with a TRF-file type. If you need to create both TRF files (a documentation file and a transfer file) for a given compiled window file, be sure to give the two TRF files different file names. Otherwise, the second TRF file will be appended to the first one.

• Window documentation files are created by selecting the Document a file option from the Window Painter Utilities Menu. A documentation file provides a window application developer with detailed information about the windows in a given window file. Documentation files can be edited using TED or IEDIT.

  Window documentation files are created on the A disk. Once they are created, they can be moved to any other disk. They have a an 80-byte record length and a fixed-length record format.

  The Create a transfer file option of the Window Painter Utilities Menu also creates a file with TRF file type. If you need to create both TRF files (a documentation file and a transfer file) for a given compiled window file, be sure to give the two TRF files different file names. Otherwise, the second TRF file will be appended to the first one.

filename FMU

filename TRF

filename TRF

You can use the FOCUS query language to read non-FOCUS data sources. FOCUS can read QSAM, ISAM, VSAM files; IMS, CA-IDMS/DB, ADABAS, MODEL 204 database files; and Teradata, CA-DATACOM/DB, Oracle, and SQL tables.

Non-FOCUS data sources must be defined to the operating system. You can let FOCUS issue default FILEDEF commands for your data sources, provided the files are either comma-delimited (COM) or fixed-format (FIX) files, where every record is a fixed- length, 80-character record. If a comma-delimited or fixed-format file has a record length other than 80, you must issue a FILEDEF.

For VSAM (KSDS or ESDS) files, use the standard DLBL commands to filedef the files prior to entering FOCUS. VSAM files exist only on OS or DOS disks (not on CMS disks). The Master Catalog must be defined. The dsname must be the VSAM cluster name. Use the IDCAMS utility to obtain it. The CMS LISTFILE command cannot be used for this purpose.

A SET command is available to switch the AMODE of the FOCSAM Interface (which reads VSAM and flat files) to 24-bit addressing. The Interface runs in 31-bit mode by default, in order to take advantage of modern operating system architecture. By extension, the Interface also builds 31-bit addresses for VSAM buffers and ACBs. However, some external VSAM buffering packages run in 24-bit mode, and do not recognize 31-bit addresses. The SET AMODE command allows the Interface to be run with these 24-bit programs.

{MVS|CMS} VSAM SET AMODE {24|31}

{MVS|CMS} VSAM SET ?

(FOC1177)  SET OPTIONS - : BUFND = n / BUFNI = n / AMODE = n

LINK VSAMDISK 191 192 R
ACC 192 B
DLBL IJSYSCT B DSN MASTER CAT (VSAM PERM)
DLBL CUST B DSN CUST DATA (VSAM PERM)

DLBL CUST B DSN CUST DATA  (VSAM PERM
DLBL DD1  B DSN CUST PATH1 (VSAM PERM
DLBL DD2  B DSN CUST PATH2 (VSAM PERM

To record output from either the TRACE or ECHO option of MODIFY in a file, you must first define the file.

FILEDEF HLIPRINT DISK fileid (RECFM recfm LRECL lrecl

CMS FILEDEF HLIPRINT DISK TRACE OUTPUT (RECFM F LRECL 32)
MODIFY FILE EMPLOYEE TRACE
PROMPT EMP_ID CURR_SAL
IF CURR_SAL GT 50000 GOTO HIGHSAL
ELSE GOTO UPDATE;

CASE UPDATE
MATCH EMP_ID
   ON MATCH UPDATE CURR_SAL
   ON NOMATCH REJECT
ENDCASE

CASE HIGHSAL
TYPE
   " "
   "YOU ENTERED A SALARY ABOVE $50,000"
   " "
PROMPT CURR_SAL.PLEASE REENTER THE SALARY BELOW.
IF CURR_SAL GT 50000 GOTO HIGHSAL
ELSE GOTO UPDATE;
ENDCASE
DATA

When you save a TableTalk session, a command file and a session file are saved. The command file has file type FOCEXEC and the session file has file type TTEDIT. Both files are created on the A disk. Each file has a fixed- length record format and a record length of 80. You can also edit a previous TableTalk session.

filename FOCEXEC A 
filename TTEDIT A

TABLETALK EDIT [filename]

HOLDSTAT files enable you to include FOCUS DBA information and environmental comments in HOLD and PCHOLD Master Files. You may create your own and specify its file name with the SET HOLDSTAT command or use the HOLDSTAT ERRORS file supplied by Information Builders.

The contents of a HOLDSTAT file are included automatically into HOLD and PCHOLD Master Files when report requests are executed. To include its contents, a HOLDSTAT file must be available and the SET HOLDSTAT command must be specified. For information about the SET HOLDSTAT command, see the Developing Applications manual.

{HOLDSTAT|fn} [MASTER|ERRORS] [fm|A]

$ ===================================================================== $
$      HOLD file created on &DATE at &TOD by FOCUS &FOCREL              $
$              Database records retrieved= &RECORDS                     $
$              Records in the HOLD file = &LINES                        $
$ ===================================================================== $

All of a Maintain procedure's Winforms are contained in a file with the file type WINFORMS. A Maintain procedure's WINFORMS and FOCEXEC files must have the same file name. The maximum LRECL for a variable length file is 32756 bytes; for a fixed length file, the maximum length is 32760 bytes. The record format can be fixed or variable. TED can only work with WINFORMs that consist of fixed or variable-length records up to 160 bytes long. When searching for WINFORMS files, FOCUS uses the standard CMS search order.

Users create and edit Winforms using the Winform Painter. Users should make changes to WINFORMS files using the Painter only, and should not attempt to edit them directly. All changes made outside the Painter are lost the next time the file is edited in the Painter.