AW: Re: Short description of system address spaces

[Peter Hunkeler]

>I see that Mike responded with a long list of names, which includes (I 
>believe) a mixture of system address spaces and started tasks. That led me to 
>wonder whether you were using "system address spaces" as a technical term 
>(meaning things like *MASTER* and SMF and DUMPSRV but not things like RMF, 
>SDSF, RACF, etc.) or whether you really meant it as a generic term that would 
>encompass normal started tasks,



The former, Walt. And to make it clear, I do not need a mere list of names; I 
know then. I looking for a short description of those.


The z/OS Basics redbook that Mike pointed to is indeed a known good starting 
point. But it does not have a list of these adrdress spaces.


Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Edward Gould]

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-requ...@listserv.ua.edu> wrote:
> 
> 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 specifically for terminal output.  PUTLINE is more generalized and 
>> issues TPUT if the current output is destined for the terminal.
>> 
> It should be the other way around.  Shmuel on occasion mentioned (e.g.):
>https://listserv.ua.edu/cgi-bin/wa?A2=ibm-main;e78c1cac.1306
> 
>> What went wrong?
> 
>It started early: George Mealy is alleged to have called it "The rape
>of the design integrity of OS/360" and blamed it on a lack of
>standards enforcement.
> 
> By the OS/360 paradigm, TSO should have written to SYSTSPRT and
> read from SYSTSIN, which could have been allocated to TERMINAL for
> interactive sessions or other data sets for logging.  A subsystem could
> have been provided to "tee" SYSTSPRT to both TERMINAL and another
> data set for interaction with logging.
> 
> -- gil
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[J R]

"
We programmers just tend to be highly nervous packrats, and we should probably 
get over it. "

Guilty as charged!  I still have tree-sourced /360 manuals that I had in the 
'60s.  Every once in a while I appease my wife and grudgingly put one or two 
out for recycling.

Sent from my iPhone

On Jul 3, 2016, at 20:40, Jack J. Woehr > 
wrote:

J R wrote:
And, even if I eventually do get everything downloaded, I have no idea how to 
organize it

I'm more or less a compulsive PDF downloader (and before that a compulsive 
bookshelf collector, still have sets from the 1990's)
but recently I've made my peace with IBM Knowledge Center. They're going to 
keep the info available, or if they don't, nobody
will be able to service their customers, and it's over.

We programmers just tend to be highly nervous packrats, and we should probably 
get over it. It's a grand waste of time downloading
manuals we might need. I grab the ones I'm using and get the rest when I want 
them.

--
Jack J. Woehr

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[Jack J. Woehr]

J R wrote:

And, even if I eventually do get everything downloaded, I have no idea how to 
organize it


I'm more or less a compulsive PDF downloader (and before that a compulsive bookshelf collector, still have sets from the 
1990's)
but recently I've made my peace with IBM Knowledge Center. They're going to keep the info available, or if they don't, 
nobody

will be able to service their customers, and it's over.

We programmers just tend to be highly nervous packrats, and we should probably get over it. It's a grand waste of time 
downloading

manuals we might need. I grab the ones I'm using and get the rest when I want 
them.

--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Paul Gilmartin]

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 specifically for terminal output.  PUTLINE is more generalized and 
>issues TPUT if the current output is destined for the terminal.
> 
It should be the other way around.  Shmuel on occasion mentioned (e.g.):
https://listserv.ua.edu/cgi-bin/wa?A2=ibm-main;e78c1cac.1306

>What went wrong?

It started early: George Mealy is alleged to have called it "The rape
of the design integrity of OS/360" and blamed it on a lack of
standards enforcement.

By the OS/360 paradigm, TSO should have written to SYSTSPRT and
read from SYSTSIN, which could have been allocated to TERMINAL for
interactive sessions or other data sets for logging.  A subsystem could
have been provided to "tee" SYSTSPRT to both TERMINAL and another
data set for interaction with logging.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[J R]

I'm fine with PDFs (KC not so much) but, despite several posts of where/how to 
download all z/OS manuals in one fell swoop, I've yet to manage that feat to a 
mobile device.  And, even if I eventually do get everything downloaded, I have 
no idea how to organize it so that it's useful.  

Sent from my iPhone

