IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

IMS SEGMENT READ ISSUE


IBM Mainframe Forums -> IMS DB/DC
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
mframe-guy

New User


Joined: 03 Dec 2020
Posts: 6
Location: India

PostPosted: Sun May 02, 2021 9:36 pm
Reply with quote

Hi All,

I have recently deleted and created a new IMS DB file and its IMS Index file using the current image copy file.
below is the sample jcl used for Loading the IMS file

//STEP02 EXEC PGM=DFSRRC00,REGION=1024K,
// PARM='UDR,DFSURDB0,DBNA0AD,7,0000,,0,,N,0,T
//* PARM='UDR,DFSURDB0,DBNA0AD'
//STEPLIB DD DISP=SHR,DSN=IMSVS.WT.TEST.PGMLIB
// DD DISP=SHR,DSN=IMSVS.WT.TEST.RESLIB
//DFSRESLB DD DISP=SHR,DSN=IMSVS.WT.TEST.RESLIB
//IMS DD DISP=SHR,DSN=SYSD.WT.TEST.IMSDBDL
//DFSVSAMP DD DISP=SHR,DSN=SYSD.WT.TEST.IMSCNTL(DFSVSAMP)
//DFSUCUM DD DUMMY
//DFSULOG DD DUMMY
//SYSPRINT DD SYSOUT=Y
//DBIMSXX1 DD DSN=TEST.IC.IMSDB1,DISP=SHR
//DFSUDUMP DD DISP=SHR,DSN=TEST.IMSU.ICIMSXX1.IMGECOPY(+0
//SYSIN DD *
S DBIMSXX DBIMSXX1

Though the IMS has been created successfully with proper record counts as same as the source.

When I run a job using these ims db and index files, some of the segments of the IMS files are misread, for instance, CURR-BUS-DAY which has to be read in 9(5) julian format (YYDDD) like below

PREV-YYDDD 9(5) : 21119
CURR-YYDDD 9(5) : 21120

but it misreads the data as

PREV-YYDDD 9(5) : 20211
CURR-YYDDD 9(5) :20202.

if the segments are not read properly, where I have to start my analysis and what could be the reason for the same.

is there anything else I have to do in the LOAD JCL I have mentioned above.

Please advise. Thank you in advance.
Back to top
View user's profile Send private message
Gary Jacek

New User


Joined: 17 Dec 2007
Posts: 64
Location: Victoria, BC, Canada

PostPosted: Wed Nov 09, 2022 3:43 am
Reply with quote

mframe-guy wrote:

When I run a job using these ims db and index files, some of the segments of the IMS files are misread, for instance, CURR-BUS-DAY which has to be read in 9(5) julian format (YYDDD) like below

PREV-YYDDD 9(5) : 21119
CURR-YYDDD 9(5) : 21120

but it misreads the data as

PREV-YYDDD 9(5) : 20211
CURR-YYDDD 9(5) :20202.


It appears your image copy was created using a DBD that has a 4 digit (Y2k-compliant) year. I suspect your DBD in SYSD.WT.TEST.IMSDBDL uses a 2 digit year.

This would explain how 21119 becomes 20211 in your resulting output.

Is the contents of SYSD.WT.TEST.IMSDBDL correct when compared to the DBDLIB used to create the image copy? The DBDMAP utility could be very useful here.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> IMS DB/DC

 


Similar Topics
Topic Forum Replies
No new posts Panvalet - 9 Character name - Issue c... CA Products 6
No new posts Issue with EXEC CICS QUERY SECURITY c... CICS 6
No new posts DASD - non SMS - volser change - VSAM... JCL & VSAM 2
No new posts Read a flat file and update DB2 table JCL & VSAM 2
No new posts how to solve this power failure shutd... ABENDS & Debugging 5
Search our Forums:

Back to Top