18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TIP<br />

Glossary<br />

The <strong>OS</strong> <strong>2200</strong> environment in which transaction processing applications are created <strong>and</strong><br />

maintained. The TIP system is integrated with the Exec.<br />

TIP common data bank file (TCDBF)<br />

An FCSS file that the administrator can set up to hold tables of static data. When the file<br />

is registered as a TCDBF, a copy of it is moved into main storage as a common bank, <strong>and</strong><br />

any application program can reference it.<br />

TIP file<br />

A file reserved for TIP within a TIP/Exec file using the TFUR or FREIPS utility. Users can<br />

create a TIP file as a permanent, temporary, or scratch file. A permanent file can be a<br />

simplex or duplex file. At creation time, the user must define a TIP file as a TIP (FCSS)<br />

file, UDS/TIP file, or Freespace file.<br />

• UDS/TIP file: A permanent TIP user file that users access <strong>and</strong> maintain through UDS.<br />

The FREIPS utility is used to set up TIP user files as UDS/TIP files, with DMS <strong>2200</strong><br />

area numbers. The DMS <strong>2200</strong> areas are numbered downward from the upper end of<br />

the range of TIP file numbers.<br />

• duplex TIP file: A permanent TIP file with two identical legs (copies) that reside in<br />

two separate TIP/Exec files on separate (but identical) devices. At creation time, you<br />

define a file as either a simplex file or a duplex file. Updates to one leg of the file are<br />

automatically made to both legs of the duplex file.<br />

• Freespace file: A TIP user file in which the user application programs have record<br />

space allocated <strong>and</strong> released as needed by Freespace functions when calling FCSS.<br />

• permanent TIP file: A TIP file set up inside an Exec file for the application database.<br />

This type of file is assigned permanently to TIP, so any transaction program accesses<br />

it quickly, without having to assign it or release it. A permanent TIP file may be a TIP<br />

(FCSS) file, UDS/TIP file, or Freespace file. In the XTC environment, permanent TIP<br />

files can be defined by the site administrator in either the local or the shared TIP<br />

FCSS directory.<br />

• temporary TIP file: A fixed-length TIP (FCSS) file that can be assigned by a<br />

transaction or batch-connect program by means of the FCSS AS function. It remains<br />

in the system until specifically released. Shared TIP files cannot be used for<br />

temporary files.<br />

• scratch TIP file: A fixed-length TIP (FCSS) file that can be assigned by a transaction or<br />

batch-connect program by means of the FCSS AS function. This type of file exists<br />

only for the duration of the execution or connect period, <strong>and</strong> is released<br />

automatically by TIP. It may be released by a TIP file control call before termination<br />

of the execution or connect period. Shared TIP files cannot be used for scratch files.<br />

• simplex TIP file: A permanent TIP file that exists as a single copy in a TIP/Exec file.<br />

• TIP (FCSS) file: A TIP user file with a fixed record structure that is accessed <strong>and</strong><br />

maintained through TIP file control. The TFUR or FREIPS utility is used to set up a<br />

TIP (FCSS) file.<br />

TIP file control<br />

An Exec component that h<strong>and</strong>les the creation <strong>and</strong> maintenance of FCSS <strong>and</strong> Freespace<br />

files <strong>and</strong> access to the files. It is also called TIP file control superstructure (FCSS).<br />

7831 0349–043 Glossary–9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!