Re: Remote Tape drives

2006-12-30 Thread Bob Shannon
I have been exposed to two different channel extenders over the years snip these were attached to either a 4341 or a 168 ( 3033)) Ed - Your experience with extenders occurred over 20 years ago. This falls into the category of AFH and is not relevant to modern equipment. Bob Shannon Rocket

Re: Remote Tape drives

2006-12-30 Thread Ed Gould
On Dec 30, 2006, at 6:17 AM, Bob Shannon wrote: I have been exposed to two different channel extenders over the years snip these were attached to either a 4341 or a 168 ( 3033)) Ed - Your experience with extenders occurred over 20 years ago. This falls into the category of AFH and is not

How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
Does anyone know how one might write a full-screen Rexx debugger, like z/XDC or Xpediter? I've spent a couple of evenings digging through the Rexx Reference, but so far I've not stumbled on a way to do it. Or even if it can be done. Any hints or ideas? I also asked on the Rexx list, but it

IEW2611E

2006-12-30 Thread Paul Gilmartin
Trying to do a link edit lately, I got: IEW2611E 4313 ALIAS CANNOT REPLACE MODULE WITH SAME NAME. Why is this considered an error when I specify (R) on the NAME statement? -- gil -- StorageTek INFORMATION made POWERFUL

Re: Remote Tape drives

2006-12-30 Thread Rick Fochtman
snip--- Any suggestions on ways we could have a tape drive 3490 in a remote location attached to our mainframe. We are talking about 1 thousand of miles. Speed is not important ---unsnip- CNT Channel

Re: Remote Tape drives

