parameter set in new server

[egsalayon]

hi,

we used parameter set to pass values like db server name, schemas, etc. in our dev't server the name of the db server is bcudevt. but when our jobs were migrated to prod'n server, the db server name is bcuprod. so we expect just to change the value of the parameter set and run the jobs with no problem. but to our amazement, somehow the jobs sometimes still have the db server name value as bcudevt, which in fact was change to dcuprod in the parameter set value. why is this so? how can we solve this with minimal changes, tnx

eric

[owen3]

1. Define your all parameter like servername, schema, uid, pwd etc at user defined enviroment variable.
2. Keep all these parameter in one parameter set like $DB_USER, $DB_SERVER etc. and save. It will be saved at Repository.
3. Open Parameter set\Parameter and double click on Default Value.
4. Small screen will pop up.
5. From drop down menu choose $PROJDEF.

This way when you move your job from one server to another it will automatically take the project defined parameter and so you don't have to manually change or there won't be any chance of getting wrong param value.

[owen3]

1. Define your all parameter like servername, schema, uid, pwd etc at user defined enviroment variable.
2. Keep all these parameter in one parameter set like $DB_USER, $DB_SERVER etc. and save. It will be saved at Repository.
3. Open Parameter set\Parameter and double click on Default Value.
4. Small screen will pop up.
5. From drop down menu choose $PROJDEF.

This way when you move your job from one server to another it will automatically take the project defined parameter and so you don't have to manually change or there won't be any chance of getting wrong param value.

[owen3]

1. Define your all parameter like servername, schema, uid, pwd etc at user defined enviroment variable.
2. Keep all these parameter in one parameter set like $DB_USER, $DB_SERVER etc. and save. It will be saved at Repository.
3. Open Parameter set\Parameter and double click on Default Value.
4. Small screen will pop up.
5. From drop down menu choose $PROJDEF.

This way when you move your job from one server to another it will automatically take the project defined parameter and so you don't have to manually change or there won't be any chance of getting wrong param value.

[egsalayon]

1. Define your all parameter like servername, schema, uid, pwd etc at user defined enviroment variable.
2. Keep all these parameter in one parameter set like $DB_USER, $DB_SERVER etc. and save. It will be saved at Repository.
3. Open Parameter set\Parameter and double click on Default Value.
4. Small screen will pop up.
5. From drop down menu choose $PROJDEF.

This way when you move your job from one server to another it will automatically take the project defined parameter and so you don't have to manually change or there won't be any chance of getting wrong param value.

I heed your advice but still there were errors, example is below:

Read_MMS_SG1_APSUPP: Error Idx = 1;
DB2Driver Embedded SQL message: SQL1013N The database alias name or database name "$PROJDEF" could not be
found. SQLSTATE=42705
;
sqlcode = -1013;
sqlstate = 42705

it seem like $PROJDEF doesn't resolve to value "bcuprod".

[swarnkar]

it seem like $PROJDEF doesn't resolve to value "bcuprod".[/quote]

While defining the parameter at Adminstrator, you have to provide the actual value of parameter and when you are using them in jobs then you can select the between $PROJDEF and $ENV.