View previous topic :: View next topic
|
Author |
Message |
Mahua Mitra
New User
Joined: 26 Apr 2007 Posts: 49 Location: Delhi
|
|
|
|
Hi
Are there some specific system tables which are required to be updated for each new high level qualifier created in production.
Thanks |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Not usually, you need to define an alias in the master catalog to point to the user catalog allocated to that alias.
Beware of shared DASD though. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
yes,
you can find out by tracing the error code you receive when you attempt to allocate a ds with an invalid hlq. this will tell you what services/applications are controlling your site.
you should speak to you systems/security people to determine valid HLQ. |
|
Back to top |
|
|
Mahua Mitra
New User
Joined: 26 Apr 2007 Posts: 49 Location: Delhi
|
|
|
|
Thank you for responding.
When I ran the job in Test region, it ran fine and the files with the HLQ were created fine.
But when I try to stage the job in a Changeman package, it gives an error that says "HLQ is not valid".
Can you please suggest why this error is coming.
Do we need some special entries so that Changeman recognizes this new HLQ? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Have the new production hlq's been defined? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
As Dick says, the job ran fine to define the alias(es) in test, but did you define the same alias(es) to the same catalog in the other environment ? |
|
Back to top |
|
|
|