Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-02 Thread Shmuel Metz (Seymour J.)
In a6b9336cdb62bb46b9f8708e686a7ea005bde01...@nrhmms8p02.uicnrh.dom, on 02/01/2010 at 12:55 PM, McKown, John john.mck...@healthmarkets.com said: Thanks for all that information. If TEE was so difficult to implement, I shudder to think about my UNIX SUBSYS= functionality! I wonder about doing

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-01 Thread Martin Kline
I think we could use the GPSAM routines from the CBT tape to create the TEE function. Both versions of this (CBT files 290 and 648) appear to have been written in 1982. I haven't tried using the code on our z/OS 1.9 system, but they use some questionable means of locating and modifying control

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-01 Thread McKown, John
Thanks for all that information. If TEE was so difficult to implement, I shudder to think about my UNIX SUBSYS= functionality! I wonder about doing something hinkey in OPEN. OPEN can open multiple DCBs in a single SVC. So, I wonder if it does it them sequentially. If so, I wonder if it would be

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-01 Thread Martin Kline
I wonder about doing something hinkey in OPEN. OPEN can open multiple DCBs in a single SVC. So, I wonder if it does it them sequentially. If so, I wonder if it would be possible to dynamically add my DCBs onto the end of the list. Probably not something that would be long term viable. Since the

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-01 Thread kopplin
- Original Message - From: Martin Kline martin.kl...@yrcw.com Newsgroups: bit.listserv.ibm-main Sent: Monday, February 01, 2010 9:09 AM Subject: Re: Friday thought - a couple of SUBSYS= subsystems for discussion. I think we could use the GPSAM routines from the CBT tape to create the

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-02-01 Thread kopplin
Martin Kline provided a response that would probably work. That being said, and having been there, done that, I wouldn't go there. Other folks have other views. These days, that subsystem code has a support status of: If it breaks, you get to keep both pieces. Looking back across four

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-01-31 Thread Shmuel Metz (Seymour J.)
In listserv%201001291001530009.0...@bama.ua.edu, on 01/29/2010 at 10:01 AM, Martin Kline martin.kl...@yrcw.com said: I can think of a couple other solutions using out-of-the-box methods, but neither is as clean as what you're proposing. You'd need a minimum number of subsystem routines - JCL

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-01-31 Thread Rick Fochtman
snip-- Doesn't FREEPOOL test whether there is a buffer pool before trying to free it? unsnip- That's a fairly recent refinement to the FREEPOOL macro. For many years there

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-01-31 Thread Ken Gunther
I think we could use the GPSAM routines from the CBT tape to create the TEE function. Ken G. McKown, John wrote: OK, it is Friday. And this is on topic. It may even be interesting. I was thinking of two possible SUBSYS= subsystems to use, especially on batch jobs.

Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-01-29 Thread McKown, John
OK, it is Friday. And this is on topic. It may even be interesting. I was thinking of two possible SUBSYS= subsystems to use, especially on batch jobs. One I call TEE. The other I call UNIX. The TEE subsystem is inspired(?) by the UNIX tee command. The tee command reads its stdin and sends it

Re: Friday thought - a couple of SUBSYS= subsystems for discussion.

2010-01-29 Thread Martin Kline
I can think of a couple other solutions using out-of-the-box methods, but neither is as clean as what you're proposing. You'd need a minimum number of subsystem routines - JCL processing, allocation, open and close, and maybe another couple. At OPEN time, issue OPENs for the related files,