2006-12-30 Thread Rick Fochtman
--snip- What ever happened to those good old Mohawk data transfer units --unsnip- IIRC, they died at about the same time that open reel tapes died. CARTRIDGES RULE!!! :-(

Re: Heads-Up: OA19281 PSA Overlay for z/OS 1.8, and bad HOLDDATA for Everyone UPDATE

2006-12-30 Thread Brian Peterson
The bad HOLDDATA for Everyone portion of this problem is now resolved. Today, the HOLDDATA file contains the following (now syntactically-valid MCS): ++HOLD(HBB7730) FMID(HBB7730) REASON(AA19281) ERROR DATE(06363) COMMENT(SMRTDATA(SYMP(IPL,FUL,PRF,PRV,SYSPLXDS) CHGDT(061229))) CLASS(HIPER).

Re: IEW2611E

2006-12-30 Thread Steve Comstock
Paul Gilmartin wrote: Trying to do a link edit lately, I got: IEW2611E 4313 ALIAS CANNOT REPLACE MODULE WITH SAME NAME. Why is this considered an error when I specify (R) on the NAME statement? -- gil Hard to tell for sure without a little more info, but it looks like you are

Re: Remote Tape drives

2006-12-30 Thread Eric N. Bielefeld
Modern equipment is just so unsexy. With the old reel tapes, at least you could see the tape spinning, and the tape bouncing up and down in the vacuum columns. Cartridges you can't see anything. Eric Bielefeld Sr. z/OS Systems Programmer Lands End Dodgeville, Wisconsin 414-475-7434 -

Re: IEW2611E

2006-12-30 Thread Phil Sidler
IEW2611E 4313 ALIAS CANNOT REPLACE MODULE WITH SAME NAME. Why is this considered an error when I specify (R) on the NAME statement? perhaps because the linkage editor doesn't want to bother finding if there are aliases for the real module that might need to be cleaned up? So it's

Re: Remote Tape drives

2006-12-30 Thread Ted MacNEIL
Cartridges you can't see anything. We used to have contests to see who could carry the most reels by stringing them on your arm. At 6'-2, I had the longest arms, so I always won. Couldn't do that with cartridges. I point out, at a non-disclosure on 3480's, that IBM had taken all the fun out

Re: Remote Tape drives

2006-12-30 Thread Ed Finnell
In a message dated 12/30/2006 11:39:25 A.M. Central Standard Time, [EMAIL PROTECTED] writes: point out, at a non-disclosure on 3480's, that IBM had taken all the fun out of being a tape ape! Guess it's year end story time. Was working in Northern California and we had a little tumbler

Re: Remote Tape drives

2006-12-30 Thread Ted MacNEIL
Well our earthquake proof building had hopped enough to knock about 50,000 reels off the shelf and everybody that could read and bend over was put to work. In the early 1970's, there was a fire in the University of Toronto Computer Room (well before the protection(s) we have today). I had to

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Binyamin Dissen
On Sat, 30 Dec 2006 16:40:12 +0100 Lindy Mayfield [EMAIL PROTECTED] wrote: :Does anyone know how one might write a full-screen Rexx debugger, like z/XDC or Xpediter? I've spent a couple of evenings digging through the Rexx Reference, but so far I've not stumbled on a way to do it. Or even if

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Charles Mills
I have not used XDC or CA-Xpediter, but I would imagine you could write a debugger in mostly Rexx with some assembler. Take a look at the TSO/E Programming Services manual for a discussion of how to write a native TSO full screen program. You will also have to give some thought to the debugging

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
I'm surprised at this question, but it is not unexpected. (-: I respect you a lot so I'll humor you with my thought process on this. Why not? Why have Xpeditor when you have READY TRACE in COBOL? I'm just curious if it can be done and if so how. An interactive environment is much easier

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Charles Mills
Ah! Binyamin and I answered different questions, I think. By full-screen Rexx debugger, do you (the OP) mean: - a full-screen debugger for Rexx programs? Or - a full-screen debugger for programs in general, written in Rexx? I answered the latter question; I think Binyamin is answering the

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
Thanks for the hints! But just to be clear, I'm not that good, and also if I could do it in my spare time it would go to sourceforge or some other type of free software place like CBT. I am NOT looking for a commercial product. Not at all. Just something to do that helps me learn and perhaps

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
Oh! (-: I meant, instead of using TRACE ?I in a Rexx program (like COBOL READY TRACE) you could in an ISPF-like full screen program trace a Rexx program. Put in breakpoints, display variable values, change them, and on and on. Like those programs do. You know, I was just curious if it

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Charles Mills
Ah! Would it be possible to replace TRACE with your own service routine, that would do TSO full-screen presentation of the data, rather than Rexx's line I/O. Interesting question. That would be a useful product. You can write code that Rexx will call for all I/O including Say. See Chapter 14 of

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
I've gone through all of those docs quite a bit, but the one point I don't find is how to interrupt the flow of the exec and how to either know what the actual statement is or how to map it to the original exec. I read Chapter 14 many times, but I don't see a way to get between the user and

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Charles Mills
What if you: - Built a full-screen application with two panes. The upper pane would be for output. A user could scroll up and down through the output, so s/he could readily see output produced earlier in the session. - The lower pane would be for input. A user could either type a command, or

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Binyamin Dissen
On Sat, 30 Dec 2006 19:22:33 +0100 Lindy Mayfield [EMAIL PROTECTED] wrote: :I'm surprised at this question, but it is not unexpected. (-: :I respect you a lot so I'll humor you with my thought process on this. :Why not? :Why have Xpeditor when you have READY TRACE in COBOL? Boy, am I the

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Paul Gilmartin
On Sat, 30 Dec 2006 16:40:12 +0100, Lindy Mayfield wrote: Does anyone know how one might write a full-screen Rexx debugger, like z/XDC or Xpediter? I've spent a couple of evenings digging through the Rexx Reference, but so far I've not stumbled on a way to do it. Or even if it can be

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Charles Mills
Don't forget you can display the value of any Rexx variable from a debugging session by typing Say Foo (or Say C2X(Foo) etc.). I could see mapping function keys such that you could put the cursor on any variable name in the display and hitting the PF key would insert Say Foo or Say C2X(Foo), etc.

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread David Cole
[Lindy Mayfield ] Seriously, I'm surprised you ask this. [Binyamin Dissen] Why have z/XDC or Xpeditor or AbendAid when you have dumps? Man! Don't get me started, Ben! [:)] Dave Cole REPLY TO: [EMAIL PROTECTED] Cole Software WEB PAGE: http://www.xdc.com 736 Fox Hollow

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Shane
And here I was thinking Dave may be going to drop some pearl of wisdom - say the critical half dozen or so lines of code that constitute a bedugger ... ;o) BTW, in all fairness to Binyamin, I think you should the get attribution correct. Shane ...

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread David Cole
[shane] BTW, in all fairness to Binyamin, I think you should the get attribution correct. You're right. I misread it. Sorry Ben. [Shane] And here I was thinking Dave may be going to drop some pearl of wisdom - say the critical half dozen or so lines of code that constitute a bedugger

Re: Remote Tape drives

2006-12-30 Thread Ed Finnell
In a message dated 12/30/2006 12:04:59 P.M. Central Standard Time, [EMAIL PROTECTED] writes: Due to poor/untested backup/dr procedures a lot of master's/PHD work was still lost. UoT has top-level procedures, today. Wonder if there's an ISO standard for Academic research regarding

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
That's an excellent point. I wrote a simple asm function that only displayed the hex value of R0. So my Rexx program was simply: Call RXENVR0 /* Displays R0 in hex */ ISRDDN Then I could use ISRDDN, knowing the location of ENVBLOCK, and then I could check out all the control blocks

Re: How to write a full-screen Rexx debugger?

2006-12-30 Thread Lindy Mayfield
Actually it was Ben who said: quote Boy, am I the wrong guy to ask that question. When I did COBOL programming I used TSO TEST to debug (after checking the PMAP for complicated instructions to make sure that they were properly done - I once found a bug in a compiler). When doing system