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

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

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' ?

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.

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:

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)