HDTenEightyP/NetNews huggingface dataset:
From: merrick@magnus.acs.ohio-state.edu (Tom Merrick)
Subject: Re: How can I get mksysb use 2 tapes?
Organization: The Ohio State University
Date: Tue, 29 Sep 1992 12:01:15 GMT

In article <1992Sep28.184805.24269@tc.cornell.edu> mqh@theory.TC.Cornell.EDU (Mike Hojnowski) writes:
>In article <9209281638.AA00238@ucbvax.Berkeley.EDU> VRBASS@ATLVMIC1.VNET.IBM.COM writes:
>>rick@ransom.msc.cornell.edu (Rick Cochran) writes:
>>> tar doesn't support multiple tapes.
>>
>>This is certainly a bit of news to me!  (I don't have a 3.2 system in
>>front of me at this very moment, but...) "tar" under AIX has supported
>>multiple media for several years now (i.e., since the version that ran
>>on the RT).   I use it on a regular basis and get "proceeding to next
>>tape" messages all the time.  If it doesn't work on 3.2GB tapes, that's
>>an odd anomaly.
>
>Rick, I agree with Vance.  I routinely back up a 1G disk (about 1/3 full)  onto
>150 MB tapes.  It takes about 3, and works without a hitch.
>
>Mike Hojnowski
>Cornell University

The old AIX 3.1 version of tar did not support multiple tape volumes, and
gave an I/O error if you reached the end of media.  So, the AIX 3.1 mksysb
command used backup/restore to save the files.

Under AIX 3.2, mksysb uses tar, which now has multiple volume support.  But
note that tar has a problem in that it does not restore sparse files correctly.
So, even though you backup your system, you may not be able to restore from
the mksysb tape if some of your logical partitions are very full.

I found this by using tar to move a file system by doing a 
  tar -cvf - . | (cd /elsewhere; tar -xvf -)
this command failed when the receiving logical volume (the same size as the
original logical volume) filled up.  Upon inspecting the results, I found that
many of the files had increased in size.

Tom Merrick
Ohio State University
From: dls@achilleus.austin.ibm.com (David Skeen)
Newsgroups: comp.unix.aix
Subject: Re: Thread package on RS6000 AIX machine WANTED
Date: 30 Sep 92 23:16:48 GMT
Reply-To: David Skeen <dls@dce.austin.ibm.com>
Organization: IBM Austin (PSP)

A user-space threads package based on POSIX 1003.4a draft 4 will be
shipped with DCE.  IBM recently announced a planned availability date
of 18 Dec 92 for our first offering of DCE core services.
--
Dave Skeen                     IBM Internal: dls@achilleus.austin.ibm.com
D55/B905  Zip 9541             IBM VNET:     SKEEN at AUSTIN
Austin, TX 78758               Internet:     dls@dce.austin.ibm.com
Newsgroups: comp.unix.aix
From: dave@netcom.com (David A. Lee)
Subject: Problems with mbuf allocation
Keywords:  mbuf network driver tcpip smit no
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Tue, 6 Oct 1992 01:24:50 GMT

I am experencing a very anoying problem with the mbuf routines on AIX.
Our device driver uses mbuf clusters, and lots of them.
Typical load may only need 50 clusters at a time, but under peak 
conditions, we may need up to 1000 mbuf 4k clusters.    
The problem is that I cannot reliably set the mbuf pool to the ammount
I need.    Changing the value in smit that says "Maximum # of physical
4K pages for network buffers" (or something close, I'm not at site now)
SHOULD set "thewall" but does nothing I can detect, even after reboot.
Using "no -o thewall=6144" does set "thewall" but only occasionally
have I actually seen the buffer pool increase to anywhere near "thewall".
I have 512 MB of real system memory, and I am the only user of this machine
so I doubt that real memory availible is the problem.

One day, I used "no -o thewall=6144" and actually got the expected results.
The next day, (after a reboot, and REsetting the wall) it didn't work!
Our device driver is registering expected and low-water marks when 
It is configured, and I see the change reflected in "no -a" output.
However, the failure mode is that m_getclust() waits forever (M_WAIT)
and netstat -m reports increasing memory request denied/delayed counts,
then NFS, tcpip, and X-Windows hang and I have to reboot the system.

