Life cycle action storage optimizer

You can find the sample JCL M9STORO in the SAMPLIB PDS deployed during the BMC AMI Cloud agent installation or upgrade. The PWD parameter must point to the agent installation directory.

Life cycle action storage optimizer parameters

The following parameters are available:

Parameter	Format	Description	Default
--simulate	yes\|no	Specifies whether life cycle runs in simulation mode, meaning, no actual deletes occur	yes
--target	cloud	Specifies the target storage to be scanned Only cloud is supported.	cloud
--action	delete-expired\|storage-optimizer	Specifies the action to perform	delete-expired
--data-directory-range	nn-nn	Specifies the range of data directories scan within the object storage	0-9
--minimal-days-from-creation	nn	Specifies the minimal number of days for a cloud object to be considered as incomplete, thus making it eligible for optimization	5

Process output DDs

Storage optimizer opens three output DD files. The following table includes details about each DD:

Ouput DD name	Description
STDOUT	The life cycle storage optimizer output
SYSOUT	The JVM output
SUMMARY	A list of Identified optimizable chunks to be deleted, including a periodic summary that is printed every five minutes

Examples

Example 1

The sample JCL M9STORO, by default, is set to scan for resources older than 30 days in simulation mode only.

//M9STORO JOB ACCT#,SYSPROG,TIME=NOLIMIT,REGION=0M,USER=M9USER,
// NOTIFY=M9SIVA,MSGLEVEL=(1,1),MSGCLASS=X
//JAVA     EXEC PROC=JVMPRC86,VERSION='M9',TIME=NOLIMIT,
// JAVACLS='-jar lib/model9-life-cycle.jar'
//STEPLIB DD DISP=SHR,DSN=SYS2.MODEL9.V270.LOADLIB
//ZM9$NORC DD DUMMY
//SYSPRINT DD SYSOUT=*
//SUMMARY DD SYSOUT=*,LRECL=1100
//STDOUT DD SYSOUT=*,LRECL=512
//SYSOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//ABNLIGNR DD DUMMY
//UTILMSGS DD SYSOUT=*
//MAINARGS DD *
--simulate yes
--target cloud
--action storage-optimizer
--data-directory-range 0-9
--minimal-days-from-creation 0
--maximal-days-from-creation 30
//STDENV   DD *
export PWD=/usr/local/model9/jenkins_agent
export CONF_HOME=$PWD/../conf
export ENV=life-cycle
. $PWD/scripts/stdenv-main.sh

Example 2

The sample output below demonstrates how the STDOUT output DD look like when running the storage optimizer process.

********************************* TOP OF DATA ******************************************************************************************************************************
ZM9L000I ********************************************************************************************************************************************************************
ZM9L000I * Model9 Life Cycle Management
ZM9L000I * Website: https://www.model9.io
ZM9L000I * Contact: support@model9.io
ZM9L000I * (c) Copyright 2016 Model9 LTD.
ZM9L000I * (c) Copyright 2023 BMC LTD.
ZM9L000I *********************************************************************************************************************************************************************
ZM9L003I Input: --simulate yes --target cloud --action storage-optimizer --data-directory-range 0-9 --minimal-days-from-creation 30
ZM9L011I MODEL9 LIFE CYCLE MANAGEMENT STARTED
ZM9L004I Target storage url: https://object.ecstestdrive.com
About to run lifecycle storage optimizer with arguments: StorageOptimizerCommandArgs{unknownArgs=[], simulate='yes', dataDirectoryRange=[0, 1, 2, 3, 4, 5, 6, 7, 8,
Number of chunks verified so far: 4001 (4001 candidates, 0 ignored, 0 malformed)
Number of optimizable chunks identified so far: 35
Total optimizable storage amount so far: 1.35 GB
Mapping object cache run statistics: CacheStats{hitCount=17, missCount=395, loadSuccessCount=395, loadExceptionCount=0, totalLoadTime=204647527, evictionCoun ZM9L012I MODEL9 LIFE CYCLE MANAGEMENT ENDED SUCCESSFULLY
******************************** BOTTOM OF DATA *****************************************************************************************************************************

Life cycle action storage optimizer