> On Jul 3, 2016, at 18:49, Jack J. Woehr  wrote:
> 
> Charles Mills wrote:
>> I can understand the move away from BookManager (as much as some of us loved 
>> it). It was a proprietary technology and I am sure expensive to maintain. 
>> But PDF is an industry standard. The technology is maintained by Adobe.
> 
> The PDF's are all still there.
> 
> -- 
> Jack J. Woehr

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[Charles Mills]

True, but it seems like they are hoping we won't find them. 

Seriously, the direction seems to be away from PDF and to -- what would you 
call it? -- proprietary Web?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jack J. Woehr
Sent: Sunday, July 03, 2016 3:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Knowledge Centre

Charles Mills wrote:
> I can understand the move away from BookManager (as much as some of us loved 
> it). It was a proprietary technology and I am sure expensive to maintain. But 
> PDF is an industry standard. The technology is maintained by Adobe.

The PDF's are all still there.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[Jack J. Woehr]

Charles Mills wrote:

I can understand the move away from BookManager (as much as some of us loved 
it). It was a proprietary technology and I am sure expensive to maintain. But 
PDF is an industry standard. The technology is maintained by Adobe.


The PDF's are all still there.

--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[Charles Mills]

Is the below actually relevant to the situation? There must be some members 
here under thirty. Do YOU like Knowledge Center? Does anyone know any young 
WebSphere or Java developers? (Yes, I realize the two technologies are not 
exclusive.)? Do THEY like Knowledge Center?

I can understand the move away from BookManager (as much as some of us loved 
it). It was a proprietary technology and I am sure expensive to maintain. But 
PDF is an industry standard. The technology is maintained by Adobe.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jack J. Woehr
Sent: Saturday, July 02, 2016 8:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Knowledge Centre



But I think IBM is reaching out to a younger market. We're a bunch of old 
farts. This is a move to mobile. I remember sitting around IBM Boulder 20 years 
ago listening to a 67-year-old and excellent IBM VM programmer rant about how 
useless GUIs are. Now he's gone and I'm 64.

You gotta make way for youth, they only know what they know. We can adapt to 
their world. Or retire. But complaining is self-abuse.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

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 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 be directed to a data set via 
> "PRINT(...)" ?
> 
> That is something I used to do often, but never had occasion to try it from 
> CLIST or REXX. It might perhaps give you some other options. 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Andy Wood]

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 be directed to a data set via 
"PRINT(...)" ?

That is something I used to do often, but never had occasion to try it from 
CLIST or REXX. It might perhaps give you some other options. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[J R]

"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 and 
issues TPUT if the current output is destined for the terminal.

I suspect the original perception may have been that TEST would have always 
been interactive, ie. driven directly via a terminal rather than some kind of 
script.

Sent from my iPhone

On Jul 3, 2016, at 13:45, Paul Gilmartin 
<000433f07816-dmarc-requ...@listserv.ua.edu>
 wrote:

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 a logging facility.

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?


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 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 in SYSOUTTRAP as well. I
had a small collection of REXX and CLIST that could be run in TEST to do
things such as single step and redisplay registers, storage, code, PSW and
so on, almost half way to a full screen debugger.

I found the differences meant I had to mix REXX and CLIST to get the job
done.

I believe this behavior is called "modal".  CLIST (but not Rexx) interfaces
similarly with (non-ISPF) Edit.  Perhaps others?  Likewise CMS EXEC (but
not EXEC2 nor Rexx) interacts similarly with old CMS (non-X-)EDIT.  And
Rexx sorely lacks any facility for instream data.

-- gil


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

Ok thanks 

 I wonder about TEST

When I looked at the "AT" subcommand 
TEST allows you to enter other subcommands after 
The paren I.E. AT +0 (ex 'myclist' ; L 1R?)

There is one caveat the doc says the clist may not be the first thing executed 
so..IF I had a SYSOUTTRAP/SYSOUTLINE in the clist it may not capture the L 
1R?