I am going to call austin tomorrow to try to get to the bottom
of this "feature" , but would appreciate anyone with suggestions about
what I could be doing wrong, or what else I could try.  If I cant get
this fixed, I will be forced to xmalloc() a huge chunk of memory at 
config time, but I really dont want to do this.

David Lee
dave@netcom.com








Newsgroups: comp.unix.aix
From: t2101fs@sun1.LRZ-Muenchen.DE ()
Subject: Stripping binaries - segmentation violation
Keywords: strip
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Sun, 27 Sep 1992 20:46:01 GMT

I translated EMACS under AIX 3.1.5 some time ago. To make the starting
of EMACS via NFS faster, I stripped the binaries (Same O.S. version).

The result was that EMACS dumps a core (segmentation violation). Why?
From: kevin@shady.UUCP (Kevin Smith)
Newsgroups: comp.unix.aix
Subject: Re: Problems with tar
Date: 5 Oct 92 13:53:25 GMT
Reply-To: kevin@shady.UUCP (Kevin Smith)
Organization: ShadeTree Software, Inc.

>In article <BIS.92Aug12161845@maud.ifi.uio.no> bis@ifi.uio.no (Bjorn Ivar Stark) writes:
>>Before I used this command when I e.g. moved a user from
>>one machine to another. 
>>
>>   root@obelix /u/obelix/d: tar cvfb - 20 sigurd |\
>>   maestria "cd /u/maestria/c; tar xfBp -" 
>>
>>Now it stops half way trough with the messages "broken pipe".
>>Any idea to what can be wrong.
>>--

Could be a block size problem.  Try smaller blocks (tar cvfb - 5) or
no blocks (tar cvf -).
-- 
	    | Email - !shady!kevin uunet!shady!kevin
Kevin Smith | Voice - (908) 874-7980
	    | Mail  - ShadeTree Software, Inc., 192 Capricorn Dr. #10,
	    |         Somerville, NJ  08876
From: arne@mango.mef.ki.se (Arne Elofsson)
Newsgroups: comp.unix.aix
Subject: Errors on GNU: ACM (Help needed)
Date: 29 Sep 1992 05:13:40 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu


I have tried to compile acm (flight simulator)
from GNU under aix3.1.X and X11R5. It compiles nice
after that I have changed a font in newPlayer.c
but when I tries to run it it crashes. It produces
two errors:
'cannot allocate colorcells' (it is due to a call
   to XAllocColor.
and
'Error in biding colors.' (due to a call to
   VBindColors)
I should note that I do not know much about 
X programming.
Any Help appreciated.
sincerly Arne
arne@mango.mef.ki.se
From: geo@george.austin.ibm.com (George Noren)
Newsgroups: comp.unix.aix
Subject: Re:  RS/6000 manuals ( was: AIX assembly language)
Date: 5 Oct 92 14:49:24 GMT
Organization: IBM AWD Early Systems Support

In article <1992Oct2.215036.21572@awdprime.austin.ibm.com>, woan@exeter.austin.ibm.com (Ronald S. Woan) writes:
|> In article <92275.111710HARVEY@wuvmd.wustl.edu> HARVEY@WUVMD.Wustl.Edu (Bill Harvey) writes:
|> >I've heard a rumor that IBM doesn't provide *any* manuals shipped
|> >with the purchase of AIX/RS6000.  The all have to be ordered (and
|> >*purchased*) separately.  Can anyone confirm or deny that?  That's
|> >just so contrary to IBM's mainframe policies that I find it difficult
|> >to believe.  You *always* get the basic manuals shipped *with* the
|> >purchase of the OS.
|> 
|> I think this is pretty much true (aside from the install manual)
|> because most customers tend to go the CDROM route (not every machine
|> needs to have one as long as one on the network does) for
|> documentation which is very cheap compared to buying hardcopy and
|> easier to update. You can of course choose to get hardcopy of anything
|> too. Your marketing rep should be able to provide you with available
|> documentation listings and pricing.
|> 
|> 
|> -- 
|> +-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+
|> +------------------------------My Employer----------------------------------+
|> + Ronald S. Woan                       woan@cactus.org or woan@vnet.ibm.com +
|> + other email addresses             Prodigy: XTCR74A Compuserve: 73530,2537 +

-- 
You get hardware usage manuals and software installation manuals, plus
a getting started with AIX package.  Basic software information is 
included in the InfoExplorer database that comes with the operating
system and should be installed on the harddisk.  This info database
includes the "man" pages for commands in the basic AIX package, plus
some other infomation.

You can order expanded information (using and managing info) as a disk
resident database, or you can order the CD-ROM which includes all info,
including the hardware maintenance manuals (with illustrations).  

You can also order hardcopy of most of the information in the softcopy
database, or you can print selected information from InfoExplorer as
needed (save a tree,... InfoExplore ;^} ).


