The file size in T24 grows with the data. In some cases we might not need the data anymore, we can remove the unwanted data and free up the space. Even though the data is deleted, the file size might remain the same. We should find a way to handle such scenarios. This blog gives a few tips about file resizing and maintenance.
Identify the badly sized files
· CHECK.T24.FILES should be placed in the local BP.
· Compile and catalog the routines.
· Create PGM.FILE with record name as CHECK.T24.FILES.
· Create a BATCH record with the ID name as BNK/CHECK.T24.FILES.
· Create a TSA.SERVICE record with ID name as BNK/CHECK.T24.FILES.
· Run the CHECK.T24.FILES subroutine as a service.
· After completing the service, the records will be written under &SAVEDLISTS& directory.
Resizing the files
There is a utility in jBASE by name jrf which can be used to resize files in jBASE.
The following steps helps you in resizing files:
Use jrf with -Rv option to check if a file needs resizing. '-Rv'
(This Option will only report and will not resize the file.)
Example:
jsh->jrf -Rv F.HOLD.CONTROL
If the output shows something like this:
Downsizing skipped from modulo xx to xx. (where 'xx' is a numeric value)
Then do: jsh-->jrf -Dv F.HOLD.CONTROL
This will downsize the file. This can be checked with a subsequent
But if jrf -Rv output shows something like the below:
Resize from xx to nn. (where 'xx' and 'nn' are numeric value)
Then do: jsh-->jrf -Snnv F.HOLD.CONTROL
Where 'nn' is the target modulo as given by the output of jrf -Rv.
This will resize the file. This can be checked with a subsequent jrf -Rv.
Try jrf -h for more details.
Note: Replace xxx with Company Mnemonic.
Reducing the size of the bnk.run directory
To reduce the size of the bnk.run kindly use the appropriate methods for &HOLD&, &COMO&, &PH&, EXCEPTION.LOG.FILES, OFS.REQUEST.DETAIL, PROTOCOL files.
Maintenance of &COMO& directory
&COMO& directory inside bnk.run will contain log files which will be having the details like COB logs and upgrade and UPDATE logs etc.
This directory is not cleared by the system and hence the size of the directory will grow periodically. The ID of the como files generated by COB will be in the format ‘tSA_3_20110901_03-04-10”. These como files can be moved from one environment to another.
In order to reduce the size of &COMO& directory, &COMO& directory should be cleared manually based on the requirement, after taking a backup.
How frequently should we resize?
The frequency of resizing really depends on the database’s growth. Start with a weekly resize procedure and over a while, you will arrive at the right frequency to resize files, i.e. weekly, fortnight,y or monthly. Monthly resize is an absolute minimum requirement.
What is the preferred way to resize files in T24 with jBase 5 and R7?
Resizing can be done through standard enquiry in Globus called EB.BAD.SIZE.FILES. Kindly run this Enquiry ENQ EB.BAD.SIZE.FILES. When this enquiry runs, it will ask for "Gather New File Size Information?" The User has to enter either FULL or FAST. The FULL option will keep a count of records in each file but FAST will not do the count on the records hence the FAST option will be quicker than the FULL.
During resizing of jbase files using RESIZE.GLOBUS, the system prompts a "probably in use" message, and the file was not resized
File resizing is a downtime activity that should be performed when NO users are logged in to the system.
Hence kindly execute RESIZE.GLOBUS when all the USERs are logged off.
This should resolve the problem.
JR files Resizing
1.) Back up the J4 (both data and dict parts) file before converting.
2.) From jsh prompt, execute the below:
jsh--> jrf –H6 <J4_FILE_NAME>
3.) Now check the below to make sure the file has been converted successfully to JR type.
jsh--> jstat -v <FILE_NAME>
How frequently should archiving be done?
The Frequency of archiving really depends on the database growth. For sites with large volumes, suggest that this is a monthly exercise. Suggest that the retention period is kept to an absolute minimum requirement. For e.g. if you require the FT data only for the past 1 month, then please keep it only for the past month. Start archiving as soon as you go live to keep the peak performance of your system. If you are on jbase, please do not forget to resize your files after archiving.
Keep up the great work! Happy Performance Engineering!
Comments