> On Jul 3, 2016, at 3:54 PM, Jesse 1 Robinson  wrote:
> 
> Poked around my own code and found one subcommand example, which works. SPACE 
> is a TSO command that allows a number of subcommands. SPACE stays in control 
> until END. One subcommand is Vxx, which display info for all volumes 
> beginning with xx. This Rexx captures all output and displays at the end. 
> Notice that subcommands must be QUEUEd in advance of the SPACE command 
> itself. 
> 
> x = OUTTRAP("cmdl.")   
> PROFILE   PROMPT   
> QUEUE "?" /* help */ 
> QUEUE "vSYSX"  
> QUEUE "END"
> "SPACE"
> DO i = 1 TO cmdl.0 
>  SAY cmdl.i   
> END
> 
> Output:
> 
> Enter Command  (? for help)   
>  
> All  List data on all online disks
>  
> Devices  List data on all devices 
>  
> End  End program  
>  
> Fxx  List data on device with volser 'XX' 
>  
> GnameList data on generic unit 'name' 
>  
> TEDSKIP  generic unit 'name' is SYSDX 
>  
> List List the generic unit names  
>  
> Offline  List data on both online and offline disks   
>  
> Uxxx List data on device with unit ADDR 'xxx' 
>  
> Uxxx,nn  List nn devices starting from ADDR 'xxx' 
>  
> Uxxx-yyy List devices from ADDR 'xxx' to 'yyy'
>  
> S OFF/ON Print sum of free cylinders and tracks   
>  
> $Toggle LSPACE option on or off   
>  
> ?Print this list  
>  
> Help Show the meaning of the fields   
>  
> Enter Command  (? for help)   
>  
> Cylinders-  ---Tracks---  
> 
> Addr Volume  Device  Atr Mnt Total  Free Contig  Free  Contig  Ext.  Usect 
> Vtoc
> 6500 SYSXL1  3390-3  SHR PVT 03338 02359 02147   00018 0   4  0007 IX 
>  
> 6508 SYSXL2  3390-3  SHR PVT 03338 02441 02218   0 0   2  0001 IX 
>  
> 6700 SYSXL3  3390-3  SHR PVT 03338 01001 01001   0 0   1  0001 IX 
>  
> 6708 SYSXL4  3390-3  SHR PVT 03338 02216 02204   0 0   2  0002 IX 
>  
> 7309 SYSX04  3390-3  SHR PVT 03338 00199 00135   00029 0   00010  0217 IX 
>  
> 7801 SYSX01  3390-3  SHR PVT 03338 00385 00041   00443 0   00095  0103 IX 
>  
> 7A0A SYSX06  3390-3  SHR PVT 03338 02999 02999   5 0   2  0006 IX 
>  
> 7B02 SYSX02  3390-3  SHR PVT 03338 6 3   00054 0   00010  0005 IX 
>  
> 7C12 SYSX03  3390-3  SHR PVT 03338 00026 2   00464 00013   00099  0260 IX 
>  
> 7E02 SYSX05  3390-3  SHR PVT 03338 01149 00176   00276 0   00076  0015 IX 
>  
> 
> 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-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 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
> 
> I have tried to capture test subcommand output I.E list under clist with no 
> success Dont  know about Rexx I am now thinking the AT subcommsnd in TEST 
> leaves you the ability to to exec a CLIST as part of the parameters  maybe 
> I'll try the SYSOUTTRAP/SYSOUTLINE in that instance 
> 
> 
> 
>> On Jul 3, 2016, at 1:51 PM, Jesse 1 Robinson  wrote:
>> 
>> I was sloppy. AFAIK the functions are equivalent.  In Rexx, you use this 
>> syntax: 
>> 
>> x = OUTTRAP("cmdl.")
>> "LISTALC STATUS"
>> line_count = cmdl.0
>> dsn = cmdl.i
>> ...
>> 
>> Output goes into the named array. Lines are identified by the value of i. 
>> 
>> Equivalent in Clist: 
>> 
>> SET SYSOUTTRAP = 600 
>> LISTALC STATUS   
>> SET SYSOUTTRAP = 0   
>> SET _COUNT = 
>> SET DSN = (&)
>> ...
>> 
>> Output always goes into complex variable  Lines are identified 
>> by the value of 
>> 

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Jesse 1 Robinson]

Poked around my own code and found one subcommand example, which works. SPACE 
is a TSO command that allows a number of subcommands. SPACE stays in control 
until END. One subcommand is Vxx, which display info for all volumes 
beginning with xx. This Rexx captures all output and displays at the end. 
Notice that subcommands must be QUEUEd in advance of the SPACE command itself. 

x = OUTTRAP("cmdl.")   
PROFILE   PROMPT   
QUEUE "?" /* help */ 
QUEUE "vSYSX"  
QUEUE "END"
"SPACE"
DO i = 1 TO cmdl.0 
  SAY cmdl.i   
END

Output:

Enter Command  (? for help)
All  List data on all online disks 
Devices  List data on all devices  
End  End program   
Fxx  List data on device with volser 'XX'  
GnameList data on generic unit 'name'  
 TEDSKIP  generic unit 'name' is SYSDX  
List List the generic unit names   
Offline  List data on both online and offline disks
Uxxx List data on device with unit ADDR 'xxx'  
Uxxx,nn  List nn devices starting from ADDR 'xxx'  
Uxxx-yyy List devices from ADDR 'xxx' to 'yyy' 
S OFF/ON Print sum of free cylinders and tracks
$Toggle LSPACE option on or off
?Print this list   
Help Show the meaning of the fields
Enter Command  (? for help)
 Cylinders-  ---Tracks---  
   
Addr Volume  Device  Atr Mnt Total  Free Contig  Free  Contig  Ext.  Usect Vtoc
6500 SYSXL1  3390-3  SHR PVT 03338 02359 02147   00018 0   4  0007 IX  
6508 SYSXL2  3390-3  SHR PVT 03338 02441 02218   0 0   2  0001 IX  
6700 SYSXL3  3390-3  SHR PVT 03338 01001 01001   0 0   1  0001 IX  
6708 SYSXL4  3390-3  SHR PVT 03338 02216 02204   0 0   2  0002 IX  
7309 SYSX04  3390-3  SHR PVT 03338 00199 00135   00029 0   00010  0217 IX  
7801 SYSX01  3390-3  SHR PVT 03338 00385 00041   00443 0   00095  0103 IX  
7A0A SYSX06  3390-3  SHR PVT 03338 02999 02999   5 0   2  0006 IX  
7B02 SYSX02  3390-3  SHR PVT 03338 6 3   00054 0   00010  0005 IX  
7C12 SYSX03  3390-3  SHR PVT 03338 00026 2   00464 00013   00099  0260 IX  
7E02 SYSX05  3390-3  SHR PVT 03338 01149 00176   00276 0   00076  0015 IX  
   
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-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 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

I have tried to capture test subcommand output I.E list under clist with no 
success Dont  know about Rexx I am now thinking the AT subcommsnd in TEST 
leaves you the ability to to exec a CLIST as part of the parameters  maybe I'll 
try the SYSOUTTRAP/SYSOUTLINE in that instance 



> On Jul 3, 2016, at 1:51 PM, Jesse 1 Robinson  wrote:
> 
> I was sloppy. AFAIK the functions are equivalent.  In Rexx, you use this 
> syntax: 
> 
> x = OUTTRAP("cmdl.")
> "LISTALC STATUS"
> line_count = cmdl.0
> dsn = cmdl.i
> ...
> 
> Output goes into the named array. Lines are identified by the value of i. 
> 
> Equivalent in Clist: 
> 
> SET SYSOUTTRAP = 600 
> LISTALC STATUS   
> SET SYSOUTTRAP = 0   
> SET _COUNT = 
> SET DSN = (&)
> ...
> 
> Output always goes into complex variable  Lines are identified by 
> the value of 
> 
> The real difference for OP is the scope of output capture in Rexx vs. Clist. 
> 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 Program Co-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
> 

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

I have tried to capture test subcommand output I.E list under clist with no 
success Dont  know about Rexx I am now thinking the AT subcommsnd in TEST 
leaves you the ability to to exec a CLIST as part of the parameters  maybe I'll 
try the SYSOUTTRAP/SYSOUTLINE in that instance 



