...@bama.ua.edu] On Behalf Of
Cheryl Walker
Sent: Thursday, 02 December, 2010 03:30 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: zOS messages.. totally true... almost totally useless
Regarding the scores, the values can range from +5 (highly desirable) to -5
(would cause negative impact
Regarding the scores, the values can range from +5 (highly desirable) to -5
(would cause negative impact). In this particular situation, 27 people said it
was desirable (7 of them said it was +5). Now compare that to opening an APAR
where only one site wants a change. In my experience,
On 11/25/2010 07:37 PM, Shmuel Metz (Seymour J.) wrote:
Inlistserv%20101122101159.0...@bama.ua.edu, on 11/22/2010
at 10:11 AM, Paul Gilmartinpaulgboul...@aim.com said:
o Place JCL error messages inline, as HLASM does, so the programmer
would be spared the need to swap between
On Sat, 27 Nov 2010 11:16:02 -0600, Joel C. Ewing wrote:
Actually this touches a minor raw nerve ...
I
never have liked WAD or longevity as a excuse for a design flaw, but if
it took us 25 years to have this case be an issue and since there are
easy circumventions (e.g, don't misuse /*, use JCL
In listserv%20101122101159.0...@bama.ua.edu, on 11/22/2010
at 10:11 AM, Paul Gilmartin paulgboul...@aim.com said:
o Place JCL error messages inline, as HLASM does, so the programmer
would be spared the need to swap between JESYSMSGS and JESJCL.
They used to, back in OS/360 and OS/VS2 R1
In listserv%201011201209565982.0...@bama.ua.edu, on 11/20/2010
at 12:09 PM, Paul Gilmartin paulgboul...@aim.com said:
Properly; I understand an excess of implementation detail is an
obstacle to fulfillment of a requirement: While we otherwise favor
the requirement, your specific proposed
the blocksize.
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
W. Kevin Kelley
Sent: Friday, November 19, 2010 9:48 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: zOS messages.. totally true... almost totally useless
On Fri, 19 Nov 2010 18:29
On 21 Nov 2010 17:42:19 -0800, in bit.listserv.ibm-main you wrote:
On Fri, 19 Nov 2010 22:42:10 -0800, Edward Jaffe
edja...@phoenixsoftware.com wrote:
According to the SHARE requirements data base, this requirement was
submitted
nearly 18 years ago in March 1993. See what you can do...
Ed,
On Mon, 22 Nov 2010 10:57:34 -0400, Clark Morris wrote:
The biggest challenge is likely to be the limited resource in TSO (the IKJ
component), but I'll see what I can do... It certainly wouldn't hurt to
resubmit
it as part of the SHARE requirements clean-up.
W. Kevin Kelley -- IBM POK Lab --
Amen, brother. This ain't 1964.
--
zMan -- I've got a mainframe and I'm not afraid to use it
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN
Robert:
We all remember the *INFAMOUS* call your systems programmer, right?
When the PUBS people (at the time of OCO) were at SHARE/GUIDE I really do not
remember. That was one of the first issue brought up and asked that IF IBM was
going to say that at least give some minimal diagnostic
On Fri, 19 Nov 2010 22:42:10 -0800, Edward Jaffe
edja...@phoenixsoftware.com wrote:
According to the SHARE requirements data base, this requirement was
submitted
nearly 18 years ago in March 1993. See what you can do...
Ed,
The biggest challenge is likely to be the limited resource in TSO
On 11/21/2010 5:40 PM, W. Kevin Kelley wrote:
Ed,
The biggest challenge is likely to be the limited resource in TSO (the IKJ
component), but I'll see what I can do... It certainly wouldn't hurt to resubmit
it as part of the SHARE requirements clean-up.
Upon closer examination, it appears this
...@bama.ua.edu] On Behalf Of
W. Kevin Kelley
Sent: Friday, November 19, 2010 8:14 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: zOS messages.. totally true... almost totally useless
On Fri, 19 Nov 2010 16:19:00 -0800, John Mattson
john_matt...@ea.epson.com wrote:
Continuing to voice my
I have an open source program I use on Windows that falls over about
once a year; when it does, it puts up a dialog box that says SOMETHING
BAD HAPPENED.
This message is every bit as useful. The word useless' is entirely appropriate.
Put another way: if it's NOT clear to the developers that it's
On 11/20/2010 6:50 AM, zMan wrote:
I have an open source program I use on Windows that falls over about
once a year; when it does, it puts up a dialog box that says SOMETHING
BAD HAPPENED.
This message is every bit as useful. The word useless' is entirely appropriate.
Put another way: if it's
--- On Fri, 11/19/10, Robert A. Rosenberg hal9...@panix.com wrote:
From: Robert A. Rosenberg hal9...@panix.com
Subject: Re: zOS messages.. totally true... almost totally useless
To: IBM-MAIN@bama.ua.edu
Date: Friday, November 19, 2010, 10:55 PM
At 02:07 + on 11/20/2010, Ted MacNEIL wrote
On Fri, 19 Nov 2010 22:42:10 -0800, Edward Jaffe wrote:
...
Benefit:I cannot tell which command in my IKJTSOxx is invalid: all
commands seem
correct to me. Today, the only way to resolve this problem, is by eliminating
commands one-by-one and re-starting TSO to discover which command is
On 11/20/2010 10:09 AM, Paul Gilmartin wrote:
Try rephrasing the benefit.
The benefit is obvious. This is not a procedural problem.You're either giving
IBM too much credit or not enough. (I really don't want to know which.)
Suggestions for rewriting a requirement are made during the
At 07:58 -0800 on 11/20/2010, Ed Gould wrote about Re: zOS messages..
totally true... almost totally useless:
Although it is far and few in between there have been code changes
as a result of pub changes. BTW these code changes are NOT quick in
coming (so do not hold your breath). Pub
Case #1
Continuing to voice my annoyance with zOS messages. This popped
up, apparantly has been that way for some time. Big help, there are 166
lines in my IKJTSO00. If it can identify duplicate, it can tell me what it
is.
IKJ710I DUPLICATE PARAMETER FOUND IN MEMBER IKJTSO00 OF
Indeed. This is almost as bad in z/OS as in UNIX.
Try z/VM, it has REAL error messages...
On Fri, Nov 19, 2010 at 7:19 PM, John Mattson john_matt...@ea.epson.com wrote:
Case #1
Continuing to voice my annoyance with zOS messages. This popped
up, apparantly has been that way for some
On Fri, 19 Nov 2010 16:19:00 -0800, John Mattson
john_matt...@ea.epson.com wrote:
Continuing to voice my annoyance with zOS messages.
May I suggest that you open a formal problem with IBM for each of these?
W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development
May I suggest that you open a formal problem with IBM for each of these?
With all due respect.
That's akin to cleaning the Agean Stables.
-
Ted MacNEIL
eamacn...@yahoo.ca
--
For IBM-MAIN subscribe / signoff / archive access
On 11/19/2010 5:14 PM, W. Kevin Kelley wrote:
On Fri, 19 Nov 2010 16:19:00 -0800, John Mattson
john_matt...@ea.epson.com wrote:
Continuing to voice my annoyance with zOS messages.
May I suggest that you open a formal problem with IBM for each of these?
LOL! This has been going on
On Fri, 19 Nov 2010 18:29:26 -0800, Edward Jaffe
edja...@phoenixsoftware.com wrote:
LOL! This has been going on so long that there is even a SHARE requirement
from
the 1980s against a similar message produced by this very same brain dead
IKJTSOxx parser.
We came across this a few months ago
At 02:07 + on 11/20/2010, Ted MacNEIL wrote about Re: zOS
messages.. totally true... almost totally useless:
May I suggest that you open a formal problem with IBM for each of these?
With all due respect.
That's akin to cleaning the Agean Stables.
-
Ted MacNEIL
eamacn...@yahoo.ca
On 11/19/2010 7:47 PM, W. Kevin Kelley wrote:
If you've given up, I can't help.
Yeah. I wish I was that powerful. ;-)
Over the years, I have helped a number of customers get changes made to
messages (primarily for automation purposes). This was done by the customer
opening a formal
28 matches
Mail list logo
