iwlock on new files

Hi All,

We tried to lock a file in a folder in which all the files have version 0+ using iwlock command. The iwlock command failed for each file. But when one file was submitted to Staging, the comand worked successfully for all the files. This strange behaviour would result in failure of the workflow when a new folder is attached to the workflow. Has anybody faced the similar problem and what would be the alternate way to achieve this.

We are on TS6.5 SP 2 on Solaris.

Find more posts tagged with

Comments

pdasarat

Since there is no version available in the STAGING, you have provide -s flag along with the command. This will suppress the check with STAGING.

iwlock "/vpath" "comments" -s

Pradeep

kaalraa

Hi All,

We tried to lock a file in a folder in which all the files have version 0+ using iwlock command. The iwlock command failed for each file. But when one file was submitted to Staging, the comand worked successfully for all the files. This strange behaviour would result in failure of the workflow when a new folder is attached to the workflow. Has anybody faced the similar problem and what would be the alternate way to achieve this.

We are on TS6.5 SP 2 on Solaris.

If you submit the folder prior to use iwlock, then also you would not encounter the issue again.

Migrateduser

Thanks pdasarat and kaalraa,

The -s option solved the problem.

The command works if the file is submitted to staging but as per the requirement, the files must be submitted only through the workflow after someone approves it.

I appreciate the help.

Thanks