> On Jul 3, 2016, at 1:51 PM, Jesse 1 Robinson  wrote:
> 
> I was sloppy. AFAIK the functions are equivalent.  In Rexx, you use this 
> syntax: 
> 
> x = OUTTRAP("cmdl.") 
> "LISTALC STATUS"
> line_count = cmdl.0
> dsn = cmdl.i
> ...
> 
> Output goes into the named array. Lines are identified by the value of i. 
> 
> Equivalent in Clist: 
> 
> SET SYSOUTTRAP = 600 
> LISTALC STATUS   
> SET SYSOUTTRAP = 0   
> SET _COUNT = 
> SET DSN = (&)
> ...
> 
> Output always goes into complex variable  Lines are identified by 
> the value of 
> 
> The real difference for OP is the scope of output capture in Rexx vs. Clist. 
> 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 Program Co-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@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
> 
> You use SYSOUTTRAP in Rexx thought it's a clist command unless you are 
> calling clist from Rexx
> 
>> On Jul 3, 2016, at 12:48 PM, Jesse 1 Robinson  
>> wrote:
>> 
>> I use SYSOUTTRAP in Rexx all the time for ordinary commands. There is indeed 
>> a huge difference between Rexx and Clist vis a vis 'subcommand mode'. An 
>> example of subcommand mode is the SEND command under OPER. Another is LIST 
>> under ACCOUNT. TEST runs in practice almost entirely in subcommand mode. 
>> 
>> In a Clist, the exec retains control when running in subcommand mode. In 
>> Rexx, the exec loses control in subcommand mode, so successive commands must 
>> be 'stacked' ahead of time via QUEUE. Trouble is that in TEST, subsequent 
>> command operands usually depend on the result of previous commands, which 
>> makes QUEUEing commands ahead of time nearly impossible. 
>> 
>> I don't recall ever trying SYSOUTTRAP in TEST.  
>> 
>> .
>> .
>> .
>> J.O.Skip Robinson
>> Southern California Edison Company
>> Electric Dragon Team Paddler
>> SHARE MVS Program Co-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:18 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
>> 
>> 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 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 in SYSOUTTRAP as 
>>> well. I had a small collection of REXX and CLIST that could be run in 
>>> TEST to do things such as single step and redisplay registers, 
>>> storage, code, PSW and so on, almost half way to a full screen debugger.
>>> 
>>> I found the differences meant I had to mix REXX and CLIST to get the 
>>> job done.
>>> 
>>> Roops
 On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
 
 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'.
> 
> /* 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
> 
> HTH
> 
> Mike
> 
> 
>> On 29 June 2016 at 15:21, Joseph Reichman 
 wrote:
>> 
>> 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 

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Jesse 1 Robinson]

I was sloppy. AFAIK the functions are equivalent.  In Rexx, you use this 
syntax: 

x = OUTTRAP("cmdl.") 
"LISTALC STATUS"
line_count = cmdl.0
dsn = cmdl.i
...

Output goes into the named array. Lines are identified by the value of i. 

Equivalent in Clist: 

SET SYSOUTTRAP = 600 
LISTALC STATUS   
SET SYSOUTTRAP = 0   
SET _COUNT = 
SET DSN = (&)
...

Output always goes into complex variable  Lines are identified by 
the value of 

The real difference for OP is the scope of output capture in Rexx vs. Clist. 
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 Program Co-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@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

You use SYSOUTTRAP in Rexx thought it's a clist command unless you are calling 
clist from Rexx

> On Jul 3, 2016, at 12:48 PM, Jesse 1 Robinson  wrote:
> 
> I use SYSOUTTRAP in Rexx all the time for ordinary commands. There is indeed 
> a huge difference between Rexx and Clist vis a vis 'subcommand mode'. An 
> example of subcommand mode is the SEND command under OPER. Another is LIST 
> under ACCOUNT. TEST runs in practice almost entirely in subcommand mode. 
> 
> In a Clist, the exec retains control when running in subcommand mode. In 
> Rexx, the exec loses control in subcommand mode, so successive commands must 
> be 'stacked' ahead of time via QUEUE. Trouble is that in TEST, subsequent 
> command operands usually depend on the result of previous commands, which 
> makes QUEUEing commands ahead of time nearly impossible. 
> 
> I don't recall ever trying SYSOUTTRAP in TEST.  
> 
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-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:18 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
> 
> 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 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 in SYSOUTTRAP as 
>> well. I had a small collection of REXX and CLIST that could be run in 
>> TEST to do things such as single step and redisplay registers, 
>> storage, code, PSW and so on, almost half way to a full screen debugger.
>> 
>> I found the differences meant I had to mix REXX and CLIST to get the 
>> job done.
>> 
>> Roops
>>> On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
>>> 
>>> 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'.
 
 /* 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
 
 HTH
 
 Mike
 
 
> On 29 June 2016 at 15:21, Joseph Reichman 
>>> wrote:
> 
> 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

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Paul Gilmartin]

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 a logging facility.

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?


>> 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 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 in SYSOUTTRAP as well. I
>> had a small collection of REXX and CLIST that could be run in TEST to do
>> things such as single step and redisplay registers, storage, code, PSW and
>> so on, almost half way to a full screen debugger.
>> 
>> I found the differences meant I had to mix REXX and CLIST to get the job
>> done.
>> 
I believe this behavior is called "modal".  CLIST (but not Rexx) interfaces
similarly with (non-ISPF) Edit.  Perhaps others?  Likewise CMS EXEC (but
not EXEC2 nor Rexx) interacts similarly with old CMS (non-X-)EDIT.  And
Rexx sorely lacks any facility for instream data.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

You use SYSOUTTRAP in Rexx thought it's a clist command unless you are calling 
clist from Rexx

> On Jul 3, 2016, at 12:48 PM, Jesse 1 Robinson  wrote:
> 
> I use SYSOUTTRAP in Rexx all the time for ordinary commands. There is indeed 
> a huge difference between Rexx and Clist vis a vis 'subcommand mode'. An 
> example of subcommand mode is the SEND command under OPER. Another is LIST 
> under ACCOUNT. TEST runs in practice almost entirely in subcommand mode. 
> 
> In a Clist, the exec retains control when running in subcommand mode. In 
> Rexx, the exec loses control in subcommand mode, so successive commands must 
> be 'stacked' ahead of time via QUEUE. Trouble is that in TEST, subsequent 
> command operands usually depend on the result of previous commands, which 
> makes QUEUEing commands ahead of time nearly impossible. 
> 
> I don't recall ever trying SYSOUTTRAP in TEST.  
> 
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler 
> SHARE MVS Program Co-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:18 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
> 
> 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 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 in SYSOUTTRAP as 
>> well. I had a small collection of REXX and CLIST that could be run in 
>> TEST to do things such as single step and redisplay registers, 
>> storage, code, PSW and so on, almost half way to a full screen debugger.
>> 
>> I found the differences meant I had to mix REXX and CLIST to get the 
>> job done.
>> 
>> Roops
>>> On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
>>> 
>>> 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'.
 
 /* 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
 
 HTH
 
 Mike
 
 
> On 29 June 2016 at 15:21, Joseph Reichman 
>>> wrote:
> 
> 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Jesse 1 Robinson]

I use SYSOUTTRAP in Rexx all the time for ordinary commands. There is indeed a 
huge difference between Rexx and Clist vis a vis 'subcommand mode'. An example 
of subcommand mode is the SEND command under OPER. Another is LIST under 
ACCOUNT. TEST runs in practice almost entirely in subcommand mode. 

In a Clist, the exec retains control when running in subcommand mode. In Rexx, 
the exec loses control in subcommand mode, so successive commands must be 
'stacked' ahead of time via QUEUE. Trouble is that in TEST, subsequent command 
operands usually depend on the result of previous commands, which makes 
QUEUEing commands ahead of time nearly impossible. 

I don't recall ever trying SYSOUTTRAP in TEST.  

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-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:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

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 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 in SYSOUTTRAP as 
> well. I had a small collection of REXX and CLIST that could be run in 
> TEST to do things such as single step and redisplay registers, 
> storage, code, PSW and so on, almost half way to a full screen debugger.
> 
> I found the differences meant I had to mix REXX and CLIST to get the 
> job done.
> 
> Roops
>> On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
>> 
>> 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'.
>>> 
>>> /* 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
>>> 
>>> HTH
>>> 
>>> Mike
>>> 
>>> 
 On 29 June 2016 at 15:21, Joseph Reichman 
>> wrote:
 
 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

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

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 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 in SYSOUTTRAP as well. I
> had a small collection of REXX and CLIST that could be run in TEST to do
> things such as single step and redisplay registers, storage, code, PSW and
> so on, almost half way to a full screen debugger.
> 
> I found the differences meant I had to mix REXX and CLIST to get the job
> done.
> 
> Roops
>> On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
>> 
>> 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'.
>>> 
>>> /* 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
>>> 
>>> HTH
>>> 
>>> Mike
>>> 
>>> 
 On 29 June 2016 at 15:21, Joseph Reichman 
>> wrote:
 
 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
>>> 
>>> 
>>> 
>>> --
>>> Mike Shorkend
>>> m...@shorkend.com
>>> www.shorkend.com
>>> Tel: +972524208743
>>> Fax: +97239772196
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Multithreaded output to stderr and stdout

[Anne & Lynn Wheeler]

jcew...@acm.org (Joel C. Ewing) writes:
> The plethora of links at the referenced URLs never even gave a direct
> answer to the question "Charlie Who". 
>
> One of the paragraphs at the many sub-links at the given URLs refers to
> him as "Charlie S.", another as "Charlie Salisbury", so apparently it
> was a Charlie A. Salisbury who worked for IBM somewhere in the realm of
> hardware design.  I found some non-garlic.com links suggesting there
> is/was at some point a Charlie Salisbury at IBM as an Engineering
> Manager or a Service Delivery Manager, but no indication whether this
> was a reference to the same CAS Charlie.  IBM could easily have had
> multiple employees over the years with the same first-last name.

re:
http://manana.garlic.com/~lynn/2016d.html#96 Multithreaded output to stderr and 
stdout
http://manana.garlic.com/~lynn/2016d.html#100 Multithreaded output to stderr 
and stdout

specifically said that CAS Charlie was later IBM associate director at
MIT Project Athena ... and provided MIT Project Athena URL references.

of course there are lots of other Charlies in the world (even at IBM),
which is true regardless of how I might have answered the request.

other trivia ... first ran into Charlie in the late 60s when Univ.  set
me to CP67 conference in silicon valley. There were a number of silicon
valley area custmers at the time that had gotten 360/67s

Charlie was IBM SE on the Lockheed (MOL, manned orbital laboratory)
program which had gotten a triplex 360/67 ... which had some
enhancements somewhat analogous to the 360/65s for the FAA air traffic
control program. On standard multiprocessor 360/67 the configuration
controller switch settings were available from the control registers
(see detailed information in 360/67 functional characteristics at
bitsavers also shown in 360/67 "blue card"). For the Lockheed MOL
triplex 360/67 it was also possible to make configuration changes by
loading different values in the control registers.

At the time, there was also a silicon chip company running cp/67 on
360/67 and Navy Postgraduate school (in Monterey) was running cp/67 on
360/67.

other trivia ... before ms/dos
http://en.wikipedia.org/wiki/MS-DOS
there was seattle computer
http://en.wikipedia.org/wiki/Seattle_Computer_Products
before seattle computer there was CP/M,
http://en.wikipedia.org/wiki/CP/M
before developing CP/M, kildall worked with CP67 at npg
http://en.wikipedia.org/wiki/Naval_Postgraduate_School

-- 
virtualization experience starting Jan1968, online at home since Mar1970

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Multithreaded output to stderr and stdout

[Joel C. Ewing]

On 07/02/2016 08:25 PM, Paul Gilmartin wrote:
> On Sat, 2 Jul 2016 17:33:46 -0700, Anne & Lynn Wheeler wrote:
>
>> mike.lamart...@mcleansoft.com (Mike La Martina) writes:
>>> After reading the story of Compare and Swap for, lo, all these many years, I
>>> am sorry but I must ask.
>>>
>>> Charlie who?
>> aka Charlie's initials are CAS ... part of the effort was to choose
>> mnemonic (compare-and-swap) that were Charlie's initials
>> http://www.garlic.com/~lynn/subtopic.html#smp
>>
>> IBM funds MIT project athena for $25M and then DEC funds another $25M,
>> both IBM and DEC get an associate director of Project Athena.  Charlie
>> leaves the science center
>> http://www.garlic.com/~lynn/subtopic.html#545tech
>> and becomes the IBM associate director of Project athena (pg 10):
>> http://simson.net/ref/athena/Q_and_A_Draft_October31_1986.pdf
>>
>>
> E... https://xkcd.com/1640/
>
> -- gil
>
>
The plethora of links at the referenced URLs never even gave a direct
answer to the question "Charlie Who". 

One of the paragraphs at the many sub-links at the given URLs refers to
him as "Charlie S.", another as "Charlie Salisbury", so apparently it
was a Charlie A. Salisbury who worked for IBM somewhere in the realm of
hardware design.  I found some non-garlic.com links suggesting there
is/was at some point a Charlie Salisbury at IBM as an Engineering
Manager or a Service Delivery Manager, but no indication whether this
was a reference to the same CAS Charlie.  IBM could easily have had
multiple employees over the years with the same first-last name.

-- 
Joel C. Ewing,Bentonville, AR   jcew...@acm.org 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

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 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 in SYSOUTTRAP as well. I
> had a small collection of REXX and CLIST that could be run in TEST to do
> things such as single step and redisplay registers, storage, code, PSW and
> so on, almost half way to a full screen debugger.
> 
> I found the differences meant I had to mix REXX and CLIST to get the job
> done.
> 
> Roops
>> On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:
>> 
>> 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'.
>>> 
>>> /* 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
>>> 
>>> HTH
>>> 
>>> Mike
>>> 
>>> 
 On 29 June 2016 at 15:21, Joseph Reichman 
>> wrote:
 
 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
>>> 
>>> 
>>> 
>>> --
>>> Mike Shorkend
>>> m...@shorkend.com
>>> www.shorkend.com
>>> Tel: +972524208743
>>> Fax: +97239772196
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Rupert Reynolds]

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 in SYSOUTTRAP as well. I
had a small collection of REXX and CLIST that could be run in TEST to do
things such as single step and redisplay registers, storage, code, PSW and
so on, almost half way to a full screen debugger.

I found the differences meant I had to mix REXX and CLIST to get the job
done.

Roops
On 3 Jul 2016 12:53, "Joseph Reichman"  wrote:

> 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'.
> >
> > /* 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
> >
> > HTH
> >
> > Mike
> >
> >
> >> On 29 June 2016 at 15:21, Joseph Reichman 
> wrote:
> >>
> >> 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
> >
> >
> >
> > --
> > Mike Shorkend
> > m...@shorkend.com
> > www.shorkend.com
> > Tel: +972524208743
> > Fax: +97239772196
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Netview Automation User ID

[Steve Horein]

Hi Bill -
There are a great bunch of NetView experts, including IBMers, at:
https://groups.yahoo.com/neo/groups/NetView/info
Documents can be found here:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/env2bk42
(chapter 14 of "Security Reference" looks promising)
Anyway, how is SECOPTS.OPERSEC in your stylesheets (CxySTUSR and/or
CxySTGEN) in DSIPARM? If SAF is included somewhere in the option (SAFPW,
SAFCHECK, or SAFDEF), then I believe a NetView segment is also required, or
completely replaces DSIOPFU needs.

On Sun, Jul 3, 2016 at 2:22 AM, Bill Widmayer 
wrote:

> Good day to all.
> First time for me to add new user ids to Netview Automation task.
> I followed the same steps I do for Netview regular, update DSIOPFU and use
> the REFRESH OPERS command.
> For Netview Automation, this did not work and still get the error :
> DSI021A INVALID OPERATOR IDENTIFICATION, REENTER
>
> Can someone point me in the right direction?
> Version is NetView V6R1 - NM.
> I've looked online at the Automation manuals and have not found a clear
> admin/setup guide.
>
> Thanks
>
> Bill Widmayer
>
>
>
>
>
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Joseph Reichman]

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'.
> 
> /* 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
> 
> HTH
> 
> Mike
> 
> 
>> On 29 June 2016 at 15:21, Joseph Reichman  wrote:
>> 
>> 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
> 
> 
> 
> -- 
> Mike Shorkend
> m...@shorkend.com
> www.shorkend.com
> Tel: +972524208743
> Fax: +97239772196
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE

[Mike Shorkend]

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

HTH

Mike


On 29 June 2016 at 15:21, Joseph Reichman  wrote:

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



-- 
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre and Browsers

[nitz-ibm]

> Assuming you can *find* the damned PDFs! That takes a while now. Sad what
> IBM has become.
Try Pubcenter: 
http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=DE
(and don't use the DE at the end).
Barbara

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Netview Automation User ID

[Bill Widmayer]

Good day to all.
First time for me to add new user ids to Netview Automation task.
I followed the same steps I do for Netview regular, update DSIOPFU and use the 
REFRESH OPERS command.
For Netview Automation, this did not work and still get the error :
DSI021A INVALID OPERATOR IDENTIFICATION, REENTER

Can someone point me in the right direction?
Version is NetView V6R1 - NM.
I've looked online at the Automation manuals and have not found a clear 
admin/setup guide.

Thanks

Bill Widmayer








The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM Knowledge Centre

[Edward Gould]

> On Jul 2, 2016, at 10:56 PM, Jack J. Woehr  wrote:
> 
> Charles Mills wrote:
> 
>>At a company apparently so into customer satisfaction.
>> 

Whoa wait a second, the last time IBM asked for a survey on here I was unable 
to take it and they couldn’t/wouldn’t give a reason. Just that I was out of 
luck.
Since then I have refused to take part of survey’s as obviously IBM doesn’t 
care about customers anymore.

Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN