home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cleveland.Freenet.Edu!ah739
- From: ah739@cleveland.Freenet.Edu (Leslie J. Somos)
- Newsgroups: bit.listserv.ibm-main
- Subject: Re: SYS1.BRODCAST
- Date: 15 Sep 1992 19:14:53 GMT
- Organization: Case Western Reserve University, Cleveland, OH (USA)
- Lines: 30
- Message-ID: <195cndINNi67@usenet.INS.CWRU.Edu>
- References: <IBM-MAIN%92091408445310@RICEVM1.RICE.EDU>
- Reply-To: ah739@cleveland.Freenet.Edu (Leslie J. Somos)
- NNTP-Posting-Host: slc4.ins.cwru.edu
-
-
- In a previous article, SSTSZXF@VCUVM1.BITNET (Zoltan Forray) says:
-
- >If I recall correctly, using the old UADS and ACCOUNT process, there was a
- >SYNCHRONIZE command to sync the BRODCAST file with the active UADS account
- >database.
- >
- >I think that ACF2 has a similar utility. Dont know about the other security
- >packages.
- >
-
-
- "SYNChronize" is a subcommand of the "ACCOUNT" command. It is IBM software,
- not part of ACF2 or other security packages.
-
- And yes, SYNC is what you need to clean up SYS1.BRODCAST .
-
- Once upon a time, when I was younger, our site was moving from TSO to ROSCOE
- for all the application programmers. So, I had to do mass deletes of TSO
- userids. Instead of doing it with the ACCOUNT command DELETE subcommand,
- I brought up the ISPF screen 3.1 and deleted entries in the SYS1.UADS
- partitioned data set directly. Things were OK for a while, just some
- strange console messages about people not receiving their NOTIFY job-end
- messages, but eventually the system _froze up_. The consoles were not
- responsive. After an IPL, we issued SYNC to clean out all the messages
- in SYS1.BRODCAST that no longer had a valid TSO userid waiting to receive
- them.
- So, yes, SYNC is what you need.
- --
- Leslie J. Somos ah739@cleveland.Freenet.edu
-