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

How to recall migrated datasets beofre executing batch jobs


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

New User


Joined: 20 Sep 2006
Posts: 4
Location: Bangalore

PostPosted: Tue Sep 11, 2007 12:19 pm
Reply with quote

Scenario:

I have a batch job (JOBAA) which runs on weekly basis. It uses around 15 flat files. Usually these datasets get migrated (to tape) after one or two days of execution. Next time, when I try to run the same job (JOBAA) it takes lot of time to recall these datasets and then the executionn starts. Actually job's execution time is less than 5 mins but it takes 15-20 mins to recall and then execution starts. Since this is a scheduled job I having serious problems with it's dependecies.

Can you please help me with recalling the datasets well before execution of the JOBAA.

Suggestions and comments are welcome.

Vinay.
Back to top
View user's profile Send private message
murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India

PostPosted: Tue Sep 11, 2007 12:30 pm
Reply with quote

vinay,

If possible change the MANAGEMENT class for the files.
Back to top
View user's profile Send private message
guptae

Moderator


Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India

PostPosted: Tue Sep 11, 2007 12:37 pm
Reply with quote

Vinay,

Other way is to schedule following jcl to riun befor ur job execution

Code:
//STEP1        EXEC PGM=IKJEFT01,REGION=512K                 
//SYSPRINT     DD SYSOUT=*                                   
//SYSTSPRT     DD SYSOUT=*                                   
//SYSTSIN      DD *                                           
  HRECALL    'DATASET NAME'      WAIT
/*
Back to top
View user's profile Send private message
murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India

PostPosted: Tue Sep 11, 2007 12:41 pm
Reply with quote

Ekta,

Quote:
Other way is to schedule following jcl to riun befor ur job execution

Once the files get migrated, I believe recall process takes time whether you run seperate job (for recalling) or run the main job without recalling the files.

If you really want to save the recall time, CHANGE the management class (as said before) or try browsing the file once in 2/3 days manually (tedious process and need to remember).
Back to top
View user's profile Send private message
acevedo

Active User


Joined: 11 May 2005
Posts: 344
Location: Spain

PostPosted: Tue Sep 11, 2007 12:43 pm
Reply with quote

IEFBR14 will do the job too.

Code:
//RECALL  EXEC PGM=IEFBR14,COND=(0,LT)                   
//DD01     DD DSN=YOUR.DSN.HERE,DISP=SHR
Back to top
View user's profile Send private message
guptae

Moderator


Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India

PostPosted: Tue Sep 11, 2007 12:45 pm
Reply with quote

Hi Murali,

Thats correct.
But what I am saying is to schedule a job befor running the actual job which does not require any manual intervation
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Tue Sep 11, 2007 1:22 pm
Reply with quote

Hi !

Your organization must trade off between dasd occupancy and overall batch performance;
I do not know about Your environment ( dataset size, dasd constraints ),
but in general datasets with a steady weekly usage are not good candidates for any kind of migration,
even pre-recalling those dataset will not guarantee You a consistent batch response time.

regards

e.s
Back to top
View user's profile Send private message
prakash271082

New User


Joined: 09 Sep 2005
Posts: 53

PostPosted: Wed Sep 12, 2007 12:37 pm
Reply with quote

Hi Vinay,

You could consult your system admin and ask him / her to increase the timeframe for dataset to get migrated. As said by one of our friend, normally the dataset migration time will atleast be a week of time. So that if you are running the job with a frequency of 2 days there won't be any problem for you.
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 How to get a stack trace on a looping... ABENDS & Debugging 5
No new posts Calling Java method from batch COBOL ... COBOL Programming 5
No new posts How to create a list of SAR jobs with... CA Products 3
No new posts Help in Automating Batch JCL jobs mon... JCL & VSAM 3
No new posts Submit multiple jobs from a library t... JCL & VSAM 14
Search our Forums:

Back to Top