And maybe extract the comment via QUERY MDISK?
On 11/02/2008, Ivica Brodaric <[EMAIL PROTECTED]> wrote: > > 5. Make the syntax similar to the one in SYSTEM CONFIG6. Integrate it into > SYSTEM CONFIG via INCLUDE and keep the source directory on PARM disks. > 7. Define the DRCT space in SYSTEM CONFIG the way warmstart and checkpoint > areas are > 8. Provide compile/nocompile option or a checkpointing system that would > not compile the directory at every IPL but would if the system is brought up > on a disaster recovery site. > > I could go on. That would be NICE. But that would be quite a sweeping > change. I was arguing for a special comment statement just for MDISK because > I think that is the statement that cries for comment option the most. If I > ever put any comment into the directory, then if it is not to do with the > userid itself (which is already catered for by "*") it is most likely to do > with MDISK. I would also like the minidisk comment statement to immediately > precede MDISK, not follow it. Plus your ideas 2 and 3. I would like the > comment to be query-able. I can imagine many situations where it would be > very useful and reassuring. > > > Ivica Brodaric > > On 11/02/2008, Alan Altmark <[EMAIL PROTECTED]> wrote: > > > > On Saturday, 02/09/2008 at 01:15 EST, Ivica Brodaric > > <[EMAIL PROTECTED]> wrote: > > > How about adding COMMENT parameter in MDISKOPT? Or even MDISKC > > statement? Yes, > > > it would reduce vertical readability, but there is not much space in > > the > > MDISK > > > statement and if you introduce asterisk, semicolon, or any other > > character as a > > > start of comment, you'd have to make sure you don't have any passwords > > that > > > look just like that. And if you use ESM that does password encryption, > > you > > > might have a password that in encrypted form looks like asterisk. > > > > If you're going to propose changes in directory syntax, why not go all > > the > > way? > > > > 1. Add a COMMENT statement that applies to the most-recently encountered > > non-COMMENT statement > > 2. Compile it into the object directory > > 3. Provide a way to extract the comment (e.g. QUERY VIRT 190 DETAILS) > > 4. Eliminate the F 80 requirement. > > > > Alan Altmark > > z/VM Development > > IBM Endicott > > > > >