|
View previous topic :: View next topic
|
| Author |
Message |
sai1621
New User
Joined: 22 Jan 2010
Posts: 4
Location: Bhubaneswar
|
|
|
|
Hi All,
This is a peculiar issue we are facing while accessing IMS DB in production region.
We have an online IMS-DC screen that picks up the data from Secondary index database. When we are trying to fetch the same data from the same segment of primary database (for which this secondary index defined) through a batch BMP job, we are getting GE status code.
We used a GN with a qualified call to read the segments from primary database.
Need help/pointers and possilble scenarios where these issues can happen.
Thanks,
Sai kumar. |
|
| Back to top |
|
 |
Sandy Zimmer
Active Member
Joined: 13 Jun 2007
Posts: 826
Location: Wilmington, DE
|
|
|
|
| We don't have enough info to help. Is this an addition to an existing process? Was this put into a PRODUCTION environment without testing? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
Was this put into a PRODUCTION environment without testing?
|
No!
that's how we test..... in production |
|
| Back to top |
|
|
sai1621
New User
Joined: 22 Jan 2010
Posts: 4
Location: Bhubaneswar
|
|
|
|
Hi,
Thanks for your prompt response !
The primary and secondary index database are in production environment since 1990's.
We are facing an issue with the access of data.
An online screen picks up data from secondary index whereas when we try accessing the same data from the primary database using a batch BMP program, it is not picked up.
Instead we tried to extract all the occurences of that particular segment type but the data is not present in the extract file.
Secondary index might not reflect the entire data from the primary database (concept of Sparse indexing) using EXIT ROUTINES, but just wanted to know is the other way round is possible or not.
Thanks,
Sai Kumar. |
|
| Back to top |
|
|
sai1621
New User
Joined: 22 Jan 2010
Posts: 4
Location: Bhubaneswar
|
|
|
|
All,
The issue is with the DBRC setup for the secondary index.
Its been setup for a incorrect VSAM dataset. Identified this from spool logs in the master IMS* environment job.
Altered the DBRC to point to the correct VSAM dataset, followed by re-build of secondary index.
This resolved the issue.
Thanks |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
| That's been that way since the 1990's??? |
|
| Back to top |
|
|
|
|
