Sorry I have it in the main clist
When I put it In the clist that executes the AT command it works now my next
step it
To see if I can issue test subcommands based
On the clist variables value
Thanks everyone so far
> On Jul 5, 2016, at 3:39 PM, Walt Farrell wrote:
>
>> On Tue, 5 Jul 2016
On Tue, 5 Jul 2016 15:03:02 -0400, Joe Reichman wrote:
>The SYSOUTTRAP will trap TEST OUTPUT but *ONLY* at the beginning of *TEST*
>Coding AT +148 ( EX MY.CLIST(TRAP))
>
>Where the clist TRAP contain SYSOUTTRAP and SYSOUTLINE to trap output won't
>work
I would expect it to be able to trap the
U] On Behalf
Of Bill Godfrey
Sent: Monday, July 4, 2016 2:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
The clist in my first post was run on z/OS 2.2.
The 4-character string "amp:" if present, is an artifact of the listserv web
interface and shoul
t in Clist:
>>>>>
>>>>> SET SYSOUTTRAP = 600
>>>>> LISTALC STATUS
>>>>> SET SYSOUTTRAP = 0
>>>>> SET &LINE_COUNT = &SYSOUTLINE
>>>>> SET DSN = &STR(&&SYSOUTLINE&I)
>
NT = &SYSOUTLINE
>>>> SET DSN = &STR(&&SYSOUTLINE&I)
>>>> ...
>>>>
>>>> Output always goes into complex variable &SYSOUTLINE. Lines are identified
>>>> by the value of &I.
>>>>
>>>> The real difference fo
> captured from the original OUTTRAP.
>>>
>>> .
>>> .
>>> .
>>> J.O.Skip Robinson
>>> Southern California Edison Company
>>> Electric Dragon Team Paddler
>>> SHARE MVS Program Co-Manager
>>> 323-715-0595 Mobile
>
> When Rexx switches into subcommand mode, I don't think output is captured
>> from the original OUTTRAP.
>>
>> .
>> .
>> .
>> J.O.Skip Robinson
>> Southern California Edison Company
>> Electric Dragon Team Paddler
>> SHARE MVS Pro
From what little I remember going over the code I suspect that a lot of TEST
uses TPUT which I belive is not capturable .
I *THINK* TSO Session manager does its part of TSO and its free so why not use
the great product?
Ed
> On Jul 3, 2016, at 7:22 PM, Paul Gilmartin
> <000433f07816-dmarc
On Sun, 3 Jul 2016 20:19:04 +, J R wrote:
>"I believe OUTTRAP catches lines written by PUTLINE(?) but not by TPUT.
>Why must there be two of them? If TPUT must be retained for comaptibility,
>couldn't it be made simply a wrapper for PUTLINE, providing uniform behavior?"
>
>TPUT is specificall
Rupert Reynolds in a earlier Post seemed to indicate that trapping TEST output
to variables was possible but I'm not sure
> On Jul 3, 2016, at 6:01 PM, Andy Wood wrote:
>
>> On Sun, 3 Jul 2016 09:32:18 -0400, Joseph Reichman
>> wrote:
>>
>> I am basically trying to save the output of test
On Sun, 3 Jul 2016 09:32:18 -0400, Joseph Reichman
wrote:
>I am basically trying to save the output of test i.e.
>Output of a test list command into variables and compare them and based on
>the result do a "AT"
>breakpoint command
>
>Thanks
>
You do know that the LIST subcommand output can
"I believe OUTTRAP catches lines written by PUTLINE(?) but not by TPUT.
Why must there be two of them? If TPUT must be retained for comaptibility,
couldn't it be made simply a wrapper for PUTLINE, providing uniform behavior?"
TPUT is specifically for terminal output. PUTLINE is more generalized
>
> Enter Command (? for help)
>
>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-753
o-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Joseph Reichman
> Sent: Sunday, July 03, 2016 9:54 AM
> To: IBM-MAIN@LISTSER
: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Joseph Reichman
> Sent: Sunday, July 03, 2016 9:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
>
> You use SYSOUTTRAP in Rexx thought it's a
@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Joseph Reichman
Sent: Sunday, July 03, 2016 9:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
You use SYSOUTTRAP in Rexx thought it&
On Sun, 3 Jul 2016 09:32:18 -0400, Joseph Reichman wrote:
>I am basically trying to save the output of test i.e.
>Output of a test list command into variables and compare them and based on
>the result do a "AT"
>breakpoint command
>
As a last resort, you might try a terminal emulator that has
gt;
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Joseph Reichman
> Sent: Sunday, July 03, 2016 9:18 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
>
> I d
5 Office
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Joseph Reichman
Sent: Sunday, July 03, 2016 9:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
I don't think the clist
I don't think the clist SYSOUTTRAP/SYSOUTTRAP
Work to trap TEST output maybe Rexx OUTTRAP
does didn't try that
> On Jul 3, 2016, at 9:16 AM, Rupert Reynolds wrote:
>
> TEST behaves differently (or did, when I used it in the 90s) in CLIST. As I
> remember it, the CLIST that starts TEST keeps r
I am basically trying to save the output of test i.e.
Output of a test list command into variables and compare them and based on the
result do a "AT"
breakpoint command
Thanks
> On Jul 3, 2016, at 9:16 AM, Rupert Reynolds wrote:
>
> TEST behaves differently (or did, when I used it in the 90
TEST behaves differently (or did, when I used it in the 90s) in CLIST. As I
remember it, the CLIST that starts TEST keeps running for the TEST session,
so the next line of a CLIST after the TEST command itself can be
subcommands such as AT and GO.
As I remember it, there were important differences
Thanks so much 🤗
Joe Reichman
8045 Newell St Apt 403
Silver Spring MD 20910
Home (240) 863-3965
Cell (917) 748 -9693
> On Jul 3, 2016, at 7:38 AM, Mike Shorkend wrote:
>
> I am not sure about CLIST but for REXX, the following will place each
> output line into a the stem variable 'test'.
>
>
I am not sure about CLIST but for REXX, the following will place each
output line into a the stem variable 'test'.
/* REXX */
x=outtrap('test.')
push "end"
PUSH "go"
PUSH "at +0"
"test 'sys1.linklib(iefbr14)'"
say "number of trapped lines is" test.0
do i = 1 to test.0
say test.i
end
Hi
Does any one know if capturing TEST output
Into CLIST variables is possible
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
25 matches
Mail list logo
