But were one of your original ideas revisited... if the 80-character limit 
to the directory records was eliminated, then comments could be in the 
same line with the actual statement (perhaps with a hex character such as 
'05'x or x'00'x as the field-mark?), then having to remember which related 
records follow a "live statement" (e.g. MINIOPT), and which precede it 
(the suggested COMMENT), and keeping them "in place" becomes a moot point.

That way comments just stay right with their pertinent statement.  No 
problems with sorting regardless of what application is dealing with them. 
 And when entering XEDIT "ALL" commands, the comments appear with the 
displayed statements, rather than being on a hidden line before or after 
the displayed record.  (Personally, MINIOPT has always bugged me).

Granted, the comments can be a little far to the right of an 80-byte wide 
the screen, but XEDIT's "SET VERIFY 1 *" takes care of that pretty easily.

Removing the 80-byte card restriction (antiquated given that very few 
sites have in-use physical card punches or readers any more) sets the 
stage for many other future directory statement improvements and 
extensions.

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Alan Altmark" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
02/11/2008 03:58 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: How comments treated by DIRMAINT






On Monday, 02/11/2008 at 09:46 EST, Thomas Kern <[EMAIL PROTECTED]> 
wrote:
> I like the idea of following the MINIOPT model and extending it to LINK,
> CPU, CRYPTO, SPECIAL, DEDICATE and now the COMMAND(?) statements.
> 
> Do you think the CLASS, OPTION and SPOOL statements also require 
comments?

I would limit my model to a single USER comment, and one per device.  That 

means each SPOOL statement could have a COMMENT.

Not COMMAND, since it is neither a user nor a device.

Alan Altmark
z/VM Development
IBM Endicott



 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. Emails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by email. 


Reply via email to