Find How Full Top Secret Files Are?
Article ID: 193373
Updated On:
Products
Top Secret
Top Secret - LDAP
WEB ADMINISTRATOR FOR TOP SECRET
Issue/Introduction
Is there a way to tell how full a Top Secret file/dataset is and find out the file utilization for the following files:
AUDIT
BACKUP
CPFRCVY
RECOVERY
SECFILE
Environment
Release : 16.0
Component : CA Top Secret for z/OS
Resolution
** The AUDIT and RECOVERY files are wrappable files, meaning when they fill up, new data is written at the beginning of the file, overlaying the previous data. A TSS message is issued when each file wraps.
TSS9209I AUDIT FILE HAS WRAPPED
TSS9011W RECOVERY FILE WRAPPED AROUND
If using 2 audit files, when 1 fills up, it switches to the other audit file to write new data and the following message is issued:
TSS9203I SWITCHED TO AUDIT/TRACKING OUTPUT FILE dddddddd
** The TSSCPR utility can be used to report on the CPFRCVY file. The CPF Recovery File saves transmitted commands until a response is received from a remote machine. Only commands selecting or defaulting to WAIT(NO) are saved for re-transmission. Commands targeted only for the local machine are not saved.
When a TSS command with WAIT(NO) is entered CPF saves a command image on the CPF Recovery File before transmitting it over the link. When a response from the remote is returned CPF deletes the command from the file. If the response is not received CPF scans the Recovery File at the resumption of service and select all commands not responded and retransmits them. When a response is received, the command(s) are deleted from the file.
Ideally the CPFRCVY file should be empty. There have been instances where commands are left in the CPF recovery file. To check this, run the TSSCPR utility. See member TSSCPR in the TSS r16 CAKOJCL0 library for sample jcl. This utility will list what is in the CPF recovery file.
If the TSSCPF utility shows commands in the CPFRCVY file, columns 149-158 in the TSSCPR output show the date the command was issued on the local node. If the dates are very old, these commands are probably orphaned and can be cleared via:
TSS REMOVE(*CPFRECV) CPFNODE(node) or
TSS REMOVE(*CPFRECV) UNTIL(mm/dd/yy), which will delete all records up to, and including, the specified date.
** The SECFILE and BACKUP files are divided into segments. To find how full each segment is, run TSSFAR with SFSTATS. The output will have:
- Acid index entries allocated: nnnnnn Acid index entries defined: nnnnnn
This is for the acid index. ‘Acid index entries allocated’ minus ‘Acid index entries defined’ tells you how many more new acids can be defined.
- Volume entries allocated: nnnn % Used nnn
- RES Blocks allocated: nn % Used nnn
- PIE Blocks allocated: nnn % Used nnn
- MLS Blocks allocated: nnn % Used nnn
- SDT Blocks allocated: nnn % Used nnn
These are for the VOLUME, RESBLOCKS, PIEBLOCKS, MLSBLOCKS, and SDTBLOCKS segments and what percentage of each segment is in use. (These values are defined when the security file is allocated.)
TSS9209I AUDIT FILE HAS WRAPPED
TSS9011W RECOVERY FILE WRAPPED AROUND
If using 2 audit files, when 1 fills up, it switches to the other audit file to write new data and the following message is issued:
TSS9203I SWITCHED TO AUDIT/TRACKING OUTPUT FILE dddddddd
** The TSSCPR utility can be used to report on the CPFRCVY file. The CPF Recovery File saves transmitted commands until a response is received from a remote machine. Only commands selecting or defaulting to WAIT(NO) are saved for re-transmission. Commands targeted only for the local machine are not saved.
When a TSS command with WAIT(NO) is entered CPF saves a command image on the CPF Recovery File before transmitting it over the link. When a response from the remote is returned CPF deletes the command from the file. If the response is not received CPF scans the Recovery File at the resumption of service and select all commands not responded and retransmits them. When a response is received, the command(s) are deleted from the file.
Ideally the CPFRCVY file should be empty. There have been instances where commands are left in the CPF recovery file. To check this, run the TSSCPR utility. See member TSSCPR in the TSS r16 CAKOJCL0 library for sample jcl. This utility will list what is in the CPF recovery file.
If the TSSCPF utility shows commands in the CPFRCVY file, columns 149-158 in the TSSCPR output show the date the command was issued on the local node. If the dates are very old, these commands are probably orphaned and can be cleared via:
TSS REMOVE(*CPFRECV) CPFNODE(node) or
TSS REMOVE(*CPFRECV) UNTIL(mm/dd/yy), which will delete all records up to, and including, the specified date.
** The SECFILE and BACKUP files are divided into segments. To find how full each segment is, run TSSFAR with SFSTATS. The output will have:
- Acid index entries allocated: nnnnnn Acid index entries defined: nnnnnn
This is for the acid index. ‘Acid index entries allocated’ minus ‘Acid index entries defined’ tells you how many more new acids can be defined.
- Volume entries allocated: nnnn % Used nnn
- RES Blocks allocated: nn % Used nnn
- PIE Blocks allocated: nnn % Used nnn
- MLS Blocks allocated: nnn % Used nnn
- SDT Blocks allocated: nnn % Used nnn
These are for the VOLUME, RESBLOCKS, PIEBLOCKS, MLSBLOCKS, and SDTBLOCKS segments and what percentage of each segment is in use. (These values are defined when the security file is allocated.)
Feedback
Yes
No
Powered by
