|
View previous topic :: View next topic
|
| Author |
Message |
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
Can anybody tell how the background application works
Like HRECALL is an utility which will recall the migrated datasets. How it could be done
Thanks,
Ugandar |
|
| Back to top |
|
 |
saiprasadh
Active User
Joined: 20 Sep 2006
Posts: 154
Location: US
|
|
|
|
Hi Ugandar,
A background Job will be submitted if you type HRECALL against a dataset name, Correct me if i am wrong.
Thanks
Sai |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
No, a background job will not be submitted if you type HRECALL against a dataset. HRECALL is a HSM subsystem command which can be entered from any active TSO session, either at the terminal, in batch, or when a process detects that a dataset to be opened is migrated.
You can load your HRECALL statements into a dataset and either submit a batch TSO session to process them, or just type EX next to the dataset in 3.4 |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| expat wrote: |
| No, a background job will not be submitted if you type HRECALL against a dataset. HRECALL is a HSM subsystem command which can be entered from any active TSO session, either at the terminal, in batch, or when a process detects that a dataset to be opened is migrated. |
This was a great information for me to know about.
| Quote: |
| You can load your HRECALL statements into a dataset and either submit a batch TSO session to process them, or just type EX next to the dataset in 3.4 |
At my site I use HR. |
|
| Back to top |
|
|
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
Can anyone please give me the jcl for this..
Thanks,
Ugandar |
|
| Back to top |
|
|
saiprasadh
Active User
Joined: 20 Sep 2006
Posts: 154
Location: US
|
|
|
|
Hi Ugandar,
The JCL to execute the HRECALL command in Batch
| Code: |
//RECALL EXEC PGM=IKJEFT01,DYNAMNBR=20,TIME=(9)
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
HRECALL 'mention the dataset name's common part ' NOWAIT
/* |
For e.g.
| Code: |
You want to recall these four datasets.
abc.aaa
abc.abd
abc.ddd
abc.ttt |
then against SYSTSIN, you can mention
HRECALL 'abc.**'
Thanks
Sai |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
Now, I'm bit confused here, according to expat 'no JOB'll be submitted when one use HR or EX' , while JCL posted by 'sai' is working for me.
JCL from 'sai' & commands 'HR & EX' have some relation in them or are they totally different altogther? If they have nothing to do with each other, then what happens at system level when one issue the command 'HR or EX' ?
Please advise. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
I believe HR and EX are extensions or aliases for HRECALL. They are site specific. They (as well as HRECALL) can run online.
The JCL provided is if someone wants to do the recall in batch and not from the terminal. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Anuj,
The example shown is a batch TSO session, PGM=IKJEFT01, so you will need to submit the job for it to run. This is just a batch version of issuing the HRECALL command in 3.4, but is useful when you have many recalls to process.
You could put all of your HRECALL commands into a dataset and in 3.4 just type EX (EXECUTE) against it, and that will be the same as you sitting there doing a HRECALL against each dataset individually.
I believe that EX is a universal command, which works against PDS members or PS datasets. It's worked at every shop that I have. |
|
| Back to top |
|
|
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
Thank you very much saiprasad...
Actually what iam going to do is I have to do string search in all the members of a pds
In normal mainframe itself we are having 3.14 option but this will do only for our personal datasets
Unauthorized or production datasets will not be opened...
so we are using one tool to do string search... but this will not work at the background... the production pds contains approximately 5000 members, so we have to wait till the process goes
I am planning to run this in batch... I think the jcl for HRECALL which is given by saiprasad will cause a root to start my job
Thanks,
Ugandar |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Thanks Dick.
Thanks expat.
| expat wrote: |
| I believe that EX is a universal command, which works against PDS members or PS datasets. It's worked at every shop that I have. |
I tried to use 'EX' command at my site, got the follwoing messages:
| Code: |
ARC1020I DFSMSHSM IS RECALLING FROM DASD DSN=HLQ.EP.BBAL.TOEP600.C.G2621V.J
UN14, YOU MAY CONTINUE THE RECALL IN THE BACKGROUND AND FREE YOUR TSO SESSION BY PRESSING THE ATTENTION KEY |
Pressed enter, next message shwon is:
| Code: |
| A command entered or contained in a CLIST has invalid syntax. |
Whilst when I used 'HR' command on some other migrated dataset, first message was:
| Code: |
| ARC1007I RECALL REQUEST 00110335 SENT TO DFSMSHSM |
Pressed enter, message shown was:
| Code: |
| ARC1000I HLQ.EP.EPD615.PGINV.SRT.F.NOV29.C128I RECALL PROCESSING ENDED*** |
What should I conclude ! 
P.S.: Above DSNs are of nature PS (QSAM).
| ug123 wrote: |
| In normal mainframe itself we are having 3.14 option but this will do only for our personal datasets |
From where you come to know about this? & I think 3.14 option is:
| Code: |
| 14 Search-For Search data sets for strings of data (Standard Dialog) |
& used for search & not for recalling migrated datasets.
| ug123 wrote: |
| Unauthorized or production datasets will not be opened... |
You need to have a proper access of production datasets before you recall them.
By the way, is there something known as abnormal mainframe ? 
| ug123 wrote: |
| In normal mainframe itself |
|
|
| Back to top |
|
|
mark_walker
New User
Joined: 24 Sep 2007
Posts: 1
Location: Lincoln, UK
|
|
|
|
| Anuj D. wrote: |
I tried to use 'EX' command at my site, got the follwoing messages:
| Code: |
ARC1020I DFSMSHSM IS RECALLING FROM DASD DSN=HLQ.EP.BBAL.TOEP600.C.G2621V.J
UN14, YOU MAY CONTINUE THE RECALL IN THE BACKGROUND AND FREE YOUR TSO SESSION BY PRESSING THE ATTENTION KEY |
|
Hi Anuj - HSM appears to be set to run in the foreground at your site, which will wait until the dataset is recalled before processing the command against it, in this case EX (for EXECUTE).
Some sites will have a patch in the HSM parms (ARCCMDxx) to release control back to the user. This means you will get a similar message to above but you will be informed to try again when the dataset has been recalled.
By typing in EX the system will first process the HRECALL command, then the EX command.
| Anuj D. wrote: |
]
Pressed enter, next message shwon is:
| Code: |
| A command entered or contained in a CLIST has invalid syntax. |
|
The reason that you received the above message is that the second part of the process (the EXecute) is being carried out against the dataset recalled. EXecute can only generally be used with PS datasets or PDS members that contain CLIST or REXX code. I suspect that the dataset that you issued the EX against was probably JCL.
| Anuj D. wrote: |
]
Whilst when I used 'HR' command on some other migrated dataset, first message was:
| Code: |
| ARC1007I RECALL REQUEST 00110335 SENT TO DFSMSHSM |
Pressed enter, message shown was:
| Code: |
| ARC1000I HLQ.EP.EPD615.PGINV.SRT.F.NOV29.C128I RECALL PROCESSING ENDED*** |
What should I conclude !
|
HR or HRECALL is a sub-command to HSM itself and purely instructs HSM to recall the dataset and doesn't process it any further.
To summarize -
to purely recall a dataset - use HR or HRECALL
to carry out additional actions against a dataset issue the relevant command: E, B, V, M, EX etc
Hope this helps.
Mark |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi Mark & Welcome to the forums & thanks for the reply 
Got some queris to ask:
1.
| Quote: |
| Some sites will have a patch in the HSM parms (ARCCMDxx) to release control back to the user. |
From where can I know about this?
2.
| Quote: |
| By typing in EX the system will first process the HRECALL command, then the EX command. |
Ok, but what 'EX' tells the system to do?
3.
| Quote: |
| can only generally be used with PS datasets or PDS members that contain CLIST or REXX code. |
Din't get this, why such a discrimination ? |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
1) In the parameter member used in HSM start up, although the patch can also be applied dynamically, in which case you won't be able to see it.
2) EX tells the system to EXECUTE the selected dataset.
3) The contents of the EXecuted dataset can be IDCAMS statements, HRECALL statements, or any other type of executable statement. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Thanks expat. Will get back to you in case of any further concern/s. |
|
| Back to top |
|
|
manugeorge2004
New User
Joined: 17 Jun 2009
Posts: 38
Location: Denver
|
|
|
|
When I submit the job..it sends the RECALL results to TSO as messages.
How can it be directed to SYSOUT or a dataset. I want to implement this is a job that can be executed via CA7 |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Why does someone believe a job needs to be scheduled to recall migrated data? |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| dick scherrer wrote: |
Hello,
Why does someone believe a job needs to be scheduled to recall migrated data? |
For the same reason that it is thought appropriate to revive a thread after three years? |
|
| Back to top |
|
|
manugeorge2004
New User
Joined: 17 Jun 2009
Posts: 38
Location: Denver
|
|
|
|
I have a requirement where we are migrating from mainframes to another technology. But we still need to keep some datasets for 10 years for audit purpose. We need a batch process to touch these datasets every month to keep them from rolling off.
I thought of having IEFBR14 step with DISP=SHR. But we have limitations to this. IKJEFT01 will help us have the list of datasets in a PARM file. We can add or remove datasets from this list whenever we want it. IEFBR14 will require PROC changes ( have to go through installation procedures every time I want to add or remove the datasets) |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Why not simply back these datasets up to cart twice (prefereably "fat carts" - 3590) and hold them for the required amount of time.
If/when they are actually to be read, copy the needed data back to dasd and delete when done with the special request. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
rolling off from where... the table maybe
anyway something looks strange, any organization with long range archival needs
has already taken care of the expiration dates so no need for a monthly <touch>
and, just curious, after Your organization has migrated to the new technology
how is it going to process old data if some audit wants to check ??? |
|
| Back to top |
|
|
|
|
