We are getting ready to upgrade from 7.5.2 to 8.1. During the migration is it possible to rename projects?
Thanks,
Vince
Renaming a project during migration
Moderators: chulett, rschirm, roy
Renaming a project during migration
Computer analyst to programmer: "You start coding. I'll go find out what they want."
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Do you need to migrate them at all? Would it be sufficient to have jobs running in the new environment create them afresh? (That's one of the things Validate Job is useful to do.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
And the how would depend on the nature of the hashed file, pathed verses account-based. The former can simply be copied by whatever mechanism you choose as long as (for dynamic hashed files) all of the files in each director (including the hidden file) make the trip together.
Account-based hashed files take an extra step to recreate the VOC record. You could Validate the new jobs which would create an empty hashed file and the needed VOC record then the same copy noted above could bring the old data over.
Account-based hashed files take an extra step to recreate the VOC record. You could Validate the new jobs which would create an empty hashed file and the needed VOC record then the same copy noted above could bring the old data over.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Thanks Craig and Ray. Some of the hashed files will be repopulated as part of normal processing but we still have hundreds of files that are "updated" and due to the nature of how things are processed cannot simply be repopulated.
Is there some mechanism to easily Validate all the jobs in the project?
Is there some mechanism to easily Validate all the jobs in the project?
Computer analyst to programmer: "You start coding. I'll go find out what they want."
I don't think there's any automagic way, Support might be able to provide one for you, though. Worst case a script using dsjob could iterate through a list of job names and validate them one by one. You could also use dsjob to generate the list of jobs.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers