Greetings,
FYI, I opened a PMR regarding the issue of directory entry "shuffling" that was happening to me. Some responses from IBM: <quote> Well this behavior is built into DirMaint. DirMaint has to sort entries is some order mostly based upon CP rules. DirMaint tries to associate LINK and MDISK statements etc. However, you can tailor the DIRECTXA DATADVH file to sort differently. Again some of these entries are enfor ced by rules so be careful when changing your entry DIRECTXA may fail it anyhow. The behavior you are seeing is done when the entry is put on line. If you issue a DIRM SEND DIRECTXA DATADVH ... receive the file yo u can edit the file. Columns 18 - 21 of this file is a number which determines the statements relative placement. YOu will note that the LINK statement is 1710 and the MDISK statement is 1810. This would put the LINK statement after the MDISK statement. Now you can change these entries but I would change the LINK. MDISK has several rules around it's usage with other statements within a direc tory. Hope this helps. EDIT and make your changes. Then issue a DIRM FIL E command to put it back followed by a DIRM RLDData command. </quote> <quote> Again using your example. DirMaint did not move the comment rather it moved the LINK statement following the MDISK statement to be the last LINK in the LINK statements area. DIRECTXA DATADVH told it by default to put it before the MDISK statement. I believe in the file LINK is 1710 and MDISK is 1810 so LINK comes before MDISK. The comment was left where it was because we have no way of determining whether a comment is to the LINK beloow it or to a statement prior to it. So when you add a new link or mdisk statement if you have the idea that link comes before mdisk in mind your comments should be fine. Only when you delete a statement (we will leave the comment before it) or if you have a statement we may move or out of place will the comments be an issue. So consult the DIRECTXA DATADVH file is your answer. For the most part just remember that LINK statements come before MDISKS by default and comment accordingly you should be OK. </quote> So, the net result is that I put all my LINK statements before my MDISK statements and there was no shuffling of any comment(s) placed before each LINK or MDISK statement. IBM did ask me if I wish to open a requirement but I declined. <quote> Otherwise I would have to say you would have to open a requirement if you want this behavior to change. </quote> Regards, Mike
