Hello Kris, Sorry to bug you. For awhile I gave up on this problem but I think I woul d like to resume it again. I wanted to know if this is a known issue. I was reluctant to create the DIRMAINT NAMES file since we have several service machines that process their reader files and I thought maybe there was a
global way of preventing this to happen instead of me having to add all t he machine names to the NAMES file. Since it seems that most people do not get this reader file there has to be some reason why we are getting it. Thanks, Mike Horlick [EMAIL PROTECTED] On Sat, 22 Jul 2006 23:25:34 +0200, Kris Buelens <[EMAIL PROTECTED] > wrote: >Any easy bypass: make a DIRMAINT NAMES file in which you code > :nick.VSExyz :userid.RUBBISH >issue DIRM FILE DIRMAINT NAMES >and DIRMAINT will send the file to user RUBBISH > >Kris, >IBM Belgium, VM customer support > >> Greetings, >> >> >> >> For the longest time we have been getting a spool file sent from >> DIRMAINT sent to a user who has its directory entry changed (DIRM >> FOR userid REPLACE). >> >> >> >> For example : >> >> >> >> q rdr XXXXXX >all >> >> ORIGINID FILE CLASS RECORDS CPY HOLD DATE TIME NAME >TYPE >> >> DIRMAINT 1813 A PUN 00000006 001 NONE 2006-07-15 00:02:08 XXXXXXX >DEVVM >> >> <mike> >Ready; >> >> > > >> >> This file once read in by CMS looks like: >> >> >> >> 2006/07/14 14:51:35 DVHBIU3427I Changes made to directory entry >> xxxxxxx by DUMMY at DEVVM >> >> 2006/07/14 14:51:35 DVHBIU3427I have been placed >> online. >> >> >> >> This presents a problem for a VSE guest or any service machine that >> may process files from its reader. >> >> >> >> Is there any way to prevent this file from being sent? >> >> >> >> Thanks, >> >> >> >> Mike >======================== ========================= ========================
