Chris,  the year is part of the device reservation expiration date.  When using symconfigure to set the reservation, the year is an optional parameter.  If no year is specified, the current year is assumed.  Now, the date in the symconfigure list -reserved is the date that the reservation was created, not when it is set to expire. To see the expiration date, you need to look at the details of the reservation itself.  # symconfigure list -reserved Symmetrix ID: 000195700398         S Y M M E T R I X  D E V I C E  R E S E R V A T I O N S-------------------------------------------------------------------------------------Reserve  Date        FlagsID      Reserved    TM    Owner        Devices    Port Addresses-------  ----------- ----- ------------- ---------  ---------------------------------000001  03/04 11:13 E-    C:licoj048\smc 0390:039F      - Legend for Flags:   Type of Reservation  (T) :  E = Enforced        A = Advisory  Mapping Address Mode (M) :  L = Lun addressing  V = Volume Set addressing                                T = Target/lun      C = Channel addressing # symconfigure show -reserve_id 1 Symmetrix ID: 000195700398   Reserve ID            : 000001   Usage                  : Reserved  Flags                  : Enforced   Reserved Date          : 03/04/2013 11:13:09  Expiration Date        : 03/20/2013 17:01:40   Devices                : 0390:039F   Owner                  : C:licoj048\smc  Hostname              : licoj048  Application            : UNIVMAX  User Data              : 0  User Comment          :  Hope that helps.
Good Day Everyone,   I'm trying to answer a question regarding Symmetrix device reservations - there is concern that the lack of a "Year" value in the "Date Reserved" column of the output below could cause an issue with some devices which have been reserved for a while in the near future, when the reservation hits 1 year (i.e., from the output below, May 18th of this year).   Could anyone confirm (or direct me to a Primus article or document) that this either would or would not be an issue, and what we should expect when a device reservation exceeds 1 year?   I'm aware that reservations typically will expire, but not being an expert on this feature of Enginuity and SymCLI, I could use some clarification & advice.   *Here's an example of the SymCLI output we're reviewing (the Date Reserved is in bolded red - also please pardon the formatting in converting from CLI):  ===================================================================================== [root[NAME] ~]# symconfigure -sid xxxx list -reserved  Symmetrix ID: xxxxxxxxxxxx  S Y M M E T R I X D E V I C E R E S E R V A T I O N S ___________________________________________________________________________ __________ Reserve Date Flags ID Reserved TM Owner Devices Port Addresses ------- ----------- ----- ------------- --------- --------------------------------- 000005 05/18 09:11 E- D:abc\wxyz 0589 - 0587:0588 - 0582 - 0585:0586 - 0583:0584 - 058A:05C2 - 1191:11BC - Comment: For Servers hostname196_197 =====================================================================================  *As a note, I've tested running this as a "symconfigure -sid xxxx list -reserved -v" (adding the verbose, "-v" option), but a year value for Date Reserved still is not displayed.   Please assist if you could, and thanks!   -Chris 
Symmetrix Reserved Devices - Date Reserved does not include a YEAR value