Information Systems:Analyzing disk usage on Bart - Revision history

Norwinu at 20:48, 1 June 2017

2017-06-01T20:48:31Z

Norwinu: /* RTVDSKINF */

2017-06-01T19:58:35Z

RTVDSKINF

Norwinu at 19:45, 1 June 2017

2017-06-01T19:45:59Z

Norwinu: /* RTVDSKINF */

2017-06-01T19:45:18Z

RTVDSKINF

Norwinu: /* Tools */

2017-06-01T19:44:20Z

Tools

Norwinu at 19:41, 1 June 2017

2017-06-01T19:41:05Z

Norwinu at 19:22, 1 June 2017

2017-06-01T19:22:27Z

Norwinu at 19:21, 1 June 2017

2017-06-01T19:21:24Z

Norwinu: /* Overview */

2017-06-01T19:19:34Z

Overview

Norwinu: Created page with "=Overview= It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint. This article documents the..."

2017-06-01T19:18:40Z

Created page with "=Overview= It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint. This article documents the..."

New page

=Overview=

It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint. This article documents the different methods and tools that can help in such an analysis.

=Observations and other notes=
For the same BRMS job (or more accurately, for the same list of objects specified by the job to be saved), certain steps seem to take longer for no apparent reason. One possible theory however, is that on fresh media (monthly tapes), writing is faster than on recycled media (daily tapes).

5/31/17 3:42:21 2 blocks processed for sequence 147, volume 000015, on de
5/31/17 4:09:01 341 objects saved from library CVT454AP.

6/01/17 3:40:44 2 blocks processed for sequence 147, volume 001804, on de
6/01/17 3:47:46 341 objects saved from library CVT454AP.

@@ Line 20: / Line 20: @@
 =Observations and other notes=
-For the same BRMS job (or more accurately, for the same list of objects specified by the job to be saved), certain steps seem to take longer for no apparent reason. One possible theory however, is that on fresh media (monthly tapes), writing is faster than on recycled media (daily tapes).
+* For the same BRMS job (or more accurately, for the same list of objects specified by the job to be saved), certain steps seem to take longer for no apparent reason. One possible theory however, is that on fresh media (monthly tapes), writing is faster than on recycled media (daily tapes).
 /31/17   3:42:21  2 blocks processed for sequence 147, volume 000015, on de
@@ Line 28: / Line 28: @@
 /01/17   3:47:46  341 objects saved from library CVT454AP.
 [[Category: IBM i]]
 [[Category: I.T. Periodic Tasks]]

@@ Line 11: / Line 11: @@
 Use this command to quickly see the disk usage in percentage. This also shows IO levels for each disk.
 ====RTVDSKINF====
-Retrieve Disk Info. [https://www.ibm.com/developerworks/ibmi/library/i-using-rtvdskinf-command/ This is a really good article] on RTVDSKINF and related tools used to diagnose disk usage health.
+Retrieve Disk Info. [https://www.ibm.com/developerworks/ibmi/library/i-using-rtvdskinf-command/ This is a really good article] on RTVDSKINF and related tools used to diagnose disk usage health. This is submitted as a batch job and takes approximately 20-30 min. PRTDSKINF produces a report from this command.
 ====SYSPARTITIONSTAT (SQL view)====

← Older revision		Revision as of 19:45, 1 June 2017
Line 27:		Line 27:
	6/01/17 3:40:44 2 blocks processed for sequence 147, volume 001804, on de		6/01/17 3:40:44 2 blocks processed for sequence 147, volume 001804, on de
	6/01/17 3:47:46 341 objects saved from library CVT454AP.		6/01/17 3:47:46 341 objects saved from library CVT454AP.
		+
		+	[[Category: IBM i]]
		+	[[Category: I.T. Periodic Tasks]]

@@ Line 11: / Line 11: @@
 Use this command to quickly see the disk usage in percentage. This also shows IO levels for each disk.
 ====RTVDSKINF====
-Retrieve Disk Info. This is a really good article on RTVDSKINF and related tools used to diagnose disk usage health:
+Retrieve Disk Info. [https://www.ibm.com/developerworks/ibmi/library/i-using-rtvdskinf-command/ This is a really good article] on RTVDSKINF and related tools used to diagnose disk usage health.
 ====SYSPARTITIONSTAT (SQL view)====

@@ Line 8: / Line 8: @@
 =Tools=
 ====RTVDSKINF====
 Retrieve Disk Info. This is a really good article on RTVDSKINF and related tools used to diagnose disk usage health:

@@ Line 4: / Line 4: @@
 [[File:bart-fs-limits.jpg|400px]]
 =Tools=
 ====RTVDSKINF====
 ====ANZLIBBRM====
  Note: Run RTVDSKINF before running this tool!
 =Observations and other notes=

← Older revision		Revision as of 19:22, 1 June 2017
Line 3:		Line 3:
	It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint: large tables in our ERP, stale temporary files, IFS folders with accumulating log files etc. This article documents the different methods and tools that can help in such an analysis. According to IBM, these are some limits we should be aware of:		It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint: large tables in our ERP, stale temporary files, IFS folders with accumulating log files etc. This article documents the different methods and tools that can help in such an analysis. According to IBM, these are some limits we should be aware of:

		+	[[File:bart-fs-limits.jpg\|400px]]
−

	=Tools=		=Tools=

@@ Line 1: / Line 1: @@
 =Overview=
-It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint: large tables in our ERP, stale temporary files, IFS folders with accumulating log files etc. This article documents the different methods and tools that can help in such an analysis.
+It should be a habit to reassess disk usage on Bart every once in a while. It helps to understand storage from a big-picture standpoint: large tables in our ERP, stale temporary files, IFS folders with accumulating log files etc. This article documents the different methods and tools that can help in such an analysis. According to IBM, these are some limits we should be aware of:
 =Observations and other notes=