Sincerely,
George Noren

+----------------------+-----------------------------------+----------------+
|AWD OEM Programs and  |Inet: geo@austin.ibm.com           |PH: 512/838-4930|
|Technology Transfer   |VNET: GEORGE at AUSTIN             |TL: 678-4930    |
|IBM Austin - Zip 2830 |AIX : geo@george.austin.ibm.com    |FX: 512/838-4851|
+----------------------+-----------------------------------+----------------+
Newsgroups: comp.unix.aix
From: greendog@max.physics.sunysb.edu (Michael D. Fischer)
Subject: Tex/MF/dvips with IBM laser printer
Organization: Institute for Theoretical Physics, SUNY at Stony Brook.
Date: Mon, 28 Sep 1992 19:50:38 GMT

Hello... I've successfully compiled Tex 3.14, MF, and dvips54 on an RS6000   
running AIX 3.2.  However, when we try to print on an IBM laser printer, the 
fonts come out "thin" and missing parts.  I don't know if this is a "write-  
white" printer, but I tried setting it up as one in the "modes.mf" file, and 
got no change.                                                               

Can someone tell me what I need to do to get this working correctly?  Thanks!

Michael
--
-------------------------------------------------------------------------
- Michael D. Fischer - greendog@max.physics.sunysb.edu - (516) 632-7966 -
- System Manager - Institute for Theoretical Physics - SUNY Stony Brook -
-------------------------------------------------------------------------
- These things take time...  But this time, I know...          - Thomas -
-  That the beauty of a dream...  Is you don't let it go...    - Dolby  -
-------------------------------------------------------------------------
Newsgroups: comp.unix.aix
From: bdh@eff.org (Brian D. Howard)
Subject: AIX/VMARK/Universe
Summary: Any other picky users out there?
Originator: bdh@eff.org
Keywords: Pick
Organization: The Electronic Frontier Foundation
Date: Sun, 4 Oct 1992 06:07:34 GMT

