MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 1998

Re: CPI96C0 message



fixed

Marty,

At 02:17 PM 2/13/98 CST, you wrote:

>I know how that goes!  I've put the CPI96C0 change in the 'next'
>release, and I've looked over the 'CPF1269' PTF that was referenced.
>
>It's possible to put the code-only part of the change out as a V3R6
>PTF (and V3R7, V4R1, etc), without the change to the CPI96C0 message,
>but then the user (you) would have to manually change the CPI96C0 message
>to see the new information.  When you installed V3R7, you'd need to re-
>refresh the CPI96C0 message again, etc.
>
>Is that okay with you?  How bad do you want the change?
>Let me know,
>Marty Keech

 Would it be possible to put this change into V3R2 also?

 -mark

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact