Can't promote to a protected project

jhmckeever · Post by **jhmckeever** » Mon Jun 19, 2006 1:05 pm

Hi Guys,

I've got 2 projects, DEV (a regular unprotected project) and TEST (a protected project) and want jobs in TEST to be read-only (uneditable in designer), but compiled so it can be tested from Director.

I'm using Version Control to promote jobs from DEV into TEST, and was hoping to find a solution that did not involve temporarily un-protecting the TEST project.

When I try and promote from DEV into TEST using VC I get an error:

Code: Select all

Record J\12\VOS3P3 in file DS_JOBOBJECTS is read-only and cannot be writen

I've got user groups DSDEV (DataStage Developer) and DSOPT(DataStage Operator) along with group DSTAGE to which all DSOPT/DSDEV users belong. I'm logging on as DSADM and promoting from DEV to TEST with the Compile/ReadOnly flags set. I've even tried allocating all user groups (DSDEV/DSOPT) Production Manager priviliges but I still get the same result.

I could just do an export/import using Manager ... but how do I then compile the job in TEST? Designer will open the job but won't allow me to compile it.

Any ideas? If I try the same thing but temporarly un-protect the project for promotion then everything works fine. Is what I'm expecting to achieve even possible? I'm using DS v7.1r2.

Thanks,
John.

[UPDATE] - I've just noticed that the DS Admin Guide says you can only Run jobs in protected projects, whilst the VC Help says you can also Compile jobs. No wonder I'm confused!

chulett · Post by **chulett** » Mon Jun 19, 2006 1:59 pm

I believe this is a known bug with your version. They've since corrected it in 7.5.x so that your 'dsadm' user can promote into a Protected project. In the meantime, I think the workaround is as you've noted - to temporarily lower your shields and hope no-one notices the momentary lapse in protection while the jobs are promoting.

The other difference I've noticed is that the Manager 'Multi-Job Compiler' can compile read only jobs where in 7.0.1 it couldn't. We never installed 7.1.x so don't know for sure how the MJC worked there.

jhmckeever · Post by **jhmckeever** » Tue Jun 20, 2006 3:29 am

chulett wrote: I believe this is a known bug with your version. They've since corrected it in 7.5.x so that your 'dsadm' user can promote into a Protected project. In the meantime, I think the workaround is as you've noted - to temporarily lower your shields and hope no-one notices the momentary lapse in protection while the jobs are promoting.

Thanks Craig,

Perhaps another alternative would be to leave TEST unprotected and mandate that all jobs are promoted as read-only?

I presume there's no way of avoiding VC. I'd like to just use Manager to import the DSX into TEST, but it sounds like this 7.1 bug means there's no way of getting it compiled once there. Am I right in this?

Thanks again,
John.

chulett · Post by **chulett** » Tue Jun 20, 2006 6:13 am

it sounds like this 7.1 bug means there's no way of getting it compiled once there. Am I right in this?

From what I recall, yes - but you really should check to see for yourself as we skipped your particular version. Does the Multi-Job Compiler allow you to compile read only jobs? You are correct in that there is no way to do this via the Designer, in any version. There is also a command line compiler command, from what I recall, but I don't remember it off the top of my head... perhaps someone else could supply that for us.

Truthfully, I haven't bothered much with Protected projects due to their teething problems early on. I've been sticking with 'normal' projects and allowing VC to mark everything as Read Only outside of development and it has been working fine so far. Granted, a Protected project adds a level of protection above and beyond RO settings, but I haven't seen a burning need for that extra protection quite yet.

I don't see any need to 'avoid' VC... and using the Manager to export/import everything is a PITA, especially if you must manually flip the RO flag afterwards.