Subfile Enhancement

Deskin, Bob Bob.Deskin at Cognos.COM
Thu Jun 21 08:25:09 CDT 2007


Our "list" is not really finalized until the feature is actually
implemented. Sometimes I'll add something to the list and the developers
tell me that it will take too long or be too destabilizing. And
sometimes we simply run out of time to do everything on the original
list. I do not want to set any false expectations.
 
As well, due to time and resources, we simply can't handle requests for
preview releases. The only time we "beta" is when there is something
quite new and we need some reality checking. For example, QKView was
tested by a few select customers.
 
We have considered releasing "patch" versions with some enhancements and
we're still thinking about it. Again, the effort in properly releasing
something that we have to support may make this impossible. We would
have to support the original release as well as the "patch" release. As
well, new features are built into the next version code stream. Once a
version goes into production, it's code stream is branched and then used
for hot site fixes only. We would have to have changes made to both code
streams. Unfortunately, these are the practicalities of software
development.
 
As for voting on enhancements, we did that a number of times in the
past. I can tell you that most of the desired features would have
required major and risky development effort. I think we actually
implemented maybe 20% of the features. It's also a major effort just to
run such a vote.
 
A few years ago we went through all outstanding enhancements and ranked
them by risk and effort. This is not to say that something requiring a
lot of effort won't be done, but it depends on the payback.
 
I go through that list and check what else has been requested. I also
solicit input from this list and see what the hot issues are. For
example, it's important to us to make migration as easy as possible,
particularly from MPE/iX to UNIX or Windows. It's also important to
provide alternative UIs. That's where QKView came from. We didn't want
yet another Windows client, but we wanted something that looked better.
 
There are always things we can do. We look at risk (both implementation
and resulting stability), effort, and return on investment (what impact
will the feature have). We also look at whether something is consistent
with our architecture and philosophy.
 
All that said, 8.4E will be shipping July/August. It has lots of new
features. F is in progress and will build on E. I have listened to what
I hear on this list and a number of the things requested are on the list
as possibles. I do appreciate the reality check and other opinions. It
certainly helps make my job easier and more interesting.
 
Bob
 
 
-----Original Message-----
From: Ken Langendock [mailto:Ken at Langendock.com] 
Sent: June 21, 2007 8:46 AM
To: 'Robert Mills'; Deskin, Bob
Cc: powerh-l at lists.sowder.com
Subject: RE: Subfile Enhancement



	Nah, those days are gone....lol
	 
	I for one would love to see a few patches with new features
released....instead of waiting for the next release....
	 
	Ken

________________________________

	From:
powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
Behalf Of Robert Mills
	Sent: June 21, 2007 8:27 AM
	To: Deskin, Bob
	Cc: powerh-l at lists.sowder.com
	Subject: RE: Subfile Enhancement
	
	
	Ken said, "Any chance we can see this "list" once it is
finalized????", to which I agree.
	 
	In the past the HP MPE Lab send a post to the HP3000 List asking
members to send in requests to be added to the next System Improvement
Ballot (SIB). The requests were then evaluated for the amount of effort
required to implement (if they could be done at all) and then the SIB
would be published. Each member of the list was given 10 votes that they
could allocate to entries on the SIB. The lab then sorted the SIB into
'highest votes first' sequence. Starting at the top of the list, the
amount of effort for each entry was accumulated until the total had
reached the amount of effort that they had allocated to the SIB. These
selected entries were then investigated in greater depth and those that
passed would be worked on for inclusion in the next release of the
operating system or as a patch.
	 
	The only question now is whether Cognos (Bob Deskin) would go
along with that.
	 
	regards, 
	  
	Robert W.Mills 
	Systems Development Manager 
	Pinnacle Arvato 
	(020) 8309 3604 
	 
	
	
________________________________

	From: Ken Langendock [mailto:Ken at Langendock.com] 
	Sent: 21 June 2007 12:49
	To: 'Deskin, Bob'; Robert Mills
	Cc: powerh-l at lists.sowder.com
	Subject: RE: Subfile Enhancement
	
	
	I think you should allow the DESCRIPTION option on any subfile
regardless of NODICT or not for documentation purposes. Even though it
will not appear in the subfile, it is still useful.
	 
	Any chance we can see this "list" once it is finalized????
	 
	Ken

________________________________

	From:
powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
Behalf Of Deskin, Bob
	Sent: June 20, 2007 12:26 PM
	To: Robert Mills
	Cc: powerh-l at lists.sowder.com
	Subject: RE: Subfile Enhancement
	
	
	Interesting. I've never seen this one before. I don't think we
would allow the description if it's a NODICT subfile but the dictionary
certainly has a DESCRIPTION option on the FILE and RECORD statements. I
don't know how difficult it would be to add to the subfile equivalents
and the routines. I'll add it to the list.
	 
	Thanks
	 
	Bob

		-----Original Message-----
		From: Robert Mills
[mailto:robert.mills at pinnaclearvato.co.uk] 
		Sent: June 20, 2007 12:17 PM
		To: Deskin, Bob
		Cc: powerh-l at lists.sowder.com
		Subject: Subfile Enhancement
		
		
		Bob,
		 
		Continuing with your original request for enhancement
requests;
		 
		Add a DESCRIPTION option to the SUBFILE statement within
QUIZ and QTP that could be read by QSHOW.
		 
		Where would you store the information? If it has a
dictionary, within the minidictionary file. If it doesn't, at the start
of the file with a leading integer value that points to the actual start
of data OR do not allow this option.
		 
		regards, 
		  
		Robert W.Mills 
		Systems Development Manager 
		Pinnacle Arvato 
		(020) 8309 3604 
		 

	 
	     This message may contain privileged and/or confidential
information.  If you have received this e-mail in error or are not the
intended recipient, you may not use, copy, disseminate or distribute it;
do not open any attachments, delete it immediately from your system and
notify the sender promptly by e-mail that you have done so.  Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20070621/a5b91828/attachment.htm


More information about the powerh-l mailing list