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

Vsam KSDS


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
krish2309

New User


Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur

PostPosted: Mon Jul 06, 2015 2:57 pm
Reply with quote

Hi All,

We have a KSDS file and length of KEY is 30 bytes which is 25 data + remaining 5 bytes filler. Recently we just passed data on filler and did not compile the routine. It was okay during testing Phase but could see following message inside VSAM file. Can you please any one advise what could be reason.

Code:

** ERROR ** RPLFDBWD=2A080020 REQ=00 OPTCD=C440 RRN=113 RBA=00E46A92
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Mon Jul 06, 2015 4:05 pm
Reply with quote

What do you mean by seeing that message "inside" the VSAM file? You mean the dataset contains a record with that data in?

How is the key used in the program which has this behaviour? If you try to do a keyed read without the correct low-order values (as they are no longer filler) then you won't be able to read newer records, perhaps.

Absolutely nowhere near enough information to provide much more useful than that.
Back to top
View user's profile Send private message
krish2309

New User


Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur

PostPosted: Mon Jul 06, 2015 4:53 pm
Reply with quote

Hi Bill,

Yes it contain that information mentioned above. We issued the BR command to view the file while it was opened in Online and that file was in use during that time.

We already requested to restore that file and will update you once it done. Our Senior suspect that it could be TSO error message shown when we issued BR command to view it during write operation.

Thank you Bill

Regards
Krishna
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Mon Jul 06, 2015 5:11 pm
Reply with quote

It looks like a program-produced error message, rather than a system one. System errors never start "** ERROR **", they start with a reference number which you can then look up to interpret the message.

You need to find out what wrote that message, and why, and then fix it. It will either be from an Assembler program, or a COBOL program using the second FILE STATUS field.

A user-written error message appears in your file. Not a great deal we can do from here.
Back to top
View user's profile Send private message
krish2309

New User


Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur

PostPosted: Mon Jul 06, 2015 5:25 pm
Reply with quote

Thank You Bill. I will update you once we receive the file and my findings. Thank you.
Back to top
View user's profile Send private message
krish2309

New User


Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur

PostPosted: Tue Jul 07, 2015 8:23 am
Reply with quote

Hi Bill,

The below message appears when we do a BR on 3.4(DSLIST) whereas it doesn't appear while view the same file in Filemanager.

Code:
** ERROR ** RPLFDBWD=2A080020 REQ=00 OPTCD=C440 RRN=113 RBA=00E46A92


I am awaiting for prod file.

I will share my findings later.

Thank you
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Tue Jul 07, 2015 12:22 pm
Reply with quote

Ah. BR looks to be something available at your site, but not a standard option. It is a Rexx/Clist or even a program. It is attempting to let you "browse-but-not-normally" a VSAM dataset, and TSO has no native access to VSAM datasets.

FileManager et al have no problem with VSAM datasets.

Try your BR on any other VSAM dataset chosen at random. I suspect you'll get a similar response.

You could try to find out what BR is, and whether it should allow you to browse a VSAM dataset, but it is a Red Herring as far as your actual problem is concerned.
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 -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts FILE STATUS - 39 ON VARIABLE LENGTH V... COBOL Programming 2
No new posts VSAM Alter Command - Cylinder Extent ... JCL & VSAM 3
No new posts RPLDDDD field for extended VSAM - ESDS JCL & VSAM 0
No new posts DFDSS msg ADR485E when restoring VSAM... JCL & VSAM 5
No new posts Sync logic between VSAM files and DB2... COBOL Programming 9
Search our Forums:

Back to Top