Ian,

Again ... as both Phil and Shimon have indicated in more detail ... you
should be able to do what you want with V/Seg-Plus.  

And, again, because you license CA's VM:Spool you also have a license
for CA's V/Seg-Plus which is a "feature" of CA's VM:Spool.

JR (Steven) Imler
CA
Senior Software Engineer
Tel:  +1 703 708 3479
Fax:  +1 703 708 3267
[EMAIL PROTECTED]


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Shimon Lebowitz
Sent: Tuesday, May 01, 2007 07:11 AM
To: [email protected]
Subject: Re: Peeking other machine's spool files (ala vm:spool)

On 1 May 2007 at 5:34, Phil Smith III wrote:

> "Ian S. Worthington" <[EMAIL PROTECTED]> wrote:
=== snip ===
> >?Also we'd rather like to be able to have a programming interface
> >which can read the spool files, which is another thing vm:spool
> >doesn't seem able to do.
> 
> >Is anyone aware of an interface and/or cure for these?
> 
> V/SEG-PLUS has a better SPOOL browser (he said modestly) that uses
> Michael Johnson's excellent SHOW as a driver.  It works currently with
> screens up to 64 lines, and could do more if one wanted to do some
> minor but irritating surgery.  It will allow you to use a programming
> interface (a SHOW macro) to read files, too.  
=== snip ===
> ...phsiii
> 

In order to use a show macro in a programmed solution
(which we do a LOT of, for files in the RDR of the SVM)
for spool files NOT in the SVM's RDR, I think one
would need a linemode command on the order of
  VSPOOL SHOW <userid> <queue> <spid> <macroname>

I admit to not going to check the docs right now, but I do 
not remember such a command. Am I wrong?

Shimon

-- 
**********************************************************************
**
Shimon Lebowitz                mailto:[EMAIL PROTECTED]
VM System Programmer           .
Israel Police National HQ.     http://www.poboxes.com/shimonpgp
Jerusalem, Israel              phone: +972 2 542-9877  fax: 542-9308
**********************************************************************
**

Reply via email to