>1) Do you  intend to support CMS 6  if listserv does NOT use  the Shared File
>System, which is an OPTIONAL component?
 
There  will probably  be  enough changes  in  CMS 6  to  adversely affect  the
operation of LISTSERV  even if it does  not use the SFS, despite  all that IBM
says. If LISTSERV does work under CMS6  or requires very little change, I will
do it.  If major  changes are  required, I  will stick  to what  I said  in my
statement.
 
>2) What if  there IS no HPO 6?  I strongly beleive there won't  be, based ont
>the fact that they are slowly sliding HPO features into base SP.
 
I do, too. Look at the first sentence in the statement.
 
>I think it would be a grave disservice to the network to not support SP/6
 
Valdis, did you have your glasses on?  I said CP release 6 would be supported,
unless it required an undue amount of conversion time etc etc (ie unless it is
so incompatible that I'd need less time to port LISTSERV to VAX).
 
>because there isn't an  HPO or XA version, if there WON'T  be an HPO version,
>and the  XA version is delayed  (XA SP/1 is  already in trouble, I  hear tell
>that SP/2 might be pushed back because of that).
 
Valdis, CMS6 is, if  my information is correct, based on CMS  5.5. Thus if CMS
5.5 is broken and delayed, CMS 6 is also likely to be broken and delayed.
 
>I'd hate to have to tell my  management that we can't upgrade to SP/6 because
>IBM isn't planning an HPO version, when we have aren't running HPO now....
 
And I'd  hate to have  to explain to  you how to keep  a copy of  CMS5 running
under CP6...
 
  Eric