Window Files

In this section:

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


Top of page

x
Compiled Window Files

Compiled window files are members of a PDS. Before they can be created by Window Painter or by the WINDOW COMPILE command, a PDS must be created with LRECL 4096 and RECFM FB, and allocated to ddname FMU.

Once the PDS is allocated, Window Painter and the WINDOW COMPILE command will create compiled window files as required. The member name will be the window file name specified in the Window Painter session or the WINDOW COMPILE command.

Note that creating the PDS is not necessary if you are creating window files to be used only in the same FOCUS session. Window Painter will temporarily allocate the PDS.


Top of page

x
Window Transfer Files and Window Documentation Files

Window transfer files and window documentation files are both members of the same PDS. Before they can be created by Window Painter, the PDS must be created with LRECL 80 to 132 and RECFM FB, and must be allocated to ddname TRF.

Once the PDS is allocated, Window Painter can create window transfer files and window documentation files as needed, and transfer files can be transferred from FOCUS running in other environments as needed. Note that before transferring a file from another operating environment, you will need to allocate a new member in the TRF PDS for it.

The member name for documentation files will be the window documentation file name specified in the Window Painter session. The member name for transfer files will be the window transfer file name specified in the Window Painter session, or the member name specified in the TSO ALLOCATE or DYNAM ALLOCATE command issued prior to the transfer.

Note: Creating the PDS is not necessary if you are creating window transfer files and documentation files to be used only in the current FOCUS session. Window Painter will temporarily allocate the PDS.

If you need to create both a documentation file and a transfer file for a given compiled window file, be sure to create these two files with different names; otherwise, the newer one will be appended to the older one in the PDS.


Top of page

x
Non-FOCUS Data Sources

How to:

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, Millennium, DB2, CA-DATACOM/DB, Teradata, and Oracle tables.

The ddname under which you should allocate the non-FOCUS data source depends on the type of data source. You should allocate QSAM, ISAM, and VSAM files to a ddname that corresponds to a member name in the PDS allocated to ddname MASTER. Database files have their own rules governing ddnames.

Except with QSAM files, FOCUS needs an Interface program to read non-FOCUS data sources. To read some IMS, CA-IDMS/DB, and ADABAS database files, you must also allocate all of the files normally used with these data sources.

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.



x
Syntax: How to Set the VSAM Addressing Mode
{MVS|CMS} VSAM SET AMODE {24|31}

With AMODE 31, FOCSAM builds ACBs and buffers in 31-bit addresses. 31 is the default. With AMODE 24, FOCSAM builds ACBs and buffers in 24-bit addresses.

To determine the addressing mode that is in effect at any time, you can issue the query

{MVS|CMS} VSAM SET ?

which returns the following output:

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

If you are not using any external programs or buffering packages that require 24-bit addresses for the ACB or buffers, you do not need to change the default.


Top of page

x
TTEDIT Files

How to:

When you save a TableTalk session, a command file and a session file are saved. These files are written as follows:

The FOCEXEC and TableTalk session are saved in their respective data sets as the member name you specify in TableTalk.

To save and edit TableTalk sessions, allocate a PDS to the ddname TTEDIT as OLD. An allocation for TTEDIT is not needed if the PDS 'prefix.TTEDIT.DATA' exists. The PDS should have LRECL=80, BLKSIZE=1760, RECFM=FB.

If you omit the file name, a list of all TTEDIT files will be displayed. Include a file name to edit a particular saved TableTalk session.



x
Syntax: How to Edit a Saved TableTalk Session

To edit saved TableTalk sessions, enter the command

TABLETALK EDIT [filename]

where:

filename

Is the CMS file name you specified in the saved TableTalk session. If you omit the file name, a list of all TTEDIT files will be displayed. Include a file name to edit a particular saved TableTalk session.


Top of page

x
HOLDSTAT Files

How to:

Reference:

HOLDSTAT files enable you to include FOCUS DBA information and environmental comments in HOLD and PCHOLD Master Files. Member HOLDSTAT in the distributed library 'prefix.ERRORS.DATA' is the default. Alternately, you may create your own HOLDSTAT or another user-specified member in your ERRORS or MASTER PDSs.

The contents of a HOLDSTAT file are automatically included in HOLD and PCHOLD Master Files when the SET HOLDSTAT command is specified to ON or to a member name. For information about the SET HOLDSTAT command, see the Developing Applications manual.



x
Syntax: How to Specify a HOLDSTAT File

The HOLDSTAT file may exist as a member in the ERRORS or MASTER library:

'prefix.ERRORS.DATA{(HOLDSTAT)|(membername)}'

or

'prefix.MASTER.DATA{(HOLDSTAT)|(membername)}'

where:

prefix

Is the high-level qualifier used at your site.

membername

Is the member name of your customized HOLDSTAT file.

Note: When FOCUS searches for the HOLDSTAT file, the MASTER ddname takes precedence over the ERRORS ddname.

A HOLDSTAT file may contain environmental comments like a file header, or the FOCUS DBA attribute, or both. The supplied HOLDSTAT member contains the following file header with Dialogue Manager system variables:

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

In the HOLD Master File, the comments appear after the FILE and SUFFIX attributes and the DBA information is appended to the end.



x
Reference: Considerations for Creating a HOLDSTAT File

If you create your own HOLDSTAT file, consider the following rules:


Top of page

x
Winform Files

All of a Maintain procedure's Winforms are contained in a member of one or more partitioned data sets allocated to ddname WINFORMS. A Maintain procedure's WINFORMS and FOCEXEC files must have the same member name. 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 files with an LRECL up to 160. When FOCUS needs to access a WINFORMS file, it searches for the ddname WINFORMS. If FOCUS finds that ddname WINFORMS is not allocated, it attempts to allocate the data set 'prefix.WINFORMS.DATA' to ddname WINFORMS. If it does not find the specified member there, FOCUS displays an error message.

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


Information Builders