Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Recent content by samizdat
-
IBM RS/6000 43P Modle 140: F04
Well this gets me to thinking. I had a 43P with this problem. Checking back on my hardware service call history notes, this particular one would not respond after we removed the battery and put it back in which was a known problem with the batch of workstations we had received. The CE ended up... -
AIX/Win 2K prnt srvr LPD srvc -- can't get LPD installed?
Check the services snap-in for "TCP/IP Print Server". That is the service that is installed by "Print Services for UNIX" and enables LPD. Start that service and you will be good to go. Also, by default, the startup type for this service is 'Manual'. Change it to 'Automatic'... -
IBM RS/6000 43P Modle 140: F04
Try popping the cover and removing the battery from the main board. Leave it off for a minute or so and put the battery back in. Then fire it up and see what happens. -
AIX/Win 2K prnt srvr LPD srvc -- can't get LPD installed?
You need to add the 'Print Services for UNIX' component to the W2K server. You can do that from Control Panel->Add/Remove Programs->Add/Remove Windows Components->Other Network File and Print Services. -
serial number of H70
lsattr -El sys0 | grep systemid returns something like: systemid IBM,01XXXXXXXX Hardware system identifier False Where XXXXXXXX can be numbers or letters. Strip away the 'IBM,01'. What's left is your serial number. May not be valid for all RS/6000's (definately not MCA machines) but... -
after smit cmd then enter the screen appears unreadable message
You will need to change the TERM variable which is different from term. type TERM=ibm3151 <ENTER> type smit <ENTER> You display should be OK. -
System hang on "518"
It's trying to mount the 'root' (/) and '/usr' from the network. Try typing: bootlist -om service The output will probably be 'ent'. To change it to boot from a cdrom, type: bootlist -m service cd0 # a specific cdrom or bootlist -m service cd # any cdrom device Look at the manpages for the... -
Filesystem Reduction?
Sorry, but I for got the step to create the filesystem from the command line. (Step 3) After creating the logical volume. It should be: monkey:root:/#> crfs -v jfs -d hd99 -m /usr/local -A -
Filesystem Reduction?
I've used both procedures below many times without a problem. Good luck! If there is not enough free space on the disk(s) to have both filesystems allocated, use the first procedure... 1. Backup to a tape drive if one is available. Use the backup command. monkey:root:/#> /usr/sbin/backup... -
mksysb help
This obviously does you no good if you cannot hook a tape drive up to the remote system if you need to restore but...Try this script: #!/bin/ksh # # @(#) Remote mksysb V1.00 # @(#) Updated for 4.3.3 12/03/2001 V1.02 #---------------------------------------------------------------------# #... -
How to remove APAR
I know 'aixmurderer' asked the question, so I don't want to step on any toes here, but yes you can uninstall the applied APAR. From the main SMIT menu select: o Software Installation and Maintenance o Reject Applied Software Updates (Use Previous Version) Then select from the software that is... -
Create bootable CD-RW for AIX
Good question. I got the cdrtools-0.1.10.23 package from the Bull site (http://freeware.bull.net). This package has a minimum requirement of AIX/V4.3.3. mkisofs source code is available from many places. freshmeat.net would be a good place to look. -
Create bootable CD-RW for AIX
Use mkcd as bjverzal mentioned. There is an option (-I) that will output the iso images as files named cd_image_123456.vol1...vol2...vol3, etc. instead of burning them to the writer. (which is a good thing, since I guess there isn't one attached to the RISC box). Refer to the man pages for mkcd... -
Problem detected
We replaced the I/O in two of our M80s. Obviously, we had to remove power and they both came back up with this message. The CE told me the reason was the removal of power. Just to be sure, I cleared the errlog and had the CE hang around while I rebooted, both servers came up normally.
