Lock 242 means a previous symconfigure reserve or release command failed to complete successfully or was cancelled by a user before completion, refer the appropriate symapi-yyyymmdd.log file.  Check with the output of the symcfg list -lock command to see the duration of lock 242. If it is held for longer that 10 minutes then release lock 242 with the following command:  symcfg -lockn # release ( -force is optional)   In your case:  symcfg -sid -lockn 242 release 
Hi,   When attempting to add a TDEV+R1 device on to a storage group, I get an error, that the operation failed due to another program using the  device reservation exclusive lock.  On trying to see more info about the lock in question (i.e symdev list -lock -lockn ALL ) I see that Lock 242 is set, and this is used for device reservation. How safe is it to release this lock manually, and what type of actions could've caused this lock to be set.   Your assistance in this regard is much appreciated.  BR, Naleendra
Device Reservation Lock