Eric, I asked myself the same question when reading Alan's reply. I wondered about misc. SES files (maybe a PARTCAT, or something similar that might harbor information about DIRECTXA MODULE on the 51D disk).
VMSES/E keeps pointers in so many places, that it's risky to simply work outside the box. So I ran a SCANCMS (and old, but handy public utility), and found only: scancms /directxa/ * * d (hit allcase /DIRECTXA/ * * D (HIT ALLCASE ******************** BEGIN SCANCMS ********************* 5VMCPR30 MIGP510 D1 ============================== HIT :PART.DIRECTXA HELPCP :STATUS.CHANGED 5VMDIR30 MIGP510 D1 ============================== HIT :PART.DIRECTXA $DATADVH :STATUS.CHANGED :PART.DIRECTXA DATADVH :STATUS.CHANGED 5VMDIR30 MIGP520 D1 ============================== HIT :PART.DIRECTXA $DATADVH :STATUS.CHANGED :PART.DIRECTXA DATADVH :STATUS.CHANGED ******************** END SCANCMS *********************==== Files read...293 Files hit.....3 Rcds read.....82362 Rcds hit.....5 Ready, MAINT AT HALINVB1; T=0.14/0.14 09:07:34 So... as far as I can see, there's nothing to worry about by simply ensuring that the 51D disk is accessed R/W as D, and then issuing: ERASE DIRECTXA MODULE D Others have said the same thing about erasing the file, but I find it valuable to "show your work", just like in school. "Trust, but verify" :-) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Eric Lawler" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 05/23/2008 06:40 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: old DIRECTXA on MAINT 51D Can the MAINT 51D version of the DIRECTXA MODULE just be erased or is there anything to tidy up in the VMSYS:MAINT file below or in VMSES ? Thanks in advance for your help, Eric Lawler. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: 22 May 2008 22:53 To: [email protected] Subject: Re: old DIRECTXA on MAINT 51D On Thursday, 05/22/2008, John Romanowski wrote: > FYI, with VM5.3, a 2007 back-level DIRECTXA MODULE on MAINT D-disk > (51D), is found and used before the serviced DIRECTXA MODULE S2. > > IBM's VM5.3 file VMSYS:MAINT.CPDV.OBJECT MINIDISK MAP lists DIRECTXA > MODULE as part of the shipped contents of MAINT's 51D (D-disk). > > You could be bit by that on MAINT when you're not using a Directory > management product to update CP user directory. I have consulted with the Oracle at Delphi. I was informed that you have discovered one of the side effects of the Second Law of Thermodynamics (an unbalanced system tends towards Chaos). Apparently there was some sort of matter distortion wave and the DIRECTXA MODULE was duplicated. Not split in half, mind you, but duplicated. One copy was Evil and went to the 51D. The other, the Good copy, went to the 190. The Oracle and one of her High Priestesses, as one Voice, instruct me to say unto you all: "If thou hast z/VM 5.3, then thou hast both Good and Evil. The Resident Evil is to be destroyed at once. Leave not a trace or crumb from which it may regenerate. If thou hast an elder version of z/VM 5.3, then thou art immune and have the protection of the Gods." Sure. Right. This is the problem talking to an Oracle: they talk funny. Delete DIRECTXA MODULE from the 51D and all will be well. Unfortunately there is nothing we can do via a PTF to automatically delete the offending module. (Sysprogs get upset when we start deleting things *we* don't think should be on the system.) Consequently, no need for a call to the Support Center. We will place a notice in the PSP bucket. Thanks for bringing it to our attention! Alan Altmark z/VM Development IBM Endicott This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC.Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised and regulated by the Financial Services Authority. 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. E-mails 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 e-mail.
