cds-links-migration parameters and examples
cds-links-migration parameters
The following parameters are available:
Parameter | Format | Description | Default |
|---|---|---|---|
--simulate | yes|no | Specifies whether the life cycle runs in simulation mode, meaning that no actual migration occurs | yes |
--target | cloud | Specifies the target storage type to be scanned | cloud |
--action | cds-links-migration | Specifies the action to perform | delete-expired |
agent.yml parameter
You must specify the following additional parameter in the agent.yml configuration file:
Parameter | Format | Description | Default value |
|---|---|---|---|
migrations.cds-links-migration-v400-enabled | true|false | true–AMI Cloud uses the CDS version 3 link format. false–AMI Cloud uses the CDS version 4 link format. | false |
Process output DDs
The cds-links-migration opens the following output DD file:
Output DD name | Description |
|---|---|
STDOUT | The life cycle cds-links-migration output, including a periodic summary that is printed every five minutes |
SYSOUT | The JVM output |
SUMMARY | A list of CDS data sets that are migrated |
Examples
The following sample JCL M9CDSMIG, set to enable migration by default:
// NOTIFY=&SYSUID,MSGLEVEL=(1,1),MSGCLASS=X
//*******************************************************************
//* (c) Copyright 2025 BMC Software, Inc.
//*******************************************************************
//CDSLNKMG EXEC PGM=JVMLDMM9,REGION=0M,TIME=NOLIMIT,
// PARM='/+T -jar lib/model9-life-cycle.jar'
//STEPLIB DD DISP=SHR,DSN=SYS2.MODEL9.V401.LOADLIB
//* DD DISP=SHR,DSN=YOUR.JAVA.STEPLIB
//MAINARGS DD *
--simulate yes
--target cloud
--action cds-links-migration
//STDENV DD *
export PWD=/usr/lpp/model9/agent
export CONF_HOME=$PWD/../conf
export ENV=expiration-handler
. $PWD/scripts/stdenv-main.sh
//ZM9$NORC DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//ABNLIGNR DD DUMMY
//SUMMARY DD SYSOUT=*
//
The following example displays a sample of the STDOUT output:
2024-11-27 02:28:36.296 INFO ZM9L000I *******************************************************************************
2024-11-27 02:28:36.345 INFO ZM9L000I * BMC AMI Cloud Life Cycle Management *
2024-11-27 02:28:36.346 INFO ZM9L000I * Website: https://www.bmc.com *
2024-11-27 02:28:36.347 INFO ZM9L000I * (c) Copyright 2016 Model9 LTD. *
2024-11-27 02:28:36.348 INFO ZM9L000I * (c) Copyright 2025 BMC Software Inc. *
2024-11-27 02:28:36.349 INFO ZM9L000I *******************************************************************************
2024-11-27 02:28:36.352 INFO ZM9L003I Input: --simulate no --target cloud --action cds-links-migration
2024-11-27 02:28:38.258 INFO ZM9L011I MODEL9 LIFE CYCLE MANAGEMENT STARTED
2024-11-27 02:28:38.260 INFO ZM9L004I Target storage url: https://bucket.vpce-0f03aea27e78e0397-hpbr0957.s3.us-east-1.vpce.amazon
aws.com
2024-11-27 02:28:39.892 INFO Start listing of CDS links for migration from the path 'model9/group-M9N4/imports/tapeDataset/'
2024-11-27 02:28:39.993 INFO Finished submitting all CDS link migration runnable
2024-11-27 02:29:39.916 INFO Finished polling all CDS link migration runnable
2024-11-27 02:29:39.921 INFO ZM9J005I CDS Link migration has ended, total 1000 links were scanned
2024-11-27 02:29:39.923 INFO ZM9J006I Out of 100 scanned cds links, 990 got migrated, 3 got errored out, 7 got skipped;
2024-11-27 02:29:39.930 INFO ZM9L012I MODEL9 LIFE CYCLE MANAGEMENT ENDED SUCCESSFULLY
******************************** BOTTOM OF DATA **************************************************************************************