We Initialized job "A" and VersionControl moved job "B" (Sequencer job).
We opened a case with Ascential.
They said they could not reproduce the error and kind of quite from then.
We happend to hit the same problem again now, after few months that happened.
This time , we moved job "X" and VersionControl moved job "Y"(regular job).
Any solution for this problem, yet?
Thanks in Advance.
version control moved different job
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Limit
While there is no documented limit on the number of versions, there may be physical factors that intervene.
At one of my client's sites they ran into the "too many subdirectories in directory" limit on Solaris. This was caused by the huge number of dynamic hashed files in the Version project. The client had very many jobs, and had been using Version Control for a number of years when the problem occurred.
Changing some (lots) of the older storage to static hashed files (which don't use directories) was a viable solution to this particular operating system restrction.
At one of my client's sites they ran into the "too many subdirectories in directory" limit on Solaris. This was caused by the huge number of dynamic hashed files in the Version project. The client had very many jobs, and had been using Version Control for a number of years when the problem occurred.
Changing some (lots) of the older storage to static hashed files (which don't use directories) was a viable solution to this particular operating system restrction.
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.