When certain FT administration commands are executed, openFT creates self-controlled internal data sets which are required for normal operation (logging file) or which contain diagnostic data (dump and trace files). These data sets must be deleted explicitly (dump files).
When using FTAC, openFT also automatically creates FTAC files in which the data generated and needed by FTAC are stored.
In total, the following internal openFT data sets exist for each openFT instance:
<openft qualifier>.<inst>.SYSRQF
Request queue (DA data set on disk)
<openft qualifier>.<inst>.SYSPTF
Partner list, corresponds to what used to be the network description file (DA data set on disk)
<openft qualifier>.<inst>.SYSOPF
Operational parameters file (DA data set on disk)
<openft qualifier>.<inst>.SYSLOG.Lyymmdd.Lhhmmss etc.
Components of the logging file:
<openft qualifier>.<inst>.SYSLOG.Lyymmdd.Lhhmmss: PS data set
<openft qualifier>.<inst>.SYSLOG.Lyymmdd.Lhhmmss.P00,
<openft qualifier>.<inst>.SYSLOG.Lyymmdd.Lhhmmss.P00.D,
<openft qualifier>.<inst>.SYSLOG.Lyymmdd.Lhhmmss.P00.I: Components of a VSAM cluster
In this example a 7-character openFT qualifier and a 5-character instance name were used. If the openFT qualifier is any longer or shorter, the display of the components can differ from this pattern.
yymmdd is the date (year, month, day) and hhmmss the time (hour, minute, second) when the logging file was created.
Instead of the second level qualifier <inst>.SYSLOG used as a standard, a value specified by the administrator can be used (keyword LOGFILE_2ND_Q in the member PARM of the FT parameter library, see section “Structure of the PARM member”). Note that depending on the length of the openFT qualifier and, possibly, of the "second level qualifier" the timestamps in the log file names are truncated or, in extreme cases, completely omitted.
All FT and FTAC logging records are stored in that file. If the file is deleted or corrupted by individual components being deleted, the logging records are all lost.
If problems occur when the logging file is created or when it is being accessed, openFT cannot be started. (Such problems might arise from there being insufficient storage space or due to access protection for the file; refer to section “Protecting openFT administrative files” for further information on admission protection.) The openFT job log file will contain the following message for example:
FTR0855 OPENFT: No space left on device for internal files
The FT system creates the logging file with the primary allocation, which you specified with the option LOGFILE_SIZE_RC (member PARM in the FT parameter library, see section “Structure of the PARM member”); the value is halved for the size of the secondary allocation. The total size of the logging file depends on the number of logging records is contains. In your role as FT administrator, depending on the volume of requests, you should save the existing logging records from time to time and then delete them from the system using FTDELLOG (see description of the command
FTDELLOG). This preserves contiguous documentation of the logging record over a longer period of time, while at the same time freeing storage space. Note that the allocated file size does not change. The space no longer occupied within the file is simply released again.
We recommend you use the following command from time to time to check to what extent the file contents has been split up:
LISTCAT ENT('<openft qualifier>.<inst>.SYSLOG.P00') ALL
If the file contents is split up to much, performance may deterioration. In that case the file should be reorganized, i.e. a new VSAM cluster with the same characteristics as the existing one should be created and the file contents should be copied using REPRO.
If no further logging records can be written into the logging file because it is full, the openFT instance system automatically deactivates itself (with the internal execution of the command FTSTOP). The openFT job log contains the system message IEC070I (meaning "An error occurred during EOV (end_of_volume) processing for a VSAM data set"). The FT administrator must then first make space available in the logging file by deleting logging records (command FTDELLOG), then the FT system can be reactivated (FJSTART) and FT operation can continue.
<openft qualifier>.<inst>.SYSFSA etc.
Components of the FTAC file (only when FTAC is used):
<openft qualifier>.<inst>.SYSFSA: PS data set
<openft qualifier>.<inst>.SYSFSA.P00,
<openft qualifier>.<inst>.SYSFSA.P00.DATA,
<openft qualifier>.<inst>.SYSFSA.P00.INDEX,
<openft qualifier>.<inst>.SYSFSA.P01,
<openft qualifier>.<inst>.SYSFSA.X01,
<openft qualifier>.<inst>.SYSFSA.X01.DATA,
<openft qualifier>.<inst>.SYSFSA.X01.INDEX: Components of a VSAM cluster
Instead of the second level qualifier <inst>.SYSFSA used as a standard, a value specified by the administrator can be used (keyword FILE_2ND_Q in the member FTACPAR of the FT parameter library, see section “Structure of the member FTACPAR”).
The file contains the FTAC environment, i.e. the admission sets, admission profiles, etc. If the file is deleted or corrupted by individual components being deleted, all admission profiles and admission sets are lost.
If problems occur when the FTAC file is created or when it is being accessed, openFT cannot be started. (Such problems might arise from there being insufficient storage space or due to access protection for the file; refer to section “Protecting openFT administrative files” for further information on admission protection.)
The openFT job log file will contain the following message for example:
FTR0855 OPENFT: No space left on device for internal files
The FT system creates the FTAC file with the primary allocation which you specified in the parameter FILE_SIZE_KB (member FTACPAR of the FT parameter library, see section “Structure of the member FTACPAR”); the value is halved for the size of the secondary allocation.
We recommend you use the following command from time to time to check to what extent the file contents has been split up:
LISTCAT ENT('<openft qualifier>.<inst>.SYSFSA.P00') ALL
If the file contents is split up to much, performance may deterioration. In that case the file should be reorganized, i.e. a new VSAM cluster with the same characteristics as the existing one should be created and the file contents should be copied using REPRO.
If an FTAC command with which data are to be stored in the FTAC file fails (e.g. the command FTCREPRF) because the file is too full, the command is rejected and the following message is issued:
FTC0255 CMD TERMINATED. SYSTEM ERROR
The FT system automatically deactivates itself (with the internal execution of the command FTSTOP). The openFT job log contains the system message IEC070I (meaning "An error occurred during EOV (end_of_volume) processing for a VSAM data set").The FT system only needs to be restarted (FTSTART) in order to continue FT operation. However, before any further information can be stored in the FTAC file, the FTAC administrator must make space available in the FTAC file by deleting admission sets and admission profiles that are no longer required.
The FTAC administrator can find out which admission profiles exist by having them displayed with the command FTSHWPRF. Admission profiles are deleted with the command FTDELPRF.
There is no special command for deleting admission sets. The FTAC administrator deletes an admission set by setting the admission set for the relevant user ID back to the standard admission set (command FTMODADS, with MAX-LEVELS=*STD). This can also be done for user IDs that have already been deleted. The FTAC administrator can find out which user ID have an admission set that differs from the standard admission set with the command FTSHWADS.
<openft qualifier>.<inst>.SYSFDF.Ddddmmmm
openFT dump file (PS data set on disk)
Dump information in this file is written automatically when a serious openFT error is encountered (e.g. protocol infringement, error situations where the messages FTR4024ff are issued, incorrect behavior of an openFT-specific exit routine).
'<openft qualifier>.<inst>.Smddhhmm.Sssccc.Iiii..FTTF'' or
'<openft qualifier>.<inst>.Ymddhhmm.Sssccc.Pnnnnnnn.FTTF'
openFT trace file (FT trace file, PS dataset with ’Undefined’ record format on disk). (see the FTMODOPT command)
Explanations
<openft qualifier> | OPENFT QUALIFIER that was defined using the FJGEN command |
<inst> | Name of the openFT- instance |
ddd | day of the year |
mmmm | minute of the day |
mddhhmm | timestamp in the format month-day-hour-minute (month: 1 = January, |
ssccc | continuation of the timestamp in the format seconds-milliseconds |
iii | index of the server process or 000 for the control process |
nnnnnnn | process ID |
The request file, the partner list, the log file and the FTAC file are set up on the volume specified for this purpose in the PARM member of the FT parameter library (keywords NABVOLUME/NABUNIT). If no specification is made here, these files are set up on the same volume as the trace and dump files. You can define this volume, too, in the PARM member of the FT parameter library (keywords DMP_VOLUME/DMP_UNIT). If no specification is made here either, these files are set up on the volume specified for VOLUME/UNIT in the FJGEN command. The dump and trace files are set up on the volume specified for this purpose in the PARM member of the FT parameter library (keywords DMP_VOLUME/DMP_UNIT). If no specification is made here, the dump and trace files are set up on the volume specified for VOLUME/UNIT in the FJGEN command.