Trapping HSM output in REXX

[Nork]

I'm in the process of trying to automate file migration using DFHSM via
REXX. Does
anyone know of a way to trap output from 'HQUERY DS(HLQ1.HLQ2)' and 'HSEND Q
W' HSM commands? Obviously I've tried using OUTTRAP with no success.

Thanks in advance for any help.

[Gilbert Saint-flour]

On 12 Oct 2000 at 11:56, "Nork" <pe...@klinsmann.prestel.co.uk> said:

>I'm in the process of trying to automate file migration using DFHSM via
>REXX. Does anyone know of a way to trap output from
>'HQUERY DS(HLQ1.HLQ2)' and 'HSEND Q W' HSM commands?
>Obviously I've tried using OUTTRAP with no success.

Replies to HSM commands often are displayed via cross-memory TPUTs from
the HSM address space, so you can't trap them. Have you tried Session
Manager?

Gilbert Saint-flour
Automated Migration Services
http://members.home.net/gsf/

[Don Isenstadt]

I think you will have to put the output of the commands to a dataset.. The
HSM output can't be trapped as far as I know...

Don Isenstadt
Parker Hannifin Corporation
Cleveland, Ohio 44124-4141
Tel: 216-896-2192
M/S-EGDC01

[Stephen E. Bacher]

>I'm in the process of trying to automate file migration using DFHSM via
>REXX. Does anyone know of a way to trap output from
>'HQUERY DS(HLQ1.HLQ2)' and 'HSEND Q W' HSM commands?
>Obviously I've tried using OUTTRAP with no success.

If you have access to a console automation product, you might try
issuing the HSM commands as operator commands and capturing the
console responses. Perhaps GETMSG et al. can help. I haven't
tried this, so I don't know.

- seb

[PC]

I did it by using the ODSN parameter on the HSM command, so the output gets
sent to a dataset.
This is asynchronous so the REXX has to wait for it to become available.
I use a "do forever" loop and wait for the TSO ALLOC of that dataset to
return a non-zero.
To cut down of rampant runaround, I use the WAIT function to pause for (say)
ten seconds before checking for the dataset.

It works quite well.

The only little glitch comes when the userid which issues the command
doesn't have the correct HSM authority. There's no way the dataset gets
created and the loop just keeps running.

Hope this helps
Phil

Stephen E. Bacher wrote in message
<2000101217...@support9.draper.com>...

[yri...@attglobal.net]

the 'do forever' way can (should) be avoided by using the 'WAIT'
parameter of the hsend command.
that parm causes hsend to wait untill completion of the command
before giving the hand back.
it does not cure the authority problem, though...

[Finbar]

You see?
THAT'S why I am using this newsgroup.

I didn't even know about the WAIT subparameter on the HSM call....

Thanks very much!

<yri...@attglobal.net> wrote in message news:1103_971828723@titine...

[guill...@gmail.com]

Wont be easier to try with the ODS parm? Maybe i misunderstood the question, but if you use for example: HSEND list CP(.......) ods(dataset.name)
Then the output goes to dataset.name