|
No, it wouldn't. Yes IBM is 'encouraging' you to use WDSC. No, they didn't take colors out of the text of WRKMBRPDM for this reason. I really believe that it was just simpler for them to remove all hex codes not in a certain range. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Booth Martin" <booth@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/26/2004 12:21 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: PDM Lost its colors - Part Deux Would this be a possible scenario? IBM wants PDM to go away, and for us to use newer tools. The color codes don't translate to the new tools. So IBM wants to dump them, like they dumped column separators. However, being bright people, they realize there will be a firestorm but they can't predict how big. What to do? Fly an easily reversible, low impact, trial balloon, and see what happens. In other words, if we complain it reverts. If we don't then it is implemented fully. --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: 08/26/04 11:45:41 To: Midrange Systems Technical Discussion Subject: RE: PDM Lost its colors - Part Deux Again, I do not think that IBM has went on a rampage to eliminate color. What happened is that if you had a member with strange hex codes that was not displayable on a 5250 screen, then you couldn't work with this with WRKMBRPDM. Granted, this shouldn't happen on a regular basis. But there are cases of a member having a corrupted text description occurring. And it was blowing up WRKMBRPDM. The easy fix for IBM was to rip out any codes that weren't of the most basic ones. At this point I think you'll need to submit a DCR to correct this issue. I suppose you could contact support line and suggest they fix that PTF to stop removing the color attributes. Actually, I'd try that first. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Dan Bale" <dbale@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/25/2004 09:01 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: PDM Lost its colors - Part Deux Well, dagnabit, we installed the TL04077 cume this past weekend. Our colors are gone now. PTF SI09069, the original "offending" PTF, was superseded by SI09530. I still don't get what it was that IBM "corrected". I've had colors on member and object descriptions for years, and never experienced the problems IBM mentions. The cover letter for SI09069 talks about "WRKLIBPDM *ALL FAILS WHEN YOU PRESS ROLLDOWN KEY" and "PDM will be corrected so that error message CPF5192 is not issued anymore when invalid(non-displayable) characters exist in the text description of a library, an object or a member. The invalid characters from the text description will be replaced with blanks." Is it time for a DCR? Anybody on V5R3 with the latest CUME having this problem? (Rob?) db > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx / Bruce Jones > > Sent: Thursday, August 12, 2004 6:19 PM > > > > We've noticed that wrkmbrpdm listing doesn't show colors of the text > > anymore. We had some member text with the color attributes but don't seem > > to honor the color anymore. The colors still work inside a source member > > just not on the member text. I assume our latest wave of ptf did this. > > > > Anybody else notice and have a workaround? > > Just a confirmation of what you experienced. I noticed this too at a prior > shop; they were on v5r2, couldn't tell you the cume level. The shop I'm at > now is on v5r2 at cume level TL03252, and I have my colors back! > > db -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
