What are the possible consequences when running TMSINIT with PARM=NODATE?

Products

• CA 1 Flexible Storage

Issue/Introduction

 

What are the possible consequences when running TMSINIT with PARM=NODATE?

 

 

Resolution

Running TMSINIT with PARM=NODATE will suppress all WTORs normally issued by TMSINIT, such as IEFTMS0. CA 1 is automatically activated and the current system date is used as is.  

When using an automated console manager, then PARM=NODATE should be specified for normal CA 1 initialization. 

If the system date is wrong the entries in the TMC will get assigned the wrong creation and last used dates. The expiration dates, which are calculated by adding the retention period to the system date, will be wrong as well.

If you should run TMSCLEAN with the system date set to a date in the future, you will expire and scratch applicable tapes too early.

PARM=NODATE can not be specified if you need to deactivate CA 1 or batch activate CA 1.