Page 1 of 1

protect my job

Posted: Sat Apr 26, 2008 8:40 pm
by Amarpreet
I have created some jobs in my my folder under jobs category. currently my jobs can be openend by other developers and they can copy my job to their folders. I want that noone can open my job. How do I make my jobs password protected so that it cannot be opened by other developers, not even read only view.

Posted: Sat Apr 26, 2008 9:37 pm
by ray.wurlod
I am not aware of any mechanism that allows for this level of protection. Project-level is the only security mechanism inherent in DataStage.

You can certainly prevent them from changing your job without changing its name, but this does not prevent them from opening or renaming the job.

About the only suggestion I could offer, therefore, is to create your very own project, cover it with heavy duty operating system protections (only the owner has rights) and store your job there.

To make the job executable in the original project compile it in your secure project, export the job executable only, and import that into the original project. When your colleagues attempt to open the job they will receive "this job has no design time information" error.

Posted: Sun Apr 27, 2008 2:07 am
by singhald
you cann't make the datastage job password protected, only can make it readonly if you use protected project, or if you promote the same job using version control project with read only permission . any one can access your job ,datstage dont have job level security setting.

datastage 8.x installation issue:SQL1762N Unable to connect

Posted: Sun Apr 27, 2008 3:54 am
by abdulgani
Hi All,

I am trying to install IBM information Server 8.0.0.4 on AIX 5.3. The installation failed with the following error message. Please advise me on it.


04/27/2008 17:21:01 UPDATE DATABASE CONFIGURATION FOR db2gdwfl USING LOGPRIMARY 50
04/27/2008 17:21:01 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

04/27/2008 17:21:01 UPDATE DATABASE CONFIGURATION FOR db2gdwfl USING LOGSECOND 200
04/27/2008 17:21:01 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

04/27/2008 17:21:01 CONNECT TO db2gdwfl
04/27/2008 17:21:09 SQL1762N Unable to connect to database because there is not enough space to allocate active log files. SQLSTATE=08004


04/27/2008 17:21:09 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONN
ECT ON DATABASE TO USER db2admin
04/27/2008 17:21:09 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During
SQL processing it returned:
04/27/2008 17:21:09 SQL1024N A database connection does not exist. SQLSTATE=08003

datastage 8.x installation issue:SQL1762N Unable to connect

Posted: Sun Apr 27, 2008 3:56 am
by abdulgani
Hi All,

I am trying to install IBM information Server 8.0.0.4 on AIX 5.3. The installation failed with the following error message. Please advise me on it.


04/27/2008 17:21:01 UPDATE DATABASE CONFIGURATION FOR db2gdwfl USING LOGPRIMARY 50
04/27/2008 17:21:01 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

04/27/2008 17:21:01 UPDATE DATABASE CONFIGURATION FOR db2gdwfl USING LOGSECOND 200
04/27/2008 17:21:01 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

04/27/2008 17:21:01 CONNECT TO db2gdwfl
04/27/2008 17:21:09 SQL1762N Unable to connect to database because there is not enough space to allocate active log files. SQLSTATE=08004


04/27/2008 17:21:09 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONN
ECT ON DATABASE TO USER db2admin
04/27/2008 17:21:09 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During
SQL processing it returned:
04/27/2008 17:21:09 SQL1024N A database connection does not exist. SQLSTATE=08003

Posted: Sun Apr 27, 2008 5:29 am
by ArndW
You have already posted these questions in a new thread - there is no reason to hijack this thread with a completely unrelated question. this is the active thread

Posted: Sun Apr 27, 2008 5:57 am
by keshav0307
Amarpreet
you can't do it in same project. Create another project to logon yourself only, and export only executable to the other project, so other developer can not copy your job