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

U0064 - GENERATION DATA GROUP DOES NOT EXIST


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
ashishsr123

New User


Joined: 06 May 2008
Posts: 33
Location: Chennai

PostPosted: Sat Jun 06, 2009 6:53 pm
Reply with quote

Hi,

One job abended and i was called for help.
Job abended with U0064,I did a JCL scan and got this
Code:
 
***ERROR  - DSS4420E - GENERATION DATA GROUP DOES NOT EXIST


Clearly shows what is the issue.
But this job ran fine yesterday, and this is Production , I was just wondering possible causes.

I do not think this GDG would have been removed ,this is Production and we have strong processes in place .this should not have happened.

Any ideas what could be the reason. I have seen this error first time.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA

PostPosted: Sat Jun 06, 2009 7:00 pm
Reply with quote

Quote:
I do not think this GDG would have been removed ,this is Production and we have strong processes in place .this should not have happened.
Why not just look under TSO ISPF option 3.4 and know for sure rather than thinking? Without facts, such as finding out for sure about the GDG, we're not going to be able to do anything more than guessing and you can do that just as well as we can.

And, by the way, I've seen a number of cases where someone thought they were working with test data sets and made changes to production by mistake so it is entirely possible that the GDG was deleted. No, it should not have happened -- but that doesn't say it did not happen. In at least one case the person used their emergency id so they had full access to the production data sets even though there was no reason for that use.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Sun Jun 07, 2009 1:08 am
Reply with quote

Hello,

Quote:
Any ideas what could be the reason.
Either the dataset does not have proper security defined or someone with permission erroneously deleted the dataset.

Quote:
But this job ran fine yesterday,
I suspect this job is the "victim" rather than the "culprit". Some other job or some person most likely deleted the gdg base.
Back to top
View user's profile Send private message
ashishsr123

New User


Joined: 06 May 2008
Posts: 33
Location: Chennai

PostPosted: Sun Jun 07, 2009 3:38 pm
Reply with quote

Forgot to mention the GDG does not exists , i check via 3.4 , i was just wondering over the reasons for it.

yes there are many possibilities.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Sun Jun 07, 2009 3:42 pm
Reply with quote

SMF records, in the 60's range, can not recall the exact record type needed, to find out who and when for deleting the dataset.
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 -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts How to save SYSLOG as text data via P... All Other Mainframe Topics 4
No new posts Store the data for fixed length COBOL Programming 1
No new posts Data set Rec-Cnt and Byte-Cnt Testing & Performance 2
No new posts SCOPE PENDING option -check data DB2 2
No new posts Check data with Exception Table DB2 0
Search our Forums:

Back to Top