Lock and unlock jobs

[jhmckeever]

I wouldn't choose to modify permissions on the files which form the DataStage repository. If you want to change the read-only flag of individual jobs do it in UV:

Code: Select all

UPDATE DS_JOBOBJECTS 
SET    READONLY = 'RO' 
WHERE  OBJIDNO = (
          SELECT JOBNO 
          FROM DS_JOBS 
          WHERE NAME = '{MyJobName}');

Set the flag to 'NRO' for Read/Write access.

J.

[NEO]

But that would make the job read only for the person who wants to work on it. Then the developer will have to switch it to NRO everytime he has to work on it and make it back to RO every time he logs off the machine, or takes a break or chooses to work on something else. Instead if he can hold a lock through the duration of his development activity, where only he can change the code, it would be much easier.

[chulett]

Would be nice, sure, but there's no such thing.

[ArndW]

Job status cannot be set per user. Changing OS-level permissions on some of the part files won't quite do it either, in addition they will generate errors and warnings for users just browsing the repository.

[DSguru2B]

Put a big, brighty-coloured annotation on it

I'm working on this.
DO NOT change it!

I think easiest, simplest solution is provided by Ray. If others have to work on this in your absence, then the developer should add his/her id and timestamp and a brief description of what was changed, to the annotation. This will be much easier.

[ray.wurlod]

Anyone using a source code control system relies upon the fact that the DSX is checked out as the "lock" you seek. Once it's checked in again, someone else is entitled to check it out. While ever you have it checked out, it's "locked".

It's easy to enforce; any violation is a sackable offence.

Someone needs to administer this, in case an emergency arises - such as you checked it out, went home, and did not reappear the next day for whatever reason.