|
View previous topic :: View next topic
|
| Author |
Message |
sanupadh
New User
Joined: 29 Jun 2010
Posts: 11
Location: chennai
|
|
|
|
Hi All,
one job is abended because job fails to recall migrated dataset
I want to know do we add step in job to recall that dataset first and later execute remainnig steps.
please provide me the jcl step.
Thanks |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| one job is abended because job fails to recall migrated dataset |
and that abend code is???? |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| sanupadh wrote: |
| please provide me the jcl step. |
Immediately after the 750 euros hits my bank account.
This has been discussed on the forum many times, and we are quite lucky as forums go because we happen to have a SEARCH button. |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| However, you should fix the cause - you are migrating datasets too soon. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Nic, Shhhhhhhhhhhh, you're curtailing my income  |
|
| Back to top |
|
|
sanupadh
New User
Joined: 29 Jun 2010
Posts: 11
Location: chennai
|
|
|
|
Actually Job runs once in a month and this month It got abended because
Not able to recall the dataset.
after some time when I resubmit the job by changing msgclass parameter
it ran fine.
someone suggested me to add one more step in the beginning of the job so that I recall the dataset first and later executes remaining step.
I cant increase the timing of migration. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
I can not for the life of me see how changing the MSGCLASS parameter has any effect at all.
As I have said previously, search the forum, perhaps using HRECALL WAIT as keywords.
Google definitely links to this forum with the answer to your question. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
on our machine, they migrate ds after 3 days - which makes mondays a lot of fun.
I wrote a rexx script that generates an iefbr14 for all of my datasets,
with a disp=shr.. before submitting, I cull those ds's that I will probably not use.
i made the mistake of submitting the job with a CLASS = 20 second jobs,
the recalls required nearly an hour (wall clock), though the job did not abend due to timeout, did tie up a job class much too long.
since then I submit under a CLASS = nolimit.
never have experienced a job timing out due to migration recall.
| Quote: |
| because job fails to recall migrated dataset |
I think the TS's was timed out due to another reason.
i base that on the ts's comment about msgclass having an effect,
and not knowing enough about JCL to create his own step to effectively 'recall' a migrated ds. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Dick, if you do need to do it, it would probably be better to generate the HRECALL cards with NOWAIT as this will queue the recall requests in HSM, and HSM is clever enough to group the recalls by tape so that each ML2 volume is mounted only once. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| thx expat. will make the change. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Dick, will PM you the code that I use for multiple functions in a few minutes.
If you're lucky you'll be able to understand my ramblings in the JCL section |
|
| Back to top |
|
|
yuvrajdutta
New User
Joined: 13 Jul 2009
Posts: 40
Location: India
|
|
|
|
We personally had a requirement of RECALLING hundred's of datasets once and we followed the below procedure:
SAVE a DSLIST (3.4) or use a REXX to so the same... I personally did a
Which resulted in the DSLIST(entire 3.4) listing being saved into a DATASET like <MY_USER_ID>.HELLO.DATASETS.
Since all our migrated datasets were in MIGRAT1 state(i believe there are other types of MIGRATION's also) we had used the following JOB to create RECALL statements in BATCH and SUBMIT the same too.
| Code: |
//SORTDATA EXEC PGM=SORT,REGION=4096K,TIME=1440,COND=(4,LT)
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SORTIN DD DSN=<MY_USER_ID>.HELLO.DATASETS,DISP=SHR
//SORTOUT DD DSN=&&C,DISP=(NEW,PASS),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// SPACE=(TRK,(200,200)),UNIT=SYSDA
//SYSIN DD *
INCLUDE COND=(46,7,CH,EQ,C'MIGRAT1')
SORT FIELDS=COPY
OUTFIL FNAMES=SORTOUT,IFOUTLEN=80,
IFTHEN=(WHEN=INIT,
BUILD=(C'''',1,45,C'''',80:X)),
IFTHEN=(WHEN=INIT,
OVERLAY=(1:1,80,SQZ=(SHIFT=LEFT)))
/*
//SORTDATA EXEC PGM=SORT,REGION=4096K,TIME=1440,COND=(4,LT)
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SORTIN DD DSN=&&C,DISP=SHR
//SORTOUT DD DSN=&&A,DISP=(NEW,PASS),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// SPACE=(TRK,(200,200)),UNIT=SYSDA
//SYSIN DD *
SORT FIELDS=COPY
OUTFIL FNAMES=SORTOUT,
BUILD=(C'HRECALL ',1,47,C' NOWAIT',80:X)
/*
//RECALL EXEC PGM=IKJEFT01,DYNAMNBR=20,TIME=(9),COND=(4,LT)
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD DSN=&&A,DISP=SHR
|
Hope this helps.. |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
Hello,
You could also accomplish the above with dataset mask for HRECALL command,
So a dataset mask possibly would make it a single step job, with the IKJEFT01 alone.
Example:
| Code: |
| TSO HRECALL 'WELLS.SAS.*.DATABASE' WAIT/NOWAIT |
Hope it helps. |
|
| Back to top |
|
|
|
|