I have some responsability (I'm not sure how much less than all)
for an RS/6000 running AIX (whatever the current version is -1)
with VMARK's Universe, a PICK variant - about 1 major release and
who knows how many minor releases behind current.

Is there anybody out there?  Is there anyone else where print jobs
queued for one particular form get stalled in the default printer
queue?  Is there anybody else that has a vague sense that the 'universe'
number is made up randomly?

Having trouble with Exabyte 8mm tape backups?  Figure that you ought to
get more than one day per?

Is 'resizing' a real bitch?


Newsgroups: comp.unix.aix
From: jdh@bu-pub.bu.edu (Jason Heirtzler)
Newsgroups: comp.unix.aix
Subject: async IO on aix 3.2
Date: 30 Sep 92 01:30:11 GMT
Organization: Boston University, Information Technology

Does anyone have a short piece of code showing how to do
asynchronous IO on a serial port with AIX 3.2?

What I thought was something along the lines of:

  if (( fd = open( "/dev/tty0", O_RDONLY )) < 0 ) {
    perror( "open" );
    exit( 1 );
  }
  signal( SIGIO, fun );
  if ( fcntl( fd, F_SETOWN, getpid()) < 0 ) {
    perror( "F_SETOWN" );
    exit( 1 );
  }
  if ( fcntl( fd, F_SETFL, FASYNC ) < 0 ) {
    perror( "FASYNC" );
    exit( 1 );
  }
  for ( ;; ) {
    sigblock( sigmask(SIGIO ));
    while (sigflag == 0)
      sigpause(0);
    /* stuff */
  }

but F_SETOWN returns ENOTTY, and the information on async IO
is really sparse in Info Explorer..


----------------------------------------------------------------
Jason Heirtzler      1-617-353-2780            jdh@bu-pub.bu.edu
Sci Comp & Vis       Information Technology    Boston University

"Congratulations.  You aren't running Eunice."
        -- Perl "Configure" script
Newsgroups: comp.unix.aix
From: alb@moose.uvm.edu (Allan L. Bazinet)
Subject: Xstation printing and unwanted header pages
Organization: University of Vermont -- Division of EMBA Computer Facility
Date: Mon, 28 Sep 1992 01:57:53 GMT

I have a Proprinter attached to my Xstation 130.  In the print queue
setup, I specified that no header and trailer pages were required.
A header page still gets printed.  Is there some way to turn this
off?

AIX 3.2.? (PTF hell, we know it well.  Just what am I running?
Only Austin knows for sure. :-(  )

-------------------
Allan L. Bazinet
Systems Programmer
University of Vermont
Newsgroups: comp.unix.aix
From: jrh@jrh.uucp (James R. Hamilton)
Subject: Re: Port from ULTRIX to AIX
Organization: private system, Toronto, Ontario
Distribution: na
Date: Sat, 03 Oct 1992 15:50:51 GMT

In article <1992Sep28.073823.13119@u.washington.edu> quantum@u.washington.edu writes:
>
>Dear Netters,
>
>I ported some fortran programs from DEC ULTRIX V4.2A to IMB3090 AIX/370.
>The code runs well on the DEC machine, but it does not converge on the IBM
>machine.  
>
>The only machine-dependent segment of my code is several calls to "dlamch"
>of LAPACK.   Is there anyone on the net who had similar problem before?   
>I am running out of idea to debug this problem.  Any comment will be 
>appreciated.  
>
>The "dlamch" is appended at the end of this message for your information.
>I also did a little program to study the machine-dependent constants.  The 
>followings are the machine constants for two systems.  For the notations used,
>please refer to the comments of the attached program.
>
>IBM3090 AIX/370:  fvs -f'optimize(3)'
> e = 0.222044604925031308E-15
> s = 0.138178696881511145E-75
> b =  16.0000000000000000
> p = 0.355271367880050093E-14
> n = 14.0000000000000000
> r = 0.000000000000000000E+00
> m = -64.0000000000000000
> u = 0.539760534693402789E-78
> l = 63.0000000000000000
> o = 0.723700557733226211E+76
>
>DEC ULTRIX:  f77 -O
> e  = 1.1102230246251565E-16
> s  = 2.225073858507201E-308
> b  = 2.000000000000000
> p  = 2.2204460492503130E-16
> n  = 53.00000000000000
> r  = 1.000000000000000
> m  = -1021.000000000000
> u  = 2.225073858507201E-308
> l  =  1024.000000000000
> o  = 1.797693134862315E+308
>
>Tsung

    AIX/370 uses a base 16 floating point representation and looking at the
    above it would appear that whatever floating point represenation that 
    the VAX is using, underflows at a somewhat smaller value. The IBM base 
    16 representation can represent numbers nearing zero down to 16**-63 
    (which is 10**-75).  It looks like the VAX is not underflowing towards
    zero until something near 10-308.

    Since at least one machine is underflowing the results are different.  My
    guess from looking at the above output is that they are both underflowing 
    and the results are suspect even on the VAX where the algorithm does 
    converge.

                       --jrh

-- 

James R. Hamilton                                   inet: jrh@jrh.gts.org
telephone: +1 416 493 4162                          uunet: ...!uunet!jrh!jrh
Toronto, Canada                                     bitnet: jrh%jrh@uunet.uu.net
Newsgroups: comp.unix.aix
From: haedener@iacrs1.unibe.ch (Konrad Haedener)
Subject: Re: Tex/MF/dvips with IBM laser printer
Followup-To: <GREENDOG.92Sep28145038@max.physics.sunysb.edu>
Reply-To: haedener@iacrs1.unibe.ch
Organization: University of Berne
Date: Tue, 29 Sep 1992 07:54:23 GMT

In article <GREENDOG.92Sep28145038@max.physics.sunysb.edu>, greendog@max.physics.sunysb.edu (Michael D. Fischer) writes:
|> Hello... I've successfully compiled Tex 3.14, MF, and dvips54 on an RS6000   
|> running AIX 3.2.  However, when we try to print on an IBM laser printer, the 
|> fonts come out "thin" and missing parts.  I don't know if this is a "write-  
|> white" printer, but I tried setting it up as one in the "modes.mf" file, and 
|> got no change.                                                               
|> 
|> Can someone tell me what I need to do to get this working correctly?  Thanks!
|> 
|> Michael
|> --
|> -------------------------------------------------------------------------
|> - Michael D. Fischer - greendog@max.physics.sunysb.edu - (516) 632-7966 -
|> - System Manager - Institute for Theoretical Physics - SUNY Stony Brook -
|> -------------------------------------------------------------------------
|> - These things take time...  But this time, I know...          - Thomas -
|> -  That the beauty of a dream...  Is you don't let it go...    - Dolby  -
|> -------------------------------------------------------------------------

o  Have you configured dvips for the correct printer resolution (300 dpi ?) ?
   There is a config file read at run-time usually called `config.ps'.

o  After changing `modes.mf', have you re-generated your font files using
   `mf' ? Fonts generated for actual printer resolution ?

o  Does running `xdvi' or an equivalent on your .dvi files give you 
   confidence that your TeX is working properly ?

BTW: I have no problems with TeX-3.141 and PostScript output under 3.2.1
     using a non-IBM printer; if your problem persists, you should probably
     specify your printer model and post to comp.text.tex: people will then
     be able to tell you what type of engine you have.
-- 
Konrad Haedener                             Phone: +41 31 65 42 25
Institute for Physical Chemistry            FAX:   +41 31 65 44 99
University of Berne
Switzerland                                 haedener@iacrs1.unibe.ch
Newsgroups: comp.unix.aix
From: dedourek@jupiter.sun.csd.unb.ca (John DeDourek)
Subject: Problem with PTF numbers on AIX 3.2.[0-2]
Organization: University of New Brunswick
Date: Thu, 1 Oct 1992 19:56:34 GMT

My SE ordered two AIX 3.2 PTF's for me:
           U406646
           U406855
A tape arrived with 108 PTFs
I asked, via the usual SMIT menus to apply
           U406646
           U406855   with prerequisites
Installp/updatep and company actually applied 45 PTF's
Leaving 63 which were not installed

Of these, 25 were already installed on the system
and 2 were for a product (hanfs) which was not installed

Thus the tape contained 36 PTF's which were not installed.

(We must watch how much we install because of limited space on /usr,
and we don't want to commit until we try them.)

Now the number questions.  I note that PTF prerequisites appear to be
stated in terms of Uxxxxxx numbers only, without regard to products.
Does this mean that prerequisites are limited to only the same
subcomponent, or does IBM have a numbering problem?

I note that the tape in hand contains:
          bosadt.prof.obj    03.02.0000.0000.U404783
          bosadt.prof.obj    03.02.0000.0000.U404992
          bosadt.prof.obj    03.02.0000.0000.U405126

          bosadt.lib.obj     03.02.0000.0000.U404783
          bosadt.lib.obj     03.02.0000.0000.U404992
          bosadt.lib.obj     03.02.0000.0000.U405126

The smit log seems to imply that the three bosadt.lib.obj PTF's were
applied, but that the three similarly numbered bosadt.prof.obj PTF's
were not.

What is my current update status?  Are my subcomponents now out of sync,
or are the similarly numbered PTF's unrelated?  When ordering PTF's, is
it necessary to specify the subcomponent as well as the PTF number, or
are all PTF's with a given number automatically shipped?  Does smit/
install/update deal with identical PTF numbers correctly in processing
prerequisites?  Does the IBM process which makes update tapes deal
with identically numbered PTF's in generating prerequisites on the tape?

dedourek@jupiter.sun.csd.unb.ca
From: scott@austin.ibm.com
Newsgroups: comp.unix.aix
Subject: Re: AIX malloc and fault tolerance
Date: 25 Sep 92 17:39:09 GMT
Organization: IBM Austin
Originator: scott@porter.austin.ibm.com


In article <lc3noqINN5a3@utkcs2.cs.utk.edu>, moore@cs.utk.edu (Keith Moore) writes:
> In article <1992Sep23.200611.25088@awdprime.austin.ibm.com>, woan@exeter.austin.ibm.com (Ronald S. Woan) writes:
> > Wouldn't you just make sure your application vendor/developer wrote
> > their application to catch SIGDANGER?
> 
> Why should an otherwise portable C program that runs unmodified on
> every other UNIX system in the world have to trap SIGDANGER just so it
> can run on AIX?  Why should I, as an application developer, have to
> even waste one millisecond of my time learning about, working around,
> and testing for such things?  Why does IBM feel like it can change
> well-established interfaces at a whim and call the result compatible
> with Unix?
> 
> Why should a user or sysadmin of AIX boxes have to worry about whether
> all of the applications she wants to use have added AIX-specific code
> to trap for SIGDANGER in order that they not be nuked by the kernel?
> 
> The claim is that the lazy allocation strategy improves performance,
> but I don't understand why it's a big performance hit for AIX to
> simply maintain a count of the number of pages of backing store that
> are still available, decrement this count every time storage is
> allocated, and return an error if there aren't enough pages available.

Some mention has been made about why the AIX method of allocating paging space
is good.  If you aren't impressed with an application's ability to utilize
sparse arrays then consider the following.  The kernel defines many of its
data structures in virtual memory and makes them pageable.  These structures
are defined to be large to support a wide range of system configurations and
loads.  The sysadmin doesn't have to re-build the AIX kernel in situations where
other kernels would have to be rebuilt to increase the size of these structures.
What the sysadmin DOES have to do is make a reasonable estimate of the peak
utilization of paging space for the system and define enough paging space so
that the SIGDANGER event never occurs.

Granted, this doesn't take care of run-away processes or other unexpected uses
of paging space.  Granted, the whole SIGDANGER implementation is ugly and
breaks the conventions previously associated with the use of malloc().  But if
you are running mission-critical applications it seems reasonable to require
the system to be configured (i.e. enough paging space defined) to handle
peak loads. 

Providing the semantics of a malloc() which allocates paging space up front is
not an easy job on a pageable kernel.  If it was we would have done so long
ago.

Scott L. Porter                         IBM AWD Austin / AIX Kernel Development
                                        Internet: scott@austin.ibm.com
From: murai@rd.yahata.enicom.nsc.co.jp (Toshifumi Murai)
Newsgroups: comp.unix.aix
Subject: Re: Porblems with Console on 220 / Gt1
Date: 6 Oct 92 06:08:16 GMT
Organization: Nishi-Nihon Regional Office, NIPPON STEEL Information &
	Communication Systems Inc., Japan


Hello, about trouble of 220 with Gt1 graphic adaptor running AIX 3.2.*.

In article <hm342st.717180447@unidui> hm342st@unidui.uni-duisburg.de (Michael Staats) writes:

 |Path: mickey01!enicom!nscgw!dclsic!wnoc-tyo-news!sh.wide!sun-barr!olivea!spool.mu.edu!yale.edu!jvnc.net!gmd.de!Germany.EU.net!unidui!unidui!hm342st
 |From: hm342st@unidui.uni-duisburg.de (Michael Staats)
 |Newsgroups: comp.unix.aix
 |Summary: Char won't be erased on scrolling
 |Date: 22 Sep 92 16:56:48 GMT
 |Organization: Universitaet Duisburg GH
 |Lines: 33
 |NNTP-Posting-Host: unidui.uni-duisburg.de
 |
 |On the console sometime exactly two characters are not erased
 |when scrolling up. On one of our 320 (AIX 3.1) I get

We had the same trouble related 220(16inch moniter) with Gt1 graphic
adapter.  But, we resolved the trouble by installing patch for
/etc/drivers/sgadd.  This patch's number is IX28989(for AIX 3.2). 
I think that you can get the patch from IBM's CE.















--
---
	Nippon Steel Information & Communication Systems Inc.
		TEL : 093-872-6023   FAX : 093-872-6272
	Toshifumi Murai		murai@rd.yahata.enicom.nsc.co.jp