Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-22 Thread Veilleux, Jon L
From Shmuel Metz: Did he specify a member name or just a bare PDS name? If the former then I'd suggestopening a PMR; if the latter then I would say tha There is an ETR and IBM has recreated the problem. Yes, there was a member name. Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-21 Thread Shmuel Metz (Seymour J.)
In [EMAIL PROTECTED], on 02/15/2007 at 01:46 PM, Veilleux, Jon L [EMAIL PROTECTED] said: We ran into an interesting situation with z/OS V1.8. One of our folks uses a PDS for his listing dataset in ISPF 3.12 and 3.14. This stopped working when we upgraded to z/OS V1.8. After hitting enter we

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-16 Thread Matthew Stitt
In this case, you are probably dealing with a record length type of error. I've seen this in the past, where a PDS has a record length of 133, and the output was probably trying to use 121 for its length. Most likely someone in SUPERC development closed(?) a hole in code. In my opinion, B. A.

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-16 Thread Paul Gilmartin
In a recent note, Matthew Stitt said: Date: Fri, 16 Feb 2007 08:41:37 -0600 In this case, you are probably dealing with a record length type of error. I've seen this in the past, where a PDS has a record length of 133, and the output was probably trying to use 121 for its length.

SUPERC allocation errors z/OS V1.8 - fix

2007-02-15 Thread Veilleux, Jon L
We ran into an interesting situation with z/OS V1.8. One of our folks uses a PDS for his listing dataset in ISPF 3.12 and 3.14. This stopped working when we upgraded to z/OS V1.8. After hitting enter we got: Listing not generated. When we hit PF1 for more information we received: Abnormal

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-15 Thread Mark Zelden
On Thu, 15 Feb 2007 13:46:08 -0500, Veilleux, Jon L [EMAIL PROTECTED] wrote: We ran into an interesting situation with z/OS V1.8. One of our folks uses a PDS for his listing dataset in ISPF 3.12 and 3.14. This stopped working when we upgraded to z/OS V1.8. After hitting enter we got: Listing not

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-15 Thread Veilleux, Jon L
Mark Zelden wrote: Thanks for letting us know. But I just checked and that PTF is not marked PE (at least not yet), so what you really need to do is open a PMR with IBM to find out if this is WAD or BAD. Is it documented anywhere that the listing data setcan't be a PDS member? We have an

Re: SUPERC allocation errors z/OS V1.8 - fix

2007-02-15 Thread Paul Gilmartin
In a recent note, Mark Zelden said: Date: Thu, 15 Feb 2007 12:56:03 -0600 On Thu, 15 Feb 2007 13:46:08 -0500, Veilleux, Jon L [EMAIL PROTECTED] wrote: We ran into an interesting situation with z/OS V1.8. One of our folks uses a PDS for his listing dataset in ISPF 3.12 and 3.14.