Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

JCL ERROR as file got migrated

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
kumarreddyuppaluru

New User


Joined: 17 Mar 2008
Posts: 8
Location: Bangalore

PostPosted: Wed Jun 17, 2009 12:06 am    Post subject: JCL ERROR as file got migrated
Reply with quote

Hi,

In our project , jobs are scheduled through control-m. i got a abend recently. It is giving JCL ERROR , UNEXPECTED CATALOG LOCATE PROCESSING ERROR - RETURN CODE

when i checked the dataset, i observed that got migrated. The same kind of problem came with other job also. I restarted the job and it went fine.

But my doubt is when we submit the job, JCL is able to recall the file, But it is not able to recall when it is submitted through control-m.

Could some one please tell me how i can eliminate this in future.

The following is info abt the dataset

General Data Current Allocation
Management class . . : MCPRDDEF Allocated tracks . : 1
Storage class . . . : SCMASTER Allocated extents . : 1
Volume serial . . . : SMAL7P
Device type . . . . : 3390
Data class . . . . . : DCHSM Current Utilization
Organization . . . : PS Used tracks . . . . : 0
Record format . . . : FB Used extents . . . : 0
Record length . . . : 80
Block size . . . . : 9040
1st extent tracks . : 1
Secondary tracks . : 60
Data set name type : SMS Compressible : NO

Creation date . . . : 2004/06/26 Referenced date . . : 2009/06/16
Expiration date . . : ***None***
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10256
Location: italy

PostPosted: Wed Jun 17, 2009 12:25 am    Post subject: Reply to: JCL ERROR AS FILE GOT MIGRATED
Reply with quote

not enough info,
what does Your storage support group say
Back to top
View user's profile Send private message
kumarreddyuppaluru

New User


Joined: 17 Mar 2008
Posts: 8
Location: Bangalore

PostPosted: Wed Jun 17, 2009 12:46 am    Post subject:
Reply with quote

Sorry ,

Return code is 38
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed Jun 17, 2009 11:28 am    Post subject:
Reply with quote

Yes, has happened before. The program opens the file which is currently being recalled, and then throws a wobbly.

You need to ensure that any migrated files are recalled before the batch job is processed.
Back to top
View user's profile Send private message
gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1703
Location: Australia

PostPosted: Wed Jun 17, 2009 11:46 am    Post subject:
Reply with quote

Hi,

I'm sure it has nothing to do with job being submitted through Control-M.


Gerry
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Jun 17, 2009 12:45 pm    Post subject:
Reply with quote

Quote:
I'm sure it has nothing to do with job being submitted through Control-M.
Ditto.

Kumar -- Don't you get some mesage-ID assosciated with that error description?(IGD04001I ?). One probable reason can be that HSM recalls fail due to missing SMS volume.

And for this
Quote:
Could some one please tell me how i can eliminate this in future.
your best bet would be to get in contact with your storage support group as suggested by Enrico.
Back to top
View user's profile Send private message
kumarreddyuppaluru

New User


Joined: 17 Mar 2008
Posts: 8
Location: Bangalore

PostPosted: Wed Jun 17, 2009 8:39 pm    Post subject:
Reply with quote

Yes Anuj, i got description IGD04001I.

For this is there any possibility to do on my own? is it the only way (contact Storage support guys).
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Jun 18, 2009 10:43 am    Post subject:
Reply with quote

If this is to do with Production runs -- strongly suggest you get in touch with Storage support or if it's a "test-region" thing you need to ensure that any migrated files are recalled before the batch job is processed, as Expat has suggested.
Back to top
View user's profile Send private message
gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1703
Location: Australia

PostPosted: Thu Jun 18, 2009 10:50 am    Post subject:
Reply with quote

Hi,

just add an IEFBR14 step to recall the files before they are needed.


Gerry
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Jun 18, 2009 11:34 am    Post subject:
Reply with quote

Hi Expat, Gerry,

I'm not a storage guy so curious-- how in the production one will ensure such things, I mean "recalling migrated files before the batch job is processed" -- adding IEFBR14 is how good, what if every jobs has such DSNs to recall? What about the I-O time for such jobs?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Jun 18, 2009 11:54 am    Post subject:
Reply with quote

That's where a storage team that knows what happens is important. I always produce reports of datasets recalled by production jobs, and go talk to the JCL monkeys about the job schedules. If it is that the ILM has auto migrated the data, then the dataset would be allocated a different MGMTCLAS to retain it on DASD, depending on size.

Of course if it's one of the JCLM's that has migrated it manually, he usually gets informed to keep his grimy little mits off of my HSM.

For very large datasets, usually for ME and QE processing it's an automated recall one or two days before the scheduled run into a specific temporary storage group for the large stuff.

All so very easily controlled by correct setup of the ACS routines.
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Jun 18, 2009 12:18 pm    Post subject:
Reply with quote

Quote:
If it is that the ILM has auto migrated the data, then the dataset would be allocated a different MGMTCLAS to retain it on DASD, depending on size.
oh.. JCLMs have at least one way to escape..! icon_lol.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Converting Variable block file to Fix... bhavana yalavarthi DFSORT/ICETOOL 10 Tue May 16, 2017 2:20 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts Issue with NDM process to transmit ES... chetanambi All Other Mainframe Topics 6 Wed May 03, 2017 10:52 am
No new posts File processing vishwakotin Mainframe Interview Questions 9 Fri Apr 28, 2017 11:38 am
No new posts Occurrence of various strings within ... TS70363 JCL & VSAM 1 Thu Apr 27, 2017 8:18 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us